fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-05-18 10:37:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#25965)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-11-24 07:21:18 +11:00
committed by GitHub
parent 7f8d2b5067
commit faedf252b3
114 changed files with 462 additions and 427 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/actuators/index.md
+1 -1
View File
@@ -8,6 +8,6 @@
- [电调校准](../advanced_config/esc_calibration.md) — PWM 电调的校准 (DShot/CAN 电调/舵机不需要) 。
## See Also
## 另见
- [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。
docs/zh/advanced_config/ethernet_setup.md
+1 -1
View File
@@ -268,7 +268,7 @@ MAVSDK can connect to the PX4 on port `14550` if you don't modify the PX4 Ethern
accelerometer_integral_dt: 4997
```
## See Also
## 另见
- [Get The Pixhawk Raspberry Pi CM4 Baseboard By Holybro Talking With PX4](https://px4.io/get-the-pixhawk-raspberry-pi-cm4-baseboard-by-holybro-talking-with-px4/) (px4.io blog):
- 展示如何通过有线以太网连接 Pixhawk 6X + Raspberry Pi 到 CM4 主板。
docs/zh/advanced_config/index.md
+1 -1
View File
@@ -33,7 +33,7 @@
- [Bootloader 更新](../advanced_config/bootloader_update.md)
- [通过 USB 更新 FMUv6X-RT bootloader](../advanced_config/bootloader_update_v6xrt.md)
## See Also
## 另见
- [标准配置](../config/index.md) - 大多数 PX4 机体所需要的基本传感器/功能配置。
- [飞控外设](../peripherals/index.md) - 设置特定传感器、可选传感器、执行器等。
docs/zh/assembly/_assembly.md
+1 -1
View File
@@ -421,7 +421,7 @@ They recommend sensors, power systems, and other components from the same manufa
- [Pixracer Wiring Quickstart](../assembly/quick_start_pixracer.md)
- [mRo (3DR) Pixhawk Wiring Quickstart](../assembly/quick_start_pixhawk.md)
## See Also
## 另见
- [Drone Components & Parts](../getting_started/px4_basic_concepts.md#drone-components-parts) (Basic Concepts)
- [Payloads](../getting_started/px4_basic_concepts.md#payloads) (Basic Concepts)
docs/zh/camera/camera_architecture.md
+1 -1
View File
@@ -107,7 +107,7 @@ The logged topic will depend on whether or not the camera capture pin is enabled
Note that camera capture events are not logged when using the [MAVLink cameras that support Camera Protocol v2](../camera/mavlink_v2_camera.md), because the corresponding trigger events are not generated within PX4.
## See Also
## 另见
- Camera trigger driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_trigger) <!-- no module doc -->
- Camera capture driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_capture) <!-- no module doc -->
docs/zh/camera/fc_connected_camera.md
+1 -1
View File
@@ -310,7 +310,7 @@ Wire up your cameras to your AUX port by connecting the ground and signal pins t
You will have to modify your driver to follow the sequence diagram above.
Public reference implementations for [IDS Imaging UEye](https://github.com/ProjectArtemis/ueye_cam) cameras and for [IEEE1394 compliant](https://github.com/andre-nguyen/camera1394) cameras are available.
## See Also
## 另见
- Camera trigger driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_trigger) <!-- no module doc -->
- Camera capture driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_capture) <!-- no module doc -->
docs/zh/camera/index.md
+1 -1
View File
@@ -14,7 +14,7 @@ PX4 integrates with three types of cameras:
推荐[MAVLink 摄像头](../camera/mavlink_v2_camera.md)，因为它们使用简单一致的命令/消息集提供了最广泛的相机功能访问。
如果相机不支持该协议，则可以在一台机载计算机上运行[摄像机管理器](../camera/mavlink_v2_camera.md#camera-managers)以在 MAVLink 和相机的本机协议之间进行接口交互。
## See Also
## 另见
- [云台(相机支架)](../advanced/gimbal_control.md)
- [相机集成/架构](../camera/camera_architecture.md) ( PX4 开发者)
docs/zh/companion_computer/ark_jetson_pab_carrier.md
+1 -1
View File
@@ -89,6 +89,6 @@ To flash the kernel, connect the Jetson to your Host PC via Micro USB, and boot
![Jetson Carrier Flashing Guide](../../assets/companion_computer/ark_jetson_pab_carrier/ark_jetson_flashing_guide.png)
## See Also
## 另见
- [ARK Jetson PAB Documentation](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-jetson-pab-carrier) (ARK Docs)
docs/zh/companion_computer/holybro_pixhawk_jetson_baseboard.md
+1 -1
View File
@@ -1329,7 +1329,7 @@ You should see high frequency sensor messages as the output:
[sensor_combined_listener-1] accelerometer_integral_dt: 4999
```
## See Also
## 另见
- [Jetson carrier board Holybro Docs](https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard)
- [PX4 Middleware docs](../middleware/uxrce_dds.md#starting-the-client)
docs/zh/companion_computer/holybro_pixhawk_rpi_cm4_baseboard.md
+1 -1
View File
@@ -418,7 +418,7 @@ And such output is expected if everything is set up correctly:
[1731210066.597046] info | ProxyClient.cpp | create_datareader | datareader created | client_key: 0x00000001, datareader_id: 0x804(6), subscriber_id: 0x804(4)
```
## See Also
## 另见
- [Get The Pixhawk Raspberry Pi CM4 Baseboard By Holybro Talking With PX4](https://px4.io/get-the-pixhawk-raspberry-pi-cm4-baseboard-by-holybro-talking-with-px4/) (px4.io blog):
- 展示如何通过有线以太网连接 Pixhawk 6X + Raspberry Pi 到 CM4 主板。
docs/zh/complete_vehicles_fw/index.md
+1 -1
View File
@@ -35,7 +35,7 @@ This section lists vehicles that are sold fully assembled and ready to fly (RTF)
This section lists vehicles where you can update the software to run PX4.
-->
## See Also
## 另见
- [DIY Builds](../frames_plane/diy_builds.md)
- [Complete Vehicles (VTOL)](../complete_vehicles_vtol/index.md)
docs/zh/complete_vehicles_mc/index.md
+1 -1
View File
@@ -40,7 +40,7 @@ These may or may not be updatable to run "vanilla" PX4.
- [Yuneec H520](https://px4.io/project/yuneec-h520-hexacopter/)
- [AeroSense Aerobo (AS-MC02-P)](https://px4.io/project/aerosense-aerobo/)
## See Also
## 另见
- [Kits (MC)](../frames_multicopter/kits.md)
- [DIY Builds](../frames_multicopter/diy_builds.md)
docs/zh/complete_vehicles_vtol/index.md
+1 -1
View File
@@ -30,7 +30,7 @@ These may or may not be updatable to run "vanilla" PX4.
- [WingtraOne Tailsitter VTOL](https://px4.io/project/wingtraone-tailsitter-vtol/)
- [Flightwave Edge](https://px4.io/project/flywave-edge/)
## See Also
## 另见
- [Complete Vehicles (Fixed-Wing)](../complete_vehicles_fw/index.md)
- [Complete Vehicles (MC)](../complete_vehicles_mc/index.md)
docs/zh/config/index.md
+1 -1
View File
@@ -72,7 +72,7 @@ The video below shows most of the calibration process (it uses an older version
If you need help with the configuration you can ask for help on the [QGroundControl Support forum](https://discuss.px4.io/c/qgroundcontrol/qgroundcontrol-usage/18).
## See Also
## 另见
- [QGroundControl > Setup](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/setup_view.html)
- [飞控外设](../peripherals/index.md) - 设置特定传感器、可选传感器、执行器等。
docs/zh/config_mc/index.md
+1 -1
View File
@@ -161,7 +161,7 @@ My assumption is that the mixing system can cope with whatever geometry you thro
Yes but it must be physically feasible. E.g. if you make a quadrotor where all motors turn the same way it will "deal" with it but that cannot work without very specific controllers. Same for a monocopter or a tricopter without swiveling one motor.
-->
## See Also
## 另见
- [QGroundControl > Setup](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/setup_view.html)
- [飞控外设](../peripherals/index.md) - 设置特定传感器、可选传感器、执行器等。
docs/zh/data_links/index.md
+1 -1
View File
@@ -12,6 +12,6 @@ PX4 使用 [MAVLink](https://mavlink.io/en/) 协议在无线电频道上传送
- [TBS Crossfire (CRSF) Telemetry](../telemetry/crsf_telemetry.md) — TBS Crossfire 接收机上的遥测
- [Satellite Comms (Iridium/RockBlock)](../advanced_features/satcom_roadblock.md) — 高延迟卫星通信
## See Also
## 另见
- [安全配置 > 数据连接丢失的失效保护](../config/safety.md#data-link-loss-failsafe)
docs/zh/dev_log/logging.md
+1 -1
View File
@@ -186,6 +186,6 @@ There are different clients that support ulog streaming:
Also make sure `txerr` stays at 0.
Also make sure <code>txerr</code> stays at 0. If this goes up, either the NuttX sending buffer is too small, the physical link is saturated or the hardware is too slow to handle the data.
## See Also
## 另见
- [Encrypted logging](../dev_log/log_encryption.md)
docs/zh/dronecan/ark_cannode.md
+1 -1
View File
@@ -99,6 +99,6 @@ If you see a solid red LED there is an error and you should check the following:
- Make sure the ARK CANnode has `ark_cannode_canbootloader` installed prior to flashing `ark_cannode_default`.
- Remove binaries from the root and ufw directories of the SD card and try to build and flash again.
## See Also
## 另见
- [ARK CANnode Documentation](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-cannode) (ARK Docs)
docs/zh/dronecan/ark_flow.md
+1 -1
View File
@@ -133,6 +133,6 @@ If you see a solid red LED there is an error and you should check the following:
_PX4 holding position using the ARK Flow sensor for velocity estimation (in [Position Mode](../flight_modes_mc/position.md))._
## See Also
## 另见
- [ARK Flow](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-flow) (ARK Docs)
docs/zh/dronecan/ark_flow_mr.md
+1 -1
View File
@@ -128,6 +128,6 @@ If you see a solid red LED there is an error and you should check the following:
_PX4 holding position using the ARK Flow MR sensor for velocity estimation (in [Position Mode](../flight_modes_mc/position.md))._
## See Also
## 另见
- [ARK Flow MR](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-flow-mr) (ARK Docs)
docs/zh/dronecan/ark_gps.md
+1 -1
View File
@@ -112,6 +112,6 @@ If you see a red LED there is an error and you should check the following:
- Make sure the ARK GPS has `ark_can-gps_canbootloader` installed prior to flashing `ark_can-gps_default`.
- Remove binaries from the root and ufw directories of the SD card and try to build and flash again.
## See Also
## 另见
- [ARK GPS](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-gps) (ARK Docs)
docs/zh/dronecan/ark_mosaic__rtk_gps.md
+1 -1
View File
@@ -44,6 +44,6 @@ Order this module from:
- USA Built
- Supports DroneCAN Firmware Updating
## See Also
## 另见
- [ARK MOSAIC-X5 RTK GPS Documentation](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-mosaic-x5-rtk-gps) (ARK Docs)
docs/zh/dronecan/ark_rtk_gps.md
+1 -1
View File
@@ -200,6 +200,6 @@ ARK RTK GPS comes with the Ublox F9P module up to date with version 1.13 or newe
- "Firmware Update SUCCESS" should be displayed if it updated successfully
![Firmware Update](../../assets/hardware/gps/ark/ark_rtk_gps_ublox_f9p_firmware_update.png)
## See Also
## 另见
- [ARK RTK GPS Documentation](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-rtk-gps) (ARK Docs)
docs/zh/dronecan/ark_teseo_gps.md
+1 -1
View File
@@ -69,6 +69,6 @@ Order this module from:
| 5 | FMU_SWCLK | 3.3V |
| 6 | GND | GND |
## See Also
## 另见
- [ARK TESEO GPS Documentation](https://arkelectron.gitbook.io/ark-documentation/sensors/ark-teseo-gps) (ARK Docs)
docs/zh/flight_controller/accton-godwit_ga1.md
+1 -1
View File
@@ -80,7 +80,7 @@ This flight controller is [manufacturer supported](../flight_controller/autopilo
| ------- | --------- | ------ | ---------- |
| SERIAL1 | Telem1 | UART7 | /dev/ttyS6 |
| SERIAL2 | Telem2 | UART5 | /dev/ttyS4 |
| SERIAL3 | GPS1 | USART1 | /dev/ttyS0 |
| SERIAL3 | GPS1 | USART1 | UART |
| SERIAL4 | GPS2 | UART8 | /dev/ttyS7 |
| SERIAL5 | Telem3 | USART2 | /dev/ttyS1 |
| SERIAL6 | UART4 | UART4 | /dev/ttyS3 |
docs/zh/flight_controller/ark_pab.md
+1 -1
View File
@@ -320,6 +320,6 @@ For information about using this port see:
![ARKPAB Bottom Photo](../../assets/flight_controller/arkpab/ark_pab_back.jpg)
## See Also
## 另见
- [ARK Pixhawk Autopilot Bus Carrier](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-pixhawk-autopilot-bus-carrier) (ARK Docs)
docs/zh/flight_controller/ark_pi6x.md
+1 -1
View File
@@ -297,6 +297,6 @@ Order this module from:
| 21 | SDA0 | 3.3V |
| 22 | 3.3V_RPI | 3.3V |
## See Also
## 另见
- [ARK Pi6X Flow Documentation](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-pi6x-flow) (ARK Docs)
docs/zh/flight_controller/ark_v6x.md
+3 -3
View File
@@ -63,9 +63,9 @@ For pinout of the ARKV6X see the [DS-10 Pixhawk Autopilot Bus Standard](https://
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 & I2C |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
@@ -78,6 +78,6 @@ For pinout of the ARKV6X see the [DS-10 Pixhawk Autopilot Bus Standard](https://
make ark_fmu-v6x_default
```
## See Also
## 另见
- [ARK Electronics ARKV6X](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/arkv6x) (ARK Docs)
docs/zh/flight_controller/auav_x2.md
+8 -8
View File
@@ -82,11 +82,11 @@ As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
docs/zh/flight_controller/cuav_pixhawk_v6x.md
+10 -10
View File
@@ -122,16 +122,16 @@ The [Pixhawk V6X Wiring Quick Start](../assembly/quick_start_cuav_pixhawk_v6x.md
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
| UART7 | /dev/ttyS6 | TELEM1 |
| UART8 | /dev/ttyS7 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | -------- |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
| UART7 | /dev/ttyS6 | TELEM1 |
| UART8 | /dev/ttyS7 | GPS2 |
## 额定电压
docs/zh/flight_controller/cuav_v5.md
+4 -4
View File
@@ -122,12 +122,12 @@ The pinout is as shown.
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------------------------- |
| UART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | TELEM4 |
| USART6 | /dev/ttyS4 | TX is RC input from SBUS_RC connector |
| UART7 | /dev/ttyS5 | Debug Console |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | PX4IO |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/cuav_v5_nano.md
+4 -4
View File
@@ -134,12 +134,12 @@ For more information see [Using JTAG for hardware debugging](#using-jtag-for-har
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------------------------- |
| UART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | TELEM4 |
| USART6 | /dev/ttyS4 | TX is RC input from SBUS_RC connector |
| UART7 | /dev/ttyS5 | Debug Console |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | Not connected (no PX4IO) |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/cuav_v5_plus.md
+4 -4
View File
@@ -160,12 +160,12 @@ For more information see [Using JTAG for hardware debugging](#using-jtag-for-har
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------------------------- |
| UART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | TELEM4 |
| USART6 | /dev/ttyS4 | TX is RC input from SBUS_RC connector |
| UART7 | /dev/ttyS5 | Debug Console |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | PX4IO |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/cuav_x25-evo.md
+9 -9
View File
@@ -99,15 +99,15 @@ Order from [CUAV](https://store.cuav.net/).
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS1 |
| USART2 | /dev/ttyS1 | GPS2 |
| USART3 | /dev/ttyS2 | Debug Console |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | RC |
| UART7 | /dev/ttyS6 | TELEM1 |
| UART | 设备 | Port |
| ------ | ---------- | ------ |
| USART1 | UART | GPS1 |
| USART2 | /dev/ttyS1 | GPS2 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | RC |
| UART7 | /dev/ttyS6 | TELEM1 |
## 额定电压
docs/zh/flight_controller/cubepilot_cube_orange.md
+8 -8
View File
@@ -204,14 +204,14 @@ The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopi
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART2 | /dev/ttyS0 | TELEM1 (flow control) |
| USART3 | /dev/ttyS1 | TELEM2 (flow control) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| USART2 | UART | TELEM1 (流控) |
| USART3 | /dev/ttyS1 | TELEM2 (流控) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/cubepilot_cube_orangeplus.md
+8 -8
View File
@@ -205,14 +205,14 @@ The manufacturer [Cube User Guide](https://docs.cubepilot.org/user-guides/autopi
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART2 | /dev/ttyS0 | TELEM1 (flow control) |
| USART3 | /dev/ttyS1 | TELEM2 (flow control) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| USART2 | UART | TELEM1 (流控) |
| USART3 | /dev/ttyS1 | TELEM2 (流控) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/cubepilot_cube_yellow.md
+8 -8
View File
@@ -98,14 +98,14 @@ Board schematics and other documentation can be found here: [The Cube Project](h
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART2 | /dev/ttyS0 | TELEM1 (flow control) |
| USART3 | /dev/ttyS1 | TELEM2 (flow control) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| USART2 | UART | TELEM1 (流控) |
| USART3 | /dev/ttyS1 | TELEM2 (流控) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | PX4IO |
| UART7 | /dev/ttyS4 | CONSOLE/ADSB-IN |
| UART8 | /dev/ttyS5 | GPS2 |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/durandal.md
+9 -9
View File
@@ -168,15 +168,15 @@ make holybro_durandal-v1_default
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS1 |
| USART2 | /dev/ttyS1 | TELEM1 |
| USART3 | /dev/ttyS2 | TELEM2 |
| UART4 | /dev/ttyS3 | TELEM4/GPS2 |
| USART6 | /dev/ttyS4 | TELEM3 |
| UART7 | /dev/ttyS5 | Debug Console |
| UART8 | /dev/ttyS6 | PX4IO |
| UART | 设备 | Port |
| ------ | ---------- | ----------- |
| USART1 | UART | GPS1 |
| USART2 | /dev/ttyS1 | TELEM1 |
| USART3 | /dev/ttyS2 | TELEM2 |
| UART4 | /dev/ttyS3 | TELEM4/GPS2 |
| USART6 | /dev/ttyS4 | TELEM3 |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | PX4IO |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/holybro_pix32.md
+8 -8
View File
@@ -94,13 +94,13 @@ As a CC-BY-SA 3.0 licensed Open Hardware design, all schematics and design files
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/holybro_pix32_v6.md
+9 -9
View File
@@ -104,15 +104,15 @@ Order from [Holybro](https://holybro.com/products/pix32-v6).
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS1 |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| UART5 | /dev/ttyS3 | TELEM2 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | TELEM1 |
| UART8 | /dev/ttyS6 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | ------ |
| USART1 | UART | GPS1 |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART5 | /dev/ttyS3 | TELEM2 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | TELEM1 |
| UART8 | /dev/ttyS6 | GPS2 |
## 尺寸
docs/zh/flight_controller/kakutef7.md
+2 -2
View File
@@ -113,9 +113,9 @@ In addition to the [basic configuration](../config/index.md), the following para
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | TELEM1 |
| USART1 | UART | TELEM1 |
| USART2 | /dev/ttyS1 | TELEM2 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | ESC telemetry (DShot) |
docs/zh/flight_controller/kakuteh7-wing.md
+1 -1
View File
@@ -69,7 +69,7 @@ Firmware can be manually installed in any of the normal ways:
| UART | 设备 | Port | Default function |
| ------ | ---------- | --------------------------- | ---------------- |
| USART1 | /dev/ttyS0 | GPS 1 | GPS1 |
| USART1 | UART | GPS 1 | GPS1 |
| USART2 | /dev/ttyS1 | R2, T2 | GPS2 |
| USART3 | /dev/ttyS2 | R3, T3 | TELEM1 |
| UART5 | /dev/ttyS3 | R5, T5 | TELEM2 |
docs/zh/flight_controller/kakuteh7.md
+2 -2
View File
@@ -117,9 +117,9 @@ In addition to the [basic configuration](../config/index.md), the following para
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | TELEM1 |
| USART1 | UART | TELEM1 |
| USART2 | /dev/ttyS1 | TELEM2 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | ESC telemetry (DShot) |
docs/zh/flight_controller/kakuteh7mini.md
+2 -2
View File
@@ -124,9 +124,9 @@ In addition to the [basic configuration](../config/index.md), the following para
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | TELEM1 |
| USART1 | UART | TELEM1 |
| UART2 | /dev/ttyS1 | TELEM2 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | ESC telemetry (DShot) |
docs/zh/flight_controller/kakuteh7v2.md
+2 -2
View File
@@ -121,8 +121,8 @@ In addition to the [basic configuration](../config/index.md), the following para
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | TELEM1 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART1 | UART | TELEM1 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | ESC telemetry (DShot) |
docs/zh/flight_controller/micoair743-lite.md
+1 -1
View File
@@ -79,7 +79,7 @@ Pinouts definition can be found in the [MicoAir743-Lite_pinout.xlsx](https://raw
| UART | 设备 | Port |
| ------ | ---------- | ------ |
| USART1 | /dev/ttyS0 | TELEM1 |
| USART1 | UART | TELEM1 |
| USART2 | /dev/ttyS1 | GPS2 |
| USART3 | /dev/ttyS2 | GPS1 |
| UART4 | /dev/ttyS3 | TELEM2 |
docs/zh/flight_controller/mindpx.md
+9 -9
View File
@@ -111,15 +111,15 @@ You can also find MindRacer at Amazon<sup>&reg;</sup> or eBay<sup>&reg;</sup>.
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | RC |
| USART2 | /dev/ttyS1 | TELEM1 |
| USART3 | /dev/ttyS2 | TELEM2 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | ? |
| UART7 | /dev/ttyS5 | Debug Console |
| UART8 | /dev/ttyS6 | ? |
| UART | 设备 | Port |
| ------ | ---------- | ------ |
| USART1 | UART | RC |
| USART2 | /dev/ttyS1 | TELEM1 |
| USART3 | /dev/ttyS2 | TELEM2 |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | ? |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | ? |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/modalai_fc_v1.md
+1 -1
View File
@@ -130,7 +130,7 @@ make modalai_fc-v1
| UART | 设备 | Port |
| ------ | ---------- | ----------------------------------------------------------- |
| USART1 | /dev/ttyS0 | GPS1 (J10) |
| USART1 | UART | GPS1 (J10) |
| USART2 | /dev/ttyS1 | TELEM3 (J4) |
| USART3 | /dev/ttyS2 | Debug Console (J2) |
| UART4 | /dev/ttyS3 | Expansion UART (J6) |
docs/zh/flight_controller/modalai_voxl_flight.md
+1 -1
View File
@@ -186,7 +186,7 @@ _Note: mappings shown are for the PX4 controlled interfaces only_
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | GPS1 (J1012) |
| USART1 | UART | GPS1 (J1012) |
| USART2 | /dev/ttyS1 | TELEM3 (J1002) |
| USART3 | /dev/ttyS2 | Debug Console (J1001) |
| UART4 | /dev/ttyS3 | Expansion UART (J6) |
docs/zh/flight_controller/mro_control_zero_f7.md
+2 -2
View File
@@ -106,8 +106,8 @@ There is also an [ARM20-CTX 20-Pin to TC2030-IDC adapter](https://www.tag-connec
| UART | 设备 | Port |
| ------ | ---------- | -------------------------------------------------------------------------------------------------- |
| USART2 | /dev/ttyS0 | TELEM1 (flow control) |
| USART3 | /dev/ttyS1 | TELEM2 (flow control) |
| USART2 | UART | TELEM1 (流控) |
| USART3 | /dev/ttyS1 | TELEM2 (流控) |
| UART4 | /dev/ttyS2 | GPS1 |
| USART6 | /dev/ttyS3 | Flex port (can be configured as SPI or UART with Flow Control). |
| UART7 | /dev/ttyS4 | CONSOLE |
docs/zh/flight_controller/mro_pixhawk.md
+8 -8
View File
@@ -86,14 +86,14 @@ See [3DR Pixhawk 1 > Pinouts](../flight_controller/pixhawk.md#pinouts)
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/mro_x2.1.md
+1 -1
View File
@@ -111,7 +111,7 @@ The board is documented on the mRo hardware repo: [x21_V2_schematic.pdf](https:/
| UART | 设备 | Port |
| ------ | ---------- | --------------- |
| USART1 | /dev/ttyS0 | IO debug |
| USART1 | UART | IO debug |
| USART2 | /dev/ttyS1 | SERIAL1 |
| USART3 | /dev/ttyS2 | TELEM2 |
| UART4 | /dev/ttyS3 | GPS/I2C |
docs/zh/flight_controller/nxp_mr_vmu_rt1176.md
+1 -1
View File
@@ -182,7 +182,7 @@ _MR-VMU-RT1176_ connectors (following [Pixhawk Connector Standard](https://githu
| UART | 设备 | Port |
| ------ | ---------- | -------- |
| UART1 | /dev/ttyS0 | Debug |
| UART | UART | Debug |
| UART3 | /dev/ttyS1 | GPS |
| UART4 | /dev/ttyS2 | TELEM1 |
| UART5 | /dev/ttyS3 | GPS2 |
docs/zh/flight_controller/omnibus_f4_sd.md
+2 -2
View File
@@ -107,7 +107,7 @@ Below are silkscreens for the Hobbywing XRotor Flight Controller F4.
RC is connected to one of the following ports:
- UART1
- UART
- SBUS/PPM port (via inverter, internally goes to UART1)
:::info
@@ -164,7 +164,7 @@ Here is an example implementation. I used a Spektrum plug to get 3.3v from the D
| UART | 设备 | Port |
| ------ | ---------- | -------- |
| USART1 | /dev/ttyS0 | SerialRX |
| USART1 | UART | SerialRX |
| USART4 | /dev/ttyS1 | TELEM1 |
| USART6 | /dev/ttyS2 | GPS |
docs/zh/flight_controller/pixfalcon.md
+1 -1
View File
@@ -68,7 +68,7 @@ Developers will need to solder wires to the board test pads for SWD, and to the
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------------------- |
| UART1 | /dev/ttyS0 | IO Debug |
| UART | UART | IO Debug |
| USART2 | /dev/ttyS1 | TELEM1 (No flow control) |
| UART4 | /dev/ttyS2 | GPS |
docs/zh/flight_controller/pixhack_v3.md
+8 -8
View File
@@ -78,11 +78,11 @@ make px4_fmu-v3_default
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | | CONSOLE |
| UART8 | | SERIAL4 |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | | CONSOLE |
| UART8 | | SERIAL4 |
docs/zh/flight_controller/pixhawk-2.md
+9 -9
View File
@@ -124,15 +124,15 @@ Board schematics and other documentation can be found here: [The Cube Project](h
### 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | <!-- IO debug? --> |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | CONSOLE |
| UART8 | /dev/ttyS6 | <!-- unknown --> |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| USART1 | UART | <!-- IO debug? --> |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | CONSOLE |
| UART8 | /dev/ttyS6 | <!-- unknown --> |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/pixhawk.md
+8 -8
View File
@@ -245,14 +245,14 @@ Due to space constraints two ports are on one connector.
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | IO debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/pixhawk3_pro.md
+8 -8
View File
@@ -75,13 +75,13 @@ For information about wiring and using this port see:
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | WiFi |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | WiFi |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/pixhawk4.md
+9 -9
View File
@@ -75,15 +75,15 @@ The exception is the [debug port(s)](#debug_port) (pin 1 is the right-most, as s
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | /dev/ttyS3 | TELEM4 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | Debug Console |
| UART8 | /dev/ttyS6 | PX4IO |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | TELEM4 |
| USART6 | /dev/ttyS4 | RC SBUS |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | PX4IO |
## 尺寸
docs/zh/flight_controller/pixhawk4_mini.md
+1 -1
View File
@@ -129,7 +129,7 @@ The pinout uses the standard [Pixhawk debug connector](https://github.com/pixhaw
| UART | 设备 | QGC Parameter Description | Port Label on FC |
| :----: | :--------: | :-----------------------: | :-----------------------------------------: |
| UART1 | /dev/ttyS0 | GPS1 | GPS Module |
| UART | UART | GPS1 | GPS Module |
| USART2 | /dev/ttyS1 | TELEM1 | TELEM1 |
| USART3 | /dev/ttyS2 | TELEM2 | N/A |
| UART4 | /dev/ttyS3 | TELEM/SERIAL4 | UART/l2C B |
docs/zh/flight_controller/pixhawk5x.md
+2 -2
View File
@@ -140,9 +140,9 @@ Connector pin assignments are left to right (i.e. Pin 1 is the left-most pin).
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 & I2C |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
docs/zh/flight_controller/pixhawk6c.md
+9 -9
View File
@@ -110,15 +110,15 @@ The [Pixhawk 6C Wiring Quick Start](../assembly/quick_start_pixhawk6c.md) provid
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS1 |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| UART5 | /dev/ttyS3 | TELEM2 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | TELEM1 |
| UART8 | /dev/ttyS6 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | ------ |
| USART1 | UART | GPS1 |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART5 | /dev/ttyS3 | TELEM2 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | TELEM1 |
| UART8 | /dev/ttyS6 | GPS2 |
## 尺寸
docs/zh/flight_controller/pixhawk6c_mini.md
+2 -2
View File
@@ -111,7 +111,7 @@ Please refer to the [Pixhawk 4 Mini Wiring Quick Start](../assembly/quick_start_
| UART | 设备 | QGC Parameter Description | Port Label on FC |
| ------ | ---------- | ------------------------- | ---------------- |
| USART1 | /dev/ttyS0 | GPS1 | GPS1 |
| USART1 | UART | GPS1 | GPS1 |
| USART2 | /dev/ttyS1 | TELEM3 | N/A |
| USART3 | /dev/ttyS2 | N/A | FMU Debug |
| UART5 | /dev/ttyS3 | TELEM2 | TELEM2 |
@@ -205,7 +205,7 @@ For information about using this port see:
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](../airframes/airframe_reference.md).
## See Also
## 另见
- [Holybro Docs](https://docs.holybro.com/) (Holybro)
- [Pixhawk 4 Mini Wiring Quick Start](../assembly/quick_start_pixhawk4_mini.md) (and [Pixhawk 6C Wiring QuickStart](../assembly/quick_start_pixhawk6c.md))
docs/zh/flight_controller/pixhawk6x-rt.md
+1 -1
View File
@@ -157,7 +157,7 @@ Sample Wiring Diagram
| UART | 设备 | Port |
| ------ | ---------- | -------- |
| UART1 | /dev/ttyS0 | Debug |
| UART | UART | Debug |
| UART3 | /dev/ttyS1 | GPS |
| UART4 | /dev/ttyS2 | TELEM1 |
| UART5 | /dev/ttyS3 | GPS2 |
docs/zh/flight_controller/pixhawk6x.md
+2 -2
View File
@@ -188,9 +188,9 @@ Sample Wiring Diagram
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 & I2C |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
docs/zh/flight_controller/pixhawk6x_pro.md
+3 -3
View File
@@ -148,9 +148,9 @@ The [Pixhawk 6X Wiring Quick Start](../assembly/quick_start_pixhawk6x.md) provid
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 & I2C |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
@@ -244,7 +244,7 @@ The complete set of supported configurations can be seen in the [Airframes Refer
Download [here](https://docs.holybro.com/autopilot/pixhawk-6x-pro/download).
## See Also
## 另见
- [Holybro Docs](https://docs.holybro.com/autopilot/pixhawk-6x-pro) (Holybro)
- [Pixhawk 6X Wiring QuickStart](../assembly/quick_start_pixhawk6x.md)
docs/zh/flight_controller/pixhawk_series.md
+18
View File
@@ -100,6 +100,24 @@ At very high level, the main differences are:
<a id="licensing-and-trademarks"></a>
### FMUv6 Comparison
| 特性 | **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
Pixhawk project schematics and reference designs are licensed under [CC BY-SA 3](https://creativecommons.org/licenses/by-sa/3.0/legalcode).
docs/zh/flight_controller/pixracer.md
+8 -8
View File
@@ -188,14 +188,14 @@ For information about using this port see:
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | WiFi (ESP8266) |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
| UART | 设备 | Port |
| ------ | ---------- | --------------------------------- |
| UART | UART | WiFi (ESP8266) |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | | |
| UART7 | CONSOLE | |
| UART8 | SERIAL4 | |
<!-- Note: Got ports using https://github.com/PX4/PX4-user_guide/pull/672#issuecomment-598198434 -->
docs/zh/flight_controller/raccoonlab_fmu6x.md
+2 -2
View File
@@ -103,9 +103,9 @@ This autopilot is [supported](../flight_controller/autopilot_pixhawk_standard.md
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 & I2C |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
docs/zh/flight_controller/radiolink_pix6.md
+8 -8
View File
@@ -302,14 +302,14 @@ Recommended modules include:
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| UART1 | /dev/ttyS0 | GPS1 |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | /dev/ttyS3 | GPS2 |
| UART7 | /dev/ttyS4 | Debug Console |
| UART8 | /dev/ttyS5 | PX4IO |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| UART | UART | GPS1 |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | GPS2 |
| UART7 | /dev/ttyS4 | 调试控制台 |
| UART8 | /dev/ttyS5 | PX4IO |
## Analog inputs
docs/zh/flight_controller/svehicle_e2.md
+10 -10
View File
@@ -74,16 +74,16 @@ CRSF receiver must be wired to a spare port (UART) on the Flight Controller. The
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ------------- |
| USART1 | /dev/ttyS0 | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | Debug Console |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
| UART7 | /dev/ttyS6 | TELEM1 |
| UART8 | /dev/ttyS7 | GPS2 |
| UART | 设备 | Port |
| ------ | ---------- | -------- |
| USART1 | UART | GPS |
| USART2 | /dev/ttyS1 | TELEM3 |
| USART3 | /dev/ttyS2 | 调试控制台 |
| UART4 | /dev/ttyS3 | UART4 |
| UART5 | /dev/ttyS4 | TELEM2 |
| USART6 | /dev/ttyS5 | PX4IO/RC |
| UART7 | /dev/ttyS6 | TELEM1 |
| UART8 | /dev/ttyS7 | GPS2 |
## PWM Output
docs/zh/flight_controller/thepeach_k1.md
+9 -9
View File
@@ -50,15 +50,15 @@ It is based on the **Pixhawk-project FMUv3** open hardware design and runs **PX4
## 串口映射
| UART | 设备 | Port |
| ------ | ---------- | ---------------------------------------- |
| USART1 | /dev/ttyS0 | IO Processor Debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART3 | /dev/ttyS2 | TELEM2 (flow control) |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | Debug Console |
| UART8 | /dev/ttyS6 | TELEM4 |
| UART | 设备 | Port |
| ------ | ---------- | ------------------------------ |
| USART1 | UART | IO Processor Debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (流控) |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | PX4IO |
| UART7 | /dev/ttyS5 | 调试控制台 |
| UART8 | /dev/ttyS6 | TELEM4 |
## 额定电压
docs/zh/flight_controller/thepeach_r1.md
+2 -2
View File
@@ -56,8 +56,8 @@ It is based on the **Pixhawk-project FMUv3** open hardware design and runs **PX4
| UART | 设备 | Port |
| ------ | ---------- | --------------------------------------------- |
| USART1 | /dev/ttyS0 | IO Processor Debug |
| USART2 | /dev/ttyS1 | TELEM1 (flow control) |
| USART1 | UART | IO Processor Debug |
| USART2 | /dev/ttyS1 | TELEM1 (流控) |
| USART3 | /dev/ttyS2 | TELEM2 (Raspberry pi cm3+) |
| UART4 | /dev/ttyS3 | GPS1 |
| USART6 | /dev/ttyS4 | PX4IO |
docs/zh/flight_modes_fw/hold.md
+1 -1
View File
@@ -40,7 +40,7 @@ Hold mode behaviour can be configured using the parameters below.
| [NAV_LOITER_RAD](../advanced_config/parameter_reference.md#NAV_LOITER_RAD) | The radius of the loiter circle. |
| <a id="NAV_MIN_LTR_ALT"></a>[NAV_MIN_LTR_ALT](../advanced_config/parameter_reference.md#NAV_MIN_LTR_ALT) | Minimum height for loiter mode (vehicle will ascend to this altitude if mode is engaged at a lower altitude). |
## See Also
## 另见
[Hold Mode (MC)](../flight_modes_mc/hold.md)
docs/zh/flight_modes_fw/land.md
+1 -1
View File
@@ -48,7 +48,7 @@ Land mode behaviour can be configured using the parameters below.
| <a id="FW_LND_AIRSPD"></a>[FW_LND_AIRSPD](../advanced_config/parameter_reference.md#FW_LND_AIRSPD) | The airspeed setpoint. |
| <a id="FW_AIRSPD_FLP_SC"></a>[FW_AIRSPD_FLP_SC](../advanced_config/parameter_reference.md#FW_AIRSPD_FLP_SC) | Factor applied to the minimum airspeed when flaps are fully deployed. Necessary if FW_LND_AIRSPD is below FW_AIRSPD_MIN. |
## See Also
## 另见
- [Land Mode (MC)](../flight_modes_mc/land.md)
- [Land Mode (VTOL)](../flight_modes_vtol/land.md)
docs/zh/flight_modes_fw/mission.md
+1 -1
View File
@@ -374,7 +374,7 @@ In landing mode, the distance sensor is used to determine proximity to the groun
| [FW_WING_SPAN](../advanced_config/parameter_reference.md#FW_WING_SPAN) | Wing span of the airframe. |
| [FW_WING_HEIGHT](../advanced_config/parameter_reference.md#FW_WING_HEIGHT) | Height of wing from bottom of gear (or belly if no gear). |
## See Also
## 另见
- [Missions](../flying/missions.md)
- [包裹投递任务](../flying/package_delivery_mission.md)
docs/zh/flight_modes_fw/return.md
+1 -1
View File
@@ -61,7 +61,7 @@ The others are relevant if the destination is a rally point or the home location
| <a id="RTL_LOITER_RAD"></a>[RTL_LOITER_RAD](../advanced_config/parameter_reference.md#RTL_LOITER_RAD) | [Fixed-wing Only] The radius of the loiter circle (at [RTL_LAND_DELAY](#RTL_LAND_DELAY)). |
| <a id="MIS_TKO_LAND_REQ"></a>[MIS_TKO_LAND_REQ](../advanced_config/parameter_reference.md#MIS_TKO_LAND_REQ) | Specify whether a mission landing or takeoff pattern is required. Fixed wings generally require this. |
## See Also
## 另见
- [Return Mode (Generic)](../flight_modes/return.md)
- [Return Mode (Multicopter)](../flight_modes_mc/return.md)
docs/zh/flight_modes_fw/takeoff.md
+1 -1
View File
@@ -142,7 +142,7 @@ Runway takeoff is affected by the following parameters:
| <a id="FW_WING_SPAN"></a>[FW_WING_SPAN](../advanced_config/parameter_reference.md#FW_WING_SPAN) | The wingspan of the vehicle. Used to prevent wingstrikes. |
| <a id="FW_WING_HEIGHT"></a>[FW_WING_HEIGHT](../advanced_config/parameter_reference.md#FW_WING_HEIGHT) | The height of the wings above ground (ground clearance). Used to prevent wingstrikes. |
## See Also
## 另见
- [Takeoff Mode (MC)](../flight_modes_mc/takeoff.md)
- [Planning a mission takeoff](../flight_modes_fw/mission.md#mission-takeoff)
docs/zh/flight_modes_mc/hold.md
+1 -1
View File
@@ -43,6 +43,6 @@ Hold mode behaviour can be configured using the parameters below.
<!-- Code for this here: https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/navigator/loiter.cpp#L61 -->
## See Also
## 另见
[Hold Mode (FW)](../flight_modes_fw/hold.md)
docs/zh/flight_modes_mc/land.md
+1 -1
View File
@@ -38,7 +38,7 @@ Land mode behaviour can be configured using the parameters below.
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). 可以分别为自动模式和 offboard 模式启用此功能，默认情况下在自动模式下启用此功能。 |
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
## See Also
## 另见
- [Land Mode (FW)](../flight_modes_fw/land.md)
- [Land Mode (VTOL)](../flight_modes_vtol/land.md)
docs/zh/flight_modes_mc/mission.md
+1 -1
View File
@@ -228,7 +228,7 @@ If a mission with no takeoff mission item is started, the vehicle will ascend to
If the vehicle is already flying when the mission is started, a takeoff mission item is treated as a normal waypoint.
## See Also
## 另见
- [Missions](../flying/missions.md)
- [包裹投递任务](../flying/package_delivery_mission.md)
docs/zh/flight_modes_mc/position.md
+1 -1
View File
@@ -81,6 +81,6 @@ All the parameters in the [Multicopter Position Control](../advanced_config/para
If the estimate falls below acceptable levels, for example due to GPS loss, this may trigger a [Position (GPS) Loss Failsafe](../config/safety.md#position-gnss-loss-failsafe).
如果估计值低于可接受的水平，例如由于 GPS 丢失，这可能会触发位置 (GPS) 丢失故障保护 根据配置，是否有遥控器，以及是否有足够的高度估计，PX4 可能会切换到高度模式、手动模式、降落模式或终止。
## See Also
## 另见
- [Position Slow Mode](../flight_modes_mc/position_slow.md)
docs/zh/flight_modes_mc/position_slow.md
+1 -1
View File
@@ -88,6 +88,6 @@ The value can be updated from a message at any time, and is latched until either
Note that PX4 does not provide velocity limit telemetry (i.e. it does not support streaming the [VELOCITY_LIMITS](https://mavlink.io/en/messages/development.html#VELOCITY_LIMITS) message).
## See Also
## 另见
- [Position Slow Mode](../flight_modes_mc/position.md)
docs/zh/flight_modes_mc/return.md
+1 -1
View File
@@ -70,7 +70,7 @@ The parameters that are relevant to multicopter (assuming the [RTL_TYPE](../adva
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md) (except when vehicle is handling a critical battery failsafe). 可以分别为自动模式和 offboard 模式启用此功能，默认情况下在自动模式下启用此功能。 |
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled). |
## See Also
## 另见
- [Return Mode (Generic)](../flight_modes/return.md)
- [Return Mode (Fixed-Wing)](../flight_modes_fw/return.md)
docs/zh/flight_modes_mc/takeoff.md
+1 -1
View File
@@ -36,7 +36,7 @@ Takeoff is affected by the following parameters:
| <a id="COM_RC_OVERRIDE"></a>[COM_RC_OVERRIDE](../advanced_config/parameter_reference.md#COM_RC_OVERRIDE) | Controls whether stick movement on a multicopter (or VTOL in MC mode) causes a mode change to [Position mode](../flight_modes_mc/position.md). 可以分别为自动模式和 offboard 模式启用此功能，默认情况下在自动模式下启用此功能。 |
| <a id="COM_RC_STICK_OV"></a>[COM_RC_STICK_OV](../advanced_config/parameter_reference.md#COM_RC_STICK_OV) | The amount of stick movement that causes a transition to [Position mode](../flight_modes_mc/position.md) (if [COM_RC_OVERRIDE](#COM_RC_OVERRIDE) is enabled) |
## See Also
## 另见
- [Throw Launch (MC)](../flight_modes_mc/throw_launch.md)
- [Takeoff Mode (FW)](../flight_modes_fw/takeoff.md)
docs/zh/flight_modes_mc/throw_launch.md
+1 -1
View File
@@ -95,7 +95,7 @@ The following parameters can be used to enable and configure throw launch:
- [COM_THROW_SPEED](../advanced_config/parameter_reference.md#COM_THROW_SPEED) determines the minimum speed the aircraft should reach to detect the throw.
If it is not reached, the engines will not turn on.
## See Also
## 另见
- [Takeoff Mode (Fixed-Wing) > Catapult/Hand Launch](../flight_modes_fw/takeoff.md#catapult-hand-launch).
docs/zh/flight_modes_vtol/land.md
+1 -1
View File
@@ -17,7 +17,7 @@ The VTOL-specific parameters are:
| ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [NAV_FORCE_VT](../advanced_config/parameter_reference.md#NAV_FORCE_VT) | Force VTOL to takeoff and land as a multicopter (default: true) |
## See Also
## 另见
- [Land Mode (MC)](../flight_modes_mc/land.md)
- [Land Mode (FW)](../flight_modes_fw/land.md)
docs/zh/flight_modes_vtol/mission.md
+1 -1
View File
@@ -49,7 +49,7 @@ After transitioning the vehicle heads towards the 3D position defined in the mis
A VTOL mission requires a `VTOL Takeoff` mission item (`MAV_CMD_NAV_VTOL_TAKEOFF`) to takeoff (or a `MAV_CMD_NAV_TAKEOFF` when the vehicle is in MC mode); if however the vehicle is already flying when the mission is started the takeoff item will be treated as a normal waypoint.
## See Also
## 另见
- [Mission Mode (MC)](../flight_modes_mc/mission.md)
- [Mission Mode (FW)](../flight_modes_fw/mission.md)
docs/zh/flight_modes_vtol/return.md
+1 -1
View File
@@ -81,7 +81,7 @@ The others are relevant if the destination is a rally point or the home location
| <a id="RTL_LOITER_RAD"></a>[RTL_LOITER_RAD](../advanced_config/parameter_reference.md#RTL_LOITER_RAD) | [Fixed-wing Only] The radius of the loiter circle (at [RTL_LAND_DELAY](#RTL_LAND_DELAY). |
| <a id="MIS_TKO_LAND_REQ"></a>[MIS_TKO_LAND_REQ](../advanced_config/parameter_reference.md#MIS_TKO_LAND_REQ) | Specify whether a mission landing or takeoff pattern is _required_. Generally fixed-wing vehicles set this to require a landing pattern but VTOL do not. |
## See Also
## 另见
- [Return Mode (Generic)](../flight_modes/return.md)
- [Return Mode (Multicopter)](../flight_modes_mc/return.md)
docs/zh/flying/basic_flying_mc.md
+1 -1
View File
@@ -94,7 +94,7 @@ The following three modes are highly recommended for new users:
You can also engage automatic modes on the _QGroundControl_ main flight screen.
:::
## See Also
## 另见
- [Terrain Follow/Hold & Range Assistance](../flying/terrain_following_holding.md) — How to enable terrain following
- [Missions](../flying/missions.md)
docs/zh/frames_multicopter/dji_f450_cuav_5nano.md
+2 -2
View File
@@ -43,8 +43,8 @@ This section lists all hardware for the frame.
| DJI F450 Bottom plate | 1 |
| DJI F450 Top plate | 1 |
| DJI F450 legs with landing gear | 4 |
| M3\*8 screws | 18 |
| M2 5\*6 screws | 24 |
| M3\*8螺丝 | 18 |
| M2.5\*6 螺丝 | 24 |
| Velcro Battery Strap | 1 |
| DJI Phantom Built-in Nut Upgrade Propellers 9.4x5 | 1 |
docs/zh/frames_multicopter/dji_f450_cuav_5plus.md
+2 -2
View File
@@ -43,8 +43,8 @@ This section lists all hardware for the frame.
| DJI F450 Bottom plate | 1 |
| DJI F450 Top plate | 1 |
| DJI F450 legs with landing gear | 4 |
| M3\*8 screws | 18 |
| M2 5\*6 screws | 24 |
| M3\*8螺丝 | 18 |
| M2.5\*6 螺丝 | 24 |
| Velcro Battery Strap | 1 |
| DJI Phantom Built-in Nut Upgrade Propellers 9.4x5 | 1 |
docs/zh/frames_multicopter/holybro_s500_v2_pixhawk4.md
+73 -73
View File
@@ -3,88 +3,88 @@
This topic provides full instructions for building the kit and configuring PX4 using _QGroundControl_.
:::info
Holybro initially supplied this kit with a [Holybro Pixhawk 4](../flight_controller/pixhawk4.md), but at time of writing this has been upgraded to a more recent Pixhawk (6C).
This build log is still relevant as the kit assembly is virtually the same, and likely to remain so as the flight controller is upgraded.
Holybro最初提供了和[Holybro Pixhawk 4](../flight_controller/pixhawk4.md)飞控一起提供这个套件, 但在撰写本文档时，这个系统已升级为较新的 Pixhawk (6C)。
这个构建记录仍然具有相关性，因为套装组件几乎是一样的，而且随着飞行控制器升级，很可能仍然如此。
:::
## Key information
- **Frame:** Holybro S500
- **Flight controller:** [Pixhawk 4](../flight_controller/pixhawk4.md)
- **Assembly time (approx.):** 90 minutes (45 minutes for frame, 45 minutes for autopilot installation/configuration)
- **机架：** Holybro S500
- **飞行控制器：** [Pixhawk 4](../flight_controller/pixhawk4.md)
- **大约组装时间：** 90 分钟 (机架组装45分钟，飞控安装和配置45分钟)
![Full S500 Kit](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_hero.png)
![完整的S500套件](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_hero.png)
## Bill of materials
The Holybro [S500 V2 Kit](https://holybro.com/collections/s500/products/s500-v2-development-kit) includes almost all the required components:
Holybro [S500 V2 套件](https://holybro.com/collections/s500/products/s500-v2-development-kit) 包含几乎所有需要的组件：
- A recent Pixhawk autopilot
- For this log it was Pixhawk 4 but far more recent versions are now included.
- Power Management PM02（Assembled）
- ARM adopts high strength plastics
- Motors - 2216 KV880（ V2 Update）
- Propeller 1045（ V2 Update）
- Pixhawk4 GPS
- 一个近期发布的 Pixhawk 飞控
- 对于这个装机日志，它是 Pixhawk 4，但是现在的套件包含了更新的版本。
- 电源管理模块 PM02(已组装)
- 采用高强度塑料的机臂
- 马达 - 2216 KV880(V2 版本)
- 1045桨叶(V2 版本)
- Pixhawk4 GPS模组
- Fully assembled Power Management Board with ESCs
- 433 MHz / 915 MHz [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md)
- Power and Radio Cables
- Battery Straps
- Dimensions:383_385_240mm
- Wheelbase:480mm
- 433 MHz / 915 MHz [Holybro数传电台](../telemetry/holybro_sik_radio.md)
- 电源线和信号线
- 电池绑带
- 尺寸：383_385_240毫米
- 轴距：480毫米
:::info
No LiPo battery is included.
In addition, we use a FrSky Taranis controller.
不包含锂电池。
此外，我们使用一个FrSky Taranis遥控。
:::
## 硬件
| Item Description | Quantity |
| --------------------------------------------- | -------- |
| Wheelbase: 480mm | 1 |
| Arms | 4 |
| Set of Landing Gear | 2 |
| M3\*8 screws | 18 |
| M2 5\*6 screws | 24 |
| Battery Straps | 1 |
| Propeller 1045 (V2 Update) | 1 |
| 物品描述 | Quantity |
| -------------------------------- | -------- |
| 轴距：480毫米 | 1 |
| 机臂 | 4 |
| 起落架 | 2 |
| M3\*8螺丝 | 18 |
| M2.5\*6 螺丝 | 24 |
| 电池绑带 | 1 |
| 1045桨叶(V2 版本) | 1 |
![S500 Hardware](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_hardware.jpg)
![S500硬件](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_hardware.jpg)
## Package
## 包装
| Items | Package |
| ---------------------------------------------------- | ------- |
| Pixhawk 4 | 1 |
| Pixhawk4 GPS MODULE | 1 |
| I2C splitter Board | 2 |
| 6 to 6 pin cable (power) | 3 |
| 4 to 4 pin cable (CAN) | 2 |
| 6 to 4 pin cable (Data) | 1 |
| 10 to 10 pin cable (PWM) | 2 |
| 8 to 8 pin cable(AUX) | 1 |
| 7 to 7 pin cable(SPI) | 1 |
| 6 to 6 pin cable(Debug) | 1 |
| PPM/SBUS out cable | 1 |
| XSR receiver cable | 1 |
| DSMX receiver cable | 1 |
| SBUS receiver cable | 1 |
| USB cable | 1 |
| 'X'type folding pedestal mount | 1 |
| 70mm & 140mm carbon rod standoff | 2 |
| 6\*3 2.54mm pitch Horizontal Pin | 1 |
| 8\*3 2.54mm pitch Horizontal Pin | 2 |
| Foam Set | 1 |
| Pixhawk4 Quick Start Guide | 1 |
| Pixhawk4 Pinouts | 1 |
| GPS Quick Start Guide | 1 |
| 物品 | 包装 |
| ---------------------------------------------------- | -- |
| Pixhawk 4 | 1 |
| Pixhawk4 GPS MODULE | 1 |
| I2C splitter Board | 2 |
| 6 to 6 pin cable (power) | 3 |
| 4 to 4 pin cable (CAN) | 2 |
| 6 to 4 pin cable (Data) | 1 |
| 10 to 10 pin cable (PWM) | 2 |
| 8 to 8 pin cable(AUX) | 1 |
| 7 to 7 pin cable(SPI) | 1 |
| 6 to 6 pin cable(Debug) | 1 |
| PPM/SBUS out cable | 1 |
| XSR receiver cable | 1 |
| DSMX receiver cable | 1 |
| SBUS receiver cable | 1 |
| USB cable | 1 |
| 'X'type folding pedestal mount | 1 |
| 70mm & 140mm carbon rod standoff | 2 |
| 6\*3 2.54mm pitch Horizontal Pin | 1 |
| 8\*3 2.54mm pitch Horizontal Pin | 2 |
| Foam Set | 1 |
| Pixhawk4 Quick Start Guide | 1 |
| Pixhawk4 Pinouts | 1 |
| GPS Quick Start Guide | 1 |
![S500 Package Contents](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_package.jpg)
### Electronics
| Item Description | Quantity |
| 物品描述 | Quantity |
| ---------------------------------------------------------- | -------- |
| Pixhawk 4 autopilot (PM06 not included) | 1 |
| Power Management PM02 (Assembled) | 1 |
@@ -112,9 +112,9 @@ The following tools are used in this assembly:
## 组装
Estimate time to assemble is 90 minutes, about 45 minutes for frame assembly and 45 minutes installing and configuring the autopilot in QGroundControl.
估计的组装时间是90分钟，组装机架约45分钟，安装和在QGroundControl配置飞控约45分钟。
1. Assembling the Landing Gear.
1. 安装起落架。
We are going to start by assembling the landing gear to the vertical pole. Unscrew the landing gear screws and insert the vertical pole as shown below.
![Figure 1](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig1.jpg)
@@ -123,27 +123,27 @@ Estimate time to assemble is 90 minutes, about 45 minutes for frame assembly and
2. Assemble the Power Management Board to the landing gear. Screw the landing gear with a vertical pole to the Fully assembled Power Management Board.
The Board has 4 holes (see arrows below).
板子有4个洞(见下面的箭头)。
![Figure 3](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig3.jpg)
Connect with the M3X8 screws, a total of 8 pieces, 4 on each side.
用 M3X8 螺丝连接，总共8个，每侧4个。
![Figure 4](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig4.jpg)
1. Assemble the arms to the Power Management Board.
Attach the arm to the Power Management Board.
1. 把机臂装到电源管理板上。
把机臂装到电源管理板上。
![Figure 6](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig7.jpg)
![Figure 7](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig8.jpg)
Use M2 5X6 screws a total of 2 in each arm.
Insert the screws from the bottom of the plate.
在每个臂上使用2个M2.5X6螺丝。
从板块底部插入螺丝。
![Figure 8](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig9.jpg)
Make sure the ESC cables run through the middle of the arm.
确保电调的电线穿过机臂中间。
![Figure 9](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig91.jpg)
@@ -255,11 +255,11 @@ Connect with the M3X8 screws, a total of 8 pieces, 4 on each side.
9. Pixhawk 4 wiring. The Pixhawk 4, which has several different wires and connections with it.
Included below is a picture of every wire needed with the Pixhawk and how it looks when connected.
10. Plugin Telemetry and GPS module to the flight controller as seen in Figure 37; plug in the RC receiver, all 4 ESCs to the flight controller as well as the power module.
10. 如图37所示，把数传模块和GPS模块接到飞行控制器上；连接遥控接收器、4 个电调以及电源模块到飞行控制器上。
![Figure 37](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_fig37.png)
Fully assembled, the kit looks as shown below:
装好以后套件看起来像下面这样：
![Pixhawk Assembled](../../assets/airframes/multicopter/s500_holybro_pixhawk4/s500_pixhawk.jpg)
@@ -274,16 +274,16 @@ _QGroundControl_ is used to install the PX4 autopilot and configure/tune it for
Full instructions for installing and configuring PX4 can be found in [Basic Configuration](../config/index.md).
:::
First update the firmware and airframe:
首先更新固件和机架配置：
- [Firmware](../config/firmware.md)
- [Airframe](../config/airframe.md)
You will need to select the _Holybro S500_ airframe (**Quadrotor x > Holybro S500**).
您需要选择 _Holybro S500_ 机架(**Quadrotor x > Holybro S500**)。
![QGroundControl - Select HolyBro X500 airframe](../../assets/airframes/multicopter/s500_holybro_pixhawk4/qgc_airframe_holybro_s500.png)
Then set the actuator outputs:
然后设置执行器输出：
- [Actuators](../config/actuators.md)
- You should not need to update the vehicle geometry (as this is a preconfigured airframe).
@@ -308,7 +308,7 @@ Ideally you should also do:
## 调试
Airframe selection sets _default_ autopilot parameters for the frame.
These are good enough to fly with, but it is a good idea to tune the parameters for a specific frame build.
这些足以让它起飞，但是为你的特定框架调整专有参数是一个好主意。
For instructions on how, start from [Autotune](../config/autotune_mc.md).
docs/zh/frames_multicopter/holybro_x500V2_pixhawk5x.md
+11 -11
View File
@@ -2,7 +2,7 @@
:::info
Holybro initially supplied this kit with a [Pixhawk 5X](../flight_controller/pixhawk5x.md), but at time of writing this has been upgraded to a [Holybro Pixhawk 6C](../flight_controller/pixhawk6c.md).
This build log is still relevant as the kit assembly is virtually the same, and likely to remain so as the flight controller is upgraded.
这个构建记录仍然具有相关性，因为套装组件几乎是一样的，而且随着飞行控制器升级，很可能仍然如此。
:::
This topic provides full instructions for building the [Holybro X500 V2 ARF Kit](https://holybro.com/collections/x500-kits) and configuring PX4 using _QGroundControl_.
@@ -71,15 +71,15 @@ _Figure 1_: X500 V2 ARF Kit what's inside
### Electronics
| Item Description | Quantity |
| ------------------------------------------------------------------------------ | -------- |
| Pixhawk5x & Assorted Cables | 1 |
| M8N GPS Module | 1 |
| Power Module PM02D (with pre-soldered ESC power cables) | 1 |
| Motors 2216 KV880（V2 Update) | 4 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| 433 MHz / 915 MHz [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md) | 1 |
| 物品描述 | Quantity |
| -------------------------------------------------------------------------- | -------- |
| Pixhawk5x & Assorted Cables | 1 |
| M8N GPS Module | 1 |
| Power Module PM02D (with pre-soldered ESC power cables) | 1 |
| Motors 2216 KV880（V2 Update) | 4 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| 433 MHz / 915 MHz [Holybro数传电台](../telemetry/holybro_sik_radio.md) | 1 |
### Tools needed
@@ -231,7 +231,7 @@ Ideally you should also do:
## 调试
Airframe selection sets _default_ autopilot parameters for the frame.
These are good enough to fly with, but it is a good idea to tune the parameters for a specific frame build.
这些足以让它起飞，但是为你的特定框架调整专有参数是一个好主意。
For instructions on how, start from [Autotune](../config/autotune_mc.md).
docs/zh/frames_multicopter/holybro_x500_pixhawk4.md
+14 -14
View File
@@ -2,7 +2,7 @@
:::info
Holybro initially supplied this kit with a [Holybro Pixhawk 4](../flight_controller/pixhawk4.md)), but at time of writing this has been upgraded to a [Holybro Pixhawk 6C](../flight_controller/pixhawk6c.md).
This build log is still relevant as the kit assembly is virtually the same, and likely to remain so as the flight controller is upgraded.
这个构建记录仍然具有相关性，因为套装组件几乎是一样的，而且随着飞行控制器升级，很可能仍然如此。
:::
This topic provides full instructions for building the kit and configuring PX4 using _QGroundControl_.
@@ -10,7 +10,7 @@ This topic provides full instructions for building the kit and configuring PX4 u
## Key information
- **Full Kit:** [Holybro X500 Kit](https://holybro.com/products/px4-development-kit-x500-v2)
- **Flight controller:** [Pixhawk 4](../flight_controller/pixhawk4.md)
- **飞行控制器：** [Pixhawk 4](../flight_controller/pixhawk4.md)
- **Assembly time (approx.):** 3.75 hours (180 minutes for frame, 45 minutes for autopilot installation/configuration)
![Full X500 Kit](../../assets/airframes/multicopter/x500_holybro_pixhawk4/x500_hero.png)
@@ -26,10 +26,10 @@ The Holybro [X500 Kit](https://holybro.com/products/px4-development-kit-x500-v2)
- Holybro BLHeli S ESC 20A x4 (superseded - check [spare parts list](https://holybro.com/products/spare-parts-x500-v2-kit) for current version).
- Propellers - 1045 x4 (superseded - check [spare parts list](https://holybro.com/products/spare-parts-x500-v2-kit) for current version).
- Battery Strap
- Power and Radio Cables
- 电源线和信号线
- Wheelbase - 500 mm
- Dimensions - 410x410x300 mm
- 433 MHz / 915 MHz [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md)
- 433 MHz / 915 MHz [Holybro数传电台](../telemetry/holybro_sik_radio.md)
Additionally you will need a battery and receiver ([compatible radio system](../getting_started/rc_transmitter_receiver.md)) if you want to control the drone manually.
@@ -55,14 +55,14 @@ This section lists all hardware for the frame and the autopilot installation.
### Electronics
| Item Description | Quantity |
| ------------------------------------------------------------------------------ | -------- |
| Pixhawk4 & Assorted Cables | 1 |
| Pixhawk4 GPS Module | 1 |
| Power Management PM07 (with pre-soldered ESC power cables) | 1 |
| Motors 2216 KV880（V2 Update) | 4 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| 433 MHz / 915 MHz [Holybro Telemetry Radio](../telemetry/holybro_sik_radio.md) | 1 |
| 物品描述 | Quantity |
| ----------------------------------------------------------------------------- | -------- |
| Pixhawk4 & Assorted Cables | 1 |
| Pixhawk4 GPS Module | 1 |
| Power Management PM07 (with pre-soldered ESC power cables) | 1 |
| Motors 2216 KV880（V2 Update) | 4 |
| Holybro BLHeli S ESC 20A x4 | 1 |
| 433 MHz / 915 MHz [Holybro数传电台](../telemetry/holybro_sik_radio.md) | 1 |
### Tools needed
@@ -223,7 +223,7 @@ First update the firmware, airframe, and actuator mappings:
- [Airframe](../config/airframe.md)
You will need to select the _Holybro S500_ airframe (**Quadrotor x > Holybro S500**).
您需要选择 _Holybro S500_ 机架(**Quadrotor x > Holybro S500**)。
![QGroundControl - Select HolyBro X500 airframe](../../assets/airframes/multicopter/s500_holybro_pixhawk4/qgc_airframe_holybro_s500.png)
@@ -250,7 +250,7 @@ Ideally you should also do:
## 调试
Airframe selection sets _default_ autopilot parameters for the frame.
These are good enough to fly with, but it is a good idea to tune the parameters for a specific frame build.
这些足以让它起飞，但是为你的特定框架调整专有参数是一个好主意。
For instructions on how, start from [Autotune](../config/autotune_mc.md).
docs/zh/frames_multicopter/holybro_x500v2_pixhawk6c.md
+2 -2
View File
@@ -84,7 +84,7 @@ Note that the ESC connectors are color-coded and must be inserted in the PWM out
![esc_connector_pixhawk6c](../../assets/airframes/multicopter/x500_v2_holybro_pixhawk6c/esc_connector.jpg)
### Arms
### 机臂
**Screw-** Socket Cap Screw M3\*38 16pcs | Flange Locknut M3 16pcs
@@ -207,7 +207,7 @@ Ideally you should also do:
## 调试
Airframe selection sets _default_ autopilot parameters for the frame.
These are good enough to fly with, but it is a good idea to tune the parameters for a specific frame build.
这些足以让它起飞，但是为你的特定框架调整专有参数是一个好主意。
For instructions on how, start from [Auto-tune](../config/autotune_mc.md).
docs/zh/frames_multicopter/qav_r_5_kiss_esc_racer.md
+1 -1
View File
@@ -270,6 +270,6 @@ Ideally you should also do:
### 调试
Airframe selection sets _default_ autopilot parameters for the frame.
These are good enough to fly with, but it is a good idea to tune the parameters for a specific frame build.
这些足以让它起飞，但是为你的特定框架调整专有参数是一个好主意。
For instructions on how, start from [Autotune](../config/autotune_mc.md).
docs/zh/frames_rover/index.md
+1 -1
View File
@@ -55,7 +55,7 @@ Each wheel is driven by its own motor, and by controlling the speed and directio
![Mecanum rover](../../assets/airframes/rover/rover_mecanum.png)
## See Also
## 另见
- [Drive Modes](../flight_modes_rover/index.md)
- [Configuration/Tuning](../config_rover/index.md)
docs/zh/gps_compass/ark_sam_gps.md
+1 -1
View File
@@ -56,6 +56,6 @@ The module should be plug-n-play when used with the `GPS2` port on most flight c
| 5 | SDA | 3.3V |
| 6 | GND | GND |
## See Also
## 另见
- [ARK SAM GPS Documentation](https://arkelectron.gitbook.io/ark-documentation/gps/ark-sam-gps) (ARK Docs)

Some files were not shown because too many files have changed in this diff Show More