Lines Matching +full:multi +full:- +full:tt
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
3 …<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"><title>Generic NMEA GPS Rec…
4 <!-- Changed by: Pearly &, 04-Feb-2019 -->
7 table.dlstable { font-size:85%; }
8 td.ttf{ font-family:Courier; font-weight:bold; }
16 <!-- #BeginDate format:En2m -->17-Oct-2020 16:00<!-- #EndDate -->
23 Reference ID: <tt>GPS</tt><br>
24 Driver ID: <tt>GPS_NMEA</tt><br>
25 Serial Port: <tt>/dev/gps<i>u</i></tt>; 4800 - 115200 bps, 8-bits, no parity<br>
26 Serial Port: <tt>/dev/gpspps<i>u</i></tt>; for just the PPS signal (this
27 is tried first for PPS, before <tt>/dev/gps<i>u</i></tt>)<br>
28 Serial Port: <tt>/dev/gps<i>u</i></tt>; symlink to server:port (for nmead)<br>
29 Features: <tt>tty_clk</tt>
36 the <tt>$GPRMC</tt>, <tt>$GPGLL</tt>, <tt>$GPGGA</tt>, <tt>$GPZDA</tt>
37 and <tt>$GPZDG</tt> NMEA sentences by default. Note that Accord's
38 custom NMEA sentence <tt>$GPZDG</tt> reports using the GPS timescale,
43 once <tt>$GPZDG</tt> is received.
46 IDs</a> when using non-GPS or multi-system receivers.
114 <td>Day of the month (1-31)</td>
168 <td>Month of the year (1-12)</td>
186 <td>GPS week (0-1023)</td>
189 <td>Seconds since start of week (0-604799)</td>
200 '1' => accuracy of +/- 20ms,<br>
201 '2' => accuracy of +/- 100ns</td>
217 can emit <tt>$GPRMC</tt> (GPS), <tt>$GLRMC</tt> (GLONASS),
218 <tt>$GARMC</tt> (Galileo), <tt>$GNRMC</tt> (generic/combined) and others
224 it is.) So whenever <tt>$GPRMC</tt> is mentioned in this document,
225 substitute any possible talker ID your receiver might emit -- it will
228 This approach has a drawback. It is easy to use for single-system
229 receivers, but it cannot separate the data streams for multi-system
233 quality to the receiver; the driver is not able to cherry-pick the best
237 combined data, which usually has the <tt>GN</tt> talker ID defined by
246 the 'mode' in the server configuration line:<br> <tt>server
247 127.127.20.x mode X</tt>
263 <td>process <tt>$GPRMC</tt></td>
268 <td>process <tt>$GPGGA</tt></td>
273 <td>process <tt>$GPGLL</tt></td>
278 <td>process <tt>$GPZDA</tt> or <tt>$GPZDG</tt></td>
280 <td rowspan="6" align="center">4-6</td>
308 <td>Write the sub-second fraction of the receive time stamp to the
318 <td>process <tt>$PGRMF</tt></td>
323 <td>process <tt>$PUBX,04</tt></td>
325 <td align="center">10-15</td>
328 <td>reserved - leave 0</td>
359 with a good hold-over characteristic, but most likely
391 1-second cycle at 4800 bps, but high-speed high-volume NMEA data is likely
395 data only, e.g. one <tt>$GPRMC</tt> or <tt>$GPZDA</tt> per second, at a
407 by default reduced to GPS time again and then (re-)mapped according to the
425 clockstats file and available with <code>ntpq -c clockvar</code>.
434 56299 76876.691 127.127.20.20 $GPGGA,212116.000,3726.0785,N,12212.2605,W,1,05,2.0,17.0,M,-25.7,M,,0…
504 <h4>Setting up the Garmin GPS-25XL</h4>
518 <dt><tt>time1 <i>time</i></tt></dt>
520 <dt><a name="fudgetime2"><tt>time2 <i>time</i></tt></a></dt>
523 <dt><tt>stratum <i>number</i></tt></dt>
525 <dt><tt>refid <i>string</i></tt></dt>
527 default <tt>GPS</tt>.</dd>
528 <dt><tt>flag1 0 | 1</tt></dt>
530 <dt><tt>flag2 0 | 1</tt></dt>
533 <dt><tt>flag3 0 | 1</tt></dt>
534 …<dd>If PPS signal processing is enabled, use the <tt>ntpd</tt> clock discipline if 0 (default); us…
536 <dt><tt>flag4 0 | 1</tt></dt>
541 <p><tt>flag1</tt>, <tt>flag2</tt>, and <tt>flag3</tt> are ignored under Windows.</p>