3DR uBlox GPS location always ~50m south

I have purchased two 3DR uBlox GPS's, one standalone and one with a compass, and both are offering the exact same coordinates as each-other, every boot. The problem is they don't match all other GPS's and maps (Google Maps, Open Street Map, etc). The location they always output is just about 50 miles south of my actual position no matter where I am. They function perfectly normal in every other regard.

I'm trying to use these GPS modules without the APM mission planner software, just as serial GPS's for arduino. I've looked through all the settings in the uBlox datasheet and reconfigured the GPS's myself, they each respond when polled by saying they are using WGS84 (like my maps), and all other settings are normal. I can't find any reference to anything else that would shift the GPS points in the configuration files. 

I'm wondering if this is a known problem, and if it is being compensated for in the APM software. I've searched through the APM firmware but cannot find a compensation shift anywhere. The mission planner maybe? 

Is this a known problem? if it is, what is causing it? what is the exact fix?

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

Join diydrones

Email me when people reply –

Replies

  • facing same problem  problem here. I have to set way point by using ch7 as a switch then and then i can make my predefined flight. In gcs, i can not set the way-point by taking reference of google map as it is shifted.

    if anybody can solve this problem then plz reply.

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
20 hours ago
DIY Robocars via Twitter
20 hours ago
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…