Andrew Tridgell, Josh Henderson, David Buzz, Jeff Wurzbach, Roel Schiphorst
As of September 2022 standard, RemoteID is a requirement in the USA
Required on all new commercial vehicles soldAble to meet FAA requirements via ASTM means of complianceYou will need to buy the MOCBasic components:A compliant transmitter moduleSupport in flight controller firmwareSupport in GCS software for operator locationCertification process with FAA and FCCArduPilot solution is based on OpenDroneID
RemoteID Hardware
Several Options available for hardware
Connection options
MAVLink over UARTDroneCAN on CAN bus
ESP32 Firmware
An ArduPilot RemoteID firmware for ESP32-S3/C3 is available here:https://github.com/ArduPilot/ArduRemoteIDPre-compiled binaries are in the releases folderSupports both MAVLink on UART and DroneCAN on CAN portPinouts are in the README on the github siteTested on ESP32-S3, will test on ESP32-C3 soonOperationThe transmitter module listens for 5 messages on MAVLink or DroneCANBasicIdSelfIDOperatorIDSystemLocationThe transmitter module sends one message for arming ok/not-okThe DroneCAN messages are identical in form to the MAVLink OpenDroneID messages
Ardupilot Firmware
The ArduPilot firmware support is merged in masterSupport is also in 4.2.3beta2 for plane and will be in copter beta shortly Could be backported to earlier firmware if requiredParametersKey parameters in ArduPilot are:DID_ENABLE : must be set to 1 to enable OpenDroneIDDID_CANDRIVER : which CAN driver to use (1 or 2), or 0 to disable CANDID_MAVPORT : serial port to use for MAVLink support, or -1 to disableDID_OPTIONS : needs to be set to 1 to enforce arming checksDID_BARO_ACC : airframe specific barometer accuracyOther key parameters also need to be locked down, for example:GPS_TYPE, GPS_TYPE2, AHRS_EKF_TYPE, SERIALn_PROTOCOL (this list will grow as we test)Lockdown mechanism is via defaults.parm and @READONLY tagSee CubeOrange-ODID and Pixhawk6X-ODID examples
Board IDs and Parameter Lock
To be compliant with ASTM means of compliance we need parameter lockdown
Each vendor creates a new build target (hwdef.dat directory)Use board ID that is vendor specific, default is 10000 + base board IDExamples for CubeOrange-ODID and Pixhawk6X-ODID are providedNeeds custom hwdef.dat option to enable OpenDroneIDNeeds custom defaults.parm to mark key parameters @READONLY
Ground Station Support
The ground station needs to provide key data to the flight controller
Key data includes:UAS IDOperator ID and descriptionOperating area limitsSome classification IDsThis data is provided via MAVLink using OPEN_DRONE_ID messagesSample implementation is in MAVProxy OpenDroneID moduleA MissionPlanner plugin should be coming soonCurrent beta already supports required DroneCAN and MAVLink messagesWe will also need QGroundControl support
Mission Planner Support
GCS Operator interface pending
DroneCAN and MAVLink support already done
Vehicle Serial Number
Vehicles needs to have an assigned serial number
Certification and testing will be a significant challenge
Both FCC and FAA certification neededFCC Transmitter Certification (47 CFR 15.247 and/or 15.249) & EMC testing (47 CFR 15.109)Co-located transmitters will be a challenge for most manufacturersHas long lead time due to lab scheduling (expect 10 weeks+)DoC (declaration of compliance) for FAAASTM F3586−22 is an MOC accepted (with comments) by the FAA Federal Register publication pending, expected this weekOutlines process options for demonstration of compliance
For discussion of all RemoteID/OpenDroneID topics please use:
The (partner only) partner_regulatory channel on discordThe public opendroneid channel on discordThe partners mailing list
Post navigation