| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Up until now, the PWN was whatever the GPS said it was. With NMEA 4.10
this is no longer sustainable. The u-blox 9 defaults to NMEA 4.10, sort
of. It sometimes puts NMEA 4.0 PRNs into NMEA 4.10 sentences.
Some people like to use both u-blox binary and NMEA sentences mixed
together, so the time has come to enforce the PRN complies with
NMEA 4.0 extended numbering. Sadly this can not map exactly into
u-blox numbering, but is a start.
Fixing this uncovered other examples of non NMEA compliant sentences in
the regressions. So many regressions changed. The most obvious
change is that NMEA 4.0 puts the SBAS PRN in the range 33-64 and
152-158, not 120-158 as u-blox does.
|
| |
|
|
| |
Another one with cycle ender issues...
|
| |
|
|
|
|
|
|
| |
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...
|
| |
|
|
|
| |
This changed some regressions as TPV now has a "status" field it
did not have before.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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...
|
| | |
|
| |
|
|
|
| |
Also update the affected regression files. gpsd had been
throwing away the DGPS status.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
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.
|
|
|
...to something more descriptive.
|
