On Wed, 12 Nov 2008 21:27:10 -0600, "Bill Hawkins" <[EMAIL PROTECTED]> 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
Yes, mine have shown similar errors from time to time. Usually a new
battery fixes the problem. I have had it happen on AC powered clocks. The
usually
go back to proper time after I press the WAVE button. I figure they must
get some interference from something that causes them to go off
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
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 yo
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 M
