Just noticed there is not a cc pad on this FC. It looks like R4 is used for camera control? Is that the right CLI code?  Does SA go to the T4 pad? Do I enable something in BF to get SA on T4? Its been a year and a little unsure about this.
(edit) Got the memo that SA needs to be on a different UART like T3.

Camera control works on the R4 pad and yes that is the cli command:

resource camera_control 1 A01

The rest of the camera control settings should work on default but depending on your camera those may need some changes. But try defaults to see if they work first.

For SmartAudio, you need to set the correct TX port you soldered the SA wire to tbs smart audio under peripherals.

Next you need to set up the VTX tables in Betaflight.

Also ensure you power the vtx via the vtx power pad as on this FC if your vtx can take lipo power as it has a vtx power on/off via pinio in the Betaflight mode. If your vtx has specific voltage requirements then do not do this eg some vtx require 5v.

I’ll use the T4 pad as it’s with the rest of my camera wires. Then I just assign R4 to SA in betaflight? I’m using the TBS unify pro32 which will take up to a 6S.

(04-Apr-2021, 05:36 AM)Kevin2112 Wrote: I’ll use the T4 pad as it’s with the rest of my camera wires. Then I just assign R4 to SA in betaflight? I’m using the TBS unify pro32 which will take up to a 6S.

You will need to use the R4 pad (not the t4 pad). The resource assignment will take care of the R4 and assign it as a camera control pin.

In the case of the TBS unify pro32 VTX you can connect it to the VBAT pad if you do not fly more than 6S. 

But note there are 2 vbat pads and the one you need to use is the one shown in the diagram as this has the PINIO assignment that can be used to power off the vtx via a switch on the transmitter.

I have used the T3 pad but you can use the T4 pad for VTX smart audio control.

Attached is my wiring diagram.

Kevin2112, I think you are a little lost with your understanding of things.

SA is a protocol to control the VTX. It is always wired to an UART TX. You can use any UART as long as you have not already used the UART RX for something else. On the port tab, just make sure you select Smartaudio on whichever port you wired it to.

Camera control (not to be confused with C1/C2 camera switching) is a way to control the camera's OSD through BF, instead of using the joystick that comes with the camera. You can also use almost any port for this. But you do need to remap resources. But to get camera control to work, you need to have an inline resistor. In your FC, the manufacturer added the resistor for you on R4, so you don't have to worry about it. Once you remap, there is nothing on the port tab setting you need to change.

The wiring diagram that kafie1980 posted pretty much outline things very clearly.

So you can't use the tx and rx of the same number for different things? Your right I am a bit confused on it. So if I do R4 for OSD then I will need to use a different T like T3 for SA? 
R4 does have a 200 ohm resistor. It looks like T3 is not used for anything yet.

(04-Apr-2021, 10:32 AM)kafie1980 Wrote: You will need to use the R4 pad (not the t4 pad). The resource assignment will take care of the R4 and assign it as a camera control pin.

In the case of the TBS unify pro32 VTX you can connect it to the VBAT pad if you do not fly more than 6S. 

But note there are 2 vbat pads and the one you need to use is the one shown in the diagram as this has the PINIO assignment that can be used to power off the vtx via a switch on the transmitter.

I have used the T3 pad but you can use the T4 pad for VTX smart audio control.

Attached is my wiring diagram.

Nicely done diagram, understand now how to wire!

(09-Apr-2021, 03:10 AM)Kevin2112 Wrote: So if I do R4 for OSD then I will need to use a different T like T3 for SA? 

Correct. You can only use a UART for one purpose with a couple of exceptions. Even if you only use one part of a UART (i.e. the TX pad) for something, you can't use the other side (i.e. the RX pad) for something else unless you remap that pad to SoftSerial.

The following link gives an overview of how the serial configuration works / is configured, along with details of any exceptions / constraints...

https://github.com/betaflight/betaflight.../Serial.md

(09-Apr-2021, 09:47 AM)SnowLeopardFPV Wrote: Correct. You can only use a UART for one purpose with a couple of exceptions. Even if you only use one part of a UART (i.e. the TX pad) for something, you can't use the other side (i.e. the RX pad) for something else unless you remap that pad to SoftSerial.

The following link gives an overview of how the serial configuration works / is configured, along with details of any exceptions / constraints...

https://github.com/betaflight/betaflight.../Serial.md

That is a very in-depth look at it! Explains a lot about where those numbers come from!

(09-Apr-2021, 12:20 PM)Kevin2112 Wrote: That is a very in-depth look at it! Explains a lot about where those numbers come from!

Yes, that document got updated in July and August of last year to include all of the number values that you now see in the document which were previously missing, so at least everything is now in one place. Before July last year it used to look like THIS, so you previously had to go hunting around through different documents and even the source code to find out what the values meant, which was one reason I created the following post...

https://intofpv.com/t-cli-reference-the-serial-command