APM 2.5 partially unresponsive

My apm has never been flown or dropped, etc. it's brand new. I started setting it up and then after my update to 2.69 all still worked but after a few power cycles and trip loading of 2.69 I get a compass init failure (as others have mentioned and the fix is to change one of the parameters (I don't have it in front of me) to anything but 0. The problem is more than just this, I can read the parameters from the apm, use the cli but I can not write any parameters at all. Everything fails. It doesn't matter what. On top of that when I hit reset on the apm, the mpu resets 5 times (as expected) then goes into panic. This never happened before. I can se the Cli to view my radio pulses per channel but when I open the config and look at it graphically there is no movement (using ppm but checked without it). Also, I have gone back to 2.68 and that didn't fix anything and when back on 2.69 there is often garbled text now. No shorts, drops, etc. it's brand new. I can't even download the logs... I even loaded arducopter on it to completely erase the EEPROM (also dod it from the cli in arduplane) and thenput ardulane back on but no go. Any ideas? I know there is mavlink bug in 2.69 but can seem to do much with it now. Also, it's a genuine one from 3dr, etc...Oh and on a side note I was able to mix 6 flight modes to a 3 switch on a JR 10x which I know there is a list of how tos floating around if anyone's curious.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hi, this unability to write to EEPROM and the many resets may indicate bad supply voltage. Try to check that. Try from a different USB port or a different computer.. and of course for flight, ensure that your BEC had enough and clean enough voltage.

    Regards

    Soren

  • Tomas,
    I was using 1.2.33 and tried 1.2.35. Originally tried updating the 1.2.33 to .35 and it failed. Used another computer later on that was using .35 but have tried both. Neither works.
    Thanks
  • Developer

    Hi Ryan,

    If it fails to startup with both 2.68 and 2.70 then it sounds like a hardware fault. I assume it also doesn't work with ArduCopter?

    Cheers, Tridge

  • Admin

    @Ryan,

    What version of the MP are you using and did you recently update the MP?

    Regards,

    TCIII

This reply was deleted.

Activity