APM 2.5 not talking

Hello:

I have an odd problem with my APM 2.5 maybe someone could help me with.Actually I have two APM's and one works properly.

The second initially worked hooked up to my computer but has since crapped out.

When connected via USB and using Mission Planner,I upload the proper firmware,quad copter,.The firmware upload is confirmed and now it tries to connect Mavlink.It does connect then fetches parameters but stops at either "param RC4_REV"  or gets to "param RC5_TRIM" then just sits there til I cancel out.

It then says to disconnect for 10 seconds then retry but I get the same results.One try got me to "FS_THR_VALVE".If I continue on with more tries during connecting,Mavlink will time out after 30 seconds nd quit.It then says "only 1 heatbeat received"

As I explained,the unit did work properly once upon a time til I wanted to re tune the radio.It has not been physically damaged in any way.

Any input is appreciated.

Thanks

Paul B

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

Join diydrones

Email me when people reply –

Replies

  • I have the same problem with one of my APMs.  Did you ever get a fix?

    • No solution to mine. I had it replaced.

  • ThanksI tried your suggestions but with no luck.I am able to upload firmware etc but not connect with Mavlink.

    It says " connected" but then just freezes while it loads parameters.Stopping on RC5_TRIM.

    It stays stuck until I click on cancel.The amber lights on the APM flash while sending/receiving data but freezing during getting parameters. The unit used to work ok but just decided to quit.

    I have another identical APM that uses the same USB cable and does not require the battery to be connected.

    • Having same problem. Did you ever solve this?

  • Developer

    It's likely failing part way through the startup maybe because the barometer or dataflash isn't working.  The parameter download freezing is just because it's alive for about that long into the startup process.  There are some people suggesting we should allow the board to boot and then display the issue (like we do for most other sensors) but we haven't done that yet.

    The board is likely outputting the reason why it's failing but you can't see it through the mission planner.  You could try connecting with an Arduino IDE's Serial Monitor if you're feeling up for that.

  • One thing to try is connecting up the battery/BEC so the APM is not relying on USB power.  Other possibilities are the USB cable (try another cable) and the USB connector on the APM, which is often not properly soldered when it was built (try slight push laterally on the cable).  I always attach a small USB extension cable to my APM USB port and cinch it to the frame as I have already broken off one connector that was badly soldered.

This reply was deleted.