How to bind an ELRS radio
RADIO // FIELD_REPORT

How to bind an ELRS radio

Published
Read time4 min read

ELRS bind is simple when radio and receiver speak the same version family. It feels cursed when you mix packet rates, forget bind mode, or assume “LED blinked once” means linked. This page is the whoop-friendly bind workflow and the checks that prove sticks actually move.

FPV Grind defaults beginners to ExpressLRS because spares and BNFs in India line up around it. Protocol basics: what is ExpressLRS. Whoop RX context: ELRS receiver for whoops in India.

Before you bind

How to bind an ELRS radio: Before you bind

□ Radio is ELRS (not a random “2.4G” orphan protocol)
□ Whoop / RX is ELRS (SPI onboard or UART RX)
□ Firmware families are compatible enough to talk
□ Props OFF for bench tests
□ You know which switch is arm - do not bump it

EdgeTX setup help: how to set up EdgeTX for FPV. Updates: how to update ExpressLRS.

Fast path (most BNFs)

  1. Power the whoop / receiver.
  2. Put the receiver into bind mode (button, three-power-cycle, or Lua - follow your FC/RX docs).
  3. On the radio, open the ELRS Lua script → Bind.
  4. Wait for a solid link LED / “Bound” confirmation.
  5. In Betaflight Receiver tab, move sticks - channels must move.

Whoop first-flight config: Betaflight whoop checklist. Binding a whole whoop kit path: how to bind whoop to radio.

Binding phrase (when you use one)

Many pilots set a binding phrase so gear auto-binds without the button dance. Set the same phrase on radio and receiver. Change phrase = treat as a new bind.

ApproachProsCons
Classic bind button / power cycleClear, works on most BNFsManual every new RX
Binding phraseFast fleet bindingPhrase mismatch = silent fail
Phrase checklist:
□ Identical phrase on TX and RX
□ No trailing spaces / typos
□ After changing phrase, re-verify stick movement in BF

Prove the bind worked

How to bind an ELRS radio: Prove the bind worked

Do not trust “it armed once in the living room.”

CheckPass
RX LED / OSD linkStable link indication
Betaflight Receiver tabThrottle/yaw/pitch/roll channels move
Channel mapMode 2 matches what you expect - Mode 2
FailsafeThrottle drops / disarms as configured
Range sanityShort walk-test indoors before freestyle

Link budget and setup depth: ELRS link budget checklist. UART vs SPI: receiver UART vs SPI.

If bind fails

SymptomCheck
No LED changeReceiver not in bind, wrong UART, or no power
Binds then dropsPacket rate / power / antennas
Sticks dead in BFWrong serial RX UART or protocol not CRSF
Arms then diesFailsafe, loose antenna, or brownout
“Bound” but wrong modelWrong model slot / mixes on radio
Works on bench, fails in roomPacket rate too ambitious / wifi interference

Urban RF context: 2.4 GHz vs 900 MHz in urban India. Failsafe thinking: failsafe scenarios.

Common beginner mistakes

MistakeWhy it hurts
Binding with props onSurprise spin on first stick twitch
Mixing ELRS TX with non-ELRS BNFWill never bind - shopping error
Skipping BF Receiver tab“Bound” LED without stick mapping
Max power / wrong packet rate day oneOvercomplicates whoop indoor flying
Never setting failsafeLost link becomes a flying knife

India notes

  • Prefer ELRS BNFs and radios with domestic spares - orphan protocols are expensive to abandon later.
  • If a listing says “compatible radio included,” still verify it is ELRS before you learn on it.
  • Practice stick feel on /sim while you wait for a radio to ship.

Bench

ELRS radios and whoop BNFs: the Bench. Custom AIO + RX pairing: Grind Lab.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.