Continuing to update my fleet! Next up is a Flighty Club Phuket 3" with a Cicada x4 30A AIO F4 controller. I guess now it would be considered a "Stack" not an AIO. I have already flashed the FC to BF 4.4.3. I removed the old Frsky RX to install a TBS Nano. I'm not sure what the best way to wire this is, or if I even have a choice. There are not many pads on this FC.
The old Frsky RX signal was connected to the FC's SBUS pad. The TBS Unify Pro 5G8 HV VTX smart audio is connected to the FC's TX6 pad. The problem is I only see one set of UART's on this FC. TX6/RX6.
First option is to tell the TBS Nano to output SBUS on CH1, solder that wire to the FC's SBUS pad, and go from there. But what about that CH2 wire?
Second option is to connect the TBS Nano CH1 and CH2 wires to RX6 and TX6 respectively, Betaflight serial receiver on UART6, and use CRSF. In this case what do I do with the Smart Audio wire from the VTX? Can it piggyback on the TX6 pad with the TBS Nano?
I don't. know the repercussions or viability of either option, but I hate to ask a question without doing a little thinking first!

You can't connect more than one device to a UART so your piggyback suggestion won't work. You also can't use the RX pad of a hardware UART for one device and the TX pad of the same hardware UART for another device.

If you don't care about Betaflight telemetry back to the transmitter, you can either run the Crossfire Nano RX in SBUS mode and use the SBUS pad, or run it in CRSF mode and just connect CH1 to R6 pad. You won't get telemetry with it wired like that but as long as you have the CRSF baud negotiation option switched OFF in Betaflight (it should be OFF by default) then it will work. With the Crossfire nano RX connected to R6, you can then remap the T6 pad to be a SoftSerial connection for SmartAudio. That would would work because the TX pad would no longer be for UART6 so you won't have two different devices connected to the same hardware UART.

If you want full telemetry from the Crossfire Nano RX you will have no option but to use UART6. Depending on how the FC has been built/configured, you might be able to remap the SBUS/PPM pad to be a SoftSerial connection for SmartAudio. Alternatively, if the LED pad isn't being used for anything, that can be remapped to SoftSerial for SmartAudio.

If you want some help with that, say which of the above options you would prefer, then run the "dump", "diff all", and "status" commands in the Betaflight Configurator CLI tab and copy/paste the results back here.

EDIT: Below is the pinout of the Sunrise Cicada F4 AIO FC for reference. This is a rebranded version of the Racerstar StarF4 AIO FC.

@SnowLeopardFPV wrote:

"If you want full telemetry from the Crossfire Nano RX you will have no option but to use UART6. Depending on how the FC has been built/configured, you might be able to remap the SBUS/PPM pad to be a SoftSerial connection for SmartAudio. Alternatively, if the LED pad isn't being used for anything, that can be remapped to SoftSerial for SmartAudio".

I am unsure what "full telemetry" gets me in a simple quad, but I will go for it. To use CRSF. I'll try to use the LED or SBUS pads for SmartAudio.

   

I'll put serial Rx on UART6 and connect the Nano to TX6/RX6.
UART1 will be VTX(TBS Smart Audio) in peripherals and connect the VTX Smart Audio wire to the SBUS pad.

If that doesn't work I'll research the LED pad, there's one on the FC but I don't know how to access it in Betaflight. Is it UART3?

(18-Nov-2023, 06:36 PM)husafreak Wrote: I am unsure what "full telemetry" gets me in a simple quad, but I will go for it. To use CRSF. I'll try to use the LED or SBUS pads for SmartAudio.

Not a huge amount to be honest. You will get LiPo voltage and current draw, but those are probably the only useful additional telemetry items with that particular FC. A lot of people like to configure low voltage audible callouts on their transmitter which you need LiPo voltage telemetry data for.

(18-Nov-2023, 06:36 PM)husafreak Wrote: I'll put serial Rx on UART6 and connect the Nano to TX6/RX6.
UART1 will be VTX(TBS Smart Audio) in peripherals and connect the VTX Smart Audio wire to the SBUS pad.

You won't be able to wire the SmartAudio connection to the SBUS pad because:

1. It's an RX pad, and you need to use a TX pad for SmartAudio.
   
2. It will have in inverter on it.
   

You might be able to disable the inverter in the Betaflight configuration (CLI), but you'll only be able to do that if it has a software configurable inverter.

(18-Nov-2023, 06:36 PM)husafreak Wrote: If that doesn't work I'll research the LED pad, there's one on the FC but I don't know how to access it in Betaflight. Is it UART3?

The LED pad is switched on or off in the Configuration tab (LED_STRIP) but just turning it on or off won't allow it to be used as a SoftSerial connection. To do that you will have to remap appropriate resources in the CLI.

  Phuket dill all preflight.txt (Size: 2.42 KB / Downloads: 23) [attachment=11351][attachment=11351]
  Phuket staus preflight.txt (Size: 595 bytes / Downloads: 13)
  Phuket dump prefight.txt (Size: 26.13 KB / Downloads: 14)

OK quad is ready to fly will full telemetry in the goggles and I do like having total and average cell voltages in the goggles as well as all the link stuff. 

I see what you mean now about transmitting to the VTX. I can only change the VTX settings manually and that is a huge drawback. Changing them via Betaflight does nothing and Smart Audio in the goggles just says offline in SA Status. I'd like to try staying with the CRSF Rx protocol first. How I remap in the CLI is unimportant to me (it's so far over my head) so I'll use either way. Moving the VTX Smart Audio wire to either the SBUS or LED pads is a one minute operation. I'll also need to know which UART to put Smart Audio on in the Ports tab, just generally what to do in Betaflight.

Move the SmartAudio wire from the SBUS pad to the LED pad, then copy/paste the following block of commands into the CLI and press <ENTER>. Once the FC has rebooted, reconnect it to Betaflight Configurator and check that you are getting a "Device ready" status of "Yes" in the Video Transmitter tab. You will need a LiPo connected to the FC when you check that status.

   

I did what you said and it worked perfectly, no surprise there! I wish those CLI commands meant something to me, maybe some day... Now I have full control of the goggles via Betaflight or Smart Audio. I'll just load a preset tune and head to the flying field now

If you're interested, below is a narration for what each of the CLI commands that were specified in my previous post do. Some of the settings that the commands change can also be done directly from the GUI: 

• resource LED_STRIP 1 NONE -> Completely unassign the LED_STRIP resource (it was originally assigned to MCU pin A01).
  
• resource SERIAL_TX 11 A01 -> Assign the SOFTSERIAL1 TX resource to MCU pin A01. Pin A01 on the MCU is connected to the LED pad on the FC board, so that pad is now a connection for SOFTSERIAL1 TX and not for an LED strip anymore.
  
• feature SOFTSERIAL -> Switch on the SoftSerial feature (as also found in the Configuration tab of Betaflight Configurator).
  
• feature TELEMETRY -> Switch on TELEMETRY feature (as also found in the Configuration tab of Betaflight Configurator) so that you get the FC telemetry values sent back to your transmitter such as LiPo voltage.
  
• serial 0 0 115200 57600 0 115200 -> Switch off all options for UART1 (as also found in the Ports tab of Betaflight Configurator).
  
• serial 30 2048 115200 57600 0 115200 -> Switch on TBS SmartAudio for SOFTSERIAL1 (as also found in the Ports tab of Betaflight Configurator).
  
• save -> Save the changed settings and reboot the FC.
  

Cool, that is petty cool, you're just telling the FC what to do almost in plain English.
The little quad flew really well today. Had a blast. I had a little breakthrough when the quad would not arm. After loading the Supafly Freestyle 3/4" tune. Comparing the Betaflight set ups before and after the tune I saw DSHOT had changed from 600 to 300, but every time I tried to save DSHOT600 it would go back to DSHOT300. Then I turned off Bidirectional DShot and now it would stay on DSHOT600. And also arm, and fly. Baby steps!