You’re at a race and the organizer assigns you a new frequency. Everyone else changes channels from their OSD in 3 seconds. You’re fumbling for the VTX button, counting LED blinks, guessing what band you’re on. SmartAudio and Tramp exist to make this instant. Here’s the full setup.
SmartAudio vs Tramp: Which Protocol Does Your VTX Use?
Every modern VTX supports one of two serial control protocols. They do the same thing — let Betaflight change channel, band, and power — but they’re not interchangeable.
SmartAudio (TBS protocol): Developed by Team BlackSheep. Used by TBS Unify, Rush Tank, AKK, some HGLRC, and Matek VTXs. It uses a single-wire half-duplex UART at 9600 baud. The wire carries both TX and RX on one pin.
Tramp (IRC protocol): Developed by ImmersionRC. Used by Tramp HV, Caddx Vista (digital), some Rush, and RDQ Mach series VTXs. It also uses a single wire but at a different baud rate and command set.
How to identify yours: Look at the VTX manual. If it says “SmartAudio” or “SA,” that’s TBS protocol. If it says “Tramp” or “IRC,” that’s Tramp. If it says neither, it might not support serial control — you’ll need to set channels via button or DIP switch. The TBS Unify Pro32 and Rush Tank Ultimate are SmartAudio. The ImmersionRC Tramp HV and RDQ Mach 3 are Tramp.
Wiring the VTX to Your Flight Controller
The wiring is the same regardless of protocol: connect the VTX data wire to a free UART TX pad on your FC. That’s it — one wire.
Pin mapping:
| VTX Wire Label | FC Pad | Notes |
|—|—|—|
| VTX Data / SA / IRC | UART TX (any) | The control wire. Single wire, half-duplex. |
| VTX 7-36V / VCC | VBAT or 9V BEC | Power input. Match voltage to VTX spec. |
| VTX GND | GND | Common ground with FC. |
| VTX Video | Video Out (VO) | Analog video signal to VTX. |
If your VTX manual says to connect SmartAudio to a UART RX pad instead of TX, it’s wrong — or at least outdated. Modern Betaflight (4.0+) expects VTX control on a TX pad. Connecting to RX won’t work because TX is the output for the FC’s half-duplex communication.
For the Rush Tank Ultimate and TBS Unify Pro32, one wire to a TX pad is sufficient — these VTXs auto-detect the protocol and baud rate on first power-up.
Betaflight Configuration Step-by-Step
Step 1: Enable the VTX Table
Go to the Video Transmitter tab. Click “Load from file,” select the JSON file matching your VTX (download from the manufacturer’s site or the Betaflight VTX table repo). This loads the supported bands, channels, and power levels.
If no JSON file exists for your VTX, build the table manually: add each supported band, frequency for each channel, and each power level in mW. This is tedious but critical — without the VTX table, Betaflight can’t validate your commands.
Step 2: Configure UART
Open the Ports tab. Find the UART where you wired the VTX data wire. Under “Peripherals,” select TBS SmartAudio or IRC Tramp (whichever matches your VTX). Set baud to AUTO. Click Save and Reboot.
What happens if you pick the wrong protocol? The OSD shows “VTX: DEVICE NOT READY” and you can’t change channels. Switch the peripheral and reboot — no permanent damage, just frustration.
Step 3: Verify VTX Communication
After reboot, go back to the Video Transmitter tab. The top section should show your VTX’s current band, channel, frequency, and power level. If it shows all zeros or “Not Connected,” the wiring or protocol selection is wrong.
Troubleshooting checklist:
– Wire connected to TX pad, not RX? ✓
– Right UART selected? ✓
– Right protocol (SA vs Tramp)? ✓
– VTX powered on? Some VTXs need battery voltage, not just USB ✓
– No other peripheral on this UART? VTX control and GPS can’t share a UART ✓
Step 4: Configure Pit Mode
Pit mode drops VTX output to near-zero (typically 0.01-0.1mW). It’s useful for race lineups, bench testing without overheating, and power-saving on the starting block.
In the Video Transmitter tab, check “Pit Mode.” Set it to activate on first arm — the VTX powers up at pit mode when you plug in, then goes to full power when you arm. This prevents the VTX from baking on the starting line while you wait for your heat.
Alternatively, map pit mode to a switch under the Modes tab → VTX PIT MODE. I run it on a momentary switch — hold it for pit mode, release for full power.
Step 5: OSD Channel and Power Control
In the OSD tab, add the “VTX Channel” element to your layout. While disarmed, use stick commands or CMS (Configuration Menu System) to enter the OSD menu:
– Throttle left + Yaw left + Pitch up = Enter CMS
– Navigate to “Features → VTX”
– Change band, channel, or power level
– Exit and save
The OSD menu is the fastest way to change channels at a race. No laptop, no button-pressing. Three stick movements and you’re on the new frequency.
VTX Table Management for Multi-Region Flying
If you fly in different regions with different legal frequency bands, create separate VTX tables. US legal 5.8GHz bands differ from EU and Japan. In the Video Transmitter tab, you can load a different JSON file as needed, or edit the table to disable bands you shouldn’t transmit on.
The TBS Unify Pro32 HV supports 25mW, 100mW, 400mW, and 1W+ levels. For most flying, 200-400mW is sufficient. Above 400mW, you need active cooling or the VTX will thermal-throttle. At a race with 6 pilots on 25mW, going to 400mW just bleeds into everyone else’s feed. Match your power to the environment, not just “crank it to max.”
Common SmartAudio and Tramp Problems
Mistake 1: Connecting SA/Tramp wire to an RX pad. The FC transmits VTX commands, so the data wire goes to TX. Connecting to RX works with some older Betaflight versions that supported half-duplex on RX pins, but 4.0+ doesn’t. Symptom: VTX not detected, power/channel won’t change.
Mistake 2: Powering the VTX from a 5V BEC that can’t deliver enough current. A TBS Unify Pro32 at 1W draws ~600mA at 5V. A 5V/1A BEC is fine. A 5V/500mA BEC browns out on punch-outs. Connect to VBAT if the VTX supports it (most do, up to 6S), or use a dedicated 9V/12V BEC with at least 1A headroom.
Mistake 3: Loading the wrong VTX table JSON. If your VTX supports 25/100/400/800mW but the table only has 25/200/500/800, selecting 200mW actually sends a command for a level that doesn’t exist — the VTX either ignores it or goes to an unexpected power level. Always verify the table matches your exact VTX model.
Mistake 4: Changing channels while armed. Betaflight blocks VTX changes while armed to prevent accidental frequency changes mid-flight. If you can’t change channels from the OSD, disarm first. This isn’t a bug — it’s a safety feature.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. VTX power output and frequency band usage are regulated. The US FCC limits unlicensed 5.8GHz transmission to specific bands and power levels. EU CE certification imposes additional restrictions. Always verify local laws regarding transmission power and frequency before flying.
SmartAudio and Tramp eliminate the most annoying part of FPV — crawling to your quad to change channels. At a race, the 30 seconds you save adds up over 8 heats. When integrated with our Betaflight OSD configuration guide, you have full control of your video link without touching a computer. For pilots who run multiple quads, our ExpressLRS binding guide shows how the same “configure once, never touch again” philosophy applies to the control link.
The Rush Tank Ultimate VTX supports both SmartAudio and Tramp protocols, delivers clean 800mW output with minimal harmonic bleed, and includes an MMCX connector for antenna flexibility — available at uavmodel.com.