From a05b5ba9ef5a443c4dede52702048038ee0bf95c Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Mon, 19 Jan 2009 19:36:26 +0000 Subject: Part-conversion of hardware reference page to capability database... ..and a Python wrapper class that parses it. --- gpscap.ini | 587 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ gpscap.py | 35 ++++ www/hardware.html | 91 +++++---- 3 files changed, 670 insertions(+), 43 deletions(-) create mode 100644 gpscap.ini create mode 100644 gpscap.py diff --git a/gpscap.ini b/gpscap.ini new file mode 100644 index 00000000..58bbb6a6 --- /dev/null +++ b/gpscap.ini @@ -0,0 +1,587 @@ +# GPS capability description file +# +# Our apologies to all Unix hackers in advance for the grubby .INI syntax, +# we're using it because the format has good cross-Unix support in Python. +# +# Each section map have the following capabilities +# +# type = "engine", "vendor", or "device" +# description = Human-readable description of this item +# packaging = A device's form factor +# reference = URL to technical documentation, or at least a spec sheet +# vendor_site = URL of a vendor site +# vendor = vendor name +# eval_unit = Which GPSD devs have one for testing (list) +# engine = GPS chipset (may reference another section) +# interfaces = interface types: USB, RS232, Bluetooth, CF. May be a list. +# usbchip = USB I/O chipset +# pps = supports pulse-per-second precision time reporting +# btglitch = has bluetooth glitch (requires -b option) +# tested = last gpsd version tested with this +# nmea = NMEA version this emits, if known +# notes = Miscellaneous notes on this item. To be interpreted as HTML. +# broken = Boolean capability, True if incompatible with GPSD. +# +# Capability strings: +# +# to_nmea = if present, how to switch to NMEA 0183 mode from native binary +# to_native = if present, how to swith to native binary mode from NMEA +# modeset = set protocol, baud rate, 8N1 +# +# Inheritance +# +# To inherit capabilities from a specified section, name the section in +# a "uses =" attribute. Use chains are followed recursively. An attribute +# in a section overrides all attributes of the same name in all ancestor +# sections. +# +# Certain escapes in capability strings are translated: +# +# %b - baud rate as ASCII numeral +# +# A string beginning with 0x is interpreted as a sequence of paired hex bytes, +# leading 0x not included. +# +# Comment lines led with "#%" are vendor section marks to be used when +# generating an HTML table from this file. Each should consist of a vendor +# name. +# +# Further notes: +# * In the packaging feld, a "GPS mouse" is a standalone sensor in a +# display-less case designed be used as an outbard peripheral. An +# "OEM module" is an un-cased circuit board with edge connectors. +# A "handset" is a standalone GPS with a display and human-usable +# controls. A "car mount: is a unit with display designed for +# mounting on a car windshield + +# +# Chipsets +# + +[GenericSiRF] +type = engine +description = Capabilities generic to all SiRF chips +# Sets 4800 baud shipping GGA+GSA+GSV+RMC +to_nmea = 0xa0a200188102010100000101050101010000000100010001000112c00000b0b3 +to_native = $PSRF100,0,%b,8,1,0 # Sets 8N1 with specified speed + +[SiRF-1] +type = engine +description = Version 1 of the SiRF GPS engine +engine = SiRF-1 +nmea = 2.2 +uses = GenericSiRF +tested = 2.34 + +[SiRF-2] +type = engine +description = Version 2 of the SiRF GPS engine +engine = SiRF-2 +nmea = 2.2 +uses = GenericSiRF +tested = 2.37 + +[SiRF-3] +type = engine +description = Version 3 of the SiRF GPS engine +engine = SiRF-3 +nmea = 3.01 +uses = GenericSiRF +tested = 2.37 + +[Garmin] +type = engine +description = There are several versions; the differences are not clear. +reference = http://www.garmin.com/support/commProtocol.html + +[Nemerix] +type = engine +description = GPS engine chip +engine = Nemerix +nmea = 3.01 + +[uNav] +type = engine +description = GPS engine chip +engine = uN3010 +nmea = 3.01 +notes = uNav was acqired by Atheros in 2007. They have inherited + one GPS product, now designated uN3010. + +[Zodiac] +type = engine +description = GPS engine chip +engine=Zodiac +nmea = 2.2 +tested = 2.0 +notes = This chip was made by Rockwell International. It has been EOLed. + +# +# Vendors (alphabetical by vendor) +# + +[Altina] +type = vendor +vendor_site = http://www.altina.com + +[Adapt Mobile] +type = vendor +vendor_site = http://www.adapt-mobile.com> + +[Axiom] +type = vendor +vendor_site = http://gpsd.berlios.de/vendor-docs/axiom + +[Billionton] +type = vendor +vendor_site = http://www.billionton.com/english/index.htm + +[Transystem] +type = vendor +vendor_site = http://www.transystem.com.tw/ + +[Central Pacific] +type = vendor +vendor_site = http://www.cpit.com + +[Delorme] +type = vendor +vendor_site = http://www.delorme.com + +[EuroTronics] +type = vendor +vendor_site = http://www.eurotronic.net/ + +[Garmin] +type = vendor +vendor_site = http://www.garmin.com + +[GlobalSat] +type = vendor +vendor_site = http://www.globalsat.com.tw/english/products.php + +[Haicom] +type = vendor +vendor_site = http://www.haicom.com.tw/ + +# +# Devices (alphabetical by vendor) +# + +#% Altina + +[GBT709] +type = device +vendor = Altina +description = handset +reference = http://www.altina.com/produkty.php?destCatId=&mainCatId=13&subCatId=&prId=19 +interfaces = Bluetooth +btglitch = yes +tested = 2.35 +uses = SiRF-3 +notes = Requires the "-b" flag to prevent mode switching. If the receiver locks + up due to a mode switch, remove the battery for 5 to 10 minutes. + Reported by Benoit Panizzon <panizzon@woody.ch> + +#% Adapt Mobile + +[AD-500] +type = device +vendor = Adapt Mobile +packaging = GPS mouse +reference = http://adapt-mobile.bosqom.com/default.php?page_ID=3&spage_ID=1 +uses = Nemerix +interfaces = Bluetooth, USB +iochip = pl2303 +tested = 2.32 +notes = Reported by Dennis van Zuijlekom <tmib@xs4all.nl>. + +#% Axiom + +[Sandpiper] +type = device +vendor = Axiom +packaging = OEM module +reference = http://gpsd.berlios.de/vendor-docs/axiom +uses = SiRF-1 +interfaces = RS232C +tested = 2.34 +notes = The vendor is out of business, but there are lots of these still + around in 2006. Complete documentation for this OEM module has been + archived at the GPSD site. + +#% Billionton + +[Billionton CF-GPS] +type = device +vendor = Billionton +packaging = GPS mouse +reference = http://www.billionton.com/english/product/CF-GPS.htm +interfaces = CF +tested = 2.16 +notes = Uses SiRF firmware version 220.006.000ES. Accepts WAAS Mode Disable + ($PSRF108,00*02) and WAAS Mode Enable ($PSRF108,01*03) + controls. + Reported by Oleg Gusev <oleg@crista.uni-wuppertal.de>. + +#% Transystem + +[iGPS-M] +type = device +vendor = Bona +packaging = GPS mouse +reference = http://www.transystem.com.tw/products/index_detail.php?mcat_no=2&cat_no=32&pno=10&ver=en +uses = uNav +interfaces = USB +usbchip = pl2303 +tested = 2.28 +notes = Formerly sold under the corporate name "Bona CompuTech". + Reported by Romain Goyet <r.goyet@gmail.com> + +#% Central Pacific + +[CPIT GP-27] +type = device +vendor = Central Pacific +packaging = GPS mouse +reference = http://www.cpit.com/en/GP-27.html +uses = Nemerix +interfaces = Bluetooth +btglitch = True +notes = Reported by Tobias Minich <belgabor@gmx.de> + +#% Delorme + +[EarthMate USB] +type = device +vendor = DeLorme +packaging = GPS mouse +reference = http://www.delorme.com/earthmate/default.asp +uses = SiRF-2 +interfaces = USB +usbchip = Cypress M8 CY7C64013 +tested = 2.5 +notes = This was the replacement for the old Zodiac version that spoke + Rockwell binary protocol; it in turn has been discontinued. Some + other sentences can be enabled. Requires a 2.6.10 or better + kernel for the Cypress USB-HID support. + +[EarthMate] +type = device +vendor = DeLorme +packaging = GPS mouse +uses = Zodiac +interfaces = RS232C +notes = These models have been discontinued. + +[TripMate] +type = device +vendor = DeLorme +packaging = GPS mouse +reference = http://vancouver-webpages.com/peter/tripmate.faq +uses = Zodiac +interfaces = RS232C +notes = Discontinued sometime before November 1998. + +#% EuroTronics + +[Blumax GPS009] +type = device +vendor = EuroTronics +packaging = GPS mouse +reference = http://www.eurotronic.net/products/produktdetails/gps_receiver.html +uses = SiRF-3 +interfaces = Bluetooth +btglitch = True +tested = 2.36 +notes = Requires "-b" ... I had to totally drain the battery of the device + and let it rest for a few days before i was able to use it again + after a first attempt of using it with without "-b" + Reported by Hartmut Holzgraefe <hartmut&x40;php.net> + +#% Garmin + +[Garmin GPS-15] +type = device +packaging = OEM module +vendor = Garmin +reference = http://www.garmin.com/products/gps15/spec.html +uses = Garmin +interfaces = RS232 +tested = 2.33 +nmea = 2.0 +pps = True +notes = "$PGRMI,,,,,,,R" must be sent to reset the device before PPS + works; after about 5 minutes the PPS signal is detected properly + by GPSD. Reported by Jason Hecker + <jhecker@wireless.org.au> + + +[Garmin GPS-16] +type = device +packaging = GPS mouse +vendor = Garmin +reference = http://www.garmin.com/products/gps16/spec.html +uses = Garmin +interfaces = RS232 +tested = 2.7 +nmea = 2.0 +notes = DGPS information in GPGGA sentence is not returned. Magnetic + variation information is not available in binary mode. Garmin + uses a nonstandard 16-bit SNR scale for signal quality in + GSA. Can be switched to NMEA 3.0 with PGRMC1. Reported by Ron + Marosko, Jr. <rmarosko@wirelessfrontier.net> and + Amaury Jacquot <sxpert@esitcom.org>. + +[Garmin GPS-17N] +type = device +packaging = GPS mouse +vendor = Garmin +reference = http://www.garmin.com/products/gps17/spec.html +uses = Garmin +interfaces = RS232 +nmea = 2.0 or 3.0 +notes = The 17N has been discontinued and replaced by the 17HVS. + The interface was RS232 but used a custom RJ-45 jack. + Reported by Wojciech Kazubski <wk@ire.pw.edu.pl>. + +[Garmin GPS-17HVS] +type = device +vendor = Garmin +reference = https://buy.garmin.com/shop/shop.do?cID=158&pID=8630 +engine = Unknown +interfaces = RS232 +tested = 2.37 +nmea = 2.0 or 3.0 +notes = Reported by Ulrich Voigt + +[Garmin GPS-18 USB] +type = device +packaging = GPS mouse +vendor = Garmin +reference = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf +uses = Garmin +interfaces = USB +tested = 2.5 +nmea = N/A +notes = The USB version requires the Linux kernel garmin_usb driver + and requires that usbfs is mounted: mount -t usbfs none + /proc/bus/usb/

+ DOP (Dilution of Precision) information is not available (Garmin protocol + includes EPE only); gpsd uses EPE to approximate DOP. Magnetic variation + information is not available. Garmin uses a nonstandard 16-bit SNR scale. + +[Garmin GPS-18 (all but USB)] +type = device +packaging = GPS mouse +vendor = Garmin +reference = http://www.garmin.com/manuals/GPS18_TechnicalSpecification.pdf +uses = Garmin +interfaces = RS232 +tested = 2.5 +nmea = 2.0 and 2.3 +notes = The RS232 versions emit NMEA and are found by normal autoconfiguration. + GPS-18 LVC and GPS-18 LVC/5m have PPS outputs. WAAS is supported. + +[GPS-25LP] +type = device +packaging = OEM module +vendor = Garmin +reference = http://www8.garmin.com/products/gps25/spec.html +uses = Garmin +interfaces = RS232 +nmea = 2.0 +notes = Discontinued embedded module. + Reported by Daniele Giangrazi &t;daniele.giangrazi@elital.net> + +[Garmin 38] +type = device +vendor = Garmin +packaging = handset +reference = http://au.geocities.com/glennbaddeley/gps/data/GPS38_OwnersManualAndReference_June1997_RevB.pdf +uses = Garmin +interfaces = RS232 +notes = Discontinued. Reported by Pascal F. Martin <pascal.martin@cox.net> + +[Garmin 48] +type = device +vendor = Garmin +packaging = handset +reference = https://buy.garmin.com/shop/shop.do?pID=85 +uses = Garmin +interfaces = RS232 +nmea = 2.0 +notes = The 48 has been discontinued. The Garmin 12XL and 45 are + nearly identical and should work as well. Details on the Garmin + proprietary protocol can be found at here. + +[Garmin GPS 60] +type = device +vendor = Garmin +packaging = handset +reference = http://www.garmin.com/manuals/GPS60_OwnersManual.pdf +uses = Garmin +interfaces = USB, RS232 +tested = 2.33 +nmea = 3.01 +notes = Reported by Diego Berge + (contact) + +[Garmin GPS 76] +type = device +vendor = Garmin +packaging = handset +reference = http://www.garmin.com/manuals/GPS76_OwnersManual.pdf +engine = Garmin +interfaces = USB +usbchip = pl2303 +tested = 2.13 +nmea = 2.3 +notes = Reported by Sebastian Niehaus <killedbythoughts@mindcrime.net> + He says it is "Software Version 3.70". + +[Geko 201] +type = device +vendor = Garmin +packaging = handset +reference = http://www.garmin.com/manuals/Geko201_OwnersManual.pdf +engine = Garmin +interfaces = RS232 +nmea = 3.0 +notes = Reported by Jose Luis Domingo Lopez <jdomingo@24x7linux.com> + + +[eTrex Vista] +type = device +vendor = Garmin +packaging = handset +reference = http://www.garmin.com/manuals/eTrexVista_OwnersManual.pdf +engine = Garmin +interfaces = RS232 +tested = 2.32 +nmea = 3.0 +notes = Reported by Reed Hedges <reed@interreality.org> + +[Nuvi 650] +type = device +vendor = Garmin +packaging = car mount +reference = http://www.garmin.com/manuals/nuvi650_OwnersManual.pdf +engine = SiRFstarIII +interfaces = USB +tested = * +nmea = 3.0 +broken = True +notes = This device does not have real-time data output, and is incompatible with GPSD. + +#% GlobalSat + +[BC-307] +type = device +vendor = GlobalSat +reference = http://www.usglobalsat.com/item.asp?itemid=12 +uses = SiRF-2 +interfaces = CF +tested = 2.35 +nmea = 2.2 +notes = Acceptably functional running firmware 231ES. Reported by + Chris Kuethe <chris.kuethe@gmail.com>. + +[BT-318] +type = device +vendor = GlobalSat +packaging = GPS mouse +reference = http://www.globalsat.com.tw/english/products_detail.php?main_id=21&p_id=107 +engine = SiRF-2 +interfaces = Bluetooth +tested = 2.20 +nmea = 2.2 +notes = Reported by Frank Nicholas <frank@nicholasfamilycentral.com>. + +[BT-338] +type = device +vendor = GlobalSat +packaging = GPS mouse +reference = http://www.usglobalsat.com/item.asp?itemid=6 +engine = SiRF-3 +interfaces = Bluetooth +tested = 2.13 +notes = Reported by Michal Panczyk <mpanczyk@gmail.com> + +[BU-303] +type = device +vendor = GlobalSat +eval_unit = esr +packaging = GPS mouse +reference = http://www.usglobalsat.com/item.asp?itemid=11&catid=13 +engine = SiRF-2 +interfaces = USB +usbchip = pl2303 +tested = 2.24 +nmea = 2.2 +notes = Older versions of the BU-303 had a + design + defect that made it likely to fail if subjected to vibration or + +[BU-353] +type = device +vendor = GlobalSat +packaging = GPS mouse +reference = http://www.usglobalsat.com/item.asp?itemid=60&catid=17 +engine = SiRF-3 +interfaces = USB +usbchip = pl2303 +tested = pre-2.29 +nmea = 2.3 +notes = This receiver, or at least the firmware it ships with does not + support PPS timing output, nor does it support WAAS - something + born out by the claimed 10m positioning accuracy. These will + hopefully be fixed in future firmware revisions. The increased + sensitivity is nice, but the lack of WAAS and PPS could be + show-stoppers for various applications. + +[TripNav TN-200] +type = device +reference = http://www.usglobalsat.com/item.asp?itemid=45&catid=13 +engine = SiRFstarII +interfaces = USB +usbchip = FTDI FT232 +nmea = 2.2 +notes = We tested a version with SiRF Firmware level 231ES. The FTDI USB-to-serial + chip is supported only as alpha software not yet + incorporated into the Linux kernel, though it seems to be well + supported by OS X and various BSDs. It seems like the only + difference between this and the BU-303 is the different + USB-to-serial chip. + +#% Haicom + +[HI-204S] +type = device +vendor = Haicom +evaal_unit = esr +Packaging = GPS mouse +reference = http://www.haicom.com.tw/products.htm +engine = SiRF-II +interfaces = USB +usbchip = pl2303 +tested = 2.24 +nmea = 2.2 +notes = SiRF firmware level 231ES (XTrac). Haicom provided a test unit. Manual +states incorrectly that VTG is off by default. + + + diff --git a/gpscap.py b/gpscap.py new file mode 100644 index 00000000..689fbdf6 --- /dev/null +++ b/gpscap.py @@ -0,0 +1,35 @@ +""" + +gpscap - GPS capability dictionary class. + +""" +import ConfigParser + +class GPSDictionary(ConfigParser.RawConfigParser): + def __init__(self, *files): + "Initialize the capability dictionary" + ConfigParser.RawConfigParser.__init__(self) + if not files: + files = ["gpscap.ini", "/usr/share/gpsd/gpscap.ini"] + self.read(files) + # Resolve uses= members + while True: + keepgoing = False + for section in self.sections(): + if self.has_option(section, "uses"): + parent = self.get(section, "uses") + if self.has_option(parent, "uses"): + continue + # Found a parent section without a uses = part. + for heritable in self.options(parent): + if not self.has_option(section, heritable): + self.set(section, + heritable, + self.get(parent, heritable)) + keepgoing = True + self.remove_option(section, "uses") + if not keepgoing: + break + +if __name__ == "__main__": + d = GPSDictionary() diff --git a/www/hardware.html b/www/hardware.html index a9f12207..4f2884ff 100644 --- a/www/hardware.html +++ b/www/hardware.html @@ -212,20 +212,20 @@ Reported by Oleg Gusev <oleg@crista.uni-wuppertal.de>. -BONA Computech +Transystem - + -iGPS-M +iGPS-M Good uNav USB (PL2303) 2.28 3.0 Reported by Romain Goyet <r.goyet@gmail.com>.
-The chipset manufacturer's webpage is here. +The uNav engine chip is apparently now the Atheros u=N3010. - + Central Pacific @@ -262,10 +262,12 @@ may differ from the syntax found in several documents on the net. USB (Cypress M8 CY7C64013) 2.5 2.2 -This is the replacement for the old Zodiac version that spoke Rockwell -binary protocol. Some other sentences can be enabled. Requires a 2.6.10 or -better kernel for the Cypress USB-HID support. +This is the replacement for the old Zodiac version that spoke +Rockwell binary protocol; it has been discintinued as well. Some other +sentences can be enabled. Requires a 2.6.10 or better kernel for the +Cypress USB-HID support. + @@ -273,7 +275,7 @@ better kernel for the Cypress USB-HID support. EarthMate Good Zodiac -RS-232 +RS232 2.0 2.2? The old Zodiac version spoke Rockwell binary protocol. These models @@ -286,11 +288,10 @@ have been discontinued but are still common. TripMate Good Zodiac -RS-232 +RS232 1.97 ? - Discontinued sometime before November 1998. Takes optional latitude -and longitude initialization. + Discontinued sometime before November 1998. EuroTronic @@ -307,7 +308,7 @@ and longitude initialization. Requires "-b" ... I had to totally drain the device's battery and let it rest for a few days before i was able to use it again after a first attempt of using it with without "-b" -Reported by Hartmut Holzgraefe <hartmut&x40;php.net>;> +Reported by Hartmut Holzgraefe <hartmut&x40;php.net> @@ -319,7 +320,7 @@ Reported by Hartmut Holzgraefe <hartmut&x40;php.net>;> Garmin GPS-15 Good Garmin -RS-232 +RS232 2.33 2.0 @@ -335,7 +336,7 @@ Reported by Jason Hecker <jhecker@wireless.org.au> Garmin GPS-16 Good Garmin -RS-232 +RS232 2.7 2.0 @@ -354,12 +355,12 @@ and Amaury Jacquot <sxpert@esitcom.org>. Garmin GPS-17N Good Garmin -RS-232 +RS232 * 2.0 or 3.0 The 17N has been discontinued and replaced by the 17HVS. -The interface was RS-232 but used a custom RJ-45 jack. +The interface was RS232 but used a custom RJ-45 jack. Reported by Wojciech Kazubski <wk@ire.pw.edu.pl>. @@ -370,7 +371,7 @@ Reported by Wojciech Kazubski <wk@ire.pw.edu.pl>. Garmin GPS-17HVS Good Unknown -RS-232 +RS232 2.37 2.0 or 3.0 @@ -402,7 +403,7 @@ WAAS is supported. Garmin GPS-18 (all but USB) Good Garmin -RS-232 +RS232 2.5 2.0 and 2.3 The RS232 versions emit NMEA and are found by normal autoconfiguration. @@ -410,36 +411,36 @@ GPS-18 LVC and GPS-18 LVC/5m have PPS outputs. WAAS is supported. - + GPS-25LP Good Garmin -RS-232 +RS232 * 2.0 Discontinued embedded module. Reported by Daniele Giangrazi &t;daniele.giangrazi@elital.net> - + -Garmin 38 +Garmin 38 Excellent Garmin -RS-232 +RS232 * ? Discontinued. Reported by Pascal F. Martin <pascal.martin@cox.net> - + -Garmin 48 +Garmin 48 Excellent Garmin -RS-232 +RS232 * 2.0 Garmin 12XL and 45 are nearly identical and should work as well. Details @@ -453,22 +454,23 @@ on Garmin's proprietary protocol can be found Garmin GPS 60 Good ? -USB +USB, RS232 2.33 3.0 -Reported by Diego Berge (contact) + +Reported by Diego Berge (contact) -Garmin GPS 76 +Garmin GPS 76 Good Garmin USB (PL2303) 2.13 -? +2.3 Reported by Sebastian Niehaus <killedbythoughts@mindcrime.net> He says it's "Software Version 3.70". @@ -481,7 +483,7 @@ He says it's "Software Version 3.70". Garmin Geko 201 Good Garmin -RS-232 +RS232 * 3.0 Reported by Jose Luis Domingo Lopez <jdomingo@24x7linux.com> @@ -490,24 +492,24 @@ He says it's "Software Version 3.70". -Garmin eTrex ("Vista" model) +Garmin eTrex ("Vista" model) Good -? +Garmin RS232 2.32 -? +3.0 Reported by Reed Hedges <reed@interreality.org> -Garmin Nuvi 650 +Nuvi 650 No SiRFstarIII USB * -None +3.0 This device does not have real-time data output, and is incompatible with GPSD @@ -525,7 +527,7 @@ He says it's "Software Version 3.70". Acceptably functional running firmware 231ES. Reported by Chris Kuethe <chris.kuethe@gmail.com>. - + @@ -535,7 +537,10 @@ Chris Kuethe <chris.kuethe@gmail.com>. Bluetooth 2.20 2.2 -Reported by Frank Nicholas <frank@nicholasfamilycentral.com>. + +Reported by Frank Nicholas +<frank@nicholasfamilycentral.com>. + @@ -654,7 +659,7 @@ with XTrac Firmware. CF * ? -Adaptors for RS-232, USB, and Bluetooth operation are available. +Adaptors for RS232, USB, and Bluetooth operation are available. Reported by David Findlay <dave@davsoft.com.au> @@ -1172,7 +1177,7 @@ Reported by Angus Ainslie <angusa@deltatee.com>. ANTARIS LEA-4H Good ANTARIS -RS-232 +RS232 * 2.3 @@ -1309,7 +1314,7 @@ GPS, please tell us the following:

  • The GPS and (if applicable) USB-to-serial chip it uses. (Look at the output of lsusb(1), it may identify the USB-to-serial chip. If it gives a vendor and product ID, send us those numbers.)
    • -
  • The interface type (RS232, USB, CF, UART (= 5V TTL RS-232))
    • +
  • The interface type (RS232, USB, CF, UART (= 5V TTL RS232))
  • The vendor
  • Version of gpsd you tested with
  • NMEA version it emits, or '?' if the documentation doesn't say
    • @@ -1333,7 +1338,7 @@ your device in our regression tests.

    RS232 levels:

    -

    UART or TTL level RS-232 uses 0v and +5v, ordinary RS-232 uses -12v to -5v +

    UART or TTL level RS232 uses 0v and +5v, ordinary RS232 uses -12v to -5v and +5v to +12 volts for the signal (IIRC). These are not compatible, and attempting to combine them can zorch your GPS. Converters do exist, see Google.

    -- cgit v1.2.1