Bill, If it's an older clock it's probably tripping over a timecode transmission format/modulation change. I forget the exact details but changes were required to my old 8085-based Spectracom receiver.

There are a number of WWVB simulator projects out there that will transmit a weak but usable signal to your clock after getting sync’d from ntp or GPS NMEA time messages. They were developed to help people develop receivers :-) One in particular uses an AVR and it should be pretty simple to make it do the “old protocol”. You’d then hide this behind your clock and it will sync to it instead of the actual WWVB signal. Solves the protocol problem and the weak signal problem from real WWVB with one little circuit. If Google does not provide, I can dig up some links tomorrow.

I also have a decades old SkyScan WWVB LCD wall clock which has survived a few sets of leaking AA batteries :). It still keeps accurate, occasionally it doesn’t sync, though I think that can be chalked up to signal propagation. It’s possible the problem is interference EMF, RF etc. Try moving it to another place in the room and/or another room. Don Resor There may be some inter Sent from someone's iPhone > On Jan 14, 2024, at 11:49 AM, Bill Gunshannon via cctalk <cctalk(a)classiccmp.org> wrote: > >  > This is kind computer related but maybe more ham radio related > but I figure if anywhere, here is the place to find an answer. > > I have a SkyScan ATOMIC CLOCK. > It is supposed to get its time from WWVB. > The antenna icon that is supposed to mean it is receiving > WWVB is on. > > Your probably wondering why I keep saying "supposed to". > The clock is always wrong. Slow by about 2 minutes. > > Is there a known problem with WWVB? > > bill >

IIRC there's something on-frequency in England that often swamps WWVB on the northeastern part of North America, too! Thanks, Jonathan