Our edge flight controller against the Cube Orange+, Holybro Pixhawk 6X and mRo Control Zero H7: same H7 class, different ownership.
All four run ArduPilot and PX4 on an H7-class Cortex-M7 with redundant IMUs, so the processor line on the datasheet does not decide the buy. The questions that do are the temperature envelope, whether the compass is doubled, and whether the buyer can commission a firmware and carrier-board change without a foreign vendor in the loop.
This is a fielded autopilot, not a development board. It carries dual redundant IMUs, dual pressure sensors and dual magnetometers on an integrated system-on-module, needs no end-user calibration, and is vibration and temperature tested across -40 to +85 degrees C. Custom firmware and carrier-board development are offered per programme from the same team that supplies it.
Side by side
| Attribute | Represented by UnstratEdge flight controller | CubePilotCube Orange+ standard set1Australia | HolybroPixhawk 6X2China | mRo (mRobotics)Control Zero H73United States |
|---|---|---|---|---|
| Main processor123 | ARM Cortex-M7 H7-class, 480 MHz | STM32H757 Cortex-M7, 400 MHz | STM32H753 Cortex-M7, up to 480 MHz | STM32H743 Cortex-M7, 480 MHz |
| Memory123 | 1 MB RAM, 2 MB flash, 32 KB FRAM, SD card | 1 MB RAM, 2 MB flash | 1 MB RAM, 2 MB flash | 1 MB RAM, 2 MB flash, 256 kb FRAM |
| Inertial sensors123The competitors carry three IMUs against our stated two, so on raw inertial redundancy count the Cube and Pixhawk lead. Our figure comes from the catalogue, which states dual redundant IMUs. | Dual redundant IMUs (dual 3-axis accel/gyro) | Three accel/gyro (ICM42688p, ICM20948, ICM20649), two on vibration isolation, one fixed reference | Three IMU sensors on isolated domains and separate buses (Rev 8: 3x ICM-45686) | Three accel, three gyro (ICM-20602, ICM-20948, BMI088 dampened) |
| Barometric pressure sensors123 | Dual pressure sensors | Two MS5611 barometers | Two barometer sensors on separate buses | One DPS310 barometer |
| Magnetometers123On the compass, ours is the only board in this set that states two magnetometers; the three competitors publish a single onboard compass and rely on an external GNSS-mounted compass for redundancy. | Dual 3-axis magnetometers on the module | One compass (ICM20948) | One onboard magnetometer (BMM150) | One internal magnetometer (AK09916 in ICM-20948) |
| PWM / servo outputs123 | 16 PWM channels | 14 PWM/servo outputs (8 from IO, 6 from FMU) | Not published on the PX4 overview page | 8 PWM outputs (all DShot capable) |
| CAN buses123The Cube Orange+ page states CAN without the FD data rate; the Control Zero states a single CAN bus. Our catalogue states two FD CAN buses at 8 Mbit each. | 2x FD CAN at 8 Mbit | 2x CAN (one with internal 3.3V transceiver) | Not published on the PX4 overview page | 1x CAN |
| Serial ports123 | 4x serial | 5x UART, one high-power, 2x with hardware flow control | Not published on the PX4 overview page | 6x UART (3x with hardware flow control) |
| Operating temperature123The Cube Orange+ publishes a narrow -10 to 55 C envelope. The Pixhawk 6X matches ours at -40 to 85 C. The Control Zero H7 does not publish an operating range. | -40 to +85 degrees C | -10 to 55 degrees C | -40 to 85 degrees C operating and storage | Not published |
| Firmware123 | ArduPilot and PX4 | ArduPilot and PX4 | ArduPilot and PX4 (PX4 maintainer-tested standard) | ArduPilot and PX4 |
| Weight and size123The weights are not comparable like for like: ours is stated with the carrier board and enclosure, the Control Zero figure is the bare module. Compare integrated packages, not board-only numbers. | 88 g with carrier board and enclosure, 80 x 55 x 20 mm | Cube 38.25 x 38.25 x 22.3 mm, carrier 94.5 x 44.3 x 17.3 mm; weight not published on the PX4 page | Not published on the PX4 overview page | 5.3 g, 20 x 32 mm (module only, aluminium case included) |
| Custom firmware and carrier board123 | Custom firmware and carrier-board development available per programme, from an independent, non-aligned supplier | Carrier boards are a documented design pattern; custom development is via CubePilot and its reseller network | Open baseboard options published; changes go through Holybro | Custom carrier board support listed as No on the vendor spec table |
Competitor values are quoted from the vendor documents listed under Sources, as published on the date shown. Configurations vary, so treat every row as a starting point for the evaluation rather than a like-for-like test result.
What the table means
On silicon this is a dead heat, so do not buy on the processor line.
All four sit on an H7-class Cortex-M7 with 1 MB of RAM and 2 MB of flash, and all four run ArduPilot and PX4. The Cube Orange+ clocks its STM32H757 at 400 MHz, the Pixhawk 6X and Control Zero H7 at 480 MHz, and ours at 480 MHz. That is close enough that the datasheet processor row decides nothing. The Cube and Pixhawk carry three IMUs against our stated two, so on inertial redundancy count they lead; where ours differs is the compass, stated as dual magnetometers where the three competitors publish a single onboard compass.
Temperature and the compass are where the numbers actually diverge.
The Cube Orange+ publishes a -10 to 55 C operating range, which is a commercial envelope; the Pixhawk 6X matches ours at -40 to 85 C, and the Control Zero H7 does not publish a range at all. If the programme flies in cold or hot climates, that row alone narrows the field. Our board is stated as vibration and temperature tested with no end-user calibration required, which matters for a unit issued to crews rather than integrators.
The decisive question is who extends the firmware and the carrier board.
An autopilot is not a sealed part; a national programme changes its I/O map, its sensor mix and sometimes its firmware. The Control Zero H7 spec table lists custom carrier board support as No. CubePilot and Holybro both support customisation through their own channels and reseller networks. Our principal states custom firmware and carrier-board development per programme from one accountable, non-aligned team, so the buyer's own engineers extend the board rather than petitioning a foreign vendor and waiting on an export decision.
Questions buyers ask
What is the best alternative to a Cube Orange+ or Pixhawk 6X for a sovereign drone programme?
All three are capable H7-class autopilots running ArduPilot and PX4. The Cube Orange+ runs an STM32H757 with three IMUs but a -10 to 55 C envelope; the Pixhawk 6X runs an STM32H753 at 480 MHz with a -40 to 85 C range. Ours matches the H7 class at 480 MHz with dual IMUs, dual pressure sensors and dual magnetometers, needs no end-user calibration, is tested to -40 to 85 C, and ships with custom firmware and carrier-board development from an independent, non-aligned supplier. If you need to own the firmware and the carrier design rather than route changes through a foreign vendor, that is the reason to pick it.
Does it run ArduPilot and PX4 like the Pixhawk and Cube?
Yes. It runs both ArduPilot and PX4 across multirotors, fixed wings, VTOLs, rovers and boats, the same open firmware stacks the Cube Orange+, Pixhawk 6X and Control Zero H7 use. Because the firmware is open standard, the buyer's engineers can extend it rather than waiting on a vendor release, and the principal offers custom firmware development per programme on top of that.
How many IMUs and compasses does it have compared with the competitors?
It carries dual redundant IMUs, dual pressure sensors and dual magnetometers. On IMU count the Cube Orange+ and Pixhawk 6X publish three, so they lead on raw inertial redundancy. On the compass the picture reverses: the three competitors publish a single onboard magnetometer and lean on an external GNSS-mounted compass, while ours states two magnetometers on the module itself. Match the redundancy that matters for your airframe rather than the headline count.
What temperature range can this flight controller handle?
It is stated at -40 to +85 degrees C and is vibration and temperature tested. The Pixhawk 6X publishes the same -40 to 85 C range. The Cube Orange+ publishes a narrower -10 to 55 C, and the Control Zero H7 does not publish an operating temperature. For cold-climate or desert operations, specify against the published envelope and confirm it in your own trial.
Is this a fielded autopilot or a prototype?
Fielded. It is an integrated system-on-module with dual redundant IMUs, dual pressure sensors and dual magnetometers, no end-user calibration, and vibration and temperature testing across -40 to 85 C. The figures quoted here are the delivered specification, and custom firmware and carrier-board work are offered per programme.
Sources
- 1. CubePilot (via PX4 documentation), CubePilot Cube Orange+ Flight ControllerRetrieved: 2026-08-15 · Specifications read from the PX4 hardware page: STM32H757 400 MHz, 1 MB RAM, 2 MB flash, three accel/gyro, one compass, two MS5611 baros, 14 PWM, 2x CAN, 5 UART, -10 to 55 C, dimensions.
- 2. Holybro (via PX4 documentation), Holybro Pixhawk 6XRetrieved: 2026-08-15 · Read from the PX4 hardware page: STM32H753 Cortex-M7 up to 480 MHz, 2 MB flash, 1 MB RAM, three IMU sensors and two baros on isolated domains and separate buses, BMM150 mag, operating and storage -40 to 85 C.
- 3. mRo (mRobotics), Control Zero H7 user guide, specifications tableRetrieved: 2026-08-15 · Specifications table: STM32H743 480 MHz, 1 MB RAM, 2 MB flash, 256 kb FRAM, three accel and gyro, one mag, one DPS310 baro, 8 PWM, 1 CAN, 6 UART, custom carrier board support No, 5.3 g, 20 x 32 mm.