Controller won't bind

Overview

DJI RC / Smart Controller pairing fails.

DJI OcuSync/Lightbridge, ExpressLRS, Crossfire, analogue 5.8 GHz VTX, Walksnail/HDZero.

Symptoms

Typical "Controller won't bind" signs in flight, app or OSD:

• Linking failed
• RC not found
• Timeout during bind
• Log RSSI/LQ during flight — where link drops.

Common causes

Before replacing parts, rule out software, mechanical and environmental causes:

• Firmware mismatch aircraft/RC
• Low battery either device
• Previous bind cache

Tools needed

Prepare before diagnostics — saves time in the field:

• Two data-capable USB cables
• ELRS/Betaflight Configurator
• Antenna and u.FL/MMCX checker

Step-by-step fix

Work safely: battery off when working on ESC/motors; props removed; after repair — VLOS test flight.

• Update aircraft and RC firmware.
• Full battery both sides.
• DJI: link aircraft to account, then pair RC.

Additional diagnostics

Log RSSI/LQ during flight — where link drops.

Ground failsafe test before each session.

Channel scan — verify clean channel away from Wi-Fi.

When to contact service

If any of the following apply — do not fly and contact authorised service:

• RX/VTX antenna physically damaged after crash.
• Link fails even at 5 m — hardware replacement.
• DJI RC screen won't boot — service.

Prevention

Prevention reduces failure risk and supports EASA Open / VLOS compliance:

• Firmware sync before field day

Frequently asked questions

Is it safe to fly with "Controller won't bind"?

No if the fault affects navigation, power, ESC or link. Fix on the ground first, then conduct a VLOS test flight in open area.

How long does diagnosis take?

Most “Controller won't bind” cases — 15–45 min on the ground. Complex ones (firmware, hardware) may need 1–2 h and service.

Must I register repair with the NAA?

No mandatory repair registration, but a maintenance log is recommended for commercial operations.