How to bind a whoop to a radio
RADIO // FIELD_REPORT

How to bind a whoop to a radio

Published
Updated
Read time4 min read

Binding connects your radio to the whoop's receiver so your stick inputs reach the flight controller. On almost every modern tiny whoop, that link is ExpressLRS (ELRS). Without a bind, the quad is a paperweight with LEDs.

FPV Grind's day-one goal: bind once, check the sticks, then hover. Don't skip the Receiver tab check. "It beeps, so it must be bound" has wasted more Saturday mornings than tired packs.

Before you touch bind mode

How to bind a whoop to a radio: Before you touch bind mode

CheckWhy
Radio and whoop both ELRSDifferent protocols never bind: what is ExpressLRS
Correct EdgeTX model selectedBinding on the wrong model causes confusion later
Internal RF set to CRSF (or the external module enabled)Wrong RF setting = silence
Battery or USB power on the whoopThe receiver must be powered
Props off or quad held downAn accidental arm after binding is ugly indoors

Fresh radio? Minimum EdgeTX path: how to set up EdgeTX for FPV. Full ELRS deep dive: how to bind an ELRS radio.

Bind workflow (typical BNF whoop)

LED colours and button presses vary by board. When your BNF's manual disagrees with these generic steps, follow the manual.

1. Power the radio, select the whoop's model
2. Open Tools → ExpressLRS Lua script
3. Put the receiver into bind mode:
   □ Bind button on the AIO / receiver, or
   □ Power-cycle sequence per the manual, or
   □ Binding phrase, if you already use that workflow
4. In the Lua script, choose Bind
5. Wait for confirmation (Lua status / receiver LED goes solid)
6. Reboot the radio or receiver if the manual says so
7. Check in Betaflight Configurator → Receiver tab:
   □ Throttle, yaw, pitch and roll move the correct bars
   □ Arm switch moves the expected AUX channel

With a binding phrase, the radio module and receiver need the same phrase and the same ELRS major version. Flashing random firmware files without reading the release notes is a classic way to break this.

Stick verification (do not skip)

TestPass looks like
Throttle stick upThrottle channel rises
Yaw left / rightYaw bar moves the right way (not reversed)
Pitch / rollMatching bars in Betaflight
Arm switchAUX flips; the quad arms only when you intend

If anything fails here, fix the channel map, stick mode or mixes before the first hover. Mode primer: what is Mode 2. Arm hygiene: how to arm.

Common bind failures

How to bind a whoop to a radio: Common bind failures

SymptomLikely causeDirection
Never enters bindReceiver not powered; wrong buttonCheck the battery plug or USB; reread the manual
Binds, but sticks don't moveReceiver settings wrong in BetaflightOnboard SPI receiver: "SPI Rx" with ExpressLRS. Separate receiver: Serial RX on the right UART, provider CRSF
Intermittent controlPacket rate, antenna or powerELRS checklist
Works on the bench, drops at rangeAntenna damaged or folded under the canopyInspect the antenna; start indoors
Bound to the wrong radioSomeone else binding nearbyBind away from other pilots

Mismatched ELRS major versions (an old 2.x radio module with a 3.x receiver) also cause mysterious failures. Update deliberately, with the release notes, not five random firmwares in one night.

Whoop-specific tips

  • Many 1S AIOs hide the bind button under the canopy. Remove it carefully; don't pry on the camera.
  • After a crash damages the receiver antenna, the link may still work on the desk and fail across the room. Antenna health matters.
  • If you own several whoops, give each its own named EdgeTX model; shared models cause "why did my arm switch move?" confusion.

Practice without burning packs

Binding is a radio skill; hovering is a stick skill. After bind:

  1. Confirm sticks on the bench
  2. Warm up on /sim with the same Mode 2 habits
  3. First packs: short indoor hovers, props clear of people; see the spectator guide

Bottom line

Confirm ELRS on both ends, put the receiver in bind mode, bind from the Lua script, then prove every axis in Betaflight's Receiver tab. Most "whoop won't bind" problems are power, the wrong model, receiver settings or versions, not cursed hardware. Once the bind is solid, arm-switch habits and hover drills matter more than tinkering.

Bench

ELRS BNFs and radios: the Bench. Stick practice: /sim. Build compatibility checks: 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.