summaryrefslogtreecommitdiff
path: root/test/daemon/trimble-lassen_iq-3dfix.log.chk
Commit message (Collapse)AuthorAgeFilesLines
* Split epe into eph and sep.Gary E. Miller2019-03-221-39/+39
| | | | | | | | 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.
* pseudonmea: remove bad sats from $GPGSV output.Gary E. Miller2019-03-201-42/+28
|
* gpsd_json: epe now in the JSON.Gary E. Miller2019-03-151-39/+39
| | | | Odd that it was never there before...
* pseudonmea: Tweak when $GPGBS is output.Gary E. Miller2019-03-141-0/+39
| | | | Require time, epx and epy. Optional epv.
* pseudonmea: In $GPGSV, ouput missing PRN as blanks, not zeros.Gary E. Miller2019-03-131-28/+28
|
* pseudonmea: Add frac seconds to $GPRMC, no zero times.Gary E. Miller2019-03-131-39/+39
| | | | Replace zero times with blanks.
* pseudonmea: Add fractional seconds to $GPGGAGary E. Miller2019-03-131-39/+39
|
* Change NMEA mode setting, thus major changes in gpsd_error_model().Gary E. Miller2019-03-071-39/+39
| | | | | | | | | | | | | | | | The start of this overly large patch was to simply move the test for MODE_2D/3D flipping, which only affect NMEA 183, back into driver_nmea0813.c But that was intertwined with how gpsd_error_model() computes derived variables, which required major changes to how NMEA 183 mode_2D/3D are set. This ultimatly led to major regression test results. Almost all for the better. I tried to break it up, but moving from one paradigm to another needed one big jump...
* TPV: Add leapseconds to TPV JSON.Gary E. Miller2018-11-051-39/+39
| | | | Most current gpsd drivers do not report leap seconds.
* Almost entirely eliminate use of sats_used array.Eric S. Raymond2015-01-101-39/+39
| | | | | | | Instead, set the used member in the satellites array directly where possible. The NMEA0183 and TSIP drivers still need a local equivalent. This changes pseudo-NMEA GSA output in several binary-protocol tests.
* Refactor representation of satellite data into an array of structs...Eric S. Raymond2014-09-221-53/+53
| | | | | | | | | | | | | | | | | | ...from a set of parallel arrays. This change flushed out a longstanding bug in the computation of DOPs for estimated error bars. Some test-load rebuilds were required: geostar-geos1m-binary.log.chk: With this change error estimates are computed and reported. trimble-lassen_iq-3dfix.log, trimble-lassen_iq-3dfix.log: the change revealed a bug in the computation of satellite-seen bits. Error estimates did not change. navcom.log: Error estimates changed. With these rebuilds, all regression tests pass.
* Fix an odd little bug in pseudo-NMEA reporting.Eric S. Raymond2014-09-221-39/+39
| | | | | | | | | | | | | | | | | | | | | | Um. What was I thinking when I wrote that guard? It zeroed out reports of satellites used. Required a rebuild of the following (binary-orotocol) test logs. test/daemon/bu303-climbing.log.chk test/daemon/bu303-moving.log.chk test/daemon/bu303-stillfix.log.chk test/daemon/italk-binary.log.chk test/daemon/navcom.log.chk test/daemon/superstar2.log.chk test/daemon/trimble-lassen_iq-3dfix.log.chk test/daemon/trimble-lassen_iq.log.chk test/daemon/ublox-aek-4t.log.chk test/daemon/ublox-lea-4t.log.chk test/daemon/ublox-sirf1.log.chk test/daemon/zodiac.log.chk After that, all regressiion tests pass.
* Fix stupid finger error in DOP computation.Eric S. Raymond2014-09-211-53/+53
|
* Second attempt at DOP computation fix.Eric S. Raymond2014-09-191-53/+53
|
* Fix a subtle error in DOP computation. This makes a prompt release a good idea.Eric S. Raymond2014-09-191-53/+53
|
* Drop the obsolete tag field from JSON output. Bump the minor protocol number.Eric S. Raymond2014-08-241-53/+53
| | | | | | | 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.
* Emit "mode" before its dependent attributes in TPV, and timestamps with .3f.Eric S. Raymond2011-03-221-39/+39
| | | | Required a regression-test rebuild.
* Make generated ZDAs report a UTC timezome, since UTC is what they emit.Eric S. Raymond2011-02-011-39/+39
|
* In pseudo-NMEA generation, emit ZDA at top of cycle.Eric S. Raymond2011-02-011-0/+39
|
* Timestamps in TPV and SKY go from float seconds since Unix epoch to ISO8601.Eric S. Raymond2011-01-291-39/+39
| | | | | | | | Protocol version number is bumped. Python and C test clients are known to work; interfaces of the C and Python client bindings are unchanged. Third-party client-side bindings which rely on naively copying JSON members will break (implementers have been repeatedly warned not to do this).
* Clear DOPs only when we get a skyview report.Eric S. Raymond2010-04-201-53/+53
| | | | | | | | | | | | | | | This solves the disappearing epx/epy bug on SiRFs, but it was actually a systemic problem that affected several drivers. Navigation solution messages were clearing DOPs, making it impossible for the error modeller to compute estimates. New logic: Clear DOPs only when we get a skyview report. They'll be regenerated by our visibility-matrix calculation when the skyview sentence is analyzed. If a sentence from the device supplies a DOP between the time the visibility calculation is done and when the next fix is reported, it will override our computed value. This might change later! This change required a regression-test rebuild.
* Suppress JSON reporting of fields the fix quality won't support.Eric S. Raymond2010-03-271-39/+39
| | | | | | | | This should suppress a bug reported by Greg Troxel where, due to numeric instability in geodetic fix computations, wecwere getting cross-archirecture differences in the low-order digits of altitude for invalid fixes on SiRF-II chips. This required that ten regression test be rebuilt; I eyeballed the diffs to make sure we didn't lose actual data.
* gpspipe exposed an orthogonality failure.Eric S. Raymond2009-12-031-0/+39
| | | | | | | | | | | | Fix it by adding a json switch separate from watch enable. This involved moving where fake NMEA is generated to a different place, treating it as just another form of report generation rather than a side effect of receiving a sentence. Also, some client-side code had to be changed to use the json flag. A side effect is that some binary-protocol devicers generate fake $GPGSA sentences somewhat more often than they used to, and this meant rebuilding four more regression tests.
* There are client library tests now, so rename the 'stable' directory...Eric S. Raymond2009-11-301-0/+173
...to something more descriptive.
View Lorry Controller Status