RadioMaster Pocket Is Bound but Betaflight Shows No Stick Movement

View RadioMaster Pocket ELRS Radio Controller

Featured gear

RadioMaster Pocket ELRS Radio Controller

The RadioMaster Pocket ELRS is a compact EdgeTX FPV radio with Hall-effect gimbals, an internal 2.4 GHz ExpressLRS system, up to 16 channels, and a Nano external module bay. Best for: FPV beginners, simulator…

The RadioMaster Pocket ELRS is a compact EdgeTX FPV radio with Hall-effect gimbals, an internal 2.4 GHz ExpressLRS system, up to 16 channels, and a Nano external module bay.

Best for

Compact EdgeTX transmitter for pilots using 2.4 GHz ExpressLRS who value portability, Hall-effect gimbals,…

Product type

Radio Transmitters

Best for

Compact EdgeTX transmitter for pilots using 2.4 GHz ExpressLRS who value portability, Hall-effect gimbals,…

Product type

FPV Radio Transmitter

View Product Check Price

The steps below apply to a Pocket using ExpressLRS and a Betaflight aircraft. Start by identifying whether the aircraft has a UART-connected receiver or an SPI receiver. Those interfaces need different settings, even when the receiver is built into the flight-controller board.

Match the symptom before changing settings

Trace where movement stops. A moving stick icon on the radio, a connected receiver and moving channels in Betaflight are three different observations. Use this table to choose the next check without changing several layers at once.

1. Confirm the Pocket produces channel output

Check the radio variant first. RadioMaster supplies the Pocket with ELRS or CC2500 internal RF hardware. The manufacturer's Pocket listing identifies the variants. A CC2500 internal module does not become ELRS through a model-setting change.

Select the aircraft's model in EdgeTX. For the Pocket's internal ELRS module, check Internal RF: CRSF and External RF: Off. If your setup uses an external ELRS module, follow that module's configuration instead. The ExpressLRS radio-preparation instructions distinguish those paths.

Open the radio's channel-output monitor. The EdgeTX monochrome-screen guide describes output bars, numerical channel values and the channel/mixer monitor among the main views. Move one stick axis at a time and watch the corresponding output channel, then check the intended switches.

If the stick graphic moves but its output channel does not, inspect the selected model's inputs and mixes before touching the aircraft. A stick source must feed a channel mix to create that channel's output. A simulator model, deleted mix or unintended model selection deserves checking here. Record the actual channel order rather than assuming that a particular channel is throttle.

2. Confirm the ELRS link, then check Model Match

Look for live link information that changes with receiver power, not merely a remembered sensor name. ExpressLRS distinguishes receiver/link telemetry from telemetry originating at the flight controller. Its troubleshooting guide separates bound receivers with basic telemetry from cases that also receive FC data.

If a receiver shows a solid LED without live radio telemetry, consult its documented LED pattern and inspect whether its boot button is held down or boot pads remain bridged. ExpressLRS notes that bootloader mode can be mistaken for a bound receiver. Disconnect power before inspecting or altering wiring. If no RF connection exists, resolve that binding or startup problem first.

When telemetry works but channels do not, check Model Match before replacing hardware. ExpressLRS can connect over the air while withholding control output because the receiver's stored model identity does not match the active model's Receiver number. Its Model Matching guide documents this behavior.

Select the intended aircraft model and compare its Receiver number with the receiver's Model Match setting. If you use Model Match, follow the documented procedure to assign the intended number while connected to that receiver. Power only the aircraft being configured. Do not assume that turning Model Match off on the handset alone clears a stored number on the receiver. Preserve the wrong-model protection you intend to use, then power-cycle and retest.

3. Check receiver power and the two serial wires

A flight controller appearing over USB does not prove its receiver has power. Some boards require aircraft battery power for the receiver supply. Keep propellers removed, use the board's approved power arrangement and limit powered bench time. Provide airflow for a powered video transmitter. ExpressLRS includes these cautions in its receiver preparation and updating instructions.

Before moving wires, disconnect both USB and battery power. Identify the exact receiver, FC model and board revision, and consult their wiring diagrams. For a conventional UART CRSF connection, the ExpressLRS wiring guide specifies these signal directions:

• Receiver TX to FC RX: carries control information toward the flight controller.
• Receiver RX to FC TX: carries flight-controller telemetry back toward the receiver.
• Both FC pads belong to the same free UART: use the board manual to identify the pair.
• Power and ground: use the receiver's specified supply and a common ground. Do not infer voltage from a connector's shape.

For example, a board whose manual identifies RX2 and TX2 as UART2 would use that pair, with receiver TX connected to RX2. This is a labeling example, not a universal UART assignment. Inspect solder joints, plugs and pad labels. An SBUS pad may have hardware inversion; do not treat it as interchangeable with an ordinary UART RX pad. Avoid sharing the receiver UART with another serial peripheral.

4. Match Betaflight and the receiver's output protocol

Save a backup of the existing FC configuration before editing it. For a UART-connected ELRS receiver using CRSF, follow the official FC configuration instructions:

1. In Ports, enable Serial RX on the UART to which the receiver is actually connected. Do not copy a tutorial's UART number.
2. In the receiver settings, select the Serial or serial-based receiver type and CRSF provider. Labels and locations vary with the app and firmware version.
3. Enable telemetry for the CRSF return-data path. Save and reconnect.
4. For the ordinary uninverted, full-duplex connection, inspect get serialrx in the CLI. The documented settings are serialrx_inverted = OFF and serialrx_halfduplex = OFF. Correct a mismatch with the corresponding set command, then save.

These steps do not apply unchanged to an SPI receiver. Betaflight's Receiver Tab guide distinguishes SPI from serial-based receivers. Use the board manufacturer's receiver interface and matching firmware instructions; an integrated receiver can require a different path from a separately wired one.

Also inspect the receiver itself. ExpressLRS supports multiple serial output protocols, selectable on supported receivers through the WebUI or the Lua tool's Other Devices menu. For this ordinary CRSF setup, confirm the receiver outputs CRSF rather than another protocol or an inverted variant. The receiver serial-protocol documentation explains those choices. Setting Betaflight to CRSF cannot convert a different receiver output.

Record the installed versions before considering a flash. The transmitter module and receiver are separate firmware targets; ExpressLRS documents matching major versions in its receiver firmware-version guide. A confirmed RF link is reason to investigate the downstream settings first. Flash only when a specific compatibility or firmware problem has been identified for the exact hardware.

5. Verify every control before moving on

Reconnect with the receiver powered and open Betaflight's Receiver tab. Move roll, pitch, yaw and throttle separately. Each named channel should respond to the intended control, in the intended direction, across its expected range. If values move under the wrong names, correct the channel map to match the radio's output order. Changing the map rearranges received channels; it cannot restore data that never arrives.

Check auxiliary switches as well. Save, power-cycle and repeat the observations. Then verify mode assignments, arming behavior and failsafe using the instructions for your firmware and aircraft, still with propellers removed. Receiver-tab movement establishes control reception; it does not by itself establish flight readiness.

If channels remain still, preserve the facts that distinguish the remaining possibilities: Pocket RF variant, active model, receiver model, FC revision, installed firmware and app versions, receiver power source, both UART wire destinations, and Model Match state. Capture the radio output monitor, Ports page and Receiver page, including what happens when a stick moves. Share the relevant configuration backup with the equipment's support provider, excluding private binding phrases and network settings. A static settings screenshot alone cannot demonstrate a successful control test.

Work from the last observation that passes: moving Pocket outputs, a verified RF connection, then correctly interpreted Betaflight channels. Correct one mismatch and repeat the same check. If the full documented path is correct but controls still fail, use the recorded configuration to investigate a board, receiver or connection fault before buying a replacement.

Last checked: September 9, 2026.