Posted: Saturday Jan 2nd, 2016 09:44 am |
|
1st Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 69 |
Status: |
Offline
|
back to top
|
The date on my Comfort KP06 keypad is behaving very strangely! This morning - 02 Jan 2016 - at about 8:00am the date said 01 Jan 2016 (01-01-2016), although the time was correct. Using programming mode from the keypad, I set the date to 02-01-2016. Imagine my concern when a little later, I noticed it had reverted to 01-01-2016. The time was still correct, though. I set it to the correct date - again - from the keypad only to find later still it had again reset to 01-01-2016! Looking at the log files, I see the following:
01/01 08:04 Sign in - User # 2
01/02 08:06 Date/Time Change UCM 1 ; I set it correctly
01/02 08:12 Sign in - User # 2 ; still correct....
01/02 08:15 Sign in - User # 2
01/01 09:04 Date/Time Change UCM 1 ; reverts to 'yesterday'
Note that at 09:04, UCM1 reset to the wrong date! But it gets worse! The time now is 13:25 and the date has changed to read correctly. The corresponding log file entries are here:
01/02 11:44 Date/Time Change 2 ; change it manually again
01/01 12:04 Date/Time Change UCM 1 ; but it gets set back - again!
01/01 13:05 Sign in - User # 2
01/02 13:07 Date/Time Change UCM 1 ; next UCM change is correct!
So you can see I changed the date to 02-01-2016 at 11:44 but UCM1 changed it back at 12:04! Then, at 13:07, UCM1 appears to set it correctly - and it is now 'sticking'.
For reference, - Comfort is Ultra II v7.093.
- UCM1 is ETH03 v7.075
- UCM2 is CBus v7.054.
- The 'Clocks/Timekeeping' line on the CBus module is OFF.
- The keypad is KP06 v6.010.
- Time is synchronised with the Australian pool NTP server at au.pool.ntp.org
- I'm in Perth, Western Australia where we do not have DST and 8hrs offset from GMT is set correctly on SNTP setting.
- The synch interval is set to 60 mins.
So, to me, it looks as though the date is 12 (13?) hours 'wrong'. Every time I set it correctly before 13:00 or so, it reverted to 'yesterday' when UCM1 changed it. But, post 13:00, it has been set correctly - and is continuing to show 'today'.
Any comments gratefully received!
Many thanks - Mike
|
Posted: Saturday Jan 2nd, 2016 09:48 am |
|
2nd Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5498 |
Status: |
Offline
|
back to top
|
I am seeing the same thing.We will look into it as soon as possible
|
Posted: Saturday Jan 2nd, 2016 10:02 am |
|
3rd Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 69 |
Status: |
Offline
|
back to top
|
A bit more information. It appears it ISN'T correcting the date! here's the latest log entries:
01/02 13:07 Date/Time Change UCM 1
01/02 13:11 Sign in - User # 2
01/02 13:32 Sign in - User # 2
01/01 13:45 Date/Time Change UCM 1 ; so UCM changes it back
01/01 13:46 Sign in - User # 2
01/02 13:47 Date/Time Change UCM 1 ; used 'submit' button on SNTP dialog
01/01 13:52 Date/Time Change UCM 1 ; ...but UCM changed it back!
01/01 13:55 Sign in - User # 2 ; still wrong!
So could it be 1 day wrong?
NTP is correct!
|
Posted: Saturday Jan 2nd, 2016 10:03 am |
|
4th Post |
Posted: Saturday Jan 2nd, 2016 11:19 am |
|
5th Post |
Ingo
UCM Pi Users
Joined: | Sunday Jan 21st, 2007 |
Location: | South Africa |
Posts: | 562 |
Status: |
Offline
|
back to top
|
Same for KP04 and KT03 on Eth03/SNTP connected system. Bus Monitor confirms ETH03 sends back the incorrect date.
|
Posted: Sunday Jan 3rd, 2016 04:40 am |
|
6th Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 69 |
Status: |
Offline
|
back to top
|
Just to confirm (but I suppose it is already obvious!) that the date this morning is showing 02-10-2016. One day late as expected.
|
Posted: Monday Jan 4th, 2016 08:26 am |
|
7th Post |
Posted: Monday Jan 4th, 2016 10:30 am |
|
8th Post |
mikeinnc
Member
Joined: | Wednesday Mar 18th, 2015 |
Location: | Perth, Australia |
Posts: | 69 |
Status: |
Offline
|
back to top
|
Thanks very much indeed! That did the trick (although I had to do a manual TFTP transfer of the hex file to ETH03). Date is now correct, and all's well again! Great service.
|
Posted: Monday Jan 4th, 2016 04:29 pm |
|
9th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5498 |
Status: |
Offline
|
back to top
|
All the best to or friends in Perth
|
|