"No GPS" Problem
So here's the issue:
My APM2.0 always has the 3DFix light go solid within a couple minutes, but quite frequently Mission Planner will display "No GPS" (and of course hdop:0 and sats:0) when connected via 3DR radios. I can get the GPS to register by disconnecting Mission Planner, pressing the reset button on the APM2, and then reconnecting Mission Planner. The GPS will keep its 3D Fix during the AMP2 reset. Sometimes I need to do this more than once before "No GPS" will turn into "No Fix" or "3D Fix" on Mission Planner. Everything seems to work fine when connected via USB instead of radio. All other sensors/telemetry work fine. I am using Mission Planner 1.1.85 and ArduPlane 2.34, which are the current versions.
Does anyone know why Mission Planner fails to detect/read the GPS on my APM2.0?
Replies to This Discussion
-
ModeratorPermalink Reply by Dean Wynton on -
Is it just the gps? sometimes when I am connected via mavlink I have to switch out of one tab into another tab and then back to show the correct data.
You could try that and see if it makes a difference? I think it just needs refreshing sometimes..
-
Permalink Reply by Cody O. on -
Thanks for the advice, but this did not have any effect. "No GPS" is still displayed after switching tabs several times.
-
DeveloperPermalink Reply by Michael Oborne on -
make sure you have the latest firmware. re the reset bug
-
Permalink Reply by Cody O. on
-
I did a search for "reset bug" and found the following threads:
Is it still necessary to press the reset button when using the Medi...
These seem to match my symptoms exactly, but I am running the current firmware (ArduPlane 2.34).
Is there still a start sequence bug in the current version that requires pressing the reset button?
Note: Yesterday the AMP2.0(ArduPlane 2.34) worked perfectly. It seems this is an intermittent problem.
-
Permalink Reply by John Cousins on -
Having this issue right now! Driving me nuts!
-
Permalink Reply by George Jeffrey on -
Same problem.
Using AC1 since 2010 without problem, including interface with Configurator and subsequently, Mission Planner.
New APM2.0 delivered this week. I had to solder in the pins. and mount the shield. All sensors are performing normally, with the exception of the GPS.
GPS locks OK with strady blue LED showing 3D fix. ABC LED's function OK at startup, but fail to show steady blue following GPS lock, and Mission Planner does not find any GPS.
I have tried resets, disconnect/reconnect and have tried both the current AC and AP firmware.
So, no GPS, but all othger sensors OK.
Any comment gratefully received!
-
Permalink Reply by James on -
You can try my solution : http://code.google.com/p/ardupilot-mega/issues/detail?id=624&can=6
-
Permalink Reply by John Cousins on
-
Problem solved! At least for me. Dodgy batch of Windows FTDI drivers passed through in a windows automatic update. Manually run Windows update and new FTDI drivers are available. Installed, rebooted and GPS is back. Dodgy drivers were severly limiting data throughput and GPS info was not valid!
-
Permalink Reply by John Cousins on
-
Nope sorry.. problem is back again...
Was working fine just 2 days ago.
Just for interests sake, when I swap back to Ublox everything works fine.
Plug in Mediatek..... solid blue light but no GPS on planner.
-
Permalink Reply by Barry Nash on -
Same problem here,
3DFix light solid blue but "C" led fails to light. It does flash on startup. This is a problem that has just started.
I am reading the rest of the blogs but have not found a solid answer as of yet.
Cheers,
Barry
-
Permalink Reply by John Cousins on
-
Mine ended up being the GPS module.The module would not accept the commands from the ardupilot. The GPS module has a line called RX (receive) which recieves commands from ardupilot (when it is booting up) to change into a special binary protocol. You can use this same RX line to configure other parameters within the GPS module. Problem is, in my case the whole RX side of the module was fried. The module was still getting power and was obtaining a fix... but it was locked in a mode which was spitting out data down the TX (transmit) line that the ardupilot couln't understand... As there was no way to send commands to the GPS module, it was useless. New mediatek fitted, and all is well. Big tip... don't get your GPS wet.... even just a couple of drops will kill it! I spent hours trying to work this out, but it wasn't until I started trying to communicate directly to the GPS via an FTDI cable that it all started to become clear. When I was using terminal software, I could see NMEA style data coming from the module, but when I tried to send it commands i.e. change baud... it didn't see a thing. Couldn't update firmware.... wouldn't accept any info into it whatsoever. I even tested the tracks in the adapter board all the way up to the module itself.
-
Permalink Reply by Jonathan M on -
Did you have an original APM2 with GPS soldered directly to the APM? I think I may have this same issue. I am curious to see if i can get another GPS module and use an extention cable to the other input. I get Sat data, but 9999 hdop and no fix no matter how long I wait. It used to work, though. Maybe it got wet at one point?
Social Networking
Top Content
Contests
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.A list of all T3 contests is here.
Groups
-
ArduRover User Group
183 members
-
ArduCopter User Group
1278 members
-
Andropilot Users Group
182 members
-
Moderators
24 members
-
Documentation Editors
51 members
Advertisement
© 2013 Created by Chris Anderson.
Powered by
