diff options
Diffstat (limited to 'html')
| -rw-r--r-- | html/drivers/driver22.html | 2 | ||||
| -rw-r--r-- | html/drivers/driver40-ja.html | 534 | ||||
| -rw-r--r-- | html/drivers/driver40.html | 358 | ||||
| -rw-r--r-- | html/drivers/driver46.html | 303 | ||||
| -rw-r--r-- | html/miscopt.html | 31 | ||||
| -rw-r--r-- | html/refclock.html | 2 |
6 files changed, 1109 insertions, 121 deletions
diff --git a/html/drivers/driver22.html b/html/drivers/driver22.html index 6e01a38cfe3f0..acae265d29500 100644 --- a/html/drivers/driver22.html +++ b/html/drivers/driver22.html @@ -80,7 +80,7 @@ <dd>Specifies PPS capture on the rising (assert) pulse edge if 0 (default) or falling (clear) pulse edge if 1. Not used under Windows - if the special <tt>serialpps.sys</tt> serial port driver is installed then the leading edge will <i>always</i> be used.</dd> <dt><tt>flag3 0 | 1</tt></dt> - <dd>Controls the kernel PPS discipline: 0 for disable (default), 1 for enable. Not used under Windows - if the special <tt>serialpps.sys<\tt> serial port driver is used then kernel PPS will be available and used.</dd> + <dd>Controls the kernel PPS discipline: 0 for disable (default), 1 for enable. Not used under Windows - if the special <tt>serialpps.sys</tt> serial port driver is used then kernel PPS will be available and used.</dd> <dt><tt>flag4 0 | 1</tt></dt> <dd>Record a timestamp once for each second if 1. Useful for constructing Allan deviation plots.</dd> diff --git a/html/drivers/driver40-ja.html b/html/drivers/driver40-ja.html new file mode 100644 index 0000000000000..8b67e9009d40b --- /dev/null +++ b/html/drivers/driver40-ja.html @@ -0,0 +1,534 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> + +<html lang="ja"> + + <head> + <meta http-equiv="content-type" content="text/html;charset=utf-8"> + <meta name="generator" content="HTML Tidy, see www.w3.org"> + <meta http-equiv="Content-Style-Type" content="text/css"> + <meta http-equiv="Content-Script-Type" content="text/javascript"> + <title>JJY Receivers</title> + <link rev="made" href="http://www.bea.hi-ho.ne.jp/abetakao/"> + <link rel="start" href="http://www.eecis.udel.edu/~mills/ntp/html/refclock.html"> + <link href="scripts/style.css" type="text/css" rel="stylesheet"> + </head> + + <body> + <h3>JJY Receivers</h3> +<p>Last update: + <!-- #BeginDate format:En2m -->15-May-2015 00:00<!-- #EndDate --> + UTC <a href="driver40.html">ENGLISH（英語）</a> <a href="driver40-ja.html">JAPANESE（日本語）</a></p> + <hr> + <h4>Synopsis</h4> + Address: 127.127.40.<em>u</em><br> + Reference ID: <code>JJY</code><br> + Driver ID: <code>JJY</code><br> + Serial Port: <code>/dev/jjy<em>u</em></code>; それぞれのJJY受信機、GPS時計、テレフォンJJYを参照して下さい。 + <h4>Description</h4> + <p>このドライバーは、以下の、日本で販売されている JJY受信機、GPS時計と、電話回線による時刻配信サービスをサポートしています。 + </p> + <table width="100%"> + <tr> + <td width="50%" style="vertical-align:top;"> + <a href="#mode-1">トライステート TS-JJY01, TS-JJY02</a><br> + <a href="#mode-2">シーデックス JST2000</a><br> + <a href="#mode-3">エコー計測器 LT-2000</a><br> + <a href="#mode-4">シチズンTIC JJY-200</a><br> + <a href="#mode-5">トライステート TS-GPSclock-01</a><br> + </td> + <td width="50%" style="vertical-align:top; border-left:solid; padding:0px 0px 0px 10px;"> + <a href="#mode-6">セイコー タイム システム TDC-300</a><br> + <a href="#mode-100">テレフォンJJY</a><br> + </td> + </tr> + </table> + <ul> + + <li> + <p><a name="mode-1">トライステート TS-JJY01, TS-JJY02</a> <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (日本語)</p><br> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 1</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN flag1 0|1</dt> + <dd> + <p>Time1 は、受信機からの時刻に加算する調整時間を、固定小数点形式の秒で設定します。<br> + この受信機には、数10ミリ秒 ( 0.0NN秒 ) から百数10ミリ秒 ( 0.1NN秒 ) の調整時間を設定すると良いでしょう。</p> + <p>Flag1 は、時刻同期には無関係です。Flag1 を 1 に設定すると、状態を問い合わせるコマンドを DATE コマンドと STIM コマンドの前に発行して、応答を clockstats ファイルに記録します。</p> + <table border="1" summary="fudge flag1"> + <tr><td>0 (Default)</td><td>DCST と STUS コマンドは、発行しません。</td></tr> + <tr><td>1</td><td>DCST と STUS コマンドを、発行します。</td></tr> + </table> + </dd> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>RS-232C, 9600 BPS, 8ビット, パリティなし, 1ストップ・ビット</p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td><code>dcst{CR}{LF}</code></td> + <td> --> </td> + <td><code>valid{CR}{LF} | invalid{CR}{LF}</code></td> + </tr> + <tr> + <td><code>stus{CR}{LF}</code></td> + <td> --> </td> + <td><code>adjusted{CR}{LF} | unadjusted{CR}{LF}</code></td> + </tr> + <tr> + <td><code>time{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + <tr> + <td><code>date{CR}{LF}</code></td> + <td> --> </td> + <td><code>YYYY/MM/DD WWW{CR}{LF}</code></td> + </tr> + <tr> + <td><code>stim{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + </table> + <p>日付と時刻は、別々に問い合わせます。日付が深夜０時の前か後かの不確定をチェックするため、日付の問い合わせの前後に時刻を問い合わせています。</p><br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-2">シーデックス JST2000</a> <a href="http://www.c-dex.co.jp/">http://www.c-dex.co.jp/</a> (日本語)</p><br> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 2</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>RS-232C, 9600 BPS, 8ビット, パリティなし, 1ストップ・ビット</p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td><code>{ENQ}1J{ETX}</code></td> + <td> --> </td> + <td><code>{STX}JYYMMDD HHMMSSS{ETX}</code></td> + </tr> + </table> + <br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-3">エコー計測器 LT-2000</a> <a href="http://www.clock.co.jp/">http://www.clock.co.jp/</a> (日本語)</p><br> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 3</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> + <br> + </dd> + <dt>Interface</dt> + <dd> + <p>RS-232C, 9600 BPS, 8ビット, パリティなし, 1ストップ・ビット</p> + <br> + </dd> + <dt>Time code format</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td><code>C</code></td> + <td> --> </td> + <td>( Mode 2 : Continuous )</td> + </tr> + <tr> + <td>( Every second before 0.5 second )</td> + <td></td> + <td><code>YYMMDDWHHMMSS{ST1}{ST2}{ST3}{ST4}{CR}</code></td> + </tr> + <tr> + <td><code>#</code></td> + <td> --> </td> + <td>( Mode 1 : Request&Send )</td> + </tr> + </table> + <br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-4">シチズンTIC JJY-200</a> <a href="http://www.tic-citizen.co.jp/">http://www.tic-citizen.co.jp/</a> (日本語)</p><br> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 4</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>RS-232C, 4800 BPS, 8ビット, パリティなし, 1ストップ・ビット</p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td>( Every second )</td> + <td></td> + <td><code>'XX YY/MM/DD W HH:MM:SS{CR}</code></td> + </tr> + </table> + <br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-5">トライステート TS-GPSclock-01</a> <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (日本語)</p> + <p>このドライバーは、JJY受信機ではないGPS時計のトライステート TS-GPSclock-01 のコマンド・レスポンス・モードをサポートします。<br> + TS-GPSclock-01 は、オンボードのスイッチとメニューでコマンド・レスポンス・モードとタイム・ゾーンをJST（日本標準時）に設定しなければなりまん。<br> + この Type 40 のドライバーの他, TS-GPSclock-01 のNMEAモードは、<a href="driver20.html">一般 NMEA GPS ドライバー ( Type 20 )</a> でも利用することができます。</p> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 5</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN flag1 0|1</dt> + <dd> + <p>Time1 は、受信機からの時刻に加算する調整時間を、固定小数点形式の秒で設定します</p> + <p>Flag1 は、時刻同期には無関係です。Flag1 を 1 に設定すると、状態を問い合わせるコマンドを DATE コマンドと STIM コマンドの前に発行して、応答を clockstats ファイルに記録します。</p> + <table border="1" summary="fudge flag1"> + <tr><td>0 (Default)</td><td>STUS コマンドは、発行しません。</td></tr> + <tr><td>1</td><td>STUS コマンドを、発行します。</td></tr> + </table> + </dd> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>USB ( /dev/ttyACM<em>0</em> )</p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td><code>stus{CR}{LF}</code></td> + <td> --> </td> + <td><code>*R{CR}{LF} | *G{CR}{LF} | *U{CR}{LF} | +U{CR}{LF}</code></td> + </tr> + <tr> + <td><code>time{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + <tr> + <td><code>date{CR}{LF}</code></td> + <td> --> </td> + <td><code>YYYY/MM/DD{CR}{LF}</code></td> + </tr> + <tr> + <td><code>time{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + </table> + <p>日付と時刻は、別々に問い合わせます。日付が深夜０時の前か後かの不確定をチェックするため、日付の問い合わせの前後に時刻を問い合わせています。</p><br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-6">セイコー タイム システム TDC-300</a> <a href="http://www.seiko-sts.co.jp/">http://www.seiko-sts.co.jp/</a> (英語と日本語)</p><br> + <p>TDC-300 は、フロント・パネルのメニュー表示とスイッチで type 3 のデータ形式に設定しなければなりません。</p> + <dl> + <dt>NTP configuration ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 6</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>RS-232C, 2400 BPS, 8-bits, no parity, 1 stop bit</p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td></td> + <td></td> + <td><code>{STX}YYMMDDWHHMMSS{ETX}</code></td> + </tr> + <tr> + <td>( 5 to 10 mSec. before second )</td> + <td></td> + <td><code>{STX}{xE5}{ETX}</code></td> + </tr> + </table> + <br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-100">テレフォンJJY</a> <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a> (英語と日本語)</p> + <p>テレフォンJJYは、電話回線による時刻配信サービスです。<br> + このサービスは、国立研究開発法人 情報通信研究機構が提供しています。</p> + <p>注意： このモード（テレフォンJJY）は、refclock_acts ( Type 18 ) のドライバーと同時に利用することはできません。 + 設定ファイルの phone は、server と関係付けられていないため、ドライバーの refclock_acts ( type 18 ) も、この refclock_jjy ( type 40, mode 100 to 180 ) のいずれも、 + 複数の phone のうち、どれが自分に関係するものか識別できないからです。</p> + <dl> + <dt>NTPの設定 ( ntp.conf )</dt> + <dd> + <dl> + <dt>server 127.127.40.X mode (100, 101 to 180) minpoll N</dt> + <dd> + <p>モード 100 を設定した場合、このドライバーは、遅延を計測するためのループバック・コマンドは発行せず、電話回線とシステムの処理による遅延は調整しません。<br> + モード 101 から 180 を設定した場合、このドライバーは、ループバック・コマンドを発行して、テレフォンJJYのループバック回路を通して電話回線とシステムの処理による遅延を計測します。<br> + テレフォンJJYのループバック回路を経由した往復の時間は、5回、計測されます。 + それぞれの遅延時間のうち、700ミリ秒を超えたものは、平均遅延時間の計算より除外されます。 + また、700ミリ秒以下の有効な遅延時間が、3回以上の場合は、そのうち、最大の遅延時間は、平均遅延時間の計算より除外され、 + 4回以上の場合は、そのうち、最小の遅延時間は、平均遅延時間の計算より除外されます。 + 調整時間は、往復時間 × ( モード番号 - 100 ) % で計算し、同期する時刻に加算されます。<br> + モード 101 から 180 を設定して自動遅延補正を選択するなら、モード 145 から 165 が良いでしょう。</p> + <p>デフォルトの日時問い合わせ処理間隔 6 ( 64 秒 ) は、このモードには、短すぎます。 "minpoll" は、8 ( 256 秒, 約 4 分 ) 以上を設定して下さい。<br> + 日時問い合わせ処理間隔は、秒数を 2 のべき乗で指定します。 minpoll の値が、12 なら 4096 秒（約1時間）、14 なら 16384 秒（約4.5時間）、16 なら 65536 秒（約18時間）となります。</p><br> + </dd> + <dt>fudge 127.127.40.X flag1 0|1 flag2 0|1 flag3 0|1 flag4 0|1</dt> + <dd> + <p>Time1 は、受信機からの時刻に加算する調整時間を、固定小数点形式の秒で設定します。<br> + mode 100 の場合は、time1 で調整する時間を設定したほうが良いでしょう。<br> + mode 101 から 180 の場合は、このドライバーが計測したループバックの遅延時間の一定の割合を同期時刻に加算しますので、time1 は設定しないほうが良いでしょう。</p> + <div style="text-align:left;">Flag1 は、タッチ・トーンかダイヤル・パルスかを指定します。</div> + <table border="1" summary="fudge flag1"> + <tr><td>0 (Default)</td><td>タッチ・トーン</td><td>ATDWTnn...nn</td></tr> + <tr><td>1</td><td>ダイヤル・パルス</td><td>ATDWPnn...nn</td></tr> + </table> + <br> + <div style="text-align:left;">Flag2 は、エラー訂正プロトコルを指定します。</div> + <table border="1" summary="fudge flag2"> + <tr><td>0 (Default)</td><td>ノーマル（エラー訂正なし）</td><td>AT\N0</td></tr> + <tr><td>1</td><td>V42, MNP, ノーマルの自動選択</td><td>AT\N3</td></tr> + </table> + <br> + <div style="text-align:left;">Flag3 は、スピーカーのオン／オフを指定します。</div> + <table border="1" summary="fudge flag3"> + <tr><td>0 (Default)</td><td>オフ</td><td>ATM0Ln</td></tr> + <tr><td>1</td><td>オン</td><td>ATM2Ln</td></tr> + </table> + <br> + <div style="text-align:left;">Flag4 は、スピーカーの音量を指定します。</div> + <table border="1" summary="fudge flag4"> + <tr><td>0 (Default)</td><td>低</td><td>ATMnL1</td></tr> + <tr><td>1</td><td>中</td><td>ATMnL2</td></tr> + </table> + <br> + </dd> + <dt>phone 042NNNNNNN</dt> + <dd> + <p>電話番号は、<a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a> で公開されています。<br> + 電話番号の桁数をチェックしています。もし、日本国外から発信するために国際電話アクセス番号と国番号を付加すると、桁数制限を超えます。<br> + また、電話番号の最初の2桁や3桁をチェックしています。日本の緊急番号や特別のサービスの番号を指定することはできません。<br> + 内線から外線に発信する時は、"0," ( ゼロとカンマ ) を先頭に付加して下さい。外線発信番号は、チェックしていて、それ以外の外線発信番号を指定することはできません。</p> + </dd> + </dl> + <br> + </dd> + <dt>インターフェース</dt> + <dd> + <p>RS-232C 又は USB, 2400 BPS, 8ビット, パリティなし, 1ストップ・ビット</p> + <p>モデム制御コマンド:<br> + <code>ATE0Q0V1, ATMnLn, AT&K4, AT+MS=V22B, AT%C0, AT\Nn, ATH1, ATDWxnn...nn</code><br> + <code>+++, ATH0</code></p> + <br> + </dd> + <dt>日時データの形式</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>プロンプト</td> + <td> --> </td> + <td>コマンド</td> + <td> --> </td> + <td>応答</td> + </tr> + <tr> + <td><code>Name{SP}?{SP}</code></td> + <td> --> </td> + <td><code>TJJY{CR}</code></td> + <td> --> </td> + <td>Welcome messages</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>LOOP{CR}</code></td> + <td> --> </td> + <td>( Switch to the loopback circuit )</td> + </tr> + <tr> + <td><code> </code></td> + <td> </td> + <td><code>( One char. )</code></td> + <td> --> </td> + <td><code>( One char. )</code></td> + </tr> + <tr> + <td><code> </code></td> + <td> </td> + <td><code>COM{CR}</code></td> + <td> --> </td> + <td>( Exit from the loopback circuit )</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>TIME{CR}</code></td> + <td> --> </td> + <td><code>HHMMSS{CR}HHMMSS{CR}HHMMSS{CR}</code> 3 times on second</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>4DATE{CR}</code></td> + <td> --> </td> + <td><code>YYYYMMDD{CR}</code></td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>LEAPSEC{CR}</code></td> + <td> --> </td> + <td><code>{SP}0{CR} | +1{CR} | -1{CR}</code></td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>TIME{CR}</code></td> + <td> --> </td> + <td><code>HHMMSS{CR}HHMMSS{CR}HHMMSS{CR}</code> 3 times on second</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>BYE{CR}</code></td> + <td> --> </td> + <td>Sayounara messages</td> + </tr> + </table> + <p>日付と時刻は、別々に問い合わせます。日付が深夜０時の前か後かの不確定をチェックするため、日付の問い合わせの前後に時刻を問い合わせています。<br> + うるう秒は、処理していません。情報として clockstats ファイルに記録しているだけです。</p> + <br> + </dd> + </dl> + </li> + + </ul> + + <p>JJY は、長波で日本標準時(JST)を送信している無線局で、国立研究開発法人 情報通信研究機構が運用しています。JJY の運用情報などは、 <a href="http://www.nict.go.jp/">http://www.nict.go.jp/</a>（英語と日本語）や <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a>（英語と日本語）で提供されています。</p> + <p>実際のシリアル・ポートのデバイスにシンボリック・リンクを作成して下さい。シンボリック・リンクを作成するコマンドは、以下のとおりです。</p> + <p><code>ln -s /dev/ttyS0 /dev/jjy0</code></p> + <p>RS-232C から USB への変換ケーブルを利用して、JJY受信機、GPS時計、モデムをRS-232Cポートではなく、USBに接続することができます。この場合のシンボリック・リンクを作成するコマンドは、以下のとおりです。</p> + <p><code>ln -s /dev/ttyUSB0 /dev/jjy0</code></p> + <p>Windows NT の場合は、 COM<em>X</em>: の数字部分がドライバーのユニット番号に使用されます。 ドライバーのユニット 1 は、COM1: にユニット 3 は、COM3: に対応します。</p> + <h4>Monitor Data</h4> + <p>このドライバーは、JJY受信機、GPS時計、モデムとの送受信データを <code>clockstats</code> ファイルに記録します。</p> + <p><code> + statsdir /var/log/ntpd/<br> + filegen clockstats file clockstats type day enable + </code></p> + <div style="text-align:left;">レコード中のマークについて</div> + <table border="1" summary="Clockstats"> + <tr><td><code>JJY</code> </td><td>情報（このドライバーの開始または終了）</td></tr> + <tr><td><code>--></code> </td><td>送信データ</td></tr> + <tr><td><code><--</code> </td><td>受信データ</td></tr> + <tr><td><code>---</code> </td><td>情報</td></tr> + <tr><td><code>===</code> </td><td>情報（ポーリングの開始、および、同期時刻）</td></tr> + <tr><td><code>-W-</code> </td><td>警告メッセージ</td></tr> + <tr><td><code>-X-</code> </td><td>エラー・メッセージ</td></tr> + </table> + <h4>Fudge Factors</h4> + <dl> + <dt><code>time1 <em>time</em></code></dt> + <dd>受信機からの時刻に対する調整時間を、固定小数点形式の秒で設定します。デフォルトは、0.0秒です。</dd> + <dt><code>time2 <em>time</em></code></dt> + <dd>未使用。</dd> + <dt><code>stratum <em>number</em></code></dt> + <dd>NTPの階層番号を 0 から 15 で指定します。デフォルトは、0です。</dd> + <dt><code>refid <em>string</em></code></dt> + <dd>ドライバーIDで、ASCII の1文字から4文字で指定します。デフォルトは、<code>JJY</code> です。</dd> + <dt><code>flag1 0 | 1</code></dt> + <dd>それぞれのモードを参照して下さい。</dd> + <dt><code>flag2 0 | 1</code></dt> + <dd>それぞれのモードを参照して下さい。</dd> + <dt><code>flag3 0 | 1</code></dt> + <dd>それぞれのモードを参照して下さい。</dd> + <dt><code>flag4 0 | 1</code></dt> + <dd>それぞれのモードを参照して下さい。</dd> + </dl> + <hr> + <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> + </body> + +</html> diff --git a/html/drivers/driver40.html b/html/drivers/driver40.html index 6799f7699611b..356429e499e6d 100644 --- a/html/drivers/driver40.html +++ b/html/drivers/driver40.html @@ -5,6 +5,7 @@ <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <meta name="generator" content="HTML Tidy, see www.w3.org"> + <meta http-equiv="Content-Style-Type" content="text/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <title>JJY Receivers</title> <link rev="made" href="http://www.bea.hi-ho.ne.jp/abetakao/"> @@ -15,8 +16,8 @@ <body> <h3>JJY Receivers</h3> <p>Last update: - <!-- #BeginDate format:En2m -->3-May-2011 00:20<!-- #EndDate --> - UTC</p> + <!-- #BeginDate format:En2m -->15-May-2015 00:00<!-- #EndDate --> + UTC <a href="driver40.html">ENGLISH</a> <a href="driver40-ja.html">JAPANESE</a></p> <hr> <h4>Synopsis</h4> Address: 127.127.40.<em>u</em><br> @@ -24,19 +25,37 @@ Driver ID: <code>JJY</code><br> Serial Port: <code>/dev/jjy<em>u</em></code>; See corresponding receiver <h4>Description</h4> - <p>This driver supports the following JJY receivers sold in Japan.</p> + <p>This driver supports the following the JJY receivers and the GPS clock sold in Japan, and the time service through a telephone line. + </p> + <table width="100%"> + <tr> + <td width="50%" style="vertical-align:top;"> + <a href="#mode-1">Tristate Ltd. TS-JJY01, TS-JJY02</a><br> + <a href="#mode-2">C-DEX Co.,Ltd. JST2000</a><br> + <a href="#mode-3">Echo Keisokuki Co.,Ltd. LT-2000</a><br> + <a href="#mode-4">CITIZEN T.I.C. CO.,LTD. JJY-200</a><br> + <a href="#mode-5">Tristate Ltd. TS-GPSclock-01</a><br> + </td> + <td width="50%" style="vertical-align:top; border-left:solid; padding:0px 0px 0px 10px;"> + <a href="#mode-6">SEIKO TIME SYSTEMS INC. TDC-300</a><br> + <a href="#mode-100">Telephone JJY</a><br> + </td> + </tr> + </table> <ul> <li> - <p>Tristate Ltd. JJY01, JJY02 <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (Japanese only)</p><br> + <p><a name="mode-1">Tristate Ltd. TS-JJY01, TS-JJY02</a> <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (Japanese only)</p><br> <dl> <dt>NTP configuration ( ntp.conf )</dt> - <dd> - <p>server 127.127.40.X mode 1</p> + <dd><br> <dl> - <dt>fudge 127.127.40.X flag1 0|1</dt> + <dt>server 127.127.40.X mode 1</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN flag1 0|1</dt> <dd> - <p>Flag1 has no effect for time synchronization. When a flag1 is set to 1, status commands are issued before DATE and STIM commands, and write a response text into a clockstats file.</p> + <p>Time1 may specify a constant to be added to the time offset for the time from the receiver, a fixed-point decimal number in seconds. You may specify the time offset from several tens of milli-seconds ( 0.0NN seconds ) to a hundred and several tens of milli-seconds ( 0.1NN seconds ) for this clock.</p> + <p>Flag1 has no effect for time synchronization. When flag1 is set to 1, status commands are issued before DATE and STIM commands, and write a response text into the clockstats file.</p> <table border="1" summary="fudge flag1"> <tr><td>0 (Default)</td><td>DCST and STUS commands are not issued</td></tr> <tr><td>1</td><td>DCST and STUS commands are issued</td></tr> @@ -47,7 +66,7 @@ </dd> <dt>Interface</dt> <dd> - <p>RS-232C, 9600 baud, 8-bits, no parity, 1 stop bit</p> + <p>RS-232C, 9600 BPS, 8-bits, no parity, 1 stop bit</p> <br> </dd> <dt>Time code format</dt> @@ -59,6 +78,21 @@ <td>Reply</td> </tr> <tr> + <td><code>dcst{CR}{LF}</code></td> + <td> --> </td> + <td><code>valid{CR}{LF} | invalid{CR}{LF}</code></td> + </tr> + <tr> + <td><code>stus{CR}{LF}</code></td> + <td> --> </td> + <td><code>adjusted{CR}{LF} | unadjusted{CR}{LF}</code></td> + </tr> + <tr> + <td><code>time{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + <tr> <td><code>date{CR}{LF}</code></td> <td> --> </td> <td><code>YYYY/MM/DD WWW{CR}{LF}</code></td> @@ -69,22 +103,26 @@ <td><code>HH:MM:SS{CR}{LF}</code></td> </tr> </table> - <br> + <p>The date and time are requested separately. The time is requested before and after the date request to check uncertainty of the date whether it's before or after midnight.</p><br> </dd> </dl> </li> <li> - <p>C-DEX Co.,Ltd. JST2000 <a href="http://www.c-dex.co.jp/">http://www.c-dex.co.jp/</a> (Japanese only)</p><br> + <p><a name="mode-2">C-DEX Co.,Ltd. JST2000</a> <a href="http://www.c-dex.co.jp/">http://www.c-dex.co.jp/</a> (Japanese only)</p><br> <dl> <dt>NTP configuration ( ntp.conf )</dt> - <dd> - <p>server 127.127.40.X mode 2</p> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 2</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> <br> </dd> <dt>Interface</dt> <dd> - <p>RS-232C, 9600 baud, 8-bits, no parity, 1 stop bit</p> + <p>RS-232C, 9600 BPS, 8-bits, no parity, 1 stop bit</p> <br> </dd> <dt>Time code format</dt> @@ -107,16 +145,20 @@ </li> <li> - <p>Echo Keisokuki Co.,Ltd. LT-2000 <a href="http://www.clock.co.jp/">http://www.clock.co.jp/</a> (Japanese only)</p><br> + <p><a name="mode-3">Echo Keisokuki Co.,Ltd. LT-2000</a> <a href="http://www.clock.co.jp/">http://www.clock.co.jp/</a> (Japanese only)</p><br> <dl> <dt>NTP configuration ( ntp.conf )</dt> - <dd> - <p>server 127.127.40.X mode 3</p> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 3</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> <br> </dd> <dt>Interface</dt> <dd> - <p>RS-232C, 9600 baud, 8-bits, no parity, 1 stop bit</p> + <p>RS-232C, 9600 BPS, 8-bits, no parity, 1 stop bit</p> <br> </dd> <dt>Time code format</dt> @@ -149,16 +191,20 @@ </li> <li> - <p>CITIZEN T.I.C. CO.,LTD. JJY-200 <a href="http://www.tic-citizen.co.jp/">http://www.tic-citizen.co.jp/</a> (Japanese only)</p><br> + <p><a name="mode-4">CITIZEN T.I.C. CO.,LTD. JJY-200</a> <a href="http://www.tic-citizen.co.jp/">http://www.tic-citizen.co.jp/</a> (Japanese only)</p><br> <dl> <dt>NTP configuration ( ntp.conf )</dt> - <dd> - <p>server 127.127.40.X mode 4</p> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 4</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> <br> </dd> <dt>Interface</dt> <dd> - <p>RS-232C, 4800 baud, 8-bits, no parity, 1 stop bit</p> + <p>RS-232C, 4800 BPS, 8-bits, no parity, 1 stop bit</p> <br> </dd> <dt>Time code format</dt> @@ -181,16 +227,18 @@ </li> <li> - <p>Tristate Ltd. TS-GPSclock-01 <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (Japanese only)</p> + <p><a name="mode-5">Tristate Ltd. TS-GPSclock-01</a> <a href="http://www.tristate.ne.jp/">http://www.tristate.ne.jp/</a> (Japanese only)</p> <p>This driver supports the Tristate TS-GPSclock-01 in command/response mode, though it is a GPS clock, not JJY radio clock. Using the menus and the onboard switches, the TS-GPSclock-01 should be set to command/response mode and JST time zone.<br> Besides this driver ( Type 40 ), <a href="driver20.html">the generic NMEA GPS driver ( Type 20 )</a> supports the TS-GPSclock-01 in NMEA mode.</p> <dl> <dt>NTP configuration ( ntp.conf )</dt> - <dd> - <p>server 127.127.40.X mode 5</p> + <dd><br> <dl> - <dt>fudge 127.127.40.X flag1 0|1</dt> + <dt>server 127.127.40.X mode 5</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN flag1 0|1</dt> <dd> + <p>Time1 may specify a constant to be added to the time offset for the time from the receiver, a fixed-point decimal number in seconds.</p> <p>Flag1 has no effect for time synchronization. When a flag1 is set to 1, status command is issued before DATE and TIME commands, and write a response text into a clockstats file.</p> <table border="1" summary="fudge flag1"> <tr><td>0 (Default)</td><td>STUS command is not issued</td></tr> @@ -214,6 +262,16 @@ <td>Reply</td> </tr> <tr> + <td><code>stus{CR}{LF}</code></td> + <td> --> </td> + <td><code>*R{CR}{LF} | *G{CR}{LF} | *U{CR}{LF} | +U{CR}{LF}</code></td> + </tr> + <tr> + <td><code>time{CR}{LF}</code></td> + <td> --> </td> + <td><code>HH:MM:SS{CR}{LF}</code></td> + </tr> + <tr> <td><code>date{CR}{LF}</code></td> <td> --> </td> <td><code>YYYY/MM/DD{CR}{LF}</code></td> @@ -224,38 +282,250 @@ <td><code>HH:MM:SS{CR}{LF}</code></td> </tr> </table> + <p>The date and time are requested separately. The time is requested before and after the date request to check uncertainty of the date whether it's before or after midnight.</p><br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-6">SEIKO TIME SYSTEMS INC. TDC-300</a> <a href="http://www.seiko-sts.co.jp/">http://www.seiko-sts.co.jp/</a> (English and Japanese)</p><br> + <p>The TDC-300 must be set to the type 3 data format using the front panel menu display and the switches.</p> + <dl> + <dt>NTP configuration ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode 6</dt> + <dd><br></dd> + <dt>fudge 127.127.40.X time1 0.NNN</dt> + </dl> + <br> + </dd> + <dt>Interface</dt> + <dd> + <p>RS-232C, 2400 BPS, 8-bits, no parity, 1 stop bit</p> + <br> + </dd> + <dt>Time code format</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>Command</td> + <td> --> </td> + <td>Reply</td> + </tr> + <tr> + <td></td> + <td></td> + <td><code>{STX}YYMMDDWHHMMSS{ETX}</code></td> + </tr> + <tr> + <td>( 5 to 10 mSec. before second )</td> + <td></td> + <td><code>{STX}{xE5}{ETX}</code></td> + </tr> + </table> + <br> + </dd> + </dl> + </li> + + <li> + <p><a name="mode-100">Telephone JJY</a> <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a> (English and Japanese)</p> + <p>The telephone JJY is the time service through a public telephone line.<br> + The service is provided by the National Institute of Information and Communications Technology in Japan.</p> + <p>ATTENTION; This mode, the telephone JJY, can not be used with the refclock_acts ( type 18 ) at the same time. + Because the "phone" statement in the ntp configuration file is not involved with the "server" statement, + so the both the refclock_acts ( type 18 ) and this refclock_jjy ( type 40, mode 100 to 180 ) can not recognize the appropriate "phone" statement among the "phone" statements.</p> + <dl> + <dt>NTP configuration ( ntp.conf )</dt> + <dd><br> + <dl> + <dt>server 127.127.40.X mode (100, 101 to 180) minpoll N</dt> + <dd> + <p>The mode 100 is specified, this driver does not issue the loopback command in order to measure the delay, and the delay of the telephone line and the system processing is not adjusted.<br> + The mode 101 to 180 is specified, this driver issues the loopback command and measures the delay of the telephone line and the system processing through the Telphone JJY loopback circuit.<br> + The round trip time through the Telphone JJY loopback circuit is measured 5 times, and each delay time is greater than 700 milli-seconds, + that delay time is ignored during average delay time calculation. Also, if the valid delay time ( <= 700 mS. ) is measured more than 3 times, the maximum delay time among the valid delay times is ignored, + and if the valid delay time is measured more than 4 times, the minimum delay time among them is ignored, like marking/grading sports judgment.<br> + The adjustment time is calculated by the formula,<br> + multiply ( the measured round trip time ) by ( ( the mode number ) - 100 ) %,<br> + and the adjustment delay time is added to the syncronizing time.<br> + If you choose the automatic delay ajustment, in other words, the mode 101 to 180 is specifed, the recommended mode number is 145 to 165.</p> + <p>The default polling interval 6 ( 64 seconds ) is too short for this mode. The "minpoll" should be set to greater than or equal to 8 ( 256 seconds, about 4 minutes ).<br> + The interval time is given the value in second power of 2. The minpoll value 12 is 4096 seconds interval ( about 1 hour ), 14 is 16384 seconds interval ( about 4.5 hours ), 16 is 65536 seconds ( about 18 hours ), respectively.</p><br> + </dd> + <dt>fudge 127.127.40.X flag1 0|1 flag2 0|1 flag3 0|1 flag4 0|1</dt> + <dd> + <p>Time1 may specify a constant to be added to the time offset for the time from the receiver, a fixed-point decimal number in seconds.<br> + When the mode 100 is specified, the time1 may be specified in order to adjust the time offset.<br> + When the mode 101 to 180 is specified, the time1 should not be specified because this driver adds some percentage of the measured loopback delay, depending on the value of the mode number.</p> + <div style="text-align:left;">Flag1 is the modem dialing type.</div> + <table border="1" summary="fudge flag1"> + <tr><td>0 (Default)</td><td>Tone</td><td>ATDWTnn...nn</td></tr> + <tr><td>1</td><td>Pulse</td><td>ATDWPnn...nn</td></tr> + </table> + <br> + <div style="text-align:left;">Flag2 is the modem error correction type.</div> + <table border="1" summary="fudge flag2"> + <tr><td>0 (Default)</td><td>Normal</td><td>AT\N0</td></tr> + <tr><td>1</td><td>Auto V42, MNP, Normal</td><td>AT\N3</td></tr> + </table> + <br> + <div style="text-align:left;">Flag3 is the modem speaker switch.</div> + <table border="1" summary="fudge flag3"> + <tr><td>0 (Default)</td><td>Off</td><td>ATM0Ln</td></tr> + <tr><td>1</td><td>On</td><td>ATM2Ln</td></tr> + </table> + <br> + <div style="text-align:left;">Flag4 is the modem speaker volume.</div> + <table border="1" summary="fudge flag4"> + <tr><td>0 (Default)</td><td>Low</td><td>ATMnL1</td></tr> + <tr><td>1</td><td>Middle</td><td>ATMnL2</td></tr> + </table> + <br> + </dd> + <dt>phone 042NNNNNNN</dt> + <dd> + <p>The phone number is available at <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a><br> + The number of digits of the phone number is checked. If the international access number and the country number are added in order to call from outside of Japan, the number of digits is over the limit.<br> + The first 2 or 3 digits are checked. The emergency service number and the special service number in Japan are not allowed.<br> + Calling from extension line, the number for an outside line should be prefix "0," ( Zero, Comma ). The prefix is also checked, and no other outside access number is allowed.</p> + </dd> + </dl> + <br> + </dd> + <dt>Interface</dt> + <dd> + <p>RS-232C or USB, 2400 BPS, 8-bits, no parity, 1 stop bit</p> + <p>Modem control commands:<br> + <code>ATE0Q0V1, ATMnLn, AT&K4, AT+MS=V22B, AT%C0, AT\Nn, ATH1, ATDWxnn...nn</code><br> + <code>+++, ATH0</code></p> + <br> + </dd> + <dt>Time code format</dt> + <dd><br> + <table summary="CommandAndReply"> + <tr> + <td>Prompt</td> + <td> --> </td> + <td>Command</td> + <td> --> </td> + <td>Reply</td> + </tr> + <tr> + <td><code>Name{SP}?{SP}</code></td> + <td> --> </td> + <td><code>TJJY{CR}</code></td> + <td> --> </td> + <td>Welcome messages</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>LOOP{CR}</code></td> + <td> --> </td> + <td>( Switch to the loopback circuit )</td> + </tr> + <tr> + <td><code> </code></td> + <td> </td> + <td><code>( One char. )</code></td> + <td> --> </td> + <td><code>( One char. )</code></td> + </tr> + <tr> + <td><code> </code></td> + <td> </td> + <td><code>COM{CR}</code></td> + <td> --> </td> + <td>( Exit from the loopback circuit )</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>TIME{CR}</code></td> + <td> --> </td> + <td><code>HHMMSS{CR}HHMMSS{CR}HHMMSS{CR}</code> 3 times on second</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>4DATE{CR}</code></td> + <td> --> </td> + <td><code>YYYYMMDD{CR}</code></td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>LEAPSEC{CR}</code></td> + <td> --> </td> + <td><code>{SP}0{CR} | +1{CR} | -1{CR}</code></td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>TIME{CR}</code></td> + <td> --> </td> + <td><code>HHMMSS{CR}HHMMSS{CR}HHMMSS{CR}</code> 3 times on second</td> + </tr> + <tr> + <td><code>></code></td> + <td> --> </td> + <td><code>BYE{CR}</code></td> + <td> --> </td> + <td>Sayounara messages</td> + </tr> + </table> + <p>The date and time are requested separately. The time is requested before and after the date request to check uncertainty of the date whether it's before or after midnight.<br> + The leap second is not handled, and only written in the clockstats file as an information.</p> <br> </dd> </dl> </li> </ul> - <p>JJY is the radio station which transmites the JST (Japan Standard Time) in long wave radio. The station JJY is operated by the National Institute of Information and Communications Technology. An operating announcement and some information are avaiable from <a href="http://www.nict.go.jp/">http://www.nict.go.jp/</a> (English and Japanese) and <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a> (English and Japanese)</p> + + <p>The JJY is the radio station which transmits the JST (Japan Standard Time) in long wave radio. The station JJY is operated by the National Institute of Information and Communications Technology. + An operating announcement and some information are available from <a href="http://www.nict.go.jp/">http://www.nict.go.jp/</a> (English and Japanese) and <a href="http://jjy.nict.go.jp/">http://jjy.nict.go.jp/</a> (English and Japanese)</p> <p>The user is expected to provide a symbolic link to an available serial port device. This is typically performed by a command such as;</p> <p><code>ln -s /dev/ttyS0 /dev/jjy0</code></p> - <p>Using RS232C to USB converter cable, the clock can be connected to an USB port instead of a serial port. In this case, typical symbolic link command is as follows; + <p>Using an RS-232C to USB converter cable, the clock or a modem can be connected to a USB port instead of a serial port. In this case, the typical symbolic link command is as follows;</p> <p><code>ln -s /dev/ttyUSB0 /dev/jjy0</code></p> <p>Windows NT does not support symbolic links to device files. COM<em>X</em>: is the unit used by the driver, based on the refclock unit number, where unit 1 corresponds to COM1: and unit 3 corresponds to COM3:</p> <h4>Monitor Data</h4> - <p>The driver writes each timecode as received to the <code>clockstats</code> file.</p> + <p>The driver writes sent and received data to/from the JJY receivers, GPS clock, and the modem into the <code>clockstats</code> file.</p> + <p><code> + statsdir /var/log/ntpd/<br> + filegen clockstats file clockstats type day enable + </code></p> + <div style="text-align:left;">Mark of the clockstats record</div> + <table border="1" summary="Clockstats"> + <tr><td><code>JJY</code> </td><td>Infomation message ( This refclock starts or stops. )</td></tr> + <tr><td><code>--></code> </td><td>Sent data</td></tr> + <tr><td><code><--</code> </td><td>Received data</td></tr> + <tr><td><code>---</code> </td><td>Infomation message</td></tr> + <tr><td><code>===</code> </td><td>Infomation message ( Start of each polling, and sync. time. )</td></tr> + <tr><td><code>-W-</code> </td><td>Warning message</td></tr> + <tr><td><code>-X-</code> </td><td>Error message</td></tr> + </table> <h4>Fudge Factors</h4> <dl> - <dt><code>time1 <em>time</em></code> - <dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0. - <dt><code>time2 <em>time</em></code> - <dd>Not used by this driver. - <dt><code>stratum <em>number</em></code> - <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0. - <dt><code>refid <em>string</em></code> - <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <code>JJY</code>. - <dt><code>flag1 0 | 1</code> - <dd>See corresponding receiver. - <dt><code>flag2 0 | 1</code> - <dd>Not used by this driver. - <dt><code>flag3 0 | 1</code> - <dd>Not used by this driver. - <dt><code>flag4 0 | 1</code> + <dt><code>time1 <em>time</em></code></dt> + <dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0.</dd> + <dt><code>time2 <em>time</em></code></dt> <dd>Not used by this driver. + <dt><code>stratum <em>number</em></code></dt> + <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0.</dd> + <dt><code>refid <em>string</em></code></dt> + <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <code>JJY</code>.</dd> + <dt><code>flag1 0 | 1</code></dt> + <dd>See corresponding receiver.</dd> + <dt><code>flag2 0 | 1</code></dt> + <dd>See corresponding receiver.</dd> + <dt><code>flag3 0 | 1</code></dt> + <dd>See corresponding receiver.</dd> + <dt><code>flag4 0 | 1</code></dt> + <dd>See corresponding receiver.</dd> </dl> <hr> <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> diff --git a/html/drivers/driver46.html b/html/drivers/driver46.html index 40aded80cca10..cdb0b6899e155 100644 --- a/html/drivers/driver46.html +++ b/html/drivers/driver46.html @@ -14,7 +14,7 @@ <body> <h3>GPSD NG client driver</h3> <p>Last update: - <!-- #BeginDate format:En2m -->1-Mar-2014 03:48<!-- #EndDate --> + <!-- #BeginDate format:En2m -->30-Apr-2015 05:53<!-- #EndDate --> UTC</p> <hr> <h4>Synopsis</h4> @@ -28,8 +28,9 @@ Features: <tt></tt> </p> - <h4>Description</h4> + <!-- --------------------------------------------------------- --> + <br><h4>Description</h4> <p> This driver is a client driver to the <i>GPSD</i> daemon, which over the time became increasingly popular for UN*Xish @@ -68,25 +69,37 @@ <p> The overall accuracy depends on the receiver used. The driver uses the error estimations (95% probability limits) provided by - <i>GPSD</i> to set the clock precision dynamically according to these - readings. + <i>GPSD</i> to set the clock precision dynamically according to + these readings. </p> <p> - The driver needs the VERSION, TPV, PPS and WATCH objects of - the <i>GPSD</i> protocol. (Others are quietly ignored.) + The driver needs the VERSION, TPV, PPS, WATCH and TOFF objects + of the <i>GPSD</i> protocol. (Others are quietly ignored.) The + driver can operate without the TOFF objects, which are available + with the <i>protocol</i> version 3.10 and above. (Not to be + confused with the <i>release</i> version of <i>GPSD</i>!) + Running without TOFF objects has a negative impact on the jitter + and offset of the serial timing information; if possible, a + version of <i>GPSD</i> with support for TOFF objects should be + used. + </p> + <p>The acronym <u>STI</u> is used here as a synonym for <i>serial + time information</i> from the data channel of the receiver, no + matter what objects were used to obtain it. </p> + <!-- --------------------------------------------------------- --> - <h4>Naming a Device</h4> + <br><h4>Naming a Device</h4> <p> - The <i>GPSD</i> driver uses the same name as the NMEA driver, - namely <tt>/dev/gps<i>u</i></tt>. There is a simple reason for - that: While the NMEA driver and the <i>GPSD</i> driver can be - active at the same time <b>for different devices</b>, - they cannot access the same device at a time. Having the same - name helps on that. It also eases migration from using NMEA - directly to using <i>GPSD</i>, as no new links etc need to be - created. + The <i>GPSD</i> driver uses the same device name as the NMEA + driver, namely <tt>/dev/gps<i>u</i></tt>. There is a simple + reason for that: While the NMEA driver and the <i>GPSD</i> + driver can be active at the same time <b>for different + devices</b>, they cannot access the same device at a + time. Having the same name helps on that. It also eases + migration from using NMEA directly to using <i>GPSD</i>, as no + new links etc need to be created. </p> <p> <i>GPSD</i> is normally started with the device name to access; @@ -97,14 +110,16 @@ identification. This makes the migration from the built-in NMEA driver a bit easier. </p> - <p><b>Note:</b> <i>GPSD</i> (as of version 3.10) cannot - use kernel mode PPS on devices that are hot-plugged. This would - require to attach the PPS line discipline to the file, which is - not possible when running with root privileges dropped. This is - not likely to change in the future. + <p><b>Note:</b> <i>GPSD</i> (as of version 3.10) cannot use kernel + mode PPS on devices that are hot-plugged. This would require to + attach the PPS line discipline to the character special file, + which is not possible when running with root privileges already + dropped. This is not likely to change in the future. </p> - <h4>The 'mode' byte</h4> + <!-- --------------------------------------------------------- --> + + <br><h4>The 'mode' word</h4> <p> A few operation modes can be selected with the mode word. </p> @@ -113,70 +128,234 @@ <th colspan="3">The Mode Word</th> <tr> <td>Bits</td><td>Value</td><td>Description</td> </tr> - <tr> <td rowspan="4"align="center">0..1</td><td align="center">0</td> - <td>Uses TPV to get absolute time stamps for full - synchronization. If PPS is available , it is used to improve - the precision, but the clock can work without it.</td> + <tr> <td rowspan="4"align="center">0..1</td> + <td align="center">0</td> + <td>STI only operation. This mode is affected by the timing + stability of whatever protocol is used between the GPS + device and GPSD. + <br> + Running on STI only is not recommended in general. Possible + use cases include: + <ul> + <li>The receiver does not provide a PPS signal. + <li>The receiver <i>does</i> provide a PPS signal and + the secondary PPS unit is used. + <li>The receiver has a stable serial timing and a proper + fudge can be established. + <li>You have other time sources available and want to + establish a useful fudge value for <tt>time2</tt>. + </ul> + </td> </tr> - <tr><td align="center">1</td> - <td>Require TPV <b>and</b> PPS to work.</td> + <tr> + <td align="center">1</td> + <td>Strict operation. This mode needs a valid PPS and a + valid STI to combine the absolute time from the STI with + the time stamp from the PPS record. Does not feed clock + samples if no valid PPS+STI pair is available. + <br><br> + This type of operation results in an ordinary clock with a + very low jitter as long as the PPS data is available, but + the clock fails once PPS drops out. This mode is a + possible choice for receivers that provide a PPS signal + most of the time but have an unstable serial timing that + cannot be fudge-compensated. + </td> </tr> <tr><td align="center">2</td> - <td>Ignore PPS data, run on TPV only. This is not a - recommended mode unless the serial timing is very stable - and GPSD provides an information element in TPV that - indicates the receive time of the fix data.</td> + <td>Automatic mode. Tries to operate in strict mode unless + it fails to process valid samples for some time, currently + 120s. Then it reverts to STI-only operation until the PPS + is stable again for 40s, when strict mode is engaged + again. + <br><br><b>Important Notice: This is an expiremental + feature!</b><br> Switching between strict and STI-only + mode will cause changes in offset and jitter. Use this + mode only if STI-only works fairly well with your setup, + or if you expect longer dropouts of the PPS signal and + prefer to use STI alone over not getting synchronised at + all.</td> + </tr> + <tr> + <td align="center">3</td> + <td><i>(reserved for future extension, do not use)</i></td> </tr> - <tr><td align="center">3</td> - <td>PPS-only mode. Ignores TPV and does only the PPS phase - correction. This means that some other source must get NTPD - close to synchronisation; only after that happened and the - phase shift between the system clock and the PPS pulse is - less than 125msec the PPS lock will be engaged.</td> + <tr> + <td align="center">2..31</td> + <td colspan="2"><i>(reserved for future extension, do not + use)</i></td> </tr> - <tf colspan="3"><b>IMPORTANT: work in progress, mode - word ignored right now. Fixed mode '0' operation.</b></tf> </table> </p> - <h4>Syslog flood throttle</h4> + <!-- --------------------------------------------------------- --> + + <br><h4>Syslog flood throttle</h4> <p>This driver can create a lot of syslog messages when things go - wrong, and cluttering the log files is frowned upon. So we attempt - to log persistent or recurring errors only once per hour. On the - other hand, when tracking a problem the syslog flood throttle can - get into the way.</p> + wrong, and cluttering the log files is frowned upon. So we + attempt to log persistent or recurring errors only once per + hour. On the other hand, when tracking a problem the syslog + flood throttle can get into the way.</p> <p>Therefore, fudge <i>flag3</i> can be used to <i>disable</i> the - flood throttle at any time; the throttle is engaged by - default. Running with the syslog flood throttle disabled for - lengthy time is not recommended unless the log files are closely - monitored.</p> + flood throttle at any time; the throttle is engaged by + default. Running with the syslog flood throttle disabled for + lengthy time is not recommended unless the log files are closely + monitored.</p> + + <!-- --------------------------------------------------------- --> + + <br><h4>PPS secondary clock unit</h4> + <p>Units with numbers ≥128 act as secondary clock unit for the + primary clock unit (u mod 128). A secondary unit processes only + the PPS data from <i>GPSD</i> and needs the corresponding master + unit to work<a href="#fn1" name="fn1bl"><sup>1</sup></a>. Use + the 'noselect' keyword on the primary unit if you are not + interested in its data. + </p><p>The secondary unit employs the usual precautions before + feeding clock samples:</p> + <ul> + <li>The system must be already in a synchronised state. + <li>The system offset must be less than 400ms absolute. + <li>The phase adjustment from the PPS signal must also be less + than 400ms absolute. + </ul> + <p>If fudge flag <tt>flag1</tt> is set for the secondary unit, the + unit asserts the PPS flag on the clock as long as PPS data is + available. This makes the unit eligible as PPS peer and should + only be used if the GPS receiver can be trusted for the quality + of its PPS signal<a href="fn2" + name="fn2bl"><sup>2</sup></a>. The PPS flag gets cleared if no + PPS records can be aquired for some time. The unit also flushes + the sample buffer at this point to avoid the use of stale PPS + data.</p> + <p><b>Attention:</b> This unit uses its own PPS fudge value + which must be set as fudge <tt>time1</tt>. Only the fudge + values <tt>time1</tt> and <tt>flag1</tt> have an impact on secondary + units.</p> + + <!-- --------------------------------------------------------- --> + + <br><h4>Clockstats</h4> + <p>If flag4 is set when the driver is polled, a clockstats record + is written for the primary clock unit. (The secondary PPS unit + does not provide clock stats on its own.) The first 3 fields are + the normal date, time, and IP address common to all clockstats + records. + </p><p> + <table border="1" frame="box" rules="all"> + <th colspan="2">The Clockstats Line</th> + <tr> <td>field</td><td>Description</td> </tr> + <tr> + <td align="center">1</td> + <td>Date as day number since NTP epoch.</td> + </tr><tr> + <td align="center">2</td> + <td>Time as seconds since midnight.</td> + </tr><tr> + <td align="center">3</td> + <td>(Pseudo-) IP address of clock unit.</td> + </tr><tr> + <td align="center">4</td> + <td>Number of received known JSON records since last + poll. The driver knows about TPV, PPS, TOFF, VERSION and + WATCH records; others are silently ignored. + </td> + </tr><tr> + <td align="center">5</td> + <td>Bad replies since last poll. A record is considered + malformed or a bad reply when it is missing vital fields + or the fields contain malformed data that cannot be + parsed. + </td> + </tr><tr> + <td align="center">6</td> + <td>Number of sample cycles since last poll that were + discarded because there was no GPS fix. This is + effectively the number of TPV records with a fix value + < 2 or without a time stamp. + </td> + </tr><tr> + <td align="center">7</td> + <td>Number of serial time information records (TPV or TOFF, + depending on the GPSD version) received since last poll. + </td> + </tr><tr> + <td align="center">8</td> + <td>Number of serial time information records used for + clock samples since the last poll. + </td> + </tr><tr> + <td align="center">9</td> + <td>Number of PPS records received since the last poll.</td> + </tr><tr> + <td align="center">10</td> + <td>Number of PPS records used for clock samples on the + secondary channel since the last poll. + </td> + </tr> + </table> + </p> - <h4>Fudge Factors</h4> + <!-- --------------------------------------------------------- --> + + <br><h4>Fudge Factors</h4> <dl> <dt><tt>time1 <i>time</i></tt></dt> <dd>Specifies the PPS time offset calibration factor, in seconds and fraction, with default 0.0.</dd> <dt><a name="fudgetime2"><tt>time2 <i>time</i></tt></a></dt> - <dd>Specifies the TPV time offset calibration factor, in seconds - and fraction, with default 0.0.</dd> + <dd><em>[Primary Unit]</em> Specifies the TPV/TIME time offset + calibration factor, in seconds and fraction, with default + 0.0.</dd> <dt><tt>stratum <i>number</i></tt></dt> - <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0.</dd> + <dd>Specifies the driver stratum, in decimal from 0 to 15, with + default 0.</dd> <dt><tt>refid <i>string</i></tt></dt> <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <tt>GPSD</tt>.</dd> - <dt><tt>flag1 0 | 1</tt></dt><dd><i>(not used)</i></dd> - <dt><tt>flag2 0 | 1</tt></dt><dd><i>(not used)</i></dd> - <dt><tt>flag3 0 | 1</tt></dt><dd>If set, <i>disable</i> the - log throttle. Useful when tracking problems in the interaction - between <i>GPSD</i> and <i>NTPD</i>, since now all error - events are logged. Persistent/recurrent errors can easily fill - up the log, so this should only be enabled during bug - hunts.</dd> - <dt><tt>flag4 0 | 1</tt></dt><dd>If set, write a clock stats - line on every poll cycle.</dd> + <dt><tt>flag1 0 | 1</tt></dt><dd><em>[<b>Secondary</b> + Unit]</em> When set, flags the secondary clock unit as a + potential PPS peer as long as good PPS data is available. + </dd> + <dt><tt>flag2 0 | 1</tt></dt> + <dd><em>[Primary Unit]</em> When set, <u>disables</u> the + processing of incoming PPS records. Intended as an aide to + test the effects of a PPS dropout when using automatic mode + (mode 2). + </dd> + <dt><tt>flag3 0 | 1</tt></dt><dd><em>[Primary Unit]</em> + If set, <u>disables</u> the log throttle. Useful when tracking + problems in the interaction between <i>GPSD</i> and <i>NTPD</i>, + since now all error events are logged. Persistent/recurrent + errors can easily fill up the log, so this should only be + enabled during bug hunts.</dd> + <dt><tt>flag4 0 | 1</tt></dt><dd><em>[Primary Unit]</em> + If set, write a clock stats line on every poll cycle. + </dd> </dl> + <!-- -- footnotes -------------------------------------------- --> + + <hr> + <p><a name="fn1" href="#fn1bl"><sup>1</sup>) </a>Data transmission + an decoding is done only once by the primary unit. The decoded + data is then processed independently in both clock units. This + avoids double transmission over two sockets and decoding the + same data twice, but the primary unit is always needed as a + downside of this approach. + </p> + <p><a name="fn2" href="#fn2bl"><sup>2</sup>) </a>The clock driver + suppresses the processing PPS records when the TPV/TIME data + indicates the receiver has no fix. It can also deal with + situations where the PPS signal is not delivered + to <i>GPSD</i>. But once it is available, it is also processed + and used to create samples. If a receiver cannot be trusted for + the precision of its PPS signal, it should not be used to create + a possible PPS peer: These get extra clout and can effectively + become the sole source of input for the control loop. You do not + want to use sloppy data for that. + <hr> <p>Additional Information</p> <p><a href="../refclock.html">Reference Clock Drivers</a></p> <hr> diff --git a/html/miscopt.html b/html/miscopt.html index 5750d17999d57..ac32419df08a8 100644 --- a/html/miscopt.html +++ b/html/miscopt.html @@ -3,6 +3,7 @@ <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <title>Miscellaneous Commands and Options</title> +<!-- Changed by: Harlan Stenn, 29-Jun-2015 --> <link href="scripts/style.css" type="text/css" rel="stylesheet"> </head> <body> @@ -10,7 +11,7 @@ <img src="pic/boom3.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/~mills/pictures.html">from <i>Pogo</i>, Walt Kelly</a> <p>We have three, now looking for more.</p> <p>Last update: - <!-- #BeginDate format:En2m -->28-Feb-2015 12:01<!-- #EndDate --> + <!-- #BeginDate format:En2m -->29-Jun-2015 05:56<!-- #EndDate --> UTC</p> <br clear="left"> <h4>Related Links</h4> @@ -26,6 +27,8 @@ <dd>This command specifies the complete path and name of the file used to record the frequency of the local clock oscillator. This is the same operation as the <tt>-f</tt> command line option. This command is mutually exclusive with the <tt>freq</tt> option of the <tt>tinker</tt> command.</dd> <dd> If the file exists, it is read at startup in order to set the initial frequency and then updated once per hour or more with the current frequency computed by the daemon. If the file name is specified, but the file itself does not exist, the starts with an initial frequency of zero and creates the file when writing it for the first time. If this command is not given, the daemon will always start with an initial frequency of zero.</dd> <dd>The file format consists of a single line containing a single floating point number, which records the frequency offset measured in parts-per-million (PPM). The file is updated by first writing the current drift value into a temporary file and then renaming this file to replace the old version.</dd> + <dt id="dscp"><tt>dscp <i>dscp</i></tt></dt> + <dd>This command specifies the Differentiated Services Code Point (DSCP) value that is used in sent NTP packets. The default value is 46 for Expedited Forwarding (EF).</dd> <dt id="enable"><tt>enable [auth | bclient | calibrate | kernel | mode7 | monitor | ntp | stats]</tt><br> <tt>disable [auth | bclient | calibrate | kernel | mode7 | monitor | ntp | stats]</tt></dt> <dd>Provides a way to enable or disable various system options. Flags not mentioned are unaffected. Note that most of these flags can be modified remotely using <a href="ntpq.html"><tt>ntpq</tt></a> utility program's <tt>:config</tt> and <tt>config-from-file</tt> commands. @@ -57,6 +60,8 @@ <dd>This command loads the NIST leapseconds file and initializes the leapsecond values for the next leapsecond time, expiration time and TAI offset. The file can be obtained directly from NIST national time servers using <tt>ftp</tt> as the ASCII file <tt>pub/leap-seconds</tt>.</dd> <dd>The <i>leapfile</i> is scanned when <tt>ntpd</tt> processes the <tt>leapfile</tt> directive or when <tt>ntpd</tt> detects that <i>leapfile</i> has changed. <tt>ntpd</tt> checks once a day to see if the <i>leapfile</i> has changed.</dd> <dd>While not strictly a security function, the Autokey protocol provides means to securely retrieve the current or updated leapsecond values from a server.</dd> + <dt id="leapsmearinterval"><tt>leapsmearinterval <i>seconds</i></tt></dt> + <dd>This EXPERIMENTAL option is only available if <tt>ntpd</tt> was built with the <tt>--enable-leap-smear</tt> option to the <tt>configure</tt> script. It specifies the interval over which a leap second correction will be applied. Recommended values for this option are between 7200 (2 hours) and 86400 (24 hours). <b>DO NOT USE THIS OPTION ON PUBLIC-ACCESS SERVERS!</b> See http://bugs.ntp.org/2855 for more information.</dd> <dt id="logconfig"><tt>logconfig <i>configkeyword</i></tt></dt> <dd>This command controls the amount and type of output written to the system <tt>syslog</tt> facility or the alternate <tt>logfile</tt> log file. All <i><tt>configkeyword</tt></i> keywords can be prefixed with <tt>=</tt>, <tt>+</tt> and <tt>-</tt>, where <tt>=</tt> sets the <tt>syslogmask</tt>, <tt>+</tt> adds and <tt>-</tt> removes messages. <tt>syslog messages</tt> can be controlled in four classes (<tt>clock</tt>, <tt>peer</tt>, <tt>sys</tt> and <tt>sync</tt>). Within these classes four types of messages can be controlled: informational messages (<tt>info</tt>), event messages (<tt>events</tt>), statistics messages (<tt>statistics</tt>) and status messages (<tt>status</tt>).</dd> <dd>Configuration keywords are formed by concatenating the message class with the event class. The <tt>all</tt> prefix can be used instead of a message class. A message class may also be followed by the <tt>all</tt> keyword to enable/disable all messages of the respective message class. By default, <tt>logconfig</tt> output is set to <tt>allsync</tt>.</dd> @@ -95,6 +100,18 @@ <dd>This command is used in conjunction with the ACTS modem driver (type 18). The arguments consist of a maximum of 10 telephone numbers used to dial USNO, NIST or European time services. The Hayes command ATDT is normally prepended to the number, which can contain other modem control codes as well.</dd> <dt id="reset"><tt>reset [allpeers] [auth] [ctl] [io] [mem] [sys] [timer]</tt></dt> <dd>Reset one or more groups of counters maintained by ntpd and exposed by <tt>ntpq</tt> and <tt>ntpdc</tt>.</dd> + <dt id="rlimit"><tt>rlimit [memlock <i>Nmegabytes</i> | stacksize <i>N4kPages</i> | filenum <i>Nfiledescriptors</i>]</tt></dt> + <dd>This command alters certain process storage allocation limits, and is only available on some operating systems. Options are as follows:</dd> + <dd> + <dl> + <dt><tt>memlock <i>Nmegabytes</i></tt></dt> + <dd>Specify the number of megabytes of memory that can be allocated. Probably only available under Linux, this option is useful when dropping root (the <tt>-i</tt> option). The default is 32 megabytes. Setting this to zero will prevent any attemp to lock memory.</dd> + <dt><tt>stacksize <i>N4kPages</i></tt></dt> + <dd>Specifies the maximum size of the process stack on systems with the <tt>mlockall()</tt> function. Defaults to 50 4k pages (200 4k pages in OpenBSD).</dd> + <dt><tt>filenum <i>Nfiledescriptors</i></tt></dt> + <dd>Specifies the maximum number of file descriptors ntp may have open at the same time. Defaults to system default.</dd> + </dl> + </dd> <dt id="saveconfigdir"><tt>saveconfigdir <i>directory_path</i></tt></dt> <dd>Specify the directory in which to write configuration snapshots requested with <tt>ntpq</tt>'s <a href="ntpq.html#saveconfig">saveconfig</a> command. If <tt>saveconfigdir</tt> does not appear in the configuration file, saveconfig requests are rejected by ntpd.</dd> <dt id="setvar"><tt>setvar <i>variable</i> [default]</tt></dt> @@ -120,18 +137,6 @@ <dd>Specifies the stepout threshold in seconds. The default without this command is 300 s. Since this option also affects the training and startup intervals, it should not be set less than the default. Further details are on the <a href="clock.html">Clock State Machine</a> page.</dd> </dl> </dd> - <dt id="rlimit"><tt>rlimit [memlock <i>Nmegabytes</i> | stacksize <i>N4kPages</i> | filenum <i>Nfiledescriptors</i>]</tt></dt> - <dd>This command alters certain process storage allocation limits, and is only available on some operating systems. Options are as follows:</dd> - <dd> - <dl> - <dt><tt>memlock <i>Nmegabytes</i></tt></dt> - <dd>Specify the number of megabytes of memory that can be allocated. Probably only available under Linux, this option is useful when dropping root (the <tt>-i</tt> option). The default is 32 megabytes. Setting this to zero will prevent any attemp to lock memory.</dd> - <dt><tt>stacksize <i>N4kPages</i></tt></dt> - <dd>Specifies the maximum size of the process stack on systems with the <tt>mlockall()</tt> function. Defaults to 50 4k pages (200 4k pages in OpenBSD).</dd> - <dt><tt>filenum <i>Nfiledescriptors</i></tt></dt> - <dd>Specifies the maximum number of file descriptors ntp may have open at the same time. Defaults to system default.</dd> - </dl> - </dd> <dt id="tos"><tt>tos [beacon <i>beacon</i> | ceiling <i>ceiling</i> | cohort {0 | 1} | floor <i>floor</i> | maxclock <i>maxclock </i>| maxdist <i>maxdist</i> | minclock <i>minclock</i> | mindist <i>mindist </i>| minsane <i>minsane</i> | orphan <i>stratum</i> | orphanwait <em>delay</em>]</tt></dt> <dd>This command alters certain system variables used by the the clock selection and clustering algorithms. The default values of these variables have been carefully optimized for a wide range of network speeds and reliability expectations. Very rarely is it necessary to change the default values; but, some folks can't resist twisting the knobs. It can be used to select the quality and quantity of peers used to synchronize the system clock and is most useful in dynamic server discovery schemes. The options are as follows:</dd> <dd> diff --git a/html/refclock.html b/html/refclock.html index d8969e38cbc3b..46d4908fd8d52 100644 --- a/html/refclock.html +++ b/html/refclock.html @@ -28,7 +28,7 @@ <p>NTP Version 4 supports almost four dozen satellite, radio and telephone modem reference clocks plus several audio devices for instrumentation signals. A general description of the reference clock support is on this page. Additional information about each reference clock driver can be found via links from this page. Additional information is on the <a href="rdebug.html">Debugging Hints for Reference Clock Drivers</a> and <a href="howto.html">How To Write a Reference Clock Driver</a> pages. Information on how to support pulse-per-second (PPS) signals produced by some devices is on the <a href="pps.html">Pulse-per-second (PPS) Signal Interfacing</a> page. All reference clock drivers require that the reference clock use only Coordinated Universal Time (UTC). Timezone and standard/daylight adjustments are performed by the operating system kernel.</p> <p>A reference clock will generally (though not always) be a radio timecode receiver synchronized to standard time as provided by NIST and USNO in the US, NRC in Canada and their counterparts elsewhere in the world. A device driver specific to each reference clock must be compiled in the distribution; however, most common radio, satellite and telephone modem clocks are included by default and are activated by configuration commands.</p> <p>Reference clocks are supported in the same way as ordinary NTP clients and use the same filter, select, cluster and combine algorithms. Drivers have addresses in the form 127.127.<i>t.u</i>, where <i>t</i> is the driver type and <i>u</i> is a unit number in the range 0-3 to distinguish multiple instances of the same driver. The connection to the computer is device dependent, usually a serial port, parallel port or special bus peripheral, but some can work directly from an audio codec or sound card. The particular device is specified by adding a soft link from the name used by the driver to the particular device name.</p> -<p>The <tt>server</tt> command is used to configure a reference clock. Only the <tt>mode>,<tt>minpoll</tt>, <tt>maxpoll</tt>, and <tt>prefer</tt> options are supported for reference clocks, as described on the <a href="clockopt.html">Reference Clock Commands</a> page. The <tt>prefer</tt> option is discussed on the <a href="prefer.html">Mitigation Rules and the <tt>prefer</tt> Keyword</a> page. Some of these options have meaning only for selected clock drivers.</p> +<p>The <tt>server</tt> command is used to configure a reference clock. Only the <tt>mode</tt>, <tt>minpoll</tt>, <tt>maxpoll</tt>, and <tt>prefer</tt> options are supported for reference clocks, as described on the <a href="clockopt.html">Reference Clock Commands</a> page. The <tt>prefer</tt> option is discussed on the <a href="prefer.html">Mitigation Rules and the <tt>prefer</tt> Keyword</a> page. Some of these options have meaning only for selected clock drivers.</p> <p>The <tt>fudge</tt> command can be used to provide additional information for individual drivers and normally follows immediately after the <tt>server</tt> command. The reference clock stratum is by default 0, so that the server stratum appears to clients as 1. The <tt>stratum</tt> option can be used to set the stratum to any value in the range 0 through 15. The <tt>refid</tt> option can be used to change the reference identifier, as might in the case when the driver is disciplined by a pulse-per-second (PPS) source. The device-dependent <tt>mode</tt>, <tt>time</tt> and <tt>flag</tt> options can provide additional driver customization.</p> <h4 id="spec">Special Considerations</h4> <p>The <a href="audio.html">Audio Drivers</a> page describes three software drivers that process audio signals from an audio codec or sound card. One is for the NIST time and frequency stations WWV and WWVH, another for the Canadian time and frequency station CHU. These require an external shortwave radio and antenna. A third is for the generic IRIG signal produced by some timing devices. Currently, these are supported in FreeBSD, Solaris and SunOS and likely in other system as well.</p> |