Free shipping on orders over ₪600 · Stock in Israel · Bit, bank transfer or card by phone

How to Choose a Pixhawk Autopilot: Cube, Carrier and Power

Published 24 October 2026

An autopilot does far more than keep a drone level. It flies missions, holds position, returns home on its own and makes decisions when the link drops. Choosing one means deciding on the firmware, the hardware generation, the carrier board that connects it to the airframe and a power supply it can rely on.

When an FPV flight controller is enough

Betaflight boards are built for manual, acro flying: a single IMU, a fast control loop and almost no navigation. INAV adds GPS navigation, return to home and waypoints on the same small F4, F7 and H7 boards, and for a long-range FPV wing or quad that is often all you need.

A Pixhawk-class autopilot running ArduPilot or PX4 makes sense when the aircraft flies autonomous missions, carries an expensive payload, needs RTK or CAN peripherals, is a VTOL, a large multirotor, a rover or a boat, or has to meet a customer's or regulator's demands for redundancy and full flight logs. ArduPilot also runs on many FPV-style H7 boards; what a Pixhawk-class unit adds is mainly redundancy, standard connectors and room for more peripherals.

ArduPilot or PX4

Both are mature open-source autopilot stacks, both speak MAVLink and both run on Cube and Pixhawk hardware. ArduPilot supports the widest range of vehicles: multirotors, helicopters, planes, QuadPlane VTOLs, rovers, boats and submarines. It is set up mainly through Mission Planner or QGroundControl and has a very large set of parameters. PX4 covers multirotors, fixed-wing, VTOL and rovers, is set up through QGroundControl, and is common in research and in companies that build products on its code.

One practical difference is the licence: ArduPilot is GPLv3, so modified code you distribute must be shared, while PX4 uses the permissive BSD licence. For most buyers the decision is simpler: which stack best supports your vehicle type, which one your team or customer already knows, and which one your peripherals are documented for.

The Pixhawk standard and FMU versions

Pixhawk is an open hardware project. Its standards define the flight management unit (FMU) generation, the processor class and the connector pinouts, so autopilots from different makers wire up the same way. The original Pixhawk 1 and its widely sold clones, such as the 2.4.8, use an STM32F427 processor. Later generations, FMUv5 (Pixhawk 4), FMUv5X and FMUv6X/6C (for example the Holybro Pixhawk 6X and 6C), moved to STM32F7 and H7 processors and standard JST-GH connectors.

CubePilot's Cube grew out of the same project: the Cube Black was an FMUv3 design, and the later Cubes are listed by PX4 as manufacturer-supported boards. Both ArduPilot and PX4 support them, but always load the firmware for your exact model: the Cube Orange and the Cube Orange+, for example, have separate firmware builds.

Older F4-based boards still fly, but they have less memory and processing headroom, and new firmware features increasingly target H7 boards. For a new build, an H7 autopilot is the sensible starting point.

The Cube family: which model for which job

In every Cube the processor and sensors sit inside the cube, and all inputs and outputs pass through a single 80-pin connector to a carrier board. That is what lets you move a Cube between airframes, or replace a damaged carrier without touching the autopilot itself.

NDAA compliance is about where the hardware and its components are made, not how well it flies. If a tender or a customer requires it, ask the manufacturer for its current declaration for the exact model.

  • Cube Orange: STM32H753 processor, three IMUs (two of them vibration-isolated and heated) and two barometers. The long-standing workhorse for multirotors, planes and VTOLs
  • Cube Orange+: the successor, on a dual-core STM32H757 with newer IMUs. Same size and 80-pin connector, so it fits the same carrier boards
  • Cube Blue H7: built in the USA with components from the US and allied countries, for projects that require NDAA compliance or a defined supply chain
  • Cube Purple: a smaller cube for rovers and boats, with a single IMU and barometer and no isolation or heating, since ground and marine vehicles rarely need that redundancy
  • Cube Red: the top of the range, with two H7 processors that can run two independent ArduPilot instances, more redundant sensors and Ethernet, aimed at critical and commercial operations

The carrier board decides how the Cube fits your airframe

The carrier board holds the connectors, the power inputs and any extra hardware. CubePilot's standard carrier offers the full set of ports, and the ADS-B version adds a 1090 MHz ADS-B IN receiver: it shows nearby manned aircraft that transmit ADS-B OUT at the ground station and can feed ArduPilot's avoidance features. It only receives, so it does not make your drone visible to anyone.

Smaller carriers, such as the CubePilot Mini carrier or third-party boards like the Aerium Altius, give up some ports to save size and weight so a Cube fits a compact airframe. Multirotor carriers such as Kore build power distribution into the board, with battery voltage and current sensing, which removes a separate power module and a lot of wiring.

Before choosing, count everything you will connect: telemetry radio, one or two GPS units, CAN devices, RC receiver, companion computer, and the number of motor and servo outputs. Then check the board's size, mounting pattern and battery voltage rating against the airframe.

Redundant, heated and isolated IMUs

The IMU, a set of accelerometers and gyros, is how the autopilot knows its attitude. Pixhawk-class autopilots usually carry two or three, and ArduPilot's EKF can run on each of them and move away from one that disagrees or fails. Two barometers do the same job for altitude.

Vibration is the most common cause of poor position hold and altitude drift. Cubes mount two of their IMUs on an internally isolated board, but that is a last line of defence: balance the propellers, stiffen the frame and check the vibration levels in your logs. A heated IMU is held at a steady temperature, so its readings do not drift as the air warms or cools, which matters on cold mornings and during long climbs.

Power: clean, monitored and redundant

An autopilot that browns out in flight means a crash, so it needs a clean 5 V supply that does not share a regulator with servos or a payload. A power module sits between the battery and the rest of the aircraft, feeds the autopilot a regulated supply and reports battery voltage and current, so low-battery warnings and failsafes are accurate. Choose one rated for both your battery voltage and the current that will flow through it: a classic module may stop at 6S, while 12S and 14S builds need a high-voltage module or a distribution board with sensing.

Analog power modules send voltage and current as analog signals. They are simple and widely supported, but they need calibrating and can pick up noise. CAN (DroneCAN) power modules measure on the module itself and send digital readings over the bus, so wiring noise affects them far less.

Cube and Pixhawk autopilots run on 4.1 to 5.7 V at each power input and switch between inputs automatically, so feeding both POWER ports from separate sources gives real redundancy. The servo rail is not powered by the autopilot: feed it from its own BEC, and connect only one BEC to it.

Quick checklist

  • You really need a Pixhawk-class autopilot, not an INAV board
  • The firmware (ArduPilot or PX4) supports your vehicle type well
  • The autopilot is H7-based, and you load the firmware for its exact model
  • The carrier board has every port you need and fits the airframe
  • The power module is rated for your battery voltage and current
  • Both power inputs are fed from separate sources, and the servo rail has its own BEC
  • Vibration levels are checked in the logs after the first flights

Shop the parts

More guides

Related products

FFPV.BASE

An Israeli shop for FPV drone parts and ready-to-fly quads. Build, fly, upgrade — all in one place.

Israeli FPV storeLicensed dealer no. 060875804Licensed by the Israeli Ministry of Communications to trade in wireless equipment
Categories
Customer service
Contact
© 2026 FPV.BASE — All rights reserved