5,838
edits
FAQ: Difference between revisions
m
→Davis to Cumulus skips one logged set of readings: new
m (→How do I correct my all-time (or monthly all-time) records?: Slight re-sequencing of existing material to emphaise edit logs before ini files.) |
|||
| Line 701: | Line 701: | ||
Note that this situation can also occur if you close Cumulus and then start it up again very soon afterwards, for similar reasons. There is nothing that Cumulus can do about this, it is an issue with the logger (or Virtual VP, which behaves in the same way). | Note that this situation can also occur if you close Cumulus and then start it up again very soon afterwards, for similar reasons. There is nothing that Cumulus can do about this, it is an issue with the logger (or Virtual VP, which behaves in the same way). | ||
== Davis to Cumulus skips one logged set of readings == | |||
The Davis DLL which Cumulus 1 uses never downloads the latest archive record. Consequently, if you have Davis and Cumulus set to logging every five minutes and restart Cumulus at 07:33, the archived readings up to 07:25 will be read across to Cumulus, the set of readings stored on Davis at 07:30 will be skipped, and Cumulus will create its own logs from 07:35 onwards. | |||
== My Davis console clock is not exactly the same as my PC clock, but I have "Synchronise station clock" selected == | == My Davis console clock is not exactly the same as my PC clock, but I have "Synchronise station clock" selected == | ||