Re: getting time from WWV

From: Floyd L. Davidson (floyd_at_barrow.com)
Date: 06/27/05


Date: Mon, 27 Jun 2005 05:11:48 -0800

phil-news-nospam@ipal.net wrote:
>I have a potential project to build a small cluster of computers to do
>a certain complex task which requires accurate timekeeping. But these
>computers are also not going to be connected to the internet, so using
>some NTP servers on the internet to get time isn't an option. What are

A discussion of various time sync methods for a local ntp server:

  http://www.wraith.sf.ca.us/ntp/

>good choices of _hardware_ to obtain to get accurate timekeeping based
>on receiving WWV transmissions at 60 kHz, and have stable oscillators
>to hold that time within 0.1 ppm when WWV can't be received ... AND can

You won't find anything that will sync to wwvb to get even near
that accuracy. Likewise you won't be able to sync anything in a
PC to better than about 1 ppm (primarily due to bus jitter).

http://www.isoc.org/isoc/conferences/inet/01/CD_proceedings/T42/inet2001.html

I don't know if it is showing up in any commercial products yet,
but NIST has developed an inexpensive atomic clock. Within a
short time we should see $200 atomic clocks on a PCI card, and
soon enough the price will be below $100. (Actually, in not too
long there will probably be an atomic clock in every cell phone.)

  http://tf.nist.gov/ofm/smallclock/index.htm

>work with Linux (presumably anything with an ethernet and NTP support
>should be just fine, but something with another means might need its own
>driver).

In the mean time, either a rubidium based Stratum 1 clock or a
GPS synchronized Stratum 2 clock (both of which are expensive)
in a standalone NTP server is just about the only way you will
get 0.1 ppm or better.

Also, be aware that NTP sources and documentation have a very
different definition of what a "Stratum" level means than those
used by industry. Hence you'll see references that are
conflicting, and others that are ambiguous.

Stratum 1 means 20 year minimum accuracy of +/- 1 x 10e11. A
Stratum 2 clock has a 20 year minimum accuracy of +/- 1.6 x 10e8
*and* a minimum (free running) stability of +/- 1 x 10e10 per
day and be capable of synchronizing to an accuracy of
+/- 1.6 x 10e8.

Essentially a Stratum 1 clock is meant to be a standalone free
running clock, while a Stratum 2 is intended to be synchronized
but have a very long (more than 1 month) holdover accuracy if
synchronization is lost. (There are lower Stratum levels too,
but they are not intended to provide holdover accuracy for more
than hours, or even be synchronized to better than 5 ppm.)

The NTP view of Stratum levels is merely an indication of how
many synchronization levels exist between any given clock and
a genuine atomic clock. Hence a Stratum 2 clock may or may
not be accurate, and may or may not remain stable when not
synchronized.

-- 
Floyd L. Davidson           <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)                         floyd@barrow.com


Relevant Pages

  • Re: Problem with Linux Machines Request for Time from an XP Machine
    ... clocks synchronized by GPS to Stratum ... A Stratum 1 clock is defined by ANSI ... synchronization for accuracy, ...
    (comp.os.linux.networking)
  • Re: question about the stratum
    ... ntp.conf for MyMachine: ... fudge 127.127.1.0 stratum 12 ... anything else but MyMachine's local clock, ... myMAchine is connected on the network to an NTP server. ...
    (comp.protocols.time.ntp)
  • Re: NTP sync problems
    ... D, which lead to not syncing, leading to offset drifting on NTP Client ... external NTP server C (stratum 1) having its own system clock as ...
    (comp.protocols.time.ntp)
  • Re: Roberts destroys SR
    ... >> about clock synchronization because it is simply physically ... and is therefore not a scientific theory. ... it is a mere definition of clock synchronization; ... When the two observers briefly meet, ...
    (sci.physics.relativity)
  • Re: Whereis NTP (client) config file in Red Hat Enterprise Linux 3.
    ... > If you right click on the clock applet on the GNOME panel, ... But reading about NTP, it suggests using three to five NTP servers, ... # Permit time synchronization with our time source, ... # permit the source to query or modify the service on this system. ...
    (linux.redhat.misc)