You’re 400 meters out, flying behind a treeline, and your OSD says “RSSI: 85.” You think you’re fine. Then the quad drops — not a graceful GPS rescue, a full failsafe into the canopy. The problem? Your RSSI was never calibrated, and 85 on the OSD was actually -102dBm at the receiver. Here’s how to fix RSSI scaling, set real warning thresholds, and know exactly when to turn back.
How RSSI Actually Works
RSSI (Received Signal Strength Indicator) is the receiver’s measurement of incoming signal power. Every receiver reports it differently:
Crossfire (CRSF): Reports actual dBm values. Values like -40dBm (tx right next to rx) to -110dBm (verge of failsafe). CRSF sends this as a native telemetry value — no scaling needed. Just set RSSI channel to “Disabled” in Betaflight (CRSF injects RSSI directly).
ExpressLRS (ELRS): Also reports dBm. ELRS 3.x sends RSSI dBm and Link Quality as separate telemetry values. LQ (Link Quality) is actually more useful than RSSI — LQ drops before RSSI does, so it’s an earlier warning. Set your OSD to show both.
Analog / FrSky: Reports a raw 0-100% value that needs scaling. FrSky receivers typically map 0-100% to approximately -110dBm to -40dBm, but the curve isn’t linear.
Ghost / Tracer: Similar to CRSF — native dBm values through the telemetry stream.
The analog RSSI problem: Without proper scaling, a 50% reading could mean -100dBm (danger) or -70dBm (safe), depending on the receiver. This is why so many pilots failsafe at “RSSI 40” — the percentage is fabricated by a default formula that doesn’t match their hardware.
Step-by-Step RSSI Configuration
Step 1: Identify Your Receiver Type
Open Betaflight Receiver tab. Look at the protocol. If it says “CRSF” — you have Crossfire or ELRS. If it says “SBUS” with an FrSky receiver — you’re on analog RSSI.
Step 2: Configure RSSI Channel (Analog Only)
For CRSF/ELRS: Skip this. Set RSSI Channel to “Disabled” in the Receiver tab. CRSF/ELRS injects RSSI as an AUX channel automatically.
For analog receivers: In Betaflight Receiver tab, set RSSI Channel to the AUX channel carrying RSSI (typically AUX4 or AUX8 — check your radio’s channel output screen). If the RSSI value jumps when you enable it, you’ve got the right channel.
What happens if you get it wrong: Setting RSSI Channel on CRSF/ELRS causes double-reporting — the OSD shows two different RSSI values, or the value flickers between the correct telemetry RSSI and a garbage AUX channel reading. Disable the channel.
Verification: In the OSD tab, add the “RSSI Value” element. Power up with the transmitter nearby — RSSI should show a high value (close to 100 for analog, -30 to -50dBm for CRSF). Walk the transmitter to another room — RSSI should decrease.
Step 3: Calibrate RSSI Scaling (Analog Only)
Analog RSSI uses the following formula in Betaflight CLI:
set rssi_scale = 100
set rssi_offset = 0
The scale maps the raw input voltage to a percentage. Default is 100 (1:1 mapping), which is wrong for most receivers.
Calibration method:
1. With TX right next to RX: note raw value (e.g., 1900)
2. Turn off TX (or put in microwave as a Faraday cage): note raw value (e.g., 1100)
3. Scale = 100 / ((max – min) / range). For FrSky: set rssi_scale = 145 and set rssi_offset = 0 is a common starting point.
For a more precise approach, power the RX through a variable attenuator and map 3-4 points. Realistically, the FrSky default of scale = 100 puts your failsafe point at around “RSSI 20” on the OSD — dangerously close to where most pilots set their warning threshold.
Step 4: Set RSSI Warning Thresholds
For CRSF/ELRS (dBm-based):
– Warning: -95dBm (signal is degrading, start heading back)
– Critical: -105dBm (imminent failsafe, land immediately)
– LQ Warning (ELRS only): 80% (packet loss starting, dBm may still look fine)
For analog (% based):
– Warning: 45% (after proper calibration — roughly -95dBm equivalent)
– Critical: 30% (failsafe within seconds)
In the OSD tab, set the RSSI element to blink at the warning threshold. This visual alert is far more effective than a number you have to read.
RSSI and Link Quality Comparison
| Receiver Protocol | Native RSSI Format | Link Quality Available | Failsafe Point (approx) | Warning Threshold | Critical Threshold | Calibration Needed |
|---|---|---|---|---|---|---|
| Crossfire (CRSF) | dBm (-40 to -110) | No (native RSSI is reliable) | -110dBm | -95dBm | -105dBm | None |
| ExpressLRS 2.4GHz | dBm + LQ% | Yes (LQ more useful) | -112dBm / LQ 0% | -100dBm / LQ 70% | -108dBm / LQ 50% | None |
| ExpressLRS 900MHz | dBm + LQ% | Yes | -117dBm / LQ 0% | -105dBm / LQ 70% | -112dBm / LQ 50% | None |
| FrSky ACCST (analog) | 0-100% scaled | No | ~30% | 45% | 30% | Required (scale + offset) |
| FrSky ACCESS | dBm (via FPORT) | No | -105dBm | -95dBm | -100dBm | None (if running FPORT) |
| Ghost | dBm | No | -110dBm | -95dBm | -105dBm | None |
| Tracer | dBm | No | -112dBm | -100dBm | -108dBm | None |
What Most Pilots Get Wrong
Mistake 1: Setting RSSI Channel in Betaflight while using CRSF or ELRS.
This is the most common RSSI bug I see. CRSF and ELRS inject RSSI directly into the telemetry stream — Betaflight picks it up automatically. When you also set an RSSI AUX channel, the OSD alternates between the correct telemetry value and a garbage AUX value. The OSD reads “50” then “95” then “50” — the pilot doesn’t know which to trust. Fix: set RSSI Channel to “Disabled” in the Receiver tab.
Mistake 2: Ignoring Link Quality on ELRS.
ELRS uses variable packet rates (50Hz to 1000Hz). At 500Hz, the receiver expects 500 packets per second. If it receives 450, RSSI dBm might still read -80 (good), but LQ drops to 90% — meaning 10% of control packets are lost. Your quad responds to only 9 out of 10 stick movements. LQ is the canary; RSSI is the confirmation. Display both in the OSD.
Mistake 3: Setting RSSI warning at 20% (analog).
Default analog RSSI scaling maps 0-100% across a voltage range that doesn’t match any real receiver. With default scale=100, the receiver’s actual failsafe point often sits at RSSI 15-25% on the OSD. Setting your warning at 20% means you get the alert roughly 0.3 seconds before the quad drops. Calibrate the scale, then set warning at 45%. You want 10-15 seconds of warning time.
Mistake 4: Flying behind obstacles and trusting RSSI alone.
RSSI updates every 50-100ms on most protocols. At 60mph (27 m/s), you cover 2.7 meters between RSSI updates. A single tree can attenuate 2.4GHz by 20-30dB instantly — that’s the difference between -80dBm and -110dBm in one update cycle. RSSI is a trend indicator, not a real-time obstacle detector. If you’re flying behind solid objects, LQ drops before RSSI catches up. As we covered in our guide to antenna placement and signal path clearance, even the best RSSI setup can’t save you from a carbon fiber frame blocking the signal path.
Mistake 5: Not testing failsafe at close range before long-range flights.
The best RSSI calibration in the world doesn’t matter if your failsafe settings are wrong. Walk 100 meters away with the quad armed (props off, or held securely), turn off the transmitter, and watch what happens. Does the quad disarm? Does GPS rescue activate? If GPS rescue doesn’t trigger within 1 second of signal loss, your failsafe stage timing is wrong. For detailed failsafe configuration, see our FPV failsafe setup guide covering Stage 1, Stage 2 behavior and landing strategy.
⚠️ 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.
For ELRS pilots who want to maximize range, the Radiomaster Ranger series with true diversity receivers provides simultaneous RSSI and LQ on two independent RF paths. The diversity telemetry gives you a much earlier warning of signal degradation because you can see when one antenna path drops before the other. Available at uavmodel.com.
For a visual guide to RSSI configuration across all receiver protocols, Oscar Liang’s walkthrough is the definitive reference: