Debugging bad PANDA data

1

Running 2 v4.5 boards using PANDA sentences. PCB is connected to the computer via a ethernet to USB adapter (one is USB C, one is Type A) and on both, I occasionally get huge GPS jumps - like half way around the world, then will jump back. I’m guessing something is getting corrupted in the data stream, but it surprises me that the checksum would be OK, so trying to figure out if it corrupt in the transmission or something is getting messed up at the teensy before sending. I did not have the raw logging on, but when looking in the elevation log, I see things like this: (Look at line 6)

40.5750455 -81.5226975 312 4 151.61 82.05 6.23 -1.4
40.5750577 -81.5226978 311.9 4 151.62 83.4 6.263 -2.1
40.5750715 -81.5226982 311.9 4 151.6 84.94 6.266 -2.3
40.5750837 -81.5226987 311.9 4 151.55 86.29 6.243 -2.1
40.5750962 -81.5226988 311.9 4 151.54 87.67 6.259 -2.2
40.5751017 81.5166667 16 11 13 784 630.56 88.29 6.226 -2.5
40.5751032 -81.5226993 311.9 4 151.38 88.58 6.136 -2.5
40.5751168 -81.5226988 311.9 4 151.54 89.96 6.103 -2.3
40.575129 -81.5226963 311.9 4 151.84 91.26 0.053 -4.1

Any suggestions on how to figure out what is happening? Makes the steering twitch and my acres covered jump by about 20,000 when this happens!

2

Maybe look at the calculation of heading, lot of negative times negative there.
Especially check when turning narrow right U turn .

3

It happens when driving straight. In most examples I’ve looked at, the Latitude goes whacky and jumps positive. Sometimes to 0 or 40 or 80. Can heading impact the latitude calculation?
Also, in almost every example, there seems to be extra fields included, which is weird - this takes getting extra commas inserted into the data stream I would suspect? Or are the commas inserted when outputting to the text file?