Re: VP 2 console clock losing time
Posted: Mon 15 Apr 2013 12:44 pm
If Cumulus is running (and as you say, continues to run for an hour after the change), it doesn't matter when the console clock changes, as the console clock is only used for logger data. If the console doesn't automatically adjust for you, the safest solution is to manually adjust it as soon as possible after the change, leaving Cumulus running.
I can't remember what happens to logger data when DST ends, whether two entries with the same timestamp get downloaded, or whether they are effectively superseded. I imagine that the logger just creates two sets of entries with the same timestamps, but I don't know what it then supplies when asked for them. And of course the Davis DLL also has a hand in things just to add to the complication; so the answer to what the console does may not be the full story. But the only full and safe solution to the DST issue is to always run the station and PC on standard time.
I can't remember what happens to logger data when DST ends, whether two entries with the same timestamp get downloaded, or whether they are effectively superseded. I imagine that the logger just creates two sets of entries with the same timestamps, but I don't know what it then supplies when asked for them. And of course the Davis DLL also has a hand in things just to add to the complication; so the answer to what the console does may not be the full story. But the only full and safe solution to the DST issue is to always run the station and PC on standard time.