Daylight Savings Issues

I always look forward to DST events. The Elk "sprung" ahead two hours today - why am I not surprised!
 
M1G: 5.2.10
M1XEP: 1.3.28
 
Now that I have CQC pushing time to the Elk via the Ascii protocol, I have finally had my first DST with no issues.  
 
So its that time of year again.
 
Last month I updated the firmware to 5.2.10 on the Elk and 1.3.28 on the XEP. 
The XEP is not configured for a time server, but that "shouldn't" matter.
 
So far, so good.  At least it didn't change a week early.
 
If you'd like to monitor when the ELK changes, you can use the attached perl script.  It monitors the XK packets, which occur every 30 seconds, and writes them to a log file (clockwatch.log).  About 220K of text per day of logging.
 


2013/10/27_16:07:55  16XK0808161271013110006E; 20131027 160808 dst=1 dif=13

2013/10/27_16:08:25  16XK3808161271013110006B; 20131027 160838 dst=1 dif=13

 
The underscore between the date and time indicates the PC is in daylight time.  It will be blank when the PC switches to standard time.  Messages should also be written to the log when the PC and Elk switch between daylight and standard. 
 
dif= is the difference in seconds between the PC and the Elk. 
 
Rename to clockwatch.zip
View attachment clockwatch.pdf
 
I've been using Strawberry perl.  You shouldn't have to install any additional perl modules.
 
 
Well, no DST love here...
 
I have 5.2.10 firmware on the M1 and 1.3.28 on the XEP with the XEP configured (and tested successfully) for time server updates at 3:30 AM but the Elk did not update.  I tried a couple of things, and then just downloaded Dan's MyElkTime to update the clock...
 
None love here either. I've got 5.2.4 on the M1 and 1.3.28 on the XEP. I thought this worked fine in the spring, but I may be wrong. My time server updates are set for 2:18AM, and manually selecting the 'Test' button was 'successful', but there was no change on the keypad(s). I also verified that the Global setting (G05) was set to observe DST as well. Thoughts (other than manually updating)? I'd prefer to 'fix' the problem rather than having to manually update.
 
My system seemed to update correctly.   I got my usual Sunday call at 9am standard time.  I can't see the keypads from here, so they may be off.
 
But the ELK did some weird stuff.
 
On Sunday, the monitoring showed that the Elk changed its time correctly at 2AM (3rd line, elk time jumps back 1 hour), but the DST flag is still active


2013/11/03_01:58:16  16XK15590110311131100075; 20131103 015915 dst=1 dif=59

2013/11/03_01:58:46  16XK45590110311131100072; 20131103 015945 dst=1 dif=59

2013/11/03_01:59:16  16XK15000110311131100083; 20131103 010015 dst=1 dif=-3541

2013/11/03_01:59:46  16XK45000110311131100080; 20131103 010045 dst=1 dif=-3541

2013/11/03 01:00:16  16XK15010110311131100082; 20131103 010115 dst=1 dif=-3541

2013/11/03 01:00:16  pc has switched to standard time

2013/11/03 01:00:46  16XK4501011031113110007F; 20131103 010145 dst=1 dif=-3541

 

 
and then this morning (Monday) at midnight:, the Elk's DST flag flipped.


2013/11/04 00:00:52  16XK52592310311131100070; 20131103 235952 dst=1 dif=-60

2013/11/04 00:01:22  16XK22000020411130100085; 20131104 000022 dst=0 dif=-60

2013/11/04 00:01:22  elk has switched to standard time

2013/11/04 00:01:52  16XK52000020411130100082; 20131104 000052 dst=0 dif=-60

2013/11/04 00:02:22  16XK22010020411130100084; 20131104 000122 dst=0 dif=-60
 
 
I just realized the time on my M1 Gold is correct but the day is 1 day ahead! It says 9/13/16.
 
I have double checked the location and it's correct. The NTP settings say it succesfully picks up the time.
 
Running the latest 5.3.10 firmware.
 
I just saw that my keypad says 12/31/2016 at 12:30pm, it's 12:/30/2016 at 12:30pm.
 
I'm using
M1G HDWare 0.13
Boot version 3.3.6
Firmware 5.3.10
Current on M1XEP firmware (Will track down version)
 
Back
Top