Skip to content

Add Remote ID docs to PX4 v1.14 level #2605

Closed
@hamishwillee

Description

@hamishwillee

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:

  • 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?
  • 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 on OPEN_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.

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions