The Receiver tab is the most-misconfigured page in Betaflight. I see the same three issues on every “my quad won’t respond” help post: wrong serial provider, TAER1234 channel map mismatch, and RSSI on the wrong aux channel. Each of these takes 30 seconds to fix if you know what to look for. Here’s the full setup workflow.
Serial Receiver Provider: The First Setting That Matters
This dropdown determines how Betaflight interprets the serial data stream from your receiver. Get it wrong and the channel bars in the Receiver tab won’t move, no matter how perfectly your radio is bound.
CRX (Crossfire): Select “CRSF” as the serial provider. Crossfire sends data via the CRSF protocol on a single UART wire. If you see “Serial RX” set on the correct UART in the Ports tab but the receiver bars don’t move, check that the TX and RX pads match — CRSF needs TX on the FC connected to RX on the Crossfire receiver.
ExpressLRS: Also “CRSF” as the serial provider. ExpressLRS uses the same CRSF protocol as Crossfire. On SPI-based ELRS receivers (built into the FC), the receiver type is “SPI RX” with “ExpressLRS” selected in the SPI bus receiver provider field that appears below.
Ghost: Same as above — “CRSF.” ImmersionRC Ghost adopted CRSF for Betaflight compatibility.
SBUS (FrSky, Futaba): Select “SBUS” as the serial provider. SBUS receivers output an inverted signal on a dedicated SBUS pad. If your FC has a dedicated SBUS pad, use it — the inverter is built in. Using a regular UART RX pad with SBUS requires enabling set sbus_inversion = ON in CLI.
Spektrum: Select “SPEKTRUM2048” for 2048 resolution or “SPEKTRUM1024” for older 1024-resolution receivers. Spektrum uses a dedicated serial port — typically labeled “SRXL2” or “Spektrum” on the FC.
PPM: Avoid entirely in 2026. PPM has 8 channels, high latency, and no telemetry. If your receiver has PPM-only output, replace it — even a $12 ELRS EP2 receiver is a massive upgrade.
Channel Map: Why Your Throttle Is on the Wrong Stick
The channel map tells Betaflight which channel corresponds to which control axis. The default is AETR1234: Aileron (roll) on CH1, Elevator (pitch) on CH2, Throttle on CH3, Rudder (yaw) on CH4. This matches the OpenTX/EdgeTX default output order.
If your radio outputs TAER order (Spektrum and some FrSky templates), change the channel map to “TAER1234” — otherwise your throttle stick controls roll, roll controls pitch, and nothing works.
How to verify: Open the Receiver tab, move each stick one axis at a time, and watch which bar moves:
– Roll stick (right) → Roll bar (first)
– Pitch stick (right) → Pitch bar (second)
– Throttle stick (left, up/down) → Throttle bar (third)
– Yaw stick (left, left/right) → Yaw bar (fourth)
If the wrong bar moves, adjust the channel map dropdown until stick-to-bar mapping is correct. Don’t try to fix channel mapping in the radio — fix it here.
RSSI Channel: Stop Flying Blind on Signal Strength
RSSI tells you how strong your radio link is. Without it configured, you’re one step away from a failsafe with no warning.
For CRSF receivers (Crossfire, ELRS): RSSI is embedded in the CRSF protocol as a dedicated field. Select “RSSI_ADC” is NOT correct — that’s for analog RSSI input on a dedicated pad. For CRSF, Betaflight reads RSSI automatically from the CRSF stream. However, you should still set up RSSI in the OSD to see it while flying.
For analog receivers with RSSI output: Connect the RSSI pad on the receiver to a dedicated RSSI pad on the FC (not a regular analog input). Enable “RSSI_ADC” in the Receiver tab. If your FC doesn’t have an RSSI pad, you can assign RSSI to an aux channel on the radio — set the channel in the “RSSI Channel” dropdown and Betaflight reads it as a percentage.
RSSI scaling: CRSF RSSI uses dBm scaling where 0 dBm is the default warning threshold. ExpressLRS uses LQ (Link Quality) on channel 14 by default — set “RSSI Channel” to “AUX12 (CH14)” for LQ display.
Failsafe Configuration and Testing
The failsafe section configures what happens when the receiver loses signal. This is NOT where you set failsafe behavior — that’s in the Failsafe tab (stage 1 and stage 2). The Receiver tab failsafe settings are for the radio/receiver side.
Failsafe mode: “Hold” means the receiver outputs the last valid channel positions. “No pulses” means the receiver stops outputting entirely. Betaflight detects loss of valid data and triggers its own failsafe in either case. I prefer “No pulses” — it’s unambiguous and triggers immediately.
Failsafe testing: Arm the quad with props OFF, then turn off your radio. The Motors tab should show motors stopping within the configured failsafe delay (default 1 second). If they keep spinning, your failsafe isn’t configured correctly.
As we detailed in our FPV Failsafe Configuration guide, proper failsafe setup is the difference between a controlled descent and a flyaway. The Receiver tab is the first link in that chain.
Signal Quality Monitoring
ExpressLRS introduced Link Quality (LQ) as a more useful metric than raw RSSI. LQ measures the percentage of successfully received packets over a sliding window. A link at -95 dBm with LQ 100 is better than a link at -80 dBm with LQ 60.
Display LQ alongside RSSI dBm on your OSD. Place both in your peripheral vision zone. When LQ drops below 80, turn back. Below 50, land immediately — you’re seconds from failsafe.
As we covered in our ExpressLRS Binding Methods guide, a correctly bound receiver with binding phrase auto-detection eliminates the need to re-enter the Receiver tab after firmware updates.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
The UAVModel Betaflight Setup Bundle includes a pre-configured flight controller with all receiver tab settings dialed in for ExpressLRS CRSF — plug in your receiver and fly. Available on our flight controllers page.