summaryrefslogtreecommitdiff
path: root/www/hardware-head.html.in
blob: f49f3546e4a269e423731e2890bc1f92da69f9fe (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="Author" content="Eric Raymond">
   <meta name="Description" content="Hardware known to work with GPSD.">
   <meta name="Keywords" content="GPS, translator, mxmap, GIS">
   <title>Compatible GPSes</title>
   <link rel="stylesheet" href="main.css" type="text/css"/>
</head>

<div id="Header">Compatible Hardware</div>

<div id="Menu">
    <img src="gpsd-logo-small.png" alt="Small gpsd Logo" /><br />
    <a href="index.html">Home</a><br/>
    <a href="index.html#news">News</a><br/>
    <a href="index.html#downloads">Downloads</a><br/>
    <a href="index.html#mailing-lists">Mailing lists</a><br/>
    <a href="index.html#documentation">Documentation</a><br/>
    <a href="faq.html">FAQ</a><br/>
    <a href="xgps-sample.html">Screenshots</a><br/>
    <a href="index.html#recipes">Recipes</a><br/>
    <a href="index.html#others">Other GPSDs</a><br/>
    Hardware</a><br/>
    <a href="for-vendors.html">For GPS Vendors</a><br/>
    <a href="wishlist.html">Wish List</a><br/>
    <a href="hall-of-shame.html">Hall of Shame</a><br/>
    <a href="hacking.html">Hacker's Guide</a><br/>
    <a href="troubleshooting.html">Troubleshooting Guide</a><br/>
    <a href="protocol-transition.html">Application Compatibility</a>
    <a href="references.html">References</a><br/>
    <a href="history.html">History</a><br/>
    <a href="future.html">Future</a><br/>

    <div>&nbsp;</div>

    <a href='http://www.catb.org/hacker-emblem/'><img
    src='http://www.catb.org/hacker-emblem/glider.png'
    alt='hacker emblem' /></a><br />

    <script type="text/javascript" src="http://www.ohloh.net/p/3944/widgets/project_thin_badge.js"></script>

    <hr/>
    <script type="text/javascript"><!--
    google_ad_client = "pub-1458586455084261";
    google_ad_width = 160;
    google_ad_height = 600;
    google_ad_format = "160x600_as";
    google_ad_type = "text";
    google_ad_channel = "";
    //--></script>
    <script type="text/javascript"
      src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
    </script>
    <hr/>

    <a href="http://validator.w3.org/check/referer"><img
          src="http://www.w3.org/Icons/valid-xhtml10"
          alt="Valid XHTML 1.0!" height="31" width="88" /></a>

</div>
<div id="Content">

<div style="text-align: center;">
<div style="text-align: left; margin: 1em auto; width: 50%;">
<span>Search for hardware information here:</span>

<!-- SiteSearch Google -->
<form method="get" action="http://www.google.com/custom" target="_top">
<table border="0" bgcolor="#ffffff">
<tr><td nowrap="nowrap" valign="top" align="left" height="32">
<a href="http://www.google.com/">
<img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" align="middle"></img></a>
</td>
<td nowrap="nowrap">
<input type="hidden" name="domains" value="@SITESEARCH@"></input>
<input type="text" name="q" size="31" maxlength="255" value=""></input>
<input type="submit" name="sa" value="Search"></input>
</td></tr>
<tr>
<td>&nbsp;</td>
<td nowrap="nowrap">
<table>
<tr>
<td>
<input type="radio" name="sitesearch" value=""></input>
<font size="-1" color="#000000">Web</font>
</td>
<td>
<input type="radio" name="sitesearch" value="@SITESEARCH@"  checked="checked"></input>
<font size="-1" color="#000000">@SITESEARCH@</font>
</td>
</tr>
</table>
<input type="hidden" name="client" value="pub-1458586455084261"></input>
<input type="hidden" name="forid" value="1"></input>
<input type="hidden" name="ie" value="ISO-8859-1"></input>
<input type="hidden" name="oe" value="ISO-8859-1"></input>
<input type="hidden" name="flav" value="0000"></input>
<input type="hidden" name="sig" value="BCQudoNGuH3P6MJe"></input>
<input type="hidden" name="cof" value="GALT:#008000;GL:1;DIV:#336699;VLC:663399;AH:center;BGC:FFFFFF;LBGC:336699;ALC:0000FF;LC:0000FF;T:000000;GFNT:0000FF;GIMP:0000FF;FORID:1"></input>
<input type="hidden" name="hl" value="en"></input>
</td></tr></table>
</form>
<!-- SiteSearch Google -->
</div>
</div>

<p><code>gpsd</code> should work with any GPS or AIS receiver using an
RS232C or USB interface that advertises NMEA-0183 compliance.  Here
are some notes on hardware we have tested.  Hyperlinks lead to
technical information.  The "Works with" column is the last
<code>gpsd</code> version with which this receiver is known to have been
successfully tested; A <img src="regression.png"/> in this column
means we have a regression test load for the device that is checked
before each release. Vendors are listed in alphabetical order.</p>

<p>There is also a <a href="#timing">table of PPS-capable
receivers</a> which may be appropriate for timing use.</p>

<p><b>Warning:</b> the baudrate-hunting code in <code>gpsd</code>
tickles serious firmware bugs on some Bluetooth and USB devices.
These bugs may send affected GPSes catatonic.  See this <a
href="upstream-bugs.html#bluetooth">bug warning</a> for a description
of the problem. Where possible, we indicate this in the device table.</p>

<p>Icons used in the table:

<ul>
<li><img src="star.png"/><img src="star.png"/><img src="star.png"/><img
src="star.png"> marks devices with <b>Excellent</b> performance: gpsd
recognizes the receiver rapidly and reliably, reports are complete and
correct.</li>

<li><img src="star.png"/><img src="star.png"/><img src="star.png"/> marks
devices with <b>Good</b> performance: <tt>gpsd</tt> has minor problems
or lag recognizing the device, but reports are complete and
correct.</li>

<li><img src="star.png"/><img src="star.png"/> marks devices with
<b>Fair</b> performance: reports have minor dropouts or problems,
including occasional transient nonsense values.</li>

<li><img src="star.png"/> marks devices with <b>Poor</b> performance:
reports frequently have values that are wrong or nonsense.</li>

<li><img src="bomb.png"/> marks devices which are <b>Broken</b>;
gpsd frequently fails to recognize the device at all.</li>

<li><img src="noconfigure.png"/> marks devices that needed the
<tt>gpsd -b</tt> option when tested. Usually these are Bluetooth
devices with defective firmware that does not handle baud-rate changes
properly.  Some poorly-designed USB devices choke if they are fed too
many probe strings; these may work better with recent versions of
<tt>gpsd</tt>, which interleaves probe writes with the first few 
packet reads.</li>

<li><img src="regression.png"/> marks devices for which we have a
regression-test load. These are checked on every release.</li>

<li><img src="discontinued.png"/> marks devices that have been
discontinued by their manufacturers.</li>

<li><img src="hotplug.png"/> marks devices which will be recognized by
the Linux hotplug system when they are plugged in. If you installed
<tt>gpsd</tt> from a binary package,or did "make udev-install" from
the source distribution, this should mean you never have to launch
<tt>gpsd</tt> manually; the udev syatem will launch it for you when
it sees a device of this kind go active.</li>
</ul></p>

<p>Note that in most cases (including the <img src="noconfigure.png"/>
bug), poor ratings reflect problems not in <tt>gpsd</tt> but rather in
device design and firmware so badly botched that <tt>gpsd</tt> cannot
compensate.</p>

<p>This table is generated from a capability database in the
<code>gpsd</code> source tree. Please help us enrich the database with
new devices by filling out <a href="@WEBFORM@">this form</a>.</p>

<div>&nbsp;</div>

<!-- hardware-head.html ends here -->