Locate the missing handoff
Separate radio-to-receiver communication from receiver-to-flight-controller communication. Follow the indicators and documentation for each device. A receiver showing a link does not establish that the flight controller is configured to receive or interpret its output.
Use the correct precautions for powered bench work. Keep propellers off for setup checks as required by the equipment. Establish a controlled observation before you make a change.
Verify the radio side
Confirm the selected radio model, the intended RF system, supported band, and firmware compatibility. For ExpressLRS, check the documented binding method and any model-matching configuration. Do not assume a connection should exist simply because two devices share a general product-family name.
Use the project documentation for the exact hardware and firmware. Keep binding phrases and other private setup information out of public screenshots.
Verify the controller side
Check the flight controller’s documented receiver connection and interface configuration. Use the board’s own pinout and instructions. Do not move wiring to a different connector because an unrelated build guide calls it a convenient port.
Observe the receiver/channel interface in the supported software. Check that the correct sticks and switches produce the expected channel movements. If some channels work and others do not, that is a different clue from having no channel data at all.
Make one observation count
Write a simple chain: radio model, RF link indication, receiver output requirements, controller configuration, observed channels. Mark the first point where your evidence stops. That is where the next question belongs.
If you cannot verify a wiring or configuration step, stop and resolve it using the hardware documentation or qualified help. Reflashing several devices at once replaces one unresolved connection with several new variables.
MAKE IT USEFUL
Your next small job.
Make a five-line control-path record and mark the first point that has not been verified.
Go straight to the source.
These official resources support the next step. Hardware, firmware, and local requirements can differ.