| 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.
|
| |
|
|
|
|
|
|
| |
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...
|
| | |
|
| |
|
|
| |
regressions updated. Other rdivers prolly need similar fixes.
|
| |
|
|
|
| |
Also update the affected regression files. gpsd had been
throwing away the DGPS status.
|
| |
|
|
|
| |
This duplicates, but improves on the accuracy of GPVTG.
Also add a bit on PSTI,001 and PSTI,032
|
| |
|
|
|
|
|
| |
The time in the packet was seconds in the day. It needed to be
merged with the known date.
rergressions updated. The chk files clearly show it is better now.
|
| |
|
|
|
|
|
|
| |
The combine code stolen from the GPGSV/BDGSV combining code.
Just 2 regressions changed. No surprise since Beidu rarely seen
in the USA.
I eyeballed the changes in the chk files and they look good.
|
|
|
Notice that the chk file shows the sats are not properly marked.
Sat 214 is the only one marked used in a 3D fix!
|
