We've got two new APM 2.5s from diydrones, and are just getting started with Arducopter (but aren't new to Arduino or embedded systems).
After downloading 2.8.1 hexacopter to them with Mission Planner, we were able to communicate with them through CLI, and connect to them with MP, but not do much else (like radio calibration). Apparently because the APMs kept resetting themselves every 5 seconds (according to message on the console).
Upgraded both to 2.9, and now one appears to be working okay when hooked up via USB. But the other one can only communicate via CLI: trying to connect via MP times out every time.
Is there a debug tool to help isolate what's failing (like, say, a diagnostic sketch for the APM, or an app that would show me what's going on over the Mavlink link? The Windoze version of MP unhelpfully closes the command prompt window on startup, so I can't see its debugging output like on Linux)?
If they're resetting, I'm guessing that they're browning out. Are you using the Power Module to power them?
This happens when they're connected to the PC via USB and running off USB power, not actually built into the copter.
I'm certain that the one that worked was connected to the receiver, because I was getting ready to calibrate the radio. I think that the second one wasn't, because I was just trying to verify that the firmware download had worked.
I've since read that the APM may reset itself if it doesn't see PPM inputs, and that might be the cause. I'm going to try installing it in the assembled copter to see if that fixes it.
I can't get my new APM2.5 to connect to MP at all. Older one works fine. How did you get to communicate through CLI ?
Did you load the flight firmware on APM 2.5? Also, have you loaded the drivers for APM 2.5 (they different from the APM 1 drivers)
I got my new APM 2.25 to work. Even though MP could not "connect" I was able to run tests from terminal so it was communicating. Then I reflashed the quad firmware which went fine, and then restarted MP. Connected fine now. Even flys perfect.
I'm having the same issue! I'm able to connect via CLI but not trough mavlink I can also upload firmwares. When I try to connect via mavlink it keeps getting stuck on AHRS RP P. I just got the the apm 2.5 yesterday. I think I was given a bad gyro.
I'm having a similar issue. It worked fine until I ran ESC calibratoin.
Now I can't connect with mavlink. It times out, but I can use CLI and upload firmware.
John hold the reset button for 30 sec and let me know if you can then re-upload 2.9.
fixed it for me.
yeah same here, the 30 sec reset does nothing for me.