Elk M1 clock issues.

[electron]

After upgrading I noticed that my XEP now supports the NTP feature. So I set it up last night, using a local NTP resource, and around 3am, my 'dusk' sequence kicked in (great for the WAF!). So I checked the clock this morning, and sure enough, it's way behind. Right now it thinks it is Monday Aug 4, 6:35AM. If I set the clock manually, everything is fine, but whenever I try the NTP test button again, it is all wrong again.

S2 source I am using: ntp0.cornell.edu

NTP setup screen shows my local timezone is -5

What am I doing wrong? Or is this a known bug? Thanks!

 

[BrettS]

After upgrading I noticed that my XEP now supports the NTP feature. So I set it up last night, using a local NTP resource, and around 3am, my 'dusk' sequence kicked in (great for the WAF!). So I checked the clock this morning, and sure enough, it's way behind. Right now it thinks it is Monday Aug 4, 6:35AM. If I set the clock manually, everything is fine, but whenever I try the NTP test button again, it is all wrong again.

S2 source I am using: ntp0.cornell.edu

NTP setup screen shows my local timezone is -5

What am I doing wrong? Or is this a known bug? Thanks!

Given that the minutes are correct (assuming you posted this about a minute after you checked the elk clock) then I'd assume it's a time zone conversion issue. Eastern time should be GMT -5, however, it looks like you're about 8 hours slow, so I'd try +3 and see if that helps. No idea why that would work if it does, but I suspect it will.

HTH,
Brett

 

[electron]

Well for now, I am better off disabling the NTP feature all together, but I am wondering why this is happening.

 

[Steve]

I vaguely remember having trouble with some time servers when I first set it up. I am on 1.2.12 with ntp.myfloridacity.us as my time server and also in -5 zone and it works fine. You may want to just try another time server.

 

[electron]

I tried the FL one, and it worked, so tried the cornell.edu one again, and that one works too now. Crazy. Thanks Steve!

 

[gcimmino]

I seem to remember getting some "funny" results when first setting up the time servers on the XEP too. I chalked it up to "less than robust" error handling and display.

It's been working fine ever since and I too am in the ET zone.

 

[Spanky]

This may be a setup sequence problem.


Setup your time zone in the Sunrise/Sunset under the Automation tab. Send the information to the M1.

In the M1XEP setup page, check to make sure the time zone is set and send the information to the M1XEP.

It should work as prescribed.



There is an issue on the M1XEP setup in the test button on the time server and DNS that could say that the connection worked, but it did not. This is fixed in the next M1XEP release.

 

[LaurentR]

I remember having that exact problem. My time zone was set in the sunset/sunrise screen, then I installed the XEP NTP feature. It totally ignored the existing timezone setting. I had to change the timezone and back in the sunset/sunrise window for the NTP timezone to change. Then everything was fine. Not a single issue since. But I think this sequencing issue should be fixed.

Laurent