From d13868b166f0dc088074d8276545aa1bc5c09989 Mon Sep 17 00:00:00 2001
From: "Eric S. Raymond" Please use this form to report GPSD Receiver Reporting Form
gpsd
successes or
-failures with GPS units, and also to upload a sample of the GPS's
+failures with GPS and AIS units, and also to upload a sample of the receiver's
output so we can add it to our regression tests and ensure continued
support of the device.
Important! Identify the vendor and model of
your device.
@@ -147,15 +147,15 @@ EOF
print $query->textfield(-name=>"techdoc", -size=>72);
print < It is useful to have an indication of how the receiver is packaged.
Please identify the device chipset and firmware version, if possible. You
may be able to get this from the display of Firmware:",
$query->textfield(-name=>"firmware", -size=>72)," Please identify, if possible, the NMEA version the receiver emits.
You may be able to get this information from the technical manual.
Likely values are Please identify the GPS's interface type (USB, RS-232, Compact Flash,
-etc.). If the GPS has adapters that support other interfaces, tell us
-the one you have and mention the adapters in the "Technical Notes" box.
-If it has an exotic interface not listed here, select "Other" and tell us
-about it in "Technical Notes". Please identify the receiver's interface type (USB, RS-232, Bluetooth,
+Compact Flash, etc.). If the receiver has adapters that support other
+interfaces, tell us the one you have and mention the adapters in the "Technical
+Notes" box. If it has an exotic interface not listed here, select "Other" and
+tell us about it in "Technical Notes".
-
@@ -164,16 +164,16 @@ on a car windshield or boat dash.
EOF
print $query->radio_group(-name=>'packaging',
- -values=>['GPS mouse', 'handset', 'handsfree',
+ -values=>['mouse', 'handset', 'handsfree',
'survey', 'OEM module', 'chipset', 'other'],
- -default=>"GPS mouse",
+ -default=>"mouse",
-linebreak=>'false');
print <xgps
; look for
-a GPS Type field or at the window title bar. Alternatively, you may find
+a Device Type field or at the window title bar. Alternatively, you may find
it in the technical manual.
Example: SiRF-II
amd 2.31ES
.2.0
, 2.2
, and 3.0
.
If the GPS emits only a vendor binary protocol, leave this field blank.Interfaces
-
Please rate how well this receiver functions with GPSD:
EOF my %labels=( "excellent", - "Excellent -- gpsd recognizes the GPS rapidly and reliably, reports are complete and correct.", + "Excellent -- gpsd recognizes the receiver rapidly and reliably, reports are complete and correct.", "good", "Good -- gpsd has minor problems or lag recognizing the device, but reports are complete and correct.", "fair", @@ -292,13 +292,13 @@ print <Important! We need a sample of the output -from your GPS - not the gpsd logfile, just raw output. We'll use this for +from your receiver - not the gpsd logfile, just raw output. We'll use this for mechanical regression testing, which is your best guarantee that support for your device won't get broken in a future release. Please be advised that these logs will be sent to a publicly archived mailing list, and will be available in the public SVN repository.
-Almost all GPS receivers will simply start throwing data to your port +
Almost all receivers will simply start throwing data to your port
immediately when they're plugged in. You should normally be able to capture
this output to a file with the gpscat
utility.
A log file is most useful when it contains (a) some sentences -generated when the GPS has no fix, (b) some sentences representing -a fix with the GPS stationary, and (c) some sentences representing -a fix with the GPS moving.
+generated when the receiver has no fix, (b) some sentences representing +a fix with the unit stationary, and (c) some sentences representing +a fix with the unit moving. EOF @@ -328,7 +328,7 @@ files.Location of the log capture. A good format would include your
nearest city or other landmark, state/province, country code, and a
-rough latitude/longitude. The GPS will give an exact location; we
+rough latitude/longitude. A GPS will give an exact location; we
want this as a sanity check.
Example: Groningen, NL, 53.2N 6.6E
Day/month/year of the log capture (the receiver will give us
hour/minute/second).
Example: 20 May 2006
.
If the receiver is a GPS, the default sampling interval in seconds (not +relevant for AIS receivers). This will usually be 1. For SiRF chips it's +always 1 and you can leave it blank; it's mainly interesting for NMEA devices +with unknown chipsets.
EOF @@ -361,10 +362,11 @@ print"Sampling interval:",$query->textfield(-name=>"interval", print <First sentence in the GPS's reporting cycle (not relevant or AIS +receivers). Leave this blank for SiRF devices; it is mainly interesting for +NMEA devices with unknown chipsets. You may be able to read it from the +manual; if not, slowing the GPS to 4800 will probably make the intercycle pause +visible.
EOF @@ -374,7 +376,7 @@ print"First sentence:",$query->textfield(-name=>"leader", print <gpsd
should work with any GPS 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 gpsd
version with
-which this GPS is known to have been successfully tested; A 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.
gpsd
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
+gpsd
version with which this receiver is known to have been
+successfully tested; A 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.
There is also a table of PPS-capable receivers which may be appropriate for timing use.
@@ -126,7 +126,7 @@ of the problem. Where possible, we indicate this in the device table.gpsmon
dates from this time
author believes to be our design mistakes. We discuss it here..
+In July and August 2009 ESR redesigned the GPSD command
+protocol and gave gpsd
the ability to read data from
+marine AIS receivers and pass it to clients.
Further forks of gpsd
seem unlikely, as the project is
now sufficiently large and visible to co-opt most developers who might
otherwise have forked the old 1.x sources or written a competing
diff --git a/www/index.html.in b/www/index.html.in
index 15d856ba..d00746b7 100644
--- a/www/index.html.in
+++ b/www/index.html.in
@@ -66,11 +66,11 @@
gpsd
gpsd
is a service daemon that monitors one or more
-GPSes attached to a host computer through serial or USB ports, making
-all data on the location/course/velocity of the sensors available to
-be queried on TCP port 2947 of the host computer. With
-gpsd
, multiple GPS client applications (such as
-navigational and wardriving software) can share access to GPSes
+GPSes or AIS receivers attached to a host computer through serial or
+USB ports, making all data on the location/course/velocity of the
+sensors available to be queried on TCP port 2947 of the host computer.
+With gpsd
, multiple location-aware client applications (such as
+navigational and wardriving software) can share access to receivers
without contention or loss of data. Also, gpsd
responds
to queries with a format that is substantially easier to parse than
the NMEA 0183 emitted by most GPSes. The gpsd
@@ -80,8 +80,8 @@ applications can use to encapsulate all communication with
gpsd
.
Besides gpsd
itself, the project provides auxiliary
-tools for diagnostic monitoring and profiling of GPSes and feeding
-GPS-aware applications GPS logs for diagnostic purposes.
The goal of the gpsd
project is to create a solid
layer of open-source infrastructure for programs running under Linux
@@ -105,7 +105,7 @@ configuration. Binary packages for this program install hotplug
scripts that do the right thing when a USB device goes active,
launching gpsd
if needed and telling gpsd
which device to read data from. Then, gpsd
deduces a
-baud rate and GPS type by looking at the data stream.
gpsd
is high-quality, carefully-audited code. It is
regularly checked with the standard mode of