Closed ddworken closed 9 years ago
Just upgraded to the beta APM Planner and the problem is still present.
Sorry, this is not a support forum, but for issues that are known and need to be fixed. Please use this forum for technical support. Thanks http://ardupilot.com/forum/viewforum.php?f=82
@billbonney, how would I go about confirming that this is support issue. As a programmer with electronics experience, everything here seems to be pointing towards a bug of some sort. The problem is that the communication protocol is sending an unsupported command of some type. Wouldn't a support issue be "Why am I losing connection to the drone?" rather than "Why is the protocol sending incorrect data?"?
You need to post OS version, Which version of ArduPilot you are using. APM Planner version. My guess is that you are running master before the routing changes have been fixed.
The protocol is working, the drone is rejecting the command. If you tested with AC3.2 stable release you would see it was working and would have looked at ardupilot as the culprit.
It easier to start these discussion on ardupilot.com forum, we bring them here when we have detailed analysis of a real programming error.
APM Planner beta on Ubuntu 14.04 Arducopter 2.5
We don't work with Arducopter 2.5, only ArduCopter 3.0+ releases.
Current versions for APM Planner are
stable: 2.0.15 beta: 2.0.16-rc1 daily: 2.0.16-rc1-2-g5d393b7
You can find the version in the About box.
Whenever I try to arm, the arducopter fails to arm. This is reproducible on the newest Arducopter version (stable and beta) with APM Planner on Ubuntu 14.04 or Mission Planner on Windows 8.1. When trying to arm, APM Planner gives a Message Log of:
[MAV 001:1] Initialising APM... [MAV 001:1] Initialising APM... [MAV 001:1] Initialising APM... [MAV 001:1] Calibrating barometer [MAV 001:1] FAILURE: Unsupported CMD: 400 [MAV 001:1] Initialising APM... [MAV 001:1] Initialising APM... (continuing forever)
This occurs every time I attempt to arm the drone. This issue started today after a reboot of the drone (no hard landing and no crash).
Does anyone have any idea why this is happening?
Identical issue reports on other projects: ardupilot, missionPlanner