summaryrefslogtreecommitdiff
path: root/test/daemon/bu303-moving.log.chk
Commit message (Collapse)AuthorAgeFilesLines
* driver_sirf: MID 2 decode set track and speed, but no data for those.Gary E. Miller2019-04-231-24/+24
| | | | 7 regressions were reporting track and speed incorrectly.
* bu303: Update regressions for GPOS Week Roll Over.Gary E. Miller2019-04-101-47/+47
| | | | | | The bu303 is SiRF II from almost 20 years old. The regression data has no data (leap second, UTC date, year) to help disambiguate the GPS epoch. So let it roll over for the next 20 years.
* Split epe into eph and sep.Gary E. Miller2019-03-221-12/+12
| | | | | | | | 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.
* gpsd_json: epe now in the JSON.Gary E. Miller2019-03-151-11/+11
| | | | Odd that it was never there before...
* pseudonmea: Add frac seconds to $GPRMC, no zero times.Gary E. Miller2019-03-131-12/+12
| | | | Replace zero times with blanks.
* pseudonmea: Add fractional seconds to $GPGGAGary E. Miller2019-03-131-12/+12
|
* psuedonmea: Make $GPGBS match NMEA 3.0 specGary E. Miller2019-03-131-11/+11
|
* libgpsd_core: Step clobbering epe when error modeling.Gary E. Miller2019-03-131-0/+11
| | | | | This released a flood of GPGBS. But the GPGBS are wrong format according to NMEA 3.0...
* driver_sirf: add gnssid:svid.Gary E. Miller2018-09-241-11/+11
| | | | Not hard since SiRF only uses GPS and SBAS.
* driver_sirf: Report ECEF in TPV.Gary E. Miller2018-06-171-12/+12
|
* Rebuild tests to deal with the leapsecond bump last night.Eric S. Raymond2017-01-011-59/+59
| | | | | | The broken tests are the ones where we have to do our own conversion from week/second to UTC because the device either doesn't supply UTC or its reporting is broken.
* Puedo GPGSA outputs 12 SATs and NaNs as empty.Gary E. Miller2016-07-181-1/+1
| | | | | | | | GPGSA is commonly taken to be 12 sats. Prevent ublox and TSIP drivers from outputting more. No regressions had more than 12 anyway. DOPs that were NaNs were output as 0.0. Now output as blanks. Too easy for a user to take 0.0 as a real number.
* Test rebuild required for the mid-2015 leap-second bump.Eric S. Raymond2015-07-111-54/+54
| | | | Explain what breaks on a leap-second transition, and why, in build.txt.
* More test trimming.Eric S. Raymond2015-02-091-155/+0
| | | | | A concerted effort to reduce all tests to below 10K in volume each while preserving all significant test features.
* Almost entirely eliminate use of sats_used array.Eric S. Raymond2015-01-101-32/+32
| | | | | | | 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.
* Revise SiRF driver to be get satellites-used info from the skyview sentence.Eric S. Raymond2015-01-091-32/+32
| | | | | | | | | | | Before, that information was partly coming from the navigation-solution message and being pieced together with related data from svinfo. This way of doing things is more consistent. While this change required a rebuild of four check files, the effects are minor. Fixes don't change, but some generated pseudo-NMEA does and the error modeler can sometimes compute error estimates in cases where the old code could not because of a determinant-zero condition.
* Fix an odd little bug in pseudo-NMEA reporting.Eric S. Raymond2014-09-221-31/+31
| | | | | | | | | | | | | | | | | | | | | | 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-91/+91
|
* Second attempt at DOP computation fix.Eric S. Raymond2014-09-191-91/+91
|
* Fix a subtle error in DOP computation. This makes a prompt release a good idea.Eric S. Raymond2014-09-191-91/+91
|
* Drop the obsolete tag field from JSON output. Bump the minor protocol number.Eric S. Raymond2014-08-241-62/+62
| | | | | | | 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-28/+28
|
* Do *not* clear DOPs every time a satellite picture comes from the receiver.Eric S. Raymond2013-01-151-65/+65
| | | | | | | | | | | | | | | | | | | 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.
* Rebuild some binary-driver tests. Explain why this is needed.Eric S. Raymond2012-07-021-146/+146
|
* SiRF regression loads needed to be rebuilt because MID4 no longer sets time.Eric S. Raymond2011-10-101-29/+29
|
* Emit "mode" before its dependent attributes in TPV, and timestamps with .3f.Eric S. Raymond2011-03-221-62/+62
| | | | Required a regression-test rebuild.
* Make generated ZDAs report a UTC timezome, since UTC is what they emit.Eric S. Raymond2011-02-011-31/+31
|
* In pseudo-NMEA generation, emit ZDA at top of cycle.Eric S. Raymond2011-02-011-0/+31
|
* Timestamps in TPV and SKY go from float seconds since Unix epoch to ISO8601.Eric S. Raymond2011-01-291-62/+62
| | | | | | | | 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).
* Go back to wiring in a default leap-second offset at start.Eric S. Raymond2011-01-201-124/+124
| | | | | I thought I could avoid this, but it turns out SiRF chips before firmware rev 2.3.2 don't reliably get a leap-second report either. Sigh...
* Stop making an assumption about the leap-second offset at startup.Eric S. Raymond2011-01-181-124/+124
| | | | | | | | | | | | Gains: the stored leap-second offset we used for this could go stale, breaking our regression tests in the process - itr's just dumb luck that it hasn't since done so since 2008. Losses: If the receiver doesn't have leap-second cached in NVRAM (e.g, between cold boot and the next subframe message) time will be inaccurate by a few more seconds. 10 regression test outputs of 66 had to be rebuilt.
* Clear DOPs only when we get a skyview report.Eric S. Raymond2010-04-201-89/+89
| | | | | | | | | | | | | | | 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.
* A longstanding bug in error modeling fixed.Eric S. Raymond2010-04-131-88/+59
| | | | | | The guard controllong DOP computation wasn't right. The result was that x/y error estimates were computed much less often than they should have been.
* Suppress JSON reporting of fields the fix quality won't support.Eric S. Raymond2010-03-271-1/+1
| | | | | | | | 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.
* Restrict usage scope of the fixbuffer private member.Eric S. Raymond2010-03-231-0/+29
| | | | | | | | | Change the data management slightly so the fixbuffer private member doesn't have to be exposed outside libgpsd_core.c any more. Oddly, this accidentally fixed a minor bug, shown by 5 regression tests in which the pseudo-NMEA code should have been generating $GPGBS (because ex/ey/ev show up in the TPV output) but weren't actually doing so. Other than these virtuous additions, all regression tests pass.
* Regenerate regression tests after changing to the Vincenty formula. Chris Kuethe2010-02-281-10/+10
| | | | | | | | Rather than computing the value the WGS84 ellipsoid semi-minor axis in every call to ecef_to_wgs84fix, and having this computation in a few different source files, use a predefined value. This slightly changes the output value of ecef_to_wgs84fix - in the least-significant digit, or about 0.1mm.
* There are client library tests now, so rename the 'stable' directory...Eric S. Raymond2009-11-301-0/+217
...to something more descriptive.
View Lorry Controller Status