Your receiver is bound, your radio is on, and Betaflight shows zero stick movement on the Receiver tab. I’ve debugged this exact scenario at a flying field while a pilot held up four other people waiting to fly. Nine times out of ten, it’s one of three settings in the Receiver tab. Here’s how to fix each one in under two minutes.
Step 1: Serial RX Provider Selection
This is the #1 misconfiguration. Betaflight defaults to SPEKTRUM1024 on a fresh flash, and no modern FPV receiver uses that protocol. The Receiver tab on the Ports page — not the Configuration tab — is where you set this.
Navigate to Ports tab first. Find the UART your receiver is wired to. Enable “Serial Rx” toggle for that UART. Do not change anything else on that row. Save and reboot.
Now go to Configuration tab → Receiver section. Set “Receiver Mode” to “Serial-based receiver”. Then set “Serial Receiver Provider” based on your hardware:
- CRSF (Crossfire, Tracer, ELRS via CRSF protocol): Select “CRSF”. This is the correct choice for all ExpressLRS receivers, all TBS Crossfire receivers, and TBS Tracer. ELRS uses the CRSF wire protocol even though it’s a different radio protocol — confusing, but that’s how it works.
- SBUS (FrSky, Futaba, older receivers): Select “SBUS”. Requires an uninverted signal. F4 and F7 flight controllers typically have a dedicated SBUS pad with a hardware inverter. Using a random UART RX pad for SBUS often results in no signal because SBUS is inverted relative to standard UART.
- IBUS (FlySky): Select “IBUS”. Connect to any free UART RX pad. Unlike SBUS, IBUS is uninverted and works on any UART.
Common pitfall: Selecting “SBUS” when using CRSF. The Receiver tab will show zero movement, no flags change, and the “Bad RX” arming disabled flag stays red. The fix is literally two clicks in the dropdown — this is the first thing I check when someone says “my receiver is bound but Betaflight doesn’t see it.”
Step 2: Channel Map
Once the provider is correct, your sticks should move on the Receiver tab preview. If they move but the wrong channels respond — throttle on the roll bar, yaw on the pitch bar — you have a channel map mismatch.
Betaflight defaults to AETR1234 (Aileron, Elevator, Throttle, Rudder, then Aux channels 1-4). Most radios default to the same. But FrSky radios default to TAER, and some FlySky radios use AETR with different channel ordering.
The fix: Go to Receiver tab. Change “Channel Map” dropdown until stick movements match the preview bars. If your throttle stick moves the Roll bar, you’re on the wrong map. Cycle through AETR1234, TAER1234, and RETA1234 until each stick controls its correct axis.
For radios that don’t match any preset, use the “Custom” channel map and define the order manually from the CLI:
map TAER1234
save
Step 3: RSSI Channel and Telemetry
RSSI setup differs by protocol:
CRSF/ELRS: RSSI is injected into the serial stream — no channel assignment needed. On the Receiver tab, RSSI channel should be set to “Disabled.” Betaflight reads RSSI directly from the CRSF frame. If you set an RSSI channel with CRSF, you create a conflict where the OSD shows duplicate or incorrect values.
To verify: open the OSD tab, add the “RSSI value” element. With the radio on and quad powered, the value should update in real-time. At 1m distance, expect RSSI around -30dB. In the OSD, this displays as “RSSI: -30dB” if you’ve selected the dBm display mode.
SBUS/IBUS: These protocols can send RSSI on an auxiliary channel. On the Receiver tab, set RSSI Channel to the aux channel your radio outputs RSSI on. This is typically configured in the radio’s model setup. For EdgeTX/OpenTX radios, you set RSSI output to a specific channel in the Telemetry page.
Telemetry output: For CRSF and ELRS, telemetry works automatically once the serial provider is set — Betaflight sends VFAS (battery voltage), current, GPS coordinates, and attitude data back to the radio. No additional configuration needed on the Receiver tab.
For SmartPort (FrSky) telemetry, you need a separate wire from a TX pad to the receiver’s SmartPort pin, plus enabling “Telemetry” output on that UART’s Ports tab. The Receiver tab itself doesn’t control telemetry — it’s all on the Ports tab.
| Setting | CRSF/ELRS | SBUS | IBUS | Notes |
|---|---|---|---|---|
| Receiver Mode | Serial-based | Serial-based | Serial-based | Same for all digital protocols |
| Serial Provider | CRSF | SBUS | IBUS | Must match receiver protocol |
| Channel Map | AETR1234 | AETR1234 or TAER1234 | AETR1234 | Check stick movement matches |
| RSSI Channel | Disabled | Aux channel (e.g., 12) | Aux channel | CRSF injects RSSI in-band |
| Telemetry | Automatic | Separate SmartPort wire | N/A | CRSF telemetry requires no extra config |
| Half-duplex UART | No (unless F4 single-wire) | No | No | Use dedicated TX and RX pads |
Common Mistakes on the Receiver Tab
Mistake 1: Changing Settings Without Saving
Betaflight requires a deliberate “Save and Reboot” in the bottom right corner of the Configuration tab. Changing the Serial Provider dropdown and navigating away without saving reverts to the previous value. I’ve watched a pilot cycle through three wrong providers, each time forgetting to save, insisting “none of them work.”
Fix: After changing any radio-related setting, click Save and Reboot. Wait for the disconnect/reconnect chime. Then verify on the Receiver tab.
Mistake 2: SBUS on a Random UART Without Inverter
F3/F4 flight controllers require an external inverter for SBUS signals. Many F4 boards have a dedicated SBUS pad with a built-in inverter. Wiring SBUS to UART1 RX instead of the SBUS pad gives no signal because the inverted serial data looks like noise to a standard UART.
Fix: Use the labeled SBUS pad. If your FC doesn’t have one, enable sbus_inversion = ON in CLI if supported by your MCU (F7/H7 only). On F4, you need an external inverter or switch to a non-inverted protocol (IBUS, CRSF).
Mistake 3: Two Receivers Enabled Simultaneously
Some flight controllers have both an onboard SPI receiver (FrSky XM+ clone) and external UART pads. If the SPI receiver is enabled in the Configuration tab and you wire an external ELRS receiver to a UART, Betaflight reads from the SPI bus and ignores the UART. The Receiver tab shows “RX loss” despite a bound external receiver.
Fix: Check Configuration tab → Receiver section. If “SPI RX support” shows a protocol (FRSKY_D, FRSKY_X, etc.), the onboard receiver is active. Either disable it and use the external receiver, or use the onboard receiver and disconnect the external one. Cannot use both.
⚠️ Regulatory Notice: The receiver configuration and telemetry settings described in this article should comply with the latest 2026 drone regulations in your country or region. Some jurisdictions regulate telemetry power output and data transmission in certain frequency bands. Always verify local laws regarding UAV radio equipment, frequency usage, and remote ID requirements. Regulations vary between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
For a complete setup walkthrough from radio to flight, see our EdgeTX radio model setup guide. If you’re troubleshooting arming issues, check our Betaflight modes tab guide which covers arm logic and pre-arm sequencing.
A properly configured receiver is the foundation of a reliable quad. The Radiomaster RP1 ELRS receiver, stocked at uavmodel, uses CRSF protocol with auto-detected serial provider — wire to any UART, set to CRSF, and the Receiver tab populates instantly. No SBUS inversion headaches.