What does the NO RX error mean in Betaflight?

The NO RX error indicates that the flight controller is not receiving any valid control data from the radio receiver. This is usually due to wiring errors, incorrect UART configuration in the Ports tab, or selecting the wrong protocol in the Receiver tab.

How do I wire an ELRS receiver to a flight controller?

You must supply 5V and GND. Then, cross the signal wires: connect the receiver's TX pad to an RX pad on the flight controller, and the receiver's RX pad to the corresponding TX pad on the flight controller.

What provider should I choose for ELRS in Betaflight?

In the Betaflight Receiver tab, select 'Serial (via UART)' for the Receiver Mode, and 'CRSF' for the Serial Receiver Provider.

Betaflight NO RX Error: Comprehensive Troubleshooting Guide

Betaflight “NO RX” Error: Comprehensive Troubleshooting Guide

Are you stuck on the bench with the dreaded **”NO RX”** warning in Betaflight? Receiver communication loss is one of the most common issues FPV pilots face, whether you are building a new quadcopter or recovering from a harsh crash. This guide breaks down the step-by-step diagnostic process to restore your control link and get you back in the air.

## Understanding the “NO RX” Error

The “NO RX” warning means your Flight Controller (FC) is not receiving valid RC data from your receiver. This is typically caused by wiring issues, incorrect Betaflight configuration, or a damaged receiver unit.

### Common Causes & Quick Checks

* **Wiring/Soldering:** Broken wire, cold solder joint, or crossed TX/RX pads.
* **Betaflight Ports Configuration:** Serial RX not enabled on the correct UART.
* **Betaflight Receiver Tab:** Incorrect protocol selected (e.g., SBUS vs. CRSF).
* **Firmware Mismatch:** Binding issues due to mismatched ExpressLRS (ELRS) major versions.

## Step-by-Step Diagnostic Protocol

Follow these steps sequentially to isolate the point of failure.

### 1. Verify Binding and Power
First, ensure your receiver is getting 5V power and is successfully bound to your radio transmitter.
For an ELRS receiver, a solid LED indicates a successful connection, whereas a slow or fast blinking LED means it is not connected or in WiFi mode.

### 2. Inspect Wiring (TX to RX, RX to TX)
A classic mistake is wiring TX to TX and RX to RX. Remember, the signal must cross over:
* **Receiver TX** -> **Flight Controller RX**
* **Receiver RX** -> **Flight Controller TX**

| Receiver Pad | Flight Controller Pad | Function |
| :— | :— | :— |
| 5V | 5V | Power supply |
| GND | GND | Ground |
| TX | RX (e.g., RX2) | Transmit telemetry to FC |
| RX | TX (e.g., TX2) | Receive control data from FC |

### 3. Check Betaflight Ports Tab
Connect to Betaflight Configurator. Go to the **Ports** tab. Ensure **Serial Rx** is toggled ON *only* for the UART where you soldered your receiver. Do not enable any other features on this UART unless you know what you are doing. Save and Reboot.

### 4. Check Betaflight Receiver Tab
Go to the **Receiver** tab and verify your settings based on your protocol:

* **ExpressLRS (ELRS) or Crossfire:**
* Receiver Mode: `Serial (via UART)`
* Serial Receiver Provider: `CRSF`
* **FrSky (SBUS):**
* Receiver Mode: `Serial (via UART)`
* Serial Receiver Provider: `SBUS`

## Hardware Upgrade Recommendation

If you have verified your wiring and configuration, but the FC still isn’t seeing the receiver, the receiver itself or the FC UART may be damaged.

For the most robust and lowest latency control link, we highly recommend upgrading to the latest ExpressLRS hardware. The [Happymodel EP1 2.4GHz ELRS Receiver](https://uavmodel.com) available at UAVModel.com offers exceptional range, tiny form factor, and includes a T-antenna for optimal signal propagation. It’s the perfect replacement to permanently solve range and communication dropouts.

## Video Tutorial

For a visual walkthrough of setting up an ELRS receiver and troubleshooting Betaflight connections, watch this excellent guide:

Leave a Comment Cancel Reply