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 "Tested with" column is the last
gpsd
version with which this receiver is known to have
been successfully tested. It is likely that later releases will
support the receiver, especially if there is a
in this column;
this means we have a regression test load for the
device that is checked before each release.
Vendors are listed in alphabetical order.
Warning: the baudrate-hunting code in gpsd
tickles serious firmware bugs on some Bluetooth and USB devices.
These bugs may send affected GPSes catatonic. See this bug warning for a description
of the problem. Where possible, we indicate this in the device table.
Icons used in the table:
gpsd
has minor problems or lag
recognizing the device, but reports are complete and correct.gpsd -b
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 gpsd
, which interleaves probe writes with the
first few packet reads.gpsd
from a binary package,or did "scons
udev-install" from the source distribution, this should mean you never
have to launch gpsd
manually; the udev system will launch it
for you when it sees a device of this kind go active.Note that in most cases (including the bug), poor ratings reflect problems not in
gpsd
but rather in device design and firmware so badly
botched that gpsd
cannot compensate.
In the PPS column of the table table, if just one number is given it is the manufacturer's claimed timing accuracy. If a second number is given it is a measured NTP offset.
This table is generated from a capability database in the
gpsd
source tree. Please help us enrich the database with
new devices by emailing a new device report to gpsd-dev@lists.nongnu.org.
Name | Packaging | Engine | Interface | Tested with | NMEA version | PPS | Notes |
---|---|---|---|---|---|---|---|
Adafruit | |||||||
Ultimate GPS HAT | HAT | MT3339 | Raspberry Pi HAT,PPS | 3.14 | 3.01 | No | Built-in antenna with connector for external antenna. Good, not great sensitivity with built-in antenna. Built-in RTC and battery. Reported by Gary E. Miller <gem@rellim.com>. |
Adapt Mobile | |||||||
AD-500 | mouse | Nemerix | Bluetooth, USB | 2.32 | 3.01 | No | NemeriX has gone into liquidation as of Jan 2009). It's funny, they didn't understand why they should give me an unencumbered protocol techdoc. Reported by Dennis van Zuijlekom <tmib@xs4all.nl>.. |
Altina | |||||||
GBT709 | handset | SiRF-3 | Bluetooth | 2.35 | 3.01 | No | 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>. |
Axiom | |||||||
Sandpiper | OEM module | SiRF-1 | RS-232,PPS | 2.34 | 2.2 | ? | 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. |
BeStar | |||||||
BN-880 | OEM module | M8030-KT | LV RS-232,PPS | 3.14 | No | 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. Reported by Gary E. Miller <gem@rellim.com>. | |
Billionton | |||||||
Billionton CF-GPS | mouse | SiRF-2 | CF | 2.16 | 2.2 | No | 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>.. |
Bluenext | |||||||
BN-901S | mouse | Skytraq Venus 6 | Bluetooth | 2.39 | No | Device reports protocol as "Generic NMEA" without a version number. Purchased retail (30GBP) to work with a Nokia 5233 - which is does well. Best performing GPS receiver I have seen - fast fix and robust against obstructions to sky view. Reported by Andrew Gray <andy_r_gray@hotmail.com>. | |
Canmore | |||||||
GT-730F | mouse | SKYTRAK | USB | 2.33 | 3.01 | No | Reported by Rene Warren <warrenlr@gmail.com>. |
Central Pacific | |||||||
CPIT GP-27 | mouse | Nemerix | Bluetooth | 2.28 | 3.01 | No |
|
Columbus | |||||||
V900 | mouse | MTK | Bluetooth | 2.38 | 3.01 | No | Device is also a GPS-Logger Reported by Konstantin Ristl <konstiristl@gmail.com>. |
Delorme | |||||||
EarthMate | mouse | Zodiac | RS-232 | 2.0 | 2.2 | No | This device was supported by GPSD up to release 2.96, but some bug introduced after that interfered with it until support was restored after 3.6. |
EarthMate USB | mouse | SiRF-2 | USB | 2.5 | 2.2 | No | 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. |
TripMate | mouse | Zodiac | RS-232 | 2.0 | 2.2 | No | Discontinued sometime before November 1998. |
Digital Yacht | |||||||
AIT250 | handsfree | unknown | RS-232 | No | Both a Class B AIS transceiver and a GPS. Reported by Jan Veninga <veninga@familiemail.nl>. | ||
EuroTronics | |||||||
Blumax GPS009 | mouse | SiRF-3 | Bluetooth | 3.01 | No | 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@php.net>. | |
Eurotech | |||||||
Com-1289 | OEM module | FastraX iTrax03 | RS-232 | No | Reported by Simon Le Pape <simon.le-pape@hotmail.fr>. | ||
Fastrax | |||||||
IT520U | OEM module | MTK | USB | 2.95 | No | Reported by Kai Scharwies <scharwies@imst.de>. | |
Garmin | |||||||
Foretrex 201 | handset | SiRF-3 | RS-232 | 2.95 | 3.0 | No | 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. Reported by Anders Lund <anders@alweb.dk>. |
GPS 152 | handheld | unknown | FTDI | 3.6 | 2.3 | No | Reported by Erkki Laasonen <erkki.laasonen@gmail.com>. |
GPS-25LP | OEM module | Garmin | RS-232 | 2.0 | No | Discontinued embedded module. Reported by Daniele Giangrazi <daniele.giangrazi@elital.net>. | |
GPSmap 76S | handset | unknown | USB | 2.94 | 2.3 | No | When the GPSmap 76S is placed into simulator mode, for some unknown reason, both the xgps and cgps clients display "n/a" in the time field. However, the lat., long., and altitude fields are being displayed correctly. Using gpspipe -r is appears that the $GPGLL message is sending out the UTC time in the HHMMSS format (Note: There are no fractional seconds being generated) Reported by Brad Skillman <brad.skillman@cobham.com>. |
Garmin 38 | handset | Garmin | RS-232 | 2.0 | No | Start-of-cycle is RMC. 2-second cycle time, 1 fix per cycle. Reported by Pascal F. Martin <pascal.martin@cox.net>. | |
Garmin 48 | handset | Garmin | RS-232 | 2.0 | No | 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 here. | |
Garmin GPS 10x | mouse | SiRF-3 | Bluetooth | 2.95 | 2.0 and 2.30 | No | 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. Reported by David Ludlow <davel@adsllc.com>. |
Garmin GPS 60 | handset | Garmin | USB, RS-232 | 2.33 | 3.01 | No | Reported by Diego Berge <gpsd@nippur.net>. |
Garmin GPS 76 | handset | Garmin | RS-232 | 2.39 | 2.3 | No | 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 garmin_gps is not needed and should not be specially loaded." Reported by Sebastian Niehaus <killedbythoughts@mindcrime.net>, Geoff Childs <dofinch-aria@yahoo.co.uk>. |
Garmin GPS-15 | OEM module | Garmin | RS-232,PPS | 2.33 | 2.0 | ? | "$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 | mouse | Garmin | RS-232 | 2.38 | 2.0 | No | 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 Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>, Amaury Jacquot <sxpert@esitcom.org>, Jeff Francis <jfrancis@gritch.org>. |
Garmin GPS-17HVS | mouse | unknown | RS-232 | 2.37 | 2.0 or 3.0 | No | Reported by Ulrich Voigt (no email address) |
Garmin GPS-17N | mouse | Garmin | RS-232 | 2.0 or 3.0 | No | The 17N has been discontinued and replaced by the 17HVS. The interface was RS-232 but used a custom RJ-45 jack. Reported by Wojciech Kazubski <wk@ire.pw.edu.pl>.. | |
Garmin GPS-18 (all but USB) | mouse | Garmin | RS-232,PPS | 2.5 | 2.0 and 2.3 | 1us 0.125s |
The RS-232 versions can 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. They will not operate indoors and require a good sky view. NTP offset quoted is at 19200bps; drops to 0.525 at 4800bps. Reported by Gary E. Miller <gem@rellim.com>. |
Garmin GPS-18 USB | mouse | Garmin | USB | 2.38 | N/A | No | The USB version requires the Linux kernel garmin_usb driver. usbfs is not required after gpsd version 2.39. 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. They will not operate indoors and require a good sky view. Reported by Gary E. Miller <gem@rellim.com>. |
Geko 201 | handset | Garmin | RS-232 | 3.0 | No | Reported by Jose Luis Domingo Lopez <jdomingo@24x7linux.com>. | |
Montana 650t | handheld | STA2065 | USB | 3.6 | No | Reported by Richard Allen <rsaxvc@gmail.com>. | |
Nuvi 650 | handsfree | SiRF-3 | USB | * | 3.0 | No | This device does not have real-time data output, and is incompatible with GPSD. |
eTrex Vista | handset | Garmin | RS-232 | 2.32 | 3.0 | No | Reported by Reed Hedges <reed@interreality.org>. |
Geostar | |||||||
GeoS-1M | OEM module | custom | TTL | 2.90 | 3.01 | No | GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its architecture includes 24 tracking channels. Reported by Viktar Palstsiuk <viktar.palstsiuk@promwad.com>. |
GlobalSat | |||||||
BC-307 | mouse | SiRF-2 | CF | 2.35 | 2.2 | No | Acceptably functional running firmware 231ES. Reported by Chris Kuethe <chris.kuethe@gmail.com>.. |
BT-318 | mouse | SiRF-2 | Bluetooth | 3.12 | 2.2 | No | Requires the -b option. Reported by Frank Nicholas <frank@nicholasfamilycentral.com>. |
BT-338 | mouse | SiRF-3 | Bluetooth | 2.13 | 3.01 | No | 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. Reported by Michal Panczyk <mpanczyk@gmail.com>. |
BU-303 | mouse | SiRF-2 | USB | 2.2 | No | 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 | mouse | SiRF-3 | USB | pre-2.29 | 2.3 | No | This receiver does not support PPS timing output. Some versions of firmware do not support WAAS, though updates may be available for a fee from GlobalSat. |
BU-353-S4 | mouse | SiRF-4 | USB | 3.11 | 3.0 | No | This receiver does not support PPS timing output. Much like the BU-353 except for using a SiRFStar IV chip. Has poor sensitivity and takes a lot longer to cold-start than the vendor claim 45 of 45 seconds. Gary Miller rates this device "DO NOT EVER BUY ONE!", observing "The big selling point of the SiRF IV is the lower power needs. Looks like they made that happen at the expense of sensitivity and timeliness of fixes." Also, has the SiRF-IV tendency to freeze when switched from binary to NMEA mode (power-cycling it unjams it). |
BU-355 | mouse | SiRF-3 | USB | 3.10 | 2.3 | No | This receiver does not support PPS timing output. Does support WAAS/EGNOS, unlike some 353s. |
ET-332 Engine Board | OEM module | SiRF-3 | TTL | No | This is an OEM module but it is available in small quantities. Reported by Val Schmidt <vschmidt@ccom.unh.edu>. | ||
MR-350P | mouse | SiRF-3 | RS-232,PPS | 3.3 | 3.01 | 50ns ? |
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. Reported by Gary E. Miller <gem@rellim.com>, Tony Hain <tony@tndh.net>. |
MR-350P S4 | mouse | SiRF-4 | RS-232,PPS | 3.3 | 3.01 | ? | Some SiRFstar IV chips require a firmware update to fix PPS output. GlobalSat does not seem to be aware of this problem, and the patch must be sourced elsewhere. A copy is available from the Internet Archive: Timer_Init1PPSOut_Patch. The supplied cable set (BR305-RS232) does not pass the PPS pin through. PPS is TTL and must be externally converted. Reported by Joe Jamison <joe@smaklab.com>. |
ND-100S | mouse | SiRF-3 | USB | 2.95 | No | SirfDemo can be used to configure the product. Reported by George E Farmer <gefgef@hotmail.com>. | |
ND100 | mouse | MSB2122 | USB | 2.38 | 3.0 | No | May ship with broken firmware that incorrectly reports the current year (2009) as 1953. A firmware update is available to resolve this issue. Reported by Arnaud Le Meur <arnaudlemeur@free.fr>. |
TripNav TN-200 | mouse | SiRF-2 | USB | 2.2 | No | 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 | mouse | SiRF-2 | CF | 2.2 | No | Sometimes sold under the brand name "Rayming", but that vendor seems to have disappeared. Chipset said to be SiRF 2 but the output looks more like old Garmin GPSes. Reported by Pascal F. Martin <pascal.martin@cox.net>. | |
HAB Supplies | |||||||
HAB-GPSPI | OEM module | unknown | TTL | 3.6 | No | Reported by mayer@iiasa.ac.at. | |
Haicom | |||||||
HI-204E | mouse | Evermore BBP1202 | USB | 2.6 | 2.2 | No | Probably uses PL2303 but we have not verified this. |
HI-204S | mouse | SiRF-2 | USB | 3.12 | 2.2 | No | SiRF firmware level 231ES (XTrac). Haicom provided a test unit. Manual states incorrectly that VTG is off by default. |
HI-303S | handsfree | SiRF-3 | RS-232 | 2.25 | 2.2 | No | 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 with XTrac firmware. Reported by Denis Perchine <dyp@perchine.com>. |
HI-305N | mouse | Nemerix | CF | 3.01 | No | Adaptors for RS-232, USB, and Bluetooth operation are available. Reported by David Findlay <dave@davsoft.com.au>. | |
Holux | |||||||
GM-210 | mouse | SiRF-2 | RS-232 | 2.2 | No | 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 one, including the split reporting cycle. Reported by Patrick L. McGillan <pmcgillan@pateri.com>.. | |
GPSlim 236 | mouse | SiRF-3 | Bluetooth | 2.2 | No | 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 -> RS-232, need cable GR230-A1(RS-232 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>. | |
GR-230 | mouse | SiRF-2 | Bluetooth | 2.19 | 2.2 | No | 4 color LED showing: Bluetooth, Navigation Update and Battery and Charger Rating Indication. FLASH based program memory. Firmware upgradeable through serial interface. Water resistant. |
Holux GR-239 | mouse | SiRF-3 | Bluetooth, USB | 2.36 | 2.2 | No | Bluetooth operation requires -b option. Powered from a car cigarette-lighter. |
M-241 | mouse | MTK | Bluetooth, USB | 2.37 | 3.01 | No | 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 speed 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 These guys make fish-finders that incorporate GPSes | |||||||
Matrix-37 | handsfree | unknown | RS-232 | No | Depth finder and water-temperature sensor. Reported by Carl Brown <cbsled@verizon.net>. | ||
Jackson Labs | |||||||
FireFly-II | OEM module | UBLOX NEO-5Q | RS-232,PPS | 50ns ? |
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 if GPS reception is lost. Reported by Said Jackson <saidjack@aol.com>. | ||
Firefly-1a | OEM module | UBLOX NEO-5Q | RS-232,PPS | ? | 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. Reported by Don Weeks <don.l.weeks.jr@gmail.com>, Said Jackson <saidjack@aol.com>. | ||
LyconSys | |||||||
GPSMOD1 | mouse | ANTARIS5 | USB | 2.95 | 2.3 | No | Reported by info@lyconsys.com. |
Magellan Now owns what used to be the Thales and Asht product lines | |||||||
315 | handset | unknown | RS-232 | No | Reported by Angel Marques Mateu <amarques@cgf.upv.es>. | ||
EC-10X | handset | Zodiac | RS-232,PPS | 2.2 | ? | It was cool in its day, now a dinosaur mainly good for regression testing. NMEA time is accurate to about 500mS. Start of cycle is GPRMC on odd seconds, GPRMB on even seconds. Reported by Gary E. Miller <gem@rellim.com>. | |
Meridian Platinum | handset | Motorola | RS-232 | 2.21 | v1.5 APA, v1.5 XTE, v2.1 GSA | No | Reported by Chris S. Newell <chris@newellfamily.net>. |
Thales AC12 | OEM module | unknown | TTL,PPS | 3.0 | 250ns ? |
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>. | |
Triton 400 | handset | SiRF-3 | USB | 3.8 and 3.5 | 2.1 | No | 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. Reported by James Gerlach <jpgerlach@gmail.com>. |
eXplorist 110 | handset | unknown | USB | 2.1 | No | Reported by rickyconnell@gmail.com. | |
eXplorist 210 | handset | unknown | USB | 2.1 | No | 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>. | |
Motorola Motorola has exited the GPS business. The OnCore line of GPSes is now sold by Synergy Systems LLC | |||||||
Oncore GT+ | OEM module | Motorola | RS-232 or TTL,PPS | 2.20 | 2.2 | 50ns ? |
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 | mouse | SiRF-3 (GSC3f-7879) | Bluetooth | 2.35 | 3.01 | No | 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. Reported by Reported by Olivier Lahaye <olivier.lahaye@free.fr>. |
NavMan | |||||||
Jupiter 20 | chipset | SiRF-2 (Jupiter 21DR Firmware) | RS-232 | 2.32 | 2.2 | No | 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>. |
Navcom | |||||||
SF-2040G | survey | Touchstone ASIC | RS-232, Bluetooth, Radio (untested) | 2.35 | 3.0 | No | Reported by Diego Berge <gpsd@nippur.net>. |
NaviLock | |||||||
BT-451 | mouse | ANTARIS4 | USB | 2.39 | No | Uses the ANTARIS4 ATR062x variant. Reported by Mindaugas <mindedie@zebra.lt>. | |
NL-209P | mouse | Sony CXD2951 | USB, RS-232, Bluetooth | 2.35 | 2.2 | No | 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 | mouse | SiRF-3 (GSW3.2.4_3.1.00.12-SDK003P1) | USB | 2.34 | No | gpsprof output can be found
here. Reported by Beat Bolli <me+gpsd@drbeat.li>. |
|
NL-402U USB | mouse | u-blox5 GPS & GALILEO SuperSense | USB | No | Starts with RMC, ends with GLL. Reported by Klaus Plöger <k.ploeger@gastradata.de>. | ||
NL-551EUSB | OEM module | u-blox5 GPS & GALILEO SuperSense | TTL | 3.5 | 2.3 | No | Reported by Bas van Duijnhoven <b.duijnhoven@chello.nl>. |
NL-8002U | mouse | LEA-8H | Other | 3.15 | V3.01 | No | Reported by Manfred Günzl <osb_mgu@gmx.de>. |
Navis Engineering Bureau | |||||||
CH-4711 | mouse | CH-4706 | USB | 3.0? | No | 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 called BINR with more capabilities. Reported by walkie@mail.ru. | |
NAVIOR-24 | OEM module | CH-4701 | TTL | No | NAVIOR-24 is the single board 24-channel navigation OEM receiver supporting GLONASS/GPS systems. Reported by Viktar Palstsiuk <viktar.palstsiuk@promwad.com>. | ||
Navisys | |||||||
GR-300 | mouse | SiRF-3 | USB | 2.38 | 3.0 | No | 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 with no problems. Approx £40 per dongle. Reported by sk1ppy14@yahoo.co.uk. |
GR601-W | mouse | LEA-6H | USB,PPS | 3.12 | 1ms ? |
Also known as the Macx-1, this is the USB variant of the GR601, customized for timing use by connecting 1PPS to DCD and capable of delivering time to 1ms accuracy. The best indoor performer I have tested. Has one odd quirk: UBX reporting can be turned on, but NMEA cannot be turned off. Reported by Eric S. Raymond <esr@thyrsus.com>.. | |
GR701-W | mouse | ublox-7 | USB,PPS | 3.21 | 2.3 | ? | Reported by James Browning <jamesb.fe80@gmail.com>. |
GR8013-W | mouse | LEA-8H | PL2303 | 3.15 | 2.3, 4.1 | No | Reported by Marc Thielemann <marc.thielemann@biama.de>. |
Navius This vendor has also traded as "Navisky". | |||||||
NSA-U3 | mouse | SiRF-2 | USB | 2.24 | 2.2 | No | Included with the horrible Windows navigation software from Rand McNally. Reported by Jeff Francis <jeff@gritch.org>. |
Nokia | |||||||
LD-4W | mouse | SiRF-3 | Bluetooth | 2.39 | 3.01 | No | I first tried gpsd package from Ubuntu 9.10, which broke device on probe. Luckily this device has 'reset' function by pressing power button for 10 sec. Then I recompiled gpsd with only support for Generic NMEA and SiRF binary and with fixed speed (--enable-fixed-port-speed=9600). Now device works in sirf mode, and does not break on probe. Reported by jussi.kivilinna@mbnet.fi. |
NovAtel | |||||||
SuperStar II (202) | OEM Module | NovAtel-L1 | RS-232,PPS | 2.38 | 2.20 | ? | There are quite 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 | handsfree | unknown | Bluetooth | 2.35 | 2.? | No | In-car hands-free bluetooth phone and GPS device. Outputs NMEA Reported by Andy Brown <andy@thebmwz3.co.uk>. |
Pharos | |||||||
GPS-360 | mouse | SiRF-2 | USB | 2.3 | No | The Pharos comes with adaptors for SDIO, CF, USB and plain RS-232. 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. Reported by Robert Pouliot <krynos@saturnus.com>. | |
iGPS-500 | mouse | SiRF-3 (GSC3f) | USB | 2.3 | 3.01 | No | 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. Reported by Aurelian Maga <aurelianmaga@yahoo.com>. |
Phonix | |||||||
BGR6205 | mouse | SiRF-2 | Bluetooth | 2.34 | 2.2 | No | 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 (no emal address) |
QGP Supply | |||||||
Quescan Q1064 | mouse | ublox-8 | USB | 3.21 | No | Reported by James Browning <jamesb.fe80@gmail.com>. | |
Qstarz | |||||||
BT-Q818 | mouse | MTK | Bluetooth | 2.92-4 | 3.01 | No | Had to use the -b option. Reported by jason.komut+gpsd@gmail.com. |
RF Solutions | |||||||
GPS-320FW | chipset | SE4100L | TTL | 3.01 | No | Has a binary protocol documented 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 "$PLCS,REV,PLN012054S07,070312,145743" at reset, not documented. May actually be manufactured by Unitraq as the GP-320FW. Reported by Stoo <f4eru@free.fr>. | |
Rikaline | |||||||
GPS-6010 USB | mouse | SiRF-2 | USB | 2.20 | 2.2 | No | 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 | mouse | SiRF-2 | USB | 2.20 | 2.2 | No | The USB cable is a separate item to order. You can also order an RS-232 cable or a PDA cable. Reported by Koos van den Hout <koos@kzdoos.xs4all.nl>. |
Royaltek | |||||||
RGM-3600 | mouse | SiRF-3 | USB | 2.37 | 3.0 | No | Works out of the box. Reported by Stijn Ghesquiere <stijn@applesnail.net>. |
RGM-3800 | mouse | SiRF-2 (GSC3f/LP) | USB (PL2303) | 3.0 | No | This is a GPS data logger with 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>. | |
Sapphire USB | mouse | SiRF-2 | USB | 1.97 | 2.2 | No | There is an RS-232 variant as well, not yet tested. |
Saab | |||||||
Saab R4 | other | Pilot Plug | Other | 2.95 | No | This is data from the PilotPlug, AIS + NMEA from various instruments on a Transas bridge. This is not normal GPS data. Pilotplugs are RS422, 38400 8N1. This data is obtained via a Moxa UPort 1130 using Minicom. GPSD does not work well with the UPort 1130, but the data is recognised (but not all NMEA sentences). This is from a simulator but with real equipment. Reported by vwf@vulkor.net. | |
San Jose Navigation | |||||||
FV-18 | OEM module | FV-18 | UART | 2.0 | 2.3 | No | Special gpsd support uses 8N2 and requests sentences that gpsd requires. OEM module only, not a retail product. |
FV-25 | OEM module | ANTARIS (TIM-LP) | UART,PPS | 2.34 | 2.3 | ? | OEM module, available in small quantities from Tri-M systems. The ANTARIS chipset is obsolete, 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 | OEM module | MTK | UART | No | Reported by Henk Fijnvandraat (no email address). | ||
GM-38/12V | mouse | Furuno GN-77 | RS-232 | 2.21 | 2.x | No | Ships bad packet checksums when it does not have a fix. |
Sejat | |||||||
SJ-5210 | mouse | SiRF-3 | USB | 2.92 | No | Page that comes with it states: NMEA 0183 - CGA, GSA, GSV, RMC Baud Rate - 4800 bps; Datum WGS-84 SiRF Star III 20-channel -159 dBm sensitivity Frequency L1, 1575.42 Mhz, C/A Code: 1023 Mhz Chip Rate Acq time: Hot start 1 sec/ warm start 38 sec/cold start 42 sec (ave) WAAS/EGNOS supported Do not know (but doubt) device handles baud rate changes. Reported by rickyrockrat <gpib@rickyrockrat.net>. | |
SkyTraq | |||||||
Venus634LP | OEM module | SkyTraq Venus 6 | TTL | 2.90 | 3.01 | No | Supports A-GPS from the SkyTraq FTP server. Reported by Viktar Palstsiuk <viktar.palstsiuk@promwad.com>. |
Sure | |||||||
SKG16B | OEM module | MTK | Bluetooth, USB, RS-232,PPS | 3.14 | 3.01 | 50ns ? |
See David Taylor's page: http://www.satsignal.eu/ntp/Sure-GPS.htm Reported by Sanjeev Gupta <ghane0@gmail.com>. |
Techway This vendor has dropped off the web | |||||||
TP-051 | mouse | SiRF-2 | USB | 2.3 | 2.x | No | Advertises that it is waterproof. |
Telit | |||||||
SL869 | OEM module | STA8088 | TTL | No | Reported by Arn <arnerro@gmail.com>. | ||
TomTom | |||||||
Mark II Bluetooth GPS | mouse | SiRF-3 | Bluetooth | 2.36 | Version 2.2 | No | I use this GPS as a time source. I use a time1 parameter of -1.4 in /etc/ntp.conf, but then it appears to provide time reliably within 100ms and only limited sky view. Reported by Jose Baars peut@peut.org. |
TomTom Go910 | handsfree | SiRF-3 | USB | None | No | This device does not have real-time data output, and is incompatible with GPSD. | |
Transystem | |||||||
737A+ Bluetooth | mouse | MTK | Bluetooth | 3.2 | 3.01 | No | USB ID: 0e8d:3329. Bluetooth (V1.2) and USB (V2) output. Linux sees the USB as a cell phone (/dev/ttyACM0). Seems a tad less sensitive than a SiRF III, but has 66 channels. Uses replaceable Lithium Ion battery that charges from the mini-USB connector. Small yet 32 hour runtime on a single charge. Reported by Gary E. Miller <gem@rellim.com>. |
iGPS-M | mouse | uN3010 | USB | 2.28 | 3.01 | No | Formerly sold under the corporate name "Bona CompuTech". Reported by Romain Goyet <r.goyet@gmail.com>. |
Trimble | |||||||
Accutime Gold | other | Trimble custom | RS-232 | 3.9 | No | Reported by Venkatesh Sandilya <vsandilya@gmail.com>. | |
Trimble BX960 | OEM module | BD960 | Ethernet | No | Firmware versoon 4.00, dated 2009-03-10 Reported by Miika Ojanen <mojanen@hytti.uku.fi>. | ||
Trimble Lassen IQ | OEM module | Colossus RF ASIC, IO-C33 (Epson C33 RISC) | USB,RS-232,PPS | 3.0 | 50ns 0.675s |
Reported by Chris Kuethe <chris.kuethe@gmail.com>. | |
Trimble Lassen SK | OEM module | Colossus RF ASIC, Scorpion DSP | UART | 2.26 | 2.1 | No | Reported by Rob Janssen (no email address) |
UniTraq | |||||||
UD731 | dongle | Skytraq Venus 524c | USB | 3.4 | 3.01 | No | 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. Reported by Reported by Eric S. Raymond <esr@thyrsus.com>. |
WGM-300U | mouse | Sony CXD2951 | USB | 2.35 | 3.0 | No | 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 Reported by Ian Darwin <ian@darwinsys.com>. |
Variotek | |||||||
VT-BT-204 | mouse | Skytraq Venus 6 | Bluetooth | No | Reported by <claus.seitter@arcor.de> Claus Seitter. | ||
Wintec | |||||||
WBT-200 | mouse | FastraX iTrax03 | Bluetooth, USB | 3.0 | No | 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 | mouse | ANTARIS4 | Bluetooth, USB | 2.33 | 2.3 | No | 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>. |
iTrek | |||||||
M3 | mouse | SiRF-3 | Bluetooth | 2.28 | 3.01 | No | 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>. |
u-blox | |||||||
ANTARIS LEA-4H | OEM module | ANTARIS4 | RS-232,PPS | 2.3 | ? | Sends 'E' in second field of GSA record, not an NMEA value. Actually sends '6' in the GGA rating record for dead-reckoning fixes. (This behavior reported on the 4H chipset.) Reported by Andreas Stricker <andreas.stricker@fela.ch>. | |
ANTARIS LEA-4S | OEM module | ANTARIS4 | USB,UART | 2.3 | No | Sends 'E' in second field of GSA record, not an NMEA value. Actually sends '6' in the GGA rating record for dead-reckoning fixes. (This behavior reported on the 4H chipset.) Reported by Ali Utku Selen <selenau@kentkart.com.tr>. | |
ANTARIS LEA-4T | OEM module | ANTARIS4 | USB,UART,PPS | 2.3 | 50ns ? |
Sends 'E' in second field of GSA record, not an NMEA value. Actually sends '6' in the GGA rating record for dead-reckoning fixes. (This behavior reported on the 4H chipset.) Reported by Chris Kuethe <chris.kuethe@gmail.com>. | |
EVK 6H | other | LEA-6H | USB, RS232,PPS | 3.9 | 1ms ? |
The u-blox eval kit for the LEA-6H. Has a TCXO on a miniboard in a nice aluminum case with both USB and serial output. PPS on DCD and DSR. Good Stratum 0 time source. Reported by Eric S. Raymond <esr@thyrsus.com>.. | |
EVK-5H-0 | other | LEA-5H | USB | 2.92 | 2.3 | No | Appears not to have the ANTARIS4 GSA quirk. Reported by Stephan Dierick <sac.dierick@hccnet.nl>. |
EVK-6H-0 | other | LEA-6H | R232, USB | 3.9 | 2.3 | No | This is the u-blox eval kit for the LEA-6H. Has both USB and RS232 with PPS outputs. Excellent indoor performance, and well suited for time service even though the 6H is not specialized for that. Reported by Eric S. Raymond <esr@thyrsus.com>. |
LEA 5Q | OEM module | UBLOX NEO-5Q | TTL,PPS | 2.95 | 50ns ? |
Sample contains GPGST (pseudorange noise statistics). This had to be manually enabled by sending "$PUBX,40,GST,1,1,1,0*5A\n" to the device. Reported by Thomas Sprinkmeier <thomas.sprinkmeier@gmail.com>. |
Some GPS receivers offer a 1PPS (one pulse per second) output that
GPSD is capable of passing along to ntpd
for use as an
extremely accurate clock source. These are marked as having PPS
in the table above. The "Claimed Accuracy" figures are taken
from manufacturers' data sheets, and have not been independently
verified.
Where specified, NTP time offsets have been measured by
comparison with the NTP time service and reported by
gpsd
.
Note that either a direct RS-232 connection or the "Magic Macx mod" (1PPS on the GPS chip connected to DCD on the serial-to-USB adaptor) is required for PPS. Typical gpsd/PPS users report ntp clock stability on the order of 1μs (microsecond) for RS232, 1ms (millisecond) for USB. From GPSes that are native USB but not PPS-capable, GPSD can extract time information from the serial data accurate to about 250ms.
All gpses require "raw" measurements internally to compute a navigation solution. The ability for users to postprocess these measurements is then a function of firmware and protocol support.
Receiver | Raw | Notes |
---|---|---|
NavSync | No | I asked them about raw measurements and they told me that a custom firmware build ($$$!) would be required, and that I probably wasn't authorized to get that data. |
SiRF | Partial | sirfstar1 has raw data in message 5, sirfstar2 has raw data in message 28, sirfstar3 has some raw data in message 28 but carrier phase is not available. rumor has it that carrier phase is available as a premium feature in superstar3. |
u-blox | Partial | The RXM-RAW message contains raw data. This is implemented in all Antaris chips. This is only implemented in the timing versions of Antaris4. In ublox5 it is "only available with premium feature raw data". |
Novatel SuperStarII | Partial | Message #23 contains raw measurements in carrier-phase-enabled firmwares. |
Fastrax | Yes | The "PSEUDO" message contains raw measurements |
Trimble | Yes | Packet 0x5a contains raw measurements |
Thales AC12 | Yes | The PASHR,MCA message contains raw measurements. |