MAVLINKHUD

Commercial Certification & Self-Declarations

Executive Summary

Building a drone with ArduPilot and a Remote ID module does not automatically make it a "Standard Remote ID Drone" in the eyes of the FAA.

To sell a "Standard Remote ID Drone," you (the integrator) become the Manufacturer. You must submit a Declaration of Compliance (DOC) to the FAA, asserting that your specific hardware/software combination meets ASTM standards.

The Self-Certification Trap

It is easy to create a DOC on the FAA DroneZone. It is harder to defend it in court.

  • The Risk: If your drone is involved in an incident and investigators find your Remote ID implementation was non-compliant (e.g., could be disabled by a user switch), you are liable for falsifying federal records.
  • Retroactive Rigor: "It worked on my bench" is not a defense. You need engineering logs proving the system refuses to arm when the ID module is disconnected.

Technical Requirements for DOC

1. Tamper Resistance

The regulations state the Remote ID system cannot be disabled by the user without "special tools" or "breaking the case."

  • ArduPilot Implementation: Use DID_OPTIONS = 1 (Enforce Arming).
  • Parameter Locking: You should "hide" or "read-only" the DID_ENABLE parameter in your custom parameter set to prevent users from turning it off.

2. Serial Number Integrity

The broadcasted Serial Number must match the physical label on the drone.

  • Standard: ANSI/CTA-2063-A.
  • Provisioning: You must burn this ID into the persistent storage (DID_UAS_ID).
  • Locking: Once set, the ID should not be user-changeable. ArduPilot supports locking the ID via the LockUASIDOnFirstBasicIDRx option.

3. Error Reporting

The system must notify the pilot if Remote ID fails.

  • ArduPilot: Sends STATUSTEXT messages ("RemoteID: Failed") to the GCS. You must ensure your GCS displays these prominently (Red Banner).

The Certification Workflow

  1. Engineering Test: Validate that disconnecting the CAN cable prevents arming. Validate that GPS loss flags the Remote ID status as "Emergency" or "Undeclared" correctly.
  2. Lab Test: Use a spectrum analyzer (or a certified lab) to verify the Bluetooth/WiFi RF power output meets FCC Part 15.
  3. Documentation: Create a "Means of Compliance" (MOC) document tracking your testing.
  4. Submission: Submit the DOC to FAA DroneZone.
  5. Production: Every unit sold must have the specific Serial Number format listed in your DOC.