ELRS 4.1.0 · REVIEWED JULY 2026FPV bench · Connect
Make the control link explain itself
ExpressLRS is dependable when every layer agrees. Hardware band, firmware generation, bind identity, Model Match, UART wiring, packet rate, and Betaflight receiver settings form one chain; a green receiver LED proves only part of it.
Start at the physical layer
A bind problem and a UART problem are not the same problem.
Answer the two compatibility questions first, then name the actual symptom. The diagnostic keeps you from reflashing a receiver when the real fault is Model Match, crossed UART wires, or a damaged antenna.
Link diagnostic
Name the failure before changing firmware.
Identify the hardware before troubleshooting behavior.
- 01Read the device information in the ExpressLRS Lua script, receiver Web UI, product label, or manufacturer target listing. Do not guess the band or flash a generic target.
Never change packet rate in flight. ExpressLRS documents that the change forces a disconnect.
The complete signal chain
Five layers must agree before the sticks reach the flight controller.
- 01
Radio model
The selected model memory and receiver number
- 02
TX module
2.4 GHz or supported 900 MHz hardware plus firmware
- 03
Receiver
Matching band, major version, bind identity, and antenna
- 04
CRSF UART
Receiver TX to FC RX, receiver RX to FC TX
- 05
Betaflight
Serial RX, CRSF, live channels, modes, and OSD
Packet rate is a system choice
Faster is not automatically stronger, safer, or better configured.
Packet rate changes latency, sensitivity, telemetry timing, and the Betaflight RC Link preset you should use. Pick a supported rate for the aircraft and radio, apply the matching preset, then prove link health. Never change packet rate while flying; ExpressLRS documents that doing so forces a disconnect.
- LQ
- Valid packets received, not a generic signal-strength percentage
- RSSI dBm
- Received power compared with the sensitivity limit for the selected rate
- Dynamic power
- Raises or lowers transmit power from link conditions and configured maximum

Before-first-flight proof
Binding is complete only when the control link, flight controller, OSD, and failsafe all tell the same story.
- 01
Set ARM on AUX1 and verify the armed state reaches the intended high channel value.
- 02
Display Link Quality and RSSI dBm in the OSD instead of relying on legacy RSSI percentage.
- 03
Run the official low-power one-meter bench test with antennas attached and correctly oriented.
- 04
Remove props, turn the transmitter off, and prove Betaflight enters its configured failsafe behavior.
Next bench station
Carry the proven control link into the flight controller.
Official source ledger
Verify the version before copying the setting.
Reviewed July 22, 2026. Firmware interfaces and defaults move; these links are the authority for the current release.