Radio and receiver compatibility without guesswork

Identify four names

Write down the radio model, its active RF module, the receiver model and the receiver firmware family. A radio may have an internal module, accept an external module, or both. EdgeTX exposes internal and external RF choices per model; activating the wrong bay or protocol can leave perfectly functional hardware unable to communicate. The receiver's advertised band, such as 2.4 GHz, does not by itself establish compatibility because different control protocols can use the same band.

For ExpressLRS, confirm that both sides are ExpressLRS on the same band and that the firmware major versions agree. The project documentation gives a clear example: 3.1.2 and 3.0.1 can synchronize, while 3.2.0 and 2.4.0 cannot. Integrated SPI receivers add another dependency because the ExpressLRS version is tied to the Betaflight firmware on the flight controller. Read the current binding page for the exact versions rather than copying a procedure from an old video.

Separate binding from model matching

Binding establishes which transmitter and receiver belong together. ExpressLRS supports a unique binding phrase and traditional binding procedures. Its documentation says a phrase is for collision avoidance, not a secret or encryption key. Model Match is an additional guard: it associates a receiver with the receiver number of a selected radio model, helping prevent control with an unintended model profile. Both sides must agree on the Model Match setting.

Consider a pilot with two small quads sharing one unique binding phrase. Without Model Match, selecting either radio model may connect to either bound receiver. With correctly assigned receiver numbers and Model Match, the living-room trainer can refuse the model profile intended for the larger outdoor quad. That does not replace preflight checks, but it makes a wrong-model selection visible. If the ExpressLRS script reports Model Mismatch, diagnose the IDs; do not repeatedly reflash at random.

• Same logo: confirm frequency band and exact RF module anyway.
• Same major firmware: required by current ExpressLRS compatibility guidance.
• Bound: verify live channels, switch assignments and failsafe before considering the job complete.

Prove the whole path with props removed

After binding, connect the flight controller to Betaflight Configurator with every propeller removed. In the Receiver tab, move one control at a time. Roll, pitch, throttle and yaw must move the corresponding bars in the expected direction; otherwise correct the channel map or radio configuration. Check that endpoints and centers are sensible, then operate arm, mode and beeper switches while watching their auxiliary channels. A solid receiver LED alone proves none of this.

Finally, verify flight-controller failsafe using the current Betaflight procedure, still with props off. Betaflight recommends that a receiver send no data on signal loss so the flight controller can detect the loss; it does not recommend receiver-based fixed-value failsafe. Restore the link, confirm the arm switch must return to disarmed, and save a dated note of radio model, receiver, major firmware, binding method and model ID. This modest record turns the next problem from folklore into comparison.