ELRS receiver won’t bindUpdated 2 months ago

If your ExpressLRS receiver does not bind to your radio, the issue is usually caused by a mismatch between frequency, region, firmware version, binding phrase, firmware target, or receiver type.

ExpressLRS is also called ELRS. Both terms refer to the same radio control system.

Always remove all propellers before troubleshooting.

Common symptoms

You may experience:

• Receiver LED keeps blinking
• Receiver does not become solid after powering on
• No telemetry on the radio
• “RXLOSS” or “NO RX” warning in Betaflight
• ExpressLRS Lua script shows “Loading…”
• Radio and receiver do not connect after flashing
• Receiver WiFi does not appear
• Receiver appears bound, but no stick movement is visible in Betaflight

Step 1 — Check frequency and region

Your transmitter module and receiver must use the same frequency band and compatible regional firmware.

ELRS 2.4 GHz

For most EU customers, the correct region is usually:

• 2.4 GHz LBT / EU CE

For non-EU or FCC regions, it is often:

• 2.4 GHz ISM / FCC

2.4 GHz LBT and 2.4 GHz ISM/FCC are not the same setup. If one side uses LBT and the other side uses ISM/FCC, binding may fail or the link may not work correctly.

ELRS 868 / 915 MHz

For most EU customers, the correct region is usually:

• 868 MHz EU

For FCC regions, it is usually:

• 915 MHz FCC

868 MHz EU and 915 MHz FCC are not compatible with each other.

Important:

• ELRS 2.4 GHz hardware cannot bind to ELRS 868/915 MHz hardware
• ELRS 868 MHz EU cannot bind to 915 MHz FCC setups
• ELRS 2.4 GHz LBT should be matched with 2.4 GHz LBT
• ELRS 2.4 GHz ISM/FCC should be matched with 2.4 GHz ISM/FCC

Selecting the wrong region or frequency is one of the most common causes of binding problems.

Step 2 — Check firmware version compatibility

The transmitter module and receiver must use compatible ExpressLRS firmware versions.

If the firmware versions are incompatible, binding will not work.

Check:

• ELRS major version on the transmitter module
• ELRS major version on the receiver
• Correct firmware target
• Correct device manufacturer and model
• Correct frequency band
• Correct regulatory domain

Do not flash a random target. Selecting the wrong target can cause the receiver or transmitter module to stop working.

If you are unsure which target to use, check the product page, factory documentation, or contact support before flashing.

Step 3 — Use a binding phrase whenever possible

The recommended method is to use the same unique binding phrase on both the transmitter and receiver.

The binding phrase must match exactly.

Check for:

• Same spelling
• Same numbers
• No extra spaces
• Same capitalization
• Same phrase on transmitter and receiver

A binding phrase is not a password. It is used so your transmitter and receiver can automatically connect to each other.

If both devices are flashed with the same binding phrase, they should connect automatically after powering on.

Step 4 — Traditional binding only works in the correct situation

Traditional binding methods include:

• Receiver bind button
• 3× power-cycle method
• Bind command from the transmitter / Lua script

However, traditional binding may not work if a binding phrase is already set on the receiver.

If the receiver was flashed with a binding phrase, use the same binding phrase on the transmitter instead of trying random manual bind methods.

Step 5 — Check receiver power

Some receivers may not power correctly from USB only.

If the receiver LED does not turn on or the receiver does not enter WiFi/bind mode:

• Check whether the receiver receives 5V power
• Try powering the drone with a battery where safe and required
• Check solder joints and connectors
• Check for damaged wires or pads
• Make sure the antenna is connected

Important: Always remove propellers before connecting a battery on the bench.

Step 6 — WiFi mode troubleshooting

Many ELRS receivers automatically enter WiFi mode after being powered for around 60 seconds without a connection.

When in WiFi mode, you should see a WiFi network such as:

• ExpressLRS RX
• ExpressLRS TX

If the WiFi network does not appear:

• Wait at least 60 seconds
• Make sure the receiver is powered correctly
• Move closer to the receiver
• Check whether the receiver is already connected to the transmitter
• Reboot and try again

Once connected to the ExpressLRS WiFi network, the Web UI is usually available at:

http://10.0.0.1

Use WiFi updates only if you are sure you selected the correct firmware target.

Step 7 — SPI receiver or UART receiver?

This is very important.

UART ELRS receivers

Most external ELRS receivers are UART receivers.

They are usually updated with:

• ExpressLRS Configurator
• ExpressLRS Web Flasher
• WiFi update
• UART flashing

In Betaflight, UART ELRS receivers normally use:

• Serial RX enabled on the correct UART
• Receiver protocol: CRSF

SPI ELRS receivers

Some small AIO flight controllers have an integrated SPI ELRS receiver.

SPI receivers are different because the ELRS code is part of the flight controller firmware.

For SPI receivers:

• Do not update them with the ExpressLRS Configurator
• Update Betaflight instead
• Use the correct Betaflight target
• Betaflight version matters for ELRS compatibility

If you flash the wrong Betaflight target or wrong receiver mode, the receiver may stop working.

Step 8 — Check Betaflight receiver settings

Even if the receiver is bound, Betaflight must be configured correctly to receive stick inputs.

For UART ELRS receivers:

1. Open Betaflight
2. Go to the Ports tab
3. Enable Serial RX only on the correct UART
4. Save and reboot
5. Go to the Receiver settings
6. Select Serial-based receiver
7. Select CRSF as receiver provider

Then open the Receiver tab and move the sticks.

If the channels do not move, binding alone is not enough. Check UART, wiring, receiver protocol, and firmware compatibility.

Step 9 — ExpressLRS Lua script stuck on “Loading…”

If the Lua script is stuck on “Loading…”, the issue is usually on the radio/transmitter side, not the receiver side.

Check:

• External RF module is enabled, if using an external module
• Internal RF is set correctly, if using internal ELRS
• Correct baud rate / CRSF settings on the radio
• Correct Lua script version
• Radio firmware supports the module correctly

A Lua script stuck on “Loading…” usually means the radio is not communicating properly with the ELRS transmitter module.

Step 10 — Before contacting support

Please collect the following information:

• Order number
• Drone model
• Receiver model
• Radio model
• Internal or external ELRS module
• ELRS frequency: 2.4 GHz, 868 MHz, or 915 MHz
• Region: LBT / EU CE, FCC, ISM, EU 868, or FCC 915
• ELRS firmware version on transmitter
• ELRS firmware version on receiver
• Binding method used
• Photos of receiver wiring
• Screenshot of Betaflight Ports tab
• Screenshot of Betaflight Receiver tab
• Short video showing receiver LED behavior

Contact our support team at:

[email protected]

For a full step-by-step flashing and binding guide, please also check our ExpressLRS Binding Guide.