> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/autopilot/kakute-f405-wing-mini/overview.md).
# Overview
### Features
* STM32F405 MCU running at 168 MHz
* High-Precision / low-noise ICM-42688-P IMU
* 2 On-board BEC output 5V, 5V/7.2V
* On-board voltage & current sensor
* Integrated SPL06 barometer
* I2C port Support
* Small & low-profile design fits into compact frames
* Supports INAV (7.1.2 & later), Ardupilot (4.5.6 & later), Betaflight (4.5.2 & later)
### Specifications
* MCU: STM32F405RGT6, 168 MHz, 192KB RAM, 1MB Flash
* IMU: ICM-42688P (SPI1)
* Baro: SPL06 (I2C2)
* OSD: AT7456E (SPI2)
* Onboard Blackbox: 128Mbits (SPI3)
* 5x Uarts (1,2,3,5,6) and R3 is with built-in inversion
* 7x PWM output, PWM7 used for NeoPixel LED by default
* 2x ADC (Bat1/Curr1)
* 1x I2C (the I2C2 is for external devices, also for onboard sensors)
* 2x LEDs for FC STATUS (Blue) and 3.3V indicator (Green)
* USB/DFU Key Extender with USB Type-C
* High-precision Current Sense (110A continuous, 132A peak)
* Battery Voltage Sensor: 1K:10K (Scale 1100 in INAV, BATT\_VOLT\_MULT 11 in ArduPilot, Scale 110 in Betaflight)
* Static power 110mA @5V
### **Power Board**
* Input voltage range: 7.4\~ 36V (2\~ 8S LiPo)
* 2x ESC power pads
* Current Sense: 110A continuous, 132A peak. (Scale 250 in INAV, 40 A/V in ArduPilot,Scale 250in Betaflight)
### **BEC 5V output**
* Designed for FC, Receiver, OSD, Camera, 2812 LED Strip, GPS,Telemetry,etc.
* Output 5.3 +/- 0.1V DC
* Continuous current 3 Amps, 4.8A Peak
### **BEC VS output**
* Designed for Servos
* Voltage adjustable, 5.3V Default, 7.2V option with Jumper pad
* Continuous current 3 Amps, 4.8A Peak
### **BEC 3.3V output**
* Linear Regulator
* Continuous current: 150mA
### **Mechanical**
* Mounting: 20 x 20mm, M2 hole
* Dimensions: 25x 30 x 20 mm
* Weight: 17g with USB extension board
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.holybro.com/autopilot/kakute-f405-wing-mini/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.