[ntp:questions] Installing more stable oscillator?
jlevine at boulder.nist.gov
Mon Jul 16 13:45:28 UTC 2007
On Jul 13, 7:43 pm, Pete Stephenson <pete+use... at heypete.com> wrote:
> Surely many of the stratum 1 servers (say, time.nist.gov) that get and
> distribute time directly from atomic clocks aren't just off-the-shelf
> servers with cheap, unstabilized system clocks, right? I know that many
> of the public stratum 1 servers deployed by individuals and
> organizations get their time from GPS, and are probably ordinary
> computers, but I have this (again, perhaps incorrect) assumption that
> the servers that supply the time /to/ the GPS system are not ordinary
time.nist.gov (and all of the other NIST time servers) use
servers. The older systems are built using Tru64 Unix and the newer
ones are built using FreeBSD. The systems are synchronized using a
telephone connection to the NIST ACTS time service.
I have modified both the kernel and the serial port driver to reduce
jitter and latency, but the systems are basically off-the-shelf in
Some of the systems have external rubidium atomic frequency standards.
These devices improve the short-term stability and the reliability
performance") of the system, but do not improve the accuracy very
since the external clock must be set on time using some external
The servers are synchronized using a separate process that is
of NTP. It is an adaptive frequency-lock loop that adjusts itself for
of each individual server The details are a bit complicated and have
published in the literature.
Once it has been characterized, a cheap computer clock can probably
timing accuracy of about 50 milliseconds for 1 day with no external
Cheap no-name hardware is typically worse, but your mileage may vary.
external quartz crystal oscillator might improve this to about 10
per day (characterized but free-running), but it is hard to do better
without more expensive hardware and/or semi-heroic measures.
Time and Frequency Division
More information about the questions