# Holybro Pix32 v5

:::warning PX4 does not manufacture this (or any) autopilot. Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues. :::

[Pix32 v5](https://holybro.com/products/pix32-v5)® is an advanced autopilot flight controller designed and made by Holybro®. It is optimized to run on PX4 firmware, which is intended for both academic and commercial developers. It is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv5** open hardware design and runs PX4 on the [NuttX](https://nuttx.apache.org/) OS. It can be regarded as a variant version of Pixhawk4.

The Pix32 v5 is designed for pilots who need a high power, flexible and customisable flight control system. It is comprised of a separate flight controller and carrier (base) board, which are connected by a 100pin connector. This design allows users to either select a base board made by Holybro, or customize their own.

![Pix32 v5 Family](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-725ba215912102b96c18a59ca8d8464a43ad44cf%2Fpix32_v5_family.jpg?alt=media)

:::note This flight controller is [manufacturer supported](https://px4.gitbook.io/px4-user-guide/drone_parts/flight_controller/autopilot_manufacturer_supported). :::

## Quick Summary

* Main FMU Processor: STM32F765
  * 32 Bit Arm® Cortex®-M7, 216MHz, 2MB memory, 512KB RAM
* IO Processor: STM32F100
  * 32 Bit Arm® Cortex®-M3, 24MHz, 8KB SRAM
* On-board sensors:
  * Accel/Gyro: ICM-20689
  * Accel/Gyro: BMI055 or ICM20602
  * Magnetometer: IST8310
  * Barometer: MS5611
* GPS: u-blox Neo-M8N GPS/GLONASS receiver; integrated magnetometer IST8310
* Interfaces:
  * 8-16 PWM outputs (8 from IO, 8 from FMU)
  * 3 dedicated PWM/Capture inputs on FMU
  * Dedicated R/C input for CPPM
  * Dedicated R/C input for Spektrum / DSM and S.Bus with analog / PWM RSSI input
  * Dedicated S.Bus servo output
  * 5 general purpose serial ports
    * 2 with full flow control
    * 1 with separate 1.5A current limit
  * 3 I2C ports
  * 4 SPI buses
    * 1 internal high speed SPI sensor bus with 4 chip selects and 6 DRDYs
    * 1 internal low noise SPI bus dedicated for
    * Barometer with 2 chip selects, no DRDYs
    * 1 internal SPI bus dedicated for FRAM
    * Supports dedicated SPI calibration EEPROM located on sensor module
    * 1 external SPI buses
  * Up to 2 CANBuses for dual CAN with serial ESC
    * Each CANBus has individual silent controls or ESC RX-MUX control
    * Analog inputs for voltage / current of 2 batteries
    * 2 additional analog inputs
* Electrical System:
  * Power module output: 4.9\~5.5V
  * Max input voltage: 6V
  * Max current sensing: 120A
  * USB Power Input: 4.75\~5.25V
  * Servo Rail Input: 0\~36V
* Weight and Dimensions:
  * Dimensions: 45x45x13.5mm
  * Weight: 33.0g
* Environmental Data, Quality & Reliability:
  * Operating temperature: -40 \~ 85°c
  * Storage temp. -40\~85℃
  * CE
  * FCC
  * RoHS compliant (lead-free)

Additional information can be found in the [Pix32 V5 Technical Data Sheet](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5_technical_data_sheet_v1.1.pdf).

## Where to Buy

Order from [Holybro website](https://holybro.com/products/pix32-v5).

## Assembly/Setup

The [Pix32 v5 Wiring Quick Start](https://px4.gitbook.io/px4-user-guide/assembly/quick_start_holybro_pix32_v5) provides instructions on how to assemble required/important peripherals including GPS, Power Management Board etc.

## Base Board Layouts

![Pix32 v5 Image](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-7c10f8f22cf78d494c5849c9c2e9e9bb3f62427a%2Fpix32_v5_base_boards_layout.jpg?alt=media)

## Pinouts

[*pix32 v5* and mini baseboard](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_Pix32-V5-Base-Mini-Pinouts.pdf)

## Dimensions

![Pix32 v5 Image](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-c12df77ed19d63cbb81ebd8959e3b8a07ed3df5b%2FDimensions_no_border.jpg?alt=media)

## Voltage Ratings

*Pix32 v5* can be triple-redundant on the power supply if three power sources are supplied. The three power rails are: **POWER1**, **POWER2** and **USB**.

:::note The output power rails **FMU PWM OUT** and **I/O PWM OUT** (0V to 36V) do not power the flight controller board (and are not powered by it). You must supply power to one of **POWER1**, **POWER2** or **USB** or the board will be unpowered. :::

**Normal Operation Maximum Ratings**

Under these conditions all power sources will be used in this order to power the system:

1. **POWER1** and **POWER2** inputs (4.9V to 5.5V)
2. **USB** input (4.75V to 5.25V)

**Absolute Maximum Ratings**

Under these conditions the system will not draw any power (will not be operational), but will remain intact.

1. **POWER1** and **POWER2** inputs (operational range 4.1V to 5.7V, 0V to 10V undamaged)
2. **USB** input (operational range 4.1V to 5.7V, 0V to 6V undamaged)
3. Servo input: VDD\_SERVO pin of **FMU PWM OUT** and **I/O PWM OUT** (0V to 42V undamaged)

## Building Firmware

:::tip Most users will not need to build this firmware! It is pre-built and automatically installed by *QGroundControl* when appropriate hardware is connected. :::

To [build PX4](https://px4.gitbook.io/px4-user-guide/development/getting_started/building_px4) for this target:

```
make holybro_pix32v5_default
```

## Debug Port

The system's [serial console](https://px4.gitbook.io/px4-user-guide/development/debug/consoles/system_console) and SWD interface runs on the **FMU Debug** port

![FMU debug port diagram](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-f3897ce19e73458f92be8558e6450370240366fd%2FFMU_Debug_Port_Horizontal.jpg?alt=media)

The pinout uses the standard [Pixhawk Debug Mini](https://px4.gitbook.io/px4-user-guide/development/debug/gdb_debugging/swd_debug#pixhawk-debug-mini) interface defined in the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf).

## Peripherals

* [Digital Airspeed Sensor](https://px4.gitbook.io/px4-user-guide/drone_parts/peripherals/airspeed)
* [Telemetry Radio Modules](https://px4.gitbook.io/px4-user-guide/drone_parts/peripherals/telemetry)
* [Rangefinders/Distance sensors](https://px4.gitbook.io/px4-user-guide/drone_parts/peripherals/rangefinders)

## Supported Platforms / Airframes

Any multicopter / airplane / rover or boat that can be controlled with normal RC servos or Futaba S-Bus servos. The complete set of supported configurations can be seen in the [Airframes Reference](https://px4.gitbook.io/px4-user-guide/airframes/airframe_reference).

## Additional Information

* [Pix32 v5 Technical Data Sheet](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5_technical_data_sheet_v1.1.pdf)
* [Pix32 v5 Pinouts](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_Pix32-V5-Base-Mini-Pinouts.pdf)
* [Pix32 v5 Base Board Schematic Diagram](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5-BASE-Schematic_diagram.pdf)
* [Pix32 v5 Mini Base Board Schematic Diagram](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Holybro_PIX32-V5-Base-Mini-Board_Schematic_diagram.pdf)
* [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165).


---

# Agent Instructions: 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:

```
GET https://px4.gitbook.io/px4-user-guide/drone_parts/flight_controller/autopilot_manufacturer_supported/holybro_pix32_v5.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.