| | 95 | [=#zoem8q] |
| | 96 | === '''u-blox ZOE-M8G''' (GW63xx) === |
| | 97 | References: |
| | 98 | - [http://dev.gateworks.com/datasheets/u-blox/ZOE-M8_DataSheet_(UBX-16008094).pdf ZOE-M8 Datasheet (UBX-16008094)] |
| | 99 | - [http://dev.gateworks.com/datasheets/u-blox/u-blox8-M8_ReceiverDescrProtSpec_(UBX-13003221)_Public.pdf u-blox M8 Receiver Protocol Specification] |
| | 100 | |
| | 101 | Features: |
| | 102 | * 72-channel u-blox M8 concurrent position receiver engine supporting multiple concurrent Global Navigation Satellite System's (GNSS): |
| | 103 | - [#gps GPS]: L1C/A (1575.42MHz) |
| | 104 | - [#glonass GLONASS]: L1OF (1602MHz) |
| | 105 | - [#beidou BeiDou]: B1l |
| | 106 | - [#galileo Galileo]: E1B/C |
| | 107 | - [#qzss QZSS]: L1C/A (1575.42MHz) |
| | 108 | - [#sbas SBAS]: WAAS/EGNOS/MSAS: L1C/A (1575.42MHz) |
| | 109 | * [#dgps Differential GPS] (DGPS): [#rtcm RTCM] 10402.3: |
| | 110 | * Navigation Update Rate: 10Hz (GPS&GLONASS) or 18Hz (GPS) |
| | 111 | * Accuracy: |
| | 112 | - Velocity: 0.05m/s |
| | 113 | - Heading: 0.3degrees |
| | 114 | - Horiz position: Autonomous 2.5m / SBAS 2.0m |
| | 115 | - PPS: 30ns RMS, 99% 60ns |
| | 116 | * Sensitivity: |
| | 117 | - Tracking & Navigation: -167dBm (GPS&GLONASS) -166dBm (GPS) -166dBm (GLONASS) -160dBm (BeiDou) -159dBm (Galileo) |
| | 118 | - Re-acquisition: -159dBm |
| | 119 | - Cold start: -147dBm |
| | 120 | * Acquisition: |
| | 121 | - Cold start Time-to-First-Fix (TTFF): 27s (GPS&GLONASS) or 30s (GPS only) |
| | 122 | - Hot start Time-to-First-Fix (TTFF): 1s |
| | 123 | * [#pps PPS]: |
| | 124 | - 30ns accuracy, configurable via UBX-CFG-TP5 with rate 0.25Hz to 10Mhz, high or low polarity, 0 to 2^32^ ms pulse width (see [http://dev.gateworks.com/datasheets/u-blox/u-blox8-M8_ReceiverDescrProtSpec_(UBX-13003221)_Public.pdf u-blox M8 Receiver Description including Protocol Specification] Chapter 18) |
| | 125 | - Default is 1Hz rising edge 100ms length |
| | 126 | - Note that for best PPS accuracy it is recommended to disable the SBAS subsystem |
| | 127 | * Communication: |
| | 128 | - 9600 baud, 8bit no parity, 1 stop bit, no flow control supporting multiple protocols: |
| | 129 | - [#nmea0183 NMEA]: Input / Output ASCII 0183 version 4.0 (configurable for 2.3 or 4.1) |
| | 130 | - [#ubx UBX]: Input / Output binary u-blox proprietary (see [wiki:gps#ubx ubx] below) |
| | 131 | - [#rtcm RTCM]: Input, messages 1,2,3,9 |
| | 132 | * Active Antenna: 15dB to 50dB recommended |
| | 133 | * Power Consumption (not including active antenna power consumption): |
| | 134 | - ~40mA@1.8V 72mW (Continuous) |
| | 135 | - ~12.5mA@1.8V 22.5mW (PSM, 1Hz) |
| | 136 | |
| | 137 | Power-on Defaults: |
| | 138 | * 9600 baud, 8 data bits, no parity, 1 stop bit: |
| | 139 | * GPS & GLONASS enabled |
| | 140 | * SBAS enabled |
| | 141 | * output: NMEA: GGA, GLL, GSA, GSV, RMC, VTG, TXT messages |
| | 142 | * input: UBX, NMEA, RTCM |
| | 143 | * PPS: 100ms active high pulse at 1Hz |
| | 144 | |
| | 145 | Note that the GPS is not connected to an RTC, battery backup, or external flash on Gateworks designs (which disallows for permanent configuration storage and firmware upgrade) |
| | 146 | |
| | 147 | The ZOE-M8 GPS has the following improvements over the EVA-M8: |
| | 148 | - Has built in SAW and LNA for passive antenna support whereas the EVA-M8 can't support passive antenna |
| | 149 | - Uses an internal TCXO (temperature compensated) oscillator to provide improved accuracy over the EVA-M8 which uses a crystal |
| | 150 | - Smaller footprint (4.5mm x 4.5mm x 1.0mm) device vs (7mm x 7mm x 1.1mm) |
| | 151 | - Supports Galileo and BeiDou. EVA-8M only supports GPS GLONASS |
| | 152 | - Improved sensitivity (-167dBm vs -164dBm) |
| | 153 | - Faster acquisition time (26s vs 33s) |
| | 154 | |
| | 155 | |
| 360 | | * [#pps PPS]: rising edge |
| | 426 | * [#pps PPS]: |
| | 427 | * ±25ns 1 sigma accuracy, configurable pulse width between 61ns and 998ms and configurable delay between 61ns and 998ms (see [http://dev.gateworks.com/datasheets/trimble/CONDOR_UG_2C_75263-00.pdf PMTK_API_SET_OUTPUT_CTL (PMTK324)]) |
| | 428 | * need to increase the PPS pulse width from the default 4.2us for pps-gpio to detect: |
| | 429 | {{{#!bash |
| | 430 | echo -n -e "\$PMTK324,0,0,1,0,1639344*24\r\n" > /dev/ttyS2 # 100ms pulse width on fix |
| | 431 | }}} |
| | 432 | * if you want to also assert PPS when GPS position is not yet fixed: |
| | 433 | {{{#!bash |
| | 434 | echo -n -e "\$PMTK324,0,0,1,1,1639344*25\r\n" > /dev/ttyS2 # 100ms pulse width no fix |
| | 435 | }}} |
| 419 | | * rising edge 1Hz 61ns |
| 420 | | * requires fix interval set to 1000ms or less - see datasheet for details |
| | 494 | * ±350ns accuracy, 1Hz, configurable edge, configurable width between 100us and 500ms, configurable delay, and configurable fix type |
| | 495 | * Configuration is done via TSIP packets (Trimble Standard Interface Protocol) or NMEA PTNLSPS message see Trimble_CopernicusII_reference_manual for details: |
| | 496 | {{{#!bash |
| | 497 | echo -n -e "\$PTNLSPS,1,1000000,1,0*73\r\n" > /dev/ttygps # 100ms pulse width no fix |
| | 498 | echo -n -e "\$PTNLSPS,2,1000000,1,0*70\r\n" > /dev/ttygps # 100ms pulse width fix required |
| | 499 | echo -n -e "\$PTNLQPS\r\n" > /dev/ttygps # query |
| | 500 | echo -n -e "\$PTNLSRT,F\r\n" > /dev/ttygps # factory reset (erase customer config, almanac, ephemeris, and last pos) |
| | 501 | }}} |
