| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Required a regression-test rebuild.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
...to something more descriptive.
|