RC Plane Won't Arm? Troubleshooting Signal and Bind Issues

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

You pull the throttle to idle, connect the battery, and the ESC beeps at you like an unhappy smoke alarm. No chime, no motor. Before swapping parts, remember that a plane which will not arm is nearly always doing its job. The ESC or receiver has found something it dislikes and is keeping the motor off on purpose. A twitching servo on the bench is a different matter again, and is not the same thing as the high-speed servo flutter pilots worry about in flight.

This guide is based on manufacturer manuals and documentation (Spektrum, HobbyZone, FrSky, FlySky, Radiolink, Hobbywing and Castle Creations), not on our own flying. ESC tone meanings in particular vary from maker to maker and from model to model, so your own manual outranks any table here.

Bind and arm are two different problems

Binding is the radio link between transmitter and receiver. If it has not happened, the receiver has no control signal at all. Arming is what the ESC does after that link exists: it checks the throttle signal (and, on stabilized receivers, waits for its own initialization) before it lets the motor turn.

A plane can bind perfectly and still refuse to arm. So start with a simple split:

Do bench work with the propeller removed, every time. The Spektrum manuals, the HobbyZone STOL S manual and the Hobbywing manuals all say so in their own words.

Step 1: The boring checks that cause most failures

1. Throttle stick and trim at the bottom. The HobbyZone STOL S manual says it flatly: if you connect the battery while the throttle is not at its lowest position, the ESC will not arm. Its troubleshooting table lists "throttle not at lowest position or throttle trim too high" first, and tells you to reset the stick and trim to their lowest setting.
2. Throttle cut state. Many Spektrum aircraft manuals recommend using throttle cut whenever the aircraft is powered and not in use. With throttle cut on, the motor will not turn. The STOL S manual also says to be sure the stick is at its lowest setting before switching throttle cut off.
3. Throttle channel direction and travel. The STOL S and AR637T+ manuals list a reversed throttle channel and throttle servo travel below 100 percent as causes of "no throttle response while other controls work." They also list a motor disconnected from the ESC.
4. The right model memory. On Spektrum radios with ModelMatch, each model memory has its own code programmed into the receiver during binding. If the system fails to connect, the manual says to check the correct model memory is selected on the transmitter. The DX5e and aircraft modules do not have ModelMatch.
5. Batteries. Both the AR637T+ and the STOL S bind troubleshooting tables list low flight battery or transmitter battery charge as a cause of binding and connection failures. A weak pack can also trip protections once the ESC draws current. For that side of things see the LiPo battery guide and our guide to motors cutting out mid-flight.

Also give stabilized receivers time. The STOL S manual says to keep the aircraft immobile while the SAFE system initializes, and that if it does not finish within about 30 seconds you should disconnect and reconnect the battery. The AR637T+ table says the same, with a 5-second still period after battery connection. A plane picked up and carried during that window is a classic source of "the controls don't move" reports.

Step 2: Fix a bind failure, brand by brand

Spektrum (DSMX and DSM2)

The AR620, AR410 and AR637T+ manuals describe the same procedure:

1. Push and hold the bind button on the receiver while powering it on (or power on and then press the button).
2. Release the button when the orange LED flashes continuously.
3. Put the transmitter in bind mode.
4. A solid orange LED means the bind is complete.

If you use a bind plug, the AR637T+ manual says to remove it after binding, otherwise the receiver goes into bind mode the next time you power up. Its troubleshooting table lists "bind plug left installed" for planes that will not connect after binding.

Other causes the manuals list for binding or connecting failures:

• The transmitter is too close to the aircraft. The AR620 FAQ puts the problem threshold at within 4 feet and says reflective material such as metal or carbon fiber can delay or prevent connection. Move away and try again.
• The aircraft or transmitter is near a large metal object, a wireless source or another transmitter.
• The bind button was not held long enough.
• The transmitter was bound using a different DSM protocol, in which case rebind.

The STOL S has a quirk. Its receiver cycles between DSMX and SLT about every 20 seconds, with a rapid LED flash for DSMX and a slow one for SLT. You hold the transmitter's bind button while powering the transmitter on, and a solid LED means bound. Bind with the throttle stick at the lowest position, because the receiver stores that as the failsafe throttle position. The failsafe guide explains why a rebind is also a failsafe event.

FrSky (ACCESS and ACCST D16)

These are two different procedures, and the ETHOS manual warns that the mode must match what the receiver supports or the model will not bind.

ACCESS has two phases.

1. Register the receiver. Select Register in the radio, hold the receiver's bind button while powering the receiver, and wait for the red and green LEDs. The radio reports the receiver as connected, you finish the registration, and the receiver goes off.
2. Bind. With the receiver off and ACCESS selected, choose Bind for the receiver, power the receiver up without touching its F/S bind button, pick the receiver from the list on the screen and wait for the success message.

Afterwards, power both down and up again. A green LED on and a red LED off means the receiver is linked.

ACCST D16 uses the Bind option in the radio and puts the receiver in bind mode, generally by holding its Failsafe button during power-up. The red and green LEDs come on; the green goes off and the red flashes when binding completes. Tap OK, power cycle the receiver, and check for green on and red off.

FrSky's warning is worth repeating: do not perform the binding operation with an electric motor connected or an internal combustion engine running. The Model ID also matters. The ETHOS manual says the receiver only responds to the Model ID it was bound to, and that the ID changes when a model is cloned. A model copy that no longer connects is a bind problem, not a hardware one.

FlySky (AFHDS 2A)

The FS-i6X manual says transmitter and receiver ship pre-bound. If you use another transmitter or receiver:

1. Connect the supplied bind cable to the B/VCC port on the receiver.
2. Insert power into any other port.
3. Hold the bind key while powering on the transmitter.
4. Remove the power and bind cable, then connect the power cable to B/VCC.
5. Check servo operation, and repeat from the start if anything is wrong.

The FS-iA6B manual describes the same idea: the receiver LED flashes quickly while in binding state and goes solid when the bind succeeds. Then unplug the binding cable and check the functions.

The other FlySky trap is protocol. The FS-i6X manual lists AFHDS receivers (R9B, R6B, R6C, GR3E, GR3F) and AFHDS 2A receivers (A3, A6, X6, iA4B, iA6, iA6B, iA10, iA10B), and says the protocol is switched under System Setup, RX setup, RF Standard. A transmitter set to the wrong standard will not bind to the receiver, however many times you try. If you need a spare receiver for testing, a FlySky FS-iA6B is an AFHDS 2A example, though its Amazon listing showed as unavailable at the time of checking.

Radiolink

The AT9S Pro manual tells you to put the transmitter and receiver about 50 centimeters apart, because a much closer distance may cause signal jamming. Power on the transmitter and the receiver, long-press the ID SET button on the receiver for more than a second until the red or purple LED flashes, and a steady LED means bound. Radiolink says its transmitters are only compatible with Radiolink receivers. The Radiolink R9DS is the receiver that manual's binding example uses.

Step 3: Fix an arming failure when the receiver is linked

If the LED says linked and servos respond but the motor stays quiet, you are in the ESC's territory.

Notice what is missing from that table: a single universal rule for beep patterns. Different ESCs use different tones. Castle's Phoenix Edge HV card, for instance, lists distinct tone patterns for low voltage cutoff, over temperature, excessive load, start fail, radio glitch, motor anomaly and over-current, and tells you to look them up for your own ESC. The beep is evidence, not a verdict.

Calibration mode is not a fault

Some ESCs enter programming mode when you power up with the throttle high. The Avian manual describes the calibration sequence: with the transmitter throttle at full, connect the battery, wait for three ascending tones and two short tones, then move the throttle to the low position within five seconds. If more than five seconds pass, the ESC enters programming mode instead. Hobbywing's XRotor manuals use a similar flow, with the stick moved to the bottom within 3 seconds after two short beeps. If your ESC is playing tones you do not recognize after power-up with a high throttle, you may simply have entered a setup routine. Unplug, lower the throttle, and start again.

When a normal start-up works, the Avian manual says the number of tones indicates that the ESC is in operation, the detected LiPo cell count and that it is ready to use. Hobbywing's XRotor manual describes a long beep about one second after battery connection as the armed signal.

Protections that need the stick brought back to idle

Several ESC protections latch until the throttle returns to the bottom. The Avian manual says that if start-up fails with the throttle above 20 percent, the stick must be moved back to the bottom before the ESC allows a restart. Hobbywing's XRotor manuals describe overload and start-up protections that behave similarly. If the motor stops after a stumble and will not restart, lower the stick fully and try again before concluding anything is broken. Also look for a propeller binding against something, since a blocked motor can trip start-up protection.

Step 4: Isolate the fault in three tests

When the checks above find nothing, split the chain into transmitter, receiver and ESC.

1. Bypass the receiver with a servo tester. A 3-mode RC servo tester plugs into the ESC and sends a known throttle signal. The Avian manual notes the ESC works with a conventional servo (PWM) signal from any common source, so a tester is a fair test of the ESC and motor. If the ESC arms on the tester but not through the receiver, the problem is in the radio chain. If it still will not arm, look at the ESC, motor and wiring. Props off, always.
2. Check the pack and the wiring with a multimeter. A basic digital multimeter shows battery voltage and checks continuity on leads and connectors, which finds failures that look like signal problems. The wiring diagram guide covers channel routing and common wiring mistakes.
3. Swap in a known-good receiver. If a receiver never reaches bind mode, a spare of the right protocol settles the question quickly. A Spektrum AR410 4-channel sport receiver is a basic DSMX example, listed at Horizon as in stock, with a 3.5 to 9 V voltage range and four servo ports. Make sure the replacement supports what your plane needs; if you rely on stabilization, the flight controller guide explains what the gyro receivers do on power-up.

Do these in order and you will land on one component instead of a pile of parts.

Step 5: Rebind, recalibrate, retest

Once you have fixed the cause, do not just power up and fly.

• Rebind from scratch and remove any bind plug.
• Re-calibrate the ESC throttle range if your ESC supports it.
• Check the control directions and, on Spektrum aircraft, the failsafe positions that the bind stored. The manuals say failsafe positions are set during binding.
• Run a range check at the field, as every maker manual recommends.

For the radio side, the transmitter and receiver guide and the ESC guide cover matching hardware from the start.

Mistakes that waste time

• Treating a beeping ESC as a broken ESC. The beep is the diagnosis.
• Forcing an arm. Raising trim or endpoints to dodge a "not at low" warning risks the propeller starting the instant the ESC accepts the signal. Fix the cause instead.
• Bench-testing with the propeller on. Every maker says to remove it.
• Binding while a motor is connected. FrSky warns against it.
• Mixing protocols. ACCST and ACCESS procedures differ, and FlySky AFHDS and AFHDS 2A receivers need the matching RF standard.
• Leaving a bind plug installed. The AR637T+ manual says to remove it so the receiver does not enter bind mode on the next power-up.
• Binding too close to the aircraft. Spektrum gives about 4 feet as a problem distance and Radiolink recommends about 50 centimeters, so follow your system's guidance.

FAQ