Update according to the final ASTM Remote ID standard and remove WIP #1317
Conversation
message_definitions/v1.0/common.xml
Outdated
| <entry value="2" name="MAV_ODID_UA_TYPE_ROTORCRAFT"> | ||
| <description>Rotorcraft (including Multirotor).</description> | ||
| <entry value="2" name="MAV_ODID_UA_TYPE_HELICOPTER_OR_MULTIROTOR"> | ||
| <description>helicopter or Multirotor.</description> |
There was a problem hiding this comment.
Helicopter or multirotor.
|
Generally we remove the WIP when we're sure we have a workable API, and that is the point there is an implementation. Is there a PX4, ArduPilot or other flight stack implementation - and if not, is one planned? @auturgy @LorenzMeier @julianoes Any comments on this final revision of the messages - ie expectation is that the ASTM remote ID messages will not be "stable". |
|
I could probably whip up an ArduPilot implantation. |
|
@apache405 might have hardware. |
Some of the UA Type names were changed in the final version of the ASTM Remote ID standard. Signed-off-by: Soren Friis <soren.friis@intel.com>
|
Review comment fixed. About implementations, I don't know if anyone else than me/Intel have used these new Mavlink messages. I have used them for sending data from a flight controller to a Bluetooth transmitter module in a so-far unpublished Intel drone. |
Signed-off-by: Soren Friis <soren.friis@intel.com>
I did the final smaller edits needed to align the message definitions with the final ASTM Remote ID standard.
I have uploaded some documentation here:
mavlink/mavlink-devguide#220
Once that PR is approved and merged, I assume we should be able to remove the Work in Progress marks as well?