Retrofit or manufacture with Dronetag DRI for Remote ID broadcast compliance
domain: help.dronetag.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Select the correct integration path: factory manufacturer integration (Standard Remote ID) vs. retrofit integration (add-on broadcast module) documented separately for US and EU rules
For retrofit integration, wire the module to receive required MAVLink messages from the flight controller (heartbeat, GPS raw, altitude, scaled pressure, system time, global position)
Configure the module and set the Operator ID using the Dronetag Toolbox App or the flight controller's own configuration tool
For manufacturer integration, implement the MAVLink OpenDroneID message set end-to-end to meet 14 CFR Part 89 Standard Remote ID requirements
Use the module's forwarding port (MAVLink 2 only) or REST/WebSocket endpoints if building a custom dashboard on top of the broadcast data
Known gotchas
Retrofit modules depend entirely on the host flight controller providing the specific MAVLink message set on time — an autopilot missing one of the required messages breaks compliance even with correct module wiring
US and EU compliance paths (ASTM F3411/FAA Part 89 vs EN 4709-002) have different documentation and requirements — following the wrong region's guide produces a non-compliant setup
The forwarding port explicitly requires MAVLink 2; MAVLink 1-only flight stacks are not supported for this integration path
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?