ChinaDroneRequest a quote →

SpeedyBee F405 V4 vs Holybro Kakute H7 Procurement Guide

Updated · 8 min read

Compare the F405 V4 with the full-size Kakute H7 V1.5 by firmware, sensor revision, peripheral power, serial ports, logging and frame fit.

Choose the SpeedyBee F405 V4 for a Betaflight or INAV build when its ports, regulated outputs and physical layout suit the equipment already on the frame. Give the full-size Holybro Kakute H7 V1.5 priority if the project calls for one board documented for Betaflight, INAV, ArduPilot and PX4, or if its smaller outline solves a fit problem. For this comparison, Kakute H7 means the full-size V1.5 unless a different revision is named. Ask for a photograph of the board marking before accepting a substitute. Even the logging medium changes between the V1 and V2 families.

Compare the board that goes into the frame

SpeedyBee F405 V4 vs Holybro Kakute H7 comparisonHolybro figures apply to full-size V1.5 unless otherwise indicated. Regulator ratings apply to the named voltage rail.
PartWhat to look forMatching products
Processor and gyroSpeedyBee uses STM32F405 and ICM-42688-P. Holybro V1.5 uses STM32H743 at 480 MHz and ICM-42688-P. V1.3 uses MPU6000.
Battery input and regulatorsF405 V4 accepts 3S–6S. Holybro lists 3S–8S for the V1.5 product. Their 5 V outputs are rated 3 A and 2 A respectively. Both list 3 A at 9 V.
UART allocationSpeedyBee reserves UART4 for Bluetooth and UART5 for ESC telemetry. Holybro lists UART1, 2, 3, 4, 6 and 7, with UART2 used on Bluetooth builds.
Frame fitF405 V4 is 41.6 × 39.4 × 7.8 mm and 10.5 g. H7 V1.5 is 35 × 35 mm and 8 g. Both have 4 mm holes on 30.5 × 30.5 mm centres.
Logging and firmwareBoth have microSD and support Betaflight and INAV. Holybro also lists ArduPilot and PX4 for Kakute H7 V1.5.

Send this list as it is and get one price for every part.

Quote the full parts list →

A flight controller and a stack are different purchasing units. SpeedyBee publishes the F405 V4 flight-controller specifications alongside those of a bundled four-in-one electronic speed controller. A current rating printed in the stack name describes the speed controller. It gives no indication of how much current the flight controller can supply to a camera, receiver or video transmitter. Ask for an itemized offer if a workshop already has speed controllers, and obtain the wiring diagram for each board in the proposed pair.

Start with the firmware and the workbench

For a club maintaining similar quads, a familiar firmware target can save time each time a board is replaced. SpeedyBee identifies SPEEDYBEEF405V4 as its target and lists Betaflight and INAV. Check that the planned release supports the features your existing configuration actually uses. Keep a copy of the settings from an approved sample and record the target and release alongside them. A technician should be able to identify the appropriate image from the board in hand, even after the carton has gone into storage.

For a teaching lab that uses several firmware projects, the Kakute H7 V1.5 offers a documented route to keeping a common board in the parts cupboard. Holybro lists all four projects and specifies Betaflight 4.5.2 or newer for V1.5. The change to the ICM-42688-P sensor matters if a course or workshop is committed to an older image. Have the instructor identify the required release before selecting the board. Budget bench time to check each firmware actually used in the course, including whether the operator can retrieve a useful log.

Processor choice alone is a weak basis for a purchase. A peripheral with nowhere to connect or a frame that blocks the USB socket can cost more workshop time than a faster processor saves. Ask the person who maintains the existing fleet what required rework on the last build. If the answer is cable access, insufficient space for a connector or confusion over revisions, take a bare frame and the actual cables to the sample review. These are all questions that can be settled before soldering production units.

Allocate ports and regulated power

Make a short list of devices that need serial communication. For each, record the port already assigned on the workshop's reference build and whether the device needs transmit, receive or both. The F405 V4 has six numbered UARTs, with UART4 assigned to onboard Bluetooth and UART5 to speed-controller telemetry. That leaves UART1, UART2, UART3 and UART6 for other assignments in the published layout. On a Bluetooth-equipped Kakute H7, UART2 serves Bluetooth telemetry. Holybro also lists a version without Bluetooth. Record which one the workshop expects if phone configuration is part of its service routine.

Need a quote for this? Tell us what you need →

Do the same exercise for power, recording each accessory under the voltage it requires. The F405 V4 has a total allowance of 3 A on its 5 V outputs and 3 A on its 9 V outputs. Several pads share each allowance. The H7 V1.5 lists 2 A continuous at 5 V and 3 A continuous at 9 V. An earlier H7 V1.2 has a lower 9 V rating. If the buyer plans to fit the same video equipment to both boards, check the accessory's input range and current requirement against the particular board revision, including its startup demand.

For a low-voltage project, ask Holybro to confirm the lower input limit for the exact revision. The V1 family pinout labels battery positive as 2S–8S, while the V1.5 product listing specifies 3S–8S. For a load approaching the 5 V regulator limit, also check the current allowed at the particular pad or connector that will supply it.

Before reusing a cable, compare its pin order at both ends with the drawings for the flight controller and accessory. A plug can fit the socket while carrying a different signal or supply voltage on an individual contact. Label the approved harness by the boards it joins. Request a second harness for the repair bench if cable damage is a common reason for bringing a quad in. This lets the technician isolate a cable fault without dismantling another aircraft to borrow its known working lead.

Check mechanical fit and log retrieval

Both boards use 30.5 mm square mounting centres, but the F405 V4 occupies a larger rectangle. Position a paper outline in the frame and add the actual USB plug, speed-controller harness and video lead. Check access with the top plate installed and the battery strap in its usual position. On the assembled sample, check that the dampers sit correctly and that a bent cable does not press against the board. A fit check that covers only the four screw holes misses the parts the technician needs to reach later.

Both the F405 V4 and H7 V1.5 accept removable media for Blackbox logs. SpeedyBee specifies SDSC or SDHC media below 32 GB, formatted FAT16 or FAT32, and describes a 4 GB recognition limit under Betaflight. Pick a specific card, create a sample log and open it using the workshop computer. Keep that card model on the approved parts list. A full-size H7 V2 uses onboard 128 MB flash instead. If a teaching exercise involves handing each student a physical card, a V2 substitution changes the exercise as well as the bill of materials.

Specify the destination and acceptance checks

Record the revision, Bluetooth option, controller-only or stack configuration, harnesses and mounting hardware for each delivery location. Ask the regional supplier to identify who handles service and what evidence the receiving technician needs to retain. When a supplier proposes another Kakute revision, compare the sensor, regulated outputs, storage and firmware requirements before accepting it. Where the order includes a radio or video transmitter, record that item's destination version separately so a controller substitution does not change the rest of the build unnoticed.

For a board-only order, list the electronics and cables actually packed. For a kit with LiPo batteries, give the forwarder each pack's label, watt-hour rating, count and packing arrangement and confirm acceptance for the intended route. An aircraft input range such as 3S to 6S tells the builder which pack voltages to consider. It cannot identify the energy or shipping configuration of a particular pack.

At receipt, compare the board markings with the offer and keep a photograph with the sample record. With propellers removed, have the technician confirm USB access, firmware target, sensor detection, peripheral assignments and a readable log using the intended configuration. Contact our team with your frame dimensions, battery cell count, peripheral list, firmware release and destination so the board and its accompanying hardware can be specified together.

Frequently asked questions

Which Kakute revision is compared here?

Full-size V1.5. Confirm the printed revision and Bluetooth option on the offered unit.

Can our V1.3 firmware image be reused on V1.5?

Verify the target and release first. Holybro specifies Betaflight 4.5.2 or later for V1.5.

Can two 5 V pads on SpeedyBee each supply 3 A?

The 3 A rating is shared across the 5 V outputs. Add up the loads on that rail.

Does the same mounting pattern guarantee fit?

Check the board outline, connector overhang, cable bends, card access and clearance under the frame plate.

Which full-size Kakute uses onboard flash for logs?

Holybro specifies 128 MB onboard flash for V2. The full-size V1 family uses an SD card.