You glance down mid-flight and the RSSI value on your OSD reads 0% — or worse, it’s stuck at 99% no matter how far out you fly. You just lost the one metric that keeps you from flying into a failsafe blind. Getting RSSI working correctly is a 10-minute fix once you understand which of the three signal paths your receiver actually uses.
RSSI Signal Sources: Pick the Right One
Your flight controller can pull RSSI from three independent sources. Using the wrong one — or having two active simultaneously — is what causes the frozen 99% or flat 0% you see in the OSD.
1. AUX Channel (Analog RSSI) — The receiver outputs RSSI as a PWM value on a spare channel. This is how FrSky ACCST and older receivers did it. You wire a physical signal wire from the receiver’s RSSI pad to an ADC-capable pin on the flight controller, or you set the RSSI channel in Betaflight’s Receiver tab to the AUX channel where your receiver injects the value.
2. RC Link Packet Rate (Digital RSSI) — Modern serial protocols — CRSF (Crossfire/ELRS), Ghost, and Tracer — embed RSSI directly in the serial data stream. No extra wire, no AUX channel assignment. Betaflight reads it from the protocol stack automatically. This is the cleanest method and what you should use if your gear supports it.
3. ADC (Analog Voltage RSSI) — Rare these days. Some analog receivers output RSSI as a 0-3.3V analog voltage on a dedicated pad. You wire that pad to an ADC input on the flight controller and configure the scale and offset in Betaflight CLI. Skip this unless you’re flying truly ancient hardware.
How to Determine What Your Receiver Uses
Power your quad on the bench (props off). Open Betaflight Configurator and go to the Receiver tab. Watch the channel values. If you see channel 16 (or AUX12) fluctuating as you move your transmitter closer and farther from the receiver, your receiver is injecting RSSI on that channel. Set Betaflight’s RSSI Channel dropdown to that AUX channel.
If you see no channel movement but your receiver is serial-connected (CRSF/ELRS/Tracer), your RSSI comes through the protocol pipeline. Set RSSI Channel to “Disabled” — Betaflight automatically reads the link quality field from the serial protocol. Setting it to a channel while using a serial protocol creates the frozen-99% bug: the protocol reports valid link quality, but the AUX channel you set also has a value, and they fight.
Setting RSSI Channel in Betaflight
Go to the Configuration tab → Receiver section → find the RSSI Channel dropdown.
- CRSF (ELRS/Crossfire/Tracer): Set to Disabled. Betaflight reads RSSI dBm and link quality from the serial protocol automatically. This is non-negotiable. If you set it to AUX8 or AUX12, you get the frozen-value bug.
- SBUS/IBUS with OpenTX/EdgeTX injected RSSI: Determine which channel your radio sends RSSI on (commonly CH8, CH12, or CH16 depending on mixer configuration), then select it from the dropdown.
- F.Port (single-wire): Usually channel 16. Verify in the Receiver tab by watching for RSSI movement.
After setting the channel (or disabling it for serial), click Save and Reboot. Go back to the Receiver tab and verify the RSSI value at the top of the screen changes when you move your transmitter away from the quad.
ExpressLRS Specific: RSSI dBm vs Link Quality
ELRS receivers report two distinct values:
– RSSI dBm: Raw signal strength. Typically ranges from -30 dBm (transmitter right next to receiver) to -110 dBm (edge of range).
– Link Quality (LQ): Percentage of valid packets received. 100% = perfect, drops below 80% when you’re pushing range limits.
Betaflight displays RSSI as a 0-100% scale by default. ELRS maps the dBm range to this percentage. The mapping is not linear — you might see 80% RSSI even when link quality is still 100% because ELRS uses LoRa modulation, which maintains perfect packet delivery well into weak signal territory. This is why RSSI isn’t the best metric for ELRS. Link quality matters more.
To display both in your OSD, use the “Link Quality” element in the OSD tab — it reads directly from the CRSF telemetry stream. Many pilots run RSSI in the top corner for a quick glance and link quality next to it as the actual go/no-go gauge.
OSD RSSI Configuration
Open the OSD tab in Betaflight Configurator. Drag the RSSI Value element onto your layout. While you’re there, also drag on Link Quality (under the Telemetry group) if you’re on CRSF/ELRS.
Warning Thresholds That Actually Help
The default RSSI warning thresholds in Betaflight are too conservative for modern links:
– Warning (default 20%): Set this to the point where you want a visual nudge. For analog/ACCST, 45%. For ELRS, 35% RSSI (link quality should still be 95%+).
– Critical: The point where you need to turn back now. Analog: 38%. ELRS: 25% RSSI or 70% link quality — whichever triggers first.
Enable “Warn RSSI” in the OSD tab’s Alarms section. You’ll get a flashing “RSSI LOW” or “LINK QUALITY LOW” overlay on the video feed when you cross the threshold. This is more useful than an audio alert because you’re wearing goggles — you see it instantly.
RSSI Parameter Comparison Table
| Configuration | RSSI Channel Setting | Signal Source | When to Use | Common Pitfall |
|---|---|---|---|---|
| CRSF (ELRS/Crossfire) | Disabled | Serial protocol data | Always for CRSF receivers | Setting it to AUX channel causes frozen 99% |
| SBUS + OpenTX injection | AUX8/AUX12/AUX16 | Transmitter mixes RSSI onto spare channel | FrSky ACCST, FlySky with OpenTX | Must match exactly what EdgeTX outputs |
| F.Port (single wire) | AUX16 typically | Receiver firmware-injected | FrSky F.Port receivers | Verify channel number in Receiver tab |
| Analog ADC | Disabled, configured via CLI | Direct RSSI pad voltage | Legacy analog VTX systems | Requires CLI scale/offset calibration |
Common Mistakes & How to Avoid Them
Mistake 1: Setting RSSI Channel to an AUX when using CRSF/ELRS. The serial protocol already delivers RSSI and link quality. Setting an additional AUX channel creates a conflict — Betaflight reads both sources and typically displays the frozen AUX value instead of the live protocol data. Fix: Set RSSI Channel to Disabled. That’s it.
Mistake 2: Confusing RSSI percentage with link quality. On ELRS, you can have 50% RSSI and 100% link quality simultaneously. Panicking at 50% RSSI and turning back when you still have a perfect link wastes flight time and battery. Display both metrics in your OSD and learn your system’s actual edge-of-range numbers empirically — fly a known course with the blackbox logging enabled and review when LQ actually starts dropping.
Mistake 3: Wrong AUX channel number when using SBUS injection. OpenTX/EdgeTX has two places where RSSI is configured: the Model Setup → Telemetry page (sets the source), and the Mixer page (assigns it to a channel). If you change the mixer channel but don’t update Betaflight’s RSSI Channel dropdown, the OSD gets noise. Verify with the slider test: power up, move TX away, watch the Receiver tab — the RSSI channel should show movement.
Mistake 4: Forgetting to set OSD warning thresholds after re-flashing. Betaflight full chip erase resets RSSI warnings to default. After any firmware update, immediately restore your warning values. Nothing worse than flying out on a new tune and not realizing your critical RSSI alert is set to 10% instead of your usual 40%.
⚠️ 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.
Your RSSI setup feeds directly into your failsafe configuration — when RSSI drops to zero, the failsafe stage 1 and stage 2 timers start counting. As we covered in our complete failsafe configuration guide, the guard time setting determines how quickly your quad reacts to a lost signal. If RSSI reads incorrectly, your failsafe activates at the wrong moment — either too late (crash) or too early (unnecessary drop).
Check the RSSI value against expected range before every session. If your quad normally shows 99% at 10 meters and one day it shows 50%, you have a hardware problem — likely a damaged receiver antenna. We covered antenna selection and placement in our antenna placement and mounting guide — a kinked or pinched U.FL connector can halve your signal strength without any visible damage to the antenna itself.
A reliable RSSI display starts with a flight controller that reads serial protocol data cleanly. The SpeedyBee F405 V4 stack handles CRSF telemetry parsing properly and has four full UARTs, so you won’t run out of ports when you add GPS, VTX control, and receiver all on the same board.