MicoAir743 V2 flight controller and AM32 ESC stack on an electronics workbench

The Smaller Board Loses Bluetooth: MicoAir743 V2 AIO vs Stack

Quick Answer

Choose the MicoAir743 V2 AIO when a 25.5mm mount and one-board build matter more than expansion. Choose the 30.5mm stack for an onboard compass, Bluetooth telemetry, one extra UART, stronger BECs and replaceable ESC hardware. For an autonomous aircraft with several peripherals, we would buy the stack.

Same H743, Different Aircraft

The names make these boards sound interchangeable. They are not. Both use a 480MHz STM32H743 with 2MB flash, BMI088 and BMI270 dual IMUs, an SPL06 barometer and microSD logging, and both support ArduPilot, PX4, INAV and Betaflight. That shared core is why the real buying decision is physical layout and I/O, not processor speed.

Feature MicoAir743 V2 stack FC MicoAir743 V2 AIO 45A
Mounting 30.5 × 30.5mm 25.5 × 25.5mm
ESC Separate 55A or 70A AM32 option Integrated 4 × 45A AM32
Battery input 2–6S 3–6S
UARTs / PWM 8 / 11 7 / 9
Compass Onboard QMC5883L External compass required
Telemetry Onboard Bluetooth on UART8 No onboard Bluetooth
BEC outputs 5V 3A and 12V 3A 5V 2A and 12V 2A

Our catalogue offers the MicoAir743 V2 as an FC, 55A stack or 70A stack. That modularity matters: a burnt ESC does not force you to replace the flight controller, and the 30.5mm pattern belongs in roomy 7–10-inch or payload builds where GPS, telemetry and other sensors soon consume ports.

MicoAir743 V2 30.5mm flight controller and separate AM32 ESC stack
The stack separates the H743 flight controller from the high-current ESC and keeps more navigation I/O available.

Where the AIO Earns Its Place

The MicoAir743 V2 AIO 45A puts the H743 and four AM32 ESC channels on a 36 × 36 × 8mm, 10g board. MicoAir specifies 45A continuous per channel with good cooling, 3–6S input, DShot300/600 and bidirectional DShot support. The compact board still provides seven UARTs, eight motor outputs, a DJI O3/O4 connector and separate 5V and 12V rails.

MicoAir743 V2 AIO 45A H743 flight controller with integrated four-in-one ESC
The AIO removes the inter-board cable and 30.5mm ESC layer, but a power-stage failure takes the whole board out of service.

We would use the AIO for a compact 3.5–5-inch build where 45A per motor is genuinely enough and the wiring plan fits seven UARTs. Do not buy it merely because “AIO” sounds cleaner: ArduPilot users normally want an external GPS/compass, and the AIO has no onboard magnetometer. Read our broader AIO versus stack trade-off before committing the airframe layout.

The Detail We Would Check Before Powering Up

MicoAir's current manual says pin 1 of each board's HD-video connector supplies 12V, while the ArduPilot board page still describes 9V for the stack. That conflict is exactly why we check the board revision, silkscreen and pinout rather than trusting a copied wiring graphic. Never put that powered pin into a 5V-only camera, receiver or GPS.

Firmware naming deserves the same care. MicoAir's current ArduPilot resources direct both of these V2 boards to MicoAir743v2, even though the AIO product name suggests that it might have its own target; other MicoAir AIO generations do. If this is your first navigation build, follow our ArduPilot setup sequence, then confirm the downloaded hardware target, orientation, receiver input, voltage scaling and motor order with props removed. Browse the current MicoAir range only after the pin and current budget is written down.

What We Would Actually Buy

For an autonomous or long-range aircraft, the 30.5mm stack wins. Bluetooth setup, an onboard compass, eight UARTs and serviceable ESC options are worth the extra layer. We would reserve the AIO for a space-limited multirotor where its 25.5mm pattern solves a real packaging problem; otherwise the stack gives more room to grow.

FAQ

Q: Does the MicoAir743 V2 AIO use BLHeli_S?

A: MicoAir's current specification lists a 32-bit AM32 four-in-one ESC. The store URL contains an older “blheli_s” phrase, so use the live manufacturer specification and inspect the received board rather than inferring firmware from the slug.

Q: Can both boards run ArduPilot?

A: Yes, both have official MicoAir firmware resources for ArduPilot alongside PX4, INAV and Betaflight. Use the exact target for the board variant and preserve a parameter backup before changing firmware.

Q: Is 45A enough for a 6S build?

A: Voltage alone cannot answer that. Check the motor-and-prop test current, expected cooling and transient margin; choose the separate 55A or 70A stack when the measured load approaches the AIO's continuous rating.

Retour au blog