NeoClock
page 11
8. FOR SOFTWARE DEVELOPERS
To ensure the safety of the data string:
•
Do not take into account the time sequence as long as the initialisation bit
(byte JS, bit 5) is not set, i.e. the autonomous NeoClock quartz clock has
not been synchronised since its last starting.
•
Do not take into account the time sequence if the checksum is wrong. In
this case, wait for the next data string.
•
Before validation of the data, compare the last received data string with the
previous one. If the difference is too big, do not take the time sequence
into account.
•
If possible, compare the time data you received with those from your
system clock. If they are too different from each other, do not take the time
sequence into account.
To get the best possible accuracy:
•
Do not acknowledge the time sequence unless the atomic bit is set.
•
Do not validate the time sequence if the value of the bad reception minute
counter is too high. This counter can go up to 65535, meaning 45 days
uninterrupted bad reception.