Binding a Radio: Protocols, Failsafe at Bind Time, and Range Checks
What binding actually does, why the stick positions at bind time become your failsafe, the protocol table that explains why a same-brand receiver won't bind, and how to range check before you trust it.
Updated Jul 22, 2026 · RC Crash Crew
Binding is how your transmitter and your receiver agree that they belong to each other. Until they have, your radio is not talking to your model — and after a bad bind, it may be talking to it in a way you did not intend.
It is a two-minute job that gets skipped, half-done, or done with the wrong protocol, and it is behind a large share of "my car just drove off on its own" stories. This covers what binding actually does, the failsafe that gets set at the same moment, why a receiver that looks compatible will not bind, and how to range check before you trust it.
What binding actually does
On 2.4 GHz, dozens of radios can run in the same field without interfering. That works because each transmitter has a unique ID, and binding is the moment a receiver memorizes that ID.
After binding, the receiver ignores every other transmitter on the band. That is the safety property: nobody else's radio can drive your model, and yours cannot drive theirs.
It also means an unbound or badly bound receiver is not "a bit unreliable" — it is a model with no reliable control link at all.
⚠️ Before you touch anything: disconnect the motor
Bind with the motor disconnected, or the pinion off, or the model up on a stand with the wheels clear.
Binding involves powering up the receiver while the transmitter is doing something unusual, and there is a window where outputs can twitch. A twitch at full throttle with the wheels on the ground is how people get hurt and how bodies get destroyed. For an airplane or a quad, an unexpected prop spin-up at arm's length is worse than that.
This costs ten seconds. Do it every time.
The general procedure
The exact steps vary by brand — your manual is the authority — but nearly every 2.4 GHz system follows the same shape:
- Select the right model memory on the transmitter first. Binding writes to whichever model slot is active. Bind on the wrong one and you have just overwritten a different model's setup, or you will later switch models and lose the link.
- Set the transmitter's controls where you want the failsafe to be — see the next section. Throttle off, brakes neutral, surfaces centered.
- Put the receiver into bind mode. Usually a bind plug in a specific port, or a button held while power is applied. Its LED will flash in a particular pattern.
- Put the transmitter into bind mode — a menu entry, or a button held at power-on.
- Wait for the LED to go solid. Solid means bound. Still flashing means it did not take.
- Remove the bind plug if your system uses one, then power everything off and back on. This is the step most often skipped, and it matters: it proves the binding was written to memory rather than only being live in that session.
- Check the controls move the right way, then range check.
The failsafe is set at bind time — this is the important part
On a great many systems, the stick and trim positions at the moment of binding become the failsafe positions. If the receiver loses signal, that is where the outputs go.
Bind with the throttle held open and you have configured your model to drive away at speed when it loses signal.
So: throttle at neutral or full brake, steering centered, and for aircraft whatever your manual specifies — then bind.
Not every system works this way. Some set failsafe in a menu instead, and some let you re-set it after binding without re-binding. There is a full guide on this site dedicated to failsafe, including how it differs by brand. Read the failsafe guide as well as this one — knowing how to bind but not what your failsafe is set to leaves the important half undone.
Test it. Bind, then with the model safely restrained and the motor disconnected, switch the transmitter off and watch what the outputs do. That is your failsafe. If you have never watched it happen, you do not know what it is.
Why a receiver that "should work" will not bind
This is the single most common binding failure, and it is almost never a fault — it is a protocol mismatch.
A 2.4 GHz receiver must speak the same protocol as the transmitter, not merely the same frequency band. Same brand is not enough; brands run several incompatible protocols, often at the same time.
| Brand | Protocols you will encounter |
|---|---|
| Spektrum | DSM2, DSMX |
| Futaba | FASST, FASSTest, FHSS, S-FHSS, T-FHSS |
| FrSky | ACCST (D8 / D16), ACCESS |
| Sanwa / Airtronics | FH2, FH3, FH4, FH5 |
| Flysky | AFHDS, AFHDS 2A, AFHDS 3 |
| Traxxas | TQi |
⚠️ Check the exact protocol on both the transmitter and the receiver before buying either. A receiver from the right brand, in the right band, of the right generation, can still be the wrong protocol — and it will simply never bind, with no error message explaining why.
Many transmitters can be *switched* between protocols in a menu (a Futaba set to FASST will not bind an S-FHSS receiver until you change it). Some can be updated by firmware to add one. Check the menu before assuming the hardware is wrong.
Range check — the step that finds the problem on the ground
Every serious radio has a range check mode that deliberately reduces transmitter power, so you can simulate a long-distance link while standing a short distance away.
How to do it:
- Motor disconnected, or the model held by someone else, or securely restrained.
- Enter range check mode on the transmitter.
- Walk away — your manual gives the distance for your system; around 30 paces is the common figure.
- Work the controls through their full travel and watch the model. Everything should respond smoothly, with no stutter, no delay and no glitching.
- Walk a circle at that distance, and turn the model to different orientations. Antenna position matters, and a link that is fine one way round can be marginal another.
- Exit range check mode. Do not fly or drive while still in it.
If it glitches at reduced power at 30 paces, it will fail at full power at distance. Find out here, on the ground.
Do this after any change to the receiver, its antennas, its mounting position, or the model's bodywork — especially anything that adds carbon fiber or metal near the antennas, both of which block 2.4 GHz badly.
Antennas — the free reliability upgrade
More binding-adjacent problems are caused by antenna installation than by the radio gear itself.
- Do not cut, coil, bend sharply or shorten the antenna. The length is part of the tuning.
- The thin end section is the active part. Keep that section straight.
- On a two-antenna receiver, position them at roughly 90 degrees to each other. That is the entire point of having two: whichever orientation the model ends up in, one antenna is well placed.
- Keep antennas away from metal, carbon fiber, motors, ESC power wires and battery packs.
- Route them outside a metal or carbon chassis, in the plastic antenna tubes provided.
- On a boat, keep the antenna above the waterline. Water blocks 2.4 GHz very effectively.
When it will not bind
| Symptom | Most likely cause |
|---|---|
| Receiver LED never changes at all | No power to the receiver, or a dead BEC / bad connection |
| LED flashes forever, never goes solid | Protocol mismatch, or transmitter not actually in bind mode |
| Binds, then loses it after power cycle | Bind plug left in, or the bind was never written — repeat and remove the plug |
| Binds, but the wrong model responds | Wrong model memory selected on the transmitter |
| Works on the bench, glitches at distance | Antenna routing, or a receiver buried in carbon / metal |
| Was fine, suddenly will not bind | Try a different receiver and a different model memory to isolate which side failed |
| Servos move but reversed | Not a binding fault — servo reversing in the transmitter menu |
Isolating a fault: the useful question is always *which side is broken?* Bind a known-good receiver to the suspect transmitter, and the suspect receiver to a known-good transmitter. Two tests, and you know which box to replace.
When you must re-bind
- A new or replacement receiver.
- After a firmware update to either the transmitter or the receiver.
- Adding a satellite receiver on systems that use them.
- Moving a receiver to a different model memory.
- Some systems, after a factory reset of the model memory.
You do not normally need to re-bind after changing a battery, changing servos, or reprogramming an ESC.
The pre-run check, every time
Binding correctly once is not the same as being safe today. Before every session:
- Transmitter on first, model on second. Reverse that order and an unbound receiver may see nothing but noise.
- Right model memory selected? Check the screen.
- Transmitter battery — check it. A radio browning out mid-run is a failsafe event with your hands on the controls.
- Controls move the correct way and reach full travel without binding against anything.
- Model off first, transmitter off last, at the end.
That order — radio on first, off last — is the oldest rule in the hobby and it exists for exactly this reason.