Jeffrey,
Your questions are answered by notes in the source code.
The clock syncs once per day by design. That time is set at 00:00 UTC in
the software developers time zone in Eastern Canada. It works out to 8
PM in California. You can recompile the code to change the sync time.
The interrupt count shows how many attempts were made (at 134 seconds
each) to obtain sync. Your clock is not receiving a clear signal if the
value is greater than "1".
NDST refers to the NEXT DST event which is moving clocks back an hour on
November 7th at 2:00 AM
Regards,
Peter
On 3/14/2021 7:52 AM, Jeffrey Pawlan wrote:
I have been using the new BPSK receiver for NIST. There are two
strange things that perhaps others can explain.
It only syncs one and only one time per day, usually around 8pm. It
also shows an interrupt count anywhere between 2 and 50 every day. I
am sure it can receive the signal more frequently than once in a day.
Is that caused by the design of the arduino software?
I also saw last night they sent a message "DST starts at 11/07 0200".
This morning it says "DST in effect" and "NDST at 11/07". Why are they
showing that date?
Regards,
Jeffrey Pawlan WA6KBL
_______________________________________________
time-nuts mailing list -- [email protected] -- To unsubscribe
send an email to [email protected]
To unsubscribe, go to and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected] -- To unsubscribe send an
email to [email protected]
To unsubscribe, go to and follow the instructions there.
