Page 1 of 1

Setting Davis console time

Posted: Thu 03 Apr 2014 2:57 pm
by XBower
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

Re: Setting Davis console time

Posted: Thu 03 Apr 2014 3:29 pm
by steve
Presumably you don't leave Cumulus running overnight? When it does the daily clock setting at around 0400, it should do it within a couple of seconds of the hour/minute. At start up, you can wait until a few seconds before the minute before starting Cumulus.

Re: Setting Davis console time

Posted: Sat 05 Apr 2014 10:53 am
by XBower
Hi.

That's correct, I don't run the system 24/7 (yet).
I simply wrote a short program that holds my startup sequence until the system time reaches a specific second before starting Cumulus.
There seems to be an average of 13 seconds after startup until the set time command is issued, so I think this will work.

Thanks

Re: Setting Davis console time

Posted: Sat 05 Apr 2014 11:21 am
by steve
I think that as a possible future enhancement, it could delay setting the clock until after it has downloaded any logger data, then set the clock on the next minute after that; rather than pausing when it starts up, doing nothing for up to a minute.