Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Topics about the Beta trials up to Build 3043, the last build by Cumulus's founder Steve Loft. It was by this time way out of Beta but Steve wanted to keep it that way until he made a decision on his and Cumulus's future.
Hi!
I have CumulusMX b3038 installed on my Raspberry Pi. But it every day shows a record 35°C at 3 o'clock am! Data on Awekas, Weather Underground and PWS Weather are OK. This record is saved just in today.ini file. The same problem appears in year.ini:
I think that, I have to upgrade Cumulus to the newest version - b3043. If that is a problem, can anyone tell me how to upgrade Cumulus from build 3038 to build 3043.
Just before the time that the problem occurs, turn on debug logging and data logging. After the problem occurs, zip up the latest MXdiags file and attach it to a reply here.
To upgrade, just copy the files contained in the zip file into your existing installation, as it says in the MX FAQ.
2017-05-20 15:50:11.566 Reading rain total
2017-05-20 15:50:17.158 ReadSerial error The operation has timed-out.
2017-05-20 15:50:17.833 ReadSerial error The operation has timed-out.
2017-05-20 15:50:18.390 ReadSerial error The operation has timed-out.
2017-05-20 15:50:19.459 ReadSerial error The operation has timed-out.
2017-05-20 15:50:19.968 Reading rain total
2017-05-20 15:50:26.404 ReadSerial error The operation has timed-out.
2017-05-20 15:50:26.906 ReadSerial error The operation has timed-out.
2017-05-20 15:50:27.590 Reading rain total
Last edited by blackie on Tue 23 May 2017 5:28 am, edited 1 time in total.
I can't unzip that file, it seems to be corrupt/incomplete.
Those messages are normal, they are just Cumulus having to retry reading data from the station; La Crosse stations are a pain and don't give up their data easily. They are also known to have problems with USB/Serial adapters, and presumably you are using one of those. These 'spikes' are likely to be just corruptions caused by interference from somewhere. Have you set a 'spike removal' value in the calibration settings? They are there for exactly this situation.
The spike removal setting works for both highs and lows - it's not an absolute value, it works on the difference between consecutive readings. So, if you set it to 30, any reading more than 30 degrees higher or lower than the previous reading is ignored. A setting of 30 is probably too high, you should set it just high enough that it could never trigger for a valid change in temperature, but no higher.