← All field guides

Systems / 2 MIN READ

Binding is an introduction, not the whole relationship.

A receiver can recognize a radio and still fail to deliver the channels you expect. Work through the entire control path.

01

Match the equipment first

Identify the radio module and receiver, their control system, supported band, hardware target, and firmware requirements. “ExpressLRS” is an ecosystem, not proof that every combination of devices and firmware is ready to communicate without checking.

Use the project documentation for the hardware you actually own. Record the current firmware version before you change it. A random target selected because its name looks close is not a useful shortcut.

02

Understand the binding method

ExpressLRS supports documented binding workflows, including binding phrases. Its traditional binding procedure has its own conditions. Choose the documented method that fits your setup, rather than trying several incompatible procedures in succession.

Treat a binding phrase as private setup information. Do not copy someone else’s example phrase or publish yours in a troubleshooting screenshot. Keep your notes somewhere you can retrieve without putting device secrets into a public post.

03

Check model matching deliberately

Model matching can restrict which model configuration is allowed to connect to a receiver. That is useful when configured intentionally and confusing when you forget that it is enabled. Check the radio model and receiver configuration against the official instructions.

Once the control link is established, verify the flight controller’s receiver configuration and the displayed channel response. Confirm that the intended controls move the intended channels. A connected receiver icon is not the end of that check.

04

Save a known-good state

Write down what worked: the radio model, hardware identifiers, firmware versions, binding method, and relevant configuration choices. Keep secrets out of shared copies. Your future self should not need to reconstruct the setup from memory.

If a change breaks the link, compare it to that record and investigate one layer at a time. Reflashing everything is a powerful way to erase evidence while feeling productive.

MAKE IT USEFUL

Your next small job.

Create a private control-link record: hardware, firmware, band, model configuration, and the official setup page.

Go straight to the source.

These official resources support the next step. Hardware, firmware, and local requirements can differ.

KEEP THE THREAD GOING

The next useful read.

All guides ↗