One Cube Is Not an Upgrade: Orange+ vs Cube Red Explained

One Cube Is Not an Upgrade: Orange+ vs Cube Red Explained

Quick Answer

Choose the Cube Orange+ for a conventional ArduPilot or PX4 aircraft. Choose Cube Red only when your engineering team needs its second H7 microcontroller, fourth IMU, third barometer, Ethernet and three CAN FD ports—and has a tested plan for using that architecture. Red is not a drop-in, automatically fail-safe Orange+.

The Naming Hides the Real Difference

The CubePilot Cube Orange+ Module has one STM32H757 dual-core microcontroller acting as its flight-management unit. It provides three IMUs, two barometers, one compass and the familiar Cube carrier-board ecosystem through one 80-pin DF17 connector. Two IMUs are vibration-isolated, while the third provides a fixed reference.

CubePilot Cube Orange+ autopilot module with orange aluminium case
Orange+ keeps the established single-connector Cube format and is the practical choice for most new aircraft.

The CubePilot Cube Red Pro Standard UAV Autopilot uses two STM32H7-series dual-core microcontrollers: a primary FMU and a secondary FMU. Its sensors are divided across them: three IMUs and two barometers serve the primary, while a fourth IMU and third barometer serve the secondary. This is a different system architecture, not simply a faster Orange+.

Cube Orange+ vs Cube Red: Verified Specification Table

Feature Cube Orange+ Cube Red Pro
Processing architecture One STM32H757 dual-core MCU; one FMU Two STM32H7-series dual-core MCUs; primary and secondary FMUs
IMUs 3 4: three on primary, one on secondary
Barometers 2 3: two on primary, one on secondary
PWM outputs 14: eight I/O, six FMU 14: eight secondary FMU, six primary FMU
CAN 2 CAN interfaces 3 CAN FD ports, split across both FMUs
Networking No onboard Ethernet interface Ethernet and DSI interfaces
Carrier connection One 80-pin DF17; established Cube carriers Two 80-pin connectors; Cube Red carrier required
Best fit General professional, research and hobby aircraft Custom safety and high-reliability system integration

Dual FMU Does Not Mean Automatic Failover

The previous version of this article implied that Cube Red’s secondary FMU automatically takes over and flies the same mission after a primary failure. That is too broad. CubePilot documents the hardware split, separate power regulation and primary/secondary outputs, but the safety behaviour still depends on firmware, configuration, carrier design and the operator’s verified integration.

Current ArduPilot firmware infrastructure publishes separate CubeRedPrimary and CubeRedSecondary targets. Treat Red as an engineering platform that needs bench, hardware-in-the-loop and aircraft-level failure testing. A second processor is useful redundancy hardware; it is not, by itself, an approved safety case or permission for BVLOS flight.

Can Cube Red Replace an Orange+ on the Same Carrier?

No. Orange+ uses the established single 80-pin Cube interface, whereas Red exposes its architecture through two 80-pin connectors and ships with a Cube Red carrier. Do not buy Red as a module swap for an existing Orange+ carrier. If you need the familiar ecosystem, the Cube Orange+ Standard Set with ADS-B is the simpler route.

CubePilot Cube Red Pro autopilot and dedicated standard carrier board
The Red Pro set includes its dedicated carrier; the extra connector is part of the dual-FMU design.

What We Would Actually Specify

For mapping, inspection, research and standard autonomous builds, we would start with Orange+. It is the lower-complexity option, works with established carriers and has mature ArduPilot and PX4 alternatives. Red makes sense only when a system engineer can name the failure modes its extra FMU, sensors and interfaces must address.

That decision should happen during system architecture, not at checkout. Our CubePilot ecosystem guide explains the module-and-carrier model, while the autopilot collection shows the current hardware options.

FAQ

Q: What is the difference between Cube Orange and Cube Orange+?

A: Orange+ uses the newer STM32H757 and a revised IMU board. It also needs its own Orange+ firmware target; do not flash standard Cube Orange firmware onto it.

Q: Is Cube Red better than Cube Orange+?

A: Not for most aircraft. Red provides more redundancy hardware and interfaces, but also requires a dedicated carrier and more integration work. Orange+ is the better default.

Q: Does Cube Red make a drone legal for BVLOS?

A: No. Hardware redundancy may support a safety case, but the aircraft, operating procedures and regulatory approval determine whether a BVLOS operation is permitted.

Back to blog