How to bind your betaflight SPI receiver via CLI (Frsky, Flysky)

How to bind your betaflight SPI receiver via CLI (Frsky, Flysky)

Many tiny whoop flight controllers that have a built in SPI receiver.  And given the small size it can be a real pain to press the bind button each time you need to bind your RX to it.  However with betaflight you can bind your RX via the CLI using a simple bind command.

This is applicable to flight controllers with built in SPI receivers, such as the Happymodel crazybee series, Betaflight whoop flight controllers etc..

Simple enter in the command below on the CLI and press enter, and the RX should enter bind mode.  You will be able to tell as teh LED on your FC will change.

For Betaflight 4.1+

  1. bind_rx

For Betaflight 4.0+

  1. bind_rx_spi

For Betaflight 3.5+

  1. frsky_bind
Once you enter this command press enter, and you should receive a reply that says binding...  and the LED on your flight controller should change.  YOu can then bind/pair your radio to the FC.  Reboot everything and you are good to go.



Other things to check

If the above does not work, please check your betaflight version and double check the CLI command.  Also double check your receiver settings are set correctly in the betaflight configuration tab.
Select "SPI RX support" for the receiver mode.
Your SPI Bus receiver provider setting is essentially the protocol the SPI receiver uses. You'll need to set this depending on the firmware and protocol your radio uses. This may sound complex, but it's rather simple, we've created a comprehensive guide for FrSky radios below:
If your radio uses:                                                                  
ACCST D16 protocol, EU (LBT) firmware
Then your SPI Bus receiver provider setting should be:
FRSKY_X_LBT
If your radio uses:                              
ACCST D16 protocol, non-EU (FCC) firmware
Then your SPI Bus receiver provider setting should be:
FRSKY_X
Finally, if your radio uses                  
ACCST D8 protocol, non-EU (FCC) firmware
Then your SPI Bus receiver provider setting should be:
FRSKY_D

ACCESS radio protocols WILL NOT WORK with SPI receivers - most ACCESS radios at least have the option to use ACCST D16, which you should select on the radio to ensure you can bind successfully.

And make sure you have selected the correct protocol according to your receiver/radio


    • Related Articles

    • ELRS Binding — Quick Troubleshooting Guide

      When this applies: Your ExpressLRS (ELRS) receiver won't bind to your transmitter, or the receiver LED doesn't match what you expect after powering on. Step 1: Check the LED pattern The receiver LED tells you exactly what state it's in. Match yours ...
    • UMT 10" FPV Long Range Analog PD Drone CLI Config/Setting

      The CLI dump for Betaflight 4.5 is attached to this article. RX is setup as CRSF (ELRS receiver) and connected by default to UART 3:
    • ELRS Binding - Quick Troubleshooting Guide

      When this applies Your ELRS receiver won't bind to your transmitter, or binds but the flight controller doesn't respond to stick inputs. Symptoms Receiver LED is off or staying solid (not blinking) LED blinks but binding never completes TX and RX ...
    • iFlight BNF FPV Quadcopter Factory CLI Dumps

      Iflight drones (such as Nazgul series) come pre-configured, requiring users to only set flight modes and bind the receiver as needed. However, there may be times when you need to update the firmware and apply new factory defaults. This guide will ...
    • Binding Your Happymodel Mobula7 1S ELRS Drone to Radio Pocket Master

      This article will guide you through the process of binding your Happymodel Mobula7 1S ELRS 75mm BNF Brushless Whoop (2.4GHz) drone to your Radio Pocket Master transmitter. Binding is the process of linking your drone and transmitter so they can ...