How to Choose an FPV Flight Controller: MCU, Gyro and UARTs
A flight controller looks like a plain circuit board, but it decides which receiver, video system, GPS and firmware your build can use. Most bad purchases come from a missing UART, the wrong voltage rating or a board that does not fit the frame, not from the processor. This guide goes through what to check, in the order that matters.
F4, F7 or H7: what does the processor change?
The MCU is the chip that runs the firmware. F4 is the older, cheaper family, F7 is faster, and H7 is the fastest of the three and has the most memory. On a simple 5-inch quad the difference you feel in the air is small. What a faster chip really buys is headroom: higher loop rates, heavier filtering and more features running at once without the processor running out of time.
Memory matters as much as speed. Firmware grows with every release, and a board with little flash may have to leave features out. ArduPilot and INAV are more demanding than Betaflight, and ArduPilot in particular is normally run on F7 and H7 boards; older F4 boards with limited flash are restricted there.
A rule of thumb: for a straightforward 5-inch freestyle or racing build, an F4 or F7 board is enough. For long range, GPS, many peripherals or ArduPilot, choose F7 or H7. Bigger chips also tend to come on boards with more UARTs, which is often the real reason to step up.
The gyro: SPI and a known model
The gyro is the sensor the whole control loop depends on. Look for a gyro connected over SPI, which is how nearly all modern FPV boards are built. Common parts include the MPU-6000, ICM-20602, BMI270 and ICM-42688-P. The ICM-42688-P is generally regarded as a low-noise newer part, and the BMI270 is widely used and works well, so no common gyro is a mistake.
In practice the board's layout and how well the stack is isolated from vibration matter more than the gyro name. Make sure the firmware version you intend to run supports the gyro on the board. For Betaflight and INAV the manufacturer normally names the target to flash; use that rather than guessing.
Count your UARTs before you buy
A UART is a serial port, and each connected device needs its own. The board may list six, but some are used internally (for example by the onboard OSD or a Bluetooth chip), and some are only partly wired out as pads. Count the pads that are actually accessible, with both TX and RX where the device needs both. The USB port does not count.
Add up the devices you want now and leave one spare for later. Typical consumers are: a receiver (one UART), an HD video system such as DJI (one UART for its OSD data), a GPS (one UART, plus two I2C pads if the module has a compass), a telemetry or MSP link (one), ESC telemetry (one, RX only) and analog VTX control over SmartAudio or Tramp (one TX). Analog camera control normally uses a single pad rather than a UART.
Here is a sample plan for a 5-inch with HD video, GPS and ELRS:
- UART 1: ELRS receiver
- UART 2: HD video unit (OSD data)
- UART 3: GPS
- UART 4: ESC telemetry, if you want per-motor data
- UART 5: spare, for a telemetry link or VTX control
- I2C pads: GPS compass, and a barometer if the board has none
Mounting pattern, stack or AIO
The mounting pattern is the hole spacing, measured centre to centre. 30.5 x 30.5 mm is the usual standard for 5-inch and larger frames and normally takes M3 screws. 25.5 x 25.5 mm is common on smaller builds, and 20 x 20 mm is used for micro and 3-inch builds. Hole size varies, so check the frame's drawing and the board's specification instead of assuming. Many boards use soft grommets, which make the exact hole diameter matter less.
A stack is a separate flight controller and a 4-in-1 ESC joined by a short cable or connector. It is easy to repair or upgrade one half. An AIO puts the flight controller and the ESC on a single board. It saves weight and wiring, but a fault in either half usually means replacing the whole board. Whichever you pick, check the connector pinout between the two boards: it is not standardised, and a mismatched pair can end up wired to the wrong pins.
Also check the board's overall size against the space between the frame plates, and the position of the USB port so you can still plug it in with the build closed.
Voltage rating, BEC outputs and current sensor
Check the input voltage range on the product page. Many boards are specified for 3S to 6S, some up to 8S. Running a board above its rating can destroy its regulator, so do not assume that a 6S-rated board and ESC are enough for 8S. The input capacitor and the ESC matter as well.
The BEC is the regulator that turns battery voltage into the supply rails for the rest of the build. 5 V normally feeds the receiver, GPS and LEDs. 9 V or 12 V rails, where present, are usually for the VTX and camera. Look at both the voltage and the current rating of each rail and compare it with what you plan to connect. An HD air unit and a GPS can draw more than a small regulator is happy to supply. Many HD units prefer to be powered from the battery side or a dedicated rail, so read the unit's own power specification.
A current sensor lets the firmware show consumption and mAh used in the OSD. Usually the ESC provides the signal, which reaches the flight controller through the stack connector, and the scale value needs a one-time calibration. If you want accurate battery data, make sure the combination provides a sensor.
Blackbox, barometer and compass
Blackbox logging records gyro, motor and setpoint data for tuning. Some boards store it on a small onboard flash chip, which fills quickly and has to be erased and downloaded often. Others have a microSD slot, which holds much more and makes tuning with long logs easier. If you plan to tune seriously, choose the board with the SD slot.
A barometer improves altitude data and is useful with GPS features and in INAV or ArduPilot. Many boards include one; check whether you need it. A compass is usually part of a GPS module connected to the I2C pads, and it works best away from power wires and motors, such as on a mast. For a pure acro build neither is needed.
Firmware support
Betaflight is the usual choice for freestyle and racing, INAV adds navigation features for GPS and long range, and ArduPilot targets autonomous and larger vehicles. Many F4, F7 and H7 boards can run more than one of them, but not all do: the supported-hardware list of the firmware is the authority, not the shop listing. If you intend to run one specific firmware, check that list first.
If your goal is a proper autopilot rather than a quad flown by hand, look at the autopilot category and read the store's guide on choosing a drone autopilot before buying a general FPV board.
Common buying mistakes
- Counting UARTs from the spec sheet instead of the pads you can reach
- Forgetting that HD video, GPS and a telemetry link all need their own port
- Assuming a 30.5 mm board fits a frame meant for 20 mm, or the reverse
- Buying an AIO or stack without checking the pinout between the two boards
- Exceeding the board's voltage rating on 8S
- Powering a power-hungry HD unit or GPS from a small 5 V regulator
- Choosing flash blackbox and then needing long logs for tuning
- Buying for ArduPilot without checking that the board is on its supported list



