# How to Bind an FPV Receiver: ELRS, Crossfire, and FrSky Methods Explained
Getting your receiver to talk to your radio is the first real test of any FPV build. A mismatched bind procedure can leave you staring at a lifeless quad, convinced something is fried when it’s actually a simple protocol mismatch. This guide walks you through binding the three most popular receiver protocols in 2026: ExpressLRS (ELRS), TBS Crossfire, and FrSky ACCST/ACCESS.
## Why Won’t My Receiver Bind?
Before diving into protocol-specific steps, check these universal prerequisites:
| Symptom | Likely Cause | Fix |
|———|————-|—–|
| No LED on receiver | No power / wrong voltage | Check 5V pad connection with multimeter |
| Solid LED, no response | Wrong UART or protocol in Betaflight | Verify Ports tab and Receiver settings |
| LED flashes rapidly | Receiver in bind mode, waiting for radio | Proceed with binding steps below |
| Bound but no stick movement | Channel map mismatch | Set TAER1234 or AETR1234 in Radio tab |
## ExpressLRS (ELRS) — The Enthusiast’s Choice
ExpressLRS has dominated the FPV scene with its open-source firmware, kilometer-range penetration, and sub-10ms latency. Binding ELRS requires a different mindset from traditional receivers — there is no physical bind button in normal operation.
### Method 1: Bind Phrase (Recommended)
This is the cleanest approach and eliminates the need for repeated binding:
1. **On your radio**: Navigate to the ELRS LUA script → scroll to `[Bind Phrase]` → enter a unique phrase (at least 6 alphanumeric characters, case-sensitive).
2. **On your receiver**: Connect to the ELRS Configurator via WiFi or USB passthrough → enter the **exact same** bind phrase → save.
3. Power cycle both devices. The receiver should connect within seconds.
**Pro tip**: Your bind phrase acts as a unique encryption key. Never share it, and write it down — losing it means manually re-flashing every receiver.
### Method 2: Traditional Binding (No Bind Phrase)
If you haven’t set a bind phrase:
1. Power on the receiver 3 times rapidly (plug/unplug battery 3x within 2 seconds). The LED should double-blink, indicating bind mode.
2. On your radio, launch the ELRS LUA script → select `[Bind]`.
3. The receiver LED should turn solid, confirming a successful bind.
### Common ELRS Binding Pitfalls
| Problem | Solution |
|———|———-|
| “Model Mismatch” in LUA | The receiver was previously bound to a different model. Use bind phrase or power-cycle bind method. |
| WiFi mode stuck | Press the boot button once (do not hold) to exit WiFi mode. |
| Firmware version mismatch | All ELRS devices must share the same major version (e.g., 3.x). Update via Configurator. |
## TBS Crossfire — The Long-Range Veteran
Crossfire remains the gold standard for professional long-range pilots who demand absolute reliability. The binding process is button-driven and refreshingly straightforward.
### Standard Binding Procedure
1. **Enter bind mode on the receiver**: Press and hold the small button on the Crossfire receiver while powering it on. Release when the LED flashes green rapidly.
2. **Trigger bind on the transmitter**: On your Tango 2 or external Crossfire module, navigate to `Crossfire Configuration` → `General` → `Bind`.
3. Wait 2-3 seconds. The receiver LED turns solid green, and the transmitter LUA script shows connected telemetry data.
### Crossfire Nano RX Specifics
The popular Crossfire Nano RX has a tiny button that requires precision. Use a plastic tweezer or toothpick — metal tools can short adjacent pads. If the button is inaccessible after mounting, you can also trigger bind mode via the TBS Agent Lite app over Bluetooth (Tango 2 only).
### Emergency Firmware Recovery
If a Crossfire receiver becomes unresponsive:
1. Power it with the button held for 10 seconds — this forces it into emergency recovery mode.
2. Connect to TBS Agent X via USB and re-flash firmware.
3. The green LED will blink rapidly during flashing, then go solid once complete.
## FrSky ACCST / ACCESS — The Budget Workhorse
FrSky receivers remain popular in budget builds and whoops, but their binding process varies significantly between ACCST (D16) and ACCESS protocols.
### ACCST (D16) Binding
1. **Receiver**: Hold the F/S (Failsafe) button while powering on. The red LED flashes steadily.
2. **Radio**: Go to `Model Setup` → `Internal RF` → set Mode to `ACCST D16` → select `[Bind]`.
3. The receiver LED turns solid green. Exit bind mode on the radio and power-cycle the receiver.
### ACCESS Binding (Registration-First)
ACCESS requires a two-step registration-then-binding process:
1. **Registration**: On the radio, go to `Model Setup` → `Internal RF` → Mode: `ACCESS` → `[Register]`. While the radio beeps, power on the receiver with the F/S button held.
2. **Binding**: After registration succeeds, select `[Bind]` on the radio. The receiver LED indicates success.
3. ACCESS receivers are registered to your radio’s unique ID and can be re-bound to any model without re-registration.
| Protocol | Latency | Max Range (LoS) | Price (RX) | Best For |
|———-|———|—————–|————|———-|
| ELRS 2.4G | 4-8ms | 5-15km | $13-25 | Racing, freestyle, value |
| ELRS 900M | 8-12ms | 20-40km | $18-30 | Extreme long range |
| Crossfire | 6-10ms | 15-30km | $30-45 | Professional long range |
| FrSky ACCST | 12-18ms | 1-3km | $10-20 | Budget builds, whoops |
| FrSky ACCESS | 10-15ms | 1-4km | $15-25 | FrSky ecosystem users |
## Setting Up in Betaflight After Binding
Once bound, you must configure Betaflight to recognize the receiver:
1. **Ports tab**: Find the UART your receiver is wired to (usually TX pad on FC → RX pad on receiver). Enable `Serial Rx` for that UART.
2. **Receiver tab**: Set Receiver Mode to `Serial-based receiver`. Set Serial Receiver Provider:
– ELRS: `CRSF` (not SBUS!)
– Crossfire: `CRSF`
– FrSky wired via SBUS: `SBUS`
– FrSky via FPort: `FPORT`
3. Verify stick movements in the Receiver tab. If channels are wrong, adjust Channel Map (commonly `TAER1234`).
## What to Do When Nothing Works
If you’ve followed every step and the receiver still won’t bind:
1. **Check firmware**: Mismatched firmware versions between TX module and RX are the #1 cause of binding failures. Update both to the latest release.
2. **Check wiring**: RX pin on the receiver goes to TX pin on the flight controller, and vice versa. A swapped UART wire is the #2 silent failure mode.
3. **Try a different power source**: Some USB ports and BECs provide noisy 5V that prevents binding. Power the receiver directly from a stable 5V bench supply to rule out power issues.
4. **Factory reset**: ELRS and Crossfire both support factory reset via their respective configurator tools.
—
**Need a reliable receiver for your next build?** UAVMODEL stocks ExpressLRS, Crossfire, and FrSky receivers with fast global shipping. [Browse receivers at uavmodel.com](https://uavmodel.com)