CubePilot Cube Orange (autopilot module)

MCU IS DISPUTED BY TWO SOURCES and the published figure is recorded: ArduPilot's Cube Orange overview specification table says 'STM32H753', while ArduPilot's own build definition for the board (AP_HAL_ChibiOS/hwdef/CubeOrange/hwdef.dat) declares 'MCU STM32H7xx STM32H743xx'. Those are pin-compatible H7 parts differing in security blocks. The specification table wins and the build-time value is left here - the same treatment this corpus gives the BMP388/BMP390 split on the Rotor Riot Brave F7. The Cube is an autopilot-on-module: it carries no stack pattern and bolts to a published 80-pin DF17 carrier standard, so mount_pattern is the registry's 'Pixhawk' value rather than a hole spacing. CONSEQUENCE, RECORDED DELIBERATELY: it therefore bolts to NO frame in this library, because every frame here is an FPV bolt square and the Cube reaches the airframe through its carrier board. The stack chain will report mismatch against any of them, and that is the true answer rather than a modelling fault - what the zero really records is that the library holds no carrier-board airframe yet. chains.go predicted this exact case and kept 'Pixhawk' OUT of nonGeometricMounts for it. uart_count 5 and pwm_outputs 14 come from CubePilot's own specifications page, which states them as 'applies to all The Cubes' ('Five general-purpose serial ports; two with full flow control' and '14 PWM servo outputs (eight from I/O and six from FMU)') - a family-scoped vendor statement, not an inference from a sibling. motor_outputs is a DOCUMENTED ABSENCE (D109): the vendor never splits motor from servo for the Cube, and the ArduPilot hwdef does not either because outputs are assigned at runtime by SERVOn_FUNCTION - so no source states what can turn a propeller, and 14 would be a guess dressed as a fact. input_voltage_cells is a DOCUMENTED ABSENCE because the field does not apply: the Cube is fed regulated 5 V through the carrier board's POWER1/POWER2 bricks and has no battery-cell input of its own, so a cell count would describe the power brick and not this part. weight_g is a DOCUMENTED ABSENCE - CubePilot publishes no mass for the bare module. size_classes declared as all five per Stephan 2026-08-02 (declare all five, narrow only on evidence): nothing recorded about a carrier-mounted autopilot rules a size class out. One onboard compass (Cube Orange and Cube Yellow carry one; Black, Green and Blue carry two), three redundant IMUs and two barometers. Equipped with the CAN FD interface. Date Added 3/30/2023, read from the DIU capture. power_draw_w is a DOCUMENTED ABSENCE, not an open gap: CubePilot publishes only the power PINOUT - the 5 V rail the part is fed on - and never a consumption figure, on the module page, in the manual, or in ArduPilot's overview. What a board is SUPPLIED is not what it DRAWS, and no retailer checked publishes a draw either.

CubePilot autopilot module listed on the DIU Blue UAS Framework capture of 2026-01-23.