Hi all i just got my telemetry working and for some reason now my MP is showing my plane in Africa,,i have tried going back to the USB and disconnecting the xbee,s but still will not report the correct location .i have GPS lock and it was showing the correct location . i,m at a loss my MP updated again this mourning could this be the problem what else can i check? i have the APM1.4 and the mediatek and am using the 2.4 xbee pro,s and also have the mag hooked up . any suggestions ?
"i have GPS lock"... what LED or output specifically are you using to determine that?
I would go into the CLI (terminal), test menu, and run the GPS test. It may be reporting Lat 0.00, Long 0.00 which is just west of the African coast. This could be due to the GPS being improperly detected, disabled or connected to the I2C port (the one marked NOGPS). If tht were the case, the blue LED on the GPS itself would indicate a lock (solid blue) because it is powered, but the data isn't being given to the APM.
Thanks. The team is investigating.
There may be something wrong with GPS autodetection using mission planner version 1.1.38 also. See this comment: http://diydrones.com/forum/topics/arducopter-2-4-released?commentId...
can you revert MP to an older version?
Sure. They're all here. Just say no when it asks you to update.
well it works on ver 1.1.37 MP at least on the USB
and works with xbee too ,i noticed a bunch of info is missing from the status on this version
Does it show the right position when you're connected via USB and have lock?
It's all working for me fine on USB.
no it s the same on usb but it was working ! gps showing right in cli terminal but wrong in the status on MP and showing wrong location but MP has updated twice since the APM ! has been connected(was wrestling with my xbee,s) been messed up since i got them working and i haven't changed MP i,m back on usb till i get this figured out to try not to add any more confusion, complications .
thanks guys will be waiting before the next update !
I am reproducing this same error with my APM2 after updating to MP 1.1.39. I guess that's the bleeding edge!