Home |
Search |
Today's Posts |
#10
![]() |
|||
|
|||
![]() "qquito" ) writes: Then, on SAT, July 23, 2005, my clock displayed "TUE, January 4" (January 4 in 2005 is indeed Tuesday). On Sunday, starting my midnight, it displayed "WED, January 5". But, after 2:00 PM on Sunday, the hour when the NIST signal is supposed to be transmitted, my clock was displaying the right information again. --Roland Have you changed the battery? I can see the clock acting up because the battery is low, and then not getting proper reception to resync properly. You do realize that they are not continuously receiving the WWVB signal. To save power, and because the internal crystal oscillator is good enough for a day or so without an update from the time station, they only gather the information once a day, usually in the very early hours of the day when propagation may be best, and when man made interference (like all those light dimmers and tv sets) will be at a minimum. Since the times you note aren't in the early hours of the morning, even if WWVB was sending out the wrong signal at odd times, the clocks would not notice unless the problem is there when they are scheduled to sync up. Also keep in mind that if WWVB was really sending out the wrong information, it would be noticed by others, and that's not happening. So change your batteries, and then get back to us. Michael |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
"Atomic clock" for cheap! | Shortwave | |||
NIST develops portable small atomic clock, could be good for freqstandard | Equipment | |||
NIST develops portable small atomic clock, could be good for freqstandard | Equipment | |||
NIST develops portable small atomic clock, could be good for freqstandard | Equipment |