mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-10-18 07:43:33 +08:00
Link fixes galore (#25151)
This commit is contained in:
Hamish Willee
@@ -77,7 +77,7 @@ The board is based on the [Pixhawk project](https://pixhawk.org/) **FMUv2** open
|
||||
- [FMUv2 + IOv2 schematic](https://raw.githubusercontent.com/PX4/Hardware/master/FMUv2/PX4FMUv2.4.5.pdf) -- Schematic and layout
|
||||
|
||||
::: info
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/PX4/Hardware).
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/pixhawk/Hardware).
|
||||
:::
|
||||
|
||||
## Serial Port Mapping
|
||||
|
||||
@@ -1,9 +1,5 @@
|
||||
# Discontinued Autopilots/Vehicles
|
||||
|
||||
:::tip
|
||||
For more information about PX4 project autopilot board support levels see: [px4.io/autopilots/](https://px4.io/autopilots/).
|
||||
:::
|
||||
|
||||
This category is for discontinued autopilots and complete vehicles.
|
||||
These are no longer being manufactured, and may not be supported by their manufacturer.
|
||||
They are listed because you may be using them in an existing drone, and because they **may** still work with the head revision of PX4.
|
||||
@@ -13,6 +9,7 @@ They are listed because you may be using them in an existing drone, and because
|
||||
- [Drotek DroPix](../flight_controller/dropix.md) (FMUv2)
|
||||
- [Omnibus F4 SD](../flight_controller/omnibus_f4_sd.md)
|
||||
- [CUAV v5](../flight_controller/cuav_v5.md) (Pixhawk FMUv5)
|
||||
- [CUAV Pixhack v3](../flight_controller/pixhack_v3.md) (FMUv3)
|
||||
- [Aerotenna OcPoC-Zynq Mini](../flight_controller/ocpoc_zynq.md)
|
||||
- [Holybro Pixhawk 4 Mini](../flight_controller/pixhawk4_mini.md) (FMUv5)
|
||||
- [Holybro Kakute F7](../flight_controller/kakutef7.md)
|
||||
|
||||
@@ -15,13 +15,12 @@ The boards in this category are:
|
||||
- [AirMind MindPX](../flight_controller/mindpx.md)
|
||||
- [AirMind MindRacer](../flight_controller/mindracer.md)
|
||||
- [ARK Electronics ARKV6X](../flight_controller/ark_v6x.md) (and [ARK Electronics Pixhawk Autopilot Bus Carrier](../flight_controller/ark_pab.md))
|
||||
- [ARK FPV Flight Controller](../flight_controller/ark_fpv.md)
|
||||
- [ARK Pi6X Flow Flight Controller](../flight_controller/ark_pi6x.md)
|
||||
- [ARK FPV Flight Controller](../flight_controller/ark_fpv.md)
|
||||
- [ARK Pi6X Flow Flight Controller](../flight_controller/ark_pi6x.md)
|
||||
- [CUAV X7](../flight_controller/cuav_x7.md)
|
||||
- [CUAV Nora](../flight_controller/cuav_nora.md)（CUAV X7 variant)
|
||||
- [CUAV V5+](../flight_controller/cuav_v5_plus.md) (FMUv5)
|
||||
- [CUAV V5 nano](../flight_controller/cuav_v5_nano.md) (FMUv5)
|
||||
- [CUAV Pixhack v3](../flight_controller/pixhack_v3.md) (FMUv3)
|
||||
- [CubePilot Cube Orange+](../flight_controller/cubepilot_cube_orangeplus.md)
|
||||
- [CubePilot Cube Orange](../flight_controller/cubepilot_cube_orange.md)
|
||||
- [CubePilot Cube Yellow](../flight_controller/cubepilot_cube_yellow.md)
|
||||
|
||||
@@ -9,7 +9,7 @@ Contact the [manufacturer](https://beagleboard.org/blue) for hardware support or
|
||||
|
||||
[BeagleBone Blue](https://beagleboard.org/blue) is an all-in-one Linux-based computer.
|
||||
Although it is optimized for robotics, this compact and inexpensive board has all necessary sensors and peripherals needed by a flight controller.
|
||||
This topic shows how to set up the board to run PX4 with [librobotcontrol](https://github.com/StrawsonDesign/librobotcontrol) robotics package.
|
||||
This topic shows how to set up the board to run PX4 with [librobotcontrol](https://github.com/beagleboard/librobotcontrol) robotics package.
|
||||
|
||||
|
||||
|
||||
@@ -77,7 +77,6 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
|
||||
|
||||
1. First set up _rsync_ (this is used to transfer files from the development computer to the target board over a network - WiFi or Ethernet).
|
||||
For _rsync_ over SSH with key authentication, follow the steps here (on the development machine):
|
||||
|
||||
1. Generate an SSH key if you have not previously done so:
|
||||
|
||||
```
|
||||
@@ -104,9 +103,7 @@ echo "PermitRootLogin yes" >> /etc/ssh/sshd_config && systemctl restart sshd
|
||||
1. Enter root password
|
||||
|
||||
1. Cross Compile Setup
|
||||
|
||||
1. Toolchain download
|
||||
|
||||
1. First install the toolchain into _/opt/bbblue_toolchain/gcc-arm-linux-gnueabihf_.
|
||||
Here is an example of using soft link to select which version of the toolchain you want to use:
|
||||
|
||||
@@ -208,6 +205,7 @@ Run the following commands on the BeagleBone Blue (i.e. via SSH):
|
||||
sudo apt-get update
|
||||
sudo apt-get install cmake python3-empy=3.3.4-2
|
||||
```
|
||||
|
||||
1. Clone the PX4 Firmware directly onto the BeagleBone Blue.
|
||||
1. Continue with the [standard build system installation](../dev_setup/dev_env_linux.md).
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ The V5 nano is similar to the [CUAV V5+](../flight_controller/cuav_v5_plus.md),
|
||||
|
||||
Some of its main features include:
|
||||
|
||||
- Full compatibility with the [Pixhawk project](https://pixhawk.org/) **FMUv5** design standard and uses the [Pixhawk Connector Standard](https://pixhawk.org/pixhawk-connector-standard/) for all external interfaces.
|
||||
- Full compatibility with the [Pixhawk project](https://pixhawk.org/) **FMUv5** design standard and uses the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) for all external interfaces.
|
||||
- More advanced processor, RAM and flash memory than FMU v3, along with more stable and reliable sensors.
|
||||
- Firmware-compatible with PX4.
|
||||
- Generous 2.6mm spacing for I/O pins, making it easier to use all the interfaces.
|
||||
@@ -31,7 +31,6 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
Main FMU Processor: STM32F765◦32 Bit Arm® Cortex®-M7, 216MHz, 2MB memory, 512KB RAM
|
||||
|
||||
- On-board sensors:
|
||||
|
||||
- Accel/Gyro: ICM-20689
|
||||
- Accel/Gyro: ICM-20602
|
||||
- Accel/Gyro: BMI055
|
||||
@@ -39,7 +38,6 @@ Main FMU Processor: STM32F765◦32 Bit Arm® Cortex®-M7, 216MHz, 2MB memory, 51
|
||||
- Barometer: MS5611
|
||||
|
||||
- Interfaces: 8 PWM outputs
|
||||
|
||||
- 3 dedicated PWM/Capture inputs on FMU
|
||||
- Dedicated R/C input for CPPM
|
||||
- Dedicated R/C input for Spektrum / DSM and S.Bus
|
||||
@@ -184,7 +182,7 @@ CUAV adopts some differentiated designs and is incompatible with some hardware,
|
||||
|
||||
The _Neo v2.0 GPS_ that is recommended for use with _CUAV V5+_ and _CUAV V5 nano_ is not fully compatible with other Pixhawk flight controllers (specifically, the buzzer part is not compatible and there may be issues with the safety switch).
|
||||
|
||||
The UAVCAN [NEO V2 PRO GNSS receiver](http://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html) can also be used, and is compatible with other flight controllers.
|
||||
The UAVCAN [NEO V2 PRO GNSS receiver](https://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html) can also be used, and is compatible with other flight controllers.
|
||||
|
||||
<a id="compatibility_jtag"></a>
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ The autopilot is recommended for commercial systems integration, but is also sui
|
||||
|
||||
Some of its main features include:
|
||||
|
||||
- Full compatibility with the [Pixhawk project](https://pixhawk.org/) **FMUv5** design standard and uses the [Pixhawk Connector Standard](https://pixhawk.org/pixhawk-connector-standard/) for all external interfaces.
|
||||
- Full compatibility with the [Pixhawk project](https://pixhawk.org/) **FMUv5** design standard and uses the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) for all external interfaces.
|
||||
- More advanced processor, RAM and flash memory than FMU v3, along with more stable and reliable sensors.
|
||||
- Firmware-compatible with PX4.
|
||||
- Modular design allows users to customize their own carrier board.
|
||||
@@ -32,7 +32,6 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
- IO Processor: STM32F100
|
||||
- 32 Bit Arm® Cortex®-M3, 24MHz, 8KB SRAM
|
||||
- On-board sensors:
|
||||
|
||||
- Accelerometer/Gyroscope: ICM-20689
|
||||
- Accelerometer/Gyroscope: BMI055
|
||||
- Magnetometer: IST8310
|
||||
@@ -57,7 +56,6 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
- Weight: 90g
|
||||
- Dimensions: 85.5\*42\*33mm
|
||||
- Other Characteristics:
|
||||
|
||||
- Operating temperature: -20 ~ 80°c（Measured value）
|
||||
|
||||
## Where to Buy
|
||||
@@ -201,7 +199,7 @@ CUAV adopts some differentiated designs and is incompatible with some hardware,
|
||||
|
||||
The _Neo v2.0 GPS_ recommended for use with _CUAV V5+_ and _CUAV V5 nano_ is not fully compatible with other Pixhawk flight controllers (specifically, the buzzer part is not compatible and there may be issues with the safety switch).
|
||||
|
||||
The UAVCAN [NEO V2 PRO GNSS receiver](http://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html) can also be used, and is compatible with other flight controllers.
|
||||
The UAVCAN [NEO V2 PRO GNSS receiver](https://doc.cuav.net/gps/neo-series-gnss/en/neo-v2-pro.html) can also be used, and is compatible with other flight controllers.
|
||||
|
||||
<a id="compatibility_jtag"></a>
|
||||
|
||||
@@ -235,7 +233,7 @@ Please do not connect other equipment (except RC receiver) on SBUS / DSM / RSSI
|
||||
## Further Information
|
||||
|
||||
- [CUAV V5+ Manual](http://manual.cuav.net/V5-Plus.pdf)
|
||||
- [CUAV V5+ docs](http://doc.cuav.net/flight-controller/v5-autopilot/en/v5+.html)
|
||||
- [CUAV V5+ docs](https://doc.cuav.net/controller/v5-autopilot/en/v5+.html)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165)
|
||||
- [CUAV Github](https://github.com/cuav)
|
||||
- [Base board design reference](https://github.com/cuav/hardware/tree/master/V5_Autopilot/V5%2B/V5%2BBASE)
|
||||
|
||||
@@ -19,7 +19,7 @@ This is automatically configured and enabled in the default PX4 firmware.
|
||||
Cube includes vibration isolation on two of the IMU's, with a third fixed IMU as a reference / backup.
|
||||
|
||||
:::tip
|
||||
The manufacturer [Cube Docs](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview) contain detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview#differences-between-cube-colours).
|
||||
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
|
||||
:::
|
||||
|
||||
## Key Features
|
||||
@@ -242,6 +242,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h
|
||||
|
||||
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
|
||||
- Cube Docs (Manufacturer):
|
||||
- [Cube Module Overview](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview)
|
||||
- [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual)
|
||||
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
|
||||
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
|
||||
|
||||
@@ -20,7 +20,7 @@ This is automatically configured and enabled in the default PX4 firmware.
|
||||
Cube includes vibration isolation on two of the IMU's, with a third fixed IMU as a reference / backup.
|
||||
|
||||
:::tip
|
||||
The manufacturer [Cube Docs](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview) contain detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview#differences-between-cube-colours).
|
||||
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
|
||||
:::
|
||||
|
||||
## Key Features
|
||||
@@ -247,6 +247,5 @@ Board schematics and other documentation can be found here: [The Cube Project](h
|
||||
|
||||
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
|
||||
- Cube Docs (Manufacturer):
|
||||
- [Cube Module Overview](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview)
|
||||
- [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual)
|
||||
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
|
||||
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
|
||||
|
||||
@@ -15,7 +15,7 @@ For example, a carrier board for a commercial inspection vehicle might include c
|
||||
Cube includes vibration isolation on two of the IMU's, with a third fixed IMU as a reference / backup.
|
||||
|
||||
:::tip
|
||||
The manufacturer [Cube Docs](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview) contain detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview#differences-between-cube-colours).
|
||||
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
|
||||
:::
|
||||
|
||||
## Key Features
|
||||
@@ -140,6 +140,5 @@ CAN1 and CAN2 silk screen on the Cube are flipped (CAN1 is CAN2 and vice versa).
|
||||
|
||||
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
|
||||
- Cube Docs (Manufacturer):
|
||||
- [Cube Module Overview](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview)
|
||||
- [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual)
|
||||
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
|
||||
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
|
||||
|
||||
@@ -211,7 +211,7 @@ The complete set of supported configurations can be seen in the [Airframes Refer
|
||||
## Pinouts
|
||||
|
||||
_Durandal_ pinouts are listed below.
|
||||
These can also be downloaded from [here](https://holybro.com/collections/autopilot-flight-controllers/products/Durandal-Pinouts).
|
||||
These can also be downloaded from [here](https://cdn.shopifycdn.net/s/files/1/0604/5905/7341/files/Durandal_Pinouts_v1.0.pdf?v=1693983344).
|
||||
|
||||
### Top Pinouts
|
||||
|
||||
@@ -422,4 +422,4 @@ These can also be downloaded from [here](https://holybro.com/collections/autopil
|
||||
|
||||
- [Durandal Wiring QuickStart](../assembly/quick_start_durandal.md)
|
||||
- [Durandal Technical Data Sheet](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Durandal_technical_data_sheet_90f8875d-8035-4632-a936-a0d178062077.pdf)
|
||||
- [Durandal Pinouts](https://holybro.com/collections/autopilot-flight-controllers/products/Durandal-Pinouts) (Holybro)
|
||||
- [Durandal Pinouts](https://cdn.shopifycdn.net/s/files/1/0604/5905/7341/files/Durandal_Pinouts_v1.0.pdf?v=1693983344) (Holybro)
|
||||
|
||||
@@ -13,7 +13,7 @@ It runs the PX4 flight stack on the [NuttX](https://nuttx.apache.org/) OS.
|
||||
|
||||
|
||||
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, schematics and design files should be [available here](https://github.com/PX4/Hardware).
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, schematics and design files should be [available here](https://github.com/pixhawk/Hardware).
|
||||
|
||||
:::tip
|
||||
The Holybro pix32 is software compatible with the [3DR Pixhawk 1](../flight_controller/pixhawk.md).
|
||||
@@ -90,7 +90,7 @@ The board is based on the [Pixhawk project](https://pixhawk.org/) **FMUv2** open
|
||||
- [FMUv2 + IOv2 schematic](https://raw.githubusercontent.com/PX4/Hardware/master/FMUv2/PX4FMUv2.4.5.pdf) -- Schematic and layout
|
||||
|
||||
::: info
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/PX4/Hardware).
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/pixhawk/Hardware).
|
||||
:::
|
||||
|
||||
## Serial Port Mapping
|
||||
|
||||
@@ -74,7 +74,7 @@ This is the silkscreen for the _Kakute F7_, showing the top of the board:
|
||||
|
||||
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
|
||||
Before PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
|
||||
Download the [kakutef7_bl.hex](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/kakutef7/kakutef7_bl_0b3fbe2da0.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
Download the [kakutef7_bl.hex](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/kakutef7/kakutef7_bl_0b3fbe2da0.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
@@ -74,12 +74,11 @@ This is the silkscreen for the _Kakute H7_, showing the top of the board:
|
||||
| M5 to M8 | Motor signal outputs (located in plug for use in 4-in-1 ESCs) | |
|
||||
| Boot | Bootloader button | |
|
||||
|
||||
|
||||
## PX4 Bootloader Update {#bootloader}
|
||||
|
||||
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
|
||||
Before PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
|
||||
Download the [kakuteh7_bl.hex](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/kakuteh7/holybro_kakuteh7_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
Download the [kakuteh7_bl.hex](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/kakuteh7/holybro_kakuteh7_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ The board can be bought from one of the following shops (for example):
|
||||
|
||||
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
|
||||
Before the PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
|
||||
Download the [holybro_kakuteh7mini_bootloader.hex](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/kakuteh7mini/holybro_kakuteh7mini_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
Download the [holybro_kakuteh7mini_bootloader.hex](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/kakuteh7mini/holybro_kakuteh7mini_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
@@ -77,7 +77,7 @@ The _Kakute H7v2_ is designed to work with the _Tekko32_ 4-in-1 ESC and they can
|
||||
|
||||
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
|
||||
Before the PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
|
||||
Download the [holybro_kakuteh7v2_bootloader.hex](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/kakuteh7v2/holybro_kakuteh7v2_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
Download the [holybro_kakuteh7v2_bootloader.hex](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/kakuteh7v2/holybro_kakuteh7v2_bootloader.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
@@ -44,7 +44,6 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
|
||||
- 3.3 and 6.6V ADC inputs
|
||||
- External microUSB port
|
||||
- Power System:
|
||||
|
||||
- Ideal diode controller with automatic failover
|
||||
- Servo rail high-power (7 V) and high-current ready
|
||||
- All peripheral outputs over-current protected, all inputs ESD protected
|
||||
@@ -99,8 +98,8 @@ See [3DR Pixhawk 1 > Pinouts](../flight_controller/pixhawk.md#pinouts)
|
||||
|
||||
The board is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv3** open hardware design.
|
||||
|
||||
- [FMUv3 schematic](https://github.com/PX4/Hardware/raw/master/FMUv3_REV_D/Schematic%20Print/Schematic%20Prints.PDF) -- Schematic and layout
|
||||
- [FMUv3 schematic](https://github.com/pixhawk/Hardware/raw/master/FMUv3_REV_D/Schematic%20Print/Schematic%20Prints.PDF) -- Schematic and layout
|
||||
|
||||
::: info
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/PX4/Hardware).
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/pixhawk/Hardware).
|
||||
:::
|
||||
|
||||
@@ -63,13 +63,13 @@ has a much smaller footprint. Major differences are updated sensors and Rev 3 FM
|
||||
By default a mRo X2.1 might come preconfigured for ArduPilot<sup>®</sup> rather than PX4. This
|
||||
can be seen during firmware update when the board is recognized as FMUv2 instead of X2.1.
|
||||
|
||||
In this case you must update the BootLoader using [BL_Update_X21.zip](https://github.com/PX4/PX4-user_guide/raw/main/assets/hardware/BL_Update_X21.zip).
|
||||
In this case you must update the BootLoader using [BL_Update_X21.zip](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/hardware/BL_Update_X21.zip).
|
||||
If this correction is not carried out your compass direction will be wrong and the
|
||||
secondary IMU will not be detected.
|
||||
|
||||
The update steps are:
|
||||
|
||||
1. Download and extract [BL_Update_X21.zip](https://github.com/PX4/PX4-user_guide/raw/main/assets/hardware/BL_Update_X21.zip).
|
||||
1. Download and extract [BL_Update_X21.zip](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/hardware/BL_Update_X21.zip).
|
||||
2. Find the folder _BL_Update_X21_. This contains a **bin** file and a subfolder named **/etc** containing an **rc.txt** file
|
||||
3. Copy these files to your micro SD card's root directory and insert it into the mRO x2.1
|
||||
4. Power on the mRO x2.1 Wait for it to boot and then reboot 1 time.
|
||||
|
||||
@@ -67,13 +67,11 @@ These are the boards tested and known to work:
|
||||
:::
|
||||
|
||||
Purchase from:
|
||||
|
||||
- [Hobbywing XRotor F4 Flight Controller w/OSD](https://www.getfpv.com/hobbywing-xrotor-f4-flight-controller-w-osd.html) (getfpv)
|
||||
|
||||
- Original Airbot Omnibus F4 SD
|
||||
|
||||
Purchase from:
|
||||
|
||||
- [Airbot (CN manufacturer)](https://store.myairbot.com/omnibusf4prov3.html)
|
||||
- [Ready To Fly Quads (US reseller)](https://quadsrtf.com/product/flip-32-f4-omnibus-rev-2/)
|
||||
|
||||
@@ -116,7 +114,6 @@ Some Omnibus F4 boards have a jumper connecting either or both the MCU SBUS and
|
||||
### UARTs
|
||||
|
||||
- UART6: GPS port
|
||||
|
||||
- TX: MCU pin PC6
|
||||
- RX: MCU pin PC7
|
||||
|
||||
@@ -125,7 +122,6 @@ Some Omnibus F4 boards have a jumper connecting either or both the MCU SBUS and
|
||||
|
||||
|
||||
- UART4
|
||||
|
||||
- TX: MCU pin PA0
|
||||
- RX: MCU pin PA1
|
||||
- 57600 baud
|
||||
@@ -227,7 +223,7 @@ The schematics are provided by [Airbot](https://myairbot.com/): [OmnibusF4-Pro-S
|
||||
|
||||
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
|
||||
Before PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
|
||||
Download the [omnibusf4sd_bl.hex](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/omnibus_f4_sd/omnibusf4sd_bl_d52b70cb39.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
Download the [omnibusf4sd_bl.hex](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/omnibus_f4_sd/omnibusf4sd_bl_d52b70cb39.hex) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
@@ -1,4 +1,10 @@
|
||||
# Pixhack V3
|
||||
# CUAV Pixhack V3 (Discontinued)
|
||||
|
||||
<Badge type="info" text="Discontinued" />
|
||||
|
||||
:::warning
|
||||
This flight controller has been [discontinued](../flight_controller/autopilot_experimental.md) and is no longer commercially available.
|
||||
:::
|
||||
|
||||
:::warning
|
||||
PX4 does not manufacture this (or any) autopilot.
|
||||
@@ -53,7 +59,6 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
|
||||
|
||||
The board can be purchased from:
|
||||
|
||||
- [store.cuav.net](http://store.cuav.net/index.php?id_product=8&id_product_attribute=0&rewrite=pixhack-v3-autopilot&controller=product&id_lang=3)
|
||||
- [leixun.aliexpress.com/store](https://leixun.aliexpress.com/store)
|
||||
|
||||
## Building Firmware
|
||||
@@ -65,13 +70,11 @@ It is pre-built and automatically installed by _QGroundControl_ when appropriate
|
||||
|
||||
To [build PX4](../dev_setup/building_px4.md) for this target:
|
||||
|
||||
```
|
||||
```sh
|
||||
make px4_fmu-v3_default
|
||||
```
|
||||
|
||||
## Pinouts and Schematics
|
||||
|
||||
- [Documentation/wiring guides](http://doc.cuav.net/flight-controller/pixhack/en/pixhack-v3.html)
|
||||
<!-- Pinouts and Schematics: section removed as guides no longer published -->
|
||||
|
||||
## Serial Port Mapping
|
||||
|
||||
@@ -80,6 +83,6 @@ make px4_fmu-v3_default
|
||||
| UART1 | /dev/ttyS0 | IO debug |
|
||||
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
|
||||
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
|
||||
| UART4 | |
|
||||
| UART7 | CONSOLE |
|
||||
| UART8 | SERIAL4 |
|
||||
| UART4 | | |
|
||||
| UART7 | | CONSOLE |
|
||||
| UART8 | | SERIAL4 |
|
||||
|
||||
@@ -11,7 +11,7 @@ We recommend however to consider products built on industry standards, such as t
|
||||
This flight controller is not following the standard and uses a patented connector.
|
||||
:::
|
||||
|
||||
The [Hex Cube Black](http://www.proficnc.com/61-system-kits2) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
|
||||
The [Hex Cube Black](https://docs.cubepilot.org/user-guides/autopilot/the-cube) flight controller (previously known as Pixhawk 2.1) is a flexible autopilot intended primarily for manufacturers of commercial systems.
|
||||
It is based on the [Pixhawk-project](https://pixhawk.org/) **FMUv3** open hardware design and runs PX4 on the [NuttX](https://nuttx.apache.org/) OS.
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ while a carrier board for a racer could includes ESCs form the frame of the vehi
|
||||
Cube includes vibration isolation on two of the IMU's, with a third fixed IMU as a reference / Backup.
|
||||
|
||||
::: info
|
||||
The manufacturer [Cube Docs](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview) contain detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview#differences-between-cube-colours).
|
||||
The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube) contains detailed information, including an overview of the [Differences between Cube Colours](https://docs.cubepilot.org/user-guides/autopilot/the-cube/introduction/specifications).
|
||||
:::
|
||||
|
||||
:::tip
|
||||
@@ -32,7 +32,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
|
||||
|
||||
## Key Features
|
||||
|
||||
- 32bit STM32F427 [Cortex-M4F](http://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4)<sup>®</sup> core with FPU
|
||||
- 32bit STM32F427 [Cortex-M4F](https://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4)<sup>®</sup> core with FPU
|
||||
- 168 MHz / 252 MIPS
|
||||
- 256 KB RAM
|
||||
- 2 MB Flash \(fully accessible\)
|
||||
@@ -61,7 +61,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
|
||||
|
||||
### Processor
|
||||
|
||||
- 32bit STM32F427 [Cortex M4](http://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4) core with FPU
|
||||
- 32bit STM32F427 [Cortex M4](https://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4) core with FPU
|
||||
- 168 MHz / 252 MIPS
|
||||
- 256 KB RAM
|
||||
- 2 MB Flash (fully accessible)
|
||||
@@ -166,6 +166,5 @@ CAN1 and CAN2 silk screen on the Cube Black are flipped (CAN1 is CAN2 and vice v
|
||||
|
||||
- [Cube Wiring Quickstart](../assembly/quick_start_cube.md)
|
||||
- Cube Docs (Manufacturer):
|
||||
- [Cube Module Overview](https://docs.cubepilot.org/user-guides/autopilot/the-cube-module-overview)
|
||||
- [Cube User Manual](https://docs.cubepilot.org/user-guides/autopilot/the-cube-user-manual)
|
||||
- [Cube User Guide](https://docs.cubepilot.org/user-guides/autopilot/the-cube)
|
||||
- [Mini Carrier Board](https://docs.cubepilot.org/user-guides/carrier-boards/mini-carrier-board)
|
||||
|
||||
@@ -60,7 +60,7 @@ Order mRo Pixhawk from:
|
||||
|
||||
### Processor
|
||||
|
||||
- 32bit STM32F427 [Cortex-M4F](http://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4) core with FPU
|
||||
- 32bit STM32F427 [Cortex-M4F](https://en.wikipedia.org/wiki/ARM_Cortex-M#Cortex-M4) core with FPU
|
||||
- 168 MHz
|
||||
- 256 KB RAM
|
||||
- 2 MB Flash
|
||||
@@ -119,7 +119,7 @@ Under these conditions the system will not draw any power (will not be operation
|
||||
[FMUv2 + IOv2 schematic](https://raw.githubusercontent.com/PX4/Hardware/master/FMUv2/PX4FMUv2.4.5.pdf) -- Schematic and layout
|
||||
|
||||
::: info
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/PX4/Hardware).
|
||||
As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files are [available](https://github.com/pixhawk/Hardware).
|
||||
:::
|
||||
|
||||
## Connections
|
||||
@@ -263,19 +263,19 @@ Due to space constraints two ports are on one connector.
|
||||
The [PX4 System Console](../debug/system_console.md) runs on the port labeled [SERIAL4/5](#serial-4-5-port).
|
||||
|
||||
:::tip
|
||||
A convenient way to connect to the console is to use a [Dronecode probe](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation), as it comes with connectors that can be used with several different Pixhawk devices.
|
||||
Simply connect the 6-pos DF13 1:1 cable on the [Dronecode probe](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation) to the Pixhawk `SERIAL4/5` port.
|
||||
A convenient way to connect to the console is to use a [Zubax BugFace BF1](https://github.com/Zubax/bugface_bf1), as it comes with connectors that can be used with several different Pixhawk devices.
|
||||
Simply connect the 6-pos DF13 1:1 cable on the [Zubax BugFace BF1](https://github.com/Zubax/bugface_bf1) to the Pixhawk `SERIAL4/5` port.
|
||||
|
||||
|
||||
|
||||
:::
|
||||
|
||||
The pinout is standard serial pinout, designed to connect to a [3.3V FTDI](https://www.digikey.com/en/products/detail/TTL-232R-3V3/768-1015-ND/1836393) cable (5V tolerant).
|
||||
|
||||
| 3DR Pixhawk 1 | | FTDI |
|
||||
| ------------- | --------- | ---- |
|
||||
| 1 | +5V (red) | | N/C |
|
||||
| 2 | S4 Tx | | N/C |
|
||||
| 3 | S4 Rx | | N/C |
|
||||
| ------------- | --------- | ---- | ---------------- |
|
||||
| 1 | +5V (red) | | N/C |
|
||||
| 2 | S4 Tx | | N/C |
|
||||
| 3 | S4 Rx | | N/C |
|
||||
| 4 | S5 Tx | 5 | FTDI RX (yellow) |
|
||||
| 5 | S5 Rx | 4 | FTDI TX (orange) |
|
||||
| 6 | GND | 1 | FTDI GND (black) |
|
||||
@@ -327,7 +327,7 @@ make px4_fmu-v2_default
|
||||
- JTAG Adapter Option #1: [BlackMagic Probe](https://1bitsquared.com/products/black-magic-probe). Note, may come without cables (check with manufacturer).
|
||||
If so, you will need the **Samtec FFSD-05-D-06.00-01-N** cable ([Samtec sample service](https://www.samtec.com/products/ffsd-05-d-06.00-01-n) or [Digi-Key Link: SAM8218-ND](http://www.digikey.com/product-search/en?x=0&y=0&lang=en&site=us&KeyWords=FFSD-05-D-06.00-01-N)) or [Tag Connect Ribbon](http://www.tag-connect.com/CORTEXRIBBON10) and a Mini-USB cable.
|
||||
- JTAG Adapter Option #2: [Digi-Key Link: ST-LINK/V2](https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND) / [ST USER MANUAL](http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/USER_MANUAL/DM00026748.pdf), needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
|
||||
- JTAG Adapter Option #3: [SparkFun Link: Olimex ARM-TINY](http://www.sparkfun.com/products/8278) or any other OpenOCD-compatible ARM Cortex JTAG adapter, needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
|
||||
- JTAG Adapter Option #3: [Olimex ARM-TINY](https://www.olimex.com/wiki/ARM-USB-TINY) or any other OpenOCD-compatible ARM Cortex JTAG adapter, needs an ARM Mini JTAG to 20pos adapter: [Digi-Key Link: 726-1193-ND](https://www.digikey.com/en/products/detail/texas-instruments/MDL-ADA2/1986451)
|
||||
- **USARTs**: Hirose DF13 6 pos ([Digi-Key Link: DF13A-6P-1.25H(20)](https://www.digikey.com/products/en?keywords=H3371-ND))
|
||||
- Mates: Hirose DF13 6 pos housing ([Digi-Key Link: Hirose DF13-6S-1.25C](https://www.digikey.com/products/en?keywords=H2182-ND))
|
||||
- **I2C and CAN**: Hirose DF13 4 pos ([Digi-Key Link: DF13A-4P-1.25H(20)](https://www.digikey.com/en/products/detail/hirose-electric-co-ltd/DF13A-4P-1-25H-20/530666) - discontinued)
|
||||
|
||||
@@ -49,7 +49,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
|
||||
- Other Characteristics:
|
||||
- Operating temperature: -40 ~ 85°c
|
||||
|
||||
Additional information can be found in the [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf).
|
||||
Additional information can be found in the [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-Autopilot/blob/main/docs/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf).
|
||||
|
||||
## Where to Buy
|
||||
|
||||
@@ -157,7 +157,7 @@ The complete set of supported configurations can be seen in the [Airframes Refer
|
||||
|
||||
## Further info
|
||||
|
||||
- [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf)
|
||||
- [Pixhawk 4 Technical Data Sheet](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixhawk4/pixhawk4_technical_data_sheet.pdf)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165).
|
||||
- [Pixhawk 4 Wiring QuickStart](../assembly/quick_start_pixhawk4.md)
|
||||
- [Pixhawk 4 Pinouts](https://cdn.shopify.com/s/files/1/0604/5905/7341/files/Pixhawk4-Pinouts.pdf) (Holybro)
|
||||
|
||||
@@ -50,7 +50,7 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
|
||||
- Other Characteristics:
|
||||
- Operating temperature: -40 ~ 85°c
|
||||
|
||||
Additional information can be found in the [_Pixhawk 4 Mini_ Technical Data Sheet](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4mini/pixhawk4mini_technical_data_sheet.pdf).
|
||||
Additional information can be found in the [_Pixhawk 4 Mini_ Technical Data Sheet](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixhawk4mini/pixhawk4mini_technical_data_sheet.pdf).
|
||||
|
||||
## Where to Buy
|
||||
|
||||
@@ -66,7 +66,7 @@ The **RC IN** and **PPM** ports are for RC receivers only. These are powered! NE
|
||||
|
||||
## Pinouts
|
||||
|
||||
Download _Pixhawk 4 Mini_ pinouts from [here](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4mini/pixhawk4mini_pinouts.pdf).
|
||||
Download _Pixhawk 4 Mini_ pinouts from [here](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixhawk4mini/pixhawk4mini_pinouts.pdf).
|
||||
|
||||
## Dimensions
|
||||
|
||||
@@ -120,7 +120,8 @@ In order to access these ports, the user must remove the _Pixhawk 4 Mini_ casing
|
||||
|
||||
|
||||
|
||||
The port has a standard serial pinout and can be connected to a standard FTDI cable (3.3V, but it's 5V tolerant) or a [Dronecode probe](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation). The pinout uses the standard [Pixhawk debug connector](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) pinout. Please refer to the [wiring](../debug/system_console.md) page for details of how to wire up this port.
|
||||
The port has a standard serial pinout and can be connected to a standard FTDI cable (3.3V, but it's 5V tolerant) or a [Zubax BugFace BF1](https://github.com/Zubax/bugface_bf1).
|
||||
The pinout uses the standard [Pixhawk debug connector](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) pinout. Please refer to the [wiring](../debug/system_console.md) page for details of how to wire up this port.
|
||||
|
||||
## Serial Port Mapping
|
||||
|
||||
@@ -153,5 +154,5 @@ It can be used for airframes that use AUX for non-essential peripherals (e.g. "f
|
||||
|
||||
## Further info
|
||||
|
||||
- [_Pixhawk 4 Mini_ Technical Data Sheet](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixhawk4mini/pixhawk4mini_technical_data_sheet.pdf)
|
||||
- [_Pixhawk 4 Mini_ Technical Data Sheet](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixhawk4mini/pixhawk4mini_technical_data_sheet.pdf)
|
||||
- [FMUv5 reference design pinout](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=912976165).
|
||||
|
||||
@@ -5,7 +5,7 @@ PX4 does not manufacture this (or any) autopilot.
|
||||
Contact the [manufacturer](https://holybro.com/) for hardware support or compliance issues.
|
||||
:::
|
||||
|
||||
The Holybro *Pixhawk<sup>®</sup> Mini* autopilot is a next-generation evolution of the Pixhawk.
|
||||
The Holybro _Pixhawk<sup>®</sup> Mini_ autopilot is a next-generation evolution of the Pixhawk.
|
||||
It is about 1/3rd the size of the original Pixhawk and has more powerful processors and sensors.
|
||||
|
||||
The Pixhawk Mini is based on the PX4 open-hardware project and has been optimized for the PX4 flight stack.
|
||||
@@ -117,7 +117,7 @@ The _Pixhawk Mini_ is shipped with the following contents:
|
||||
| Safety switch |  |
|
||||
| 8 Channel PWM Breakout cable |  |
|
||||
| Mounting foam |  |
|
||||
| I2C breakout board ? - not listed parts on handout | - |
|
||||
| I2C breakout board ? - not listed parts on handout | - |
|
||||
|
||||
## Optional accessories
|
||||
|
||||
@@ -263,7 +263,7 @@ Pixhawk Mini supports many different radio receiver models:
|
||||
|
||||
<img src="../../assets/flight_controller/pixhawk_mini/pixhawk_mini_port_rcin.png" width="350px" title="Pixhawk Mini - Radio port for PPM receivers" />
|
||||
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RCIN** port _via a PPM encoder_ [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
- PPM and PWM receivers that have an _individual wire for each channel_ must connect to the **RCIN** port _via a PPM encoder_ [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
|
||||
|
||||
For more information about selecting a radio system, receiver compatibility, and binding your transmitter/receiver pair, see: [Remote Control Transmitters & Receivers](../getting_started/rc_transmitter_receiver.md).
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ The [Pixhawk project](https://pixhawk.org/) creates open hardware designs in the
|
||||
Manufacturers are encouraged to take the [open designs](https://github.com/pixhawk/Hardware) and create products that are best suited to a particular market or use case (the physical layout/form factor not part of the open specification). Boards based on the same design are binary compatible.
|
||||
|
||||
::: info
|
||||
While a physical connector standard is not mandated, newer products generally follow the [Pixhawk Connector Standard](https://pixhawk.org/pixhawk-connector-standard/).
|
||||
While a physical connector standard is not mandated, newer products generally follow the [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf).
|
||||
:::
|
||||
|
||||
The project also creates reference autopilot boards based on the open designs, and shares them under the same [licence](#licensing-and-trademarks).
|
||||
@@ -89,9 +89,9 @@ At very high level, the main differences are:
|
||||
More CAN buses.
|
||||
Much more configurable & customizable.
|
||||
([Pixhawk 5X](../flight_controller/pixhawk5x.md), Skynode)
|
||||
- **FMUv6C:**
|
||||
- **FMUv6C:**
|
||||
([Holybro Pixhawk 6C Mini](../flight_controller/pixhawk6c_mini.md), [Holybro Pixhawk 6C](../flight_controller/pixhawk6c.md))
|
||||
- **FMUv6X:**
|
||||
- **FMUv6X:**
|
||||
([CUAV Pixhawk V6X](../flight_controller/cuav_pixhawk_v6x.md),[Holybro Pixhawk 6X](../flight_controller/pixhawk6x.md))
|
||||
- **FMUv6X-RT:** Faster MCU core (1GHz) (vs 480Mhz on 6X).
|
||||
More RAM (2Mb).
|
||||
|
||||
@@ -85,7 +85,7 @@ For more information see: [Pixracer Wiring Quickstart > External Telemetry](../a
|
||||
|
||||
## Connectors
|
||||
|
||||
All connectors follow the [Pixhawk connector standard](https://pixhawk.org/pixhawk-connector-standard/).
|
||||
All connectors follow the [Pixhawk connector standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf).
|
||||
Unless noted otherwise all connectors are JST GH.
|
||||
|
||||
## Pinouts
|
||||
@@ -204,8 +204,8 @@ The reference is provided as: [Altium Design Files](https://github.com/AUAV-Open
|
||||
|
||||
The following PDF files are provided for _convenience only_:
|
||||
|
||||
- [pixracer-rc12-12-06-2015-1330.pdf](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixracer/pixracer-rc12-12-06-2015-1330.pdf)
|
||||
- [pixracer-r14.pdf](https://github.com/PX4/PX4-user_guide/raw/main/assets/flight_controller/pixracer/pixracer-r14.pdf) - R14 or RC14 is printed next to the SDCard socket
|
||||
- [pixracer-rc12-12-06-2015-1330.pdf](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixracer/pixracer-rc12-12-06-2015-1330.pdf)
|
||||
- [pixracer-r14.pdf](https://github.com/PX4/PX4-Autopilot/raw/main/docs/assets/flight_controller/pixracer/pixracer-r14.pdf) - R14 or RC14 is printed next to the SDCard socket
|
||||
|
||||
## Building Firmware
|
||||
|
||||
|
||||
Reference in New Issue
Block a user