summaryrefslogtreecommitdiff
path: root/test/daemon/garmin-geko201.log.chk
Commit message (Collapse)AuthorAgeFilesLines
* gpsd_json: epe now in the JSON.Gary E. Miller2019-03-151-2/+2
| | | | Odd that it was never there before...
* driver_nmea0183: xxGLL,V now sets MODE_NO_FIX.Gary E. Miller2019-03-141-1/+19
| | | | Better detection of NO FIX state.
* driver_nmea0183: Be more aggressive reporting NO_FIX in GPRMC.Gary E. Miller2019-03-141-0/+1
| | | | | Fixes long standing complaints that gpsd freezes instead of reporting NO FIX.
* driver_nmea0183: Add STATUS_SIM. Update status in GPGGA.Gary E. Miller2019-03-141-3/+3
| | | | | 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. Miller2019-03-141-0/+1
| | | | Changed two regressions for the better.
* Change NMEA mode setting, thus major changes in gpsd_error_model().Gary E. Miller2019-03-071-0/+1
| | | | | | | | | | | | | | | | 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...
* driver_nmea0183: Decode gnssid:svid from $xxGSV.Gary E. Miller2018-09-191-18/+18
|
* nmea 0183: better fix for non-updating DOPs.Gary E. Miller2017-01-091-5/+5
| | | | regressions updated. Other rdivers prolly need similar fixes.
* Second attempt at DOP computation fix.Eric S. Raymond2014-09-191-18/+18
|
* Fix a subtle error in DOP computation. This makes a prompt release a good idea.Eric S. Raymond2014-09-191-18/+18
|
* Drop the obsolete tag field from JSON output. Bump the minor protocol number.Eric S. Raymond2014-08-241-20/+20
| | | | | | | 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.
* Do *not* clear DOPs every time a satellite picture comes from the receiver.Eric S. Raymond2013-01-151-18/+18
| | | | | | | | | | | | | | | | | | | Required a regression-test rebuild. The immediate reason for this was Savannah bug bug #37810: satellites_used always zero via gpsd socket with multi nmea GSA/GSV. As the user reporting said: The "satellites_used" field in a "struct gps_data_t" filled in by "gps_read" is always returning zero. This module emits GNGSA messages in a group of three. My information is that the first GNGSA pertains to GPS, second to GLONASS, third to QZSS. It also emits GSV messages using talker id's GL,GP,QZ. The larger point is that DOPs are likely to be valid for longer than a GSV reporting cycle; they change only slowly as the actual sat configuration does. So it makes sense to retain them.
* Emit "mode" before its dependent attributes in TPV, and timestamps with .3f.Eric S. Raymond2011-03-221-2/+2
| | | | Required a regression-test rebuild.
* Previous commit requires a test-suite rebuild.Eric S. Raymond2010-06-141-17/+0
| | | | It suppresses some previously emitted but contentless sentences.
* Complete privious change. Required rebuilding of three regressin tests.Eric S. Raymond2010-05-091-1/+0
|
* Clear DOPs only when we get a skyview report.Eric S. Raymond2010-04-201-35/+35
| | | | | | | | | | | | | | | 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.
* A longstanding bug in error modeling fixed.Eric S. Raymond2010-04-131-35/+35
| | | | | | 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.
* This commit resolves the time overflows in the rgm3800 and mkt3301.Eric S. Raymond2009-12-041-19/+19
| | | | | | | | | | | These were causing port problems on systems with 32-bit time. It turns out the problem was with the assumption that these devices always deliver a valid time in $GPRMC. They don't when the navigation warning bit (second field 'V') is on! The NMEA driver now knows. Also, the code now contains a sanity check - it will log a complaint if it sees a date moere than a year in the future. This invariably indicates some driver-level problem with time extraction.
* There are client library tests now, so rename the 'stable' directory...Eric S. Raymond2009-11-301-0/+250
...to something more descriptive.
View Lorry Controller Status