| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | gpsd_json: RAW, only output freqid for GLO, skip GLO PRN 255. | Gary E. Miller | 2019-05-17 | 3 | -732/+732 |
| | | | | | | Only GLONASS uses freqid, no need for other GNSS. GLO PRN 255 is not tracked yet, useless in RAW. | ||||
| * | JSON/RAW: Add sigid, if non-zero. | Gary E. Miller | 2019-05-17 | 1 | -654/+654 |
| | | | | | | Only affects ZED-F9P for now. Easier than decoding the obs_code. | ||||
| * | driver_ubx: Forgot to rebuild zed rawx regression | Gary E. Miller | 2019-05-08 | 1 | -654/+654 |
| | | |||||
| * | driver_ubx: Improve RXM-RAWX decode for u-blox 9. | Gary E. Miller | 2019-05-06 | 1 | -654/+654 |
| | | | | | | | As expected, just changed the ZED-F9T regression. Sadly the u-blox signal ids do not match the RINEX signal ids, so a lot is just guessing... | ||||
| * | gpsd_json: Filter out PRN from SKY w/o Elevation and Azimuth | Gary E. Miller | 2019-05-06 | 4 | -28/+28 |
| | | | | | | | | NMEA says to not report bad elevation and azimuth, so follow that advice. This only affects some u-blox 8 binary, and one odd GREIS regression. | ||||
| * | driver_ubx: Forgot one regression... | Gary E. Miller | 2019-05-03 | 1 | -36/+39 |
| | | |||||
| * | driver_ubx: Separate ubx and NMEA PRNs. | Gary E. Miller | 2019-05-03 | 4 | -52/+52 |
| | | | | | | Also fixed some bugs. SBAS moved from 120-159 to 33-64,152-158. QZSS goes up to 199. | ||||
| * | driver_nmea0183: Enforce NMEA 4.0 type PRNs. | Gary E. Miller | 2019-05-02 | 24 | -317/+317 |
| | | | | | | | | | | | | | | | | | 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. | ||||
| * | driver_nmea0183: DOn't mark sat as used if ss==0 | Gary E. Miller | 2019-04-30 | 5 | -270/+270 |
| | | | | | | NMEA 4.10 tells us which sats a are used, but not which signal (L1, L2, etc). | ||||
| * | timebase: Rollback 2037+ dates to GPS eopch 1. | Gary E. Miller | 2019-04-24 | 2 | -127/+127 |
| | | | | | | | | | | | | Dates past 18-Jan-2038 break 32-bit time_t, and are a while off from now. So roll the GPS epoch back to 1 when week is past week 968 in epoch 2 (late in 2037). This fixes one GREIS regression, and allows the rollback of two more to their correct date. All regressions now pass again. Until 2037... | ||||
| * | driver_sirf: MID 2 decode set track and speed, but no data for those. | Gary E. Miller | 2019-04-23 | 7 | -189/+189 |
| | | | | | 7 regressions were reporting track and speed incorrectly. | ||||
| * | SiRF: replace sirfstar v regressions. | Gary E. Miller | 2019-04-23 | 2 | -775/+1074 |
| | | | | | | The old one was Jan 2019. After the roll over that put the time past the 2038 time_t roll over. Punt with a new regression. | ||||
| * | driver_ubx: Cleanup HPPPOSxx and POSxx decodes. | Gary E. Miller | 2019-04-23 | 1 | -1/+1 |
| | | |||||
| * | driver_ubx: UBX-NAV-PVT was using height above ellipsoid, not MSL. | Gary E. Miller | 2019-04-23 | 2 | -126/+126 |
| | | |||||
| * | u-blox: Add regression with HPPOSECEF, HPPOSLLH, EOE. | Gary E. Miller | 2019-04-22 | 2 | -0/+203 |
| | | | | | New messages not used yet. | ||||
| * | driver_ubx: Change cycle ender to use iTOW. | Gary E. Miller | 2019-04-22 | 6 | -82/+0 |
| | | | | | This cleaned up some regressions. | ||||
| * | driver_ubx: Fix minor TOW calc in UBX-NAV-SOL. | Gary E. Miller | 2019-04-22 | 4 | -140/+140 |
| | | | | | Changing the length of the cycle changed epc in some regressions. | ||||
| * | driver_nmea0183: Update xxGSV to handle NMEA 4.10. | Gary E. Miller | 2019-04-19 | 1 | -203/+203 |
| | | | | | | This only affected the ZED-M9P NMEA regressions, which were broken anyway... | ||||
| * | regressions: Add ZED-F9P binary and NMEA samples | Luke Reid | 2019-04-17 | 4 | -0/+6210 |
| | | | | | Signed-off-by: Gary E. Miller <gem@rellim.com> | ||||
| * | driver_ubx: Working cycle end detection. | Gary E. Miller | 2019-04-13 | 7 | -11/+189 |
| | | | | | | | | 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. | ||||
| * | GREIS regressions: Update for GPS rollover. | Gary E. Miller | 2019-04-13 | 3 | -171/+171 |
| | | | | | | The GPS Roll over puts the times in the current epoch. Nothing to worry about. | ||||
| * | ubxtool: Add end of cycle detection. | Gary E. Miller | 2019-04-12 | 1 | -0/+140 |
| | | | | | | This made the ublox-neo-m8n.log regression finally look good. Needed for u-blox 9. | ||||
| * | bu303: Update regressions for GPOS Week Roll Over. | Gary E. Miller | 2019-04-10 | 5 | -163/+163 |
| | | | | | | | 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. | ||||
| * | driver_zodiac: Stop calculating epx/epy, let gpsd_error_model(). | Gary E. Miller | 2019-03-26 | 1 | -21/+21 |
| | | | | | Oddly, gained eph, lost nothing, in regressions. | ||||
| * | driver_navcom: Move error math to gpsd_error_model() | Gary E. Miller | 2019-03-26 | 1 | -12/+11 |
| | | | | | The numbers look better now. | ||||
| * | driver_greis: Remove epx/epy computation. Do in gpsd_model_error(). | Gary E. Miller | 2019-03-26 | 4 | -459/+459 |
| | | | | | Wow, all these various computations of epx/epy, all different... | ||||
| * | driver_nmea0183: Add decode for $PGRME. | Gary E. Miller | 2019-03-25 | 1 | -1/+2 |
| | | | | | Another one with cycle ender issues... | ||||
| * | driver_zodia: Decopde map datum. | Gary E. Miller | 2019-03-25 | 1 | -21/+21 |
| | | | | | Shows in regression. | ||||
| * | driver_sirf: Decode datum. Finally a regression change! | Gary E. Miller | 2019-03-25 | 1 | -60/+60 |
| | | |||||
| * | daemon side: stop using VERR_SET. Exposed a bug in sirf driver. | Gary E. Miller | 2019-03-25 | 2 | -140/+140 |
| | | | | | It seems the gpsd epc is more pessimistic than from the GPS. | ||||
| * | driver_nmea0183: Use eph from $PSRFEPE if available. | Gary E. Miller | 2019-03-25 | 2 | -12/+12 |
| | | | | | Use GPS values when possible instead of calculated values. | ||||
| * | driver_nmea0183: Use epv from $PSRFEPE if available. | Gary E. Miller | 2019-03-25 | 1 | -3/+3 |
| | | | | | Use GPS values when possible instead of calculated values. | ||||
| * | Split epe into eph and sep. | Gary E. Miller | 2019-03-22 | 99 | -2899/+2899 |
| | | | | | | | | | 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. | ||||
| * | pseudonmea: remove bad sats from $GPGSV output. | Gary E. Miller | 2019-03-20 | 7 | -216/+179 |
| | | |||||
| * | driver_nmea0183: Missed one regression change. | Gary E. Miller | 2019-03-19 | 1 | -0/+7 |
| | | | | | The NMEA driver now seems to report NO_FIX much better. | ||||
| * | driver_nmea0183: Tweak xxGGA mode setting. | Gary E. Miller | 2019-03-19 | 12 | -37/+37 |
| | | |||||
| * | driver_nmea0183: Have xxGNS report No FIX from FAA mode. | Gary E. Miller | 2019-03-19 | 3 | -13/+16 |
| | | | | | Also, ignore missing "nav status" | ||||
| * | driver_nmea0183: xxRMC: Stop reporting missing fields as zero. | Gary E. Miller | 2019-03-18 | 15 | -284/+284 |
| | | | | | lat/lon/track/etc. | ||||
| * | driver_nmea0183: Have xxGGA set time and mode. | Gary E. Miller | 2019-03-18 | 34 | -234/+538 |
| | | |||||
| * | driver_nmea0183: Fix 32/64 bug in cycle enders. | Gary E. Miller | 2019-03-18 | 2 | -8/+0 |
| | | | | | | | Long standing bug, that became obvious when more NMEA decodes were added. A 32 bit mask used to index into a 40 member array.o Also fix over agressive mode setting on $PSRFEPE. | ||||
| * | driver_nmea0183: Handle 2099 on 32-bits as 1999. | Gary E. Miller | 2019-03-15 | 1 | -1/+1 |
| | | | | | The 32-bit hosts will fail on 2038... | ||||
| * | gpsd_json: epe now in the JSON. | Gary E. Miller | 2019-03-15 | 94 | -2669/+2669 |
| | | | | | Odd that it was never there before... | ||||
| * | pseudonmea: Tweak when $GPGBS is output. | Gary E. Miller | 2019-03-14 | 6 | -115/+151 |
| | | | | | Require time, epx and epy. Optional epv. | ||||
| * | pseudonmea: Don't report unknown lat/lon/spd/trk as zeros. | Gary E. Miller | 2019-03-14 | 1 | -40/+40 |
| | | | | | Report as empty. | ||||
| * | driver_nmea0183: $PSRFEPE,V sets MODE_NO_FIX | Gary E. Miller | 2019-03-14 | 2 | -0/+8 |
| | | | | | Only present in old SiRF. | ||||
| * | driver_nmea0183: xxGLL,V now sets MODE_NO_FIX. | Gary E. Miller | 2019-03-14 | 14 | -29/+132 |
| | | | | | Better detection of NO FIX state. | ||||
| * | driver_nmea0183: Be more aggressive reporting NO_FIX in GPRMC. | Gary E. Miller | 2019-03-14 | 30 | -0/+183 |
| | | | | | | Fixes long standing complaints that gpsd freezes instead of reporting NO FIX. | ||||
| * | driver_nmea0183: Add STATUS_SIM. Update status in GPGGA. | Gary E. Miller | 2019-03-14 | 2 | -5/+5 |
| | | | | | | status = 8 supposed to be simulator mode. Older Garmin seems to use it for something undocuemnted. | ||||
| * | driver_nmea0183: Have $GPRMC,V, report no fix. | Gary E. Miller | 2019-03-14 | 2 | -0/+2 |
| | | | | | Changed two regressions for the better. | ||||
| * | Regressions: cleanup april6_2019 test case. | Gary E. Miller | 2019-03-14 | 2 | -8/+5 |
| | | |||||
 |
index : delta/gpsd.git | |
| git.savannah.gnu.org: git/gpsd.git |
| summaryrefslogtreecommitdiff |