On Jan 20, 11:49*am, (Geoffrey S. Mendelson) wrote:
John Kasupski wrote:
Yes, assuming it can get a signal...which problem exists with the
WWVB-based devices as well (and which was the whole point of the
article cited by the OP).

That is a problem of any radio based device, whether it uses GPS,
60kHz (or the European equivalent) signals, cell phone, etc.

I understand that analog TV signals in the U.S. also had time
coding in them to eliminate the flashing "12:00" problem.
Of course that's about to go away, and I have no idea if U.S.
HDTV signals include time coding or not.

When someone asked on another list about this several months ago,
so that he could get an heirloom digital clock to receive the 60kHz
signals in a place that was too well shielded and electricaly noisy,
I looked into generating the time signals with a PC. :-)

Programing wise it was simple, one could take the system clock
and build the data stream. If it was kept in sync with NTP,

- it would be close enough for those clocks that only display
- to minute or second resolution.

Yes there is the practical consideration that most common
Consumer Products that have a Time Display "Only" display
the Time-to-the-Minute {No Seconds} and therefore Time that
is "Accurate to the Nearest Minute" meets the Needs of these
Non-Techincal Consumers of Time.