5,838
edits
FAQ: Difference between revisions
m
→On restarting Cumulus, it did not successfully read all data from when it last ran: add 2 more cross- ref (1 each para 3 and 4)
m (→On restarting Cumulus, it did not successfully read all data from when it last ran: made last paragraph clearer) |
m (→On restarting Cumulus, it did not successfully read all data from when it last ran: add 2 more cross- ref (1 each para 3 and 4)) |
||
|
#Use the 'rewind feature' of Cumulus. Look in the backup folder for the backup which Cumulus took when it first started up today. Stop Cumulus, copy all of the files from that backup folder into the data folder (overwriting the files which are there) - this restores Cumulus to the state it was in before you ran it today. Make sure nothing else on the computer is running that might affect either your station or Cumulus log files. You can look in [[today.ini]] to see the date and time that you will rewind back to. Start Cumulus and it should then download the data (from the date and time in the "today.ini"), to get up to date. (Ignore remaining paragraphs if this has worked).
#As mentioned elsewhere if option 1 does not work, you can choose an older back-up and rewind back further providing the information is in the station logger. Remember however, that when you restart Cumulus it will only have access to observations at the station's logging interval, so any extremes between logging times previously picked up by the frequent querying of the station while Cumulus was previously running during the period you are now rewinding may be lost.
#If Cumulus still cannot catch-up, then you can try this more risky solution, you can edit
#If you are very skilled in understanding how Cumulus uses its various
== Cumulus read some invalid figures from my station ==
| |||