Help wanted! Here is the latest firmware revision that fixes the longitude issue. If you are one of those that are having problems please try this new version:


Let me know your results.

Instructions for reloading your firmware are here.

Views: 4546

3D Robotics
Comment by Chris Anderson on September 2, 2010 at 8:14pm
The latest ArduPilot MediaTek library now support this firmware release. Although this firmware puts your module into NMEA mode, the library will automatically switch it into more efficient binary for the session.

As always, use subversion to ensure you're using the latest libraries before compiling the code.
Comment by Steve Oliver on September 2, 2010 at 9:28pm
Is it possible to use a sketch on the APM to pass through whatever serial commands are needed to update the firmware?

3D Robotics
Comment by Chris Anderson on September 2, 2010 at 9:31pm
Steve: Yes, I think that would work. Try the sketch in the manual here.
Comment by Steve Oliver on September 2, 2010 at 9:32pm
Thanks Chris!
Comment by Alex McEwan on September 3, 2010 at 1:18pm
Will all the units from the store from now on have the updated firmware?
Comment by Fabien Bruning on September 3, 2010 at 2:22pm
Thanks, I got the right coordinates this afternoon.

Sorry can't test anything else, my UAV flew away :(
Comment by Ken on September 3, 2010 at 4:56pm
Oooh goody!
I think I will have time to do an upload tomorrow. (Saturday)

Comment by Jordi Muñoz on September 3, 2010 at 5:24pm
Hello Alex,

After now yes. But anyway I still don't know if the firmware works fine...
Comment by Earl on September 3, 2010 at 5:31pm
Looks like it fixed my bad MTK.
Comment by Serge on September 4, 2010 at 12:37am
Oh Yes!!! Thanks so much!
It did indeed fix it, It now puts me right where I need to be at lat:51 lon:005

One issue that i'm having is that it sometimes will keep led C blinking indicating that messages are being received, but that they are not correct. The MTK then indicates a fix (blue led), but the APM does not get any coordinates. Strange thing is that this occurs lets say 2 out of 3 times after startup. I can't figure out yet what determines success or failure. I'll keep you posted if I figure it out.

thanks again!


You need to be a member of DIY Drones to add comments!

Join DIY Drones


Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service