WXforum.net
May 18, 2013, 11:46:49 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
Members: 6608  •  Posts: 178115  •  Topics: 18094
Please welcome TargY, our newest member.
Welcome to the the new hosting for WXforum.net.
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: computer time slipping back  (Read 958 times)
0 Members and 1 Guest are viewing this topic.
Davidb
Senior Member
**
Offline Offline

Posts: 88


WWW
« on: November 07, 2011, 04:02:46 AM »

Since we had a few power cuts last week,  the Weather Station computer clock seems to want to run 45 or so minutes late:

http://www.glassonsailing.co.uk/weather.html

on the windows clock I have disabled both "auto adjust" and "auto syc to windows time server" , but the problem still persists.

any ideas where to look please?

very strange, I have reset it 3 or 4 times now, but it keeps slipping,   David
Logged
DanS
Chiang Mai weather
Forecaster
*****
Offline Offline

Posts: 4294



WWW
« Reply #1 on: November 07, 2011, 04:49:18 AM »

Have you checked the p.c.'s internal CMOS battery? If it's starting to get low then the clock may be effected as a result. Also, why not use the online clock sync and have it update frequently?
« Last Edit: November 07, 2011, 05:05:25 AM by DanS » Logged

Dan ThaiWx website
WS-2310/2810 WUHU WinXP 24/7
mackbig
Forecaster
*****
Offline Offline

Posts: 4072



WWW
« Reply #2 on: November 07, 2011, 07:18:02 AM »

My older wx pc did this also. It happened right after installing my Boltek, but pretty sure it was coincidental, and my cmos battery just decided to start dying about the same time.  I solved it with a tweat to the timing of the window pc time update, reg hack made it update faster than the lowest selectable frequency via the gui.

Andrew
Logged


Andrew - Davis VP2+ 6163, serial weatherlink, wireless anemometer, running Weather Display.  Boltek PCI Stormtracker, Astrogenic Nexstorm, Strikestar - UNI, CWOP CW8618, GrLevel3, (Station 2 OS WMR968, VWS 13.01p09), Windows 7-64
Davidb
Senior Member
**
Offline Offline

Posts: 88


WWW
« Reply #3 on: November 07, 2011, 11:39:08 AM »

-
Thanks for those replies.

It is a remote computer, so I shall change the battery when I am next on site. The surprising thing is that the time slips even when the comp stays powered up - I thought that the battery was just to see it through power cuts.

David
-
Logged
Bushman
Forecaster
*****
Offline Offline

Posts: 3491


WWW
« Reply #4 on: November 07, 2011, 12:02:02 PM »

Write down any custom CMOS settings before you change the battery as they will get reset.
Logged
WeatherHost
Forecaster
*****
Offline Offline

Posts: 1636



« Reply #5 on: November 07, 2011, 12:59:14 PM »

You want the PC clock to auto sync to a remote time server.  I'm sure there are a few in the UK.  It should check at least once a day.

Logged
mackbig
Forecaster
*****
Offline Offline

Posts: 4072



WWW
« Reply #6 on: November 07, 2011, 01:31:32 PM »

That's what I thought as well but I would lose quite a bit of time over the course of the day on a pc running 24/7.   Can remember what frequency I ended up with, something like 10 or 30 minutes.

Found my original thread.  there is a link to a third party app that syncs, and instructions on how to tweak the native windows settings to update more frequently.

http://www.wxforum.net/index.php?topic=2838.0

Andrew


It is a remote computer, so I shall change the battery when I am next on site. The surprising thing is that the time slips even when the comp stays powered up - I thought that the battery was just to see it through power cuts.
Logged


Andrew - Davis VP2+ 6163, serial weatherlink, wireless anemometer, running Weather Display.  Boltek PCI Stormtracker, Astrogenic Nexstorm, Strikestar - UNI, CWOP CW8618, GrLevel3, (Station 2 OS WMR968, VWS 13.01p09), Windows 7-64
DanS
Chiang Mai weather
Forecaster
*****
Offline Offline

Posts: 4294



WWW
« Reply #7 on: November 07, 2011, 06:31:10 PM »

If the battery swap doesn't do it you can also tweak the clock auto sync rate with your pc's registry settings in "regedit". Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32time\TimeProviders\NtpClient there is a SpecialPollInterval that can be set for sync rate.

I have mine set (wx PC) to update every 6 hours for the same reason you mention, clock drift,and it stays on time this way.
Logged

Dan ThaiWx website
WS-2310/2810 WUHU WinXP 24/7
WeatherHost
Forecaster
*****
Offline Offline

Posts: 1636



« Reply #8 on: November 07, 2011, 06:36:31 PM »

If a PC clock is drifting more than a few seconds in a week, there is some other problem.

Logged
W3DRM
Forecaster
*****
Online Online

Posts: 1345



WWW
« Reply #9 on: November 07, 2011, 08:54:29 PM »

While it is true that the PC clock should not be drifting as much as some of you are indicating, there are ways of ensuring that your PC time is accurate.

Ham radio operators using digital modes of communication run into the need to maintain their computers at very tight time constraints (within a second or so) so they and other users around the world are in sync on a 24/7 basis. We do not use the standard Microsoft provided time standards to do this. There are many different software packages available to keep you in sync. Personally, I use a package from Meinberg in Germany to keep all of my computers in time-sync. I've used for over a year now and have never had any problems with it. It just runs in the background and keeps my clock accurate, all the time. A link to their site follows:


Just make sure you explicitly follow their instructions and you shouldn't have any problems at all.
Logged

Don - W3DRM - Minden, Nevada --- Davis Wireless VP2, VWS 14.00 p101,
StartWatch, VirtualVP, VPLive, WL 5.9.3, Win7 Ultimate-SP1
--- Logitech QuickCam Fusion webcam
Davidb
Senior Member
**
Offline Offline

Posts: 88


WWW
« Reply #10 on: November 08, 2011, 03:08:37 PM »

-
I had a hunch and it seemed to be right - before connecting the weatherstation ( a Davies VP ) you need to install and run a programme called weatherlink. This is usually a one - off operation.

But then you stop it and run VWS ( virtual weather station - our normal programme )

so I went on weatherlink and changed the time setting and away we go.

I have also reinstated the windows time synchronizing option with daylight saving.

See how it goes, its been fine all day,

thanks for suggestions. cheers, David
Logged
Weather Display
Forecaster
*****
Offline Offline

Posts: 2249


WWW
« Reply #11 on: November 08, 2011, 03:30:49 PM »

do you mean that the time on the VP console was not set correct, and the software was setting the pc time to that
and now you have corrected the time on the console
or?
Logged

WeatherHost
Forecaster
*****
Offline Offline

Posts: 1636



« Reply #12 on: November 08, 2011, 04:21:22 PM »

If the time on the weather console is wrong, syncing the PC and the console will set the PC to the incorrect console time.  Or so I've always found.  I've never found a way to set the console time to the PC time.

Logged
Davidb
Senior Member
**
Offline Offline

Posts: 88


WWW
« Reply #13 on: November 08, 2011, 04:53:13 PM »

-
Yes, the console time was wrong, so I corrected it with Weatherlink

david
Logged
SLOweather
Administrator
Forecaster
*****
Offline Offline

Posts: 2342



WWW
« Reply #14 on: November 08, 2011, 05:23:40 PM »

FWIW, you can also set the time from the console from the keypad by putting it in setup mode. It's fast and easy. The instructions are in the console manual.
Logged
Weather Display
Forecaster
*****
Offline Offline

Posts: 2249


WWW
« Reply #15 on: November 08, 2011, 07:56:33 PM »

Quote
I've never found a way to set the console time to the PC time.
there is 3rd party software that can be set to do that, auto, daily
(the davis console time can drift a bit,especialy if your AC frequency is not always up to par, unless running on batteries only)
Logged

Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.112 seconds with 20 queries.
anything