Hi Brian: The WWVB clocks typically want to see 2 or 3 minutes go by where the data packets have date and time incrementing by 1 minute. If you see that then you have valid data. Hard for interference to mess it up.
But a low battery will cause problems, i.e. the clock may miss steps and get behind, not sync, etc. I wonder which way Bill's friend's clock was off? Have Fun, Brooke Clarke http://www.prc68.com Brian Kirby wrote: > I figure there is no CRC check for the WWV clocks. > > I had on lose it for about 3 days in the middle of summer, and then it > picked it back up and has been OK since. > > Maybe local RFI when the clock went to check the signal.... > > Brian KD4FM > > > > Bill Hawkins wrote: >> My apologies, but I didn't think you'd want to hear about jumps. >> >> My good friend, and software genius, was late for a lunch appointment >> today. The "atomic" alarm clock that he has used for years was 3.3 >> hours behind this morning, but not on any other morning. My WWVB clock >> was dead on at 4 PM (in MN, where we both are located). >> >> Anybody got a story about an "atomic" clock messing up like that? >> >> Bill Hawkins >> >> "It's five o'clock somewhere ..." Jimmy Buffet >> >> >> _______________________________________________ >> time-nuts mailing list -- [email protected] >> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
