All the tutorials for this FC mention how to set up using radios that I don't have.  I have an FlySky (Turnigy i10) transmitter with an iA6C  S-Bus receiver.  I have the receiver connected to the S-Bus pin on the FC.  The receiver is bound to the transmitter.  But when I go to the RADIO tab in BetaFlight Configurator, I get nothing. 

There is nothing in the PORTS tab that mentions S-BUS. 

How do I get this working?  My oscilloscope shows that serial data is coming out of the S-Bus pin on the receiver.
I have read mentions of an inverter needed, but I think that is with FrSKY, which is a different brand.

You don't mention which version of the board you are using. For the V4 board, the SBUS pad is connected to UART2. So in the ports tab set SERIAL_RX to enabled on UART 2, and in the receiver tab select SERIAL (VIA UART) and SBUS. If you have a different board you can check the manual.

However SBUS pad is for an inverted SBUS signal (ie Frsky/DJI), I don't know if your receiver is the same. If it is a non-inverted SBUS signal, then you can try to solder it to the RX2 pad instead, with the same settings.

My board is a V4. I updated the board to the latest settings and now, the BetaFlight Configurator only shows the USB port - no UARTS!  


What next?  How do I get the ports back?

I have built dozens of fliers using Ardupilot, but BetaFlight is a new experience!

If by update the board you mean flashing BF, that is NOT recommended unless you know what you're doing in BF or have a specific compatibility issue.

If none of the ports are showing up, then likely you have flashed the wrong target. Make sure you select SPEEDYBEEF405V4 and if it came with BF4.3 then seriously consider going back as 4.4 adds other complexities. You can refer to the manual for flashing firmware
https://store-fhxxhuiq8q.mybigcommerce.c...ual_EN.pdf

If you are getting no ports showing up in the Ports tab then in 99% of cases it means that you haven't applied custom default settings after flashing the firmware. If you run the "dump" command in the CLI I'm going to bet that all of the resources at the top are set to "NONE". If that is the case then re-flash the firmware again and when you first connect and are prompted to do so, click on the "Apply Custom Defaults" button...



EDIT: When flashing the firmware, don't forget to include SBUS for the Radio Protocol under the Build Configuration settings.

(19-Feb-2024, 04:42 PM)SnowLeopardFPV Wrote: EDIT: When flashing the firmware, don't forget to include SBUS for the Radio Protocol under the Build Configuration settings.

That is if you are installing 4.4 and then if you plan to use GPS, LED, PINIO, SERVO, or even OSD?, VTX? you would have to include those as well. If the board has a custom baro chip, I believe you need to add that too. Not sure if you need to do anything for the SD Logger? 
For 4.3 it is just so much easier, don't have to worry about any of that, it is all there by default.

I have successfully reflashed the FW several times.  But I have two issues:  There is no option for SPEEDYBEE in the firmware flasher.  Ony "STM32F405" and a whole lot of other options, none of them are SpeedyBee.  I have been loading    betaflight_4.42_STM32F405.hex

Also, I cannot find any option "Load Custom Defaults".  That doesn't show up anywhere.  Can you please tell me how to get that tab?

I have tried both the "Firmware Flasher" in the left margin of the BetaFlight Configurator, and also the "UPDATE FIRMWARE".  I can find no place where it tells me to apply custom defaults - before OR after flashing.

For the SpeedyBee F405 V4 FC you need to flash the SPEEDYBEEF405V4 Betaflight target to it. After you do that, when you connect for the first time you will then get the "Apply Custom Defaults" prompt.

What version of BF Configurator are you using? You should probably upgrade it to 10.9.

I had Configurator V. 10.5.  That was the major problem.  In the older version, it did not ask for custom defaults.  Now I have to get SBus working.