Time Synchronization Issue

kinder · **Posted:** Tue Jan 25, 2011 7:45 am

Hello.After using for a month cumulus with davis vantage pro 2,i have found a small problem that is related with time synchronization between the pc and the davis console.
First of all i have checked the option to synchronize davis clock to pc,and this thing never worked for me.
Secondly i found a small isue related to time also.Every time i start cumulus,the cumulus downloads new data from the datalogger(the ip version).For that time the data is downloading,the console looses the seconds that this procedure lasts.
So lets say that you have a davis console and a pc running at the same time.The time is entered by hand on the console,cause of the automatic clock synchronization not working.Every time you start cumulus,the console looses 20 seconds or 15 or 30,and thats a big problem if u haven't noticed that,because after 2 or 3 reboots,the davis and the pc time differs around 1 or more minutes.
I am using latest stable cumulus v1.9.0 (958) and the operating system is windows 7 with all the updates till now installed.The davis console has the latest firmware(1.90 US) and the datalogger has also the latest firmware)(i think 1.09).All internet feautures of the weatherlink ip are disabled from web interface,and the davis console runs on ac power,with a standby ups and has new batteries.
Is this normal or i have to worry?:P

steve · **Posted:** Tue Jan 25, 2011 9:02 am

Please zip up the diags folder and attach it, so I can see what happens when Cumulus attempts to set the clock.

As for the console losing time during the logger download; the console does 'stop' while data is being downloaded (you can see that the wind speed doesn't update, for example). I didn't know that this also affected the clock.

Could you update your profile, please?

kinder · **Posted:** Thu Jan 27, 2011 6:39 am

I will do that as soon as i have physical access to the laptop running the weather station.

kinder · **Posted:** Fri Feb 04, 2011 4:27 pm

for some reason i cant attach a file

steve · **Posted:** Fri Feb 04, 2011 4:38 pm

Some file types aren't allowed - is it a zip file?

HopeMaineWx · **Posted:** Tue Mar 29, 2011 2:28 am

Hi Steve,

Just curious to see if this ever got answered, maybe in another post? I too, can't seem to keep my PC/Cumuls synched with the clock on the Davis Vantage Vue or vice versa. There's always a 2 min difference. I have tried checking and unchecking the option for synching Davis clock to PC.

This also effects my high wind gusts, for example, today the console had a max gust of 25mph at 9:16am, but Cumulus had a max of 24 at 9:17am. I have noticed this has happened several times that Cumulus hasn't obtained the same high gust as the console.

Maybe these 2 issues aren't related, not sure.

Thanks,
Mike

steve · **Posted:** Tue Mar 29, 2011 7:07 am

HopeMaineWx wrote:

Just curious to see if this ever got answered, maybe in another post?

Not that I'm aware of; some people never respond to my requests for further information or come back and say they have resolved the problem.

Quote:

I too, can't seem to keep my PC/Cumuls synched with the clock on the Davis Vantage Vue or vice versa. There's always a 2 min difference. I have tried checking and unchecking the option for synching Davis clock to PC.

Note that Cumulus only sets the Davis clock at start up, and can only do it to the start of the current minute, so there will always be periods when they disagree by one minute, and they are then likely to drift. I've just looked at mine, and they were between 1 and 2 minutes different. I restarted Cumulus, and it brought the station correctly into line with the PC (with the above proviso). Could you try the same (with the synchronise setting turned on) and see if it works OK? If not, please zip up the diags folder and attach it, and I'll see if I can see why it was unable to set the clock.

Quote:

This also effects my high wind gusts, for example, today the console had a max gust of 25mph at 9:16am, but Cumulus had a max of 24 at 9:17am. I have noticed this has happened several times that Cumulus hasn't obtained the same high gust as the console

Have you tried this: http://wiki.sandaysoft.com/a/FAQ#My_Davis_station_shows_a_higher_maximum_wind_speed_than_Cumulus?

HopeMaineWx · **Posted:** Fri Apr 01, 2011 2:26 am

Hi Steve,

I have attached the diags folder. When I restart Cumulus the synch of the clock checked off in the settings, I dont the clock on the console change at all, it remains 2 minutes behind. Today's wind gust matched speeds correctly, but it was 30 minutes later so it may just be coincidence that it recorded the same high gust as the console.

Quote:

Have you tried this: http://wiki.sandaysoft.com/a/FAQ#My_Davis_station_shows_a_higher_maximum_wind_speed_than_Cumulus?

[/quote][/quote]

I just added the line to the ini file from the FAQ, we'll see if this has any effects.

Thanks,

Mike

steve · **Posted:** Fri Apr 01, 2011 7:23 am

Cumulus is telling the Davis DLL to set the clock, and the DLL says it has successfully done it:

3/31/2011 22:19:40.847 : VP2: Setting station clock
3/31/2011 22:19:40.847 : y=2011 m=3 d=31 h=22 m=19
3/31/2011 22:19:40.988 : VP2: SetStationTime_V res = 0

Perhaps it's a bug/feature of WeatherlinkIP? Kinder is also using one.

HopeMaineWx · **Posted:** Sun Apr 03, 2011 1:19 am

Thanks Steve for looking into it. Not sure what the deal is; the two never stray 2 minutes apart. Weird. Im not using WLIP, just the standard WL.

steve · **Posted:** Sun Apr 03, 2011 7:21 am

HopeMaineWx wrote:

Im not using WLIP, just the standard WL.

But you're using TCP/IP? So how does that work?

HopeMaineWx · **Posted:** Sun Apr 03, 2011 2:31 pm

Its how I got Virual VP to work with WL and Cumulus. I originally had the setup has a USB connection, but when using third party software you need to emulate serial port. For what ever reason, I was either having issues or exactly knowing hwat I was doing, but in the process of getting evertything to work I ended on TCP/IP.

steve · **Posted:** Sun Apr 03, 2011 3:57 pm

Ah, Virtual VP, useful information; I thought you were talking to the station direct. You don't have the 'protect console' setting checked, by any chance? That would stop VVP passing on the 'set clock' command. But I think someone else had problems getting Cumulus to set the clock via VVP. It's either another incompatibility between the Davis DLL and VVP, or possibly (given that it doesn't seem to work with WLIP either) a problem with the set clock command in the Davis DLL when using TCP/IP.

HopeMaineWx · **Posted:** Mon Apr 04, 2011 2:18 am

You the man Steve! I did have "protect console" checked. I unchecked it, restarted VVP as well as Cumulus. Upon the restart of both programs, the consoles time changed to match the computers. Thanks for the dudiligence and help!

Mike

steve · **Posted:** Mon Apr 04, 2011 7:27 am

Great - that confirms that 'set clock' does work with TCP/IP, so the problem the original poster had/has is presumably in WLIP.

	It is currently Fri May 24, 2013 2:46 am
Please click here before posting. Help me to help you!
Useful Links: Cumulus FAQ • Enhancement requests • Wiki (documentation)
Please put your approximate location into your profile
Add your web site to the Cumulus user map
Vantage Pro2 users with firmware 3.00 should upgrade to fw 3.12 and Cumulus 1.9.4
Latest Cumulus release v1.9.3 (build 1059) - Feb 09 2013 Latest Cumulus beta v1.9.4 build 1077 - May 23 2013 --> Latest Cumulus Realtime v1.0.0.5 - Sep 05 2009

Sandaysoft

Time Synchronization Issue

Who is online