summaryrefslogtreecommitdiff
path: root/test/daemon/bu303-nofix.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-7/+7
| | | | 7 regressions were reporting track and speed incorrectly.
* bu303: Update regressions for GPOS Week Roll Over.Gary E. Miller2019-04-101-21/+21
| | | | | | 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.
* pseudonmea: Add frac seconds to $GPRMC, no zero times.Gary E. Miller2019-03-131-7/+7
| | | | Replace zero times with blanks.
* Rebuild tests to deal with the leapsecond bump last night.Eric S. Raymond2017-01-011-15/+15
| | | | | | 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.
* Test rebuild required for the mid-2015 leap-second bump.Eric S. Raymond2015-07-111-8/+8
| | | | Explain what breaks on a leap-second transition, and why, in build.txt.
* Drop the obsolete tag field from JSON output. Bump the minor protocol number.Eric S. Raymond2014-08-241-14/+14
| | | | | | | 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.
* Do *not* clear DOPs every time a satellite picture comes from the receiver.Eric S. Raymond2013-01-151-6/+6
| | | | | | | | | | | | | | | | | | | 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-7/+7
|
* Emit "mode" before its dependent attributes in TPV, and timestamps with .3f.Eric S. Raymond2011-03-221-14/+14
| | | | Required a regression-test rebuild.
* Timestamps in TPV and SKY go from float seconds since Unix epoch to ISO8601.Eric S. Raymond2011-01-291-14/+14
| | | | | | | | 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-21/+21
| | | | | 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-21/+21
| | | | | | | | | | | | 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-7/+7
| | | | | | | | | | | | | | | 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-7/+7
| | | | | | | | 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.
* There are client library tests now, so rename the 'stable' directory...Eric S. Raymond2009-11-301-0/+28
...to something more descriptive.
View Lorry Controller Status