danny wang 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans
..
README.md 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans
defaults.parm 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans
hwdef-bl.dat 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans
hwdef.dat 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans
pixhawk4-pinout.jpg 6b2cb6fa39 this N3 net clean robot use bfd1.5V6 il y a 2 ans

README.md

Pixhawk4 Flight Controller

The Pixhawk4 flight controller is sold by Holybro

Features

  • STM32F765 microcontroller
  • Two IMUs: ICM20689 and BMI055
  • MS5611 SPI barometer
  • builtin I2C IST8310 magnetometer
  • microSD card slot
  • 6 UARTs plus USB
  • 14 PWM outputs
  • Four I2C and two CAN ports
  • External Buzzer
  • external safety Switch
  • voltage monitoring for servo rail and Vcc
  • two dedicated power input ports for external power bricks

Pinout

Pixhawk4 Board

UART Mapping

  • SERIAL0 -> USB
  • SERIAL1 -> UART2 (Telem1)
  • SERIAL2 -> UART3 (Telem2)
  • SERIAL3 -> UART1 (GPS)
  • SERIAL4 -> UART4 (GPS2)
  • SERIAL5 -> UART6 (spare)
  • SERIAL6 -> UART7 (spare, debug)

The Telem1 and Telem2 ports have RTS/CTS pins, the other UARTs do not have RTS/CTS.

The UART7 connector is labelled debug, but is available as a general purpose UART with ArduPilot.

TELEM1, TELEM2 ports

Pin Signal Volt
1 (red) VCC +5V
2 (blk) TX (OUT) +3.3V
3 (blk) RX (IN) +3.3V
4 (blk) CTS +3.3V
5 (blk) RTS +3.3V
6 (blk) GND GND

GPS port

Pin Signal Volt
1 (red) VCC +5V
2 (blk) SERIAL3 TX (OUT) +3.3V
3 (blk) SERIAL3 RX (IN) +3.3V
4 (blk) SCL +3.3 (pullups)
5 (blk) SDA +3.3 (pullups)
6 (blk) SafetyButton +3.3V
7 (blk) SafetyLED +3.3V
8 (blk) VDD 3.3 (OUT) +3.3V
9 (blk) Buzzer +3.3V
10 (blk) GND GND

RC Input

RC input is configured on the port marked DSM/SBUS RC. This connector supports all RC protocols. Two cables are available for this port. To use software binding of Spektrum satellite receivers you need to use the Spektrum satellite cable.

PWM Output

The Pixhawk4 supports up to 16 PWM outputs. First first 8 outputs (labelled "MAIN") are controlled by a dedicated STM32F100 IO controller. These 8 outputs support all PWM output formats, but not DShot.

The remaining 8 outputs (labelled AUX1 to AUX8) are the "auxillary" outputs. These are directly attached to the STM32F765 and support all PWM protocols. The first 6 of the auxillary PWM outputs support DShot.

The 8 main PWM outputs are in 3 groups:

  • PWM 1 and 2 in group1
  • PWM 3 and 4 in group2
  • PWM 5, 6, 7 and 8 in group3

The 8 auxillary PWM outputs are in 2 groups:

  • PWM 1, 2, 3 and 4 in group1
  • PWM 5 and 6 in group2
  • PWM 7 and 8 in group3

Channels within the same group need to use the same output rate. If any channel in a group uses DShot then all channels in the group need to use DShot.

Battery Monitoring

The board has two dedicated power monitor ports on 6 pin connectors. The correct battery setting parameters are dependent on the type of power brick which is connected.

Compass

The Pixhawk4 has a builtin IST8310 compass. Due to potential interference the board is usually used with an external I2C compass as part of a GPS/Compass combination.

GPIOs

The 6 PWM ports can be used as GPIOs (relays, buttons, RPM etc). To use them you need to limit the number of these pins that is used for PWM by setting the BRD_PWM_COUNT to a number less than 6. For example if you set BRD_PWM_COUNT to 4 then PWM5 and PWM6 will be available for use as GPIOs.

The numbering of the GPIOs for PIN variables in ArduPilot is:

  • AUX1 50
  • AUX2 51
  • AUX3 52
  • AUX4 53
  • AUX5 54
  • AUX6 55

Analog inputs

The Pixhawk4 has 7 analog inputs

  • ADC Pin0 -> Battery Voltage
  • ADC Pin1 -> Battery Current Sensor
  • ADC Pin2 -> Battery Voltage 2
  • ADC Pin3 -> Battery Current Sensor 2
  • ADC Pin4 -> ADC port pin 2
  • ADC Pin14 -> ADC port pin 3
  • ADC Pin10 -> ADC 5V Sense
  • ADC Pin11 -> ADC 3.3V Sense
  • ADC Pin103 -> RSSI voltage monitoring

I2C Buses

  • the internal I2C port is bus 0 in ArduPilot (I2C3 in hardware)
  • the port labelled I2CA is bus 3 in ArduPilot (I2C4 in hardware)
  • the port labelled I2CB is bus 2 in ArduPilot (I2c2 in hardware)
  • the port labelled GPS is bus 1 in ArduPilot (I2c1 in hardware)

Pinout for I2CA

Pin Signal Volt
1 (red) VCC +5V
2 (blk) SCL +3.3 (pullups)
3 (blk) SDA +3.3 (pullups)
4 (blk) GND GND

Pinout for I2CB+UART

Pin Signal Volt
1 (red) VCC +5V
2 (blk) SERIAL4 TX (OUT) +3.3V
3 (blk) SERIAL4 RX (IN) +3.3V
4 (blk) SCL +3.3 (pullups)
5 (blk) SDA +3.3 (pullups)
6 (blk) GND GND

CAN

The Pixhawk4 has two independent CAN buses, with the following pinouts.

CAN1&2

Pin Signal Volt
1 (red) VCC +5V
2 (blk) CAN_H +12V
3 (blk) CAN_L +12V
4 (blk) GND GND

Debug

The Pixhawk4 supports SWD debugging on the debug port

Pin Signal Volt
1 (red) FMU VDD 3.3 +3.3V
2 (blk) UART TX Debug (OUT) +3.3V
3 (blk) UART RX Debug (IN) +3.3V
4 (blk) SWDIO +3.3V
5 (blk) SWCLK +3.3V
6 (blk) GND GND

Loading Firmware

The board comes pre-installed with an ArduPilot compatible bootloader, allowing the loading of *.apj firmware files with any ArduPilot compatible ground station.

Acknowledgements

Thanks to PX4 for images used under the CC-BY 4.0 license