Posted: Saturday Sep 5th, 2015 12:28 pm |
|
1st Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 71 |
Status: |
Offline
|
back to top
|
When I read my Comfort Event Log, I see that it records a Date / Time change just about every hour of every day! Of course, this fills the Event Log with a lot of entries that are really not at all interesting....... So, my question is - is there any way I can stop a 'Date / Time Change' being logged. It will make reading the log far easier!
Many thanks, as usual.
|
Posted: Saturday Sep 5th, 2015 01:45 pm |
|
2nd Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
Are you using the UCM/ETH03 which is able to synchronise the time wth an Internet Time Server? This could be what is correcting the Comfort time when it becomes a little out
The SNTP (Simple Network Time Protocol) button below

The SNTP setting page is below
The NTP synchronise interval is the time between syncs.It is shown as 30 minutes above. If there is a time difference at the time of sync then the time is updated and iit may be recorded to the event log
Upgrade to the latest Comfort firmware to reduce the number of events logged
In the current firmware, if the time difference is less than 4 seconds, the time is updated but it is not recorded in the event log. 30 or 60 minutes as the update interval should work, as the comfort time will not be so inaccurate as to be out by 4 seconds during this time interval
|
Posted: Saturday Sep 5th, 2015 03:10 pm |
|
3rd Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 71 |
Status: |
Offline
|
back to top
|
Thanks very much for that! I've just upgraded to the latest firmware, and, yes, I do use a UCM/ETH03 synchronised to an Australian NTP pool server. I believe this will be a significant improvement - the event log really didn't need all those date/time change events! 
|
Posted: Sunday Sep 6th, 2015 03:12 pm |
|
4th Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 71 |
Status: |
Offline
|
back to top
|
Well, now that the new firmware has been in place for > 24 hrs, I thought I'd check in the event log.....and it hasn't made a scrap of difference! Here's a sample of the log AFTER the new firmware has been installed.
09/05 18:57 Date/Time Change 18
09/05 20:07 Date/Time Change 18
09/05 21:18 Date/Time Change 18
09/05 22:28 Date/Time Change 18
09/05 23:39 Date/Time Change 18
09/06 00:49 Date/Time Change 18
09/06 01:59 Date/Time Change 18
09/06 03:10 Date/Time Change 18
09/06 04:20 Date/Time Change 18
09/06 05:31 Date/Time Change 18
09/06 06:41 Date/Time Change 18
09/06 07:51 Date/Time Change 18
09/06 09:02 Date/Time Change 18
09/06 10:12 Date/Time Change 18
09/06 11:23 Date/Time Change 18
Nearly every hour there is an entry - just as before. So either my Comfort clock is very poor at keeping time - or the firmware update hasn't worked! Is there any manual way to stop these entries - other than turning off the NTP Synch?
Attachment: ComfortNTP.jpg (Downloaded 40 times)
|
Posted: Sunday Sep 6th, 2015 05:54 pm |
|
5th Post |
juwi_uk
Member

back to top
|
I must admit I unchecked the box after a while too on mine as otherwise 90% of my log file were these.
Last edited on Sunday Sep 6th, 2015 05:58 pm by juwi_uk
|
Posted: Sunday Sep 6th, 2015 05:54 pm |
|
6th Post |
Posted: Sunday Sep 6th, 2015 06:10 pm |
|
7th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
Your Comfort clock is probably inaccurate so that if you wait 1 hour the error is too much
Can you change the setting to 10 minutes and see what is the result?
|
Posted: Sunday Sep 6th, 2015 06:16 pm |
|
8th Post |
Posted: Sunday Sep 6th, 2015 07:53 pm |
|
9th Post |
juwi_uk
Member

back to top
|
Yep you can set your watch by an entry going in the log.
I knew there was a reason I turned it off again.
You cant tell me this isnt a bug. Something is wrong here big time.
It is a daylight savings issue?
I think I'll turn it off again
Julian
Attachment: 2015-09-06_15-50-16.png (Downloaded 34 times)
|
Posted: Monday Sep 7th, 2015 02:57 am |
|
10th Post |
Ingo
UCM Pi Users

Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 598 |
Status: |
Offline
|
back to top
|
I tend to agree with Julian, something is wrong. If NTP adjusted the time then it stands to good reason that the time can run in the corrected state for at least the 10 minutes before the next NTP check. If however there is really something wrong with the RTC then I agree that NTP will keep correcting the time. If however Julian has disabled NTP, and he can verify that the time is correct to within the 4s, or 10s I can't remember, of NTP time then we know there is a bug somewhere. Too many people complain about the same thing to be a coincidence.
Julian, do a check for us. Set the time to NTP time and check it exactly 24H later to see how far the time drifted. My guess is that it shouldn't drift at all because Comforts RTC is very accurate on its own. I will do the same this side.
Ingo
|
Posted: Monday Sep 7th, 2015 05:02 am |
|
11th Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 71 |
Status: |
Offline
|
back to top
|
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!!
|
Posted: Monday Sep 7th, 2015 09:35 am |
|
12th Post |
juwi_uk
Member

back to top
|
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
|
Posted: Monday Sep 7th, 2015 09:52 am |
|
13th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
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
|
Posted: Monday Sep 7th, 2015 10:29 am |
|
14th Post |
juwi_uk
Member

back to top
|
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.
|
Posted: Monday Sep 7th, 2015 12:05 pm |
|
15th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
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
|
Posted: Monday Sep 7th, 2015 07:27 pm |
|
16th Post |
tman
Comfort Installers
Joined: | Wednesday Sep 22nd, 2010 |
Location: | United Kingdom |
Posts: | 22 |
Status: |
Offline
|
back to top
|
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.
Last edited on Monday Sep 7th, 2015 07:28 pm by tman
|
Posted: Monday Sep 7th, 2015 08:27 pm |
|
17th Post |
Ingo
UCM Pi Users

Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 598 |
Status: |
Offline
|
back to top
|
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.
|
Posted: Tuesday Sep 8th, 2015 05:49 am |
|
18th Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 71 |
Status: |
Offline
|
back to top
|
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.
|
Posted: Tuesday Sep 8th, 2015 09:43 am |
|
19th Post |
Posted: Tuesday Sep 8th, 2015 09:54 am |
|
20th Post |
slychiu
Administrator

Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5766 |
Status: |
Offline
|
back to top
|
That is without the ETH03 update time? Are you sure? Our RTC should not even be this accurate?
|
Current time is 05:05 pm | Page: 1 2 3 |
|