summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* ATT: change heading to %.3f to match Trimble precision.Gary E. Miller2018-09-113-58/+58
|
* Add regression for hemisphere GPS. Fix detection of empty GPHDT.Gary E. Miller2018-09-112-0/+1533
| | | | A GPHDT with no heading was output as a heading of 0.00.
* gpsd_json, AIS: add missing JSON terminators.Sven Geggus2018-09-042-0/+4225
| | | | | | | | This could create unparseable JSON messages. Including regression tests. Signed-off-by: Gary E. Miller <gem@rellim.com>
* Add GREIS (Javad) GPS driver.Gregory Fong2018-07-2910-0/+1499
| | | | | | | | | | | | All functional changes inside "#ifdef GREIS_ENABLE" Includes new regression tests. All regressions tests pass. Developed by Gregory Fong, with help and support from Virgin Orbit. Signed-off-by: Gary E. Miller <gem@rellim.com>
* Fix pseudo GSA generationGregory Fong2018-07-141-0/+4
| | | | | | | | | | | | At one point, the check for MODE_SET made sense in gpsd_binary_quality_dump(). But since then, the calling code was refactored to only invoke nmea_tpv_dump() when REPORT_IS is set, eliminating the dupes. Remove the MODE_SET check and update the affected binary regression check files to contain the expected GSA sentences. Signed-off-by: Gary E. Miller <gem@rellim.com>
* driver_italk: report ECEF in TPV.Gary E. Miller2018-06-171-3/+3
|
* driver_sirf: Report ECEF in TPV.Gary E. Miller2018-06-174-32/+32
|
* driver_skytraq: report ECEF data in TPV.Gary E. Miller2018-06-171-1/+1
|
* driver_ubx: Put ECEF data fro mUBX-NAV-SOL into TPV.Gary E. Miller2018-06-172-6/+6
|
* Support Galileo $GA... talkers and fix a couple of $GB casesChris Lawrence2018-06-151-6/+2
| | | | | | | | | | | | | | | | | | | | | | Now that the Galileo constellation is live, the NMEA 4.1 standard appears to have standardized on the "$GA..." prefix for Galileo-specific messages. The lexer currently filters these out; this patch ensures they go through to e.g. gpspipe -r. (I tore my hair out for days trying to figure out why these were not being passed through even though I could see them using screen etc.) Also added logic to the GSA and GSV message parsing to account for the Galileo messages. It probably needs more work to match up satellite numbers between the GSA and GSV messages and to account for the GNSS type field in NMEA 4.1, but it's a start at least. I also fixed a couple of situations where the 'GB' prefix was being ignored even though 'BD' was not. This leads to a regression in test/daemon/beidou-gb.log, but the "regression" is actually incorrect old behavior (JSON messages omitting BeiDou satellites) exposed by the patch. Signed-off-by: Gary E. Miller <gem@rellim.com>
* Implement processing of NMEA0183 - $GPVTG messagesdwilliams2018-06-135-75/+75
| | | | | | | Co-authored-by: hkpatel <hpatel@sea-machines.com> Co-authored-by: dwilliams <equipoise@gmail.com> Signed-off-by: Gary E. Miller <gem@rellim.com>
* UBX: revert end of cycle change, but make regression changes.Gary E. Miller2018-02-094-186/+66
| | | | | | | | | | 2 steps forward, one step back. Changing cycle end for UBX broke old UBX samples. Reverting that change breaks the new ECEF, that will need more work. Fixing when a UBX cycle is cleared broke the UBX regression tests, but the old way was wrong. So update the regression tests.
* Add ntrip sourcetable example.Gary E. Miller2017-12-152-0/+36
| | | | | The chk file is empty, not sure how to get 'scons check' to do the right thing with it. New bug #52678 to add regression on this flie.
* tests: add exact GPS mpdel number to ublox-8-time.logGary E. Miller2017-12-041-0/+0
|
* gpsfake: add test for ublox 8 in position hold (time) modeGary E. Miller2017-12-012-0/+490
| | | | | Interesting because it has no altitude in TPV, which used to crash gegps.
* Fixes broken regression test data for uBlox NEO-M8N.Fred Wright2017-10-071-120/+120
| | | | | | | | | | | | Commit 71a487d8, "Support UBX NAV-PVT", added a new regression test case, but the .chk data didn't actually match. All mismatches were a difference of 0.01 in the 'epc' value. Whether the difference is due to an actual code difference or excessive numeric sensitivity remains to be seen, but in the meantime this gets rid of the failure which seems to be consistent. TESTED: Ran "scons build-all check", which now succeeds.
* Support UBX NAV-PVTClark Li2017-09-192-0/+120
| | | | | | | NAV-SOL has only been retained for backwards compatibility; users are recommended to use the UBX-NAV-PVT message in preference. A regression test case using ublox-neo-m8n is also added.
* Revert "Support UBX NAV-PVT"Gary E. Miller2017-09-053-121/+1
| | | | | | | | | This reverts commit 22a020ec1c2bc85eff681ecacc6d2bb79fdddc9c. This commit broke PPS on uBlox. PPS would flip from offset 0 to offset -1, and back, every few minutes. Also stray characters (^M) in the log files.
* Support UBX NAV-PVTClark Li2017-08-073-1/+121
| | | | | | | | | | | | | NAV-SOL has only been retained for backwards compatibility; users are recommended to use the UBX-NAV-PVT message in preference. A regression test case using ublox-neo-m8n is also added. Also fix the checking on valid flags of iTOW and fTOW and process fTOW whose range is +-500us. Update test/dae/ublox-aek-4t.log.chk accordingly. Signed-off-by: Clark Li <clark.li@cohdawireless.com> Signed-off-by: Fred Wright <fw@fwright.net>
* Reverts broken portion of old character pushback change.Fred Wright2017-03-051-4/+6
| | | | | | | | | | | | | | | | | | | This one instance of the 63 character-pushback changes in commit fbaaaa76 broke the packet-regress test, though that was masked due to another bug's causing that test to be disabled. With this instance reverted, the test passes again. It's not entirely clear why a change within Zodiac-specific code broke one SiRF test and two Evermore tests, but that's empirically the case. This change affects one daemon regression test. The ublox-8 test begins with a $GPRMC sentence preceded by a bunch of garbage. The broken version of packet.c skips this sentence, while the fixed version recognizes it. The test data has been updated accordingly. TESTED: Manually ran the packet-regress test successfully. Ran "scons build-all www check".
* Updates packet-regress test data.Fred Wright2017-03-051-13/+15
| | | | | | | | | | | | | | This updates the test data to reflect the two new tests that were added in commit 58a35243. This was neglected before due to a bug (commit 40c40cc4) that causes the packet-regress test to be inaccessible. This test still doesn't pass due to a bug introduced in commit fbaaaa76, but this update makes the current failure equivalent to the previous failure. In particular, it avoids gratuitous miscompares due to mismatches in the line numbers. TESTED: Running the test manually now gets the same errors as it did prior to the addition of the new tests.
* UBX: add regression for MAX-M8QGary E. Miller2017-01-092-0/+2174
|
* nmea 0183: better fix for non-updating DOPs.Gary E. Miller2017-01-0933-612/+612
| | | | regressions updated. Other rdivers prolly need similar fixes.
* Rebuild tests to deal with the leapsecond bump last night.Eric S. Raymond2017-01-0111-270/+270
| | | | | | The broken tests are the ones where we have to do our own conversion from week/second to UTC because the device either doesn't supply UTC or its reporting is broken.
* Decode SkytTraq undocumented $STI sentence.Gary E. Miller2016-07-212-0/+20
| | | | | | | Eric will gag at my abuse of the parser, but I'm not up to a major resturcture today. Not sure how to output the error in JSON.
* Puedo GPGSA outputs 12 SATs and NaNs as empty.Gary E. Miller2016-07-185-29/+29
| | | | | | | | GPGSA is commonly taken to be 12 sats. Prevent ublox and TSIP drivers from outputting more. No regressions had more than 12 anyway. DOPs that were NaNs were output as 0.0. Now output as blanks. Too easy for a user to take 0.0 as a real number.
* Fix a typos in a date in a logfile comment.Fred Wright2016-07-141-1/+1
| | | | Signed-off-by: Gary E. Miller <gem@rellim.com>
* Adds regression data for Navika-100.Fred Wright2016-04-212-0/+409
| | | | | | | | | | | This is a "with fix" case for the Navika-100 chip, and includes GSV data for the real PRN 1. A previously fixed bug caused a phantom PRN 1 instance to appear for each GSV sentence, due to misinterpreting the signal ID as a satellite ID. TESTED: Verified that this test illustrates the "phantom satellite 1" bug prior to that bug's being fixed.
* Fixes bug in filtering of ID 0 in satellite views.Fred Wright2016-04-212-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | Because the GSV processing invokes nmeaid_to_prn() before checking for an apparent ID of zero, it was possible for zero (or blank) IDs for non-GPS sentences to get offset to nonzero values and hence not filtered out. This fix ensures that only nonzero values are adjusted. Due to this bug, two of the regression tests had incorrect reference results: 1) The nl2008u receiver includes the new signal ID field, though the reported value is (incorrectly) zero. Due to another bug (to be fixed separately), this is interpreted as an additional ID in each GSV sentence. The zero-ID filter excluded this correctly for GPGSV, but for GLGSV it saw phantom entries for "ID 37". 2) The sl869 receiver reports empty fields for unused satellite slots in any GSV sentence. Again, this didn't hurt for GPGSV, and the GLGSV test data happens to have a multiple of four satellites, but the QZGSV sentences produced phantom "ID 193" entries. TESTED: Ran "scons build-all check", which passed after updating the two regression cases noted above.
* RTCM3 is unsigned byte, not chars.Gary E. Miller2016-04-201-127/+127
| | | | | | | | | | | | | | This was causing problems in sign extension. On amd64/Gentoo sign was extended: (unsigned int)(char 0x80) became: 0xfffffff80 But on Pi2/Wheezy the same thing became: 0x80. The obvious fix is to make it unsigned, as god intended. All regression tests pass on pi2/wheezzy and amd64/gentoo.
* Fix regressions changed by GNGSA fix.Gary E. Miller2016-04-078-133/+133
|
* Stop adding 37 to some GN PRN's.Gary E. Miller2016-04-071-30/+30
| | | | | | | | What could go wrong with code that says this: /* GLONASS GL doesn't seem to do this, but better safe than sorry */ GPGSA prn 21 was becoming prn 58
* GPGSV took a blank as 0 then converted that to a PRNGary E. Miller2016-04-071-18/+18
| | | | | | Skip blanks now. Blank in BDGSV became PRN=200 Blank in GLGSV became PRN=37
* Fixes client.py bug ausing RTCM3.2 regression-test failures.Fred Wright2016-04-071-6/+0
| | | | | | | | | | | | | | | | | When an entire 4K buffer of packet data contains no newlines, it's simply retained for future use. But the code was failing to clear the previous response in that case, causing the caller to see duplicate data. Since this bug only mattered with lines longer than 4K bytes, and since even then it varied as a function of the alignment of lines vs. 4K boundaries, it was never seen on previous regression tests. TESTED: Ran "scons build-all check" with the updated code and the corrected test data for RTCM3.2. Signed-off-by: Gary E. Miller <gem@rellim.com>
* Replace corrupted log file.Gary E. Miller2016-04-072-146/+2280
| | | | All regressions pass.
* New regression: Skytraq NMEA DGPSGary E. Miller2016-04-062-0/+151
|
* Add "status" to TPV for DGPS notificationGary E. Miller2016-04-0614-287/+287
| | | | | Also update the affected regression files. gpsd had been throwing away the DGPS status.
* Add missing double quotes. Fixed .chk to match.Gary E. Miller2016-04-061-0/+171
|
* RTCM3 packets can be bigger than RTCM2 ones.Gary E. Miller2016-04-062-0/+27
| | | | I have seen up to about 490 in RTCM3.
* Use the data from Skytraq PSTI,030 sentence.Gary E. Miller2016-04-053-15/+18
| | | | | This duplicates, but improves on the accuracy of GPVTG. Also add a bit on PSTI,001 and PSTI,032
* Improve GNGSA handling, add rx210.log which shows the problem.Gary E. Miller2016-04-053-44/+425
| | | | | GNGSA's almost always come in pairs, and never with any other flavor of xxGSA.
* Add Skytraq binary regression test.Gary E. Miller2016-03-312-0/+20
| | | | 2d and 3d modes.
* GPGST time was always 1970-01-03Txxxx. Fixed.Gary E. Miller2016-03-307-91/+83
| | | | | | | 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.
* Fix GPGSA/BDGSA processing so they combine.Gary E. Miller2016-03-302-18/+13
| | | | | | | | 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.
* Skytraq regression with GPGSA and BDGSA in same second.Gary E. Miller2016-03-292-0/+155
| | | | | Notice that the chk file shows the sats are not properly marked. Sat 214 is the only one marked used in a 3D fix!
* Fix JSON dump code to not report time in GST unless there's a valid fix.Eric S. Raymond2016-03-292-14/+14
|
* Add Skytraq regression test logs.Gary E. Miller2016-03-284-0/+595
|
* ISYNC regression test files.Eric S. Raymond2016-02-092-0/+332
|
* Move reference ais-nmea-sample file out to contribJon Schlueter2016-01-252-252901/+0
| | | | | | | Useful reference set of sentences but not as useful as part of regression data Took over 45 minutes on one architecture.
* [aivdm] Disable some mis-behaving sample entriesJon Schlueter2016-01-053-24/+19
| | | | | | | | | | | | Moved some sample entries from ais-nmea-sample.log to sample.aivdm and commented them out. these were generating warning/errors in gpsd Likely malformed but would like to stash them away to be looked into more when someone with specs or other sample data can look for similar types of data
View Lorry Controller Status