| Full-size H7 autopilot board | Uses an STM32H7-family processor; some members of this family operate at up to 480 MHz. ArduPilot or PX4 support depends on the exact board and its firmware target. | Often provides multiple UARTs, sensor connections, and sometimes CAN; motor-output count and output protocols vary by board. | Well suited to larger multirotor frames when the controller supports the required motor layout and the frame has room for the board and wiring. | Confirm the board’s mounting holes, power-input range, and supported firmware target. Set the frame type, motor order, output functions, and failsafe behavior before flight. | GPS-assisted builds, larger aircraft, and projects needing extensive telemetry or peripheral connections. |
| Compact H7 multirotor board | Uses an H7-family processor, but compact boards differ in available memory, sensor layout, and firmware support. Check the exact target rather than relying on processor family alone. | Usually offers a capable processor with fewer connectors or less expansion space than a full-size autopilot board. | Can fit Tarot-style frames if the mounting pattern, board dimensions, and stack height match the frame’s electronics bay. | Measure the available plate area and check connector clearance. Use vibration isolation when appropriate, and keep the compass away from high-current wiring. | Builds needing strong processing capability in a restricted installation space. |
| F7 multirotor flight controller | Uses an STM32F7-family processor; the family’s maximum clock rate is up to 216 MHz. Betaflight and iNav are common on supported targets; other firmware requires explicit board support. | Commonly provides several UARTs and multiple motor outputs, but the count, signal type, and peripheral support are board-specific. | Suitable for many quad, hexacopter, and other multirotor builds when the board’s outputs and firmware support the selected configuration. | Match the motor layout to the firmware configuration. Verify UART assignments for GPS, receiver, telemetry, and digital video systems before wiring. | General-purpose multirotors needing a balance of processing capability, size, and peripheral support. |
| F4 multirotor flight controller | Uses an STM32F4-family processor; clock speed and memory depend on the specific chip. Many boards support established Betaflight or iNav targets, but support varies by model. | Often has fewer spare resources or peripheral connections than newer H7 designs; check the board documentation for available UARTs and outputs. | Can control a Tarot-style multirotor if its output count, firmware target, and mounting arrangement meet the build requirements. | Confirm that the required firmware version still supports the exact target. Plan serial-port use carefully, especially when adding GPS, telemetry, or other peripherals. | Cost-conscious or simpler builds that do not require many peripherals or advanced processing features. |
| Flight-controller and ESC all-in-one board | Processor and firmware depend on the integrated board; common designs use F4, F7, or H7 processors. Confirm support for the exact board target and ESC protocol. | Combines the flight controller with electronic speed controllers, reducing separate power and signal wiring. Current rating and motor-output count are model-specific. | Useful where the airframe has limited electronics space, provided the integrated ESCs are rated for the chosen motors, propellers, battery, and cooling conditions. | Check continuous-current ratings, battery voltage limits, cooling airflow, and connector polarity. Keep high-current wiring secure and follow the board’s power-supply instructions. | Compact builds prioritizing fewer components and simpler wiring over modular replacement. |