Two errors in Cumulus MX 3.21.1 b3205

[mcrossley]

OK, can you switch on data and debug logging before you close down today, then post the latest MXdiags file after you start CMX tomorrow. Thanks.

[BrunswickWeather]

After starting CumulusMX next day
Line 4136
2022-10-11 09:50:53.016 Spike removal: Max rainfall rate spike value exceed

Diags file attached

[EA3CH]

OK, can you switch on data and debug logging before you close down today, then post the latest MXdiags file after you start CMX tomorrow. Thanks.

MXdiags is here.

[mcrossley]

OK, I see the problem, thanks for the diags, I'll get a patch release out soon.

[EA3CH]

OK, I see the problem, thanks for the diags, I'll get a patch release out soon.

With the new update, the problem of the wild Rain Rate values has not been solved.

A question: is it necessary to update the whole folder?
or only the CumulusMX.exe file must be updated?

The station is FROGGIT WH1080SE

[sfws]

A question: is it necessary to update the whole folder?
or only the CumulusMX.exe file must be updated?

For release 3.22.1, which is the one your recent post references as having a bug with the rain code fix, the release announcement specifically mentions a change in another file, so yes you are expected to update what you call the whole folder (actually whole set of multiple files in multiple directories).

In general, release announcements do not mention all the changes since the previous release, so it is impossible to work out easily which files have changed (you cannot even use "date-modified" because the changes can be done at different dates, and some might even have been done before date of previous release, but not included in that previous release because of either need to urgently fix some bug or the interdependencies between files). This is why the frequently mentioned instruction is to upgrade everything in the zip. If you customise any files, then modify the file name (prefix with something like "my" or "_" or store in a different directory), so your customised files are not overwritten.

[mcrossley]

Version 3.22.2 is now available that should resolve the bug introduced in 3.22.1

As @sfws says the advice is to update everything. But you can use the checksum file in release zips to compare your installation and see which files have changed if you really need to.