Posts: 619
Threads: 62
Joined: Jan 2007
Reputation:
1
Correct yes. Eth03 Updates disabled. NTP checked and sync\'d on my PC before every test.
I have changed my RTC setting from 0 to 1 to see what the accuracy will be for the next 24H test. Even with 1s out over 30H it still doesn\'t explain the DT changes every 10 minutes for some users. I will enable mine again in 24H to see what happens.
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
Mine is actually showing it is 23 seconds behind this morning if i do a DT command while watching the SNTP field readout.
How can the RTC be that far our after 24 hours when as somebody else mentioned cheap $1 watches dont do that.
What do I need to adjust?
Julian
Posts: 619
Threads: 62
Joined: Jan 2007
Reputation:
1
Julian, also take note that every Comfort reset will set the clock back a few seconds. On my test system it\'s 3s. This is probably because the HW doesn\'t use a dedicated RTC chip but rather the CPU for the clock - I\'m just guessing by looking at the design.
That said, the CPU is additionally clocked by a 32,768khz crystal for RTC applications so while running normally it \'should\' be very accurate depending on the code.
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
Enter +23 into the Time Adjust fieldThis speeds up the clock by 23 seconds per day
Keep the SNTP update disabled and see the results after a day
tuning fork crystals are delicate They may drift due to force or knocks, as it is not locked away like in a watch
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
I still don\'t understand where this is getting me. Even if it is out 30 secs a day it is not out more than a second in 10 minutes so why does it try to change every 10 minutes.
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
we do not understand this
That is why we need more information
It does not happen in our systems that we see
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
Checking 12 hours after my last post and it\'s 8secs behind.
I have set the adjust to 23 (12 hours ago) and sync\'d the clock when I uploaded to Comfort so assume that applies in one go at some stage (at midnight?).
How accurate should a normal clock be; do I need to get the hardware repaired?
Julian
Posts: 5,952
Threads: 871
Joined: Apr 2006
Reputation:
2
Try entering 39 instead of 23 assuming it is 39 seconds slowIt seems to be too much if it is out by 39 seconds a dayWith the UCM/ETH03 time adjustment and the daily time offset feature, it should not be a big problem, but we will be happy to change the crystal if you return the Comfort. But I do not think it is worthwhile
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
09-09-2015, 10:14 AM
(This post was last modified: 09-09-2015, 10:15 AM by juwi_uk.)
Yesterday it was 23 seconds behind.
This morning it is 18 seconds ahead (but obviously the 23 sec adjustment was applied)
Dont know what to make of this.
Going to zero the adjustment again.
Posts: 1,255
Threads: 219
Joined: May 2007
Reputation:
0
09-09-2015, 10:19 AM
(This post was last modified: 09-09-2015, 10:20 AM by juwi_uk.)
Perhaps you can relax the NTP Synchronize interval from it\'s max of 60 minutes so we can set to 1 day?
...or as this post started don\'t write these to the event log in the first place.
