1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 3<html> 4 5 <head> 6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> 7 <meta name="GENERATOR" content="Mozilla/4.01 [en] (Win95; I) [Netscape]"> 8 <title>NIST Modem Time Service</title> 9 <link href="../scripts/style.css" type="text/css" rel="stylesheet"> 10 </head> 11 12 <body> 13 <h3>NIST Modem Time Service</h3> 14 <hr> 15 <h4>Synopsis</h4> 16 <p>Address: 127.127.18.<i>u</i><br> 17 Reference ID: <tt>NIST</tt><br> 18 Driver ID: <tt>ACTS_NIST</tt><br> 19 Serial Port: <tt>/dev/acts<i>u</i></tt>; 1200 baud, 8-bits, no parity<br> 20 Features: <tt>tty_clk</tt><br> 21 Requires: <tt>/usr/include/sys/termios.h</tt> header file with modem control</p> 22 <h4>Description</h4> 23 <p>This driver supports the NIST Automated Computer Time Service (ACTS). It periodically dials a prespecified telephone number, receives the NIST timecode data and calculates the local clock correction. It designed primarily for use when neither a radio clock nor connectivity to Internet time servers is available. For the best accuracy, the individual telephone line/modem delay needs to be calibrated using outside sources.</p> 24 <p>The ACTS is located at NIST Boulder, CO, telephone 303 494 4774. A toll call from Newark, DE, costs between three and four cents, although it is not clear what carrier and time of day discounts apply. The modem dial string will differ depending on local telephone configuration, etc., and is specified by the phone command in the configuration file. The argument to this command is an AT command for a Hayes compatible modem.</p> 25 <p>The driver can operate in either of two modes, as determined by the mode parameter in the server configuration command. In mode 0 the driver operates continuously at intervals determined by the fudge time1 parameter, as described above. In mode 1 the driver is enabled only when no other sources of synchronization are available and when we have gone more than MAXOUTAGE (3600 s) since last synchronized by other sources of synchronization.</p> 26 <p>The accuracy produced by this driver should be in the range of a millisecond or two, but may need correction due to the delay characteristics of the individual modem involved. For undetermined reasons, some modems work with the ACTS echo-delay measurement scheme and some don't. This driver tries to do the best it can with what it gets. Initial experiments with a Practical Peripherals 9600SA modem here in Delaware suggest an accuracy of a millisecond or two can be achieved without the scheme by using a fudge time1 value of 65.0 ms. In either case, the dispersion for a single call involving ten samples is about 1.3 ms.</p> 27 <p>For reliable call management, this driver requires a 1200-bps modem with a Hayes-compatible command set and control over the modem data terminal ready (DTR) control line. Present restrictions require the use of a POSIX-compatible programming interface, although other interfaces may work as well. The ACTS telephone number and modem setup string are hard-coded in the driver and may require changes for nonstandard modems or special circumstances.</p> 28 <p>The fudge time1 parameter represents a propagation-delay correction factor which is added to the value computed by ACTS when the echo-delay scheme is used. This scheme does not work with all modems; for those that don't, fudge flag2 should be set to disable the feature. In this case the fudge time1 parameter represents the total propagation delay due to all causes and must be determined by external calibration.</p> 29 <p>The ACTS call interval is determined by a counter initially set to the fudge time2 parameter. At each poll interval, minpoll (usually 64 s) is subtracted from the counter. When the counter is equal to or less than zero, the fudge flag1 is set, which causes up to three call attempts to be made to ACTS. The fudge flag1 is reset after a valid clock update has been determined or by a device fault, timeout or manually using <tt>ntpdc</tt>. After a valid clock update, the counter is reset for the next interval. Setting the <tt>fudge time2</tt> parameter to zero disables automatic call attempts. Manual call attempts can be made at any time by setting <tt>fudgeflag1</tt> using ntpdc.</p> 30 <p>The NIST timecode message is transmitted at 1200 bps in the following format:</p> 31 <pre> 32jjjjj yy-mm-dd hh:mm:ss tt l uuu mmmmm UTC(NIST) * 33 34jjjjj = modified Julian day 35yy-mm-dd = year, month, day 36hh:mm:ss = hours, minutes, seconds 37tt = DST indicator (see driver listing) 38l = leap-second warning (see driver listing) 39uuu = DUT1 correction (see driver listing) 40mmmmm = modem calibration (see driver listing) 41on-time = '*'</pre> 42 <p>The timecode message is transmitted continuously after a signon banner, which this driver ignores. The driver also ignores all but the yy-mm-dd, hh:mm:ss and on-time character '*' fields, although it checks the format of all fields of the message. A timestamp is captured at the '*' character, as required by the ACTS specification, and used as the reference time of the timecode. If a message with an on-time character of '#' is received, the driver updates the propagation delay. The driver disconnects when (a) ten valid messages have been received, (b) no message has been received for 15 s, (c) an on-time character of '#' is received. These messages are processed by a trimmed-mean filter to reduce timing noise and then by the usual NTP algorithms to develop the clock correction.</p> 43 <p>Since the accumulated error grows with the interval between calls, it is important that the intrinsic frequency error be minimized. This can be done by observing difference in offsets between two calls placed some hours apart and calculating the uncorrected frequency error. This error, as a fixed-point value in parts-per-million, should be installed in the ntp.drift file before the daemon is started. Some experimentation may be necessary in order to reduce the intrinsic frequency error to the order of 1 ppm.</p> 44 <p>The behavior of the clock selection algorithm is modified when this driver is in use. The algorithm is designed so that this driver will never be selected unless no other discipline source is available. This can be overridden with the prefer keyword of the server configuration command, in which case only this driver will be selected for synchronization and all other discipline sources will be ignored.</p> 45 <p>Unlike other drivers, each ACTS call generates one clock correction and that correction is processed immediately. There is no wait to allow the clock filter to accumulate samples. In addition, the watchdog timeout of the local clock algorithm is disabled, so that a correction received from this driver that exceeds CLOCK_MAX (128 ms) causes an immediate step/slew.</p> 46 <p>Since the interval between updates can be much longer than used with ordinary NTP peers, the local clock procedure has been modified to operate in either of two modes, depending on whether the interval between updates is less than or greater than CLOCK_MAXSEC (1200 s). If less than this value, the local clock procedure operates using the standard NTP phase-lock loop as with other NTP peers. If greater than this value, the procedure operates using a modified frequency-lock loop suggested by Judah Levine in his lockclock algorithm designed specifically for ACTS.</p> 47 <h4>Call Management</h4> 48 <p>Since ACTS will be a toll call in most areas of the country, it is necessary to carefully manage the call frequency. This can be done in two ways, by specifying the interval between calls, or by setting a flag bit manually or via a cron job. The call interval is determined by a counter initially set to the fudge time2 parameter. At each poll interval, minpoll (usually 64 s) is subtracted from the counter. When the counter is equal to or less than zero, the fudge flag1 is set, which causes up to three call attempts to be made. The fudge flag1 is reset after ten offset samples have been determined in a single call or by a device fault, timeout or manually using ntpdc. Upon successful completion of a call, the eight samples have been shifted into the clock filter, the local clock updated and the counter reset for the next interval. Setting the fudge time2 parameter to zero disables automatic call attempts.</p> 49 <p>Manual call attempts can be made at any time by setting fudge flag1 using ntpdc. For example, the ntpdc command</p> 50 <pre> 51fudge 127.127.18.1 flags 1</pre> 52 <p>will ask for a key identifier and password and, if authenticated by the server, will set flag1. There may be a short delay until the expiration of the current poll timeout.</p> 53 <p>The flag1 can be set from a cron job in the following way. Construct a file with contents</p> 54 <pre>keyid 11 55passwd dialup 56fudge 127.127.18.1 flags 1 57quit</pre> 58 <p>Then, run the following program at specified times as required.</p> 59 <pre>/usr/local/bin/ntpdc <file</pre> 60 <h4>Monitor Data</h4> 61 <p>When enabled by the <tt>flag4</tt> fudge flag, every received timecode is written as-is to the <tt>clockstats</tt> file.</p> 62 <h4>Fudge Factors</h4> 63 <dl> 64 <dt><tt>time1 <i>time</i></tt> 65 <dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0. 66 <dt><tt>time2 <i>time</i></tt> 67 <dd>Not used by this driver. 68 <dt><tt>stratum <i>number</i></tt> 69 <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0. 70 <dt><tt>refid <i>string</i></tt> 71 <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <tt>NIST</tt>. 72 <dt><tt>flag1 0 | 1</tt> 73 <dd>Not used by this driver. 74 <dt><tt>flag2 0 | 1</tt> 75 <dd>Not used by this driver. 76 <dt><tt>flag3 0 | 1</tt> 77 <dd>Not used by this driver. 78 <dt><tt>flag4 0 | 1</tt> 79 <dd>Not used by this driver. 80 </dl> 81 <h4>Additional Information</h4> 82 <p><a href="../refclock.html">Reference Clock Drivers</a> </p> 83 <hr> 84 <script type="text/javascript" language="javascript" src="../scripts/footer.txt"></script> 85 </body> 86 87</html>