[Elecraft] Clock loses time

[Phil Kane]

On 12/30/2012 6:13 AM, Richard Fjeld wrote:

> Mine is about 2 secs per month.  Having come from the 'wind-up' era, this is great.

I can live with 2 sec/month as long as it is easily correctable.

The old "railroad" standard dating from the 19th and 20th centuries was
one second per day (30 seconds per month) for "approved" mechanical
watches.  This was changed years ago to require a timepiece  that "keeps
accurate time" as operating crew members preferred "quartz"
wrist-watches rather than "approved" (i.e. expensive) pocket watches.  I
had a Hamilton "railroad" pocket-watch from the last production run that
had terrible quality control and it kept worse time than my Seiko
wrist-watch.  The only people who lost out on that deal were the
watchmaker/jewelers who were on the "Watch Inspector" list to certify
the "approved" watches on a regular basis.

Now we're in the 21st century.  What I would love for my office/hamshack
is a stand-alone box with large (4" or so) digital readout to the second
that would be pluggable to my router and auto-update every xxxx hours
from the Naval Observatory or NIST time server.  I tried both the
WWVB-based "atomic" clocks sold by MFJ and RadShack but the WWVB signal
here is not adequate to keep those clocks in sync and their "native"
accuracy was abysmal.

I can dream as I rebuild my office and unpack my K2 from storage......   <G>

73 de K2ASP - Phil Kane
Elecraft K2/100   s/n 5402