Why CubePilot Separates the Autopilot From the Carrier Board
Quick Answer
CubePilot is an autopilot-on-module system: the Cube contains the processors and flight sensors, while a separate carrier board provides aircraft-facing power and connectors. Choose it when you want replaceable modules, configurable I/O and vibration-isolated inertial sensors. For most professional builds, we would start with Cube Orange+ rather than pay for Cube Red’s dual-FMU architecture.
What CubePilot Actually Is
CubePilot builds a wider hardware ecosystem around the Cube autopilot, not just a single flight controller. A Cube module plugs into a carrier board; GNSS, power monitoring, telemetry, CAN peripherals and actuators then connect through that board. This division is the reason system integrators choose Cube: the carrier can be changed or designed for an airframe without redesigning the flight-computer module.
One correction matters because it is repeated in older guides: the long-term Cube interface is an 80-position Hirose DF17 connector, not a 40-pin connector. That interface carries the autopilot signals to the carrier board. A bare module is therefore not a complete, wire-ready flight controller.
Cube Orange+ or Cube Red?
The CubePilot Cube Orange+ Module is our default recommendation. Its STM32H757 runs at 400MHz with 1MB RAM and 2MB flash. It provides three IMUs, two barometers, 14 PWM outputs, five general-purpose serial ports and two CAN interfaces when used with a suitable carrier. Two IMUs are mechanically isolated; the third acts as a fixed reference or backup.
The CubePilot Cube Red Pro changes the architecture rather than merely adding a faster processor. CubePilot documents two independent flight-management units and an Ethernet interface. That is relevant to aircraft whose safety case genuinely requires dual flight computers. For mapping, inspection, research and conventional VLOS work, Orange+ is the simpler choice. See our detailed Cube Orange+ versus Cube Red comparison before specifying Red.
| Decision | Choose | Why |
|---|---|---|
| Most professional prototypes and production aircraft | Cube Orange+ | Triple IMUs, dual barometers and mature ArduPilot/PX4 support without dual-FMU complexity |
| Project requires two independent flight computers | Cube Red | Dual-FMU architecture plus Ethernet |
| Small hobby build where module replacement is not important | Pixhawk-class board | Often a cleaner, smaller installation |
CubePilot vs Pixhawk: The Useful Distinction
“Cube or Pixhawk?” is not simply modular versus integrated. Pixhawk is a family of open autopilot standards, and boards such as the Pixhawk 6X also use a baseboard and have triple IMUs. Cube is a specific autopilot-on-module and 80-pin carrier ecosystem. Compare the connector layout, carrier-board choice, sensor architecture and firmware target against your aircraft rather than assuming every Pixhawk is a basic single-board controller.
Orange+ has dedicated ArduPilot and PX4 targets; it does not use the older Cube Orange firmware target. If you are starting with ArduPilot, follow our ArduPilot setup guide. Our Pixhawk 6 comparison covers the alternative hardware family.
What Else You Need
A module still needs a carrier, regulated power and positioning hardware. The Cube Carrier Board with ADS-B exposes the I/O and adds ADS-B In reception; it does not make an aircraft automatically compliant or provide collision avoidance. The Power Brick Mini supplies voltage and current measurements. Use our drone GNSS guide to select positioning hardware.
For a first Cube installation, the Cube Orange+ Standard Set with ADS-B removes some connector guesswork. For a custom carrier or compact airframe, buy the module only after checking the carrier pinout and power design. Browse the current autopilots and flight controllers rather than choosing by processor alone.
FAQ
Does CubePilot run ArduPilot or PX4?
Cube Orange+ has current ArduPilot and PX4 support. Always install the firmware target for the exact module: Orange+ and the older Orange do not share a firmware target.
Can I use a third-party Cube carrier board?
Yes, if it follows the Cube 80-pin interface and its power design suits the module and peripherals. Verify the carrier documentation rather than treating mechanical fit as electrical validation.
Is CubePilot better than Pixhawk?
Not universally. Choose Cube when its carrier ecosystem, serviceability and isolated sensor module solve a real integration problem. Choose a suitable Pixhawk-standard board when its size, connector layout or baseboard better matches the aircraft.