Setting Davis console time
Posted: Thu 03 Apr 2014 2:57 pm
Hi all.
I have been experimenting a bit with the "Synchronise station clock" option lately.
First, YES - it DOES work with the WeatherLinkIP logger, at least with the latest firmware (1.1.1).
I would say that these lines from the diag file shows this:
2014-04-03 16:23:27.338 : VP2: Setting station clock
2014-04-03 16:23:27.338 : y=2014 m=4 d=3 h=16 m=23
2014-04-03 16:23:29.401 : VP2: SetStationTime_V res = 0
I have, as many others, noticed that the time on the console lags sometimes quite a lot.
I know that this is because the set time command only accept a 1 minute resolution, and Cumulus simply strips off the seconds from the current time when setting the console time.
What I was thinking --
Would it not be possible to synchronise the issuing of this command with the PC clock, at xx seconds sharp?
Either at a predefined value or user configurable, to take into account some local network latency.
I would imagine that this could make the initialising process a bit longer when starting Cumulus, but I for one would gladly take that if it would insure an accurate clock on the console at all times.
I use a Davis Vantage Vue station with WeatherLinkIP logger and Cumulus 1.9.4 b1085.
Regards
I have been experimenting a bit with the "Synchronise station clock" option lately.
First, YES - it DOES work with the WeatherLinkIP logger, at least with the latest firmware (1.1.1).
I would say that these lines from the diag file shows this:
2014-04-03 16:23:27.338 : VP2: Setting station clock
2014-04-03 16:23:27.338 : y=2014 m=4 d=3 h=16 m=23
2014-04-03 16:23:29.401 : VP2: SetStationTime_V res = 0
I have, as many others, noticed that the time on the console lags sometimes quite a lot.
I know that this is because the set time command only accept a 1 minute resolution, and Cumulus simply strips off the seconds from the current time when setting the console time.
What I was thinking --
Would it not be possible to synchronise the issuing of this command with the PC clock, at xx seconds sharp?
Either at a predefined value or user configurable, to take into account some local network latency.
I would imagine that this could make the initialising process a bit longer when starting Cumulus, but I for one would gladly take that if it would insure an accurate clock on the console at all times.
I use a Davis Vantage Vue station with WeatherLinkIP logger and Cumulus 1.9.4 b1085.
Regards