+* Documentation nit cleanup.
* Documentation updates from Dave Mills.
(4.2.7p62) 2010/10/12 Released by Harlan Stenn <stenn@ntp.org>
* [Bug 1567] from 4.2.6p3-RC3: Support Arbiter 1093C Satellite Clock on
<hr>
<h2><font size="+1">Fudge Factors</font></h2>
<dl>
- <dt><b><a name="time1"></a><tt><font size="+1"><a href="#Configuration">time1 <i>time</i></a></font></tt></b>
+ <dt><b><tt><font size="+1">time1 <i>time</i></font></tt></b>
<dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0. Should be set to 20 milliseconds to correct serial line and operating system delays incurred in capturing time stamps from the synchronous packets.
<dt><tt><font size="+1"><a href="#REFID"><b>refid <i>string</i></b></a></font></tt>
<dd>Specifies the driver reference identifier, <b>GPS </b><i>or</i> <b>DCF</b>.
</ol>
<p>Well, this is very sketchy, i know. But I hope it helps a little bit. The best way is to look which clock comes closest to your and tweak that code.</p>
<p>Two sorts of clocks are used with parse. Clocks that automatically send their time code (once a second) do not need entries in the poll routines because they send the data all the time. The second sort are the clocks that need a command sent to them in order to reply with a time code (like the Trimble clock).</p>
- <p>For questions: <a href="mailto:%20kardel <AT> acm.org">kardel@acm.org</a>.</p>
+ <p>For questions: <a href="mailto:%20kardel AT acm.org">kardel@acm.org</a>.</p>
<p>Please include an exact description on how your clock works. (initialisation, TTY modes, strings to be sent to it, responses received from the clock).</p>
<hr>
<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
<body></body>
-</html>
\ No newline at end of file
+</html>
projects / thirdparty / ntp.git / commitdiff
