How to bind an ELRS receiver: binding phrase, bind mode, Betaflight
For your radio to control the quad, the transmitter module and the receiver have to be bound. ExpressLRS (ELRS) gives you two ways: a shared binding phrase or bind mode on the receiver. Here are both with every variant, what the LED tells you, how to set up the receiver in Betaflight and what to do when it doesn’t work. Checked against ExpressLRS 4.1.0 and Betaflight 2026.6.2, backed by the ExpressLRS docs and the source code of both projects.
In 5 steps
- Compare versions: the first number of the version has to match on transmitter module and receiver, so 4.x with 4.x. Otherwise, according to the docs, none of the methods works.
- Same regulatory domain: both need the same firmware options, including the same frequency range (regulatory domain), or they won’t bind.
- Bind: either set the same binding phrase on both, and they connect on their own at power-up. Or put the receiver into bind mode (power it on and off three times quickly, press its button for 1.5 seconds or use Betaflight) and select “Bind” in the ExpressLRS Lua script on the radio.
- Check: the receiver LED is solid, and the Lua script shows a “C” for connected in the top right corner.
- Betaflight: in the Ports tab, switch on “Serial Rx” for the receiver’s UART; in the Receiver tab, pick CRSF and check that the bars follow your sticks.
If something doesn’t work, look up the symptom in the list of faults.
Check first: version and regulatory domain
The current version is ExpressLRS 4.1.0 from July 17, 2026 (release). The 3.x line still got bug fixes after 4.0, most recently 3.6.4 from June 8, 2026. For binding, the first number is what counts. The docs: “The first number in the Version string should match between a TX Module and a Receiver.” And: “If your firmware versions are incompatible, NONE of the methods below will work.” The 4.0.0 release notes put it plainly: version 4 is not compatible with 3.x, 2.x or 1.x and “will not connect at all”. 4.1.0 works with any 4.x.
- Read the version: near the bottom of the ExpressLRS Lua script there is a version line, for the transmitter module and, once it is connected, for the receiver (Lua docs). If the receiver isn’t connected yet, its web UI shows the version in the “Information” tab (how to open it).
- Regulatory domain: it sets the frequency range and is mandatory when you flash. Firmware Options: “It is important that these options match to both the TX module and receiver in order for them to bind.” The EU domains EU_868 and EU_CE_2400 use listen before talk (LBT). On 900 MHz you can change the domain in the web UI, on 2.4 GHz you can’t: according to the web UI docs, the EU version with LBT is “a Compile-time option”. What is permitted in Germany is in Legal radio: video and control link.
- After updating to 4.0: the release notes say the update erases the settings from the web UI’s Options tab, “regulatory domain overrides” included. So check both devices afterwards.
Method 1: binding phrase
ExpressLRS turns the binding phrase into an ID, the UID. Devices with the same phrase connect on their own at power-up, there is no separate bind step (Firmware Options). That also means: “Any transmitter using the same binding phrase will connect to any receiver with the same binding phrase, so be unique.” The docs recommend “a unique phrase with at least 8 alpha-numeric characters”, from the Latin alphabet; “The best candidate is your Pilot Handle.” It doesn’t have to be secret: “The binding phrase is not for security, it is for anti-collision.”
You can set it in four ways:
- When flashing: the ExpressLRS Configurator and the Web Flasher have a field for the binding phrase. Flash the same phrase to transmitter module and receiver.
- In the web UI (ExpressLRS 3.0 and newer): tab “Binding”, no flashing needed (how to).
- From the radio (ExpressLRS 4.1 and newer): with the “ExpressLRS Bind” tool from the new Lua package. It sets the phrase on the transmitter module or the receiver, also takes a UID of 4 to 6 numbers instead of a phrase and keeps a history of phrases you have used (ExpressLRS blog, Nov 8, 2026). “Setting the binding phrase from the radio requires ExpressLRS 4.1 or newer on the device you are changing.”
- Built-in receiver (SPI): in the Betaflight App, see below.
The Lua package is a ZIP at ExpressLRS/Lua, version 1.1.0 on Nov 12, 2026. It needs EdgeTX 2.12.1 or newer and ExpressLRS 3.5.4 or newer; older radios and modules get a legacy package. The blog: delete the old scripts elrs.lua, elrsV2.lua, elrsV3.lua and their .luac counterparts from SCRIPTS/TOOLS, then extract the ZIP onto the root of the SD card. The Tools menu then lists “ExpressLRS” and “ExpressLRS Bind”.
Open the receiver’s web UI
- Switch the radio off, power the receiver. If it gets no connection for about 60 seconds, it switches to WiFi on its own and the LED blinks rapidly. If it is already connected, the Lua script is quicker: “WiFi Connectivity”, then “Enable Rx WiFi”. If it has a button: hold it for 5 seconds.
- Join the WiFi network “ExpressLRS RX”, password “expresslrs”.
- Open
http://10.0.0.1/in the browser. Some routers use the same address; the docs suggest a phone in that case. If you entered your home WiFi when flashing, the receiver joins that network instead and the address ishttp://elrs_rx.local. - Enter the phrase in the “Binding” tab and save. The “Information” tab shows version, regulatory domain and UID.
Source: web UI docs. The button timings are in the source code (devButton.cpp): 1.5 seconds bind mode, 5 seconds WiFi.
Method 2: bind mode on the receiver, then “Bind” on the radio
The traditional way: the receiver waits in bind mode and the radio sends its ID at the press of a button. Since ExpressLRS 3.4.0, “Any Receiver flashed with 3.4.0 or newer can be put into Bind Mode, even with a set Binding UID” (docs). Receivers up to 3.3.x with a phrase don’t enter it.
Put the receiver into bind mode
- Power it on and off three times: radio off. Power the receiver, the LED lights up, “Turn it off within 2 seconds”, three times in total. The docs: “This step is best done using a LiPo flight pack, so make sure you’ve wired your flight controller properly and checked for any shorts.” In the source code, a bound receiver counts every start. If it runs 2 seconds without a connection, it resets the counter; on the third short start it enters bind mode (
rx_main.cpp). - Button on the receiver: press it for 1.5 seconds. Without a button, briefly short the boot pad to ground (docs).
- From Betaflight: click “Bind Receiver” in the Receiver tab or type
bind_rxin the CLI. According to the ExpressLRS docs this needs Betaflight 4.5.0 or newer, details below. - From the radio: if the receiver is connected, “Enter Bind Mode” in its settings in the Lua script (in the “Other Devices” folder, according to the docs) puts it into bind mode, for example to bind it to another radio (Lua docs).
- Never bound: a receiver without a bind and without a phrase starts in bind mode on its own, according to the source code (
rx_main.cpp).
Bind
- The LED blinks twice, then pauses: the receiver is in bind mode.
- Switch on the radio, start the “ExpressLRS” script under Tools in the system menu (SYS key; on older radios long-press the menu key) and select “Bind”. A popup shows briefly.
- If the LED turns solid, the receiver is bound. The Lua script shows a “C” in the top right corner instead of a dash.
The order, per the docs: “RX first, TX second.” With the same binding phrase on both devices, pressing “Bind” “is not needed”, the docs say. The bind stays until you bind again. To leave bind mode, restart the receiver; it then keeps using the old bind (docs).
Whether the bind stays is set by “Bind Storage” in the receiver’s settings in the Lua script. “Persistent” keeps it, “Volatile” forgets it at every restart and the receiver then starts in bind mode. “Returnable” is for loaning models and needs a binding phrase (Lua docs). The 4.1.0 source code also has “Administered”: then none of the ways above puts the receiver into bind mode, and binding only happens through the web UI (RXParameters.cpp, rx_main.cpp).
What the receiver LED tells you
This is the table from the ExpressLRS docs for receivers with a single-color LED. We checked the blink timings against the 4.1.0 source code (devLED.cpp).
| LED | Meaning |
|---|---|
| Solid on | Connected to the transmitter, or the receiver is in bootloader mode (fault) |
| Double blink, then pause | Bind mode |
| Slow blink, 0.5 s on, 0.5 s off | Waiting for the transmitter |
| Triple blink, then pause | Connected, but Model Match doesn’t fit (fault) |
| Blink with a long pause | Radio chip not detected. The docs say “100ms on/off”, the source code has 0.2 s on, 1 s off. |
| Very fast flicker | WiFi mode (fault) |
Receivers with an RGB LED show, according to the docs: a rainbow at startup, a green heartbeat in WiFi mode, a slow blink while waiting for the transmitter, an orange double blink in bind mode, an orange triple blink on a Model Match mismatch, red flashing without a radio chip and one solid color when connected; the color then stands for the packet rate. No light at all means off or in bootloader mode.
Betaflight setup: UART, CRSF, channels
This part is about receivers wired to a UART of the flight controller. For built-in receivers, see SPI.
Wiring
The docs: receiver TX to flight controller RX, receiver RX to TX, both on the same UART (same number), plus 5 V and ground. “Manufacturer-suggested Receiver UARTs, or UARTs alloted for Receivers usually have a pull-down resistor to aid with SBUS (RX pad inversion) which will result into SOLID LEDs on the ESP-based ExpressLRS Receivers.” Better avoid those UARTs.
Ports and Receiver tab
- Ports tab: switch on “Serial Rx” for the receiver’s UART. RX1/TX1 is UART1 and so on. Don’t also switch on “Configuration/MSP” on the same UART; the App refuses to save that (Setup Guide). “Save and Reboot”.
- Receiver tab: set “Receiver Mode” to “Serial (via UART)” and “Serial Receiver Provider” to “CRSF”. “UART-based ExpressLRS Receivers use the CRSF Serial Protocol to communicate with a Flight Controller” (ELRS docs).
- Switch on “Telemetry output”. The Betaflight docs: it is “Also required for VTX control from ELRS receivers”.
- Set “RSSI Channel” to “Disabled” and switch “Analog RSSI input” off. Both are for old receivers; the Betaflight docs: “Do not enable this option with a modern receiver”.
- Save.
The CLI shows whether it’s all right. “The CRSF Protocol requires a full UART pair, uninverted and in full-duplex mode” (docs). The command lists every setting whose name contains “serialrx” (cli.c):
# Target quad: <your quad’s name> get serialrx
You want serialrx_provider = CRSF, serialrx_inverted = OFF and serialrx_halfduplex = OFF. If not, set them like this; save stores and reboots the flight controller. Back up first: Betaflight backup with diff all.
# Target quad: <your quad’s name> set serialrx_provider = CRSF set serialrx_inverted = OFF set serialrx_halfduplex = OFF save
Check the channels
With the radio on, move the sticks in the Receiver tab. The bars “Roll [A]”, “Pitch [E]”, “Yaw [R]” and “Throttle [T]” have to follow the right stick. If the wrong one moves, change the “Channel Map” (Receiver Tab). Betaflight’s default is AETR1234 (pg/rx.c); the App offers the presets “FrSky / Futaba / Hitec (AETR1234)” and “Spektrum / Graupner / JR (TAER1234)” (ReceiverTab.vue). In the CLI the command is map.
The ExpressLRS docs want the arm switch on AUX1, which is channel 5: “~1000 is disarmed, ~2000 is armed” (Switch Config). “AUX1 is the low-latency switch, sent with every packet”, and ExpressLRS uses it to know whether the model is armed (docs). That applies to “Arm using CH5”, the default in EdgeTX 2.11 and newer. The App’s help text in the Receiver tab: “Adjust the channel endpoint or range values in the transmitter to ~1000 to ~2000, and set the midpoint to 1500.”
If no signal arrives, the Receiver tab shows a “Failsafe active” box and the quad won’t arm: arming flag RXLOSS. What’s behind it is in Quad won’t arm: all arming flags.
Switch off the radio’s ADC filter
“OpenTx and EdgeTx both enable an ADC filter by default. Betaflight users should turn this off” (Betaflight docs). With it on, stick movements arrive in steps of about 1% of the stick travel. The checkbox is in the Hardware tab of the radio’s global settings. The ExpressLRS docs name the filter as the cause when the RC trace in a blackbox log shows steps. How to record a log is in Blackbox logging: setup and downloading your log.
Bind mode from Betaflight
Betaflight 2026.6.2 can put the receiver into bind mode itself. The command bind_rx (“initiate binding for RX SPI, SRXL2 or CRSF”, cli.c) sends a bind command to a CRSF receiver over the UART (crsf.c). ExpressLRS 4.1.0 answers by entering bind mode (RXEndpoint.cpp). The “Bind Receiver” button in the Receiver tab does the same; the App then logs “Bind request sent to the flight controller.” (ReceiverTab.vue).
# Target quad: <your quad’s name> bind_rx
The App only shows the button when the flight controller reports that it can bind: with a serial receiver on CRSF or SRXL2, and with built-in SPI receivers (rx_bind.c, msp.c). Otherwise bind_rx answers “Not supported.”. So set CRSF and save first. The receiver needs power while you do this. Then select “Bind” in the Lua script as above.
Built-in receiver (SPI), e.g. on a whoop
Some flight controllers carry the ELRS receiver on the board, connected over SPI instead of a UART. ExpressLRS then runs as part of Betaflight and is updated with Betaflight: “You cannot use the ExpressLRS Configurator to update these FCs” (SPI docs). You don’t need a UART. In the Receiver tab, set “Receiver Mode” to “SPI Rx (e.g. built-in Rx)” and “SPI Bus Receiver Provider” to “EXPRESSLRS” (Setup Guide).
- Version: the 2026.6 release notes: “ELRS V3 is the default protocol when flashing new firmware, and is not compatible with ELRS V4 transmitters. V4 is enabled by setting ELRSV4 in the build flags in the firmware flasher, which would then be incompatible with ELRS V3 transmitters” (release notes 2026.6,
expresslrs_common.h). You type the option into “Custom Defines” in the Firmware Flasher, in expert mode (Build Options). The docs warn: “Manual build options are not tested on all boards.” Back up first: Betaflight backup with diff all. - Binding phrase: the Receiver tab then has a “Binding phrase” field. The App turns it into the UID and shows it next to the label; the field only appears with ExpressLRS over SPI (
ReceiverTab.vue). In the CLI the setting isexpresslrs_uid. - Bind mode: “Bind Receiver”,
bind_rx, the bind button on the flight controller orset expresslrs_uid = 0followed bysave. Then “Bind” in the Lua script; the LED on the flight controller turns solid (SPI docs). - Packet rate: according to the ExpressLRS docs, SPI receivers don’t bind in D250, D500 and the Full Res modes. F500 and F1000 work from Betaflight 4.5.1.
Faults: symptom, cause, fix
Sorted by where it gets stuck. Backed by the ExpressLRS troubleshooting page, the binding docs and the source code of ExpressLRS 4.1.0 and Betaflight 2026.6.2.
Transmitter and receiver won’t connect
The LED keeps blinking slowly, even after “Bind” on the radio
- Cause
- The transmitter module and the receiver run different major versions, say 4.x and 3.x. The docs: “The first number in the Version string should match between a TX Module and a Receiver.” Version 4 “will not connect at all” to 3.x (release notes 4.0.0).
- Fix
- Read both versions in the Lua script or the web UI and flash both devices to the same major version. The docs recommend the latest version; on Nov 12, 2026 that is 4.1.0.
Same binding phrase, still no connection
- Cause
- The options of transmitter and receiver don’t match, above all the regulatory domain. Firmware Options: “It is important that these options match to both the TX module and receiver in order for them to bind.” The update to 4.0 erases a regulatory domain that was changed in the web UI (release notes 4.0.0).
- Fix
- Compare the regulatory domain under “Information” in the web UI of both devices (how to open it). On 900 MHz you match it in the “Options” tab. On 2.4 GHz the EU version with LBT (EU_CE_2400) is set when you flash: reflash the odd device with the matching domain.
The receiver won’t enter bind mode, no double blink
- Cause
- Three causes have sources. During the three power cycles it ran longer than 2 seconds each time: it then resets the counter (source code 4.1.0). Its firmware is 3.3.x or older and has a binding phrase: then there is no bind mode (Lua docs). Or “Bind Storage” is set to “Administered”: according to the source code it can then only be bound through the web UI.
- Fix
- Disconnect within 2 seconds each time, or use another way: button for 1.5 seconds or Betaflight. With old firmware, use the binding phrase or reflash. With “Administered”, set the phrase or UID in the web UI, tab “Binding”.
A quad with a built-in receiver (a whoop, say) won’t connect to the radio
- Cause
- On built-in SPI receivers, Betaflight 2026.6 speaks ExpressLRS 3 by default, which “is not compatible with ELRS V4 transmitters” (release notes 2026.6). Or the packet rate doesn’t fit: according to the SPI docs, SPI receivers don’t bind in D250, D500 and the Full Res modes.
- Fix
- Transmitter on 4.x: flash Betaflight with the build option
ELRSV4(see SPI), back up first. WithELRSV4, a transmitter on 3.x no longer works. For the packet rate, pick another one in the Lua script.
The ExpressLRS Lua script hangs at “Loading...”
- Cause
- The radio isn’t set up for ExpressLRS (troubleshooting). Between radio and transmitter module, ExpressLRS uses CRSF.
- Fix
- In the model setup, set the internal RF module to “CRSF” and the external one to off, or the other way round for an external module (Radio Preparation).
Connected, but the quad doesn’t respond
Connected (“C” in the Lua script), but Betaflight shows no stick movement and the radio finds only 10 telemetry sensors
- Cause
- The flight controller doesn’t read the receiver: RX and TX swapped, the wrong UART set in Betaflight, or the UART is inverted or in half duplex (troubleshooting).
- Fix
- Check the wiring (receiver TX to flight controller RX), set the UART and CRSF as above, check
get serialrx. If that doesn’t help, the docs say to try a different UART.
More than 10 telemetry sensors but no sticks; the LED blinks three times, then pauses; the Lua script shows “Model Mismatch”
- Cause
- Model Match: the receiver number of the model in the radio doesn’t match the model ID in the receiver. The docs: “the receiver will connect to the handset, but no data will be sent from the receiver to the flight controller” (Model Match). According to the troubleshooting page it can also be the firmware option RCVR_INVERT_TX, meant only for flight controllers with nothing but an SBUS pad free.
- Fix
- With the quad connected, switch “Model Match” in the Lua script off and on again: that assigns the current number. If you don’t want Model Match, set it to “On” briefly and back to “Off” after a second; that clears the ID in the receiver (docs). Only use RCVR_INVERT_TX if you are on the SBUS pad.
CRSF is greyed out in the “Serial Receiver Provider” list, or the App shows “The selected Receiver Provider is not supported by the current Build Configuration …”
- Cause
- The firmware was built without CRSF. In the Firmware Flasher CRSF is selected by default, but it can be deselected (Build Options).
- Fix
- Back up your settings (backup with diff all), reflash Betaflight and pick CRSF under “Radio Protocol” in the Firmware Flasher.
The quad won’t arm, Betaflight reports RXLOSS; the Receiver tab shows “Failsafe active”
- Cause
- The flight controller gets no valid signal from the receiver. The bars in the Receiver tab then show the failsafe values, not your sticks.
- Fix
- Work through the faults here. What exactly triggers RXLOSS: Quad won’t arm: RXLOSS.
The wrong bar moves, say throttle when you move the roll stick
- Cause
- The radio’s channel order doesn’t match the channel map in Betaflight.
- Fix
- Change the “Channel Map” in the Receiver tab; the default is AETR1234 (check the channels).
The LED shows something else
The LED is solid although the radio is off; no sticks, no RSSI
- Cause
- The receiver isn’t connected, it is in bootloader mode. According to the docs, the UART often pulls the RX pad low (pull-down for SBUS), or the boot button is being pressed, by heatshrink for example, or the boot pad touches ground. With a DJI Air Unit, Caddx Vista or DJI O3 wired with all six wires to the flight controller, it can be the SBUS/DJI HDL wire.
- Fix
- Disconnect the receiver’s TX and RX from the flight controller and power up again. If the LED now blinks slowly, it’s the UART: use another one or, as the docs say, solder a 300 Ω to 1 kΩ resistor between the flight controller’s RX pad and 3.3 V or 5 V. Check the boot button and the boot pad; with DJI, remove the SBUS/DJI HDL wire.
The LED flickers very fast and the receiver won’t connect
- Cause
- It is in WiFi mode. If it gets no connection for about 60 seconds after power-up, it switches its WiFi on (web UI docs). That happens, for example, when the radio is off.
- Fix
- Switch the radio on and power-cycle the receiver. The waiting time is an option in the web UI.
After every power-up it double-blinks again and the bind is gone
- Cause
- “Bind Storage” is set to “Volatile”: “Binding info is forgotten after a power-cycle” and the receiver boots into bind mode (Lua docs).
- Fix
- Bind again, then set “Bind Storage” to “Persistent” in the receiver’s settings in the Lua script.
Bound: what next?
If the quad still won’t arm, Betaflight tells you why with an arming flag: Quad won’t arm: all arming flags. Before your first flight, check the failsafe as described in Set up Betaflight failsafe; the App’s Receiver tab links the failsafe docs for that: “Always check that your Failsafe is working properly!”
How fast the quad turns is set by your rates; where to set them is in Setting up Betaflight rates. With a blackbox log, the free check shows you how you really use your sticks and whether your rates fit.
Sources
As of November 12, 2026, checked against ExpressLRS 4.1.0 (July 17, 2026) and Betaflight 2026.6.2 (App and firmware from September 16, 2026), the latest versions on that day. Nothing here was tested on hardware; procedures, menu names and LED patterns come from the docs and the source code.
- ExpressLRS docs: Binding, LED Status, Firmware Options, Web UI, Lua Script, Radio Preparation, Wiring up, Configuring FC, Troubleshooting, SPI Receivers, Switch Config, Model Match, blog post on the new Lua scripts.
- ExpressLRS: release notes 4.1.0 and 4.0.0, source code 4.1.0:
rx_main.cpp,devButton.cpp,devLED.cpp,RXEndpoint.cpp,RXParameters.cpp,TXModuleParameters.cpp; Lua package ExpressLRS/Lua. - Betaflight docs: Setup Guide, Receiver Tab, Ports Tab, Rx, CLI, Build Options, release notes 2026.6.
- Betaflight 2026.6.2 source code:
cli.c,crsf.c,rx_bind.c,msp.c,pg/rx.c,expresslrs_common.h; App:ReceiverTab.vue, English textslocales/en/messages.json.
Last updated: Nov 14, 2026 · checked with Betaflight 2026.6.2