Your ELRS packet rate is the single most impactful setting you probably haven’t touched since flashing. Most pilots flash the default 500Hz and never look back — but 500Hz is a compromise that’s optimal for neither racing nor long-range. At 1000Hz, your control latency drops by 40% compared to 500Hz. At 50Hz with a 1:32 telemetry ratio, your effective receiver sensitivity improves by 9dB — roughly doubling your usable range.
The packet rate isn’t a “set and forget” parameter. It’s a situational tool that should change based on what you’re flying and where. Here’s how to optimize it.
Packet Rate Fundamentals
ExpressLRS transmits control data as LoRa packets at one of seven defined rates. The rate determines:
- Packet interval: How often the transmitter sends a control frame
- LoRa spreading factor: How the data is encoded over the air (higher SF = more range, less speed)
- Telemetry slot availability: How often the receiver can send telemetry data back
| Packet Rate | Interval | Spreading Factor | Range (estimated LoS) | Best For |
|---|---|---|---|---|
| 50Hz | 20ms | SF9, BW125 | 30km+ | Extreme long-range |
| 150Hz | 6.67ms | SF8, BW250 | 15-20km | Mid-range cruising |
| 250Hz | 4ms | SF7, BW500 | 8-12km | Freestyle at moderate range |
| 500Hz | 2ms | SF6, BW500 | 3-5km | Default, freestyle, light long-range |
| 333Hz Full | 3ms | Hybrid | 5-8km | FLRC sub-mode, balance |
| 1000Hz Full | 1ms | Hybrid | 2-3km | Racing, high-speed proximity |
| D500 | 2ms | DVDA | 3-5km | Diversity dual-band mode |
The Latency-Range Tradeoff
Lower packet rates use higher spreading factors. At SF9 (50Hz), each bit is spread across more LoRa chirps, which means the receiver can recover the signal at significantly lower RSSI. At SF6 (500Hz), fewer chirps per bit mean faster transmission but the signal-to-noise threshold is higher — the link drops at a stronger RSSI.
The practical difference: at 500Hz, your link starts dropping packets around -105dBm RSSI and failsafe triggers around -112dBm. At 50Hz, packets stay clean down to -117dBm and failsafe doesn’t trigger until roughly -124dBm. That 12dB difference translates to roughly double the range in open air.
Full-Res Mode: 333Hz and 1000Hz
The “Full” rates (333Hz Full, 1000Hz Full) use a hybrid LoRa/FLRC modulation scheme that packs more data into each packet. The key feature: full 10-bit or 11-bit channel resolution instead of the CRSF-standard 10-bit at all channels. This matters if you run very high Betaflight rates (1000+ deg/s) where 10-bit resolution creates visible stepping. At 1000Hz Full, stick-to-output latency drops to roughly 3-4ms — about half of the 500Hz mode’s 7-8ms.
The cost is range: FLRC modulation has a higher SNR threshold than pure LoRa. Expect 30-40% less range at 1000Hz Full compared to 500Hz.
Telemetry Ratio Configuration
The telemetry ratio sets how many control packets are sent before one telemetry slot is allocated. This ratio directly impacts your OSD data refresh rate and the resolution of your RSSI/LQ readings.
| Telemetry Ratio | Control Packets per Telemetry Slot | Telemetry Update Rate at 500Hz | RSSI/LQ Resolution | Best For |
|---|---|---|---|---|
| 1:2 | 1 out of 2 | 250Hz | High | Racing (need fast LQ updates) |
| 1:4 | 1 out of 4 | 125Hz | Good | Freestyle (default) |
| 1:8 | 1 out of 8 | 62.5Hz | Moderate | Mid-range cruising |
| 1:16 | 1 out of 16 | 31.25Hz | Low | Light long-range |
| 1:32 | 1 out of 32 | 15.6Hz | Minimal | Extreme long-range |
| Std | Dynamic | Varies | Dynamic | General use |
A lower ratio (1:2) gives faster telemetry updates at the cost of slightly reduced control link budget — each telemetry slot is time not spent sending a control packet. For racing, the fast LQ update (250Hz) helps you spot link degradation before it affects control. For long-range at 50Hz, a 1:32 ratio means you get a telemetry update roughly every 640ms — your OSD numbers will be “behind” by about half a second, but the control link benefits from maximum time-on-air.
Dynamic Power + Telemetry Ratio
When Dynamic Power is enabled (and it should be, always), the transmitter adjusts output power based on received telemetry. If telemetry updates are too infrequent (e.g., 1:32 at 50Hz), the transmitter’s power adjustment lags behind the actual link condition. For dynamic power to work well, keep the telemetry update rate above 10Hz. At 50Hz with a 1:32 ratio, you’re at 1.56 telemetry updates per second — too slow for dynamic power to react to a sudden obstruction. At these extreme ratios, consider setting a fixed power level (100mW or 250mW depending on planned range) instead of relying on dynamic power.
Packet Rate Selection by Flying Style
Racing (250Hz / 500Hz / 1000Hz Full)
For racing, latency matters more than range. Use 500Hz for most courses and 1000Hz Full if you can feel the difference (some pilots can, many can’t below 900 deg/s rates). At race ranges (<500m), link budget is never the limiting factor — even at 1000Hz Full, your LQ will stay at 100 throughout the heat.
When switching to 1000Hz Full, set telemetry ratio to 1:2. At this rate, you actually want the fast telemetry feedback. If your LQ dips below 90 at any point in the course, you have an antenna placement problem, not a packet rate problem.
Freestyle (500Hz default)
500Hz is the sweet spot for freestyle. At typical freestyle ranges (bandos within 300m, open field within 1km), the latency is low enough for crisp stick response and the link budget is sufficient for flying behind concrete and steel. Set telemetry ratio to 1:4 — your OSD LQ updates 125 times per second, which is fast enough to catch a link degradation during a power loop behind a building.
If you fly abandoned factories with thick concrete walls, drop to 250Hz. The extra link budget at the lower rate helps punch through attenuation, and the 4ms packet interval (vs 2ms at 500Hz) is still imperceptible for the slower stick movements of bandos.
Mid-Range Cruising (150Hz / 250Hz)
For mountain surfing and 3-8km flights, 150Hz is the default. At 3km, 500Hz starts showing its range limits and you’ll see LQ dips below 80 on antenna nulls. At 150Hz with SF8, LQ stays pegged at 100 through 5km of clear air. Telemetry ratio 1:8 gives useful OSD data without sacrificing too much airtime.
Long-Range (50Hz)
For 10km+ flights, 50Hz with 1:32 telemetry ratio is the only game. The 20ms packet interval means your control link has 100ms of latency (5 packets buffered, plus transmission time), which is noticeable but completely acceptable for the gentle coordinated turns of long-range cruise flight. You would never freestyle at 50Hz — the latency makes tight maneuvers feel disconnected.
One critical note: at 50Hz, the failsafe timeout (how long the receiver waits without a valid packet before declaring failsafe) should be increased from the default 1 second to 2 seconds. A single missed packet at 50Hz represents 20ms of lost data — well within the receiver’s ability to interpolate — but at a 1-second failsafe timeout, you only need 50 consecutive lost packets. In marginal link conditions, that can happen faster than the link can recover. A 2-second timeout (100 missed packets) gives the link room to bounce back.
Practical Configuration Steps
Step 1: Determine your primary flying style and expected maximum range.
Step 2: Select the packet rate from the table above based on your range requirement.
Step 3: Set telemetry ratio. Lower (1:2, 1:4) for proximity flying, higher (1:16, 1:32) for long-range.
Step 4: Set failsafe timeout. 1 second for rates 150Hz and above, 2 seconds for 50Hz.
Step 5: Enable dynamic power for all rates except 50Hz with 1:32 telemetry ratio. At 50Hz, set fixed power based on planned range (100mW for <15km, 250mW for 15-25km, 500mW+ for 25km+).
Step 6: Verify LQ stays above 85 throughout a test flight at your expected range. If LQ drops below 85, drop one packet rate level.
Common Mistakes & What Most Pilots Get Wrong
1. Running 1000Hz on a long-range build “because the radio supports it.” Packet rate is a link budget tradeoff, not a spec sheet number. Pushing 1000Hz on a 7-inch cruiser reduces your usable range by 60% with zero perceptible latency benefit at cruise speeds. Match the rate to the mission.
2. Over-optimizing telemetry ratio for OSD data rate. The telemetry data in your OSD is informative, not critical. You don’t need RSSI updating at 250Hz when you’re 8km out — you need the airtime those telemetry slots are consuming. At long-range, sacrifice OSD update rate for control link robustness.
3. Leaving failsafe timeout at 1 second for 50Hz long-range. This is the most common long-range loss mechanism I see in crash analysis threads. At 50Hz, link recovery after a temporary obstruction (flying behind a ridgeline for 2-3 seconds) is normal. A 1-second failsafe timeout triggers GPS rescue before the link has a chance to recover, and GPS rescue with a failsafe-triggered climb is when things go wrong — the climb increases distance from home, potentially worsens the obstruction, and burns pack capacity. A 2-second timeout lets the link self-heal.
4. Disabling dynamic power to “save transmitter battery.” Dynamic power at 500Hz with 1:4 telemetry saves transmitter battery compared to a fixed 250mW output, because the transmitter spends 80%+ of its time at 10-25mW. Disabling it forces full power constantly — that burns your radio battery faster, not slower.
5. Choosing packet rate based on what “sounds fast.” I’ve met pilots running 1000Hz Full on 7-inch builds with 800 deg/s rates who couldn’t feel the difference from 500Hz in a blind test. The latency difference between 1ms (1000Hz) and 2ms (500Hz) is below human perception threshold for most pilots at sub-1000 deg/s rates. Meanwhile they’re giving up 40% of their range. Match the rate to your actual flying, not the marketing spec.
⚠️ Regulatory Notice: ExpressLRS operates in the 2.4GHz ISM band (and 900MHz for 900MHz variants). Transmitter power output is regulated by your local authority — in the US, the FCC limits 2.4GHz FHSS devices to 1W (30dBm) conducted output at the antenna port. The EU (ETSI) limits 2.4GHz devices to 100mW (20dBm) EIRP. Always verify your transmitter’s compliance with your region’s 2026 radio regulations. Some countries restrict the use of 900MHz ELRS (868/915MHz) to licensed amateur radio operators. Check your local band plan before operating 900MHz variants.
For the full ELRS ecosystem, our ELRS Binding and Receiver Setup Guide covers binding phrases, model match, and wireless flashing. Our ELRS Antenna Tuning Guide addresses the antenna-side link budget optimization. And if you’re comparing ELRS against other protocols, our Crossfire vs ExpressLRS comparison has the link budget and latency benchmarks.
A reliable ELRS link starts with a receiver that pulls clean RSSI and maintains lock through 3-4 seconds of obstruction. The Happymodel EP1 Dual TCXO receiver’s temperature-compensated crystal oscillator holds frequency lock within ±1ppm across a 60°C temperature swing — that means the receiver doesn’t drift off-frequency when your quad heats up during a long flight, and the link doesn’t drop during the thermal transition from cold startup to cruise temperature.