Your ExpressLRS link works fine at 200 meters, then drops LQ to 30 at 400 meters and you don’t know why. The answer is usually the packet rate-to-telemetry ratio you selected. 500Hz feels instant but burns link budget. 50Hz reaches 30 kilometers but feels like flying through molasses. Here’s how to pick the right settings for every flight scenario.
Packet Rate: How Fast Your Radio Talks to the Receiver
ExpressLRS packet rates range from 25Hz to 1000Hz. Higher numbers mean lower latency but shorter range. The packet rate is the primary factor in both link feel and link budget.
| Packet Rate | Update Interval | Effective Range (100mW) | Latency Feel | Best Use |
|---|---|---|---|---|
| 1000Hz (F1000) | 1.0ms | ~500m | Instant, wired feel | Pro racing, tight courses |
| 500Hz | 2.0ms | ~800m | Near-instant | Freestyle, aggressive flying |
| 250Hz | 4.0ms | ~1.5km | Very responsive | All-around, most pilots |
| 150Hz | 6.7ms | ~3km | Responsive | Cinematic, medium range |
| 50Hz | 20.0ms | ~10km+ | Noticeable delay | Long range, endurance |
| 25Hz | 40.0ms | ~20km+ | Obvious delay | Extreme range, survey |
At 1000Hz, your radio sends 1000 packets per second. Every one of those packets consumes a piece of the link budget. Fewer packets = more energy per packet = further range. The math is straightforward: cut your packet rate in half and you roughly double your range (in ideal conditions).
The latency numbers above are for the RC link only — add ~5-10ms for video latency and another 3-5ms for your FC’s processing loop. At 50Hz you’ll feel a ~30ms total delay between stick movement and quad response. It’s flyable but mushy. At 500Hz, total system latency drops under 10ms and the quad feels telepathic.
Telemetry Ratio: How Much Data Comes Back
ExpressLRS can send telemetry back to your radio — RSSI, LQ, battery voltage, GPS coordinates, altitude. The telemetry ratio determines how many packets are “return” packets vs “control” packets.
The standard ratios:
– 1:2 — one telemetry packet for every two control packets. 33% telemetry duty cycle. Good balance.
– 1:4 — one telemetry for every four control. 20% duty. Max range configuration.
– 1:8 — one telemetry for every eight control. 11% duty. Extreme range, slow updates.
– 1:16 — one telemetry for every sixteen control. 6% duty. Telemetry update every ~300ms at 50Hz.
– 1:32 — nearly telemetry off. 3% duty. Only for absolute max range.
– Std — standard ratio, varies by packet rate. Usually 1:32 at 500Hz, 1:16 at 250Hz.
Lower telemetry ratios mean fewer return packets, which means more of the link budget goes to control. Your radio calls out “telemetry lost” earlier at lower ratios because updates are sparse. This isn’t a failsafe — it just means your radio hasn’t heard from the receiver recently. The control link is still solid.
The Packet Rate × Telemetry Ratio Matrix
Choosing both settings together is where most pilots get confused. Here’s what actually matters:
For racing (0-300m): 500Hz or 1000Hz at Std telemetry. You don’t need telemetry — you need every microsecond of latency gone. The quad is always in sight. If it failsafes, you walk 50 meters.
For freestyle (0-500m): 250Hz or 500Hz at 1:8 or 1:16. You want snappy response with battery voltage telemetry for landing warnings. LQ at these ranges stays above 90.
For cinematic / medium range (500m-2km): 150Hz or 250Hz at 1:4. Smoother flying needs GPS telemetry at reasonable update rates. 1:4 gives you fresh GPS coordinates every ~25ms at 150Hz.
For long range (2km-10km): 50Hz at 1:4 or 1:2. At these distances, every packet matters. Telemetry at 1:2 means you get position updates fast enough to see if the quad is actually coming home during GPS rescue.
For extreme range (10km+): 25Hz at 1:8 or Std. Control is the priority. Telemetry is a nice-to-have. At these ranges you’re running Li-Ion packs with 30+ minute flight times — the quad can cruise home on its own as long as it has a GPS fix.
Dynamic Power: The Third Variable
ExpressLRS 3.x+ includes dynamic power — the transmitter adjusts its output based on signal quality. Set it and forget it, right? Not quite. Dynamic power interacts with packet rate in ways that can hurt you.
At 500Hz with dynamic power, the TX starts at 10mW and ramps up as needed. The problem: by the time RSSI dips enough to trigger a power increase, you’ve already lost dozens of packets. At 500Hz, that’s milliseconds of control loss — you feel it as a micro-glitch.
At 50Hz, dynamic power has time to react. RSSI drops, TX power ramps from 100mW to 250mW within a few packet intervals, and the link stabilizes before you feel anything.
My rule: dynamic power at 250Hz and below, fixed power at 500Hz and above. At 500Hz I lock my TX at 100mW or 250mW depending on the environment. The overhead means I never hit the knee of the power curve. As discussed in our ExpressLRS dynamic power guide, SNR-based auto-power is more nuanced than simple RSSI thresholds.
What Happens When LQ Drops
Link Quality (LQ) is not RSSI. RSSI measures signal strength. LQ measures valid packet percentage — 100 means every packet got through, 50 means half are lost.
At 500Hz, LQ drops from 100 to 90 in a fraction of a second once you exceed the link budget. At 50Hz, LQ degrades gradually — you see it trending down over several seconds and have time to turn back.
The LQ warning thresholds from our failsafe setup guide apply here: warning at 80, critical at 50. At LQ 50, half your stick inputs are lost. The quad won’t failsafe yet (that happens at LQ ~10 with default settings), but control feels inconsistent.
Common Packet Rate Mistakes
Mistake 1: Running 500Hz for everything. 500Hz feels great, but if you’re flying 2 kilometers out, the link budget can’t sustain it. You’ll failsafe at a range where 150Hz would be solid. Match the packet rate to the flight profile, not just “what feels best.”
Mistake 2: Setting telemetry ratio to 1:32 for long range. You need GPS telemetry to navigate home if video cuts out. At 1:32 on 50Hz, telemetry updates every ~640ms. That’s fine for voltage — terrible for GPS coordinates when you’re trying to figure out which way the quad is facing.
Mistake 3: Not testing the packet rate before pushing range. Fly a known 500m course at each packet rate. Note where LQ drops below 90. That’s your effective range for that rate. Then push 100m further and note where LQ hits 50 — that’s your hard limit. These numbers are specific to your hardware, antenna placement, and environment. Generic range tables are starting points.
Mistake 4: Assuming higher TX power fixes a bad packet rate choice. Going from 100mW to 1W doubles your range, roughly. Dropping from 500Hz to 50Hz increases range 10x. Packet rate is a much bigger lever than power output. Choose the right rate first, then adjust power for headroom.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. ExpressLRS operates in the 2.4GHz ISM band and 900MHz band — verify local power limits and frequency allocations. 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.
Packet rate tuning isn’t set-and-forget. I change rates between flying sessions depending on whether I’m racing gates or cruising mountains. The good news: ExpressLRS stores rate and telemetry settings in the receiver, so changing from your radio takes 10 seconds in the Lua script. For proper binding procedures and firmware setup, our ExpressLRS 3.x flashing guide covers the end-to-end workflow.
The HappyModel EP1 Dual TCXO receiver supports full 25Hz-1000Hz packet rates with a true diversity dual-antenna setup, SPI ELRS for sub-5ms latency, and ceramic antenna tuning for reliable long-range performance — available at uavmodel.com.