Closed
Description
RemoteID/OpenID mavlink protocol has been added to main
.
In mainline the current implementation :
-
Streams these streamed at 1Hz in modes: normal, onboard, usb, onboard low bandwidth:
- OPEN_DRONE_ID_LOCATION
- OPEN_DRONE_ID_SYSTEM
- Uses hard coded values and home position for operator - see src/modules/mavlink/streams/OPEN_DRONE_ID_SYSTEM.hpp
-
This has a stream defined but is not streamed by default:
- OPEN_DRONE_ID_BASIC_ID
- ID format is not in correct format (TODO: MAV_ODID_ID_TYPE_SERIAL_NUMBER needs to be ANSI/CTA-2063 format)
- Is this fixed before release v1.14?
- OPEN_DRONE_ID_BASIC_ID
-
There is one parameter/setting:
- COM_ARM_ODID
- Enable Drone ID system detection and health check.
- Essentially sets what PX4 does if OpenID is not found or is lost, with respect to ARMING. (disabled, warning, or required).
- Default is 0 - so system allows arming without OpenID hardware by default.
-
RemoteID hardware presence determined by existence of heartbeat message in last 3 seconds.
-
Remote ID hardware
health
is determined by heartbeat too (spec indicates should also depend onOPEN_DRONE_ID_ARM_STATUS
, which is not handled on receive). -
No incoming drone ID messages are handled.
There is also a new PR Open Drone ID Live GNSS and Arm status prototype #21647.
- Not clear if this is going into PX4 v1.14 (?)
- Adds
- Plans to stream:
- Updates to
Other docs resources:
That about right?
- What remote id hardware/firmware have we actually tested it on?
- What do we "expect" would work based on what we know.
- What's going to be going into PX4 v1.14.
- Is our implementation "compliant" with US regulation, and can I state that?
Metadata
Metadata
Assignees
Labels
No labels