5,838
edits
FAQ: Difference between revisions
m
→On restarting Cumulus, it did not successfully read all data from when it last ran: made last paragraph clearer
(→On restarting Cumulus, it did not successfully read all data from when it last ran: Added numbering to paragraphs) |
m (→On restarting Cumulus, it did not successfully read all data from when it last ran: made last paragraph clearer) |
||
|
#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 the time in [[today.ini]] to exactly match a logging time in your station, the restart should then read all subsequent timed storage locations in the station. This only applies to makes of stations that store the exact time with each logging, not to station types that only record duration since previous logging.
#If you are very skilled in understanding how Cumulus uses its various files, it is possible (when you stop Cumulus) to back up all the Cumulus log files, before you perform the rewind and a restart,
== Cumulus read some invalid figures from my station ==
| |||