Hi,
I have my automation system setting the time every night on my Panel with a "Set Time/Date" command. Problem is: the panel time remains out of sync by up to a minute with the time that I am trying to set. For instance, at a local time of "04:03:10", the Panel reports a system time of "04:04".
I have the automatic time/date setting disabled from Eyezon web interface.
Here is the interaction: the date/time in the left hand column are my server time, to which I am trying to synchronize my panel to:
* The first log entry shows a 550 Time Broadcast from the panel. At 03:55:10, the panel system time is set to 03:56 (at least 50 seconds fast).
2016/12/28 03:55:10
receiving '55003561228169C' ('Time/Date Broadcast' TPI command)
panel system time = '2016-12-28 03:56'
* The second log entry shows the '010' "Set Date/Time" command being issued at 04:00:00.
2016/12/28 04:00:00
sending '010040012281689' ('Set Time/Date TPI command')
* The next time broadcast happens at 04:03:10. The panel system time is now set to 04:04, meaning that the panel remains at least 50 seconds ahead of the correct time.
2016/12/28 04:03:10
receiving '550040412281696' ('Time/Date Broadcast' TPI command)
panel system time = '2016-12-28 04:04'
My suspicion is that the panel sets the hours and minutes correctly, but does not bother resetting the seconds to zero.
Any idea?
Thanks,
Michael
2DS "Set Time/Date" TPI command not setting seconds?
Moderators: EyezOnRich, GrandWizard
Re: 2DS "Set Time/Date" TPI command not setting seconds?
Yeah that is a DSC thing. When setting the time it seems to be only granulary to the minute. Our auto-time-update feature on DSC has the same problem in that it will only keep the panel time accurate to the minute.
That is why we don't use panel time for anything. We offer the auto-time-update service so people's wall-clocks (keypads) are kept in sync. Events use the standard UNIX epoch.
That is why we don't use panel time for anything. We offer the auto-time-update service so people's wall-clocks (keypads) are kept in sync. Events use the standard UNIX epoch.