Strange output on uBlox LEA-6H GPS

I have a uBlox LEA-6H gps as an external GPS for an APM 2.0. I get great locks and the GPS coordinates are approximately correct, but the output is strange. I have a custom datalog routine to save all the gps data.

It starts out ok:


Timestamp (milliseconds) GPS time (hhmmss.sss * 1000 in UTC) GPS Status (0 = No Lock, 1 = Lock) Number of satellites acquired Latitude (degrees) Longitude (degrees) Altitude (meters) Altitude via GPS along (meters) Ground speed (m/s) Ground course (degrees)

GPS: 104316, 408893600, 1, 9, 43.7914470, -110.9391300, 2820.4900, 2843.4199, 7.4800, 257.4300
GPS: 104417, 408893800, 1, 9, 43.7914470, -110.9391300, 2820.1599, 2843.0601, 7.3400, 244.6900
GPS: 104517, 408893800, 1, 8, 43.7914390, -110.9391300, 2819.8999, 2843.0601, 7.3400, 244.6900
GPS: 104617, 408894000, 1, 8, 43.7914390, -110.9391300, 2819.6101, 2842.5701, 7.3400, 244.6900
GPS: 104718, 408894000, 1, 8, 43.7914390, -110.9391300, 2819.3101, 2842.5701, 7.3400, 244.6900
GPS: 104818, 408894200, 1, 8, 43.7914390, -110.9391300, 2819.1101, 2842.2100, 5.7100, 232.0800
GPS: 104919, 408894200, 1, 8, 43.7914280, -110.9391600, 2819.1101, 2842.2100, 5.7100, 232.0800
GPS: 105018, 408894400, 1, 8, 43.7914280, -110.9391600, 2819.3000, 2841.7700, 7.4700, 236.5400
GPS: 105118, 408894400, 1, 8, 43.7914160, -110.9391700, 2819.0400, 2841.7700, 7.4700, 236.5400
GPS: 105219, 408894600, 1, 8, 43.7914160, -110.9391700, 2818.8301, 2841.3501, 7.3900, 247.6500

(columns 5 and 6 are Lat and Long; column 2 is GPS time (hhmmss.sss * 1000 in UTC); column 1 is ardupilot milliseconds since startup.)

However, after a while I get both the GPS time and the longitude locking up:


GPS: 311568, 409027000, 1, 8, 43.7951700, -110.9478400, 2418.8999, 2607.6599, 5.3400, 327.8600
GPS: 311668, 409027000, 1, 8, 43.7951700, -110.9478400, 2418.3301, 2607.6599, 5.3400, 327.8600
GPS: 311768, 409027000, 1, 8, 43.7951700, -110.9478400, 2418.0300, 2607.6599, 5.3400, 327.8600
GPS: 311868, 409027000, 1, 8, 43.7951810, -110.9478400, 2417.6499, 2607.6599, 5.3400, 327.8600
GPS: 312049, 409027000, 1, 8, 43.7951810, -110.9478400, 2418.4600, 2607.6599, 5.3400, 327.8600
GPS: 312148, 409027000, 1, 8, 43.7951890, -110.9478400, 2418.8201, 2607.6599, 5.3400, 327.8600
GPS: 312249, 409027000, 1, 8, 43.7951890, -110.9478400, 2419.1399, 2607.6599, 5.3400, 327.8600
GPS: 312349, 409027000, 1, 8, 43.7952000, -110.9478500, 2420.0200, 2607.6599, 5.3400, 327.8600
GPS: 312450, 409027000, 1, 8, 43.7952000, -110.9478500, 2420.3701, 2607.6599, 5.3400, 327.8600
GPS: 312550, 409027000, 1, 8, 43.7952080, -110.9478500, 2420.8401, 2607.6599, 5.3400, 327.8600
GPS: 312650, 409027000, 1, 8, 43.7952080, -110.9478500, 2420.8401, 2607.6599, 5.3400, 327.8600
GPS: 312751, 409027000, 1, 8, 43.7952160, -110.9478700, 2420.5100, 2607.6599, 5.3400, 327.8600
GPS: 312851, 409027000, 1, 8, 43.7952160, -110.9478700, 2420.3501, 2607.6599, 5.3400, 327.8600
GPS: 312950, 409027000, 1, 8, 43.7952270, -110.9478700, 2419.9199, 2607.6599, 5.3400, 327.8600
GPS: 313052, 409027000, 1, 8, 43.7952270, -110.9478700, 2419.6799, 2607.6599, 5.3400, 327.8600
GPS: 313151, 409027000, 1, 8, 43.7952310, -110.9478800, 2419.1001, 2607.6599, 5.3400, 327.8600
GPS: 313332, 409027000, 1, 8, 43.7952310, -110.9478800, 2418.3899, 2607.6599, 5.3400, 327.8600
GPS: 313432, 409027000, 1, 8, 43.7952420, -110.9478900, 2417.8799, 2607.6599, 5.3400, 327.8600 

And then there is a weird jump (this is contiguous with the previous text in the log file). Note how the longitude has a big jump right after the GPS time suddenly starts responding. The Ardupilot milliseconds has no jump in time (goes from 313432 to 313532, which is 10hz).


GPS: 313532, 409102600, 1, 8, 43.7952420, -110.9478900, 2417.3201, 2472.6299, 5.6800, 278.6700
GPS: 313632, 409102600, 1, 8, 43.7940290, -110.9520800, 2416.9500, 2472.6299, 5.6800, 278.6700
GPS: 313733, 409102800, 1, 8, 43.7940290, -110.9520800, 2416.7100, 2472.3799, 5.0400, 277.8500
GPS: 313833, 409102800, 1, 8, 43.7940290, -110.9520900, 2416.4199, 2472.3799, 5.0400, 277.8500
GPS: 313933, 409103000, 1, 8, 43.7940290, -110.9520900, 2416.1399, 2472.2700, 5.1700, 274.8200
GPS: 314034, 409103000, 1, 8, 43.7940290, -110.9521000, 2416.0601, 2472.2700, 5.1700, 274.8200
GPS: 314134, 409103200, 1, 8, 43.7940290, -110.9521000, 2416.0400, 2472.2800, 3.8500, 269.5900
GPS: 314234, 409103200, 1, 8, 43.7940290, -110.9521200, 2416.0400, 2472.2800, 3.8500, 269.5900
GPS: 314334, 409103400, 1, 8, 43.7940290, -110.9521200, 2416.0801, 2472.2200, 3.3400, 261.7400
GPS: 314434, 409103400, 1, 8, 43.7940290, -110.9521300, 2415.9600, 2472.2200, 3.3400, 261.7400
GPS: 314534, 409103600, 1, 8, 43.7940290, -110.9521300, 2416.1001, 2472.2400, 3.7000, 251.8900
GPS: 314635, 409103600, 1, 8, 43.7940250, -110.9521400, 2416.1201, 2472.2400, 3.7000, 251.8900
GPS: 314735, 409103800, 1, 8, 43.7940250, -110.9521400, 2416.1899, 2472.1599, 3.0700, 244.8900

The GPS coordinates are approximately in the right location according to google earth, but it is not exactly in the correct location.

What could be causing these errors?

I can post the full log file and kml file if it would help.

Thanks,

Tom

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…