I am having trouble getting my drones to work, I have bound all of my receivers, set failsafes, I have fixed any CLI flag reports in beta flight, motors spin in BetaFlight, values go up and down in "receiver" tab in BetaFlight when I move the sticks. I have set up throttle cut on sf switch, which works in BetaFlight (or doesn't for the throttle when deactivated) when I move the sticks on the receiver. However, all the drones won't respond when trying to fly.

This happens with the TBS Sixty9 attached to the Kopis2 even though there are both solid green lights on the TBS Transmitter module and the Sixty9 receiver. The same happens with the TBS Transmitter module and the TBS CrossFire Nano receiver attached to my Darwin BabyApe 2, both have solid green lights, seems to be working in BetaFlight, but not a sausage in real life. So I tried using my Archer ACCESS GR8 receiver, however, first I plugged in a power supply so that I could bind it. Bound fine with solid green light and the receiver recognised in the X20s. However when plugging into the BabyApe's flight controller, no lights on the GR8.

The TBS Nano Transmitter wont fit into the lite bay on the back properly. I have to push it down hard to make connection with the pins. I am thinking of creating some pins and sockets to fix this in permanently with the spare shell that comes with the TBS Crossfire.

All the kit is new, I have:

• FrSky X20s Transmitter
  
  • GR8 Access Receiver
    
  • TBS Crossfire Nano Transmitter TX
    
• Darwin Baby Ape 2
  • With TBS Crossfire Nano RX
    
• Holybro Kopis 2 5"
  • With TBS Sixty9 RX/VTX
    

What am I doing wrong? Is there an arm switch that I don't know about?

I'm not entirely sure what you mean when you say "I have set up throttle cut on sf switch". Do you mean that you've configured the "SF" switch on your X20S to output values on an auxiliary channel and that you have configured the ARM mode in Betaflight to react to that particular AUX channel, or have you done something funky in Ethos on your FrSky X20S transmitter to achieve "throttle cut"?

With the FC plugged into your computer via a USB cable, when you flip the arming switch on your transmitter to the ARM position, do you see any Arming Disable Flags in the Info section on the right-hand side of the Setup tab in Betaflight Configurator?

Can you please run the "dump", "diff all", and "status" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

(27-Jan-2024, 10:36 AM)SnowLeopardFPV Wrote: I'm not entirely sure what you mean when you say "I have set up throttle cut on sf switch". Do you mean that you've configured the "SF" switch on your X20S to output values on an auxiliary channel and that you have configured the ARM mode in Betaflight to react to that particular AUX channel, or have you done something funky in Ethos on your FrSky X20S transmitter to achieve "throttle cut"?

With the FC plugged into your computer via a USB cable, when you flip the arming switch on your transmitter to the ARM position, do you see any Arming Disable Flags in the Info section on the right-hand side of the Setup tab in Betaflight Configurator?

Can you please run the "dump", "diff all", and "status" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

I have set the SF switch to have throttle at 0% when off. That's it, not sure how to set an arming switch, so I have not configured the arm mode in betaflight.

Even if i set it to aux 1 I cant find a switch to move between the 2 lines.

Arming flags are as below. Which indicate the receiver isn't talking to the flight controller. but I have tested all wires with a multimeter and are ok. Even with the other drone that I used to test it, it had the same flags, without the RXLOSS, but it still wouldn't spin the motors on command from the transmitter.





Dump and Diff all files attached.

Few red lines in there.

Cheers for this.

In the mode, if you select AUTO and have your radio/rx powered, then you can flip the switch you want to use and configurator will automatically detect the movement and select the respective AUX channel for you. If nothing gets selected, then check your radio model setup in the MIXES tabs (for Open/EdgeTX) and add mappings for the switches you want to use. AUX channels are usually channel 5 and up.