Data Set locked on a single set of values for 3 days+

[gvheard]

Don't quite know what happened here, but for 3 days, Cumulus just registered the same temperature. Unfortunately I was working away so was not able to shut the program or machine down. Came home late yesterday, looked at the base station and it was reading the correct temperature (3.6C) whereas the Cumulus display was 6.5. Shut Cumulus down and restarted, and it picked up with the correct readings. Below are the readings for the couple of hours, as you can see apart from the time, they are identical. If the system was recording correctly, then the correct data is in the memory of the base station, is there anyway of telling Cumulus to reload that data?

17/02/11,20:00,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,20:10,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,20:20,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,20:30,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,20:40,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,20:50,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:00,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:10,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:20,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:30,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:40,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,21:50,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,22:00,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5
17/02/11,22:10,6.5,83,3.8,6.4,12.4,109,0.0,0.3,1000.7,16.5,21.4,30,6.7,4.4,6.5

Also below is an extract from a file from the Diags directory

14/02/2011 00:00:00.590 : === Day reset for 14/02/2011
14/02/2011 00:00:00.599 : Raintotal = 16.5 Raindaystart = 16.2000007629395
14/02/2011 00:00:00.599 : Rainyesterday (calibrated) set to 0.299999237060547
14/02/2011 00:00:00.599 : Raindaystart set to 16.5
14/02/2011 00:00:01.049 : Writing todayfile, LastUpdateTime = 13/02/2011 23:50:00 raindaystart = 16.5
14/02/2011 00:00:01.179 : === Day reset complete
14/02/2011 00:00:01.404 : Writing todayfile, LastUpdateTime = 14/02/2011 00:00:01 raindaystart = 16.5
14/02/2011 00:10:00.837 : Writing todayfile, LastUpdateTime = 14/02/2011 00:10:00 raindaystart = 16.5
14/02/2011 00:20:01.218 : Writing todayfile, LastUpdateTime = 14/02/2011 00:20:00 raindaystart = 16.5
14/02/2011 00:30:00.934 : Writing todayfile, LastUpdateTime = 14/02/2011 00:30:00 raindaystart = 16.5
14/02/2011 00:40:01.154 : Writing todayfile, LastUpdateTime = 14/02/2011 00:40:00 raindaystart = 16.5

15/02/2011 00:00:01.376 : === Day reset for 15/02/2011 00:00:01
15/02/2011 00:00:01.403 : Raintotal = 16.5 Raindaystart = 16.5
15/02/2011 00:00:01.403 : Rainyesterday (calibrated) set to 0
15/02/2011 00:00:01.403 : Raindaystart set to 16.5
15/02/2011 00:00:02.501 : Writing todayfile, LastUpdateTime = 14/02/2011 23:50:00 raindaystart = 16.5
15/02/2011 00:00:02.775 : === Day reset complete
15/02/2011 00:00:03.105 : Writing todayfile, LastUpdateTime = 15/02/2011 00:00:02 raindaystart = 16.5
15/02/2011 00:10:00.940 : Writing todayfile, LastUpdateTime = 15/02/2011 00:10:00 raindaystart = 16.5
15/02/2011 00:20:00.581 : Writing todayfile, LastUpdateTime = 15/02/2011 00:20:00 raindaystart = 16.5
15/02/2011 00:30:00.689 : Writing todayfile, LastUpdateTime = 15/02/2011 00:30:00 raindaystart = 16.5
15/02/2011 00:40:01.610 : Writing todayfile, LastUpdateTime = 15/02/2011 00:40:01 raindaystart = 16.5
15/02/2011 00:50:00.971 : Writing todayfile, LastUpdateTime = 15/02/2011 00:50:00 raindaystart = 16.5
15/02/2011 01:00:00.820 : Writing todayfile, LastUpdateTime = 15/02/2011 01:00:00 raindaystart = 16.5
15/02/2011 01:10:00.773 : Writing todayfile, LastUpdateTime = 15/02/2011 01:10:00 raindaystart = 16.5

and it carries on like that up to last night when I reset it.

Any ideas what could have caused the problem?

Thanks

Gary

[werribee_au]

If the system was recording correctly, then the correct data is in the memory of the base station, is there anyway of telling Cumulus to reload that data?

The following text is from this post by KJM
https://cumulus.hosiene.co.uk/viewtopic.p ... 168#p25168

Every time Cumulus starts, it takes a backup of the data files and puts them in the backups folder. Each backup is inside a folder whose name is the timestamp of the backup time. If you find at any time that bad data has been downloaded from your station, you can stop Cumulus and 'rewind' by using the appropriate backup files to over-write the ones in the Data folder. Cumulus will then re-download the data from your station (assuming it is a type which has a data logger), and this may well correct the problem

[steve]

Any ideas what could have caused the problem?

The usual causes of all of the data 'flatlining' are:

1. Loss of USB connection
2. One or more the data readings being completely out of range
3. The station simply stops writing new data to its memory
4. Others that I've forgotten

For some of these you would see an error message in the diags log at the time the problem first occurred, and depending on the version of Cumulus, it may also flash the error light.

[steve]

The following text is from this post by KJM
https://cumulus.hosiene.co.uk/viewtopic.p ... 168#p25168

Which is itself a quote from the help file

[werribee_au]

The following text is from this post by KJM
https://cumulus.hosiene.co.uk/viewtopic.p ... 168#p25168

Which is itself a quote from the help file

Now I did look the help and couldn't find it because I thought I had read something about backups before.
Had another look and this time I did find it.