Lines Matching +full:secondary +full:- +full:device
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
3 <meta http-equiv="Content-Type"
4 content="text/html;charset=iso-8859-1"><title>GPSD-NG client driver</title>
8 table.dlstable { font-size:85%; }
9 td.ttf{ font-family:Courier; font-weight:bold; }
17 <!-- #BeginDate format:En2m -->30-Apr-2015 05:53<!-- #EndDate -->
27 device (not used directly; see below)<br>
31 <!-- --------------------------------------------------------- -->
39 applications. <i>GPSD</i> can also auto-detect and handle PPS
46 using a GPS device with PPS support.</b>
49 The GPSD-NG protocol is text based, using JSON notation to
53 device <tt>/dev/gps<i>u</i></tt> to be watched. (Different clock
60 clock device to be present <i>a priori</i>; it will try to
61 re-establish a lost or hitherto unsuccessful connection and will
62 wait for device to come up in <i>GPSD.</i> There is an initial
91 <!-- --------------------------------------------------------- -->
93 <br><h4>Naming a Device</h4>
95 By default, the <i>GPSD</i> driver uses the same device name as
99 different devices</b>, they cannot access the same device at a
105 <i>GPSD</i> is normally started with the device name to access;
106 it can also be instructed by hot-plug scripts to add or remove
107 devices from its device pool. Luckily, the symlinks used by the
109 makes it possible to use the symlink names as device
110 identification. This makes the migration from the built-in NMEA
114 The driver also honors <tt>device</tt> statements for
118 and <i>NTPD</i>: Simply name the device as it was given
122 mode PPS on devices that are hot-plugged or activated on demand.
124 at <i>GPSD</i>'s <tt>-n</tt> (<i>nowait</i>) option.
127 <!-- --------------------------------------------------------- -->
142 device and GPSD.
149 the secondary PPS unit is used.
169 cannot be fudge-compensated.
175 120s. Then it reverts to STI-only operation until the PPS
179 feature!</b><br> Switching between strict and STI-only
181 mode only if STI-only works fairly well with your setup,
198 <!-- --------------------------------------------------------- -->
212 <!-- --------------------------------------------------------- -->
214 <br><h4>PPS secondary clock unit</h4>
215 <p>Units with numbers ≥128 act as secondary clock unit for the
216 primary clock unit (u mod 128). A secondary unit processes only
221 </p><p>The secondary unit employs the usual precautions before
229 <p>If fudge flag <tt>flag1</tt> is set for the secondary unit, the
240 values <tt>time1</tt> and <tt>flag1</tt> have an impact on secondary
243 <!-- --------------------------------------------------------- -->
247 is written for the primary clock unit. (The secondary PPS unit
263 <td>(Pseudo-) IP address of clock unit.</td>
300 secondary channel since the last poll.
306 <!-- --------------------------------------------------------- -->
324 <dt><tt>flag1 0 | 1</tt></dt><dd><em>[<b>Secondary</b>
325 Unit]</em> When set, flags the secondary clock unit as a
345 <!-- -- footnotes -------------------------------------------- -->