How to bind an ELRS radio
RADIO // FIELD_REPORT

How to bind an ELRS radio

Published
Updated
Read time4 min read

Binding ELRS is simple when the radio and receiver run the same major version (2.x with 2.x, 3.x with 3.x). It feels cursed when the versions don't match, you forget bind mode, or you assume "the LED blinked once" means linked. This page is the whoop-friendly bind workflow plus the checks that prove the sticks actually move.

FPV Grind starts beginners on ExpressLRS because that's what most BNFs and spares in India use. 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 some other "2.4G" protocol)
□ Whoop / receiver is ELRS (onboard SPI or a UART receiver)
□ Radio module and receiver on the same ELRS major version
□ Props OFF for bench tests
□ You know which switch is ARM; don't 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: usually plug in power three times in a row (on, off, on, off, on), or use the bind button. Onboard SPI receivers can also be put in bind mode from Betaflight's Receiver tab or the bind_rx CLI command. Follow your FC/receiver docs.
  3. On the radio, open the ExpressLRS Lua script → Bind.
  4. Wait for a solid receiver LED or the link indicator in the Lua script.
  5. In Betaflight's Receiver tab, move the sticks; the channel bars 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 when flashing, so gear binds automatically without the button dance. The same phrase must be on the radio module and the receiver. Changing the phrase means rebinding everything.

ApproachProsCons
Bind button / power cycleClear, works on most BNFsManual for every new receiver
Binding phraseFast for a whole fleetA mismatched phrase fails silently
Phrase checklist:
□ Identical phrase on radio and receiver
□ No trailing spaces or typos
□ After changing the phrase, re-check stick movement in Betaflight

Prove the bind worked

How to bind an ELRS radio: Prove the bind worked

Don't trust "it armed once in the living room".

CheckPass
Receiver LED / OSD linkStable link indication
Betaflight Receiver tabThrottle, yaw, pitch and roll bars move
Channel mapEach stick moves the right bar; see Mode 2
FailsafeRadio off → receiver-loss warning, motors stop as configured
Range checkShort walk around the house 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 mode, or no power
Never bindsELRS major versions don't match, or phrase mismatch
Binds then dropsPower, antennas or a damaged antenna lead
Sticks dead in BetaflightSerial RX on the wrong UART, or protocol not set to CRSF
Arms then diesFailsafe, loose antenna or brownout
"Bound" but wrong behaviourWrong model selected, or mixes on the radio
Works on the bench, drops in the roomLow output power or interference; try a lower packet rate

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 the first stick twitch
ELRS radio with a non-ELRS BNFIt will never bind; a shopping error
Skipping the Betaflight Receiver tabA "bound" LED but wrong stick mapping
Tweaking power and packet rate on day oneOvercomplicates indoor whoop flying
Never checking failsafeA lost link becomes a runaway quad

India notes

  • Prefer ELRS BNFs and radios with domestic spares; other protocols are expensive to abandon later.
  • If a listing says "compatible radio included", check that it's 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. Matching an AIO and receiver for a custom build: 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.