I almost get asked every other day, "what SmartAudio does my VTX have?" You need to know this in order to setup VTXTables for VTX Control to work properly.

There are three different versions, and it confuses the hell out of people. Product page and manual don't state that. But you can find out using the Debug mode in Betaflight:

• Go to Blackbox tab, under "Blackbox Debug Mode", select "SmartAudio". Doesn't matter what you choose for the other two options
  
• Hit "Save & Reboot"
  
• Enable "Expert Mode" (top left corner)
  
• Go to "Sensor" tab, uncheck everything but "Debug"
  • Debug 0 = SmartAudio Version * 100 + Device Mode
    
  • Debug 1 = Device Channel
    
  • Debug 2 = Device Frequency
    
  • Debug 3 = Device Power
    
• Power up your quad, and look at Debug 0 (Refresh 10ms not matter), the X value will indicate what SmartAudio version you have
  

For example:

100 = SA 1.0
116 = SA 1.0 unlocked
200 = SA 2.0
216 = SA 2.0 unlocked
300 = SA 2.1

side note: if what Oscar said doesn't work, try re-flashing your FC along with the AKK RDS Release.

Hi Oscar,

I was updating to 4.1.1 yesterday and found in the Betaflight page the following info:

Smart Audio Debug[0] key:


100 = SA 1.0
116 = SA 1.0 unlocked
200 = SA 2.0
216 = SA 2.0 unlocked
300 = SA 2.1

The page says that 2.1 is only for the latest TBS models like EVO or Pro32.
https://github.com/betaflight/betaflight...VTX-tables

Ssombra, I have the unify pro hv race version 2 VTX and it also reports 300 in the debug. Even though the bf documentation says evo and pro32 when you perform the debug task it will show 300 for a lot of tbs VTX models I believe.

As long as you get the right vtx table json file based on the debug (and subsequent smart audio) then you’ll be fine!

Cheers,

Ph2t.

When I go to blackbox tab I have no Debug option. No drop down for it. Just the ones for device and rate. I'm using the latest version of configurator.

(19-Jan-2020, 07:44 PM)Andy0679 Wrote: When I go to blackbox tab I have no Debug option. No drop down for it. Just the ones for device and rate. I'm using the latest version of configurator.

What version of BF and BFC do you HAVE? Maybe you have to get a later version.

(19-Jan-2020, 07:44 PM)Andy0679 Wrote: When I go to blackbox tab I have no Debug option. No drop down for it. Just the ones for device and rate. I'm using the latest version of configurator.

You need to be on any version of Betaflight 4.1 (earlier versions of BF including 4.0.x don't support the blackbox debug mode via the BFC GUI), and you need to be on Betaflight Configurator 10.6.0 (again, earlier versions of BFC don't have the blackbox debug mode dropdown). You can of course still set blackbox debug mode through the CLI for earlier versions.

Im on 10.6. The latest version and Matek F411 fw. Can you post the cmd line for CLI please?

(19-Jan-2020, 11:25 PM)SnowLeopardFPV Wrote: You need to be on any version of Betaflight 4.1 (earlier versions of BF including 4.0.x don't support the blackbox debug mode via the BFC GUI), and you need to be on Betaflight Configurator 10.6.0 (again, earlier versions of BFC don't have the blackbox debug mode dropdown). You can of course still set blackbox debug mode through the CLI for earlier versions.

Im on a Matek F411 (Tyro79) using Betaflight / MATEKF411 (MK41) 3.5.6 Feb 16 2019 / 13:21:00 (c28ca22f9) MSP API: 1.40. I'm using the latest release of the BF Configurator 10.6.0

What other firmware can I use? Can I use Betaflight F4? I thought it had to be F411 and that I can't just firmware ending in just "F4".

Am I mistaken?



EDIT: NVM I figured it out. My mistake. It's not the target, it's the version of the target. My version was 3.5.6 I just updated to 4.1.1 I was mistaken. lol Ok let's see if I got it now.

Flashing to a new version will erase your configuration and set everything vanilla. I believe the dev team has stated NOT to load any old 3.5.whatever DIFF's into 4.1.whatever, but tune from scratch.

This means setting up the serials and switches again.

Yeah I set up from scratch. Good thing I didn't have much to adjust. Everything is working, even my rx that you helped me with before. It just worked without the cli cmd you wrote for me when I joined a few weeks ago this time. I found my SA version and loaded the json file. I have SA 2.0 Set powers too. Thx for the help.

Hi Oscar

I have been unable to access the OSD function on a GEPRC GEP-20A-F4 flight controller using smart audio but fortunately found your page :-) Have followed through your instructions, however find that when I set smartaudio in the blackbox debug mode and move over to sensors, while still connected to Betaflight and plugging a battery into the quad and going to the sensors tab, the Debug 0 'X' reads zero rather that one of the values you indicate should be present. There must be something I'm doing incorrectly but can't see what. Is it obvious to you?

Thanks
Pete

(10-Dec-2020, 04:53 AM)skycamnz Wrote: Hi Oscar

I have been unable to access the OSD function on a GEPRC GEP-20A-F4 flight controller using smart audio but fortunately found your page :-) Have followed through your instructions, however find that when I set smartaudio in the blackbox debug mode and move over to sensors, while still connected to Betaflight and plugging a battery into the quad and going to the sensors tab, the Debug 0 'X' reads zero rather that one of the values you indicate should be present. There must be something I'm doing incorrectly but can't see what. Is it obvious to you?

Thanks
Pete

I use the same FC in combination with a Rushtank Ultimate Mini and also having several problems. Have you found a solution to your issues?

Thnx!

Same issue meaning you do not get OSD displayed on the video feed? Or is it something else?