A Remote ID module only works when three things are done in order: mount and power it correctly, register its serial number in FAA DroneZone, and verify the broadcast before takeoff. Skip any one of them and the drone is not compliant. This guide walks through all three, then gives you a pre-flight checklist to run every time you fly.
If you have not bought a module yet, start with How to Choose a Broadcast Remote ID Module.
Step 1: Check the FAA DOC list before you mount anything
Do this before you mount the module. A module that is not on the FAA Declaration of Compliance list does not meet the rule, no matter how well it works as a radio. No firmware update and no DroneZone entry can fix an unlisted module.
Have the module serial handy: it is on the sticker on the module case, in the companion app, or on the box. Source: Spektrum SkyID manual; FAA Remote ID page.
Open the FAA UAS Declaration of Compliance list at uasdoc.faa.gov. Search by the maker name, filter by Remote ID, and match the exact model name and FCC ID. A close name is not a match. Check the serial range in the entry too: some entries cover only part of a production run. Source: FAA Remote ID page; post 17349.
The list returned a live 200 response on 2026-11-21 and loads as a searchable web app. If the search returns nothing for your model, treat the module as unlisted. If the seller cannot name the DOC entry, do not buy it. Source: live fetch 2026-11-21; post 17349.
Warning: this guide makes no per-module DOC claim. The choosing guide 17349 makes none, and neither does this draft. Only a live lookup on uasdoc.faa.gov on the day you buy tells you whether a module counts.
The Holybro module needs a special note. It is a Standard Remote ID solution for manufacturers and integrators, not a plug-and-play retrofit, and it needs its own Declaration of Compliance submission in the USA. The choosing guide 17349 and the QRC DroneZone guide both record that it has no verified DOC entry as an end-user broadcast module. Do not enter its serial in DroneZone unless a DOC entry covers your build. Source: post 17349; QRC DroneZone guide.
Step 2: Mount a standalone module on the aircraft
A standalone module carries its own battery and GPS, turns on with a button, and needs no wiring into the aircraft. Mounting is the whole physical job. Get the position wrong and the module may not get a GPS fix or may not be heard by receivers.
Charge it first. Charge the module fully over USB before the first use. The Holyton manual states a full charge takes about 40 minutes and gives up to 5 hours of operation. Source: Holyton manual; Ruko R111 manual.
Pick the spot. Mount the module on the flat upper surface of the drone, clear of the propeller arc, clear of carbon fiber and metal above the case, and clear of other electronics. Carbon fiber blocks radio signal, so a module buried under a carbon top plate may broadcast weakly or not at all. Source: Holy Stone manual; Spektrum SkyID manual; post 17349.
Fix it twice. Attach the module with the supplied hook and loop pads, then add a zip tie through a frame arm or landing gear as a backup. Adhesive pads fail in heat and after hard landings. Check by hand that the module cannot shift, slide, or rotate into a propeller. Source: Holy Stone manual; Ruko R111 manual; post 17349.
Do not block the drone GPS, then weigh the aircraft. Keep the module clear of the drone own GPS antenna: the Ruko manual warns that a module placed over the drone GPS can block it. If your drone takes longer than usual to get a GPS lock after fitting the module, move the module first. Then weigh the whole aircraft, module included: a 249 gram drone plus a 19 gram module is over 250 grams, which triggers registration. Source: Ruko R111 manual; post 17349.
Step 3: Bind the module to your drone in the app
Most standalone modules need the drone details stored in the module before the first flight. This is called binding: the module broadcasts the serial number and position, and the binding ties that broadcast to your aircraft model and weight in the companion app.
Power on and enter setting mode. The sequence is the same shape across the common manuals, but the exact buttons differ by model, so follow your manual. On the Holyton module, hold the power switch for 3 seconds to turn it on, then hold the settings switch for 3 seconds to enter the setting steps. On the Ruko R111, press the power switch for 3 seconds, then press the settings button for 3 seconds. Then open the maker companion app, tap the device serial number to connect, enter the aircraft model and weight, and save. Source: Holyton manual; Ruko R111 manual.
Restart the module so the binding sticks. This is the step most people skip. On the Holyton module, hold the power switch again to restart: the binding succeeds only after the module is restarted. On the Ruko R111, restart the device until the indicator on the right side blinks rapidly. If you change the binding later, repeat the whole sequence, including the restart. Source: Holyton manual; Ruko R111 manual.
Wait for a GPS fix outdoors, then read the status light. A broadcast module can only send broadcast data when it has a GPS signal, and it needs a clear view of the sky. The Ruko manual states GPS search time is 90 to 120 seconds outdoors. Check GPS outdoors, not indoors: no position indoors is usually fine, while no position outdoors after two minutes is a real problem. Per the Spektrum SkyID manual, a slow flash means it is still acquiring GPS, a solid light means ready, and a rapid flash means an error, so do not fly. Source: Ruko R111 manual; Spektrum SkyID manual.
Step 4: Wire the Holybro module to a flight controller
This step is only for the Holybro Remote ID module on a PX4 or ArduPilot build. It does not apply to a standalone module, which needs no wiring. The Holybro module has no GPS of its own and takes power and position data from the flight controller, so it only fits builds with a flight controller that can feed it. If your aircraft has no flight controller, you need a module with its own GPS instead. Source: post 17349.
The Holybro module runs ArduRemoteID firmware on an ESP32-C3 radio, broadcasts over WiFi and Bluetooth, and connects to the flight controller over CAN or serial. It weighs 27.5 grams with case and antenna and takes 5V from the flight controller. It is a Standard Remote ID solution for manufacturers and integrators, not a plug-and-play retrofit. Source: Holybro Remote ID user manual v1.1; post 17349; QRC listing for ID 13414.
Connect it over serial or CAN. Over serial, connect the module to the flight controller through the Remote ID serial port with the 6-pin GH wire, using the MAVLink or TELEM interface. Over CAN, connect it through the Remote ID CAN port using the DroneCAN interface. Pick the port your flight controller has free, wire it per the manual, and do not share the port with another device. The Matek F405-WING V2 flight controller in the parts block below is an ArduPilot fixed-wing controller that provides the feed a module like this needs. Source: Holybro Remote ID user manual v1.1.
Set the ArduPilot parameters. In Mission Planner, with ArduPilot version 4.x or newer, set DID_ENABLE to 1, DID_OPTIONS to 1, and DID_MAVPORT to the serial port the module is wired to. For the CAN path, follow the manual CAN section for the port setup. Check the module status in your ground station after setting the parameters: ArduPilot shows Remote ID status in Mission Planner and QGroundControl. Do not fly until the ground station shows the module communicating with the autopilot. Source: Holybro Remote ID user manual v1.1; post 17349.
Update the firmware over WiFi if needed. The module acts as a WiFi access point by default. Connect to the RID network with the default password from the manual, open http://192.168.4.1, and upload the ArduRemoteID firmware file for the ESP32-C3 from the releases page on GitHub. A failed update reverts to the factory firmware. Source: Holybro Remote ID user manual v1.1.
Step 5: Register the module serial in DroneZone
Registration is the paperwork half of compliance; the module is the hardware half. A module that is fitted but not registered does not complete compliance. The full walkthrough is in the QRC guide How to Register a Drone and Remote ID in DroneZone. The condensed steps below follow the FAA Remote ID page directly. Create a DroneZone account before the flight day, not at the field.
Know which registration you hold. Recreational flyers register the pilot once, and one registration number covers every drone in the inventory for 3 years. Part 107 pilots register each drone separately, each with its own registration number, at $5 per drone for 3 years. Recreational registration costs $5 and lasts three years. You need your address, email, phone number, the drone make and model, the Remote ID serial number, and a payment card. Source: FAA Remote ID page; FAA register drone page.
Enter the serial in your device inventory. Log in to FAA DroneZone and open the Drone Owners and Pilots Dashboard. Click Manage Device Inventory, then Add Device. Answer Yes to the Remote ID question. Choose the device type: Remote ID broadcast module, or Standard Remote ID drone. Enter the Remote ID serial number from the module, then click Add Device. The serial is on the module case or in the companion app, and it is not the same as the drone serial number. Source: FAA Remote ID page; Spektrum SkyID manual.
Recreational pilots: one module can move between drones. If you use one broadcast module on several drones that lack built-in Standard Remote ID, select broadcast module for each drone and enter the same module serial number on each drone record, with each drone make and model listed. Part 107 pilots do not get this: each device must be registered separately, each with its own registration number. For a drone already registered under Part 107, edit its record the same way and save. Source: FAA Remote ID page.
Mark the drone and carry the certificate. Write the registration number on the outside of the drone before you fly. Print or save the registration certificate and carry it when you fly. Open the drone record in DroneZone after you save it and check that the Remote ID answer reads yes with the serial shown. Source: FAA Remote ID page; QRC DroneZone guide.
Step 6: Verify the broadcast before takeoff
A record in DroneZone and a module on the aircraft are not proof the broadcast works. Verify it with a receiver before every first flight with a new module, and any time the module has been rewired, updated, or moved to another drone. The full verification guide is How to Check Your Remote ID Is Broadcasting.
Open a Remote ID scanner app, turn on Bluetooth and WiFi, and power on the module outdoors with a GPS fix. Your module serial should appear in the app with the right position. Stand within a few meters for the first check: Bluetooth and WiFi broadcasts reach hundreds of meters, not miles. Source: post 17349; post 17351.
For the Holybro module, check the ground station too: open the OpenDroneID OSM app on Android, and check the Remote ID status in Mission Planner or QGroundControl. Finally, confirm the serial in the scanner app matches the serial in your DroneZone inventory. A mismatch usually means the wrong serial was entered. Fix the DroneZone record before you fly. Source: Holybro Remote ID user manual v1.1; post 17349.
The pre-flight checklist
Run this list before every flight with a Remote ID module. It takes two minutes on the ground and catches the failures that ground a flight or break compliance in the air.
- Module serial checked on the FAA DOC list, exact model name and serial range confirmed.
- Module serial entered in DroneZone, Remote ID answer reads yes, serial shown on the record.
- Registration number marked on the outside of the drone.
- Registration certificate and TRUST certificate (recreational) carried or saved on your phone.
- Standalone module battery charged; add-on module powered from the aircraft.
- Module mounted on top, clear of carbon fiber, metal, and the propeller arc, with a zip tie backup.
- Drone weighed with the module fitted; registration status correct for that weight.
- Module powered on, status light showing ready, not an error flash.
- GPS fix acquired outdoors; module position showing in the app or ground station.
- Broadcast verified in a scanner app; serial shown matches the DroneZone record.
- Flight stays within visual line of sight the whole flight.
- If the broadcast stops in flight, land as soon as practicable, then find the fault before the next flight.
Checklist sources: FAA Remote ID page; post 17349; Holyton, Ruko, and Spektrum manuals; QRC DroneZone guide.
What mistakes cause the most failed setups?
- Checking the DOC list after the first flight. Check it before you pay. A module that is not listed cannot be fixed with a firmware update or a registration entry. Source: post 17349.
- Entering the drone serial instead of the module serial. The module serial is on the module case or in the companion app. A DroneZone record with the wrong serial does not match the broadcast. Source: post 17349.
- Skipping the restart after binding. The binding succeeds only after the module is restarted. Save the drone details in the app, then power the module off and back on. Source: Holyton manual; Ruko R111 manual.
- Mounting under carbon fiber or metal. Carbon fiber blocks radio signal. A module under a carbon top plate may not be heard by receivers, even though its light looks fine. Source: post 17349.
- Trusting adhesive alone. Hook and loop pads fail in heat and after hard landings. Add a zip tie backup every time. Source: post 17349.
- Forgetting the weight. A module can push a sub-250 gram drone over 250 grams at takeoff, which triggers registration. Weigh the aircraft with the module fitted. Source: post 17349.
Troubleshooting: the module does not work as expected
The module does not show up in a scanner app. Check that it is powered on and charged. Move the phone closer: Bluetooth and WiFi broadcasts reach hundreds of meters, not miles. Try a second scanner app. Check the mount: a module under carbon fiber or metal may not be heard. Source: post 17349.
No GPS fix. Give the module a clear view of the sky and wait at least two minutes outdoors. A slow flashing status light on the SkyID means it is still acquiring GPS, so do not fly until the light goes solid. Source: Spektrum SkyID manual; Ruko R111 manual; post 17349.
The broadcast drops mid-flight. Land as soon as practicable. Check the battery charge on a standalone module, and check the power connection on an add-on module. Check that vibration has not loosened the mount or the wiring. Source: post 17349.
The Holybro module shows no Remote ID status. The Holybro module needs a flight controller feed over CAN or serial, and the port must be set for Remote ID traffic in the firmware. Check the wiring, check DID_MAVPORT and the other DID parameters in Mission Planner, and check the module status in your ground station. Check that the flight controller has a GPS lock, since the module has none of its own. Source: Holybro Remote ID user manual v1.1; post 17349.
Which setup path fits your drone?
| Your aircraft | Setup path | What to watch |
|---|---|---|
| Older consumer drone, recreational flying | Standalone module, Steps 1, 2, 3, 5, 6 | Charge, top mount, app binding, restart after binding |
| Homebuilt FPV drone | Light add-on module with its own DOC listing, Steps 1, 5, 6, plus the maker wiring steps | Weight, free power port, firmware path for your stack |
| Fixed-wing or long-range PX4 or ArduPilot build | Holybro module, Steps 1, 4, 5, 6 | Flight controller feed, DID parameters, DOC submission for the build |
| Part 107 commercial flying | One module per drone, Steps 1 through 6 per aircraft | Each drone registered separately, each with its own serial entry |
For the module choice behind each path, read the choosing guide: How to Choose a Broadcast Remote ID Module.
Parts used in this guide
Prices and stock were verified live on qualityrcparts.com on 2026-11-21. All three items below are in stock and purchasable.
- Holybro Remote ID Module With Case – WiFi / Bluetooth, CAN / Serial, PX4 / ArduPilot (ID 13414) – $49.99. The only Remote ID module Quality RC Parts stocks. It broadcasts over WiFi and Bluetooth and runs ArduRemoteID firmware. It needs a flight controller feed, so it fits PX4 and ArduPilot builds. It is a Standard Remote ID solution for manufacturers and integrators, not a plug-and-play retrofit, and it needs its own Declaration of Compliance submission in the USA.
- MAVLink2 WiFi Telemetry Module for Pixhawk/APM (ID 10242) – from $42.99. A supporting part, not a Remote ID module. It gives a MAVLink2 WiFi link for Pixhawk and APM flight controllers, useful on the same PX4 and ArduPilot builds that use the Holybro module.
- Matek F405-WING V2 Flight Controller with OSD and SD Slot for ArduPilot / INAV (ID 12989) – $138.99. A supporting part, not a Remote ID module. It runs ArduPilot with OSD and an SD slot for fixed-wing builds, and it provides the flight controller feed a module like the Holybro unit needs.
Shipped fast and securely from our secure facility in Queensbury, NY. QRC ships within the USA only.
Related guides
- How to Choose a Broadcast Remote ID Module
- How to Register a Drone and Remote ID in DroneZone
- How to Check Your Remote ID Is Broadcasting
- How to Choose a Holybro Remote ID Module for PX4 Builds
- How to Add Remote ID to a Home-Built FPV Drone
FAQ
Do I need a Remote ID module for my drone? You need one if your drone weighs 250 grams or more at takeoff, or is flown under Part 107 at any weight, and it has no built-in Standard Remote ID, and you do not plan to fly only inside a FAA-Recognized Identification Area. Check the FAA list for your drone first: many drones built since late 2022 already have Remote ID built in. Source: FAA Remote ID page; post 17349.
How do I check if a module is legal before I buy it? Search the FAA UAS Declaration of Compliance list at uasdoc.faa.gov for the exact model name and FCC ID, and check the serial range in the entry. Only a module on the accepted list meets the rule. A close name is not a match. Source: FAA Remote ID page; post 17349.
Where do I enter the Remote ID serial number? Log in to FAA DroneZone, open Manage Device Inventory, click Add Device, answer Yes, choose Remote ID broadcast module, enter the module serial number, and click Add Device. Source: FAA Remote ID page.
Can one broadcast module cover more than one drone? For recreational flyers, yes. List the same module serial number on each drone record in the same inventory, and fly only one drone at a time with it. Part 107 pilots must register each drone separately. Source: FAA Remote ID page.
Why does my module not show up in a scanner app? Check power and charge first, then move the phone closer, then try a second app. A module under carbon fiber or metal may not be heard, and a module with no GPS fix outdoors will not broadcast position. Source: post 17349.
Does the Holybro module work as a plug-and-play retrofit? No. It has no GPS of its own, takes power and position data from the flight controller over CAN or serial, runs ArduRemoteID firmware, and fits PX4 and ArduPilot builds. It is a Standard Remote ID solution for manufacturers and integrators and needs its own Declaration of Compliance submission in the USA. Source: post 17349; Holybro Remote ID user manual v1.1.
Sources
- FAA, Remote Identification of Drones: https://www.faa.gov/uas/getting_started/remote_id
- FAA, How to Register Your Drone: https://www.faa.gov/uas/getting_started/register_drone
- FAA, UAS Declaration of Compliance list: https://uasdoc.faa.gov/
- FAA DroneZone: https://faadronezone.faa.gov/
- Quality RC Parts, How to Choose a Broadcast Remote ID Module (post 17349): https://qualityrcparts.com/choose-broadcast-remote-id-module/
- Quality RC Parts, How to Register a Drone and Remote ID in DroneZone: https://qualityrcparts.com/register-drone-remote-id-in-dronezone/
- Quality RC Parts, How to Check Your Remote ID Is Broadcasting (post 17351): https://qualityrcparts.com/check-remote-id-broadcast-before-flight/
- Quality RC Parts, How to Choose a Holybro Remote ID Module for PX4 Builds (post 17346): https://qualityrcparts.com/choose-holybro-remote-id-module/
- Quality RC Parts, How to Add Remote ID to a Home-Built FPV Drone (post 13435): https://qualityrcparts.com/best-way-to-add-remote-id-to-homebuilt-drone/
- Quality RC Parts store listings, checked live 2026-11-21 (IDs 13414, 10242, 12989)
- Holyton FAA Compliant Remote Identification Broadcast Module User Manual: https://manuals.plus/asin/B0CKMJVQB4.pdf
- Ruko R111 Remote ID Module User Manual: https://manuals.plus/m/e7ba92f4a9aa8f13f7c076512672a39a96c55d863139861d59321865030ca3d0.pdf
- Holy Stone FAA Compliant Remote Identification Broadcast Module User Manual: https://manuals.plus/asin/B0CGTTNJXL.pdf
- Spektrum SkyID Remote ID Module Instruction Manual: https://manuals.plus/spektrum/207858-2-skyid-remote-id-module-manual
- Holybro Remote ID user manual v1.1 (ArduRemoteID, ESP32-C3): https://www.fccpdf.com/2AP22/2AP22-REMOTEID/6691523.pdf
- The DroneU, FAA Remote ID Rules for Drones (2026): https://www.thedroneu.com/blog/remote-id/
Last updated: 2026-11-21
