We have seen problems with the modules itself before. If the problem is in the module then you should ask for a replacement from Seeed or the distributor from where you brought the GPS.
Hey rschmidt, sorry to hop in here; I was just looking over the . Before we send you off to test the GPS unit, are you sure you’re not entering in GPS data directly into Google maps to get the 40 mile error?
GPS puts out an NMEA string, and the data comes out in the format DDMM.MM where D is degrees, and M is minutes.
But before we dig deeper on the problem, I just wanted to check that we’re not pumping GPRMC string data directly into google maps. Is that the case? Can you share your GPRMC string with us (I understand not wanting to because of privacy issues).
I put the the straight decimal numbers into this site: http://www.latlong.net/convert-address-to-lat-long.html, dividing by 100 first so it should be in DD.MMMMSS format. I pretty sure I’m doing this right. Do you still see a problem?
You can use the third calculator (where you input DDD MM.MMMM) to calculate the DD number from the string that the sensor reports, and that should report the correct number for Google maps.
This is really great. Thank you for updating the code, and thanks for working through this. This is really fantastic and I think I’ll try to write a blog post about it.
rshmidt, what are you planning to do? Can you share with us?
I’m implementing a lot of your python code in Elixir. So i’m going through your examples and seeing if I can make it work in Elixir. I’ve implemented the basic examples with no problem in Elixir. Next step is to write my control code to make the robot autonomous using all the sensors as input. I actually probably won’t use the GPS much right now as most of what I’ll be doing will be inside.
Also, you’re basically going to need to calculate azimuth between two sets of coordinates, turn to that angle, and run until your distance is 0 between your current coordinates, and the coordinates you’re aiming for.
With that in mind, if you have a compass and a GPS, the two numbers you need to know are azimuth to destination and distance to destination. And you can calculate those, in python, from two sets of GPS coordinates, using this fancy article here:
I think!
Hey, so can you tell us more about your project and what you’re working on?
I got everything up and running and my GPS.PY keeps outputting “unable to read” every second or two. The cables are switched properly. (A picture of the crossed over cable under the instruction would probably help people or even a 20 second youtube of someone crossing over the cable with a small screwdriver.) Does anyone have any experience with that unable to read message? Any clues on what to do? My build is the one that I downloaded about 10 days ago.
I am not sure but suspect that you have the wrong code (see my entry from May 23, 2015 at 8:28 pm). There I switched to GrovePI (but you need the board) and came back when rschmidt and karan had corrected the code for the GoPiGo.
Don’t spend much time but this is a possible reason. Just read through the whole thread to see similarities.
Or the GPS is broken (less realistic).
Normally it works even inside a building (not for the first steps to exclude this error cause).
I can confirm that updated GPS.PY file is outputting GPS data that looks fairly accurate. I can see 8 satellites inside of my two story stucco house in San Diego CA. Does anyone have a program that helps the gopigo navigate to waypoints? I assume you need a compass to orient the gopigo before you send it towards the next point?
I think that there are a couple of people working on the waypoint navigation but we have heard from anyone who got it to work. It would require a compass to navigate and there is some discussion on this thread too. Do let us know if you get it to work with your GoPiGo.