PageRenderTime 25ms CodeModel.GetById 19ms app.highlight 3ms RepoModel.GetById 0ms app.codeStats 0ms

HTML | 83 lines | 79 code | 4 blank | 0 comment | 0 complexity | ba33cc804c22f2d748b95cbfcaea0169 MD5 | raw file
Possible License(s): MPL-2.0-no-copyleft-exception, BSD-3-Clause, LGPL-2.0, LGPL-2.1, BSD-2-Clause, 0BSD, JSON, AGPL-1.0, GPL-2.0
 1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 5	<head>
 6		<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
 7		<meta name="GENERATOR" content="Mozilla/4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) [Netscape]">
 8		<title>Motorola Oncore GPS Receiver</title>
 9		<link href="scripts/style.css" type="text/css" rel="stylesheet">
10	</head>
12	<body>
13		<h3>Motorola Oncore GPS receiver</h3>
14		<hr>
15		<h4>Synopsis</h4>
16		<p>Address: 127.127.30.<i>u</i><br>
17			Reference ID: <tt>GPS</tt><br>
18			Driver ID: ONCORE<br>
19			Serial Port: <tt>/dev/oncore.serial.</tt><i>u</i>; &nbsp;9600 baud, 8-bits, no parity.<br>
20			PPS Port: <tt>/dev/oncore.pps.</tt><i>u</i>;&nbsp; <tt>PPS_CAPTUREASSERT</tt> required,&nbsp; <tt>PPS_OFFSETASSERT</tt> supported.<br>
21			Configuration File: <tt>ntp.oncore</tt>, or <tt>ntp.oncore.</tt><i>u</i>, or <tt>ntp.oncore</tt><i>u</i>, in <tt>/etc/ntp</tt> or <tt>/etc</tt>.</p>
22		<h4>Description</h4>
23		<p>This driver supports most models of the <a href="">Motorola Oncore GPS receivers</a> (Basic, PVT6, VP, UT, UT+, GT, GT+, SL, M12, M12+T), as long as they support the <i>Motorola Binary Protocol</i>.</p>
24		<p>The interesting versions of the Oncore are the VP, the UT+, the &quot;Remote&quot; which is a prepackaged UT+, and the M12 Timing. The VP is no longer available new, and the UT, GT, and SL are at end-of-life. The Motorola evaluation kit can be recommended. It interfaces to a PC straightaway, using the serial (DCD) or parallel port for PPS input and packs the receiver in a nice and sturdy box. Less expensive interface kits are available from <a href="">TAPR</a> and <a href="">Synergy</a>.<br>&nbsp;</p>
25		<center>
26			<table>
27				<tr>
28					<td><img src="../pic/oncore_utplusbig.gif" alt="gif" height="124" width="210"></td>
29					<td><img src="../pic/oncore_evalbig.gif" alt="gif" height="124" width="182"></td>
30					<td><img src="../pic/oncore_remoteant.jpg" alt="gif" height="188" width="178"></td>
31				</tr>
32				<tr>
33					<td>
34						<center>
35							UT+ oncore</center>
36					</td>
37					<td>
38						<center>
39							Evaluation kit</center>
40					</td>
41					<td>
42						<center>
43							Oncore Remote</center>
44					</td>
45				</tr>
46			</table>
47		</center>
48		<p>The driver requires a standard <tt>PPS</tt> interface for the pulse-per-second output from the receiver. The serial data stream alone does not provide precision time stamps (0-50msec variance, according to the manual), whereas the PPS output is precise down to 50 nsec (1 sigma) for the VP/UT models and 25 nsec for the M12 Timing. If you do not have the PPS signal available, then you should probably be using the NMEA driver rather than the Oncore driver. Most of these are available on-line</p>
49		<p>The driver will use the &quot;position hold&quot; mode with user provided coordinates, the receivers built-in site-survey, or a similar algorithm implemented in this driver to determine the antenna position.</p>
50		<h4>Monitor Data</h4>
51		The driver always puts a lot of useful information on the clockstats file, and when run with debugging can be quite chatty on stdout. When first starting to use the driver you should definitely review the information written to the clockstats file to verify that the driver is running correctly.
52		<p>In addition, on platforms supporting Shared Memory, all of the messages received from the Oncore receiver are made available in shared memory for use by other programs. See the <a href="oncore-shmem.html">Oncore-SHMEM</a> manual page for information on how to use this option. For either debugging or using the SHMEM option, an Oncore Reference Manual for the specific receiver in use will be required.</p>
53		<h4>Fudge Factors</h4>
54		<dl>
55			<dt><tt>time1 <i>time</i></tt>
56			<dd>Specifies the time offset calibration factor, in seconds and fraction, with default 0.0.
57			<dt><tt>time2 <i>time</i></tt>
58			<dd>Not used by this driver.
59			<dt><tt>stratum <i>number</i></tt>
60			<dd>Specifies the driver stratum, in decimal from 0 to 15, with default 0.
61			<dt><tt>refid <i>string</i></tt>
62			<dd>Specifies the driver reference identifier, an ASCII string from one to four characters, with default <tt>GPS</tt>.
63			<dt><tt>flag1 0 | 1</tt>
64			<dd>Not used by this driver.
65			<dt><tt>flag2 0 | 1</tt>
66			<dd>Not used by this driver.
67			<dt><tt>flag3 0 | 1</tt>
68			<dd>Not used by this driver.
69			<dt><tt>flag4 0 | 1</tt>
70			<dd>Not used by this driver.
71		</dl>
72		<h4>Additional Information</h4>
73		<p>The driver was initially developed on FreeBSD, and has since been tested on Linux, SunOS and Solaris.</p>
74		<p><b>Configuration</b></p>
75		<p>There is a driver specific configuration file <tt>ntp.oncore</tt> (or <tt>ntp.oncore.</tt><i>u</i> or <tt>ntp.oncore</tt><i>u</i> if you must distinguish between more than one Oncore receiver) that contains information on the startup mode, the location of the GPS receiver, an offset of the PPS signal from zero, and the cable delay. The offset shifts the PPS signal to avoid interrupt pileups `on' the second, and adjusts the timestamp accordingly. See the driver source for information on this file. The default with no file is: no delay, no offset, and a site survey is done to get the location of the gps receiver.</p>
76		<p>The following three options can be set in the driver specific configuration file only if the driver is using the PPSAPI. The edge of the PPS signal that is `on-time' can be set with the keywords [ASSERT/CLEAR] and the word HARDPPS will cause the PPS signal to control the kernel PLL.</p>
77		<p><b>Performance</b></p>
78		<p>Really good. With the VP/UT+, the generated PPS pulse is referenced to UTC(GPS)&nbsp;with better than 50 nsec (1 sigma) accuracy. The limiting factor will be the timebase of the computer and the precision with which you can timestamp the rising flank of the PPS signal. Using FreeBSD, a FPGA&nbsp;based Timecounter/PPS&nbsp;interface, and an ovenized quartz oscillator, that performance has been reproduced. For more details on this aspect: <a href="">Sub-Microsecond timekeeping under FreeBSD</a>.</p>
79		<hr>
80		<script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
81	</body>