Mirrors_Framework/PX4-Autopilot
1
0
Fork 0
mirror of https://github.com/PX4/PX4-Autopilot.git synced 2026-05-26 01:17:51 +08:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

docs: auto-sync metadata [skip ci]

Browse Source 
Co-Authored-By: PX4 BuildBot <bot@px4.io>
This commit is contained in:
PX4BuildBot
2026-02-11 22:43:01 +00:00
parent 01b348c86b
commit 36b5e1e1bb
374 changed files with 12147 additions and 1765 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/flight_controller/airlink.md
+2 -10
View File
@@ -26,7 +26,6 @@ AIRLink has two computers and integrated LTE Module:
## Specifications
- **Sensors**
- 3x Accelerometers, 3x Gyroscopes, 3x Magnetometers, 3x Pressure sensorss
- GNSS, Rangefinders, Lidars, Optical Flow, Cameras
- 3x-redundant IMU
@@ -34,7 +33,6 @@ AIRLink has two computers and integrated LTE Module:
- Temperature stabilization
- **Flight Controller**
- STM32F7, ARM Cortex M7 with FPU, 216 MHz, 2MB Flash, 512 kB RAM
- STM32F1, I/O co-processor
- Ethernet, 10/100 Mbps
@@ -51,7 +49,6 @@ AIRLink has two computers and integrated LTE Module:
- Safety switch / LED option
- **AI Mission Computer**
- 6-Core CPU: Dual-Core Cortex-A72 + Quad-Core Cortex-A53
- GPU Mali-T864, OpenGL ES1.1/2.0/3.0/3.1
- VPU with 4K VP8/9, 4K 10bits H265/H264 60fps Decoding
@@ -65,7 +62,6 @@ AIRLink has two computers and integrated LTE Module:
- 2x Video: 4-Lane MIPI CSI (FPV Camera) and 4-Lane MIPI CSI with HMDI Input (Payload Camera)
- **LTE/5G Connectivity Module**
- Up to 600 Mbps bandwidth
- 5G sub-6 and mmWave, SA and NSA operations
- 4G Cat 20, up to 7xCA, 256-QAM DL/UL, 2xCA UL
@@ -142,7 +138,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
![Left side](../../assets/flight_controller/airlink/airlink-interfaces-left.jpg)
- **Left side interfaces:**
- Power input with voltage & current monitoring
- AI Mission Computer micro SD card
- Flight Controller micro SD card
@@ -169,12 +164,12 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
- **RC Connector - JST GH SM06B-GHS-TB**
| Pin number | Pin name | Direction | Voltage | Function |
| ---------- | -------- | --------- | ------- | ----------- |
| ---------- | -------- | --------- | ------- | ----------- | --- | --- | ------ |
| 1 | 5V | OUT | +5V | 5V output |
| 2 | PPM_IN | IN | +3.3V | PPM input |
| 3 | RSSI_IN | IN | +3.3V | RSSI input |
| 4 | FAN_OUT | OUT | +5V | Fan output |
| 5 | SBUS_OUT | OUT | +3.3V | SBUS output | 6 | GND | Ground |
| 5 | SBUS_OUT | OUT | +3.3V | SBUS output | 6 | GND | Ground |
* **FMU SD card - microSD**
@@ -183,7 +178,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
![Right side](../../assets/flight_controller/airlink/airlink-interfaces-right.jpg)
- **Right side interfaces:**
- Ethernet port with power output
- Telemetry port
- Second GPS port
@@ -247,7 +241,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
![Front side](../../assets/flight_controller/airlink/airlink-interfaces-front.jpg)
- **Front side interfaces:**
- Main GNSS and compass port
- Main telemetry port
- CSI camera input
@@ -305,7 +298,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
![Back side](../../assets/flight_controller/airlink/airlink-interfaces-back.jpg)
- **Rear side interfaces:**
- SBUS input
- 16 PWM output channels
- 2x LTE antenna sockets (MIMO)
docs/en/flight_controller/cuav_x25-evo.md
+13 -11
View File
@@ -83,7 +83,7 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
### Mechanical Data
- Not provided.
- Not provided.
## Purchase Channels
@@ -91,11 +91,11 @@ Order from [CUAV](https://store.cuav.net/).
## Assembly/Setup
- Not provided.
- Not provided.
## Pin Definitions
- Not provided.
- Not provided.
## Serial Port Mapping
@@ -112,11 +112,13 @@ Order from [CUAV](https://store.cuav.net/).
## Voltage Ratings
The _X25-EVO_ achieves triple redundancy on power supplies if three power sources are provided. The three power rails are POWERC1, POWERC2, and USB.
- **POWER C1** and **POWER C2** are DroneCAN/UAVCAN battery interfaces.
**Normal Operation Maximum Ratings**
Under these conditions, all power sources will be used to power the system in the following order:
1. **POWER C1** and **POWER C2** Inputs (10V to 18V)
2. USB Input (4.75V to 5.25V)
@@ -143,14 +145,14 @@ make cuav_x25-evo_default
The [PX4 System Console](../debug/system_console.md) and [SWD Interface](../debug/swd_debug.md) operate on the **FMU Debug** port.
| Pin | Signal | Volt |
| -------- | ---------------- | ----- |
| 1 (red) | 5V+ | +5V |
| 2 (blk) | DEBUG TX (OUT) | +3.3V |
| 3 (blk) | DEBUG RX (IN) | +3.3V |
| 4 (blk) | FMU_SWDIO | +3.3V |
| 5 (blk) | FMU_SWCLK | +3.3V |
| 6 (blk) | GND | GND |
| Pin | Signal | Volt |
| ------- | -------------- | ----- |
| 1 (red) | 5V+ | +5V |
| 2 (blk) | DEBUG TX (OUT) | +3.3V |
| 3 (blk) | DEBUG RX (IN) | +3.3V |
| 4 (blk) | FMU_SWDIO | +3.3V |
| 5 (blk) | FMU_SWCLK | +3.3V |
| 6 (blk) | GND | GND |
## Supported Platforms / Airframes
docs/en/flight_controller/gearup_airbrainh743.md
+10 -10
View File
@@ -39,20 +39,20 @@ The pin order is different from the Pixhawk standard (compatible to the Betaflig
Current UART configuration:
| UART | Device | Function |
| ------ | ---------- | ---------------------------- |
| USART1 | /dev/ttyS0 | Console/Debug |
| USART2 | /dev/ttyS1 | RC Input |
| USART3 | /dev/ttyS2 | TEL4 (DJI/MSP) |
| UART4 | /dev/ttyS3 | TEL1 |
| UART5 | /dev/ttyS4 | TEL2 |
| UART7 | /dev/ttyS5 | TEL3 (ESC Telemetry) |
| UART8 | /dev/ttyS6 | GPS1 |
| UART | Device | Function |
| ------ | ---------- | -------------------- |
| USART1 | /dev/ttyS0 | Console/Debug |
| USART2 | /dev/ttyS1 | RC Input |
| USART3 | /dev/ttyS2 | TEL4 (DJI/MSP) |
| UART4 | /dev/ttyS3 | TEL1 |
| UART5 | /dev/ttyS4 | TEL2 |
| UART7 | /dev/ttyS5 | TEL3 (ESC Telemetry) |
| UART8 | /dev/ttyS6 | GPS1 |
### Motor/Servo Outputs
| Connector | Pin | Function |
| ----------| ------------------ |
| --------- | --- | ------------ |
| ESC | M1 | Motor 1 |
| ESC | M2 | Motor 2 |
| ESC | M3 | Motor 3 |
docs/en/flight_controller/kakuteh7-wing.md
+10 -12
View File
@@ -1,4 +1,4 @@
# Holybro Kakute H743-Wing
# Holybro Kakute H743-Wing
<Badge type="tip" text="PX4 v1.16" />
@@ -9,7 +9,6 @@ Contact the [manufacturer](https://holybro.com/) for hardware support or complia
The [Holybro Kakute H743 Wing](https://holybro.com/products/kakute-h743-wing) is a fully featured flight controller specifically aimed at fixed-wing and VTOL applications. It has the STM32 H743 Processor running at 480 MHz and CAN Bus support, along with dual camera support & switch, ON/OFF Pit Switch, 5V, 6V/8V, 9V/12 BEC, and plug-and-play GPS, CAN, I2C ports.
::: info
This flight controller is [manufacturer supported](../flight_controller/autopilot_manufacturer_supported.md).
:::
@@ -20,7 +19,6 @@ The board can be bought from one of the following shops (for example):
- [Holybro](https://holybro.com/products/kakute-h743-wing)
## Connectors and Pins
| Pin | Function | PX4 default |
@@ -69,15 +67,15 @@ Firmware can be manually installed in any of the normal ways:
## Serial Port Mapping
| UART | Device | Port | Default function |
| ------ | ---------- | --------------------- | ---------------- |
| USART1 | /dev/ttyS0 | GPS 1 | GPS1 |
| USART2 | /dev/ttyS1 | R2, T2 | GPS2 |
| USART3 | /dev/ttyS2 | R3, T3 | TELEM1 |
| UART5 | /dev/ttyS3 | R5, T5 | TELEM2 |
| USART6 | /dev/ttyS4 | R6, (T6) | RC input |
| UART7 | /dev/ttyS5 | R7, T7, RTS, CTS | TELEM3 |
| UART8 | /dev/ttyS6 | R8, T8 | Console |
| UART | Device | Port | Default function |
| ------ | ---------- | ---------------- | ---------------- |
| USART1 | /dev/ttyS0 | GPS 1 | GPS1 |
| USART2 | /dev/ttyS1 | R2, T2 | GPS2 |
| USART3 | /dev/ttyS2 | R3, T3 | TELEM1 |
| UART5 | /dev/ttyS3 | R5, T5 | TELEM2 |
| USART6 | /dev/ttyS4 | R6, (T6) | RC input |
| UART7 | /dev/ttyS5 | R7, T7, RTS, CTS | TELEM3 |
| UART8 | /dev/ttyS6 | R8, T8 | Console |
## Debug Port
docs/en/flight_controller/pixhawk_series.md
+15 -15
View File
@@ -102,21 +102,21 @@ At very high level, the main differences are:
### FMUv6 Comparison
| Feature | **FMUv6X-RT** | **FMUv6X** | **FMUv6C** |
| ------------------ | --------------------- | ----------------- | ------------------ |
| **FMU MCU** | NXP i.MX RT1176 | STM32H753 | STM32H743V |
| **RAM** | 2 MB | 1 MB | 1 MB |
| **Flash** | 64 MB Octal SPI | 2 MB internal | 2 MB internal |
| **IO MCU** | STM32F103 | STM32F103 | STM32F103 |
| **Secure Element** | NXP SE051 | NXP SE051 | Not supported |
| **PAB Standard** | Supported | Supported | Not supported |
| **Ethernet** | Supported | Supported | Not supported |
| **IMUs** | 3× | 3× | 2× |
| **Barometers** | 2× | 2× | 1× |
| **Magnetometer** | 1× | 1× | 1× |
| **FMU PWM** | 12× | 8× | 8× |
| **IO PWM** | 8× | 8× | 8× |
| **CAN Bus** | 3× | 2× | 2× |
| Feature | **FMUv6X-RT** | **FMUv6X** | **FMUv6C** |
| ------------------ | --------------- | ------------- | ------------- |
| **FMU MCU** | NXP i.MX RT1176 | STM32H753 | STM32H743V |
| **RAM** | 2 MB | 1 MB | 1 MB |
| **Flash** | 64 MB Octal SPI | 2 MB internal | 2 MB internal |
| **IO MCU** | STM32F103 | STM32F103 | STM32F103 |
| **Secure Element** | NXP SE051 | NXP SE051 | Not supported |
| **PAB Standard** | Supported | Supported | Not supported |
| **Ethernet** | Supported | Supported | Not supported |
| **IMUs** | 3× | 3× | 2× |
| **Barometers** | 2× | 2× | 1× |
| **Magnetometer** | 1× | 1× | 1× |
| **FMU PWM** | 12× | 8× | 8× |
| **IO PWM** | 8× | 8× | 8× |
| **CAN Bus** | 3× | 2× | 2× |
### Licensing and Trademarks
docs/en/flight_controller/svehicle_e2.md
+1
View File
@@ -63,6 +63,7 @@ These flight controllers are [manufacturer supported](../flight_controller/autop
Order from [S-Vehicle](https://svehicle.cn/).
## Radio Control
A Radio Control (RC) system is required if you want to manually control your vehicle (PX4 does not require a radio system for autonomous flight modes).
You will need to select a compatible transmitter/receiver and then bind them so that they communicate (read the instructions that come with your specific transmitter/receiver).