| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
7 regressions were reporting track and speed incorrectly.
|
|
|
|
|
|
|
| |
This should force output when people program their u-blox
in strange ways. The obvious effect on the regressions is
just extra TPV output. Need to improve the cycle detection
a bit more to prevent that.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Odd that it was never there before...
|
|
|
|
| |
Replace zero times with blanks.
|
| |
|
| |
|
|
|
|
|
| |
This released a flood of GPGBS. But the GPGBS are wrong format
according to NMEA 3.0...
|
|
|
|
| |
Most current gpsd drivers do not report leap seconds.
|
|
|
|
| |
Not hard since SiRF only uses GPS and SBAS.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Explain what breaks on a leap-second transition, and why, in build.txt.
|
|
|
|
|
| |
A concerted effort to reduce all tests to below 10K in volume each while
preserving all significant test features.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|