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>Hewlett Packard 58503A GPS Receiver and HP Z3801A</title> 9 <link href="scripts/style.css" type="text/css" rel="stylesheet"> 10 </head> 11 12 <body> 13 <h3>Hewlett Packard 58503A GPS Receiver and HP Z3801A</h3> 14 <hr> 15 <h4>Synopsis</h4> 16 <p>Address: 127.127.26.<i>u</i><br> 17 Reference ID: <tt>GPS</tt><br> 18 Driver ID: <tt>GPS_HP</tt><br> 19 Serial Port: <tt>/dev/hpgps<i>u</i></tt>; 9600 baud, 8-bits, no parity, 19200 baud 7-bits, odd parity for the HP Z3801A</p> 20 <h4>Description</h4> 21 <p>This driver supports the HP 58503A Time and Frequency Reference Receiver and HP Z3801A GPS Receiver. They use HP SmartClock (TM) to implement an Enhanced GPS receiver. The receiver accuracy when locked to GPS in normal operation is better than 1 usec. The accuracy when operating in holdover is typically better than 10 us per day. It receiver should be operated with factory default settings. Initial driver operation: expects the receiver to be already locked to GPS, configured and able to output timecode format 2 messages.</p> 22 <p>The driver uses the poll sequence <tt>:PTIME:TCODE?</tt> to get a response from the receiver. The receiver responds with a timecode string of ASCII printing characters, followed by a <cr><lf>, followed by a prompt string issued by the receiver, in the following format:</p> 23 <pre>T#yyyymmddhhmmssMFLRVcc<cr><lf>scpi ></pre> 24 The driver processes the response at the <cr> and <lf>, so what the driver sees is the prompt from the previous poll, followed by this timecode. The prompt from the current poll is (usually) left unread until the next poll. So (except on the very first poll) the driver sees this: 25 <pre>scpi >T#yyyymmddhhmmssMFLRVcc<cr><lf></pre> 26 <p>The T is the on-time character, at 980 msec. before the next 1PPS edge. The # is the timecode format type. We look for format 2. Without any of the CLK or PPS stuff, then, the receiver buffer timestamp at the <cr> is 24 characters later, which is about 25 msec. at 9600 bps, so the first approximation for fudge time1 is nominally -0.955 seconds. This number probably needs adjusting for each machine / OS type, so far: -0.955000 on an HP 9000 Model 712/80 HP-UX 9.05 -0.953175 on an HP 9000 Model 370 HP-UX 9.10</p> 27This driver will probably work with the 58503B and 59551A if they are setup appropriately.<P> 28To use an HP Z3801A, specify <tt>mode 1</tt> on the server config line to setup the right line paramters.<P> 29The timekeeping portion of HP's business has been sold to <a href="http://www.symmetricom.com/">Symmetricom</a>.<P> 30 <h4>Fudge Factors</h4> 31 <dl> 32 <dt><tt>time1 <i>time</i></tt> 33 <dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0. 34 <dt><tt>time2 <i>time</i></tt> 35 <dd>Not used by this driver. 36 <dt><tt>stratum <i>number</i></tt> 37 <dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0. 38 <dt><tt>refid <i>string</i></tt> 39 <dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <tt>GPS</tt>. 40 <dt><tt>flag1 0 | 1</tt> 41 <dd>Not used by this driver. 42 <dt><tt>flag2 0 | 1</tt> 43 <dd>Not used by this driver. 44 <dt><tt>flag3 0 | 1</tt> 45 <dd>Not used by this driver. 46 <dt><tt>flag4 0 | 1</tt> 47 <dd>Not used by this driver. 48 </dl> 49 <hr> 50 <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> 51 </body> 52 53</html> 54