summaryrefslogtreecommitdiff
path: root/driver_nmea0183.c
Commit message (Collapse)AuthorAgeFilesLines
* driver_nmea0183: Update xxGSV to handle NMEA 4.10.Gary E. Miller2019-04-191-20/+91
| | | | | This only affected the ZED-M9P NMEA regressions, which were broken anyway...
* driver_nmea0183: remove redundant clears., add comment.Gary E. Miller2019-04-191-2/+4
| | | | | No need to do: session->gpsdata.satellites_visible = 0; After gpsd_zero_satellites() which does the same thing.
* driver_nmea0183: Whoops, debug code removed.Gary E. Miller2019-04-191-2/+2
| | | | Serves me right for commiting b4 second cup of coffee...
* ubxtool: Fix output of UBX-COMMS portId.Gary E. Miller2019-04-191-2/+10
|
* driver_nmea0183: Minor code cleanup. No functional change.Gary E. Miller2019-04-181-9/+36
| | | | Change bunch of "if" to one "switch, some other tweaks.
* driver_nmea0183: Prep work to support gnssid in xxGSV.Gary E. Miller2019-04-121-3/+18
| | | | This is needed to fix NMEA 4.10 decodes.
* driver_nmea0183: Comment on NMEA 4.10 additions to xxGSAGary E. Miller2019-04-111-1/+13
|
* driver_nmea0183: Comment new xxGSV field in NMEA 4.10Gary E. Miller2019-04-111-0/+11
|
* driver_nmea0183: rearrange nmeaid_to_prn(), no functional change.Gary E. Miller2019-04-111-21/+37
|
* driver_nmea0813: Add unused sentence types to table.Gary E. Miller2019-03-261-0/+17
| | | | | This cuts down on scary "unknown sentence" warings that freak some people out...
* gpsd_error_model(): be more consistent with HERR_SET.Gary E. Miller2019-03-261-0/+2
|
* driver_nmea0183: Add decode for $PGRME.Gary E. Miller2019-03-251-11/+86
| | | | Another one with cycle ender issues...
* driver_nmea0183: Minor table format cleanup.Gary E. Miller2019-03-251-2/+2
|
* drivber_nmae0183: Comment $xxDTM fails due to cycle ender.Gary E. Miller2019-03-251-0/+1
| | | | Comes after cycle ender, so never output...
* driver_nmea0183: Decode $xxDTM for datum.Gary E. Miller2019-03-251-1/+72
| | | | Oddly no output either...
* gps_data_t: Add datum field. Add decode for $PGRMM.Gary E. Miller2019-03-251-2/+28
| | | | | Sadly, $PGRMM is after a cycle ender and the data is never reported, so no regression changes. Cycle ender needs to get fixed...
* driver_nmea0183: Tweak $PSRFEPE. No regressions changes.Gary E. Miller2019-03-251-5/+8
| | | | Better log output. Keep time, even if invalid.
* VERR_SET: Removed flag from daemon. No regressions changed.Gary E. Miller2019-03-251-1/+0
| | | | Obviously redundant.
* driver_nmea0183: Use eph from $PSRFEPE if available.Gary E. Miller2019-03-251-2/+4
| | | | Use GPS values when possible instead of calculated values.
* driver_nmea0183: Use epv from $PSRFEPE if available.Gary E. Miller2019-03-251-2/+1
| | | | Use GPS values when possible instead of calculated values.
* driver_nmae0183: Command on $GPGBS.Gary E. Miller2019-03-231-0/+2
|
* driver_nmea0183: Add 3 more NMEA messages, but no new decodes.Gary E. Miller2019-03-231-1/+4
|
* Split epe into eph and sep.Gary E. Miller2019-03-221-3/+3
| | | | | | | | Try to do it with forward and backward compatibility, which is challenging with current miscojson. Sometimes epe was used to 2D estimated erro. Sometimes for 3D error. So make it explicit eph is 2D, and sep is 3D.
* Fix fencepost errors in GPS epoch (mainly comments).Fred Wright2019-03-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | The definition of GPS_EPOCH in gpsd.h is correct, but the comment specified the incorrect corresponding date, which is 06-Jan-1980, not 06-Jan-1981, which isn't even a Sunday. The century hack in driver_nmea0183.c establishes a 100-year window for interpreting two-digit years. For now, the range 1980-2079 is reasonable, given that the GPS epoch is 06-Jan-1980, and the mention of wrapping "at" 2080 is consistent with this, but the comment incorrectly placed the GPS epoch in 1981 (perhaps due to believing the wrong comment in gpsd.h), and the code was written to wrap *after* 2080, rather than *at* 2080. This would place the window at 1981-2080, which would screw up 1980 (admittedly an unlikely case). This is mostly about not misleading people reading the code than actual real-life trouble. TESTED: Existing tests pass. A test case for a year of "80" would be needed to actually verify the fix, though.
* driver_nmea0183: Move error checking into do_lat_lon().Gary E. Miller2019-03-191-92/+102
| | | | No regression changes, just simpler code.
* driver_nmea0183: Tweak xxGGA mode setting.Gary E. Miller2019-03-191-37/+41
|
* driver_nmea0183: Have xxGNS report No FIX from FAA mode.Gary E. Miller2019-03-191-11/+12
| | | | Also, ignore missing "nav status"
* driver_nmea0183: xxRMC: Stop reporting missing fields as zero.Gary E. Miller2019-03-181-17/+32
| | | | lat/lon/track/etc.
* driver_nmea0183: Have xxGGA set time and mode.Gary E. Miller2019-03-181-24/+30
|
* driver_nmea0183: Fix 32/64 bug in cycle enders.Gary E. Miller2019-03-181-62/+69
| | | | | | Long standing bug, that became obvious when more NMEA decodes were added. A 32 bit mask used to index into a 40 member array.o Also fix over agressive mode setting on $PSRFEPE.
* driver_nmea0183: Another place ss.ss -> ss.sssGary E. Miller2019-03-151-1/+1
| | | | Oh, and fix missing decimal point.
* driver_nmea0183: remove bad cast.Gary E. Miller2019-03-151-1/+1
|
* driver_nmea: Another place to report time to %.3fGary E. Miller2019-03-151-1/+1
| | | | Many NMEA now reporting ss.sss.
* driver_nmea0183: Better subseconds in merge_hhmmss().Gary E. Miller2019-03-151-3/+11
| | | | Might need to change subseconds to integer nanoseconds.
* driver_nmea0183: Fix comment about Telit malformed year.Gary E. Miller2019-03-151-1/+1
|
* driver_nmea0183: Handle 2099 on 32-bits as 1999.Gary E. Miller2019-03-151-1/+13
| | | | The 32-bit hosts will fail on 2038...
* Move epe from gps_data_t to be near its friends in gps_fix_t.Gary E. Miller2019-03-151-6/+4
| | | | No functional changes. Looks like epe never went anywhere...
* driver_nmea0183: $PSRFEPE,V sets MODE_NO_FIXGary E. Miller2019-03-141-4/+13
| | | | Only present in old SiRF.
* driver_nmea0183: xxGLL,V now sets MODE_NO_FIX.Gary E. Miller2019-03-141-2/+9
| | | | Better detection of NO FIX state.
* driver_nmea0183: Be more aggressive reporting NO_FIX in GPRMC.Gary E. Miller2019-03-141-9/+4
| | | | | Fixes long standing complaints that gpsd freezes instead of reporting NO FIX.
* driver_nmea0183: Add STATUS_SIM. Update status in GPGGA.Gary E. Miller2019-03-141-5/+13
| | | | | status = 8 supposed to be simulator mode. Older Garmin seems to use it for something undocuemnted.
* driver_nmea0183: Have $GPRMC,V, report no fix.Gary E. Miller2019-03-141-1/+2
| | | | Changed two regressions for the better.
* drier_nmea: Make merge_hhmmss() more paranoid, return error codes.Gary E. Miller2019-03-141-79/+108
|
* driver_nmea: Fix potential segfault w/ DD() in merge_ddmmyy()Gary E. Miller2019-03-141-3/+4
|
* driver_nmea0183: Be more paranoid in merge_ddmmyy()Gary E. Miller2019-03-141-2/+28
| | | | Check for properly formatted ddmmyy string.
* driver_nmea0813: Change merge_ddmmyy() to return errors.Gary E. Miller2019-03-141-11/+20
| | | | Try to catch bad dates...
* driver_nmea0183 and more: Decode $PSRFEPE add eps.Gary E. Miller2019-03-131-6/+11
| | | | | Turns out eps also came from other GPS, but never made it to TPV. Regressions changed to show new eps data.
* driver_nmea0183 and more: Decode $PSRFEPE, and epd.Gary E. Miller2019-03-131-2/+66
| | | | | Turns out epd also came from SiRF, but never made it to TPV. Regressions changed to show new epd data.
* driver_nmea0183: Be more consisten on gps_mask_t mask.Gary E. Miller2019-03-131-50/+37
| | | | | I suspect this catches a few unitialized variable cases. No changes to regressions.
* driver_nmea0183: Change $PSTI,030, use faa_mode() and altitude.Gary E. Miller2019-03-081-50/+35
| | | | No regression changes.
View Lorry Controller Status