You’ve soldered everything to the flight controller, plugged in a battery, and… nothing. The receiver LED is dark. The VTX isn’t transmitting. The GPS module shows zero satellites. Nine times out of ten, the problem isn’t a dead component — it’s a wiring mistake. Misassigned UARTs, incorrect voltage pads, and missing ground connections kill more maiden flights than faulty hardware ever has. Here’s how to wire an FC so it works the first time.
The Flight Controller Pad Layout: What Everything Does
Every FPV flight controller has the same basic set of pads, but their arrangement and labeling vary by manufacturer. Understanding the function of each pad type before you start soldering prevents the “I’ll figure it out later” wiring that leads to burned regulators and crossed signals.
UART Pads: TX and RX
UARTs (Universal Asynchronous Receiver-Transmitter) are serial communication ports. Each UART has a TX (transmit) pad and an RX (receive) pad. The rules:
– TX on the peripheral connects to RX on the FC
– RX on the peripheral connects to TX on the FC
– The UART must be configured in Betaflight’s Ports tab to the correct function
Common UART assignments for modern builds:
– UART1: Receiver (Serial RX). This is the default on most F7 boards and many F4 boards.
– UART2: VTX SmartAudio or Tramp control. TX-only connection — the FC sends channel/power commands, no data comes back.
– UART3: GPS module. Both TX and RX are used. GPS transmits position data on its TX (to FC RX), and the FC sends configuration on its TX (to GPS RX).
– UART4 or UART6: ESC telemetry (for bidirectional DShot/RPM filtering). RX-only — ESC TX connects to FC RX.
– UART5: Spare, often used for a receiver on F7 boards that don’t have a dedicated SBUS pad.
On F4 boards, UARTs have hardware inversion on specific ports. SBUS receivers (including Crossfire in SBUS mode) require an inverted signal. If your receiver isn’t detected, check whether the UART you’re using supports hardware inversion (UART1 on F4, any UART on F7).
Voltage Pads: VBAT, 5V, 9V, 3.3V
Flight controllers include voltage regulators that step down battery voltage to the levels different components need:
- VBAT (battery voltage, 2S-6S): Direct battery connection. Use for: ESCs (power input), VTX power input (if the VTX accepts wide voltage), capacitor. Do NOT connect to receivers, cameras, or GPS modules — they’ll fry instantly.
- 9V or 10V: Filtered, regulated output. Use for: VTX, DJI Air Unit/O3/O4 (which typically accept 7.4-26.4V but benefit from a clean regulated supply), or camera if it accepts wide voltage.
- 5V: The workhorse rail. Use for: receivers (ELRS, Crossfire), GPS modules, WS2812 LED strips, buzzer. Most flight controllers provide 2-3A on the 5V rail, which is enough for 2-3 peripherals.
- 3.3V: Low-current rail, usually for logic-level signaling only. Use for: Spektrum satellite receivers (rare, and even those are typically 3.3V from the receiver port). Do not use for anything that draws significant current.
The most common wiring mistake I see in build groups: connecting a VTX’s 5V input to VBAT because “I thought it could handle it.” Read your VTX’s input voltage spec. If it says 5V input, it means 5V, not “somewhere around battery voltage.”
Signal Ground: The Missing Wire That Causes Intermittent Problems
For analog video systems, the camera and VTX signal wires should be paired with a ground wire — not the power ground, but a separate signal ground that runs alongside the video signal. Without it, the video signal’s return path goes through the main power ground, which carries ESC switching noise. The result: diagonal lines in the feed that get worse with throttle.
For digital systems (DJI O3/O4, Walksnail, HDZero), the MIPI cable carries signal and ground on separate conductors internally — you don’t need to add external signal grounds for the video path.
Step-by-Step Wiring Sequence
I follow this order on every build. It minimizes the chance of burying an inaccessible pad under a tangle of wires.
- Motor wires to ESC pads — These are the biggest pads and the hardest to access once other wires are in place. Solder them first.
- Main battery leads + capacitor — The thickest wires, soldered to the largest pads. I add the capacitor at the same time since it shares the same pads.
- Receiver wiring — 5V, GND, and RX pad. Keep the receiver antenna away from the VTX antenna.
- VTX wiring — Power (9V or VBAT, depending on the VTX), GND, and SmartAudio/Tramp wire to a UART TX. Add a signal ground wire alongside the video signal.
- Camera wiring — Power (5V or VBAT, depending on the camera), GND, video signal. Add signal ground.
- GPS wiring — If used: 5V, GND, TX→FC-RX, RX→FC-TX. Mount the GPS module as far from the VTX antenna as physically possible — the VTX can interfere with GPS reception.
- Buzzer/LED wiring — Last, since they’re optional and can be tested after everything else works.
FC Wiring Quick Reference Table
| Component | Power Pad | Data Pad(s) | Additional Connections | Common Pitfall |
|---|---|---|---|---|
| ELRS Receiver | 5V | UART RX (TX→RX) | None (single wire) | Wrong UART inversion on F4 |
| Crossfire Nano RX | 5V | UART TX + RX (Ch1/Ch2 on RX) | Ch3/Ch4 for telemetry (optional) | Forgetting Ch2 connection |
| Analog VTX | 9V or VBAT | UART TX (SmartAudio/Tramp) | Video wire, signal ground | Powering 5V VTX from VBAT |
| Analog Camera | 5V or VBAT | Video pad | Signal ground | Missing signal ground → noise |
| DJI O3/O4 | 9V or VBAT (7.4-26.4V) | UART TX + RX (MSP for OSD) | 6-pin DJI connector | Wrong UART baud rate for MSP |
| GPS Module | 5V | UART TX + RX | Compass SDA/SCL (if equipped) | GPS too close to VTX antenna |
| Buzzer | 5V | BZ- pad | BZ+ to 5V | Polarity — piezo buzzers have polarity |
Common Mistakes & What Most Pilots Get Wrong
Mistake 1: Connecting peripherals to random UARTs and sorting it out in software later. Every UART is physically identical, but some have hardware inversion (F4 UART1), some are shared with other peripherals (USB, OSD chip), and some are reserved for specific functions. Check your FC’s pinout diagram before soldering. If the diagram says “UART1 for Serial RX,” use UART1 for the receiver. Don’t get creative.
Mistake 2: Running all ground wires to a single pad to be “clean.” Daisy-chaining grounds creates ground loops. Each component should have its own ground wire back to the FC or a shared ground bus. The practical approach: camera and VTX grounds to the camera and VTX ground pads. Receiver and GPS grounds to any convenient 5V GND pad. They all share the same ground plane internally on the FC.
Mistake 3: Skipping the smoke stopper on first power-up. A Pololu or VIFLY smoke stopper costs $8. A new flight controller costs $40-80. If you have a solder bridge between 5V and GND (invisible to the naked eye under a connector), the smoke stopper trips before the FC dies. Use one every time you power a new build for the first time.
Mistake 4: Wiring the VTX SmartAudio wire to an RX pad instead of TX. SmartAudio is the FC telling the VTX what to do — data flows from the FC (TX) to the VTX (RX). Connect the FC’s TX pad to the VTX’s SmartAudio pad. Connecting SmartAudio to the FC’s RX pad silently fails — no error message, VTX just doesn’t respond to channel changes.
Mistake 5: Assuming all 5V pads are the same. On most FCs, all the 5V pads are on the same rail. On some (notably older Matek boards), the 5V for the receiver port is a separate regulated output, and other 5V pads come from a different regulator. If a receiver works on one 5V pad but not another, check your FC’s schematic to see if they’re on the same rail.
⚠️ Regulatory Notice: The build and flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
Clean wiring starts with good solder joints. Before you touch an iron to your FC, read our FPV soldering guide — it covers the 63/37 solder and rosin flux that produce joints you don’t have to reflow later. Once the FC is wired, the Betaflight Ports tab guide walks through assigning each UART to the correct function.
When building with an F7 flight controller that gives you plenty of UARTs and clean power rails, the SpeedyBee F7 V3 has one of the most builder-friendly pad layouts I’ve used — all the UARTs are labeled clearly on the silkscreen, the 9V BEC handles both analog VTX and DJI O4, and the through-hole pads are large enough that you’re not soldering under a magnifying glass.