My new APM2.5 just quit working while I was doing the final setup on my plane. I was running v2.40 firmware because the newer versions would not work on the board when it arrived last week (2.70 was not out yet). But, all was well with v2.40 and I proceeded with the build.
I had 3DR telemetry & FPV w/ MinimOSD operating perfectly. Spektrum radio was calibrated and had 3 modes: MAN, STAB, RTL programmed. Aircraft surfaces responded in STAB mode correctly, then suddenly, nothing.
I disconnected everything including the GPS, and connected via USB to the MP. Connection failed at "Got param GND_ABS_PRESS" (62 of 183) in v.2.40.
I got access via Terminal and reset the EEPROM: no difference.
I can upload any firmware version to the board, but now only 2.70 will connect via Mavlink, v.2.68 stops at "RLL2SRV_D" (175 of 256), earlier versions on different lines, but all stop without connecting. Version 2.70 loads great, but I have no compass or accel.
In Terminal window, a test of:
Compass = disabled
ins = Panic: failed to boot MPU6000 5 times
Attached is the screen shots of the Terminal interface and a schematic of my flight system. I video recorded the successful functionality tests of the system (prior to failure) so that I could feature it on my website. I can post that video as well.
Everything was working perfectly before the sudden failure.
Any help appreciated. I just went from "Maiden Flight" to "Discouraged" in 5 minutes. Thanks, Al
Replies
How long are you waiting after you load the new code before trying the cli and checking the compass or the MPU6000?
Do you see the Initializing message on the MP AHRS?
It can take a couple of minutes after loading 2.7 or going back to one of the other versions for the dataflash to format. Those devices are unresponsive during that time.
You can read more about this over in the release thread.
http://diydrones.com/forum/topics/arduplane-2-69-released
Could you try loading arducopter 2.9.1. to see if it boots? There was a large change to "AP_HAL" which makes it easier to port the software to there px4 board. ArduCopter is pre-AP_HAL while Arduplane is a little further ahead and has already moved over.
If ArduCopter also doesn't work then you've likely got a hardware problem.