FAQ: Difference between revisions

690 bytes added ,  11:48, 18 December 2010
Cumulus takes a long time to download the data from my Davis station at start up
(Cumulus takes a long time to download the data from my Davis station at start up)
Line 212: Line 212:
==The peak values on my graphs are not the same as my extreme values==
==The peak values on my graphs are not the same as my extreme values==
The graphs are snapshots of the data, taken once a minute while Cumulus is running. If the extreme value did not coincide exactly with the point at which the data was added to the graph, then it will not appear on the graph. This is most noticeable with wind gusts, the value of which can change rapidly, even over a period of a minute.
The graphs are snapshots of the data, taken once a minute while Cumulus is running. If the extreme value did not coincide exactly with the point at which the data was added to the graph, then it will not appear on the graph. This is most noticeable with wind gusts, the value of which can change rapidly, even over a period of a minute.
==Cumulus takes a long time to download the data from my Davis station at start up==
When Cumulus starts, it asks the station for all the data from the logger since the last time it was running. If the timestamp that it supplies does not exactly match the timestamp of an entry in the Davis logger, the station has a strange 'feature' where it decides to send the entire contents of the logger. This will take some time to download, during which the Davis console display will appear freeze.
It is recommended that you set the logging interval in Cumulus to the same interval as the station, then Cumulus will be able to make sure it uses a timestamp that matches an entry in the logger.