ExpressLRS is already the dominant radio link in FPV — but most pilots only scratch the surface. They bind a receiver, set a packet rate, and call it done. Yet ELRS packs a suite of advanced features that eliminate the USB cable dance, stream full MAVLink telemetry to your ground station, and even let your VRX talk directly to your TX module. If you are still pulling receivers out of your quad to flash firmware, or if you want INAV telemetry on your Radiomaster screen, this guide is for you.
WiFi Firmware Flashing: Cut the USB Cable
Every ExpressLRS receiver since version 2.0 ships with a WiFi access point mode. Power the receiver (plug in a LiPo), wait 60 seconds, and it broadcasts its own WiFi network named ExpressLRS RX with the password expresslrs. Connect with your phone or laptop, open a browser to 10.0.0.1, and you get a full web interface for uploading firmware — no USB cable, no FTDI adapter, no desoldering.
The workflow replaces the old USB passthrough method entirely:
- Build your firmware in the ELRS Configurator (select target, binding phrase, regulatory domain, packet rates)
- Click “Build” — the configurator compiles and downloads a firmware.bin file
- Power your receiver (or TX module) and wait for the WiFi AP to appear
- Connect, browse to 10.0.0.1, upload firmware.bin, and click Update
- The device reboots with new firmware — total elapsed time under 90 seconds
The same WiFi workflow works for TX modules too. A Radiomaster Ranger, Happymodel ES24TX, or BetaFPV SuperG module enters WiFi mode when powered without a handset connection. For internal-module radios like the Radiomaster Boxer or TX16S, you enable WiFi from the Lua script under WiFi Connectivity → Enable WiFi, then follow the same 10.0.0.1 upload path.
Pitfall: If the web interface shows “Update Failed” or hangs, your browser may be caching the old page. Hard-refresh (Ctrl+Shift+R) or use incognito mode. Also, the receiver only stays in WiFi mode for about 60 seconds after power-on — if you miss the window, power-cycle and try again.
Backpack: Wireless VRX Integration
The ELRS Backpack is one of the most underrated features in the ecosystem. It is a secondary ESP8285 chip available on most newer TX modules (Radiomaster Ranger series, BetaFPV SuperG, Happymodel Gemini) that communicates over WiFi — not with your computer, but with your video receiver. When your VRX (goggles or ground station module) supports the Backpack protocol, your TX module can send it the current VTx channel and pit mode status in real time.
Why this matters: in a multi-pilot race or event, you can set your quad to a specific VTx channel, and your goggles automatically tune to that channel without you touching a single button. The TX module bridges the RC link and the video link. Supported VRx hardware includes:
- HDZero VRX (native support via WiFi backpack mode)
- RapidFire / TBS Fusion modules (via ESP32 backpack mod or RapidFire WiFi firmware)
- Walksnail VRX (community firmware available)
- DIY ESP32 backpack boards connected to any analog module
To enable Backpack, flash your TX module with the Backpack option selected in the ELRS Configurator. The backpack’s WiFi SSID appears as ExpressLRS TX Backpack. Connect your VRX to this network, and channel synchronization happens automatically whenever you power on or change VTx channels via the Lua script.
MAVLink Telemetry: Full Flight Controller Data on Your Radio
Standard CRSF telemetry gives you basic data: RSSI, link quality, battery voltage, GPS coordinates. But if you run INAV or ArduPilot, you want the full picture: altitude, heading, airspeed, waypoint status, flight mode, satellite count, home arrow — all on your handset screen. ELRS delivers this through MAVLink-over-CRSF.
Setup steps:
- Flash your ELRS TX and RX with the MAVLink option enabled in Configurator (under “Other Options”)
- In INAV/ArduPilot, set the serial port connected to your ELRS receiver to MAVLink protocol (not CRSF — the receiver handles the conversion to CRSF framing for the radio link)
- Set the MAVLink baud rate. ELRS 3.x recommends 115200 baud for MAVLink
- On the RX side, set the serial protocol to MAVLink via the Lua script or web UI
- On your EdgeTX/OpenTX radio, go to the Telemetry screen and discover new sensors — you should see altitude, heading, flight mode, and GPS data populate automatically
Packet rate tradeoff: MAVLink telemetry frames are larger than CRSF telemetry. At 150Hz or 250Hz packet rates, there is not enough airtime for both RC data and full MAVLink telemetry. ELRS 3.x drops the effective MAVLink telemetry rate at higher packet rates. For reliable MAVLink with long-range aircraft, run 50Hz or 100Hz Full packet rate. The RC link still feels responsive (20ms or 10ms update), and telemetry flows at a usable rate.
What’s New in ExpressLRS 3.x (2025–2026)
The 3.x firmware branch introduced major architectural changes that every pilot should understand, even if you stay on stable:
| Feature | ELRS 2.x | ELRS 3.x |
|---|---|---|
| Packet rates | Fixed set (50/150/250/500Hz) | Expanded: Full, FullRes, and mode-switched variants |
| Binding phrase | 6+ characters | Now requires 6+ characters; UID-based binding as fallback |
| FLRC modes | Not available | FLRC 500Hz / 1000Hz for racing (lowest latency) |
| Diversity RX | Antenna switching | Gemini (true dual-frequency diversity RX) support |
| WiFi AP | Standard | Improved stability, faster firmware uploads |
| MAVLink | Experimental | Full support, configurable baud, improved reliability |
FLRC (Faster LoRa Rate Coding) at 1000Hz is a game-changer for racers who previously needed TBS Tracer for sub-millisecond latency. FLRC tightens the LoRa coding rate significantly, trading some link budget for raw speed. In a race environment with clean RF, 1000Hz FLRC delivers control latency on par with the fastest links available — all over standard ELRS hardware with no additional cost.
Practical Configurations for Different Flying Styles
| Flying Style | Packet Rate | Telemetry Ratio | Switch Mode | MAVLink |
|---|---|---|---|---|
| Racing | FLRC 1000Hz or 500Hz | 1:128 (Off) | 8ch | No |
| Freestyle | 250Hz or 150Hz | 1:32 | 8ch or 16ch/2 | No |
| Long-range / INAV | 100Hz Full or 50Hz | 1:8 or 1:16 | Full Res 16ch | Yes |
| Cinematic / slow cruise | 50Hz | 1:4 | Full Res 16ch | Yes |
Common Pitfalls and Debugging
- WiFi AP not appearing: Receiver must be powered for 60+ seconds without binding to a TX. If your TX is on and bound, the receiver skips WiFi mode. Power the quad alone.
- MAVLink telemetry missing: Check that your FC serial port baud matches the ELRS RX MAVLink baud setting (both must be 115200 or both must be 57600). Mismatch is the #1 cause.
- Backpack not connecting: Older TX modules lack the ESP8285 backpack chip. Check your module specs — if it was manufactured before 2023, it probably does not have backpack hardware.
- FLRC link dropping at close range: FLRC at 1000Hz has reduced link budget. It is designed for a race track (sub-500m). Do not use FLRC for long range — switch to 100Hz Full when you need distance.
- Multiple receivers on same binding phrase: This is a feature, not a bug — but it means you must power only one quad at a time unless you want both to arm simultaneously.
ExpressLRS’s advanced feature set puts it on par with or ahead of commercial systems costing ten times as much. The WiFi workflow alone saves hours of frustration over a season of racing. MAVLink integration turns a $20 receiver into a full telemetry downlink. And Backpack makes frequency management at events genuinely seamless. If you have not explored beyond basic binding and rate switching, pick one feature — WiFi flashing is the easiest entry point — and try it on your next bench session.