# GPS capability description file
#
# Our apologies to all Unix hackers in advance for the grubby .INI syntax,
# we're using it because the format has good cross-Unix support in Python.
#
# Each section map have the following capabilities
#
# type = "engine", "vendor", or "device"
# description = Human-readable description of this item
# packaging = A device's form factor
# reference = URL to technical documentation, or at least a spec sheet
# vendor_site = URL of a vendor site
# vendor = vendor name
# 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, RS232, Bluetooth, CF, TTL. May be a list.
# usbchip = USB I/O chipset
# pps = supports pulse-per-second precision time reporting
# noconfigure = can be bricked by baud-rate changes (requires -b option)
# tested = last gpsd tested, or "regression" if we have a test load
# nmea = NMEA version this emits, if known
# notes = Miscellaneous notes on this item. To be interpreted as HTML.
# status = excellent, good, fair, poor, broken, other
# discontinued = If present, product has been discontinued
#
# Capability strings:
#
# to_nmea = if present, how to switch to NMEA 0183 mode from native binary
# to_native = if present, how to swith to native binary mode from NMEA
# modeset = set protocol, baud rate, 8N1
#
# Inheritance
#
# To inherit capabilities from a specified section, name the section in
# a "uses =" attribute. Use chains are followed recursively. An attribute
# in a section overrides all attributes of the same name in all ancestor
# sections.
#
# Certain escapes in capability strings are translated:
#
# %b - baud rate as ASCII numeral
#
# A string beginning with 0x is interpreted as a sequence of paired hex bytes,
# leading 0x not included.
#
# Comment lines led with "#%" are vendor section marks to be used when
# generating an HTML table from this file. Each should consist of a vendor
# name.
#
# Further notes:
# * In the packaging feld, a "GPS mouse" is a standalone sensor in a
# display-less case designed be used as an outbard peripheral. An
# "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
# mounting on a car windshield or boat dash.
# * In the status field:
# "excellent" - gpsd recognizes the GPS rapidly and reliably,
# reports are complete and correct.
# "good" -- gpsd has minor problems or lag recognizing the device,
# but reports are complete and correct.
# "fair" -- Reports have minor dropouts or problems, including occasional
# transient nonsense values.
# "poor" -- Reports frequently have values that are wrong or nonsense.
# "broken" -- gpsd frequently fails to recognize the device at all.
# "other -- See Technical Notes.
#
# Chipsets
#
[GenericSiRF]
type = engine
description = Capabilities generic to all SiRF chips
# Sets 4800 baud shipping GGA+GSA+GSV+RMC
to_nmea = 0xa0a200188102010100000101050101010000000100010001000112c00000b0b3
to_native = $PSRF100,0,%b,8,1,0 # Sets 8N1 with specified speed
[SiRF-1]
type = engine
description = Version 1 of the SiRF GPS engine
engine = SiRF-1
nmea = 2.2
uses = GenericSiRF
tested = 2.34
status = good
[SiRF-2]
type = engine
description = Version 2 of the SiRF GPS engine
engine = SiRF-2
# Later versions may do 2.3
nmea = 2.2
uses = GenericSiRF
tested = 2.37
status = good
[SiRF-3]
type = engine
description = Version 3 of the SiRF GPS engine
engine = SiRF-3
nmea = 3.01
uses = GenericSiRF
tested = 2.37
status = good
[ANTARIS]
type = engine
engine = ANTARIS
nmea = 2.3
status = good
reference = http://www.u-blox.com/products/tim_lp.html
notes = The ANTARIS chipset has been end-of-lifed.
[ANTARIS4]
type = engine
engine = ANTARIS4
reference = http://www.u-blox.com/products/a4products.html
nmea = 2.3
status = good
notes = Sends 'E' in second field of GSA record, not an NMEA value.
Actually sends '6' in the GGA status record for dead-reckoning fixes.
(This behavior reported on the 4H chipset.)
[FastraX iTrax03]
type = engine
reference = http://www.fastraxgps.com/products/gpsmodules/index.cfm?template=products.show.cfm&productGuid=4594da1a-503c-469c-91b2-6948043189be
engine = FastraX iTrax03
status = good
[Garmin]
type = engine
engine = Garmin
description = There are several versions; the differences are not clear.
reference = http://www.garmin.com/support/commProtocol.html
status = good
[MTK]
type = engine
nmea = 3.01
engine = MTK
status = good
[Nemerix]
type = engine
engine = Nemerix
nmea = 3.01
status = good
notes = NemeriX has gone into liquidation as of Jan 2009). It's funny, they
didn't understand why they should give me an unencumbered protocol
reference.
[NovAtel-L1]
type = engine
engine = NovAtel-L1
reference = http://www.novatel.com/Documents/Manuals/om-20000086.pdf
nmea = 2.20
status = good
notes = Seems to be built around the Zarlink GP4020.
[Sony CXD2951]
type = engine
reference = http://gpsd.berlios.de/vendor-docs/cxd2951-commands.pdf
engine = Sony CXD2951
status = good
[Touchstone ASIC]
type = engine
engine = Touchstone ASIC
status = good
reference = http://www.navcomtech.com/Products/GPS/Touchstone.cfm
[uNav]
type = engine
engine = uN3010
nmea = 3.01
notes = uNav was acquired by Atheros in 2007. They have inherited
one GPS product, now designated uN3010.
status = good
[Zodiac]
type = engine
engine = Zodiac
nmea = 2.2
tested = 2.0
reference = http://www.gpskit.nl/downloads-en.htm
notes = This chip was made by Rockwell International. It was
also known as the Jupiter. It has been EOLed.
status = good
#
# Vendors (alphabetical by vendor)
#
[Altina]
type = vendor
vendor_site = http://www.altina.com
[Adapt Mobile]
type = vendor
vendor_site = http://www.adapt-mobile.com>
[Axiom]
type = vendor
vendor_site = http://gpsd.berlios.de/vendor-docs/axiom
[Billionton]
type = vendor
vendor_site = http://www.billionton.com/english/index.htm
[Central Pacific]
type = vendor
vendor_site = http://www.cpit.com
[Delorme]
type = vendor
vendor_site = http://www.delorme.com
[Eurotech]
type = vendor
vendor_site = http://www.eurotech-inc.com/
[EuroTronics]
type = vendor
vendor_site = http://www.eurotronic.net/
[Garmin]
type = vendor
vendor_site = http://www.garmin.com
[GlobalSat]
type = vendor
vendor_site = http://www.globalsat.com.tw/english/products.php
[Haicom]
type = vendor
vendor_site = http://www.haicom.com.tw/
[Holux]
type = vendor
vendor_site = http://www.holux.com
[Humminbird]
type = vendor
vendor_site = http://www.humminbird.com/
notes = These guys make fish-finders that incorporate GPSes
[iTrek]
type = vendor
vendor_site = http://www.i-trek.jp
[Magellan]
type = vendor
vendor_site = http://www.magellangps.com
notes = Now owns what used to be the Thales and Ashtech product lines
[Motorola]
type = vendor
vendor_site = http://www.motorola.com/ies/GPS/products_legacy.html
notes = Motorola has exited the GPS business
[Navcom]
type = vendor
vendor_site = http://www.navcomtech.com/
[Navius]
type = vendor
vendor_site = http://www.navius.biz/
notes = This vendor has also traded as "Navisky".
[NaviLock]
type = vendor
vendor_site = http://www.navilock.de
[NavMan]
type = vendor
vendor_site = http://www.navmanwirelessoem.com/
[NovAtel]
type = vendor
vendor_site = http://www.novatel.com/
[Parrot]
type = vendor
vendor_site = http://www.parrot.biz
[Pharos]
type = vendor
vendor_site = http://www.pharosgps.co/
[Phonix]
type=vendor
vendor_site = http://www.phonix.it/
[Rikaline]
type = vendor
vendor_site = http://www.rikaline.com
[Royaltek]
type = vendor
vendor_site = http://www.royaltek.com/
[San Jose Navigation]
type = vendor
vendor_site = http://www.sanav.com
[Transystem]
type = vendor
vendor_site = http://www.transystem.com.tw/
[Techway]
type = vendor
vendor_site = http://www.techwayinc.com.tw/
notes = This vendor has drooped off the web
[TomTom]
type = vendor
vendor_site = http://www.tomtom.com
[Trimble]
type = vendor
vendor_site = http://www.trimble.com/
[uBlox]
type = vendor
vendor_site = http://www.u-blox.de/
[UniTraq]
type = vendor
vendor_site = http://www.unitraq.com/
[Wintec]
type = vendor
vendor_site = http://www.wintec.com.tw/
#
# Devices (alphabetical by vendor)
#
#% Altina
[GBT709]
type = device
vendor = Altina
packaging = handset
reference = http://www.altina.com/produkty.php?destCatId=&mainCatId=13&subCatId=&prId=19
interfaces = Bluetooth
noconfigure = True
tested = 2.35
uses = SiRF-3
notes = Requires the "-b" flag to prevent mode switching. If the receiver locks
up due to a mode switch, remove the battery for 5 to 10 minutes.
Reported by Benoit Panizzon <panizzon@woody.ch>
#% Adapt Mobile
[AD-500]
type = device
vendor = Adapt Mobile
packaging = GPS mouse
reference = http://adapt-mobile.bosqom.com/default.php?page_ID=3&spage_ID=1
uses = Nemerix
interfaces = Bluetooth, USB
iochip = pl2303
tested = 2.32
notes = Reported by Dennis van Zuijlekom <tmib@xs4all.nl>.
#% Axiom
[Sandpiper]
type = device
vendor = Axiom
packaging = OEM module
reference = http://gpsd.berlios.de/vendor-docs/axiom
uses = SiRF-1
interfaces = RS232C
tested = 2.34
pps = True
notes = The vendor is out of business, but there are lots of these still
around in 2006. Complete documentation for this OEM module has been
archived at the GPSD site.
#% Billionton
[Billionton CF-GPS]
type = device
vendor = Billionton
packaging = GPS mouse
reference = http://www.billionton.com/english/product/CF-GPS.htm
uses = SiRF-2
interfaces = CF
tested = 2.16
notes = Uses SiRF firmware version 220.006.000ES. Accepts WAAS Mode Disable
($PSRF108,00*02) and WAAS Mode Enable ($PSRF108,01*03)
controls.
Reported by Oleg Gusev <oleg@crista.uni-wuppertal.de>.
#% Central Pacific
[CPIT GP-27]
type = device
vendor = Central Pacific
packaging = GPS mouse
reference = http://www.cpit.com/en/GP-27.html
uses = Nemerix
interfaces = Bluetooth
tested = 2.28
noconfigure = True
notes = Reported by Tobias Minich <belgabor@gmx.de>
- There are proprietary PNMRX{30[0124],603} sentences that are only sent
on change or by request
- Several sentences can be sent to the device to change settings or
request information. DO NOT USE THE PNMRX100 SENTENCE TO CHANGE THE BAUD
RATE! This is not supported by the bluetooth chip on the device.
- Settings are saved in flash powered by a backup battery and persistent
over connections and when you turn it off.
- The syntax of the PNMRX303 message and part 4 of the PNMRX603 message
may differ from the syntax found in several documents on the net.
#% Delorme
[EarthMate USB]
type = device
vendor = Delorme
packaging = GPS mouse
reference = http://www.delorme.com/earthmate/default.asp
uses = SiRF-2
interfaces = USB
usbchip = Cypress M8 CY7C64013
tested = 2.5
notes = This was the replacement for the old Zodiac version that spoke
Rockwell binary protocol; it in turn has been discontinued. Some
other sentences can be enabled. Requires a 2.6.10 or better
kernel for the Cypress USB-HID support.
[EarthMate]
type = device
vendor = Delorme
packaging = GPS mouse
uses = Zodiac
interfaces = RS232C
notes = These models have been discontinued.
[TripMate]
type = device
vendor = Delorme
packaging = GPS mouse
reference = http://vancouver-webpages.com/peter/tripmate.faq
uses = Zodiac
interfaces = RS232C
discontinued = True
notes = Discontinued sometime before November 1998.
#% Eurotech
[Com-1289]
type = device
vendor = Eurotech
packaging = OEM module
reference = http://www.eurotech.fi/products/COM-1289.html
engine = FastraX iTrax03
interfaces = RS232
tested = regression
status = good
notes = Simon Le Pape
Reported by
#% EuroTronics
[Blumax GPS009]
type = device
vendor = EuroTronics
packaging = GPS mouse
reference = http://www.eurotronic.net/products/produktdetails/gps_receiver.html
uses = SiRF-3
interfaces = Bluetooth
noconfigure = True
tested = regression
notes = Requires "-b" ... I had to totally drain the battery of the device
and let it rest for a few days before i was able to use it again
after a first attempt of using it with without "-b"
Reported by Hartmut Holzgraefe <hartmut&x40;php.net>
#% Garmin
[Garmin GPS-15]
type = device
packaging = OEM module
vendor = Garmin
reference = http://www.garmin.com/products/gps15/spec.html
uses = Garmin
interfaces = RS232
tested = 2.33
nmea = 2.0
pps = True
notes = "$PGRMI,,,,,,,R" must be sent to reset the device before PPS
works; after about 5 minutes the PPS signal is detected properly
by GPSD. Reported by Jason Hecker
<jhecker@wireless.org.au>
[Garmin GPS-16]
type = device
packaging = GPS mouse
vendor = Garmin
reference = http://www.garmin.com/products/gps16/spec.html
uses = Garmin
interfaces = RS232
tested = 2.38
nmea = 2.0
notes = DGPS information in GPGGA sentence is not returned. Satellite
azimuths/elevations and magnetic variation information are not
available in binary mode. Garmin uses a nonstandard 16-bit SNR
scale for signal quality in GSA. Can be switched to NMEA 3.0
with PGRMC1. Reported by Ron Marosko,
Jr. <rmarosko@wirelessfrontier.net>, Amaury Jacquot
<sxpert@esitcom.org>, and Jeff Francis
<jfrancis@gritch.org>.
[Garmin GPS-17N]
type = device
packaging = GPS mouse
vendor = Garmin
reference = http://www.garmin.com/products/gps17/spec.html
uses = Garmin
interfaces = RS232
tested = regression
nmea = 2.0 or 3.0
notes = The 17N has been discontinued and replaced by the 17HVS.
The interface was RS232 but used a custom RJ-45 jack.
Reported by Wojciech Kazubski <wk@ire.pw.edu.pl>.
[Garmin GPS-17HVS]
type = device
vendor = Garmin
packaging = GPS mouse
reference = https://buy.garmin.com/shop/shop.do?cID=158&pID=8630
engine = unknown
interfaces = RS232
tested = 2.37
status = good
nmea = 2.0 or 3.0
notes = Reported by Ulrich Voigt
[Garmin GPS-18 USB]
type = device
packaging = GPS mouse
vendor = Garmin
reference = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf
uses = Garmin
interfaces = USB
tested = 2.38
nmea = N/A
notes = The USB version requires the Linux kernel garmin_usb driver
and requires that usbfs is mounted: mount -t usbfs none
/proc/bus/usb/
DOP (Dilution of Precision) information is not available (Garmin protocol
includes EPE only); gpsd uses EPE to approximate DOP. Magnetic variation
information is not available. Garmin uses a nonstandard 16-bit SNR scale.
The 18 series, unlike the 16, reports skyview via a packet 114.
[Garmin GPS-18 (all but USB)]
type = device
packaging = GPS mouse
vendor = Garmin
reference = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf
uses = Garmin
interfaces = RS232
pps = True
tested = 2.5
nmea = 2.0 and 2.3
notes = The RS232 versions emit NMEA and are found by normal autoconfiguration.
GPS-18 LVC and GPS-18 LVC/5m have PPS outputs. WAAS is supported.
The 18 series, unlike the 16, reports skyview via a packet 114.
[GPS-25LP]
type = device
packaging = OEM module
vendor = Garmin
reference = http://www8.garmin.com/products/gps25/spec.html
uses = Garmin
interfaces = RS232
nmea = 2.0
tested = regression
discontinued = True
notes = Discontinued embedded module.
Reported by Daniele Giangrazi &t;daniele.giangrazi@elital.net>
[Garmin 38]
type = device
vendor = Garmin
packaging = handset
reference = http://au.geocities.com/glennbaddeley/gps/data/GPS38_OwnersManualAndReference_June1997_RevB.pdf
uses = Garmin
interfaces = RS232
status = excellent
tested = regression
nmea = 2.0
discontinued = True
notes = Reported by Pascal F. Martin <pascal.martin@cox.net>
[Garmin 48]
type = device
vendor = Garmin
packaging = handset
reference = https://buy.garmin.com/shop/shop.do?pID=85
uses = Garmin
interfaces = RS232
nmea = 2.0
status = excellent
tested = regression
notes = 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 here.
[Garmin GPS 60]
type = device
vendor = Garmin
packaging = handset
reference = http://www.garmin.com/manuals/GPS60_OwnersManual.pdf
uses = Garmin
interfaces = USB, RS232
tested = 2.33
nmea = 3.01
notes = Reported by Diego Berge
(contact)
[Garmin GPS 76]
type = device
vendor = Garmin
packaging = handset
reference = http://www.garmin.com/manuals/GPS76_OwnersManual.pdf
uses = Garmin
interfaces = USB
usbchip = pl2303
tested = 2.13
nmea = 2.3
notes = Reported by Sebastian Niehaus <killedbythoughts@mindcrime.net>
He says it is "Software Version 3.70".
[Geko 201]
type = device
vendor = Garmin
packaging = handset
reference = http://www.garmin.com/manuals/Geko201_OwnersManual.pdf
uses = Garmin
interfaces = RS232
tested = regression
nmea = 3.0
notes = Reported by Jose Luis Domingo Lopez <jdomingo@24x7linux.com>
[eTrex Vista]
type = device
vendor = Garmin
packaging = handset
reference = http://www.garmin.com/manuals/eTrexVista_OwnersManual.pdf
uses = Garmin
interfaces = RS232
tested = 2.32
nmea = 3.0
notes = Reported by Reed Hedges <reed@interreality.org>
[Nuvi 650]
type = device
vendor = Garmin
packaging = handsfree
reference = http://www.garmin.com/manuals/nuvi650_OwnersManual.pdf
uses = SiRF-3
interfaces = USB
tested = *
nmea = 3.0
status = broken
notes = This device does not have real-time data output, and is incompatible with GPSD.
#% GlobalSat
[BC-307]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.usglobalsat.com/item.asp?itemid=12
uses = SiRF-2
interfaces = CF
tested = 2.35
nmea = 2.2
notes = Acceptably functional running firmware 231ES. Reported by
Chris Kuethe <chris.kuethe@gmail.com>.
[BT-318]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.globalsat.com.tw/english/products_detail.php?main_id=21&p_id=107
uses = SiRF-2
interfaces = Bluetooth
tested = 2.20
nmea = 2.2
notes = Reported by Frank Nicholas <frank@nicholasfamilycentral.com>.
[BT-338]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.usglobalsat.com/item.asp?itemid=6
uses = SiRF-3
interfaces = Bluetooth
tested = 2.13
notes = Reported by Michal Panczyk <mpanczyk@gmail.com>
[BU-303]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.usglobalsat.com/item.asp?itemid=11&catid=13
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = regression
status = excellent
eval_unit = esr
nmea = 2.2
notes = Older versions of the BU-303 had a
design
defect that made it likely to fail if subjected to vibration or
[BU-353]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.usglobalsat.com/item.asp?itemid=60&catid=17
uses = SiRF-3
interfaces = USB
usbchip = pl2303
tested = pre-2.29
nmea = 2.3
notes = This receiver, or at least the firmware it ships with does not
support PPS timing output, nor does it support WAAS - something
born out by the claimed 10m positioning accuracy. These will
hopefully be fixed in future firmware revisions. The increased
sensitivity is nice, but the lack of WAAS and PPS could be
show-stoppers for various applications.
[TripNav TN-200]
type = device
vendor = GlobalSat
packaging = GPS mouse
reference = http://www.usglobalsat.com/item.asp?itemid=45&catid=13
uses = SiRF-2
interfaces = USB
usbchip = FTDI FT232
tested = regression
status = excellent
notes = We tested a version with SiRF Firmware level 231ES. The FTDI USB-to-serial
chip is supported only as alpha software not yet
incorporated into the Linux kernel, though it seems to be well
supported by OS X and various BSDs. It seems like the only
difference between this and the BU-303 is the different
USB-to-serial chip.
[TripNav TN-204]
type = device
vendor = GlobalSat
packaging = GPS mouse
uses = SiRF-2
interfaces = CF
tested = regression
status = excellent
notes = Sometimes sold under the brand name "Rayming", but that vendor
seems to have disappeared. "Pascal F. Martin"
#% Haicom
[HI-204S]
type = device
vendor = Haicom
packaging = GPS mouse
reference = http://www.haicom.com.tw/products.htm
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = 2.24
status = excellent
eval_unit = esr
nmea = 2.2
notes = SiRF firmware level 231ES (XTrac). Haicom provided a test unit. Manual
states incorrectly that VTG is off by default.
[HI-204E]
type = device
vendor = Haicom
packaging = GPS mouse
reference = http://www.haicom.com.tw/gps204E.shtml
engine = Evermore BBP1202
interfaces = USB
tested = 2.6
status = excellent
nmea = 2.2
notes = Probably uses PL2303 but we have not verified this.
[HI-303S]
type = device
vendor = Haicom
packaging = handsfree
reference = http://www.haicom.com.tw/gps303s.shtml
uses = SiRF-3
interfaces = RS232
tested = 2.25
nmea = 2.2
notes = NMEA works, but SiRF binary does not. This device seems to ignore the
$PSRF100 mode switch command. (SiRF binary may be available on the
auxiliary serial port, but this is unconfirmed.) This device ships
This device ships with XTrac Firmware. It has been discontinued.
Reported by Denis Perchine <dyp@perchine.com>
[HI-305N]
type = device
vendor = Haicom
packaging = GPS mouse
reference = http://www.haicom.com.tw/
uses = Nemerix
interfaces = CF
tested = regression
discontinued = True
notes = Adaptors for RS232, USB, and Bluetooth operation
are available. Reported by David Findlay
<dave@davsoft.com.au>
#% Holux
[GM-210]
type = device
vendor = Holux
packaging = GPS mouse
reference = http://www.amazon.com/Holux-GM-210-Receiver-Laptop-Pocket/dp/B0006ZMBTW
uses = SiRF-2
interfaces = RS232
tested = regression
nmea = 2.2
discontinued = True
notes = Reported by Patrick L. McGillan <pmcgillan@pateri.com>.
[GR-230]
type = device
vendor = Holux
packaging = GPS mouse
reference = http://www.holux.com.tw/Temp%20web/GR-230.html
uses = SiRF-2
interfaces = Bluetooth
noconfigure = True
tested = 2.19
nmea = 2.2
discontinued = True
notes = 4 color LED showing: Bluetooth, Navigation Update and Battery
and Charger Status Indication. FLASH based program
memory. Firmware upgradeable through serial interface. Water
resistant.
[GPSlim 236]
type = device
vendor = Holux
packaging = GPS mouse
reference = http://en.holux.com.cn/product/search.htm?filename=gpsreceiver_bluetooth_gpslim2+36.htm&target=bluetooth00&level=grandsonson
uses = SiRF-3
interfaces = Bluetooth
tested = regression
status = poor
nmea = 2.2
notes = Does not report altitude reliably.
Optional interfaces:
mini-USB -> USB, needing a special cable : GR230-A2 (USB data cable),
otherwise it will not work;
mini-USB -> RS232, need cable GR230-A1(RS232 data cable), I didn't
try it with a normal cable;
mini-USB -> PS2, need cable GR230-A3 (Mini USB port to PS2 port ), I
didn't try it with a normal cable.
Reported by "Kévin Redon" <kevredon@gmail.com>
[Holux GR-239]
type = device
vendor = Holux
packaging = GPS mouse
reference = http://www.holux.com/JCore/en/support/DLF.jsp?DLU=http://www1.holux.com.tw:8080/JCore/UploadFile/79754.pdf
uses = SiRF-3
interfaces = Bluetooth, USB
noconfigure = True
tested = 2.36
status = poor
nmea = 2.2
notes = Bluetooth operation requires -b option. Powered from a car
cigarette-lighter.
[M-241]
type = device
vendor = Holux
packaging = GPS mouse
reference = http://www.holux.com/JCore/en/products/products_content.jsp?pno=341
uses = MTK
interfaces = Bluetooth, USB
usbchip = CP2101
noconfigure = True
tested = 2.37
notes = gpsd crashes the device when autoprobing @ baud rate 9600 (unless
'-b'/broken-device-safety is enabled - need to unplug/reset the device).
'stty -F /dev/ttyUSB1 ispeed 38400' helps avoiding too much autoprobing -
though stty complains about not being able to perform all requested
operations. Reported by Roland Ager <roland.ager@gmx.de>
#% Humminbird
[Matrix-37]
type = device
vendor = Humminbird
packaging = handsfree
reference = http://www.retrevo.com/support/Humminbird-37-GPS-manual/
engine = unknown
interfaces = RS232
discontinued = True
tested = regression
status = good
notes = Depth finder and water-temperature sensor.
Reported by "Carl Brown"
#% iTrek
[M3]
type = device
vendor = iTrek
packaging = GPS mouse
reference = http://www.semsons.com/im3blgpsresi.html
uses = SiRF-3
interfaces = Bluetooth
tested = 2.28
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. Reported by Lance
Fetters <ashikase@users.sourceforge.net>
#% Magellan
[EC-10X]
type = device
vendor = Magellan
packaging = handset
reference = http://www.herman-nelson.com/itemInfo.cfm?itemID=205
uses = Zodiac
interfaces = RS232
pps = True
tested = regression
discontinued = True
notes = It was cool in its day, now a dinosaur mainly good for
regression testing. NMEA time is accurate to about 500mS.
Reported by Gary E. Miller <gem@rellim.com>.
[315]
type = device
vendor = Magellan
packaging = handset
reference = https://www.magellangps.com/assets/manuals/gps_310_315_en.pdf
engine = unknown
interfaces = RS232
tested = regression
status = good
notes = Reported by Ángel Marqués Mateu <amarques@cgf.upv.es>
[Meridian Platinum]
type = device
vendor = Magellan
packaging = handset
reference = http://www.amazon.com/Magellan-Meridian-Platinum-Handheld-GPS/dp/B00005OLYD
engine = Motorola
interfaces = RS232
tested = 2.21
status = excellent
nmea = v1.5 APA, v1.5 XTE, v2.1 GSA
discontinued = true
notes = Reported by Chris S. Newell <chris@newellfamily.net>
[eXplorist 210]
type = device
vendor = Magellan
packaging = handset
reference = http://www.magellangps.com/assets/manuals/newprod/eXplorist%20210_US.pdf
engine = unknown
interfaces = USB
tested = regression
status = good
nmea = 2.1
notes = USB has 3 modes — 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>. Reported by paul van den berg
<paulberg@wanadoo.nl>
[Thales AC12]
type = device
vendor = Magellan
packaging = OEM module
reference = ftp://ftp.magellangps.com/OEM,%20Sensor%20&%20ADU/A12,%20%20B12,%20&%20AC12/Reference%20Material/A12,%20B12%20&%20AC12%20RM%20rev%20E.pdf
engine = unknown
interfaces = TTL
nmea = 3.0
tested = regression
status = good
pps = True
notes = Receiver comes up in silent mode, you may need to use ashctl to turn
on a default set of messages. Tested with firmware BQ00 and BQ04.
Reported by Chris Kuethe
<chris.kuethe@gmail.com>.
#% Motorola
[Oncore GT+]
type = device
vendor = Motorola
packaging = OEM module
reference = http://www.tapr.org/gps_oncorevp.html
engine = Motorola
interfaces = RS232 or TTL
tested = 2.20
nmea = 2.2
pps = True
status = good
notes = The Motorola Oncore product family has been discontinued.
RTCM input, no WAAS. In binary mode can deliver differential
correction for another Oncore GT+. Similar Motorola Oncore UT
timing receiver has less functions but better timing
accuracy. Reported by Wojciech Kazubski
<wk@ire.pw.edu.pl>.
[T805]
type = device
vendor = Motorola
packaging = GPS mouse
reference = http://www.motorola.com/motoinfo/product/detailsPf.jsp?globalObjectId=185
uses = SiRF-3
subtype = GSC3f-7879
interfaces = Bluetooth
tested = 2.35
notes = Reported by Olivier Lahaye <olivier.lahaye@free.fr>.
#% Navcom
[SF-2040G]
type = device
vendor = Navcom
packaging = survey
reference = http://www.navcomtech.com/Products/GPS/sf2040g.cfm
uses = Touchstone ASIC
interfaces = RS232, Bluetooth, Radio (untested)
tested = 2.35
status = good
nmea = 3.0
notes = Reported by Diego Berge (contact)
#% Navius
[NSA-U3]
type = device
vendor = Navius
packaging = GPS mouse
reference = http://www.navius.biz/
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = 2.24
status = excellent
notes = Included with the horrible Windows navigation software from
Rand McNally. Reported by Jeff Francis <jeff@gritch.org>
#% NaviLock
[NL-209P]
type = device
vendor = NaviLock
packaging = GPS mouse
reference = http://www.navilock.de/produkte/gruppen/3/Kabel_Empfaenger/61371_NL-209PU.html?show=spec
uses = Sony CXD2951
interfaces = USB, RS232, Bluetooth
noconfigure = True
usbchip = pl2303
tested = 2.35
nmea = 2.2
notes = When running, need to use the -b option, else the device will
hang during the GPSD probing phase and it needs to be unplugged
and reinserted. To use this device with NTPd, set the the
"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. Reported by
Jason Curl <jcurlnews@arcor.de>
[NL-302U]
type = device
vendor = NaviLock
packaging = GPS mouse
reference = http://www.navilock.de/produkte/gruppen/3/Kabel_Empfaenger/61422_NL-302U.html?show=spec
uses = SiRF-3
subtype = GSW3.2.4_3.1.00.12-SDK003P1
interfaces = USB
usbchip = pl2303
nmea = 2.34
notes = gpsprof
output can be found
here.
Reported by Beat Bolli <me+gpsd@drbeat.li>
#% NavMan
[Jupiter 20]
type = device
vendor = NavMan
packaging = chipset
reference =
uses = SiRF-2
subtype = Jupiter 21DR Firmware
interfaces = RS232
tested = 2.32
nmea = 2.2
discontinued = True
notes = Not a complete GPS, but a chipset. It is running with an external
gyro on a our self-developed board. Reported by Andreas Stricker
<andreas.stricker@fela.ch>
#% Novatel
[SuperStar II (202)]
type = device
vendor = NovAtel
packaging = OEM Module
uses = NovAtel-L1
reference = http://www.novatel.com/Documents/Manuals/om-20000077.pdf
tested = 2.38
discontinued = True
interfaces = RS232
pps = True
notes = There are quote a number of models of SuperStarII, this is a
169-613955-202 (1Hz, Carrier Phase, Timing, 19200). Other SuperStarII
boards should work. Reported by Chris Kuethe
<chris.kuethe@gmail.com>
#% Parrot
[CK3300]
type = device
vendor = Parrot
packaging = handsfree
reference = http://www.parrot.biz/uk/products/ck3300gps
engine = unknown
interfaces = Bluetooth
tested = 2.35
status = good
nmea = 2.?
notes = Reported by Andy Brown <andy@thebmwz3.co.uk>
In-car hands-free bluetooth phone and GPS device. Outputs NMEA
#% Pharos
[GPS-360]
type = device
vendor = Pharos
packaging = GPS mouse
reference = http://www.pharosgps.com/support/igps360_spec.htm
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = regression
nmea = 2.3
discontinued = True
notes = Reported by Robert Pouliot <krynos@saturnus.com>
The Pharos comes with adaptors for SDIO, CF, USB and plain RS232. Usually
ships with XTrac firmware. It is strongly recommended that this device
not be flashed with a different firmware as all reflashed receivers
tested thus far fail to work afterward. May come bundled with Microsoft
Streets and Trips.
[iGPS-500]
type = device
vendor = Pharos
packaging = GPS mouse
reference = http://www.pharosgps.com/products/proddetail.asp?prod=006_PB010_1.00&cat=141
uses = SiRF-3
subtype = GSC3f
usbchip = PL2303
interfaces = USB
tested = 2.3
notes = Reported by Aurelian Maga <aurelianmaga@yahoo.com>
#% Phonix
[BGR6205]
type = device
vendor = Phonix
packaging = GPS mouse
reference = http://www.phonix.it/html/catalogo_dettaglio.cfm?idProducts=E09B5AB7-BCDF-DF66-24853E2B4680AB2C
uses = SiRF-2
interfaces = Bluetooth
noconfigure = True
tested = 2.34
nmea = 2.2
notes = Reported by Sebastiano Zabert
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.
#% Rikaline
[GPS-6010 USB]
type = device
vendor = Rikaline
packaging = GPS mouse
reference = http://www.rikaline.com/download/GPS-6010-Manual-E.pdf
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = 2.20
nmea = 2.2
notes = Uses SiRF firmware version 2.3.2-GSW2-2.05.024-C1Prod1.1. Manufacturer
claims it is waterproof (1 meter), WAAS and EGNOS are supported.
[GPS-6010-X5]
type = device
vendor = Rikaline
packaging = GPS mouse
reference = http://www.rikaline.com/gps_receiver.htm
uses = SiRF-2
interfaces = USB
usbchip = PL2303
tested = 2.20
nmea = 2.2
notes = The USB cable is a separate item to order. You can also order an
RS232 cable or a PDA cable. Reported by Koos van den Hout,
<koos@kzdoos.xs4all.nl>
#% Royaltek
[Sapphire USB]
type = device
vendor = Royaltek
packaging = GPS mouse
reference = http://www.royaltek.com/content/view/27/27/
uses = SiRF-2
interfaces = USB
tested = 1.97
nmea = 2.2
notes = There is an RS232 variant as well, not yet tested.
[RGM-3800]
type = device
reference = http://www.royaltek.com/products_dtl.php?cid=2&id=23&argPage=1&argI=3
vendor = Royaltek
packaging = GPS mouse
uses = SiRF-2
subtype = GSC3f/LP
interfaces = USB (PL2303)
tested = regression
nmea = 3.0
notes = This is a GPS data logger with GPS mouse functionality. Before it can be
used with gpsd, the mouse functionality has to be switched on. That
can be done with the rgm3800py utility by Karsten Petersen. The author of
said tool has been very helpful to me by describing how to do that on
the
projectpage. Basically, one needs to run "rgm3800.py -d
/dev/ttyUSB0 gmouse on" before starting gpsd. Reported by
Philipp Klenze >hq.ks@web.de<
#% San Jose Navigation
[FV-18]
type = device
vendor = San Jose Navigation
packaging = OEM module
reference = http://www.sanav.com/gps_engine_board/fv-18.htm
engine = FV-18
interfaces = UART
tested = 2.0
status = good
nmea = 2.3
notes = Special gpsd support uses 8N2 and requests sentences that gpsd requires.
OEM module only, not a retail product.
[FV-25]
type = device
vendor = San Jose Navigation
packaging = OEM module
reference = http://www.tri-m.com/products/systems/fv25.html
uses = ANTARIS
subtype = TIM-LP
interfaces = UART
tested = 2.34
pps = True
notes = OEM module, available in small quantities from Tri-M
systems. The ANTARIS chipset is obsolere, replaced by
ANTARIS4. This module works in NMEA mode; gpsd also supports the
UBX binary protocol. Firmware updates are available from uBlox;
the update is strongly recommended as it fixes a number of UBX
bugs, and adds useful new features.
[FV-M11]
type = device
vendor = San Jose Navigation
packaging = OEM module
reference = http://www.sanav.com/gps_engine_board/FV-M7_FV-M11.htm
uses = MTK
subtype = 3301
interfaces = UART
status = good
tested = regression
notes = Henk Fijnvandraat
[GM-38/12V]
type = device
vendor = San Jose Navigation
packaging = GPS mouse
reference = http://www.tri-m.com/products/systems/gm38.html
engine = Furuno GN-77
interfaces = RS232
tested = 2.21
nmea = 2.x
discontinued = True
status = broken
notes = Ships bad packet checksums when it does not have a fix.
#% Techway
[TP-051]
type = device
vendor = Techway
packaging = GPS mouse
reference = http://www.techwayinc.com.tw/TP-051.htm
uses = SiRF-2
interfaces = USB
usbchip = pl2303
tested = 2.3
nmea = 2.x
discontinued = True
notes = Advertises that it is waterproof.
#% Transystem
[iGPS-M]
type = device
vendor = Transystem
packaging = GPS mouse
reference = http://www.transystem.com.tw/products/index_detail.php?mcat_no=2&cat_no=32&pno=10&ver=en
uses = uNav
interfaces = USB
usbchip = pl2303
tested = 2.28
notes = Formerly sold under the corporate name "Bona CompuTech".
Reported by Romain Goyet <r.goyet@gmail.com>
#% TomTom
[TomTom Go910]
type = device
vendor = TomTom
packaging = handsfree
reference = http://www.tomtom.com/products/product.php?ID=475&Category=0&Lid=4
engine = SiRF-3
interfaces = USB
nmea = None
status = broken
notes = This device does not have real-time data output, and is incompatible
with GPSD.
#% Trimble
[Trimble Lassen SK]
type = device
vendor = Trimble
packaging = OEM module
reference = http://www.trimble.com/lassensk2.shtml
engine = Colossus RF ASIC, Scorpion DSP
interfaces = UART
tested = 2.26
status = good
nmea = 2.1
notes = Reported by Rob Janssen.
[Trimble Lassen IQ]
type = device
vendor = Trimble
packaging = OEM module
reference = http://www.trimble.com/lasseniq.shtml
engine = Colossus RF ASIC, IO-C33 (Epson C33 RISC)
interfaces = USB,RS232
pps = True
usbchip = Silicon Labs CP2102
tested = regression
status = good
nmea = 3.0
notes = Reported by Chris Kuethe <chris.kuethe@gmail.com>
#% uBlox
[ANTARIS LEA-4H]
type = device
vendor = uBlox
packaging = OEM module
reference = http://www.u-blox.com/products/lea_4h.html
uses = ANTARIS4
tested = regression
interfaces = RS232
pps = True
notes = Reported by Andreas Stricker <andreas.stricker@fela.ch>
[ANTARIS LEA-4S]
type = device
vendor = uBlox
packaging = OEM module
reference = http://www.u-blox.com/products/lea_4s.html
uses = ANTARIS4
interfaces = USB,UART
tested = regression
notes = Reported by Ali Utku Selen <selenau@kentkart.com.tr>
[ANTARIS LEA-4T]
type = device
vendor = uBlox
packaging = OEM module
reference = http://www.u-blox.com/products/lea_4t.html
uses = ANTARIS4
interfaces = USB,UART
tested = regression
pps = True
notes = Reported by Chris Kuethe <chris.kuethe@gmail.com>
#% Wintec
[WBT-200]
type = device
vendor = Wintec
packaging = GPS mouse
reference = http://www.wintec.com.tw/en/product_detail.php?pro_id=57
engine = FastraX iTrax03
interfaces = Bluetooth, USB
usbchip = Silicon Laboratories CP2101
tested = regression
nmea = 3.0
status = good
notes = This receiver operates correctly as a generic NMEA device,
iTalk support is also functional, though switching between NMEA
and iTalk does not yet work, nor does any device configuration.
Reported by Chris Kuethe <chris.kuethe@gmail.com>
[WBT-201]
type = device
vendor = Wintec
packaging = GPS mouse
reference = http://www.wintec.com.tw/en/product_detail.php?pro_id=65
uses = ANTARIS4
interfaces = Bluetooth, USB
usbchip = Silicon Laboratories CP2101
tested = 2.33
notes = This receiver operates correctly as a generic NMEA device, UBX support
is also functional, though switching between NMEA and UBX does not yet
work, nor does any device configuration.
Reported by Espen Talberg <espental@gmail.com>
#% UniTraq
[WGM-300U]
type = device
vendor = UniTraq
packaging = GPS mouse
reference = http://www.wintec.com.tw/en/support_detail.php?cate_id=11&support_id=14
uses = Sony CXD2951
noconfigure = True
interfaces = USB
usbchip = Silicon Laboratories CP2101
tested = 2.35
nmea = 3.0
notes = This receiver operates as a generic NMEA device, the Sony
binary protocol is unsupported. The receiver seems to lock up if
too much data is thrown at it (ie. gpsd probes) thus it may
require a read-only (-b) instance of gpsd. (We say 'may' because
more recent instances of gpsd break the probe writes into pieces
interleaved with read, and may no longer trigger this problem)
Reported by Ian Darwin <ian@darwinsys.com>