1# GPS capability description file 2# 3# This file is Copyright (c) 2010 by the GPSD project 4# SPDX-License-Identifier: BSD-2-clause 5# 6# Our apologies to all Unix hackers in advance for the grubby .INI syntax, 7# we're using it because the format has good cross-Unix support in Python. 8# 9# Each section may have the following capabilities 10# 11# type = "engine", "vendor", or "device" 12# date = date of submission 13# submitter = email of submitter, name may need quoting for RFC822 14# description = Human-readable description of this item 15# packaging = A device's form factor 16# techdoc = URL to technical documentation, or at least a spec sheet 17# vendor_site = URL of a vendor site 18# vendor = vendor name 19# eval_unit = Which GPSD devs have one for testing (list) 20# engine = GPS chipset (may reference another section) 21# subtype = engine subtype or firmware revision level 22# interfaces = interface types: USB, RS-232, Bluetooth, CF, TTL, CAN. 23# May be a list. 24# usbchip = USB I/O chipset 25# pps = supports pulse-per-second precision time reporting 26# pps_accuracy = claimed PPS accuracy 27# time_offset = NTP offset 28# configurable = can the device be bricked by speed changes? 29# tested = last gpsd tested, or "regression" if we have a test load 30# nmea = NMEA version this emits, if known 31# notes = Miscellaneous notes on this item. To be interpreted as HTML 32# rating = excellent, good, fair, poor, broken, other 33# discontinued = If True, product has been discontinued 34# 35# Capability strings: 36# 37# to_nmea = if present, how to switch to NMEA 0183 mode from native binary 38# to_native = if present, how to swith to native binary mode from NMEA 39# modeset = set protocol, baud rate, 8N1 40# 41# Inheritance 42# 43# To inherit capabilities from a specified section, name the section in 44# a "uses =" attribute. Use chains are followed recursively. An attribute 45# in a section overrides all attributes of the same name in all ancestor 46# sections. 47# 48# Certain escapes in capability strings are translated: 49# 50# %b - baud rate as ASCII numeral 51# 52# A string beginning with 0x is interpreted as a sequence of paired hex bytes, 53# leading 0x not included. 54# 55# Comment lines led with "#%" are vendor section marks to be used when 56# generating an HTML table from this file. Each should consist of a vendor 57# name. 58# 59# Further notes: 60# * In the packaging feld, a "GPS mouse" is a standalone sensor in a 61# display-less case designed be used as an outbard peripheral. An 62# "OEM module" is an un-cased circuit board with edge connectors; a 63# "chipset" is what it sounds like. 64# A "handset" is a standalone GPS with a display and human-usable 65# controls. A "handsfree" is a hands-free unit with display designed for 66# mounting on a car windshield or boat dash. 67# * In the rating field: 68# "excellent" - gpsd recognizes the GPS rapidly and reliably, 69# reports are complete and correct. 70# "good" -- gpsd has minor problems or lag recognizing the device, 71# but reports are complete and correct. 72# "fair" -- Reports have minor dropouts or problems, including occasional 73# transient nonsense values. 74# "poor" -- Reports frequently have values that are wrong or nonsense. 75# "broken" -- gpsd frequently fails to recognize the device at all. 76# "other -- See Technical Notes. 77 78# 79# Chipsets (alphabetical) 80# 81 82[ANTARIS] 83type = engine 84engine = ANTARIS 85nmea = 2.3 86rating = good 87techdoc = http://www.u-blox.com/products/tim_lp.html 88discontinued = True 89notes = The ANTARIS chipset has been end-of-lifed. 90 91[ANTARIS4] 92type = engine 93engine = ANTARIS4 94techdoc = http://www.u-blox.com/products/a4products.html 95nmea = 2.3 96rating = good 97notes = Sends 'E' in second field of GSA record, not an NMEA value. 98 Actually sends '6' in the GGA rating record for dead-reckoning fixes. 99 (This behavior reported on the 4H chipset.) 100logs = ublox-lea-4h.log, ublox-lea-4s.log, ublox-lea-4t.log 101 102[BD960] 103type = engine 104engine = BD960 105nmea = 3.0? 106tested = 2.39 107notes = Spec sheet says it emits GSV, AVR, RMC, HDT, VGK, VHD, GGLK, GGA, GSA, 108 ZDA, VTG, GST, and PIT in NMEA mode. Many of these are nonstandard. 109 Also says: "JK and Binary: Trimble GSOF". Other web sources say 110 it has RTK capability. 111rating = good 112 113[FastraX iTrax03] 114type = engine 115techdoc = http://www.fastraxgps.com/products/gpsmodules/index.cfm?template=products.show.cfm&productGuid=4594da1a-503c-469c-91b2-6948043189be 116engine = FastraX iTrax03 117rating = good 118logs = com-1289.log 119notes = Start of fix cycle is RMC, end is GGA (GSVs may come after). 120 121[Garmin-Native] 122type = engine 123engine = Garmin 124description = There are several versions; the differences are not clear. 125techdoc = http://www.garmin.com/support/commProtocol.html 126rating = good 127 128[LEA-5H] 129type = engine 130engine = LEA-5H 131nmea = 2.3 132rating = good 133tested = 2.92 134notes = Appears not to have the ANTARIS4 GSA quirk. 135logs = ublox-lea-5h.log 136 137[LEA-6H] 138type = engine 139engine = LEA-6H 140nmea = 2.3 141rating = good 142tested = 3.9 143notes = Appears not to have the ANTARIS4 GSA quirk. Excellent indoors. 144 145[LEA-8H] 146type = engine 147engine = LEA-8H 148nmea = 2.3, 4.1 149rating = excellent 150tested = 3.15 151notes = Appears not to have the ANTARIS4 GSA quirk. Excellent indoors. 152logs = gr8013-w.log 153 154[MSB2122] 155type = engine 156engine = MSB2122 157nmea = 2.3 158rating = good 159techdoc = http://www.mstar-europe.com/products.php 160notes = Code-named "Poseidon 2", this appears to be a MIPS core. May 161 ship with serious bugs that cause bogus fixes or hard crashes. 162 163[MT3339] 164type = engine 165nmea = 3.01 166engine = MT3339 167rating = good 168techdoc = http://www.adafruit.com/datasheets/PMTK_A11.pdf 169notes = 10Hz update. 170 171[MTK] 172type = engine 173nmea = 3.01 174engine = MTK 175rating = good 176techdoc = http://www.fastraxgps.cn/download/NMEA_manual_for_Fastrax_IT500_Series_GPS_receivers.pdf 177notes = We have seen two versions of this, the MTK3301 and MTK3329. The 178 technical-documentation link describes the 3329, but we think the 3301 179 is compatible for GPSD purposes. 180 181[Nemerix] 182type = engine 183engine = Nemerix 184nmea = 3.01 185rating = good 186notes = NemeriX has gone into liquidation as of Jan 2009). It's funny, they 187 didn't understand why they should give me an unencumbered protocol 188 techdoc. 189 190[NovAtel-L1] 191type = engine 192engine = NovAtel-L1 193techdoc = http://www.novatel.com/Documents/Manuals/om-20000086.pdf 194nmea = 2.20 195rating = good 196notes = Seems to be built around the Zarlink GP4020. 197 198[Pilot Plug] 199type = engine 200engine = Pilot Plug 201rating = good 202 203[SE4100L] 204type = engine 205nmea = 3.01 206rating = fair 207notes = Does not handle dates after the 10-bit GPS week rollover in 2019 well. 208logs = gp-320fw-2019-03-28.log, gp-320fw-2019-03-28.log-overflow, gp-320fw-2019-03-28.log-coldboot 209 210[SirfGeneric] 211type = engine 212description = Capabilities generic to all SiRF chips 213# Sets 4800 baud shipping GGA+GSA+GSV+RMC 214to_nmea = 0xa0a200188102010100000101050101010000000100010001000112c00000b0b3 215to_native = $PSRF100,0,%b,8,1,0 # Sets 8N1 with specified speed 216 217[SiRF-1] 218type = engine 219description = Version 1 of the SiRF GPS engine 220engine = SiRF-1 221nmea = 2.2 222uses = SirfGeneric 223tested = 2.34 224rating = good 225logs = ublox-sirf1.log 226notes = ublox-sirf1.log was made from a device with ublox firmware and 227 may not be typical of SiRF-1 chips. 228 229[SiRF-2] 230type = engine 231description = Version 2 of the SiRF GPS engine 232engine = SiRF-2 233# Later versions may do 2.3 234nmea = 2.2 235uses = SirfGeneric 236tested = 2.37 237rating = good 238logs = bu303b-nofix.log, bu303-climbing.log, bu303-moving.log, 239 bu303-nofix.log, bu303-stillfix.log, haicom-305N.log, holux-gm-210.log, 240 pharos-360.log, tn200-all.log, tn200.log, tn204.log 241notes = The bu* logs are in native binary format; the Haicom, Holux, Pharos, 242 and TripNav logs in NMEA. NMEA starts with GGA and ends with RMC. The 243 tn204 NMEA looks remarkably like older Garmin cruft and may be emulating 244 one, including the split reporting cycle. 245 246[SiRF-3] 247type = engine 248description = Version 3 of the SiRF GPS engine 249engine = SiRF-3 250nmea = 3.01 251uses = SirfGeneric 252rating = good 253logs = blumax-gps009.log, gpslim236.log, motorola-t805.log, rgm3800.log, et-332.log, tomtom-mkII.log 254notes = The Blumax log is in NMEA mode. Start of cycle is GGA, End of cycle 255 is RMC. Some variants (like the Blumax) emit ZDA before GGA; others 256 (like the GPSlim 1236, Motorola T805, RGM3800) do not. 257 258[SiRF-4] 259type = engine 260description = Version 4 of the SiRF GPS engine 261engine = SiRF-4 262nmea = 3.01 263uses = SirfGeneric 264rating = poor 265logs = bu353s4.log 266notes = Low power usage, but poor sensitivity and very long startup. 267 Resets to 4800N1 every time it is unplugged. Has a tendency to freeze 268 when switched from binary to NMEA mode (unplugging it fixes this). 269 270[SiRF-5] 271type = engine 272description = Version 5 of the SiRF (Sirfstar V) GPS engine 273engine = SiRF-5 274nmea = Unknown 275uses = SirfGeneric 276rating = bad 277logs = sirfstarv.log 278notes = Undocumented by Qualcomm, thus unsupported in binary mode by 279 gpsd. 280 281[SiRF-TriG] 282type = engine 283description = Chinese variant of the SiRF GPS engine 284engine = SiRF-TriG 285nmea = 4.00 286uses = SirfGeneric 287#rating = poor 288logs = beidou-bd.log, beidou-gb.log 289notes = SiRF-IV variant produced for the Chinese market; it handles the 290 Beidou and GLONASS constellations as well as US GPS. The main 291 variant is described by the Chinese standard "Technical 292 Specification of Communication Protocol for BDS Compatible 293 Positioning Module" (TSCPB) and uses the talker ID BD. This 294 standard is not available in English translation. There is a 295 variant with closer NMEA 4.00 conformance that uses the talker 296 ID GB. 297 298[Skytraq S2525F8-BD-RTK] 299type = engine 300description = RTK Receiver with cm accuracy 301engine = Skytraq Venus 8 302nmea = 3.01 303rating = good 304tested = 3.16 305logs = skytraq.log, skytraq-fix.log 306notes = Supports GPS, BDS, QZSS, and SBAS. Tracks 28 satellites. 307 gpsd 3.17 has basic support for some Skytraq binary. 308 Can take RTCM 3.0, 3.1, or raw data from a base station for up to 309 cm accuracy. 310 Measured CEP(50) with partial sky view of 1.9m. 311 RTCM/RAW mode untested with gpsd. 312 313[Skytraq Venus 6] 314type = engine 315nmea = 3.01 316rating = good 317tested = 2.90 318 319[Sony CXD2951] 320type = engine 321techdoc = http://gpsd.googlecode.com/files/cxd2951-commands.pdf 322engine = Sony CXD2951 323rating = good 324 325[STA8088] 326type = engine 327nmea = 2.2 328rating = good 329tested = 3.7 330notes = From ST Microelectronics 331 332[Touchstone ASIC] 333type = engine 334engine = Touchstone ASIC 335rating = good 336techdoc = http://www.navcomtech.com/Products/GPS/Touchstone.cfm 337 338[uNav] 339type = engine 340engine = uN3010 341nmea = 3.01 342notes = uNav was acquired by Atheros in 2007. They have inherited 343 one GPS product, now designated uN3010. 344rating = good 345 346[UBLOX M8030-KT] 347type = engine 348engine = M8030-KT 349rating = good 350tested = 3.14 351notes = Supports GPS, GLONASS, Galileo, BeiDou, QZSS and SBAS. a.k.a NEO-M8N 352logs = neo-m8n.log 353 354[UBLOX NEO-5Q] 355type = engine 356nmea = 2.3 357rating = good 358tested = 2.39 359notes = Supports WAAS. 360 361[Zodiac] 362type = engine 363engine = Zodiac 364nmea = 2.2 365tested = 2.0 366techdoc = http://www.gpskit.nl/downloads-en.htm 367notes = This chip was made by Rockwell International. It was 368 also known as the Jupiter. It has been EOLed. 369rating = good 370logs = zodiac.log 371 372# 373# Vendors (alphabetical by vendor) 374# 375 376[Adafruit] 377type = vendor 378vendor_site = https://www.adafruit.com/ 379 380[Altina] 381type = vendor 382vendor_site = http://www.altina.com 383 384[Adapt Mobile] 385type = vendor 386vendor_site = http://www.adapt-mobile.com> 387 388[Axiom] 389type = vendor 390vendor_site = http://code.google.com/p/gpsd/downloads/detail?name=SiRF-Axiom.pdf&can=2&q= 391 392[BeStar] 393type = vendor 394vendor_site = http://www.sz-beitian.com/ 395 396[Billionton] 397type = vendor 398vendor_site = http://www.billionton.com/english/index.htm 399 400[Bluenext] 401type = vendor 402vendor_site = http://www.bluenext.co.uk/ 403 404[Canmore] 405type = vendor 406vendor_site = http://www.canmore.com.tw/ 407 408[Columbus] 409type = vendor 410vendor_site = http://www.columbus-gps.de/ 411 412[Central Pacific] 413type = vendor 414vendor_site = http://www.cpit.com 415 416[Delorme] 417type = vendor 418vendor_site = http://www.delorme.com 419 420[Digital Yacht] 421type = vendor 422vendor_site = http://digitalyacht.mesltd.co.uk/ 423 424[Eurotech] 425type = vendor 426vendor_site = http://www.eurotech-inc.com/ 427 428[Fastrax] 429type = vendor 430vendor_site = http://www.fastraxgps.com/ 431 432[EuroTronics] 433type = vendor 434vendor_site = http://www.eurotronic.net/ 435 436[Garmin] 437type = vendor 438vendor_site = http://www.garmin.com 439 440[Geostar] 441type = vendor 442vendor_site = http://www.geostar-navigation.com 443 444[GlobalSat] 445type = vendor 446vendor_site = http://www.globalsat.com.tw/ 447 448[HAB Supplies] 449type = vendor 450vendor_site = http://ava.upuaut.net/?page_id=388 451 452[Haicom] 453type = vendor 454vendor_site = http://www.haicom.com.tw/ 455 456[Holux] 457type = vendor 458vendor_site = http://www.holux.com 459 460[Humminbird] 461type = vendor 462vendor_site = http://www.humminbird.com/ 463notes = These guys make fish-finders that incorporate GPSes 464 465[iTrek] 466type = vendor 467vendor_site = http://www.i-trek.jp 468 469[Jackson Labs] 470type = vendor 471vendor_site = http://jackson-labs.com/ 472 473[LyconSys] 474type = vendor 475vendor_site = http://www.lyconsys.com/index.php/en/ 476 477[Magellan] 478type = vendor 479vendor_site = http://www.magellangps.com 480notes = Now owns what used to be the Thales and Asht product lines 481 482[Motorola] 483type = vendor 484vendor_site = http://www.motorola.com/ies/GPS/products_legacy.html 485notes = Motorola has exited the GPS business. The OnCore line of 486 GPSes is now sold by <a href="http://www.synergy-gps.com/">Synergy Systems LLC</a> 487 488[Navcom] 489type = vendor 490vendor_site = http://www.navcomtech.com/ 491 492[Navis Engineering Bureau] 493type = vendor 494vendor_site = http://navis.ru/ 495 496[Navius] 497type = vendor 498vendor_site = http://www.navius.biz/ 499notes = This vendor has also traded as "Navisky". 500 501[NaviLock] 502type = vendor 503vendor_site = http://www.navilock.de 504 505[Navisys] 506type = vendor 507vendor_site = http://www.navisys.com.tw/ 508 509[NavMan] 510type = vendor 511vendor_site = http://www.navmanwirelessoem.com/ 512 513[Nokia] 514type = vendor 515vendor_site = http://www.nokia.com/ 516 517[NovAtel] 518type = vendor 519vendor_site = http://www.novatel.com/ 520 521[Parrot] 522type = vendor 523vendor_site = http://www.parrot.com/ 524 525[Pharos] 526type = vendor 527vendor_site = http://www.pharosgps.co/ 528 529[Phonix] 530type=vendor 531vendor_site = http://www.phonix.it/ 532 533[Qstarz] 534type=vendor 535vendor_site = http://www.qstarz.com/ 536 537[RF Solutions] 538type = vendor 539vendor_site = http://www.rfsolutions.co.uk 540 541[Rikaline] 542type = vendor 543vendor_site = http://www.rikaline.com 544 545[Royaltek] 546type = vendor 547vendor_site = http://www.royaltek.com/ 548 549[Saab] 550type = vendor 551vendor_site = http://www.saabgroup.com/ 552 553[San Jose Navigation] 554type = vendor 555vendor_site = http://www.sanav.com 556 557[Sejat] 558type = vendor 559vendor_site = http://sejats.blogspot.com/ 560 561[SkyTraq] 562type = vendor 563vendor_site = http://www.skytraq.com.tw/ 564 565[Sure] 566type = vendor 567vendor_site = http://stores.ebay.com/Sure-Electronics/_i.html?_nkw=gps&submit=Search&_sid=208644246 568 569[Telit] 570type = vendor 571vendor_site = http://www.telit.com/ 572 573[Transystem] 574type = vendor 575vendor_site = http://www.transystem.com.tw/ 576 577[Techway] 578type = vendor 579vendor_site = http://www.techwayinc.com.tw/ 580notes = This vendor has dropped off the web 581 582[TomTom] 583type = vendor 584vendor_site = http://www.tomtom.com/ 585 586[Trimble] 587type = vendor 588vendor_site = http://www.trimble.com/ 589 590[u-blox] 591type = vendor 592vendor_site = http://www.u-blox.de/en/ 593 594[UniTraq] 595type = vendor 596vendor_site = http://www.unitraq.com/ 597 598[Variotek] 599type = vendor 600vendor_site = http://variotek.de/ 601 602[Wintec] 603type = vendor 604vendor_site = http://www.wintec.com.tw/ 605 606# 607# Devices (alphabetical by vendor) 608# 609 610#% Adafruit 611 612[Ultimate GPS HAT] 613type = device 614packaging = HAT 615vendor = Adafruit 616techdoc = https://learn.adafruit.com/adafruit-ultimate-gps-hat-for-raspberry-pi 617interfaces = Raspberry Pi HAT 618tested = 3.14 619rating = excellent 620uses = MT3339 621pps = Yes 622submitter = Gary E. Miller <gem@rellim.com> 623notes = Built-in antenna with conenctor for external antenna. Good, not 624 great sensitivity with built-in antenna. Built-in RTC and battery. 625 626#% Altina 627 628[GBT709] 629type = device 630vendor = Altina 631packaging = handset 632techdoc = http://www.altina.com/produkty.php?destCatId=&mainCatId=13&subCatId=&prId=19 633interfaces = Bluetooth 634configurable = insane 635tested = 2.35 636uses = SiRF-3 637submitter = Benoit Panizzon <panizzon@woody.ch> 638notes = Requires the "-b" flag to prevent mode switching. If the receiver locks 639 up due to a mode switch, remove the battery for 5 to 10 minutes. 640 641#% Adapt Mobile 642 643[AD-500] 644type = device 645vendor = Adapt Mobile 646packaging = mouse 647techdoc = http://adapt-mobile.bosqom.com/default.php?page_ID=3&spage_ID=1 648uses = Nemerix 649interfaces = Bluetooth, USB 650usbchip = pl2303 651tested = 2.32 652submitter = Dennis van Zuijlekom <tmib@xs4all.nl>. 653discontinued = True 654 655#% Axiom 656 657[Sandpiper] 658type = device 659vendor = Axiom 660packaging = OEM module 661techdoc = http://code.google.com/p/gpsd/downloads/detail?name=SiRF-Axiom.pdf&can=2&q= 662uses = SiRF-1 663interfaces = RS-232 664tested = 2.34 665pps = True 666notes = The vendor is out of business, but there are lots of these still 667 around in 2006. Complete documentation for this OEM module has been 668 archived at the GPSD site. 669 670#% BeStar 671 672[BN-880] 673type = device 674vendor = BeStar 675packaging = OEM module 676uses = UBLOX M8030-KT 677interfaces = LV RS-232 678tested = 3.14 679rating = excellent 680submitter = Gary E. Miller <gem@rellim.com> 681pps = False 682notes = Vendor is in Shenzhen, China. Frequently on eBay. Sold as a 683 'Flight Control Module' as it also contains gyros and acceleromters 684 in a separate I2C bus. Does not have PPS but some resellers claim PPS. 685 686#% Billionton 687 688[Billionton CF-GPS] 689type = device 690vendor = Billionton 691packaging = mouse 692techdoc = http://www.billionton.com/english/product/CF-GPS.htm 693uses = SiRF-2 694interfaces = CF 695tested = 2.16 696submitter = Oleg Gusev <oleg@crista.uni-wuppertal.de>. 697notes = Uses SiRF firmware version 220.006.000ES. Accepts WAAS Mode Disable 698 (<code>$PSRF108,00*02</code>) and WAAS Mode Enable (<code>$PSRF108,01*03</code>) 699 controls. 700 701#%Bluenext 702 703[BN-901S] 704type = device 705engine = Skytraq Venus 6 706date = 2010-06-10 707location = 708model = BN-901S 709packaging = mouse 710interfaces = Bluetooth 711rating = excellent 712submitter = Andrew Gray <andy_r_gray@hotmail.com> 713techdoc =http://www.bluenext.co.uk/customer-support/downloads/doc_download/34-bluenext-bn-901s-gps-receiver.html 714tested = 2.39 715vendor = Bluenext 716notes = Device reports protocol as "Generic NMEA" without a version number. 717 Purchased retail (30GBP) to work with a Nokia 5233 - which is does well. 718 Best performing GPS receiver I have seen - fast fix and robust against 719 obstructions to sky view. 720logs = bn-9015.log 721 722#% Canmore 723 724[GT-730F] 725type = device 726engine = SKYTRAK 727interfaces = USB 728nmea = 3.01 729packaging = mouse 730rating = good 731submitter = Rene Warren <warrenlr@gmail.com> 732techdoc = http://www.canmore.com.tw/pdf/English%20user%20manual_GT-730F_L.pdf 733tested = 2.33 734vendor = Canmore 735notes = 736 737#% Columbus 738[V900] 739type = device 740uses = MTK 741interfaces = Bluetooth 742model = V900 743packaging = mouse 744rating = fair 745submitter = Konstantin Ristl <konstiristl@gmail.com> 746techdoc = http://www.columbus-gps.de/v-900_support.php 747tested = 2.38 748vendor = Columbus 749notes = Device is also a GPS-Logger 750 751#% Central Pacific 752 753[CPIT GP-27] 754type = device 755vendor = Central Pacific 756packaging = mouse 757techdoc = http://www.cpit.com/en/GP-27.html 758uses = Nemerix 759interfaces = Bluetooth 760tested = 2.28 761configurable = insane 762submitter = Tobias Minich <belgabor@gmx.de> 763notes = <ul> 764 <li>There are proprietary PNMRX{30[0124],603} sentences that are only sent 765 on change or by request</li> 766 <li>Several sentences can be sent to the device to change settings or 767 request information. DO NOT USE THE PNMRX100 SENTENCE TO CHANGE THE BAUD 768 RATE! This is not supported by the bluetooth chip on the device.</li> 769 <li>Settings are saved in flash powered by a backup battery and persistent 770 over connections and when you turn it off.</li> 771 <li>The syntax of the PNMRX303 message and part 4 of the PNMRX603 message 772 may differ from the syntax found in several documents on the net.</li> 773 </ul> 774 775#% Delorme 776 777[EarthMate USB] 778type = device 779vendor = Delorme 780packaging = mouse 781techdoc = https://shop.delorme.com/OA_HTML/DELibeCCtpSctDspRte.jsp?section=10043&minisite=10020 782uses = SiRF-2 783interfaces = USB 784usbchip = Cypress M8 CY7C64013 785tested = 2.5 786discontinued = True 787notes = This was the replacement for the old Zodiac version that spoke 788 Rockwell binary protocol; it in turn has been discontinued. Some 789 other sentences can be enabled. Requires a 2.6.10 or better 790 kernel for the Cypress USB-HID support. 791 792[EarthMate] 793type = device 794vendor = Delorme 795packaging = mouse 796uses = Zodiac 797interfaces = RS-232 798discontinued = True 799rating = good 800notes = This device was supported by GPSD up to release 2.96, but some bug 801 introduced after that interfered with it until support was restored 802 after 3.6. 803 804[TripMate] 805type = device 806vendor = Delorme 807packaging = mouse 808techdoc = http://vancouver-webpages.com/peter/tripmate.faq 809uses = Zodiac 810interfaces = RS-232 811discontinued = True 812notes = Discontinued sometime before November 1998. 813 814#% Digital Yacht 815 816[AIT250] 817type = device 818vendor = Digital Yacht 819engine = unknown 820packaging = handsfree 821techdoc = http://www.yachtronics.com/yachtronics/manuals/DIGITAL%20YACHT%20AIT250%20OPERATION.pdf 822interfaces = RS-232 823discontinued = False 824tested = regression 825rating = good 826submitter = Jan Veninga <veninga@familiemail.nl> 827notes = Both a Class B AIS transceiver and a GPS. 828logs = ait250.log 829 830#% Eurotech 831 832[Com-1289] 833type = device 834vendor = Eurotech 835packaging = OEM module 836techdoc = http://www.eurotech.fi/products/COM-1289.html 837engine = FastraX iTrax03 838interfaces = RS-232 839tested = regression 840rating = good 841submitter = Simon Le Pape <simon.le-pape@hotmail.fr> 842 843#% EuroTronics 844 845[Blumax GPS009] 846type = device 847vendor = EuroTronics 848packaging = mouse 849techdoc = http://www.eurotronic.net/products/produktdetails/gps_receiver.html 850uses = SiRF-3 851interfaces = Bluetooth 852configurable = insane 853tested = regression 854submitter = Hartmut Holzgraefe <hartmut@php.net> 855notes = Requires "-b" ... I had to totally drain the battery of the device 856 and let it rest for a few days before i was able to use it again 857 after a first attempt of using it with without "-b" 858 859#% Fastrax 860 861[IT520U] 862type = device 863vendor = Fastrax 864engine = MTK 865packaging = OEM module 866techdoc = http://www.fastraxgps.com/showfile.cfm?guid=5861a92d-2628-4c8b-9621-058a3435edb5 867date = 2011-02-21 868firmware = AXN_1.30,0145,Fastrax IT500 869interfaces = USB 870location = Kamp Lintfort, DE, 51deg 29min N, 6deg 32min E 871model = IT520 872rating = good 873submitter = Kai Scharwies <scharwies@imst.de> 874tested = 2.95 875logs = mtk-3329.log 876 877#% Garmin 878 879[Foretrex 201] 880type = device 881engine = SiRF-3 882date = 2010-08-26 883interfaces = RS-232 884location = Ulb?lle, DK, 55.04N 10.25E 885model = Foretrex 201 886nmea = 3.0 887notes = This device is not a conventional handfrtee unut for a car; it looks 888 like a bulky wristwatch and is meant for bicycle handlebars. It must 889 be set to NMEA output in the settings->interface page. 890packaging = handset 891rating = excellent 892submitter = Anders Lund <anders@alweb.dk> 893techdoc = http://www.garmin.com/manuals/Foretrex201_OwnersManual.pdf 894tested = 2.95 895vendor = Garmin 896discontinued = True 897logs = foretrex-201.log 898 899[Garmin GPS 10x] 900type = device 901uses = SiRF-3 902date = 2010-07-18 903model = GPS 10x 904nmea = 2.0 and 2.30 905interfaces = Bluetooth 906packaging = mouse 907rating = excellent 908submitter = David Ludlow <davel@adsllc.com> 909techdoc = http://www.garmin.com/manuals/GarminMobile10forlaptops_PDAs_TechnicalSpecifications.pdf 910tested = 2.95 911vendor = Garmin 912logs = garmin-10x.log 913 914[Garmin GPS-15] 915type = device 916packaging = OEM module 917vendor = Garmin 918techdoc = http://www.garmin.com/products/gps15/spec.html 919uses = Garmin-Native 920interfaces = RS-232 921tested = 2.33 922nmea = 2.0 923pps = True 924submitter = Jason Hecker <jhecker@wireless.org.au> 925notes = "$PGRMI,,,,,,,R" must be sent to reset the device before PPS 926 works; after about 5 minutes the PPS signal is detected properly 927 by GPSD. 928 929[Garmin GPS-16] 930type = device 931packaging = mouse 932vendor = Garmin 933techdoc = http://www.garmin.com/products/gps16/spec.html 934uses = Garmin-Native 935interfaces = RS-232 936tested = 2.38 937nmea = 2.0 938submitter = Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>, 939 Amaury Jacquot <sxpert@esitcom.org>, 940 Jeff Francis <jfrancis@gritch.org> 941notes = DGPS information in GPGGA sentence is not returned. Satellite 942 azimuths/elevations and magnetic variation information are not 943 available in binary mode. Garmin uses a nonstandard 16-bit SNR 944 scale for signal quality in GSA. Can be switched to NMEA 3.0 945 with PGRMC1. . 946 947[Garmin GPS-17N] 948type = device 949packaging = mouse 950vendor = Garmin 951techdoc = http://www.garmin.com/products/gps17/spec.html 952uses = Garmin-Native 953interfaces = RS-232 954tested = regression 955nmea = 2.0 or 3.0 956submitter = Wojciech Kazubski <wk@ire.pw.edu.pl>. 957notes = The 17N has been discontinued and replaced by the 17HVS. 958 The interface was RS-232 but used a custom RJ-45 jack. 959logs = garmin17n.log 960 961[Garmin GPS-17HVS] 962type = device 963vendor = Garmin 964packaging = mouse 965techdoc = https://buy.garmin.com/shop/shop.do?cID=158&pID=8630 966engine = unknown 967interfaces = RS-232 968tested = 2.37 969rating = good 970nmea = 2.0 or 3.0 971notes = Reported by Ulrich Voigt (no email address) 972 973[Garmin GPS-18 USB] 974interfaces = USB 975nmea = N/A 976packaging = mouse 977submitter = Gary E. Miller <gem@rellim.com> 978techdoc = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf 979tested = 2.38 980type = device 981uses = Garmin-Native 982vendor = Garmin 983notes = The USB version requires the Linux kernel garmin_usb driver. 984 usbfs is not required after gpsd version 2.39. 985 DOP (Dilution of Precision) information is not available (Garmin protocol 986 includes EPE only); gpsd uses EPE to approximate DOP. Magnetic variation 987 information is not available. Garmin uses a nonstandard 16-bit SNR scale. 988 The 18 series, unlike the 16, reports skyview via a packet 114. They will 989 not operate indoors and require a good sky view. 990 991[Garmin GPS-18 (all but USB)] 992interfaces = RS-232 993nmea = 2.0 and 2.3 994packaging = mouse 995pps = True 996pps_accuracy = 1us 997time_offset = 0.125s 998submitter = Gary E. Miller <gem@rellim.com> 999techdoc = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf 1000tested = 2.5 1001type = device 1002uses = Garmin-Native 1003vendor = Garmin 1004notes = The RS-232 versions can emit NMEA and are found by normal autoconfiguration. 1005 GPS-18 LVC and GPS-18 LVC/5m have PPS outputs. WAAS is supported. 1006 The 18 series, unlike the 16, reports skyview via a packet 114. They will 1007 not operate indoors and require a good sky view. NTP offset quoted is 1008 at 19200bps; drops to 0.525 at 4800bps. 1009 1010[GPS-25LP] 1011type = device 1012packaging = OEM module 1013vendor = Garmin 1014techdoc = http://www8.garmin.com/products/gps25/spec.html 1015uses = Garmin-Native 1016interfaces = RS-232 1017nmea = 2.0 1018tested = regression 1019discontinued = True 1020submitter = Daniele Giangrazi <daniele.giangrazi@elital.net> 1021notes = Discontinued embedded module. 1022logs = garmin25lp.log 1023 1024[Garmin 38] 1025type = device 1026vendor = Garmin 1027packaging = handset 1028techdoc = http://au.geocities.com/glennbaddeley/gps/data/GPS38_OwnersManualAndTechdoc_June1997_RevB.pdf 1029uses = Garmin-Native 1030interfaces = RS-232 1031rating = excellent 1032tested = regression 1033nmea = 2.0 1034discontinued = True 1035submitter = Pascal F. Martin <pascal.martin@cox.net> 1036notes = Start-of-cycle is RMC. 2-second cycle time, 1 fix per cycle. 1037logs = garmin38.log 1038 1039[Garmin 48] 1040type = device 1041vendor = Garmin 1042packaging = handset 1043techdoc = https://buy.garmin.com/shop/shop.do?pID=85 1044uses = Garmin-Native 1045interfaces = RS-232 1046nmea = 2.0 1047discontinued = True 1048rating = excellent 1049tested = regression 1050notes = Start-of-cycle is RMC. 2-second cycle time, 2 fixes per cycle, GLL 1051 reports second fix. The 48 has been discontinued. The Garmin 1052 12XL and 45 are nearly identical and should work as well. 1053 Details on the Garmin proprietary protocol can be found at <a 1054 href="http://www.garmin.com/support/commProtocol.html">here</a>. 1055 1056[Garmin GPS 60] 1057type = device 1058vendor = Garmin 1059packaging = handset 1060techdoc = http://www.garmin.com/manuals/GPS60_OwnersManual.pdf 1061uses = Garmin-Native 1062interfaces = USB, RS-232 1063tested = 2.33 1064nmea = 3.01 1065submitter = Diego Berge <gpsd@nippur.net> 1066 1067[Garmin GPS 76] 1068type = device 1069vendor = Garmin 1070packaging = handset 1071techdoc = http://www.garmin.com/manuals/GPS76_OwnersManual.pdf 1072uses = Garmin-Native 1073interfaces = RS-232 1074tested = 2.39 1075nmea = 2.3 1076submitter = Sebastian Niehaus <killedbythoughts@mindcrime.net>, 1077 Geoff Childs <dofinch-aria@yahoo.co.uk> 1078notes = The device has a four pin socket described by Garmin as a serial 1079 interface. Connection to a standard 9 pin RS-232 computer socket 1080 is made using the special adaptor lead supplied by Garmin. Sebastian 1081 Niehaus says it annunces "Software Version 3.70". Geoff Childs adds: 1082 "The Garmin GPS 76 comms MUST be set to 'NMEA'. The kernel module 1083 garmin_gps is not needed and should not be specially loaded." 1084 1085[Geko 201] 1086type = device 1087vendor = Garmin 1088packaging = handset 1089techdoc = http://www.garmin.com/manuals/Geko201_OwnersManual.pdf 1090uses = Garmin-Native 1091interfaces = RS-232 1092tested = regression 1093nmea = 3.0 1094submitter = Jose Luis Domingo Lopez <jdomingo@24x7linux.com> 1095notes = 1096logs = garmin-geko201.log 1097 1098[eTrex Vista] 1099type = device 1100vendor = Garmin 1101packaging = handset 1102techdoc = http://www.garmin.com/manuals/eTrexVista_OwnersManual.pdf 1103uses = Garmin-Native 1104interfaces = RS-232 1105tested = 2.32 1106nmea = 3.0 1107submitter = Reed Hedges <reed@interreality.org> 1108notes = 1109 1110[Nuvi 650] 1111type = device 1112vendor = Garmin 1113packaging = handsfree 1114techdoc = http://www.garmin.com/manuals/nuvi650_OwnersManual.pdf 1115uses = SiRF-3 1116interfaces = USB 1117tested = * 1118nmea = 3.0 1119rating = broken 1120notes = This device does not have real-time data output, and is incompatible 1121 with GPSD. 1122 1123[GPSmap 76S] 1124type = device 1125vendor = Garmin 1126engine = unknown 1127packaging = handset 1128rating = other 1129techdoc = http://www8.garmin.com/manuals/GPSMAP76S_OwnersManual.pdf 1130tested = 2.94 1131nmea = 2.3 1132date = 2011-10-24 1133interfaces = USB 1134submitter = Brad Skillman <brad.skillman@cobham.com> 1135model = GPSmap 76S 1136notes = When the GPSmap 76S is placed into simulator mode, for some 1137 unknown reason, both the xgps and cgps clients display "n/a" in 1138 the time field. However, the lat., long., and altitude fields 1139 are being displayed correctly. Using gpspipe -r is appears that 1140 the $GPGLL message is sending out the UTC time in the HHMMSS 1141 format (Note: There are no fractional seconds being generated) 1142logs = GPSmap-76S 1143 1144[Montana 650t] 1145type = device 1146packaging = handheld 1147interfaces = USB 1148submitter = Richard Allen <rsaxvc@gmail.com> 1149vendor = Garmin 1150techdoc = http://static.garmincdn.com/pumac/Montana_600_OM_EN.pdf 1151engine = STA2065 1152rating = good 1153tested = 3.6 1154 1155[GPS 152] 1156type = device 1157submitter = Erkki Laasonen <erkki.laasonen@gmail.com> 1158vendor = Garmin 1159techdoc = http://www.manualrepubliccdn.com/pdf/garmin/396-m-gps-152-manual-owner-s-manual.pdf 1160packaging = handheld 1161engine = unknown 1162firmware = 3.60 1163nmea = 2.3 1164interfaces = FTDI 1165tested = 3.6 1166rating = broken 1167location = Uusikaupunki, FI, 61N 21E 1168date = 2014-06-30 1169sample_notes: Log was taken on my moored boat. 1170 1171#% Geostar Navigation 1172 1173[GeoS-1M] 1174type = device 1175date = 2010-07-09 1176location = Minsk, Belarus, 53N 27E 1177model = GeoS-1M 1178engine = custom 1179interfaces = TTL 1180nmea = 3.01 1181packaging = OEM module 1182rating = good 1183sample_notes = NMEA output for a few minutes after power up. 1184submitter = Viktar Palstsiuk <viktar.palstsiuk@promwad.com> 1185techdoc = http://geostar-navigation.com/fail/manuals/User_Manual_GeoS-1M_en.pdf 1186tested = 2.90 1187vendor = Geostar 1188notes = GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its 1189 architecture includes 24 tracking channels. 1190logs = geos-1m.log 1191 1192#% GlobalSat 1193 1194[BC-307] 1195type = device 1196vendor = GlobalSat 1197packaging = mouse 1198techdoc = http://www.usglobalsat.com/item.asp?itemid=12 1199uses = SiRF-2 1200interfaces = CF 1201tested = 2.35 1202nmea = 2.2 1203rating = fair 1204submitter = Chris Kuethe <chris.kuethe@gmail.com>. 1205notes = Acceptably functional running firmware 231ES. 1206 1207[BT-318] 1208type = device 1209vendor = GlobalSat 1210packaging = mouse 1211techdoc = http://www.globalsat.com.tw/english/products_detail.php?main_id=21&p_id=107 1212uses = SiRF-2 1213interfaces = Bluetooth 1214tested = 3.12 1215nmea = 2.2 1216rating = fair 1217configurable = insane 1218submitter = Frank Nicholas <frank@nicholasfamilycentral.com> 1219notes = Requires the -b option. 1220 1221[BT-338] 1222type = device 1223vendor = GlobalSat 1224packaging = mouse 1225techdoc = http://www.usglobalsat.com/item.asp?itemid=6 1226uses = SiRF-3 1227interfaces = Bluetooth 1228tested = 2.13 1229rating = fair 1230submitter = Michal Panczyk <mpanczyk@gmail.com> 1231 1232[BU-303] 1233type = device 1234vendor = GlobalSat 1235packaging = mouse 1236techdoc = http://www.usglobalsat.com/item.asp?itemid=11&catid=13 1237uses = SiRF-2 1238interfaces = USB 1239usbchip = pl2303 1240tested = regression 1241rating = excellent 1242eval_unit = esr 1243nmea = 2.2 1244notes = Older versions of the BU-303 had a design defect that made it 1245 likely to fail if subjected to vibration or hard shocks. 1246 1247[BU-353] 1248type = device 1249vendor = GlobalSat 1250packaging = mouse 1251techdoc = http://www.usglobalsat.com/item.asp?itemid=60&catid=17 1252uses = SiRF-3 1253interfaces = USB 1254usbchip = pl2303 1255tested = pre-2.29 1256rating = excellent 1257eval_unit = esr 1258nmea = 2.3 1259notes = This receiver does not support PPS timing output. Some versions of 1260 firmware do not support WAAS, though updates may be available for a 1261 fee from GlobalSat. 1262 1263[BU-355] 1264type = device 1265vendor = GlobalSat 1266packaging = mouse 1267uses = SiRF-3 1268interfaces = USB 1269usbchip = pl2303 1270tested = 3.10 1271rating = good 1272eval_unit = esr 1273nmea = 2.3 1274notes = This receiver does not support PPS timing output. Does support 1275 WAAS/EGNOS, unlike some 353s. 1276 1277[BU-353-S4] 1278type = device 1279vendor = GlobalSat 1280packaging = mouse 1281techdoc = http://usglobalsat.com/store/download/688/bu353s4_ds.pdf 1282uses = SiRF-4 1283interfaces = USB 1284usbchip = pl2303 1285tested = 3.11 1286rating = poor 1287eval-unit = esr,gary 1288nmea = 3.0 1289# Also tested by Paul Beard <paulbeard@paulbeard.name> 1290# Hamilton, Waikato, 37.8S 175.3E 2014-12-31 1291notes = This receiver does not support PPS timing output. Much like the 1292 BU-353 except for using a SiRFStar IV chip. Has poor 1293 sensitivity and takes a lot longer to cold-start than the vendor 1294 claim 45 of 45 seconds. Gary Miller rates this device "DO NOT 1295 EVER BUY ONE!", observing "The big selling point of the SiRF IV 1296 is the lower power needs. Looks like they made that happen at 1297 the expense of sensitivity and timeliness of fixes." Also, 1298 has the SiRF-IV tendency to freeze when switched from binary 1299 to NMEA mode (power-cycling it unjams it). 1300 1301[BT-359] 1302vendor = GlobalSat 1303uses = SiRF-3 1304interfaces = Bluetooth 1305nmea = 2.2 1306packaging = mouse 1307rating = excellent 1308submitter = Patrick Forristal <tradiuz@gmail.com> 1309techdoc = http://www.globalsat.com.tw/eng/support_check.php?check_id=126&checkType=Manual 1310tested = 2.37 1311 1312[ET-332 Engine Board] 1313type = device 1314engine = SiRF-3 1315firmware = unknown 1316model = ET-322 Engine Board 1317interfaces = TTL 1318notes = This is an OEM module but it is available in small quantities. 1319logs = et-332.log 1320packaging = OEM module 1321rating = good 1322submitter = Val Schmidt <vschmidt@ccom.unh.edu> 1323techdoc =http://www.globalsat.com.tw/products-page.php?menu=2&gs_en_product_id=4&gs_en_product_cnt_id=44&img_id=110&product_cnt_folder=4 1324vendor = GlobalSat 1325 1326[ND-100S] 1327type = device 1328engine = SiRF-3 1329date = 2011-03-14 1330interfaces = USB 1331model = ND-100S 1332notes = SirfDemo can be used to configure the product. 1333packaging = mouse 1334rating = excellent 1335submitter = George E Farmer <gefgef@hotmail.com> 1336techdoc = http://usglobalsat.com/store/download/590/nd100s_v1.0-manual.pdf 1337tested = 2.95 1338vendor = GlobalSat 1339logs = nd-1005.log 1340 1341[MR-350P] 1342date = 2010-02-03 1343interfaces = RS-232 1344nmea = 3.01 1345packaging = mouse 1346pps = True 1347pps_accuracy = 50ns 1348time_offset = ? 1349rating = excellent 1350submitter = Gary E. Miller <gem@rellim.com>, Tony Hain <tony@tndh.net> 1351techdoc = http://usglobalsat.com/p-58-mr-350p-bulkhead.aspx 1352tested = 3.3 1353type = device 1354uses = SiRF-3 1355vendor = GlobalSat 1356notes = May work inside wood frame buildings. PPS pulse is only 1uS wide, 1357 but newer gpsd handles that fine. Be careful, there is also an MR-350 1358 (no suffix P) that does NOT have PPS. 1359logs = mr-350p 1360 1361[TripNav TN-200] 1362type = device 1363vendor = GlobalSat 1364packaging = mouse 1365techdoc = http://www.usglobalsat.com/item.asp?itemid=45&catid=13 1366uses = SiRF-2 1367interfaces = USB 1368usbchip = FTDI FT232 1369tested = regression 1370rating = excellent 1371notes = We tested a version with SiRF Firmware level 231ES. The <a 1372 href='http://ftdi-usb-sio.sourceforge.net/'>FTDI USB-to-serial 1373 chip</a> is supported only as alpha software not yet 1374 incorporated into the Linux kernel, though it seems to be well 1375 supported by OS X and various BSDs. It seems like the only 1376 difference between this and the BU-303 is the different 1377 USB-to-serial chip. 1378 1379[TripNav TN-204] 1380type = device 1381vendor = GlobalSat 1382packaging = mouse 1383uses = SiRF-2 1384interfaces = CF 1385tested = regression 1386rating = excellent 1387submitter = Pascal F. Martin <pascal.martin@cox.net> 1388notes = Sometimes sold under the brand name "Rayming", but that vendor 1389 seems to have disappeared. Chipset said to be SiRF 2 but the 1390 output looks more like old Garmin GPSes. 1391 1392[ND100] 1393type = device 1394uses = MSB2122 1395interfaces = USB 1396usbchip = pl2303 1397nmea = 3.0 1398packaging = mouse 1399rating = excellent 1400submitter = Arnaud Le Meur <arnaudlemeur@free.fr> 1401techdoc = http://www.globalsat.com.tw/eng/product_detail_00000124.htm 1402tested = 2.38 1403vendor = GlobalSat 1404notes = May ship with broken firmware that incorrectly reports the 1405 current year (2009) as 1953. A firmware update is available 1406 to resolve this issue. 1407 1408#% HAB supplies 1409 1410[HAB-GPSPI] 1411type = device 1412submitter = mayer@iiasa.ac.at 1413vendor = HAB Supplies 1414techdoc = http://ava.upuaut.net/store/index.php?route=product/product&path=59_60&product_id=95 1415packaging = OEM module 1416engine = unknown 1417firmware = unknown 1418interfaces = TTL 1419tested = 3.6 1420rating = excellent 1421location = Laxenburg, Austria, 48.06N 16.36E 1422date = 2015-06-21 1423sample_notes = This device was not moved as it is used as a NTP server. 1424logs=hab-gpspi.log 1425 1426#% Haicom 1427 1428[HI-204S] 1429type = device 1430vendor = Haicom 1431packaging = mouse 1432techdoc = http://www.haicom.com.tw/products.htm 1433uses = SiRF-2 1434interfaces = USB 1435usbchip = pl2303 1436tested = 3.12 1437rating = excellent 1438eval_unit = esr 1439nmea = 2.2 1440notes = SiRF firmware level 231ES (XTrac). Haicom provided a test unit. Manual 1441 states incorrectly that VTG is off by default. 1442 1443[HI-204E] 1444type = device 1445vendor = Haicom 1446packaging = mouse 1447techdoc = http://www.haicom.com.tw/gps204E.shtml 1448engine = Evermore BBP1202 1449interfaces = USB 1450tested = 2.6 1451rating = excellent 1452nmea = 2.2 1453notes = Probably uses PL2303 but we have not verified this. 1454 1455[HI-303S] 1456type = device 1457vendor = Haicom 1458packaging = handsfree 1459techdoc = http://www.haicom.com.tw/gps303s.shtml 1460uses = SiRF-3 1461interfaces = RS-232 1462tested = 2.25 1463nmea = 2.2 1464submitter = Denis Perchine <dyp@perchine.com> 1465discontinued = True 1466notes = NMEA works, but SiRF binary does not. This device seems to ignore the 1467 $PSRF100 mode switch command. (SiRF binary may be available on 1468 the auxiliary serial port, but this is unconfirmed.) This 1469 device ships with XTrac firmware. 1470 1471[HI-305N] 1472type = device 1473vendor = Haicom 1474packaging = mouse 1475techdoc = http://www.haicom.com.tw/ 1476uses = Nemerix 1477interfaces = CF 1478tested = regression 1479discontinued = True 1480submitter = David Findlay <dave@davsoft.com.au> 1481notes = Adaptors for RS-232, USB, and Bluetooth operation are available. 1482 1483#% Holux 1484 1485[GM-210] 1486type = device 1487vendor = Holux 1488packaging = mouse 1489techdoc = http://www.amazon.com/Holux-GM-210-Receiver-Laptop-Pocket/dp/B0006ZMBTW 1490uses = SiRF-2 1491interfaces = RS-232 1492tested = regression 1493nmea = 2.2 1494discontinued = True 1495submitter = Patrick L. McGillan <pmcgillan@pateri.com>. 1496 1497 1498[GR-230] 1499type = device 1500vendor = Holux 1501packaging = mouse 1502techdoc = http://www.holux.com.tw/Temp%20web/GR-230.html 1503uses = SiRF-2 1504interfaces = Bluetooth 1505configurable = insane 1506tested = 2.19 1507nmea = 2.2 1508discontinued = True 1509notes = 4 color LED showing: Bluetooth, Navigation Update and Battery 1510 and Charger Rating Indication. FLASH based program 1511 memory. Firmware upgradeable through serial interface. Water 1512 resistant. 1513 1514[GPSlim 236] 1515type = device 1516vendor = Holux 1517packaging = mouse 1518techdoc = http://en.holux.com.cn/product/search.htm?filename=gpsreceiver_bluetooth_gpslim2+36.htm&target=bluetooth00&level=grandsonson 1519uses = SiRF-3 1520interfaces = Bluetooth 1521tested = regression 1522rating = poor 1523nmea = 2.2 1524submitter = Kévin Redon <kevredon@gmail.com> 1525notes = Does not report altitude reliably. 1526 Optional interfaces: 1527 mini-USB -> USB, needing a special cable : GR230-A2 (USB data cable), 1528 otherwise it will not work; 1529 mini-USB -> RS-232, need cable GR230-A1(RS-232 data cable), I didn't 1530 try it with a normal cable; 1531 mini-USB -> PS2, need cable GR230-A3 (Mini USB port to PS2 port ), I 1532 didn't try it with a normal cable. 1533 1534[Holux GR-239] 1535type = device 1536vendor = Holux 1537packaging = mouse 1538techdoc = http://www.holux.com/JCore/en/support/DLF.jsp?DLU=http://www1.holux.com.tw:8080/JCore/UploadFile/79754.pdf 1539uses = SiRF-3 1540interfaces = Bluetooth, USB 1541configurable = insane 1542tested = 2.36 1543rating = poor 1544nmea = 2.2 1545notes = Bluetooth operation requires -b option. Powered from a car 1546 cigarette-lighter. 1547 1548[M-241] 1549type = device 1550vendor = Holux 1551packaging = mouse 1552techdoc = http://www.holux.com/JCore/en/products/products_content.jsp?pno=341 1553uses = MTK 1554interfaces = Bluetooth, USB 1555usbchip = CP2101 1556configurable = insane 1557tested = 2.37 1558btglitch = yes 1559submitter = Roland Ager <roland.ager@gmx.de> 1560notes = gpsd crashes the device when autoprobing @ baud rate 9600 (unless 1561 '-b'/broken-device-safety is enabled - need to unplug/reset the device). 1562 'stty -F /dev/ttyUSB1 ispeed 38400' helps avoiding too much autoprobing - 1563 though stty complains about not being able to perform all requested 1564 operations. 1565 1566#% Humminbird 1567 1568[Matrix-37] 1569type = device 1570vendor = Humminbird 1571packaging = handsfree 1572techdoc = http://www.retrevo.com/support/Humminbird-37-GPS-manual/ 1573engine = unknown 1574interfaces = RS-232 1575discontinued = True 1576tested = regression 1577rating = good 1578submitter = Carl Brown <cbsled@verizon.net> 1579notes = Depth finder and water-temperature sensor. 1580logs = humminbird-M37.log 1581 1582#% iTrek 1583 1584[M3] 1585type = device 1586vendor = iTrek 1587packaging = mouse 1588techdoc = http://www.semsons.com/im3blgpsresi.html 1589uses = SiRF-3 1590interfaces = Bluetooth 1591tested = 2.28 1592submitter = Lance Fetters <ashikase@users.sourceforge.net> 1593notes = The product page points at a retail site carrying these 1594 because the vendor site is in Japanese only. This GPS emits a 1595 weirdly broken GSA sentence that crashed gpsd versions prior to 1596 2.28. Serial parameters default to 38400; 8, N, 1. May come 1597 bundled with Microsoft Streets and Trips. 1598logs = iTrek.log 1599 1600#% Jackson Labs 1601 1602[Firefly-1a] 1603type = device 1604engine = UBLOX NEO-5Q 1605firmware = 0.918 1606interfaces = RS-232 1607pps = True 1608pps_accuracy = 50ns 1609packaging = OEM module 1610rating = excellent 1611submitter = Don Weeks <don.l.weeks.jr@gmail.com>, 1612 Said Jackson <saidjack@aol.com> 1613techdoc = http://jackson-labs.com/docs/FireFly_quickstart.pdf 1614vendor = Jackson Labs 1615notes = Only outputs GGA and RMC NMEA strings. There are other proprietary 1616 commands. See the gpsd-dev list for patches. GPSD works as far back 1617 as the 0.914 version, which emitted \r\r\n terminations. All the 1618 FireFly units are OCXO driven, so the 1PPS output stays accurate even 1619 if GPS reception is lost. 1620 1621[FireFly-II] 1622type = device 1623engine = UBLOX NEO-5Q 1624date = 2010-07-07 1625firmware = 2.18 1626interfaces = RS-232 1627pps = True 1628pps_accuracy = 50ns 1629time_offset = ? 1630model = FireFly-1A and FireFly-II GPSDO 1631notes = Uses ublox Antaris 5 with Kick Start and Super Sense, 1632 soon movingto ublox-6. Defective \r\r\n string terminations 1633 have been fixed in the 2.18 firmware version. All the 1634 FireFly units are OCXO driven, so the 1PPS output stays accurate even 1635 if GPS reception is lost. 1636packaging = OEM module 1637rating = good 1638sample_notes = Stationary state, roof-mounted antenna, three levels of 1639 GPS distribution Amplifier between antenna and receiver. 1640submitter = Said Jackson <saidjack@aol.com> 1641techdoc = http://www.jackson-labs.com/docs/Quickstart_FireFly_IIA_FW-rev_2.x.pdf 1642vendor = Jackson Labs 1643 1644#% LyconSys 1645 1646[GPSMOD1] 1647type = device 1648engine = ANTARIS5 1649firmware = ROM CORE 4.00 (25682) 1650interfaces = USB 1651model = GPSMOD1 1652nmea = 2.3 1653packaging = mouse 1654rating = excellent 1655submitter = info@lyconsys.com 1656techdoc = http://www.lyconsys.com/produkte/gps-emfanger-lyconsys-gpsmod1.htm 1657tested = 2.95 1658vendor = LyconSys 1659 1660#% Magellan 1661 1662[EC-10X] 1663type = device 1664vendor = Magellan 1665packaging = handset 1666techdoc = http://www.herman-nelson.com/itemInfo.cfm?itemID=205 1667uses = Zodiac 1668interfaces = RS-232 1669pps = True 1670tested = regression 1671discontinued = True 1672submitter = Gary E. Miller <gem@rellim.com> 1673notes = It was cool in its day, now a dinosaur mainly good for 1674 regression testing. NMEA time is accurate to about 500mS. 1675 Start of cycle is GPRMC on odd seconds, GPRMB on even seconds. 1676logs = magellan315.log 1677 1678[315] 1679type = device 1680vendor = Magellan 1681packaging = handset 1682techdoc = https://www.magellangps.com/assets/manuals/gps_310_315_en.pdf 1683engine = unknown 1684interfaces = RS-232 1685tested = regression 1686rating = good 1687submitter = Angel Marques Mateu <amarques@cgf.upv.es> 1688notes = 1689logs = magellan315.log 1690 1691[Meridian Platinum] 1692type = device 1693vendor = Magellan 1694packaging = handset 1695techdoc = http://www.amazon.com/Magellan-Meridian-Platinum-Handheld-GPS/dp/B00005OLYD 1696engine = Motorola 1697interfaces = RS-232 1698tested = 2.21 1699rating = excellent 1700nmea = v1.5 APA, v1.5 XTE, v2.1 GSA 1701discontinued = True 1702submitter = Chris S. Newell <chris@newellfamily.net> 1703 1704[eXplorist 110] 1705type = device 1706vendor = Magellan 1707packaging = handset 1708techdoc = http://support.magellangps.com/support/index.php?_m=downloads%26_a=viewdownload#26downloaditemid=322 1709engine = unknown 1710interfaces = USB 1711tested = regression 1712rating = good 1713nmea = 2.1 1714submitter = rickyconnell@gmail.com 1715logs = eXplorist110.log 1716 1717[eXplorist 210] 1718type = device 1719vendor = Magellan 1720packaging = handset 1721techdoc = http://www.magellangps.com/assets/manuals/newprod/eXplorist%20210_US.pdf 1722engine = unknown 1723interfaces = USB 1724tested = regression 1725rating = good 1726nmea = 2.1 1727submitter = Paul van den Berg <paulberg@wanadoo.nl> 1728notes = USB has 3 modes — NMEA data comm (3 submodes): outputs GPS data 1729 (creates /dev/ttyACM0), USB file transfer: transfer files (creates 1730 /dev/sdX and /dev/sdX1), or Power Only: use USB only for electrical 1731 power. The APA and XTE extensions choke gpsd, so select V2.1 GSA 1732 under "NMEA Data Comm>". 1733logs = eXplorist210.log 1734 1735[Thales AC12] 1736type = device 1737vendor = Magellan 1738packaging = OEM module 1739techdoc = ftp://ftp.magellangps.com/OEM,%20Sensor%20&%20ADU/A12,%20%20B12,%20&%20AC12/Techdoc%20Material/A12,%20B12%20&%20AC12%20RM%20rev%20E.pdf 1740engine = unknown 1741interfaces = TTL 1742nmea = 3.0 1743tested = regression 1744rating = good 1745pps = True 1746pps_accuracy = 250ns 1747time_offset = ? 1748submitter = Chris Kuethe <chris.kuethe@gmail.com> 1749notes = Receiver comes up in silent mode, you may need to use ashctl to turn 1750 on a default set of messages. Tested with firmware BQ00 and BQ04. 1751logs=ac12.log 1752 1753[Triton 400] 1754type = device 1755vendor = Magellan 1756submitter = James Gerlach <jpgerlach@gmail.com> 1757techdoc = http://www.tritonforum.com/Files/UserManual_ENG.pdf 1758packaging = handset 1759uses = SiRF-3 1760firmware = GSW3.2.4 1761nmea = 2.1 1762interfaces = USB 1763tested = 3.8 and 3.5 1764rating = good 1765location = Wellington, FL, USA 1766date: 2013-03-31 1767logs=triton400.log 1768 1769#% Motorola 1770 1771[Oncore GT+] 1772type = device 1773vendor = Motorola 1774packaging = OEM module 1775techdoc = http://www.tapr.org/gps_oncorevp.html 1776engine = Motorola 1777interfaces = RS-232 or TTL 1778tested = 2.20 1779nmea = 2.2 1780pps = True 1781pps_accuracy = 50ns 1782time_offset = ? 1783rating = good 1784discontinued = True 1785submitter = Wojciech Kazubski <wk@ire.pw.edu.pl> 1786notes = RTCM input, no WAAS. In binary mode can deliver differential 1787 correction for another Oncore GT+. Similar Motorola Oncore UT 1788 timing receiver has less functions but better timing 1789 accuracy. 1790logs = oncore.log 1791 1792[T805] 1793type = device 1794vendor = Motorola 1795packaging = mouse 1796techdoc = http://www.motorola.com/motoinfo/product/detailsPf.jsp?globalObjectId=185 1797uses = SiRF-3 1798subtype = <a href="http://www.sirf.com/products/GSC3ProductInsert.pdf">GSC3f-7879</a> 1799interfaces = Bluetooth 1800tested = 2.35 1801submitter = Reported by Olivier Lahaye <olivier.lahaye@free.fr> 1802 1803#% Navcom 1804 1805[SF-2040G] 1806type = device 1807vendor = Navcom 1808packaging = survey 1809techdoc = http://www.navcomtech.com/Products/GPS/sf2040g.cfm 1810uses = Touchstone ASIC 1811interfaces = RS-232, Bluetooth, Radio (untested) 1812tested = 2.35 1813rating = good 1814nmea = 3.0 1815submitter = Diego Berge <gpsd@nippur.net> 1816 1817#$ NaviSys 1818 1819[GR601-W] 1820type = device 1821vendor = Navisys 1822packaging = mouse 1823techdoc = http://www.navisys.com.tw/products/image/130416/GR-601_flyer-130416.pdf 1824engine = LEA-6H 1825interfaces = USB 1826tested = 3.12 1827pps = True 1828pps_accuracy = 1ms 1829time_offset = ? 1830rating = excellent 1831eval-unit = esr, gary 1832submitter = Eric S. Raymond <esr@thyrsus.com>. 1833notes = Also known as the Macx-1, this is the USB variant of the 1834 GR601, customized for timing use by connecting 1PPS to DCD 1835 and capable of delivering time to 1ms accuracy. The best 1836 indoor performer I have tested. Has one odd quirk: UBX 1837 reporting can be turned on, but NMEA cannot be turned off. 1838logs = gr601-w.log 1839 1840[GR8013-W] 1841type = device 1842submitter = Marc Thielemann <marc.thielemann@biama.de> 1843vendor = Navisys 1844techdoc = http://www.navisys.com.tw/products/GPS&GNSS_%20receivers/flyer/GR-801_flyer-150326.pdf 1845packaging = mouse 1846engine = LEA-8H 1847firmware = 2.01 1848nmea = 2.3, 4.1 1849interfaces = PL2303 1850tested = 3.15 1851rating = excellent 1852location = Berlin, Germany, 5230.88669N 01327.85593E 1853date = 2015-06-19 1854logs = g8013-w.log 1855 1856[EVK 6H] 1857type = device 1858vendor = u-blox 1859packaging = other 1860techdoc = http://www.u-blox.com/images/downloads/Product_Docs/EVK-6_UserGuide_%28GPS.G6-EK-10040%29.pdf 1861engine = LEA-6H 1862interfaces = USB, RS232 1863tested = 3.9 1864pps = True 1865pps_accuracy = 1ms 1866time_offset = ? 1867rating = excellent 1868eval-unit = esr 1869submitter = Eric S. Raymond <esr@thyrsus.com>. 1870notes = The u-blox eval kit for the LEA-6H. Has a TCXO on a miniboard in 1871 a nice aluminum case with both USB and serial output. PPS on DCD 1872 and DSR. Good Stratum 0 time source. 1873 1874#% Navius 1875 1876[NSA-U3] 1877type = device 1878vendor = Navius 1879packaging = mouse 1880techdoc = http://www.navius.biz/ 1881uses = SiRF-2 1882interfaces = USB 1883usbchip = pl2303 1884tested = 2.24 1885rating = excellent 1886submitter = Jeff Francis <jeff@gritch.org> 1887notes = Included with the horrible Windows navigation software from 1888 Rand McNally. 1889 1890#% NaviLock 1891 1892[NL-209P] 1893type = device 1894vendor = NaviLock 1895packaging = mouse 1896techdoc = http://www.navilock.de/produkte/gruppen/3/Kabel_Empfaenger/61371_NL-209PU.html?show=spec 1897uses = Sony CXD2951 1898interfaces = USB, RS-232, Bluetooth 1899configurable = insane 1900usbchip = pl2303 1901tested = 2.35 1902nmea = 2.2 1903submitter = Jason Curl <jcurlnews@arcor.de> 1904notes = When running, need to use the -b option, else the device will 1905 hang during the GPSD probing phase and it needs to be unplugged 1906 and reinserted. To use this device with NTPd, set the the 1907 "fudge" factor to 0.840. There is no known PPS signal associated 1908 with this device. While the technical information claims 1us 1909 accuracy on the clock, the interface is undocumented, so there 1910 is no way to know if there is a usable 1PPS signal. 1911 1912[NL-302U] 1913type = device 1914vendor = NaviLock 1915packaging = mouse 1916techdoc = http://www.navilock.de/produkte/gruppen/3/Kabel_Empfaenger/61422_NL-302U.html?show=spec 1917uses = SiRF-3 1918subtype = GSW3.2.4_3.1.00.12-SDK003P1 1919interfaces = USB 1920usbchip = pl2303 1921nmea = 2.34 1922submitter = Beat Bolli <me+gpsd@drbeat.li> 1923notes = <code>gpsprof</code> output can be found 1924 <a href="http://www.drbeat.li/album/-Diverses/GPS/Navilock+NL-302U">here</a>. 1925 1926[NL-402U USB] 1927type = device 1928engine = u-blox5 GPS & GALILEO SuperSense 1929date = 2008-07-24 1930location = Neustadt / Holstein 54.05N 10.49 E 1931model = NL-402U USB Empfänger 1932interfaces = USB 1933packaging = mouse 1934rating = excellent 1935submitter = Klaus Plöger <k.ploeger@gastradata.de> 1936techdoc = http://www.navilock.de/download/PDFs/60095_-_NL-402U_Datenblatt/531 1937tested = regression 1938vendor = NaviLock 1939logs = nl402u.log 1940notes = Starts with RMC, ends with GLL. 1941 1942[NL-551EUSB] 1943type = device 1944engine = u-blox5 GPS & GALILEO SuperSense 1945submitter = Bas van Duijnhoven <b.duijnhoven@chello.nl> 1946vendor = NaviLock 1947techdoc = http://www.navilock.de/files/11409.download 1948packaging = OEM module 1949interfaces = TTL 1950firmware = 6.02 1951nmea = 2.3 1952tested = 3.5 1953location = Rheden, NL, 52.002N 6.036E 1954date = 2012-07-03 1955rating = good 1956logs = nl551e.log 1957 1958[BT-451] 1959type = device 1960engine= ANTARIS4 1961date = 2009-12-09 1962location = Lithuania, 55.8N 23.6E 1963model = BT-451 1964packaging = mouse 1965interfaces = USB 1966rating = good 1967submitter = Mindaugas <mindedie@zebra.lt> 1968techdoc = http://www.navilock.de/produkte/gruppen/28/Nicht_mehr_lieferbare_Artikel/60307_BT-451.html?show=spec 1969tested = 2.39 1970vendor = NaviLock 1971logs = bt451.log 1972notes = Uses the ANTARIS4 ATR062x variant. 1973 1974[NL-8002U] 1975type=device 1976submitter = Manfred Günzl <osb_mgu@gmx.de> 1977vendor = NaviLock 1978techdoc = http://www.navilock.de/produkte/G_62523/dokumente.html 1979packaging = mouse 1980engine = LEA-8H 1981firmware = SW 2.01 (75331),HW 00080000,PROTVER 15.00 1982nmea = V3.01 1983interfaces = Other 1984tested = 3.15 1985rating = excellent 1986location = Schramberg Sulgen, DE, 48.2N 8.4E 1987date = 2015-10-10 1988logs = nl2008u.log 1989 1990#% NavMan 1991 1992[Jupiter 20] 1993type = device 1994vendor = NavMan 1995packaging = chipset 1996techdoc = 1997uses = SiRF-2 1998subtype = Jupiter 21DR Firmware 1999interfaces = RS-232 2000tested = 2.32 2001nmea = 2.2 2002discontinued = True 2003submitter = Andreas Stricker <andreas.stricker@fela.ch> 2004notes = Not a complete GPS, but a chipset. It is running with an external 2005 gyro on a our self-developed board. 2006 2007#%Navis Engineering Bureau 2008 2009[CH-4711] 2010type = device 2011vendor = Navis Engineering Bureau 2012engine = CH-4706 2013date = 2009-11-21 2014firmware = m4706 03.10 02/06/09 | 12044 | M2002 05.01 02/06/09 2015nmea = 3.0? 2016packaging = mouse 2017interfaces = USB 2018usbchip = FTDI FT232 2019rating = good 2020submitter = walkie@mail.ru 2021techdoc = http://navis.ru/downloads/CH-4711_USB/ 2022logs = ch-4711.log 2023notes = By default the device does not report 2d fixes; the vendor 2024 configuration tool offers checkboxes to enable any combination of 2025 none, 2D fixes, 3D fixes, or both. The devices has only a very 2026 limited set of NMEA controls but speaks a proprietary vendor format 2027 called BINR with more capabilities. 2028 2029[NAVIOR-24] 2030type = device 2031engine = CH-4701 2032interfaces = TTL 2033date = 2008-05-29 2034location = Minsk, Belarus, 53N 27E 2035model = NAVIOR-24 2036packaging = OEM module 2037rating = good 2038submitter = Viktar Palstsiuk <viktar.palstsiuk@promwad.com> 2039techdoc = http://navis.ru/en/catalog_110_139.html 2040vendor = Navis Engineering Bureau 2041notes = NAVIOR-24 is the single board 24-channel navigation OEM receiver 2042 supporting GLONASS/GPS systems. 2043logs = ch-4701.log 2044 2045#%Navisys 2046 2047[GR-300] 2048type = device 2049uses = SiRF-3 2050date = 2009-07-03 2051firmware = GSW3.2.4Pat2_3.1.00.12-SDK001P1.00 2052interfaces = USB 2053location = East Haddon, Northampton, England, UK, 53.3N, 1.02W 2054model = GR-300 2055nmea = 3.0 2056packaging = mouse 2057rating = excellent 2058submitter = sk1ppy14@yahoo.co.uk 2059techdoc = http://www.navisys.com.tw/products/image/GR-300_flyer-080409.pdf 2060tested = 2.38 2061vendor = Navisys 2062notes = Also includes an (untested) Bluetooth interface. Has two LEDs: 2063 blue for bluetooth, green for rating. Solid green = on and searching 2064 for satellite fixes. Blinking green = on and has 3D fix. 2065 Also a similar GR-310 version available. It is possible that only GR-310 2066 supports Bluetooth. Programs only seem to be able to communicate 2067 with the dongle at 4800 baud rates, though this is autodetected by gpsd 2068 with no problems. Approx £40 per <a href="http://www.navisys.com.tw/products/gps_usb_dongle.htm">dongle</a>. 2069 2070#%Nokia 2071 2072[LD-4W] 2073type = device 2074uses = SiRF-3 2075date = 2009-12-05 2076location = Oulu, FI, 65N 25E 2077model = LD-4W 2078interfaces = Bluetooth 2079noconfigure = yes 2080packaging = mouse 2081rating = fair 2082submitter = jussi.kivilinna@mbnet.fi 2083techdoc = http://www.microsoft.com/en/mobile/phones/ 2084tested = 2.39 2085vendor = Nokia 2086logs = nokia-ld-4w.log 2087notes = I first tried gpsd package from Ubuntu 9.10, which broke 2088 device on probe. Luckily this device has 'reset' function by 2089 pressing power button for 10 sec. Then I recompiled gpsd with 2090 only support for Generic NMEA and SiRF binary and with fixed 2091 speed (--enable-fixed-port-speed=9600). Now device works in sirf 2092 mode, and does not break on probe. 2093 2094#% NovAtel 2095 2096[SuperStar II (202)] 2097type = device 2098vendor = NovAtel 2099packaging = OEM Module 2100uses = NovAtel-L1 2101techdoc = http://www.novatel.com/Documents/Manuals/om-20000077.pdf 2102tested = 2.38 2103discontinued = True 2104interfaces = RS-232 2105pps = True 2106submitter = Chris Kuethe <chris.kuethe@gmail.com> 2107notes = There are quite a number of models of SuperStarII, this is a 2108 169-613955-202 (1Hz, Carrier Phase, Timing, 19200). Other SuperStarII 2109 boards should work. 2110 2111#% Parrot 2112 2113[CK3300] 2114type = device 2115vendor = Parrot 2116packaging = handsfree 2117techdoc = http://www.parrot.com/ 2118engine = unknown 2119interfaces = Bluetooth 2120tested = 2.35 2121rating = good 2122nmea = 2.? 2123submitter = Andy Brown <andy@thebmwz3.co.uk> 2124notes = In-car hands-free bluetooth phone and GPS device. Outputs NMEA 2125 2126#% Pharos 2127 2128[GPS-360] 2129type = device 2130vendor = Pharos 2131packaging = mouse 2132techdoc = http://www.pharosgps.com/support/igps360_spec.htm 2133uses = SiRF-2 2134interfaces = USB 2135usbchip = pl2303 2136tested = regression 2137nmea = 2.3 2138discontinued = True 2139submitter = Robert Pouliot <krynos@saturnus.com> 2140notes = The Pharos comes with adaptors for SDIO, CF, USB and plain 2141 RS-232. Usually ships with XTrac firmware. It is strongly 2142 recommended that this device not be flashed with a different 2143 firmware as all reflashed receivers tested thus far fail to work 2144 afterward. May come bundled with Microsoft Streets and Trips. 2145 2146[iGPS-500] 2147type = device 2148vendor = Pharos 2149packaging = mouse 2150techdoc = http://www.pharosgps.com/products/proddetail.asp?prod=006_PB010_1.00&cat=141 2151uses = SiRF-3 2152subtype = GSC3f 2153usbchip = PL2303 2154interfaces = USB 2155tested = 2.3 2156submitter = Aurelian Maga <aurelianmaga@yahoo.com> 2157 2158#% Phonix 2159 2160[BGR6205] 2161type = device 2162vendor = Phonix 2163packaging = mouse 2164techdoc = http://www.phonix.it/html/catalogo_dettaglio.cfm?idProducts=E09B5AB7-BCDF-DF66-24853E2B4680AB2C 2165uses = SiRF-2 2166interfaces = Bluetooth 2167configurable = insane 2168tested = 2.34 2169nmea = 2.2 2170notes = As this is a Bluetooth device, gpsd must either be run with "-b" or must 2171 be compiled with fixed port speed, as the Bluetooth interface does not 2172 tolerate port speed changes at all. Reported by Sebastiano Zabert 2173 (no emal address) 2174 2175#% Qstarz 2176 2177[BT-Q818] 2178type = device 2179vendor = Qstarz 2180uses = MTK 2181interfaces = Bluetooth 2182date = 2010-06-03 2183location = +34d 1m 58.80sec, -117deg 44min 49.56sec 2184model = BT-Q818 2185notes = Had to use the -b option. 2186packaging = mouse 2187rating = excellent 2188sample_notes = Not moving. Left unit on a north facing window sill. 2189submitter = jason.komut+gpsd@gmail.com 2190techdoc = http://www.qstarz.com/download/BT-Q818%20Quick%20Guide-V1.pdf 2191tested = 2.92-4 2192logs=bt-q818.log 2193 2194#% RF Solutions 2195 2196[GPS-320FW] 2197type = device 2198engine = SE4100L 2199interfaces = TTL 2200nmea = 3.01 2201packaging = chipset 2202rating = fair 2203submitter = Stoo <f4eru@free.fr> 2204techdoc = http://www.rfsolutions.co.uk/acatalog/DS320-2.pdf 2205vendor = RF Solutions 2206notes = Has a binary protcol documetened at 2207 http://www.rfsolutions.co.uk/acatalog/DS-41COM-2.pdf. 2208 Sat-simulator testing reveals that the chipset does not handle 2209 dates after 2019 well; they wrap to 1999. The device sends out 2210 "$PLCS,REV,PLN012054S07,070312,145743" at reset, not documented. 2211 May actually be manufactured by Unitraq as the GP-320FW. 2212 2213#% Rikaline 2214 2215[GPS-6010 USB] 2216type = device 2217vendor = Rikaline 2218packaging = mouse 2219techdoc = http://www.rikaline.com/download/GPS-6010-Manual-E.pdf 2220uses = SiRF-2 2221interfaces = USB 2222usbchip = pl2303 2223tested = 2.20 2224nmea = 2.2 2225notes = Uses SiRF firmware version 2.3.2-GSW2-2.05.024-C1Prod1.1. Manufacturer 2226 claims it is waterproof (1 meter), WAAS and EGNOS are supported. 2227 2228[GPS-6010-X5] 2229type = device 2230vendor = Rikaline 2231packaging = mouse 2232techdoc = http://www.rikaline.com/gps_receiver.htm 2233uses = SiRF-2 2234interfaces = USB 2235usbchip = PL2303 2236tested = 2.20 2237nmea = 2.2 2238submitter = Koos van den Hout <koos@kzdoos.xs4all.nl> 2239notes = The USB cable is a separate item to order. You can also order an 2240 RS-232 cable or a PDA cable. 2241 2242#% Royaltek 2243 2244[Sapphire USB] 2245type = device 2246vendor = Royaltek 2247packaging = mouse 2248techdoc = http://www.royaltek.com/content/view/27/27/ 2249uses = SiRF-2 2250interfaces = USB 2251tested = 1.97 2252nmea = 2.2 2253notes = There is an RS-232 variant as well, not yet tested. 2254 2255[RGM-3600] 2256type = device 2257uses = SiRF-3 2258firmware = GSW3.2.5_3.3.01.06_SDK001P1.00 2259interfaces = USB 2260nmea = 3.0 2261notes = Works out of the box. 2262packaging = mouse 2263rating = excellent 2264submitter = Stijn Ghesquiere <stijn@applesnail.net> 2265techdoc = http://www.royaltek.com/FileDownload.php?dir=Product_C1_Info&file=RGM-3600%20operational%20manual%20V1_1209966059.pdf 2266tested = 2.37 2267vendor = Royaltek 2268 2269[RGM-3800] 2270type = device 2271techdoc = http://www.royaltek.com/products_dtl.php?cid=2&id=23&argPage=1&argI=3 2272vendor = Royaltek 2273packaging = mouse 2274uses = SiRF-2 2275subtype = GSC3f/LP 2276interfaces = USB (PL2303) 2277tested = regression 2278nmea = 3.0 2279submitter = Philipp Klenze <hq.ks@web.de> 2280notes = This is a GPS data logger with mouse functionality. Before it can be 2281 used with gpsd, the mouse functionality has to be switched on. That 2282 can be done with the rgm3800py utility by Karsten Petersen. The author of 2283 said tool has been very helpful to me by describing how to do that on 2284 the <a href="http://code.google.com/p/rgm3800py/wiki/GPSd"> 2285 projectpage</a>. Basically, one needs to run "rgm3800.py -d 2286 /dev/ttyUSB0 gmouse on" before starting gpsd. 2287 2288#% Saab 2289 2290[Saab R4] 2291type = device 2292date = 2011-06-01 2293interfaces = Other 2294model = SAAB AIS GPS R4 positioning system 2295uses = Pilot Plug 2296notes = This is data from the PilotPlug, AIS + NMEA from various 2297 instruments on a Transas bridge. This is not normal GPS 2298 data. Pilotplugs are RS422, 38400 8N1. This data is obtained via 2299 a Moxa UPort 1130 using Minicom. GPSD does not work well with 2300 the UPort 1130, but the data is recognised (but not all NMEA 2301 sentences). This is from a simulator but with real equipment. 2302packaging = other 2303rating = broken 2304submitter = vwf@vulkor.net 2305techdoc = http://www.saabgroup.com/Civil-security/Maritime-Transportation-and-Port-Security/Traffic-Management-Solutions/Shipborne-AIS--NAV-Solutions/R4-GPS--DGPS--Navigation-System/ 2306tested = 2.95 2307vendor = Saab 2308logs = saab-r4 2309 2310#% San Jose Navigation 2311 2312[FV-18] 2313type = device 2314vendor = San Jose Navigation 2315packaging = OEM module 2316techdoc = http://www.sanav.com/gps_engine_board/fv-18.htm 2317engine = FV-18 2318interfaces = UART 2319tested = 2.0 2320rating = good 2321nmea = 2.3 2322notes = Special gpsd support uses 8N2 and requests sentences that gpsd requires. 2323 OEM module only, not a retail product. 2324 2325[FV-25] 2326type = device 2327vendor = San Jose Navigation 2328packaging = OEM module 2329techdoc = http://www.tri-m.com/products/systems/fv25.html 2330uses = ANTARIS 2331subtype = TIM-LP 2332interfaces = UART 2333tested = 2.34 2334pps = True 2335notes = OEM module, available in small quantities from Tri-M 2336 systems. The ANTARIS chipset is obsolete, replaced by 2337 ANTARIS4. This module works in NMEA mode; gpsd also supports the 2338 UBX binary protocol. Firmware updates are available from ublox; 2339 the update is strongly recommended as it fixes a number of UBX 2340 bugs, and adds useful new features. 2341 2342[FV-M11] 2343type = device 2344vendor = San Jose Navigation 2345engine = MTK 2346packaging = OEM module 2347techdoc = http://www.sanav.com/gps_engine_board/FV-M7_FV-M11.htm 2348interfaces = UART 2349rating = good 2350tested = regression 2351submitter = Henk Fijnvandraat (no email address) 2352logs = mtk-3301.log 2353 2354[GM-38/12V] 2355type = device 2356vendor = San Jose Navigation 2357packaging = mouse 2358techdoc = http://www.tri-m.com/products/systems/gm38.html 2359engine = Furuno GN-77 2360interfaces = RS-232 2361tested = 2.21 2362nmea = 2.x 2363discontinued = True 2364rating = broken 2365notes = Ships bad packet checksums when it does not have a fix. 2366 2367#%Sejat 2368 2369[SJ-5210] 2370type = device 2371engine = SiRF-3 2372date = 2011-05-04 2373interfaces = USB 2374location = Boise, ID: 43deg 33min 52sec N / 116deg 13min 22sec W 2375model = SJ-5210 2376notes = Page that comes with it states: NMEA 0183 - CGA, GSA, GSV, RMC 2377 Baud Rate - 4800 bps; Datum WGS-84 2378 SiRF Star III 20-channel 2379 -159 dBm sensitivity 2380 Frequency L1, 1575.42 Mhz, C/A Code: 1023 Mhz Chip Rate 2381 Acq time: Hot start 1 sec/ warm start 38 sec/cold start 42 sec (ave) 2382 WAAS/EGNOS supported 2383 Do not know (but doubt) device handles baud rate changes. 2384packaging = mouse 2385rating = excellent 2386submitter = rickyrockrat <gpib@rickyrockrat.net> 2387techdoc = http://www.sejats.com/SEJAT-SJ-5210-USB-Mouse-GPS-Receiver-w-SiRF-star-III-SJ-5210.htm 2388tested = 2.92 2389vendor = Sejat 2390 2391#%Skytraq 2392 2393[Venus634LP] 2394type = device 2395engine = SkyTraq Venus 6 2396interfaces = TTL 2397date = 2010-02-05 2398firmware = ver,011023,rev,090210 2399location = Minsk, Belarus, 53N 27E 2400model = Venus634LP 2401nmea = 3.01 2402notes = Supports A-GPS from the SkyTraq FTP server. 2403packaging = OEM module 2404rating = good 2405submitter = Viktar Palstsiuk <viktar.palstsiuk@promwad.com> 2406techdoc = http://www.skytraq.com.tw/download/Venus634LPx_PB_v3.pdf 2407tested = 2.90 2408vendor = SkyTraq 2409logs = venus634lp.log 2410 2411#%Sure 2412 2413[SKG16B] 2414type = device 2415users = MTK 2416engine = MTK 2417interfaces = Bluetooth, USB, RS-232 2418date = 2015-04-11 2419firmware = MTK-3301 AXN_1.36-0000 2420model = SKG16B 2421nmea = 3.01 2422notes = See David Taylor's page: http://www.satsignal.eu/ntp/Sure-GPS.htm 2423techdoc = http://sure-electronics.net/download/GP-GS010_Ver2.0_EN.pdf 2424packaging = OEM module 2425rating = excellent 2426pps = True 2427pps_accuracy = 50ns 2428time_offset = ? 2429submitter = Sanjeev Gupta <ghane0@gmail.com> 2430tested = 3.14 2431vendor = Sure 2432 2433#% Techway 2434 2435[TP-051] 2436type = device 2437vendor = Techway 2438packaging = mouse 2439techdoc = http://www.techwayinc.com.tw/TP-051.htm 2440uses = SiRF-2 2441interfaces = USB 2442usbchip = pl2303 2443tested = 2.3 2444nmea = 2.x 2445discontinued = True 2446notes = Advertises that it is waterproof. 2447 2448#% Telit 2449 2450[SL869] 2451type = device 2452engine = STA8088 2453submitter = Arn <arnerro@gmail.com> 2454vendor = Telit 2455techdoc = http://www.telit.com/module/infopool/download.php?id=4906 2456firmware = TELIT SW Version: SL869 v3.1.2.1 -STD -N96 2457packaging = OEM module 2458interfaces = TTL 2459location = Sydney, NSW, AU, -33.68 151.29 2460rating = good 2461date = 2012-11-25 2462logs = sl869.log 2463 2464#% TomTom 2465 2466[TomTom Go910] 2467type = device 2468vendor = TomTom 2469packaging = handsfree 2470techdoc = http://www.tomtom.com/en_us/drive/car/products/ 2471engine = SiRF-3 2472interfaces = USB 2473nmea = None 2474rating = broken 2475notes = This device does not have real-time data output, and is incompatible 2476 with GPSD. 2477 2478[Mark II Bluetooth GPS] 2479type = device 2480vendor = TomTom 2481engine = SiRF-3 2482interfaces = Bluetooth 2483date = 2010-06-20 2484location = Veldhoven, NL 2485nmea = Version 2.2 2486packaging = mouse 2487rating = good 2488sample_notes = The unit was stationary (sorry). It is a putty log after connecting to port 2947. 2489submitter = Jose Baars peut@peut.org 2490techdoc = http://download.tomtom.com/open/manuals/mob5_nav5/Wireless_GPS_manual_NAV5_MOB5.pdf 2491tested = 2.36 2492logs = tomtom-mkII.log 2493notes = I use this GPS as a time source. I use a time1 parameter of 2494 -1.4 in /etc/ntp.conf, but then it appears to provide time 2495 reliably within 100ms and only limited sky view. 2496 2497#% Transystem 2498 2499[iGPS-M] 2500type = device 2501vendor = Transystem 2502packaging = mouse 2503techdoc = http://www.transystem.com.tw/products/index_detail.php?mcat_no=2&cat_no=32&pno=10&ver=en 2504uses = uNav 2505interfaces = USB 2506usbchip = pl2303 2507tested = 2.28 2508submitter = Romain Goyet <r.goyet@gmail.com> 2509notes = Formerly sold under the corporate name "Bona CompuTech". 2510 2511[737A+ Bluetooth] 2512type = device 2513uses = MTK 2514date = 2011-11-10 2515interfaces = Bluetooth 2516location = Bend, Oregon 44N, 121W 2517model = 737A+ Bluetooth 2518nmea = 3.01 2519notes = USB ID: 0e8d:3329. Bluetooth (V1.2) and USB (V2) output. Linux sees 2520 the USB as a cell phone (/dev/ttyACM0). Seems a tad less 2521 sensitive than a SiRF III, but has 66 channels. Uses 2522 replaceable Lithium Ion battery that charges from the mini-USB 2523 connector. Small yet 32 hour runtime on a single charge. 2524packaging = mouse 2525rating = excellent 2526sample_notes = Covered up with aluminum foil until lost lock, started capture, 2527 removed foil and logged until a good fix. 2528submitter = Gary E. Miller <gem@rellim.com> 2529techdoc = http://www.transystem.com.tw/product/53/737A+%20User%20Manual_v1.3.pdf 2530tested = 3.2 2531logs = tr737A+.log 2532vendor = Transystem 2533 2534#% Trimble 2535 2536[Trimble Lassen SK] 2537type = device 2538vendor = Trimble 2539packaging = OEM module 2540techdoc = http://www.trimble.com/lassensk2.shtml 2541engine = Colossus RF ASIC, Scorpion DSP 2542interfaces = UART 2543tested = 2.26 2544rating = good 2545nmea = 2.1 2546notes = Reported by Rob Janssen (no email address) 2547 2548[Trimble Lassen IQ] 2549type = device 2550vendor = Trimble 2551packaging = OEM module 2552techdoc = http://www.trimble.com/lasseniq.shtml 2553engine = Colossus RF ASIC, IO-C33 (Epson C33 RISC) 2554interfaces = USB,RS-232 2555pps = True 2556pps_accuracy = 50ns 2557time_offset = 0.675s 2558usbchip = CP2102 2559tested = regression 2560rating = good 2561nmea = 3.0 2562submitter = Chris Kuethe <chris.kuethe@gmail.com> 2563logs = trimble-lassen_iq-3dfix.log, trimble-lassen_iq-playacar.log, 2564 trimble-lassen_iq.log 2565 2566[Trimble BX960] 2567type = device 2568vendor = Trimble 2569packaging = OEM module 2570techdoc = http://www.trimble.com/embeddedsystems/pdf/bx960_ds.pdf 2571engine = BD960 2572interfaces = Ethernet 2573tested = regression 2574rating = good 2575submitter = Miika Ojanen <mojanen@hytti.uku.fi> 2576notes = Firmware versoon 4.00, dated 2009-03-10 2577 2578[Accutime Gold] 2579type = device 2580packaging = other 2581submitter = Venkatesh Sandilya <vsandilya@gmail.com> 2582vendor = Trimble 2583techdoc = http://www.trimble.com/timing/acutime-gold-gps-antenna.aspx?dtID=support 2584engine = Trimble custom 2585interfaces = RS-232 2586tested = 3.9 2587rating = excellent 2588date = 2013-08-28 2589 2590#% u-blox 2591 2592[ANTARIS LEA-4H] 2593type = device 2594vendor = u-blox 2595packaging = OEM module 2596techdoc = http://www.u-blox.com/products/lea_4h.html 2597uses = ANTARIS4 2598tested = regression 2599interfaces = RS-232 2600pps = True 2601submitter = Andreas Stricker <andreas.stricker@fela.ch> 2602 2603[ANTARIS LEA-4S] 2604type = device 2605vendor = u-blox 2606packaging = OEM module 2607techdoc = http://www.u-blox.com/products/lea_4s.html 2608uses = ANTARIS4 2609interfaces = USB,UART 2610tested = regression 2611submitter = Ali Utku Selen <selenau@kentkart.com.tr> 2612 2613[ANTARIS LEA-4T] 2614type = device 2615vendor = u-blox 2616packaging = OEM module 2617techdoc = http://www.u-blox.com/products/lea_4t.html 2618uses = ANTARIS4 2619interfaces = USB,UART 2620tested = regression 2621pps = True 2622pps_accuracy = 50ns 2623time_offset = ? 2624submitter = Chris Kuethe <chris.kuethe@gmail.com> 2625 2626[EVK-5H-0] 2627type = device 2628uses = LEA-5H 2629date = 2010-08-21 2630interfaces = USB 2631location = Rotterdam, NL, 51.9N 4.6E 2632model = EVK-5H-0 2633packaging = other 2634rating = other 2635submitter = Stephan Dierick <sac.dierick@hccnet.nl> 2636techdoc = http://www.u-blox.com/images/downloads/Product_Docs/u-blox5_Protocol_Specifications%28GPS.G5-X-07036%29.pdf 2637vendor = u-blox 2638 2639[LEA 5Q] 2640type = device 2641engine = UBLOX NEO-5Q 2642date = 2011-02-02 2643interfaces = TTL 2644pps = True 2645pps_accuracy = 50ns 2646time_offset = ? 2647location = Adelaide, AU, 34.9S, 138.6E 2648model = LEA 5Q 2649notes = Sample contains GPGST (pseudorange noise statistics). 2650 This had to be manually enabled by sending "$PUBX,40,GST,1,1,1,0*5A\n" 2651 to the device. 2652packaging = OEM module 2653rating = excellent 2654submitter = Thomas Sprinkmeier <thomas.sprinkmeier@gmail.com> 2655techdoc = http://www.u-blox.com/customersupport/gps.g5/u-blox5_Protocol_Specifications(GPS.G5-X-07036).pdf 2656tested = 2.95 2657vendor = u-blox 2658logs = ublox-lea-5q.log 2659 2660[EVK-6H-0] 2661type = device 2662uses = LEA-6H 2663date = 2013-10-24 2664interfaces = R232, USB 2665location = Malvern, PA, 40N 75W 2666model = EVK-6H-0 2667packaging = other 2668rating = excellent 2669pps_accuracy = 50ns 2670time_offset = ? 2671submitter = Eric S. Raymond <esr@thyrsus.com> 2672techdoc = http://www.u-blox.com/images/downloads/Product_Docs/u-blox6_ReceiverDescriptionProtocolSpec_%28GPS.G6-SW-10018%29.pdf 2673vendor = u-blox 2674notes = This is the u-blox eval kit for the LEA-6H. Has both USB and 2675 RS232 with PPS outputs. Excellent indoor performance, and well 2676 suited for time service even though the 6H is not specialized 2677 for that. 2678 2679#% UniTraq 2680 2681[WGM-300U] 2682type = device 2683vendor = UniTraq 2684packaging = mouse 2685techdoc = http://www.wintec.com.tw/en/support_detail.php?cate_id=11&support_id=14 2686uses = Sony CXD2951 2687configurable = insane 2688interfaces = USB 2689usbchip = CP2101 2690tested = 2.35 2691nmea = 3.0 2692submitter = Reported by Ian Darwin <ian@darwinsys.com> 2693notes = This receiver operates as a generic NMEA device, the Sony 2694 binary protocol is unsupported. The receiver seems to lock up if 2695 too much data is thrown at it (ie. gpsd probes) thus it may 2696 require a read-only (-b) instance of gpsd. (We say 'may' because 2697 more recent instances of gpsd break the probe writes into pieces 2698 interleaved with read, and may no longer trigger this problem) 2699 2700[UD731] 2701type = device 2702vendor = UniTraq 2703packaging = dongle 2704techdoc = http://www.unitraq.com/product_main.php?id=17 2705engine = Skytraq Venus 524c 2706rating = excellent 2707interfaces = USB 2708usbchip = CP2101 2709tested = 3.4 2710nmea = 3.01 2711submitter = Reported by Eric S. Raymond <esr@thyrsus.com> 2712notes = Device has two variants; the basic receiver is 'R' and the 2713 version with additional data-logger capability is N. Emits only NMEA. 2714 Some Web sources incorrectly describe it as SiRF-3-based. 2715 2716#%Variotek 2717 2718[VT-BT-204] 2719type = device 2720engine = Skytraq Venus 6 2721date = 2010-03-20 2722model = VT-BT-204 2723packaging = mouse 2724interfaces = Bluetooth 2725#location = 48.13333 N 11.593281 E 2726#sample_notes = all time fixed 2727submitter = <claus.seitter@arcor.de> Claus Seitter 2728techdoc = http://variotek.de/wp-content/uploads/2009/02/vt_bt204_guide_english.pdf 2729vendor = Variotek 2730rating = good 2731 2732#% Wintec 2733 2734[WBT-200] 2735type = device 2736vendor = Wintec 2737packaging = mouse 2738techdoc = http://www.wintec.com.tw/en/product_detail.php?pro_id=57 2739engine = FastraX iTrax03 2740interfaces = Bluetooth, USB 2741usbchip = CP2101 2742tested = regression 2743nmea = 3.0 2744rating = good 2745submitter = Chris Kuethe <chris.kuethe@gmail.com> 2746notes = This receiver operates correctly as a generic NMEA device, 2747 iTalk support is also functional, though switching between NMEA 2748 and iTalk does not yet work, nor does any device configuration. 2749 2750 2751[WBT-201] 2752type = device 2753vendor = Wintec 2754packaging = mouse 2755techdoc = http://www.wintec.com.tw/en/product_detail.php?pro_id=65 2756uses = ANTARIS4 2757interfaces = Bluetooth, USB 2758usbchip = CP2101 2759tested = 2.33 2760submitter = Espen Talberg <espental@gmail.com> 2761notes = This receiver operates correctly as a generic NMEA device, UBX support 2762 is also functional, though switching between NMEA and UBX does not yet 2763 work, nor does any device configuration. 2764 2765 2766