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

    • 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 ...

    • R/C Receiver Troubleshooting Guide

      This is a general guide to help direct you to check some of the common causes of issues customers have with their R/C receivers. Please check the information below and if you have checked the list below and still have an issue please contact us with ...

    • How to install/Flash Betaflight Firmware (GUI or DFU Mode)

      This is a quick guide that will walk you through the process of flashing betaflight firmware onto your flight controller What is a "Firmware Target" or "HEX File" in this context? Betaflight firmware is made to run on many different boards. So, it is ...

    • BetaFlight Resource Mapping Guide

      As manufacturers are stuffing more and more features into flight controllers, we are increasingly seeing boards that have fewer pins available for accessories. The result is lost capabilities, such as: Not enough UART input/outputs Inability to fly ...

    • Loading CLI Defaults onto Your Betaflight Flight Controller/Drone: A Step-by-Step Guide

      Important things to note when using CLI Dumps/Diff When using CLI dumps, there are several important things to keep in mind: Always make sure the version of Betaflight firmware on your board is the same version as that on the CLI Dump file. While you ...