summaryrefslogtreecommitdiff
path: root/gpscap.ini
diff options
context:
space:
mode:
authorGary E. Miller <gem@rellim.com>2015-04-13 13:04:37 -0700
committerGary E. Miller <gem@rellim.com>2015-04-13 13:04:37 -0700
commitfd4f4ac2e65435feabfefca5501bb3058b883de5 (patch)
tree6f0b156311aff77ac545983b5327a9eb3495106b /gpscap.ini
parent747004133067cafadeb99a645496d2fd8ae24b85 (diff)
downloadgpsd-fd4f4ac2e65435feabfefca5501bb3058b883de5.tar.gz
Remove trailing whitespace
Diffstat (limited to 'gpscap.ini')
-rw-r--r--gpscap.ini100
1 files changed, 50 insertions, 50 deletions
diff --git a/gpscap.ini b/gpscap.ini
index 3a51d598..ec7eb27c 100644
--- a/gpscap.ini
+++ b/gpscap.ini
@@ -19,7 +19,7 @@
# eval_unit = Which GPSD devs have one for testing (list)
# engine = GPS chipset (may reference another section)
# subtype = engine subtype or firmware revision level
-# interfaces = interface types: USB, RS-232, Bluetooth, CF, TTL, CAN.
+# interfaces = interface types: USB, RS-232, Bluetooth, CF, TTL, CAN.
# May be a list.
# usbchip = USB I/O chipset
# pps = supports pulse-per-second precision time reporting
@@ -62,7 +62,7 @@
# "OEM module" is an un-cased circuit board with edge connectors; a
# "chipset" is what it sounds like.
# A "handset" is a standalone GPS with a display and human-usable
-# controls. A "handsfree" is a hands-free unit with display designed for
+# controls. A "handsfree" is a hands-free unit with display designed for
# mounting on a car windshield or boat dash.
# * In the rating field:
# "excellent" - gpsd recognizes the GPS rapidly and reliably,
@@ -157,7 +157,7 @@ nmea = 3.01
engine = MT3339
rating = good
techdoc = http://www.adafruit.com/datasheets/PMTK_A11.pdf
-notes = 10Hz update.
+notes = 10Hz update.
[MTK]
type = engine
@@ -214,7 +214,7 @@ uses = SirfGeneric
tested = 2.34
rating = good
logs = ublox-sirf1.log
-notes = ublox-sirf1.log was made from a device with ublox firmware and
+notes = ublox-sirf1.log was made from a device with ublox firmware and
may not be typical of SiRF-1 chips.
[SiRF-2]
@@ -226,12 +226,12 @@ nmea = 2.2
uses = SirfGeneric
tested = 2.37
rating = good
-logs = bu303b-nofix.log, bu303-climbing.log, bu303-moving.log,
- bu303-nofix.log, bu303-stillfix.log, haicom-305N.log, holux-gm-210.log,
+logs = bu303b-nofix.log, bu303-climbing.log, bu303-moving.log,
+ bu303-nofix.log, bu303-stillfix.log, haicom-305N.log, holux-gm-210.log,
pharos-360.log, tn200-all.log, tn200.log, tn204.log
-notes = The bu* logs are in native binary format; the Haicom, Holux, Pharos,
+notes = The bu* logs are in native binary format; the Haicom, Holux, Pharos,
and TripNav logs in NMEA. NMEA starts with GGA and ends with RMC. The
- tn204 NMEA looks remarkably like older Garmin cruft and may be emulating
+ tn204 NMEA looks remarkably like older Garmin cruft and may be emulating
one, including the split reporting cycle.
[SiRF-3]
@@ -242,8 +242,8 @@ nmea = 3.01
uses = SirfGeneric
rating = good
logs = blumax-gps009.log, gpslim236.log, motorola-t805.log, rgm3800.log, et-332.log, tomtom-mkII.log
-notes = The Blumax log is in NMEA mode. Start of cycle is GGA, End of cycle
- is RMC. Some variants (like the Blumax) emit ZDA before GGA; others
+notes = The Blumax log is in NMEA mode. Start of cycle is GGA, End of cycle
+ is RMC. Some variants (like the Blumax) emit ZDA before GGA; others
(like the GPSlim 1236, Motorola T805, RGM3800) do not.
[SiRF-4]
@@ -642,7 +642,7 @@ tested = 3.14
rating = excellent
submitter = Gary E. Miller <gem@rellim.com>
pps = False
-notes = Vendor is in Shenzhen, China. Frequently on eBay. Sold as a
+notes = Vendor is in Shenzhen, China. Frequently on eBay. Sold as a
"Flight Control Module" as it also contains gyros and acceleromters
in a separate I2C bus. Does not have PPS but some resellers claim PPS.
@@ -667,7 +667,7 @@ notes = Uses SiRF firmware version 220.006.000ES. Accepts WAAS Mode Disable
type = device
engine = Skytraq Venus 6
date = 2010-06-10
-location =
+location =
model = BN-901S
packaging = mouse
interfaces = Bluetooth
@@ -847,8 +847,8 @@ interfaces = RS-232
location = Ulb?lle, DK, 55.04N 10.25E
model = Foretrex 201
nmea = 3.0
-notes = This device is not a conventional handfrtee unut for a car; it looks
- like a bulky wristwatch and is meant for bicycle handlebars. It must
+notes = This device is not a conventional handfrtee unut for a car; it looks
+ like a bulky wristwatch and is meant for bicycle handlebars. It must
be set to NMEA output in the settings->interface page.
packaging = handset
rating = excellent
@@ -899,7 +899,7 @@ uses = Garmin
interfaces = RS-232
tested = 2.38
nmea = 2.0
-submitter = Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>,
+submitter = Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>,
Amaury Jacquot <sxpert@esitcom.org>,
Jeff Francis <jfrancis@gritch.org>
notes = DGPS information in GPGGA sentence is not returned. Satellite
@@ -1011,7 +1011,7 @@ nmea = 2.0
discontinued = True
rating = excellent
tested = regression
-notes = Start-of-cycle is RMC. 2-second cycle time, 2 fixes per cycle, GLL
+notes = Start-of-cycle is RMC. 2-second cycle time, 2 fixes per cycle, GLL
reports second fix. The 48 has been discontinued. The Garmin
12XL and 45 are nearly identical and should work as well.
Details on the Garmin proprietary protocol can be found at <a
@@ -1037,13 +1037,13 @@ uses = Garmin
interfaces = RS-232
tested = 2.39
nmea = 2.3
-submitter = Sebastian Niehaus <killedbythoughts@mindcrime.net>,
+submitter = Sebastian Niehaus <killedbythoughts@mindcrime.net>,
Geoff Childs <dofinch-aria@yahoo.co.uk>
-notes = The device has a four pin socket described by Garmin as a serial
- interface. Connection to a standard 9 pin RS-232 computer socket
+notes = The device has a four pin socket described by Garmin as a serial
+ interface. Connection to a standard 9 pin RS-232 computer socket
is made using the special adaptor lead supplied by Garmin. Sebastian
Niehaus says it annunces "Software Version 3.70". Geoff Childs adds:
- "The Garmin GPS 76 comms MUST be set to 'NMEA'. The kernel module
+ "The Garmin GPS 76 comms MUST be set to 'NMEA'. The kernel module
garmin_gps is not needed and should not be specially loaded."
[Geko 201]
@@ -1056,7 +1056,7 @@ interfaces = RS-232
tested = regression
nmea = 3.0
submitter = Jose Luis Domingo Lopez <jdomingo@24x7linux.com>
-notes =
+notes =
logs = garmin-geko201.log
[eTrex Vista]
@@ -1069,7 +1069,7 @@ interfaces = RS-232
tested = 2.32
nmea = 3.0
submitter = Reed Hedges <reed@interreality.org>
-notes =
+notes =
[Nuvi 650]
type = device
@@ -1081,7 +1081,7 @@ interfaces = USB
tested = *
nmea = 3.0
rating = broken
-notes = This device does not have real-time data output, and is incompatible
+notes = This device does not have real-time data output, and is incompatible
with GPSD.
[GPSmap 76S]
@@ -1149,7 +1149,7 @@ submitter = Viktar Palstsiuk <viktar.palstsiuk@promwad.com>
techdoc = http://geostar-navigation.com/fail/manuals/User_Manual_GeoS-1M_en.pdf
tested = 2.90
vendor = Geostar
-notes = GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its
+notes = GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its
architecture includes 24 tracking channels.
logs = geos-1m.log
@@ -1205,7 +1205,7 @@ tested = regression
rating = excellent
eval_unit = esr
nmea = 2.2
-notes = Older versions of the BU-303 had a design defect that made it
+notes = Older versions of the BU-303 had a design defect that made it
likely to fail if subjected to vibration or hard shocks.
[BU-353]
@@ -1317,8 +1317,8 @@ tested = 3.3
type = device
uses = SiRF-3
vendor = GlobalSat
-notes = May work inside wood frame buildings. PPS pulse is only 1uS wide,
- but newer gpsd handles that fine. Be careful, there is also an MR-350
+notes = May work inside wood frame buildings. PPS pulse is only 1uS wide,
+ but newer gpsd handles that fine. Be careful, there is also an MR-350
(no suffix P) that does NOT have PPS.
logs = mr-350p
@@ -1540,7 +1540,7 @@ notes = The product page points at a retail site carrying these
because the vendor site is in Japanese only. This GPS emits a
weirdly broken GSA sentence that crashed gpsd versions prior to
2.28. Serial parameters default to 38400; 8, N, 1. May come
- bundled with Microsoft Streets and Trips.
+ bundled with Microsoft Streets and Trips.
logs = iTrek.log
#% Jackson Labs
@@ -1554,14 +1554,14 @@ pps = True
pps_accuracy = 50ns
packaging = OEM module
rating = excellent
-submitter = Don Weeks <don.l.weeks.jr@gmail.com>,
+submitter = Don Weeks <don.l.weeks.jr@gmail.com>,
Said Jackson <saidjack@aol.com>
techdoc = http://jackson-labs.com/docs/FireFly_quickstart.pdf
vendor = Jackson Labs
-notes = Only outputs GGA and RMC NMEA strings. There are other proprietary
- commands. See the gpsd-dev list for patches. GPSD works as far back
- as the 0.914 version, which emitted \r\r\n terminations. All the
- FireFly units are OCXO driven, so the 1PPS output stays accurate even
+notes = Only outputs GGA and RMC NMEA strings. There are other proprietary
+ commands. See the gpsd-dev list for patches. GPSD works as far back
+ as the 0.914 version, which emitted \r\r\n terminations. All the
+ FireFly units are OCXO driven, so the 1PPS output stays accurate even
if GPS reception is lost.
[FireFly-II]
@@ -1574,10 +1574,10 @@ pps = True
pps_accuracy = 50ns
time_offset = ?
model = FireFly-1A and FireFly-II GPSDO
-notes = Uses ublox Antaris 5 with Kick Start and Super Sense,
+notes = Uses ublox Antaris 5 with Kick Start and Super Sense,
soon movingto ublox-6. Defective \r\r\n string terminations
- have been fixed in the 2.18 firmware version. All the
- FireFly units are OCXO driven, so the 1PPS output stays accurate even
+ have been fixed in the 2.18 firmware version. All the
+ FireFly units are OCXO driven, so the 1PPS output stays accurate even
if GPS reception is lost.
packaging = OEM module
rating = good
@@ -1631,7 +1631,7 @@ interfaces = RS-232
tested = regression
rating = good
submitter = Angel Marques Mateu <amarques@cgf.upv.es>
-notes =
+notes =
logs = magellan315.log
[Meridian Platinum]
@@ -1657,7 +1657,7 @@ interfaces = USB
tested = regression
rating = good
nmea = 2.1
-submitter = rickyconnell@gmail.com
+submitter = rickyconnell@gmail.com
logs = eXplorist110.log
[eXplorist 210]
@@ -1675,7 +1675,7 @@ notes = USB has 3 modes &mdash; NMEA data comm (3 submodes): outputs GPS data
(creates /dev/ttyACM0), USB file transfer: transfer files (creates
/dev/sdX and /dev/sdX1), or Power Only: use USB only for electrical
power. The APA and XTE extensions choke gpsd, so select V2.1 GSA
- under "NMEA Data Comm>".
+ under "NMEA Data Comm>".
logs = eXplorist210.log
[Thales AC12]
@@ -1837,7 +1837,7 @@ notes = When running, need to use the -b option, else the device will
"fudge" factor to 0.840. There is no known PPS signal associated
with this device. While the technical information claims 1us
accuracy on the clock, the interface is undocumented, so there
- is no way to know if there is a usable 1PPS signal.
+ is no way to know if there is a usable 1PPS signal.
[NL-302U]
type = device
@@ -1936,8 +1936,8 @@ techdoc = http://navis.ru/downloads/CH-4711_USB/
logs = ch-4711.log
notes = By default the device does not report 2d fixes; the vendor
configuration tool offers checkboxes to enable any combination of
- none, 2D fixes, 3D fixes, or both. The devices has only a very
- limited set of NMEA controls but speaks a proprietary vendor format
+ none, 2D fixes, 3D fixes, or both. The devices has only a very
+ limited set of NMEA controls but speaks a proprietary vendor format
called BINR with more capabilities.
[NAVIOR-24]
@@ -1973,12 +1973,12 @@ submitter = sk1ppy14@yahoo.co.uk
techdoc = http://www.navisys.com.tw/products/image/GR-300_flyer-080409.pdf
tested = 2.38
vendor = Navisys
-notes = Also includes an (untested) Bluetooth interface. Has two LEDs:
- blue for bluetooth, green for rating. Solid green = on and searching
+notes = Also includes an (untested) Bluetooth interface. Has two LEDs:
+ blue for bluetooth, green for rating. Solid green = on and searching
for satellite fixes. Blinking green = on and has 3D fix.
- Also a similar GR-310 version available. It is possible that only GR-310
- supports Bluetooth. Programs only seem to be able to communicate
- with the dongle at 4800 baud rates, though this is autodetected by gpsd
+ Also a similar GR-310 version available. It is possible that only GR-310
+ supports Bluetooth. Programs only seem to be able to communicate
+ with the dongle at 4800 baud rates, though this is autodetected by gpsd
with no problems. Approx &pound;40 per <a href="http://www.navisys.com.tw/products/gps_usb_dongle.htm">dongle</a>.
#%Nokia
@@ -2083,7 +2083,7 @@ tested = 2.34
nmea = 2.2
notes = As this is a Bluetooth device, gpsd must either be run with "-b" or must
be compiled with fixed port speed, as the Bluetooth interface does not
- tolerate port speed changes at all. Reported by Sebastiano Zabert
+ tolerate port speed changes at all. Reported by Sebastiano Zabert
(no emal address)
#% Qstarz
@@ -2117,7 +2117,7 @@ rating = fair
submitter = Stoo <f4eru@free.fr>
techdoc = http://www.rfsolutions.co.uk/acatalog/DS320-2.pdf
vendor = RF Solutions
-notes = Has a binary protcol documetened at
+notes = Has a binary protcol documetened at
http://www.rfsolutions.co.uk/acatalog/DS-41COM-2.pdf.
Sat-simulator testing reveals that the chipset does not handle
dates after 2019 well; they wrap to 1999. The device sends out
@@ -2623,7 +2623,7 @@ usbchip = CP2101
tested = 3.4
nmea = 3.01
submitter = Reported by Eric S. Raymond <esr@thyrsus.com>
-notes = Device has two variants; the basic receiver is 'R' and the
+notes = Device has two variants; the basic receiver is 'R' and the
version with additional data-logger capability is N. Emits only NMEA.
Some Web sources incorrectly describe it as SiRF-3-based.