Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Date / Time change in Event Log
#11
Well, I\'ve just set my interval to 15 minutes and I\'ll monitor what happens. It shouldn\'t be a daylight saving issue - we don\'t have summer time / winter time in Western Australia. The voters won\'t accept it! (We\'ve had 3 votes in some 20 years and they have all failed so in summer we are 3 hrs behind Eastern States and in winter, 2 hrs.)

But I\'m tending to agree there is a bug somewhere. Cheap and cheerful $2.00 watches can keep accurate time, so I\'m certain the Comfort RTC can!!
Reply
#12
I\'ve just done some tests by having the SNTP window open and doing a \"DT\" command to Comfort. I also tried \"Dt\" as well.

Both are returning the time to the same second as the SNTP realtime update field.

From what I can see they are both totally in sync yet Comfort doesnt think so itself.

Ju
Reply
#13
Can you disable the tome update after synchornising the time
After 24 hours check  how many seconds is Comfort time out compared to the corect time
Reply
#14
Why is that going to make any difference when it thinks it is out after only 10 minutes?
I ran side by side for an hour and time same to the second.
Reply
#15
We want to see if the time is realy out
There is also a adjust time parameter in Configuration > Modules and Srttings to compensate for time innacuacry on a daily basis
Reply
#16
I\'m getting the Date/Time Change message every hour as well on the installs we have here. They\'re all running the latest Comfort and ETH03 firmware.
Reply
#17
I also did a test for 18 hours and Comfort didn\'t gain/lose one second. The RTC has proven itself to be be accurate over this time but I will let it run for another 24H just to see if it really gains/loses anything.
Reply
#18
Some 24 hours now since I set the update time interval to 15 minutes, and the event log is still showing a Date/Time change event virtually every hour. Yes, it skipped the occasional hour but still irritatingly - and it would appear unnecessarily - frequent. This is certainly looking like a bug. I note the comment about the adjust time parameter, but I\'d be really reluctant to adjust this without a detailed analysis of the RTC accuracy. And, as Ingo has confirmed, I\'m very confident that the RTC IS accurate.
Reply
#19
30H, lost 1s only.
Reply
#20
That is without the ETH03 update time? Are you sure? Our RTC should not even be this accurate?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)