Oscar Liang explains radio-link health for safer FPV racing

Why radio-link health is a race-day edge

Oscar Liang’s May 30, 2026 tutorial makes a simple but brutal point: if you wait for a failsafe to tell you the link is bad, you are already late. In FPV racing, the difference between a clean lap and a dead quad can be a few gates, a wall, or one bad angle behind an obstacle, so the real advantage is knowing when the radio link is slipping before the aircraft drops out of the fight.

That is why the article treats LQ, RSSI, and SNR as race tools, not abstract telemetry. Each one answers a different question, and together they help you decide whether to keep pushing, back off, or blame the environment instead of the quad.

LQ is the number that matters when you want to finish the lap

ExpressLRS’s official guidance is clear: there are two main signal-health measures, RSSI and LQI, and if you only have one, LQI is the one to trust. That matters because LQ is tied to packet success, which makes it the best day-to-day read on whether the control link is actually holding together.

Betaflight agrees on the practical side. For Crossfire hardware, it recommends LQ over RSSI, and its setup guide tells pilots to use only the metric their radio system supports, whether that is Link Quality, RSNR, RSSI Value, or RSSI dBm Value. In race terms, LQ is the warning light that tells you the conversation with the quad is getting choppy, even if the motors still feel locked in.

RSSI dBm tells you how close you are to the cliff

RSSI is often misunderstood because the percentage view feels neat and reassuring. But the more useful version is RSSI in dBm, because it shows how much signal is actually reaching the receiver and whether it is still above the sensitivity limit needed to be understood.

That is where Oscar Liang’s framing gets useful for racers: RSSI dBm is less about comfort and more about the edge of the map. If the number is sliding toward the receiver’s sensitivity threshold, you are not in a “maybe it’s fine” situation. You are in a back-off situation, especially if you are about to dive behind a structure, hold a long straight, or stay low in a noisy part of the field.

Older Crossfire manual text gives that idea some hard numbers, noting that RSSI can fall to around -130 dBm before the link breaks up. That does not mean you should race anywhere near that edge; it means the metric is showing you how much room you have left before the system starts to fall apart.

SNR is the clue when the field, not the quad, is the problem

SNR, or signal-to-noise ratio, matters because it helps explain whether the radio is fighting distance, interference, or both. Liang’s tutorial treats it as part of the same diagnostic picture, which is exactly how racers should use it: not as a score to admire, but as a clue about why the link feels softer in one section of the course than another.

That distinction matters on race day. If the link looks worse only when you are clipped behind obstacles or buried in a bad angle, the issue may be the course geometry, not a broken antenna or a bad receiver. If LQ and RSSI dBm are both sliding, then the smart move is usually to stop pretending the line is still clean.

Set the warnings before the gate drop

The best part of Oscar Liang’s advice is that it is operational, not philosophical. He pushes pilots to make the link visible in Betaflight OSD, set alarms, and bench-test before takeoff, so the radio stops being a mystery during the heat of a race.

ExpressLRS’s pre-flight guidance is especially practical:

• Put Link Quality and RSSI dBm on the OSD.
• Disable RSSI Channel and RSSI_ADC in the receiver tab.
• Set the RSSI dBm warning in CLI, with `osd_rssi_dbm_alarm = -100` as the example.
• Use an RSSI dBm alarm that is 5 to 10 dB above the sensitivity shown for the packet rate you chose.
• Start the LQ alarm at 60.

That is not busywork. It is how you turn signal data into a mid-race decision instead of a post-crash autopsy.

Why this matters more now in modern FPV

ExpressLRS now supports both 900 MHz and 2.4 GHz hardware and advertises packet rates up to 1000 Hz, which is another way of saying the ecosystem is built for speed, low latency, and fast decision-making. Team BlackSheep describes Crossfire the same way from a different angle, calling it an adaptive long-range R/C link with low latency and telemetry.

That combination raises the stakes. The faster and more responsive the system gets, the more expensive it is to misunderstand the warning signs. A pilot who still treats RSSI percentage as the whole story is racing with the wrong dashboard. A pilot who reads LQ first, checks RSSI dBm for the cliff, and uses SNR to understand the noise floor is racing with a real edge.

The race-day call, stripped down

Here is the clean version. If LQ starts dropping, the link is losing packets and the risk is rising. If RSSI dBm is trending toward the sensitivity threshold, you are running out of margin. If SNR looks ugly in one part of the course, the problem may be the environment around the quad, not the quad itself.

That is the real value of Liang’s tutorial. It does not just define radio terms. It changes how you fly the lap. The racer who can see the warning before the fail-safe has already made the most important pass of the day: the one that keeps the quad in the air.