embedaddon/ntp/html/drivers/driver28.html - view

File: [ELWIX - Embedded LightWeight unIX -] / embedaddon / ntp / html / drivers / driver28.html
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Tue May 29 12:08:38 2012 UTC (12 years, 7 months ago) by misho
Branches: ntp, MAIN
CVS tags: v4_2_6p5p0, v4_2_6p5, HEAD

ntp 4.2.6p5

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Mozilla/4.01 [en] (Win95; I) [Netscape]"> <title>Shared memoy Driver</title> <link href="scripts/style.css" type="text/css" rel="stylesheet"> </head> <body> <h3>Shared Memory Driver</h3> <hr> <h4>Synopsis</h4> <p>Address: 127.127.28.<i>u</i><br> Reference ID: <tt>SHM</tt><br> Driver ID: <tt>SHM</tt></p> <h4>Description</h4> <p>This driver receives its reference clock info from a shared memory-segment. The shared memory-segment is created with owner-only access for unit 0 and 1, and world access for unit 2 and 3</p> <h4>Structure of shared memory-segment</h4> <pre>struct shmTime {   int    mode; /* 0 - if valid set                 *       use values,                  *       clear valid                 * 1 - if valid set                  *       if count before and after read of                  *       values is equal,                 *         use values                  *       clear valid                 */   int    count;   time_t clockTimeStampSec;      /* external clock */   int    clockTimeStampUSec;     /* external clock */   time_t receiveTimeStampSec;    /* internal clock, when external value was received */   int    receiveTimeStampUSec;   /* internal clock, when external value was received */   int    leap;   int    precision;   int    nsamples;   int    valid;   int    dummy[10];  };</pre> <h4>Operation mode=0</h4> <p>Each second, the valid-flag of the shared memory-segment is checked:</p> <p>If set, the values in the record (clockTimeStampSec, clockTimeStampUSec, receiveTimeStampSec, receiveTimeStampUSec, leap, precision) are passed to ntp, and the valid-flag is cleared and a counter is bumped.</p> <p>If not set, a counter is bumped</p> <h4>Operation mode=1</h4> <p>Each second, the valid-flag of the shared memory-segment is checked:</p> <p>If set, the count-field of the record is remembered, and the values in the record (clockTimeStampSec, clockTimeStampUSec, receiveTimeStampSec, receiveTimeStampUSec, leap, precision) are read. Then, the remembered count is compared to the count now in the record. If both are equal, the values read from the record are passed to ntp. If they differ, another process has modified the record while it was read out (was not able to produce this case), and failure is reported to ntp. The valid flag is cleared and a counter is bumped.</p> <p>If not set, a counter is bumped</p> <h4>gpsd</h4> <a href="http://gpsd.berlios.de/"><i>gpsd</i></a> knows how to talk to many GPS devices. It works with <i>ntpd</i> through the SHM driver. <P> The <i>gpsd</i> man page suggests setting minpoll and maxpoll to 4. That was an attempt to reduce jitter. The SHM driver was fixed (ntp-4.2.5p138) to collect data each second rather than once per polling interval so that suggestion is no longer reasonable. <P> <h4>Clockstats</h4> If flag4 is set when the driver is polled, a clockstats record is written. The first 3 fields are the normal date, time, and IP address common to all clockstats records. <P> The 4th field is the number of second ticks since the last poll. The 5th field is the number of good data samples found. The last 64 will be used by ntpd. The 6th field is the number of sample that didn't have valid data ready. The 7th field is the number of bad samples. The 8th field is the number of times the the mode 1 info was update while nptd was trying to grab a sample. <P> Here is a sample showing the GPS reception fading out: <pre> 54364 84927.157 127.127.28.0 66 65 1 0 0 54364 84990.161 127.127.28.0 63 63 0 0 0 54364 85053.160 127.127.28.0 63 63 0 0 0 54364 85116.159 127.127.28.0 63 62 1 0 0 54364 85180.158 127.127.28.0 64 63 1 0 0 54364 85246.161 127.127.28.0 66 66 0 0 0 54364 85312.157 127.127.28.0 66 50 16 0 0 54364 85375.160 127.127.28.0 63 41 22 0 0 54364 85439.155 127.127.28.0 64 64 0 0 0 54364 85505.158 127.127.28.0 66 36 30 0 0 54364 85569.157 127.127.28.0 64 0 64 0 0 54364 85635.157 127.127.28.0 66 0 66 0 0 54364 85700.160 127.127.28.0 65 0 65 0 0 </pre> <h4>Fudge Factors</h4> <dl> <dt><tt>time1 <i>time</i></tt> <dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0. <dt><tt>time2 <i>time</i></tt> <dd>Not used by this driver. <dt><tt>stratum <i>number</i></tt> <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0. <dt><tt>refid <i>string</i></tt> <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <tt>SHM</tt>. <dt><tt>flag1 0 | 1</tt> <dd>Not used by this driver. <dt><tt>flag2 0 | 1</tt> <dd>Not used by this driver. <dt><tt>flag3 0 | 1</tt> <dd>Not used by this driver. <dt><tt>flag4 0 | 1</tt> <dd>If flag4 is set, clockstats records will be written when the driver is polled. <h4>Additional Information</h4> <p><a href="../refclock.html">Reference Clock Drivers</a></p> </dl> <hr> <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> </body> </html>