search

ArduPilot / ardupilot

ArduPlane, ArduCopter, ArduRover, ArduSub source
http://ardupilot.org/
GNU General Public License v3.0
10.81k stars 17.26k forks source link

Copter: send error codes to GCS via MAVLink #1707

Open rmackay9 opened 9 years ago

rmackay9 commented 9 years ago

Basically we need a message format agreed. By the way, we already have a bunch of error codes defined at the bottom of ArduCopter/define.h.

I think the format of the message could be: byte 0: error list (0=common, 1=px4stack, 2=ardupilot stack, etc) byte 1: subsystem (we would define an enum for this, error list specific or shared?) byte 2: error code (list specific?) byte 3: 0 = cleared, 1 = occurred (so if an error ever resolves itself we can tell the GCS)

The above format would need to be put into one of the mavlink xml files and we'd also need a big enum (or something) for each error list.

Related to this pull request. https://github.com/diydrones/ardupilot/pull/1335

R-Lefebvre commented 9 years ago

Is this still going to happen for AC3.3?

rmackay9 commented 9 years ago

No, it won't make it. Moved to AC3.4.

rmackay9 commented 8 years ago

Bumping to AC-3.5.

mentonin commented 12 months ago

This issue has no activity for 5 years, but is still open. Is there still an interest in converting the message system to be ID based? As I understand it, this would make it easier to translate and maintain messages, and could also make the compiled binary smaller.