summaryrefslogtreecommitdiff
path: root/test/daemon/tr737A+.log.chk
Commit message (Collapse)AuthorAgeFilesLines
* driver_nmea0183: Enforce NMEA 4.0 type PRNs.Gary E. Miller2019-05-021-8/+8
| | | | | | | | | | | | | | | | Up until now, the PWN was whatever the GPS said it was. With NMEA 4.10 this is no longer sustainable. The u-blox 9 defaults to NMEA 4.10, sort of. It sometimes puts NMEA 4.0 PRNs into NMEA 4.10 sentences. Some people like to use both u-blox binary and NMEA sentences mixed together, so the time has come to enforce the PRN complies with NMEA 4.0 extended numbering. Sadly this can not map exactly into u-blox numbering, but is a start. Fixing this uncovered other examples of non NMEA compliant sentences in the regressions. So many regressions changed. The most obvious change is that NMEA 4.0 puts the SBAS PRN in the range 33-64 and 152-158, not 120-158 as u-blox does.
* Split epe into eph and sep.Gary E. Miller2019-03-221-14/+14
| | | | | | | | 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.
* driver_nmea0183: Tweak xxGGA mode setting.Gary E. Miller2019-03-191-1/+1
|
* driver_nmea0183: Have xxGGA set time and mode.Gary E. Miller2019-03-181-4/+9
|
* gpsd_json: epe now in the JSON.Gary E. Miller2019-03-151-8/+8
| | | | Odd that it was never there before...
* driver_nmea0183: Be more aggressive reporting NO_FIX in GPRMC.Gary E. Miller2019-03-141-0/+3
| | | | | Fixes long standing complaints that gpsd freezes instead of reporting NO FIX.
* driver_nmea0183: Decode gnssid:svid from $xxGSV.Gary E. Miller2018-09-191-8/+8
|
* More test trimming.Eric S. Raymond2015-02-091-169/+0
| | | | | A concerted effort to reduce all tests to below 10K in volume each while preserving all significant test features.
* Shorten many regression tests to improve test time.Eric S. Raymond2015-02-081-1590/+0
|
* Fix stupid finger error in DOP computation.Eric S. Raymond2014-09-211-404/+404
|
* Second attempt at DOP computation fix.Eric S. Raymond2014-09-191-404/+404
|
* Fix a subtle error in DOP computation. This makes a prompt release a good idea.Eric S. Raymond2014-09-191-404/+404
|
* A bug fix for error modeling when NMEA 0183 reports empty DOP fields.Eric S. Raymond2014-09-191-4/+4
| | | | Required 13 regression-test rebuilds.
* Drop the obsolete tag field from JSON output. Bump the minor protocol number.Eric S. Raymond2014-08-241-466/+466
| | | | | | | Required a regression-test rebuild, of course. The field is still set by the TSIP and SiRF drivers; the SiRF driver actually uses it. It may be possible to eliminate the TSIP uses, but so far attempting this has produced odd regression-test failures.
* A fix to internal track interpolation - required some test load rebuilds.Eric S. Raymond2013-11-221-201/+201
|
* Do *not* clear DOPs every time a satellite picture comes from the receiver.Eric S. Raymond2013-01-151-406/+406
| | | | | | | | | | | | | | | | | | | Required a regression-test rebuild. The immediate reason for this was Savannah bug bug #37810: satellites_used always zero via gpsd socket with multi nmea GSA/GSV. As the user reporting said: The "satellites_used" field in a "struct gps_data_t" filled in by "gps_read" is always returning zero. This module emits GNGSA messages in a group of three. My information is that the first GNGSA pertains to GPS, second to GLONASS, third to QZSS. It also emits GSV messages using talker id's GL,GP,QZ. The larger point is that DOPs are likely to be valid for longer than a GSV reporting cycle; they change only slowly as the actual sat configuration does. So it makes sense to retain them.
* Test rebuild required by mike_t's last commit.Eric S. Raymond2012-10-231-202/+202
|
* Add a test load for the Transystem 737A+Eric S. Raymond2011-11-151-0/+1828
View Lorry Controller Status