Good evening,
I'm having a problem with the smart audio of the TBS unify pro32 nano v1.1.
I' m using vtx tab by TBS official site and tx4 as UART.
Below some photos a video link to understand if I unlocked good the vtx(now I have blue and red light solid) and with 6 orange light I have 3 blue light so SA mode is activated(I think).
I'm using the last BF release and a diatone f722 20x20.
Thanks in advance

So what exactly is the problem?

Are you unable to change vtx settings via Betaflight?

Do you get video with OSD?

the issue is that the pro32 nano uses smartaudio v2.1 essentially which has to be setup in betaflight to support it. there are some guides that talk about this. Also, you have to make sure you unlock the VTX.

"Using any Smart Audio V2.1 compatible flight controller simply connect the Smart Audio data pin to a free
and supported port on your FC (see pinout below).
For Betaflight users, you can then configure the connected port in Betaflight configurator to Smart Audio
V2.1 protocol. Ideally you make sure to get a Betaflight firmware which supports the new SA2.1 (Betaflight
>=V3.5.6) rather than the older SA2.0. This way you get access to the new power levels of SA2.1."

The vtx unlocking is done using the button modes of the vtx and instructions are in the manual at the TBS website.

Betaflight already supports SA2.1. Any version after 4.1 should be compatible.

You will need the VTX tables for the vtx and Oscar has this on his website along with instructions: https://oscarliang.com/smartaudio-tramp-...vtxtables/

(23-Jun-2021, 04:32 AM)kafie1980 Wrote: The vtx unlocking is done using the button modes of the vtx and instructions are in the manual at the TBS website.

Betaflight already supports SA2.1. Any version after 4.1 should be compatible.

You will need the VTX tables for the vtx and Oscar has this on his website along with instructions: https://oscarliang.com/smartaudio-tramp-...vtxtables/

sorry for the delay in replayng you.
thanks for your  support.

now i'm running the vtx tables as TBS manual provide.
attached you can see my CLI.

On sensor tab page,when i plug the battery and flag only debug sensor i have no value....i'm thinking it's not a vtx problem,maybe a fc problem.....
i saw an old tread on this forum and Mr SnowLeopardFPV  suggested a pulldown on the UART3 TX pin by running the following CLI commands : resource PULLDOWN 1 B10
probably in my case it is a different tx(i'm using smartaudio connection on tx 4)...can you explain me please what is mean pulldow command?

thanks in advance

(26-Jun-2021, 10:10 PM)SBLAUS Wrote: sorry for the delay in replayng you.
thanks for your  support.

now i'm running the vtx tables as TBS manual provide.
attached you can see my CLI.

On sensor tab page,when i plug the battery and flag only debug sensor i have no value....i'm thinking it's not a vtx problem,maybe a fc problem.....
i saw an old tread on this forum and Mr SnowLeopardFPV  suggested a pulldown on the UART3 TX pin by running the following CLI commands : resource PULLDOWN 1 B10
probably in my case it is a different tx(i'm using smartaudio connection on tx 4)...can you explain me please what is mean pulldow command?

thanks in advance

The pull down stuff with Smart Audio (LITE version) was with the TBS UNIFY NANO version along time ago and has been fixed: https://github.com/betaflight/betaflight/issues/5329

The UNIFY Pro32 NANO does not suffer from this issue.

What Flight Controller are you using?

Looking at your dump file the VTX tables look correct and the ports are configured to "2048 = TBS SmartAudio" on UART 4:

Quote:serial 3 2048 115200 57600 0 115200

(27-Jun-2021, 10:38 AM)kafie1980 Wrote: The pull down stuff with Smart Audio (LITE version) was with the TBS UNIFY NANO version along time ago and has been fixed: https://github.com/betaflight/betaflight/issues/5329

The UNIFY Pro32 NANO does not suffer from this issue.

What Flight Controller are you using?

Hi, I'm using a Mamba 722 basic MK3 mini(20x20) 
Thanks

Sorry, I just read you mentioned in an earlier post that you were using a Mamba F722 Basic.

I can see you are using a TBS VTX/RX mounting board. Can you test for connectivity between the SA pin on the Pro32 Nano to the SA pad on the mounting board and then also between the SA pad on the mounting board and the TX4 pas on your FC.

(27-Jun-2021, 10:57 AM)kafie1980 Wrote: Sorry, I just read you mentioned in an earlier post that you were using a Mamba F722 Basic.

I can see you are using a TBS VTX/RX mounting board. Can you test for connectivity between the SA pin on the Pro32 Nano to the SA pad on the mounting board and then also between the SA pad on the mounting board and the TX4 pas on your FC.

I will try asap because no sensor value on sensor tab is very unusual if all wirings are good

(27-Jun-2021, 11:18 AM)SBLAUS Wrote: I will try asap because no sensor value on sensor tab is very unusual if all wirings are good

If the continuity tests are good then something else is at play here.

Any chance you have pitmode turned on via the modes tab?

Perhaps a quick factory reset might help too.

Also check via Betaflight OSD in your goggles for VTX settings to see if you have the Op Mode set to Race instead of Free.

(27-Jun-2021, 01:15 PM)kafie1980 Wrote: If the continuity tests are good then something else is at play here.

Any chance you have pitmode turned on via the modes tab?

Perhaps a quick factory reset might help too.

Also check via Betaflight OSD in your goggles for VTX settings to see if you have the Op Mode set to Race instead of Free.

The problem was the TBS board....now I'm using vtx alone on a tpu holder separate from the nano Rx and smartaudio works perfect now.
Anyway there was signal from the pin (from board to FC and from vtx to board).
Thanks a lot for your help 
Appreciate very much

Grazie

Good thing you got it sorted.

But I am surprised you have continuity but SA doesn't works while mounted on the TBS VTX/RX mounting board. Must be some sort of a electrical/RF noise issue I assume but this has never been reported previously.