No receiver input in BetaflightUpdated 2 months ago

If your drone is powered on and connected to your radio, but no stick movement appears in the Betaflight Receiver tab, the issue is usually related to receiver protocol, UART configuration, firmware compatibility, frequency mismatch, or wiring.

This can happen with:

• DJI O3 / O4 / O4 Pro systems
• ExpressLRS (ELRS)
• TBS Crossfire (CRSF)
• FrSky SBUS receivers
• Other UART-based receiver systems

Always remove all propellers before troubleshooting.

Common Symptoms

You may experience:

• No stick movement in the Betaflight Receiver tab
• The drone does not arm
• “RXLOSS” or “NO RX” warning in the OSD
• Receiver appears bound, but Betaflight receives no input
• DJI video works, but the radio does not control the drone
• ELRS or Crossfire shows a link, but channels do not move

Step 1 — Identify your receiver system

First identify which receiver system your drone is using.

Common setups include:

• DJI O3 / O4 / O4 Pro with DJI Remote Controller
• ELRS 2.4 GHz
• ELRS 868/915 MHz
• TBS Crossfire (CRSF)
• External SBUS receiver connected to the flight controller

Important:
A working video feed does not automatically mean the radio control link is working. Video transmission and receiver control are separate systems.

Step 2 — Check ELRS frequency and region compatibility

If you use ELRS, both the transmitter module and the receiver must use:

• The same frequency band
• Compatible regional firmware
• Compatible ELRS firmware versions

ELRS systems are separated by both frequency and regulatory region.

Typical examples:

2.4 GHz ELRS

• EU region: usually LBT firmware
• International region: usually ISM / FCC firmware

868 / 915 MHz ELRS

• EU region: 868 MHz EU firmware
• International region: 915 MHz FCC firmware

Important:

• ELRS 2.4 GHz hardware does not work with ELRS 868/915 hardware
• ELRS 868 MHz EU does not work with 915 MHz FCC firmware
• ELRS 2.4 GHz LBT does not properly work with 2.4 GHz ISM/FCC firmware
• Matching binding phrases alone are not sufficient if region or frequency is incorrect

For most EU customers, the correct setup is:

• 2.4 GHz LBT
  or
• 868 MHz EU

Also verify:

• Matching ELRS major firmware versions
• Correct firmware target
• Receiver antenna connected correctly
• Receiver is powered properly
• Receiver enters bind mode normally

Incorrect ELRS firmware or region settings are one of the most common causes of missing receiver input.

Step 3 — Check receiver protocol in Betaflight

In Betaflight:

1. Open the “Ports” tab
2. Enable “Serial RX” only on the UART used by the receiver
3. Save and reboot

Then:

1. Open the “Configuration” tab
2. Under Receiver Mode select:
   • “Serial-based receiver”
3. Under Serial Receiver Provider select the correct protocol

Common examples:

• ELRS receiver → CRSF
• TBS Crossfire → CRSF
• DJI systems → SBUS or SBUS_FAST depending on setup
• FrSky receivers → SBUS

Do not enable Serial RX on multiple UARTs unless specifically required.

Incorrect receiver protocol settings are one of the most common causes of no receiver input.

Step 4 — DJI O3 / O4 / O4 Pro specific checks

DJI systems require several settings to match correctly.

Please verify:

• The Air Unit is activated and linked correctly
• The Goggles are in the correct mode
• The DJI Remote Controller is linked correctly
• Betaflight uses the correct receiver protocol
• The protocol configured in the Goggles matches Betaflight

Some DJI systems support:

• NORMAL SBUS
  or
• FAST SBUS (SBUS_FAST)

If FAST protocol is enabled in the Goggles, Betaflight must also be configured correctly.

This is commonly configured in Betaflight CLI:

set sbus_baud_fast = ON
save

If the Goggles are configured for NORMAL mode, FAST SBUS should not be enabled in Betaflight.

A mismatch between DJI protocol settings can result in:

• No receiver input
• RXLOSS
• Failure to arm
• Intermittent receiver connection

Step 5 — Do not randomly rewire the receiver

Do not randomly move or resolder receiver wires unless you fully understand the wiring and firmware requirements.

Many flight controllers are configured specifically for:

• DJI SBUS
• ELRS CRSF
• Crossfire CRSF
• SBUS receivers

Changing receiver type may require:

• Different UART configuration
• Different receiver protocol
• Different Betaflight settings
• Correct factory dump or preset
• In some cases reflashing Betaflight correctly

Incorrect rewiring or wrong firmware settings may result in:

• No receiver input
• RXLOSS
• Hardware damage
• Short circuits

Step 6 — Check receiver wiring

If you use an external receiver, inspect the wiring carefully.

Typical UART receiver wiring:

• Receiver TX → Flight Controller RX
• Receiver RX → Flight Controller TX
• 5V → 5V
• GND → GND

Common problems:

• TX/RX reversed incorrectly
• Receiver connected to wrong UART
• Loose wires
• Cold solder joints
• Damaged pads
• Receiver powered only by USB when battery power is required
• Missing or damaged antenna

Some Air Units and receivers require full battery power and may not initialize correctly from USB power alone.

Step 7 — Check Betaflight Receiver tab

After saving all settings:

1. Reboot the flight controller
2. Power the drone correctly
3. Turn on the radio
4. Open the Receiver tab in Betaflight
5. Move the sticks

You should see movement for:

• Roll
• Pitch
• Yaw
• Throttle

If channels move incorrectly, verify the channel map.

Common channel maps:

• AETR
• TAER

Step 8 — If it still does not work

Please collect the following information before contacting support:

• Order number
• Drone model
• Receiver type
• Radio model
• DJI Goggles model if used
• Air Unit model (O3, O4, O4 Pro)
• ELRS frequency and region
• Betaflight Ports screenshot
• Betaflight Receiver screenshot
• Receiver wiring photos
• Firmware versions if known

Please contact our support team at:

[email protected]