diff --git a/docs/zh/actuators/index.md b/docs/zh/actuators/index.md index 71f11b5a05..60b3dac4d0 100644 --- a/docs/zh/actuators/index.md +++ b/docs/zh/actuators/index.md @@ -8,6 +8,6 @@ - [电调校准](../advanced_config/esc_calibration.md) — PWM 电调的校准 (DShot/CAN 电调/舵机不需要) 。 -## See Also +## 另见 - [外设](../peripherals/index.md) - 包括非核心执行器，如夹具， 降落伞等。 diff --git a/docs/zh/advanced_config/ethernet_setup.md b/docs/zh/advanced_config/ethernet_setup.md index ac1fca8e67..b41967a31e 100644 --- a/docs/zh/advanced_config/ethernet_setup.md +++ b/docs/zh/advanced_config/ethernet_setup.md @@ -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 主板。 diff --git a/docs/zh/advanced_config/index.md b/docs/zh/advanced_config/index.md index b41f62561a..bab4c3f593 100644 --- a/docs/zh/advanced_config/index.md +++ b/docs/zh/advanced_config/index.md @@ -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) - 设置特定传感器、可选传感器、执行器等。 diff --git a/docs/zh/assembly/_assembly.md b/docs/zh/assembly/_assembly.md index 19062417ac..42804d30f4 100644 --- a/docs/zh/assembly/_assembly.md +++ b/docs/zh/assembly/_assembly.md @@ -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) diff --git a/docs/zh/camera/camera_architecture.md b/docs/zh/camera/camera_architecture.md index fd81c41352..89b9ea5a54 100644 --- a/docs/zh/camera/camera_architecture.md +++ b/docs/zh/camera/camera_architecture.md @@ -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) - Camera capture driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_capture) diff --git a/docs/zh/camera/fc_connected_camera.md b/docs/zh/camera/fc_connected_camera.md index ea9e1e0164..fdae04a272 100644 --- a/docs/zh/camera/fc_connected_camera.md +++ b/docs/zh/camera/fc_connected_camera.md @@ -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) - Camera capture driver: [source code](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_capture) diff --git a/docs/zh/camera/index.md b/docs/zh/camera/index.md index 015d7fc9a5..6367fb82c0 100644 --- a/docs/zh/camera/index.md +++ b/docs/zh/camera/index.md @@ -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 开发者) diff --git a/docs/zh/companion_computer/ark_jetson_pab_carrier.md b/docs/zh/companion_computer/ark_jetson_pab_carrier.md index c34e2a96e4..bbfa91cc1e 100644 --- a/docs/zh/companion_computer/ark_jetson_pab_carrier.md +++ b/docs/zh/companion_computer/ark_jetson_pab_carrier.md @@ -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) diff --git a/docs/zh/companion_computer/holybro_pixhawk_jetson_baseboard.md b/docs/zh/companion_computer/holybro_pixhawk_jetson_baseboard.md index 93dd15e4e2..e49a32a97a 100644 --- a/docs/zh/companion_computer/holybro_pixhawk_jetson_baseboard.md +++ b/docs/zh/companion_computer/holybro_pixhawk_jetson_baseboard.md @@ -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) diff --git a/docs/zh/companion_computer/holybro_pixhawk_rpi_cm4_baseboard.md b/docs/zh/companion_computer/holybro_pixhawk_rpi_cm4_baseboard.md index edece004af..91bceef69c 100644 --- a/docs/zh/companion_computer/holybro_pixhawk_rpi_cm4_baseboard.md +++ b/docs/zh/companion_computer/holybro_pixhawk_rpi_cm4_baseboard.md @@ -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 主板。 diff --git a/docs/zh/complete_vehicles_fw/index.md b/docs/zh/complete_vehicles_fw/index.md index 636dfd5ef6..23a08e6ada 100644 --- a/docs/zh/complete_vehicles_fw/index.md +++ b/docs/zh/complete_vehicles_fw/index.md @@ -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) diff --git a/docs/zh/complete_vehicles_mc/index.md b/docs/zh/complete_vehicles_mc/index.md index b8a8f1d948..9080d8601f 100644 --- a/docs/zh/complete_vehicles_mc/index.md +++ b/docs/zh/complete_vehicles_mc/index.md @@ -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) diff --git a/docs/zh/complete_vehicles_vtol/index.md b/docs/zh/complete_vehicles_vtol/index.md index 9f32760d55..d3dc22f104 100644 --- a/docs/zh/complete_vehicles_vtol/index.md +++ b/docs/zh/complete_vehicles_vtol/index.md @@ -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) diff --git a/docs/zh/config/index.md b/docs/zh/config/index.md index 1f02d044e1..cfc1fb3515 100644 --- a/docs/zh/config/index.md +++ b/docs/zh/config/index.md @@ -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) - 设置特定传感器、可选传感器、执行器等。 diff --git a/docs/zh/config_mc/index.md b/docs/zh/config_mc/index.md index e74e71cec9..3cb84d34cf 100644 --- a/docs/zh/config_mc/index.md +++ b/docs/zh/config_mc/index.md @@ -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) - 设置特定传感器、可选传感器、执行器等。 diff --git a/docs/zh/data_links/index.md b/docs/zh/data_links/index.md index 8e2ee7e2df..03154f03ce 100644 --- a/docs/zh/data_links/index.md +++ b/docs/zh/data_links/index.md @@ -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) diff --git a/docs/zh/dev_log/logging.md b/docs/zh/dev_log/logging.md index 05ed21e709..36bb608f46 100644 --- a/docs/zh/dev_log/logging.md +++ b/docs/zh/dev_log/logging.md @@ -186,6 +186,6 @@ There are different clients that support ulog streaming: Also make sure `txerr` stays at 0. Also make sure txerr 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) diff --git a/docs/zh/dronecan/ark_cannode.md b/docs/zh/dronecan/ark_cannode.md index 994405ef9b..d7b0724f8e 100644 --- a/docs/zh/dronecan/ark_cannode.md +++ b/docs/zh/dronecan/ark_cannode.md @@ -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) diff --git a/docs/zh/dronecan/ark_flow.md b/docs/zh/dronecan/ark_flow.md index 50af8e5c9f..9507785cc7 100644 --- a/docs/zh/dronecan/ark_flow.md +++ b/docs/zh/dronecan/ark_flow.md @@ -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) diff --git a/docs/zh/dronecan/ark_flow_mr.md b/docs/zh/dronecan/ark_flow_mr.md index 6ad95d9e73..eebbbc142c 100644 --- a/docs/zh/dronecan/ark_flow_mr.md +++ b/docs/zh/dronecan/ark_flow_mr.md @@ -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) diff --git a/docs/zh/dronecan/ark_gps.md b/docs/zh/dronecan/ark_gps.md index 5ffa097d86..f7284e0bae 100644 --- a/docs/zh/dronecan/ark_gps.md +++ b/docs/zh/dronecan/ark_gps.md @@ -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) diff --git a/docs/zh/dronecan/ark_mosaic__rtk_gps.md b/docs/zh/dronecan/ark_mosaic__rtk_gps.md index 24193f8de8..fb3851bd85 100644 --- a/docs/zh/dronecan/ark_mosaic__rtk_gps.md +++ b/docs/zh/dronecan/ark_mosaic__rtk_gps.md @@ -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) diff --git a/docs/zh/dronecan/ark_rtk_gps.md b/docs/zh/dronecan/ark_rtk_gps.md index a30768e7dd..eb4d580f7e 100644 --- a/docs/zh/dronecan/ark_rtk_gps.md +++ b/docs/zh/dronecan/ark_rtk_gps.md @@ -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) diff --git a/docs/zh/dronecan/ark_teseo_gps.md b/docs/zh/dronecan/ark_teseo_gps.md index d5a3285f01..04313dc583 100644 --- a/docs/zh/dronecan/ark_teseo_gps.md +++ b/docs/zh/dronecan/ark_teseo_gps.md @@ -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) diff --git a/docs/zh/flight_controller/accton-godwit_ga1.md b/docs/zh/flight_controller/accton-godwit_ga1.md index 20e78c102b..1c3f0a39ff 100644 --- a/docs/zh/flight_controller/accton-godwit_ga1.md +++ b/docs/zh/flight_controller/accton-godwit_ga1.md @@ -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 | diff --git a/docs/zh/flight_controller/ark_pab.md b/docs/zh/flight_controller/ark_pab.md index bbdf2081e1..da170835ec 100644 --- a/docs/zh/flight_controller/ark_pab.md +++ b/docs/zh/flight_controller/ark_pab.md @@ -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) diff --git a/docs/zh/flight_controller/ark_pi6x.md b/docs/zh/flight_controller/ark_pi6x.md index 053e282c98..a8073e2658 100644 --- a/docs/zh/flight_controller/ark_pi6x.md +++ b/docs/zh/flight_controller/ark_pi6x.md @@ -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) diff --git a/docs/zh/flight_controller/ark_v6x.md b/docs/zh/flight_controller/ark_v6x.md index d03215834f..75c7cb6d8a 100644 --- a/docs/zh/flight_controller/ark_v6x.md +++ b/docs/zh/flight_controller/ark_v6x.md @@ -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) diff --git a/docs/zh/flight_controller/auav_x2.md b/docs/zh/flight_controller/auav_x2.md index 04db108057..803d492ce6 100644 --- a/docs/zh/flight_controller/auav_x2.md +++ b/docs/zh/flight_controller/auav_x2.md @@ -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 | | diff --git a/docs/zh/flight_controller/cuav_pixhawk_v6x.md b/docs/zh/flight_controller/cuav_pixhawk_v6x.md index 867935b932..814c52b10a 100644 --- a/docs/zh/flight_controller/cuav_pixhawk_v6x.md +++ b/docs/zh/flight_controller/cuav_pixhawk_v6x.md @@ -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 | ## 额定电压 diff --git a/docs/zh/flight_controller/cuav_v5.md b/docs/zh/flight_controller/cuav_v5.md index 5136fa5116..b73968cf07 100644 --- a/docs/zh/flight_controller/cuav_v5.md +++ b/docs/zh/flight_controller/cuav_v5.md @@ -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 | diff --git a/docs/zh/flight_controller/cuav_v5_nano.md b/docs/zh/flight_controller/cuav_v5_nano.md index 70e48783aa..c8f1c37c32 100644 --- a/docs/zh/flight_controller/cuav_v5_nano.md +++ b/docs/zh/flight_controller/cuav_v5_nano.md @@ -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) | diff --git a/docs/zh/flight_controller/cuav_v5_plus.md b/docs/zh/flight_controller/cuav_v5_plus.md index 29f628ead0..49b6aa6d2d 100644 --- a/docs/zh/flight_controller/cuav_v5_plus.md +++ b/docs/zh/flight_controller/cuav_v5_plus.md @@ -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 | diff --git a/docs/zh/flight_controller/cuav_x25-evo.md b/docs/zh/flight_controller/cuav_x25-evo.md index baa18091b4..ec68641440 100644 --- a/docs/zh/flight_controller/cuav_x25-evo.md +++ b/docs/zh/flight_controller/cuav_x25-evo.md @@ -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 | ## 额定电压 diff --git a/docs/zh/flight_controller/cubepilot_cube_orange.md b/docs/zh/flight_controller/cubepilot_cube_orange.md index 5af04e96a0..1ab22c5bdb 100644 --- a/docs/zh/flight_controller/cubepilot_cube_orange.md +++ b/docs/zh/flight_controller/cubepilot_cube_orange.md @@ -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 | diff --git a/docs/zh/flight_controller/cubepilot_cube_orangeplus.md b/docs/zh/flight_controller/cubepilot_cube_orangeplus.md index c117bea8aa..b45014c233 100644 --- a/docs/zh/flight_controller/cubepilot_cube_orangeplus.md +++ b/docs/zh/flight_controller/cubepilot_cube_orangeplus.md @@ -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 | diff --git a/docs/zh/flight_controller/cubepilot_cube_yellow.md b/docs/zh/flight_controller/cubepilot_cube_yellow.md index cbdc917433..fab8867d0c 100644 --- a/docs/zh/flight_controller/cubepilot_cube_yellow.md +++ b/docs/zh/flight_controller/cubepilot_cube_yellow.md @@ -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 | diff --git a/docs/zh/flight_controller/durandal.md b/docs/zh/flight_controller/durandal.md index 6c552d2f62..b4acc8bb09 100644 --- a/docs/zh/flight_controller/durandal.md +++ b/docs/zh/flight_controller/durandal.md @@ -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 | diff --git a/docs/zh/flight_controller/holybro_pix32.md b/docs/zh/flight_controller/holybro_pix32.md index 1f35c44ca1..14c9b08e42 100644 --- a/docs/zh/flight_controller/holybro_pix32.md +++ b/docs/zh/flight_controller/holybro_pix32.md @@ -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 | | diff --git a/docs/zh/flight_controller/holybro_pix32_v6.md b/docs/zh/flight_controller/holybro_pix32_v6.md index 383938b43c..a91aa132ca 100644 --- a/docs/zh/flight_controller/holybro_pix32_v6.md +++ b/docs/zh/flight_controller/holybro_pix32_v6.md @@ -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 | ## 尺寸 diff --git a/docs/zh/flight_controller/kakutef7.md b/docs/zh/flight_controller/kakutef7.md index 9f928b43b3..3508db0e5c 100644 --- a/docs/zh/flight_controller/kakutef7.md +++ b/docs/zh/flight_controller/kakutef7.md @@ -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) | diff --git a/docs/zh/flight_controller/kakuteh7-wing.md b/docs/zh/flight_controller/kakuteh7-wing.md index e426a8aabe..59031d431b 100644 --- a/docs/zh/flight_controller/kakuteh7-wing.md +++ b/docs/zh/flight_controller/kakuteh7-wing.md @@ -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 | diff --git a/docs/zh/flight_controller/kakuteh7.md b/docs/zh/flight_controller/kakuteh7.md index a48a394490..27c60acfde 100644 --- a/docs/zh/flight_controller/kakuteh7.md +++ b/docs/zh/flight_controller/kakuteh7.md @@ -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) | diff --git a/docs/zh/flight_controller/kakuteh7mini.md b/docs/zh/flight_controller/kakuteh7mini.md index d23416130f..23198d0064 100644 --- a/docs/zh/flight_controller/kakuteh7mini.md +++ b/docs/zh/flight_controller/kakuteh7mini.md @@ -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) | diff --git a/docs/zh/flight_controller/kakuteh7v2.md b/docs/zh/flight_controller/kakuteh7v2.md index cdd2f07aa7..d5b1f8faec 100644 --- a/docs/zh/flight_controller/kakuteh7v2.md +++ b/docs/zh/flight_controller/kakuteh7v2.md @@ -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) | diff --git a/docs/zh/flight_controller/micoair743-lite.md b/docs/zh/flight_controller/micoair743-lite.md index b3a76a0065..bf8c114b90 100644 --- a/docs/zh/flight_controller/micoair743-lite.md +++ b/docs/zh/flight_controller/micoair743-lite.md @@ -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 | diff --git a/docs/zh/flight_controller/mindpx.md b/docs/zh/flight_controller/mindpx.md index d69ba6d89b..7b3145c1bd 100644 --- a/docs/zh/flight_controller/mindpx.md +++ b/docs/zh/flight_controller/mindpx.md @@ -111,15 +111,15 @@ You can also find MindRacer at Amazon® or eBay®. ## 串口映射 -| 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 | ? | diff --git a/docs/zh/flight_controller/modalai_fc_v1.md b/docs/zh/flight_controller/modalai_fc_v1.md index 1e9562b83d..53ce071462 100644 --- a/docs/zh/flight_controller/modalai_fc_v1.md +++ b/docs/zh/flight_controller/modalai_fc_v1.md @@ -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) | diff --git a/docs/zh/flight_controller/modalai_voxl_flight.md b/docs/zh/flight_controller/modalai_voxl_flight.md index 352fd22892..806ea037ad 100644 --- a/docs/zh/flight_controller/modalai_voxl_flight.md +++ b/docs/zh/flight_controller/modalai_voxl_flight.md @@ -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) | diff --git a/docs/zh/flight_controller/mro_control_zero_f7.md b/docs/zh/flight_controller/mro_control_zero_f7.md index f17ce6a8f4..564cc9d13c 100644 --- a/docs/zh/flight_controller/mro_control_zero_f7.md +++ b/docs/zh/flight_controller/mro_control_zero_f7.md @@ -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 | diff --git a/docs/zh/flight_controller/mro_pixhawk.md b/docs/zh/flight_controller/mro_pixhawk.md index 7ff5c5cd9c..afd00c790e 100644 --- a/docs/zh/flight_controller/mro_pixhawk.md +++ b/docs/zh/flight_controller/mro_pixhawk.md @@ -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 | | diff --git a/docs/zh/flight_controller/mro_x2.1.md b/docs/zh/flight_controller/mro_x2.1.md index d54c36cd5e..f22b80daa1 100644 --- a/docs/zh/flight_controller/mro_x2.1.md +++ b/docs/zh/flight_controller/mro_x2.1.md @@ -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 | diff --git a/docs/zh/flight_controller/nxp_mr_vmu_rt1176.md b/docs/zh/flight_controller/nxp_mr_vmu_rt1176.md index 06436027d7..6f3ca1b0b8 100644 --- a/docs/zh/flight_controller/nxp_mr_vmu_rt1176.md +++ b/docs/zh/flight_controller/nxp_mr_vmu_rt1176.md @@ -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 | diff --git a/docs/zh/flight_controller/omnibus_f4_sd.md b/docs/zh/flight_controller/omnibus_f4_sd.md index ca2f22a264..c1783c71d1 100644 --- a/docs/zh/flight_controller/omnibus_f4_sd.md +++ b/docs/zh/flight_controller/omnibus_f4_sd.md @@ -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 | diff --git a/docs/zh/flight_controller/pixfalcon.md b/docs/zh/flight_controller/pixfalcon.md index df1b22c5d8..0a53eb2800 100644 --- a/docs/zh/flight_controller/pixfalcon.md +++ b/docs/zh/flight_controller/pixfalcon.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhack_v3.md b/docs/zh/flight_controller/pixhack_v3.md index e9f48ca3c5..f8e7b063e9 100644 --- a/docs/zh/flight_controller/pixhack_v3.md +++ b/docs/zh/flight_controller/pixhack_v3.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhawk-2.md b/docs/zh/flight_controller/pixhawk-2.md index c92f721c6b..94272adce4 100644 --- a/docs/zh/flight_controller/pixhawk-2.md +++ b/docs/zh/flight_controller/pixhawk-2.md @@ -124,15 +124,15 @@ Board schematics and other documentation can be found here: [The Cube Project](h ### 串口映射 -| UART | 设备 | Port | -| ------ | ---------- | ---------------------------------------- | -| USART1 | /dev/ttyS0 | | -| 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 | | +| UART | 设备 | Port | +| ------ | ---------- | ------------------------------ | +| USART1 | UART | | +| USART2 | /dev/ttyS1 | TELEM1 (流控) | +| USART3 | /dev/ttyS2 | TELEM2 (流控) | +| UART4 | /dev/ttyS3 | GPS1 | +| USART6 | /dev/ttyS4 | PX4IO | +| UART7 | /dev/ttyS5 | CONSOLE | +| UART8 | /dev/ttyS6 | | diff --git a/docs/zh/flight_controller/pixhawk.md b/docs/zh/flight_controller/pixhawk.md index cbe395c9b0..6a2d7346ae 100644 --- a/docs/zh/flight_controller/pixhawk.md +++ b/docs/zh/flight_controller/pixhawk.md @@ -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 | | diff --git a/docs/zh/flight_controller/pixhawk3_pro.md b/docs/zh/flight_controller/pixhawk3_pro.md index 38a10f1cd3..a0aebc8e8e 100644 --- a/docs/zh/flight_controller/pixhawk3_pro.md +++ b/docs/zh/flight_controller/pixhawk3_pro.md @@ -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 | | diff --git a/docs/zh/flight_controller/pixhawk4.md b/docs/zh/flight_controller/pixhawk4.md index 5930e4db48..9ae81b06e0 100644 --- a/docs/zh/flight_controller/pixhawk4.md +++ b/docs/zh/flight_controller/pixhawk4.md @@ -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 | ## 尺寸 diff --git a/docs/zh/flight_controller/pixhawk4_mini.md b/docs/zh/flight_controller/pixhawk4_mini.md index 1a73ddc3c2..e3921cbf63 100644 --- a/docs/zh/flight_controller/pixhawk4_mini.md +++ b/docs/zh/flight_controller/pixhawk4_mini.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhawk5x.md b/docs/zh/flight_controller/pixhawk5x.md index 456b61315f..e0d6177760 100644 --- a/docs/zh/flight_controller/pixhawk5x.md +++ b/docs/zh/flight_controller/pixhawk5x.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhawk6c.md b/docs/zh/flight_controller/pixhawk6c.md index d344238d42..b950285f81 100644 --- a/docs/zh/flight_controller/pixhawk6c.md +++ b/docs/zh/flight_controller/pixhawk6c.md @@ -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 | ## 尺寸 diff --git a/docs/zh/flight_controller/pixhawk6c_mini.md b/docs/zh/flight_controller/pixhawk6c_mini.md index 1973aa00b6..a5e6079313 100644 --- a/docs/zh/flight_controller/pixhawk6c_mini.md +++ b/docs/zh/flight_controller/pixhawk6c_mini.md @@ -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)) diff --git a/docs/zh/flight_controller/pixhawk6x-rt.md b/docs/zh/flight_controller/pixhawk6x-rt.md index cddcc6d4c6..bb3b3fa805 100644 --- a/docs/zh/flight_controller/pixhawk6x-rt.md +++ b/docs/zh/flight_controller/pixhawk6x-rt.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhawk6x.md b/docs/zh/flight_controller/pixhawk6x.md index 8212476581..aec1d331f4 100644 --- a/docs/zh/flight_controller/pixhawk6x.md +++ b/docs/zh/flight_controller/pixhawk6x.md @@ -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 | diff --git a/docs/zh/flight_controller/pixhawk6x_pro.md b/docs/zh/flight_controller/pixhawk6x_pro.md index 02b3d67618..d93f74cf9a 100644 --- a/docs/zh/flight_controller/pixhawk6x_pro.md +++ b/docs/zh/flight_controller/pixhawk6x_pro.md @@ -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) diff --git a/docs/zh/flight_controller/pixhawk_series.md b/docs/zh/flight_controller/pixhawk_series.md index 6e98320632..20b01255b5 100644 --- a/docs/zh/flight_controller/pixhawk_series.md +++ b/docs/zh/flight_controller/pixhawk_series.md @@ -100,6 +100,24 @@ At very high level, the main differences are: +### 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). diff --git a/docs/zh/flight_controller/pixracer.md b/docs/zh/flight_controller/pixracer.md index 2af7add617..2510ed17b1 100644 --- a/docs/zh/flight_controller/pixracer.md +++ b/docs/zh/flight_controller/pixracer.md @@ -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 | | diff --git a/docs/zh/flight_controller/raccoonlab_fmu6x.md b/docs/zh/flight_controller/raccoonlab_fmu6x.md index 844a685878..ab1f90407d 100644 --- a/docs/zh/flight_controller/raccoonlab_fmu6x.md +++ b/docs/zh/flight_controller/raccoonlab_fmu6x.md @@ -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 | diff --git a/docs/zh/flight_controller/radiolink_pix6.md b/docs/zh/flight_controller/radiolink_pix6.md index c5edb6ee19..61be8aeacb 100644 --- a/docs/zh/flight_controller/radiolink_pix6.md +++ b/docs/zh/flight_controller/radiolink_pix6.md @@ -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 diff --git a/docs/zh/flight_controller/svehicle_e2.md b/docs/zh/flight_controller/svehicle_e2.md index d34e22e553..6bbcb05a8d 100644 --- a/docs/zh/flight_controller/svehicle_e2.md +++ b/docs/zh/flight_controller/svehicle_e2.md @@ -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 diff --git a/docs/zh/flight_controller/thepeach_k1.md b/docs/zh/flight_controller/thepeach_k1.md index 8f831afaba..3f69940c1a 100644 --- a/docs/zh/flight_controller/thepeach_k1.md +++ b/docs/zh/flight_controller/thepeach_k1.md @@ -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 | ## 额定电压 diff --git a/docs/zh/flight_controller/thepeach_r1.md b/docs/zh/flight_controller/thepeach_r1.md index 1be40738ba..f4a4cb7281 100644 --- a/docs/zh/flight_controller/thepeach_r1.md +++ b/docs/zh/flight_controller/thepeach_r1.md @@ -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 | diff --git a/docs/zh/flight_modes_fw/hold.md b/docs/zh/flight_modes_fw/hold.md index 437613fbb0..c626e198d9 100644 --- a/docs/zh/flight_modes_fw/hold.md +++ b/docs/zh/flight_modes_fw/hold.md @@ -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. | | [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) diff --git a/docs/zh/flight_modes_fw/land.md b/docs/zh/flight_modes_fw/land.md index 0a4220437d..2bb388a0a7 100644 --- a/docs/zh/flight_modes_fw/land.md +++ b/docs/zh/flight_modes_fw/land.md @@ -48,7 +48,7 @@ Land mode behaviour can be configured using the parameters below. | [FW_LND_AIRSPD](../advanced_config/parameter_reference.md#FW_LND_AIRSPD) | The airspeed setpoint. | | [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) diff --git a/docs/zh/flight_modes_fw/mission.md b/docs/zh/flight_modes_fw/mission.md index 63425174ba..e3d9dcb654 100644 --- a/docs/zh/flight_modes_fw/mission.md +++ b/docs/zh/flight_modes_fw/mission.md @@ -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) diff --git a/docs/zh/flight_modes_fw/return.md b/docs/zh/flight_modes_fw/return.md index 62eefc6e2d..db71badb10 100644 --- a/docs/zh/flight_modes_fw/return.md +++ b/docs/zh/flight_modes_fw/return.md @@ -61,7 +61,7 @@ The others are relevant if the destination is a rally point or the home location | [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)). | | [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) diff --git a/docs/zh/flight_modes_fw/takeoff.md b/docs/zh/flight_modes_fw/takeoff.md index 593c1f61e0..4561d8c8e4 100644 --- a/docs/zh/flight_modes_fw/takeoff.md +++ b/docs/zh/flight_modes_fw/takeoff.md @@ -142,7 +142,7 @@ Runway takeoff is affected by the following parameters: | [FW_WING_SPAN](../advanced_config/parameter_reference.md#FW_WING_SPAN) | The wingspan of the vehicle. Used to prevent wingstrikes. | | [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) diff --git a/docs/zh/flight_modes_mc/hold.md b/docs/zh/flight_modes_mc/hold.md index e65feb8774..605746c6f0 100644 --- a/docs/zh/flight_modes_mc/hold.md +++ b/docs/zh/flight_modes_mc/hold.md @@ -43,6 +43,6 @@ Hold mode behaviour can be configured using the parameters below. -## See Also +## 另见 [Hold Mode (FW)](../flight_modes_fw/hold.md) diff --git a/docs/zh/flight_modes_mc/land.md b/docs/zh/flight_modes_mc/land.md index f3cfe60a07..70f6c5d843 100644 --- a/docs/zh/flight_modes_mc/land.md +++ b/docs/zh/flight_modes_mc/land.md @@ -38,7 +38,7 @@ Land mode behaviour can be configured using the parameters below. | [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 模式启用此功能，默认情况下在自动模式下启用此功能。 | | [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) diff --git a/docs/zh/flight_modes_mc/mission.md b/docs/zh/flight_modes_mc/mission.md index 77cd340405..7b8b03cb2d 100644 --- a/docs/zh/flight_modes_mc/mission.md +++ b/docs/zh/flight_modes_mc/mission.md @@ -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) diff --git a/docs/zh/flight_modes_mc/position.md b/docs/zh/flight_modes_mc/position.md index 023c8b95b8..f32b4f357b 100644 --- a/docs/zh/flight_modes_mc/position.md +++ b/docs/zh/flight_modes_mc/position.md @@ -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) diff --git a/docs/zh/flight_modes_mc/position_slow.md b/docs/zh/flight_modes_mc/position_slow.md index d89bf42aff..24a81c5985 100644 --- a/docs/zh/flight_modes_mc/position_slow.md +++ b/docs/zh/flight_modes_mc/position_slow.md @@ -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) diff --git a/docs/zh/flight_modes_mc/return.md b/docs/zh/flight_modes_mc/return.md index a933ab4567..f24fd32ddc 100644 --- a/docs/zh/flight_modes_mc/return.md +++ b/docs/zh/flight_modes_mc/return.md @@ -70,7 +70,7 @@ The parameters that are relevant to multicopter (assuming the [RTL_TYPE](../adva | [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 模式启用此功能，默认情况下在自动模式下启用此功能。 | | [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) diff --git a/docs/zh/flight_modes_mc/takeoff.md b/docs/zh/flight_modes_mc/takeoff.md index beed798c98..0cb1d3460f 100644 --- a/docs/zh/flight_modes_mc/takeoff.md +++ b/docs/zh/flight_modes_mc/takeoff.md @@ -36,7 +36,7 @@ Takeoff is affected by the following parameters: | [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 模式启用此功能，默认情况下在自动模式下启用此功能。 | | [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) diff --git a/docs/zh/flight_modes_mc/throw_launch.md b/docs/zh/flight_modes_mc/throw_launch.md index 8bfa6c55f3..d421442b5f 100644 --- a/docs/zh/flight_modes_mc/throw_launch.md +++ b/docs/zh/flight_modes_mc/throw_launch.md @@ -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). diff --git a/docs/zh/flight_modes_vtol/land.md b/docs/zh/flight_modes_vtol/land.md index 681bcf18fd..3da643d652 100644 --- a/docs/zh/flight_modes_vtol/land.md +++ b/docs/zh/flight_modes_vtol/land.md @@ -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) diff --git a/docs/zh/flight_modes_vtol/mission.md b/docs/zh/flight_modes_vtol/mission.md index ed4ffa878d..ca31540873 100644 --- a/docs/zh/flight_modes_vtol/mission.md +++ b/docs/zh/flight_modes_vtol/mission.md @@ -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) diff --git a/docs/zh/flight_modes_vtol/return.md b/docs/zh/flight_modes_vtol/return.md index 4905e2654e..34876f9f68 100644 --- a/docs/zh/flight_modes_vtol/return.md +++ b/docs/zh/flight_modes_vtol/return.md @@ -81,7 +81,7 @@ The others are relevant if the destination is a rally point or the home location | [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). | | [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) diff --git a/docs/zh/flying/basic_flying_mc.md b/docs/zh/flying/basic_flying_mc.md index 8bda6719e8..2f2cd8ac60 100644 --- a/docs/zh/flying/basic_flying_mc.md +++ b/docs/zh/flying/basic_flying_mc.md @@ -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) diff --git a/docs/zh/frames_multicopter/dji_f450_cuav_5nano.md b/docs/zh/frames_multicopter/dji_f450_cuav_5nano.md index d0310b1cb2..325680e123 100644 --- a/docs/zh/frames_multicopter/dji_f450_cuav_5nano.md +++ b/docs/zh/frames_multicopter/dji_f450_cuav_5nano.md @@ -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 | diff --git a/docs/zh/frames_multicopter/dji_f450_cuav_5plus.md b/docs/zh/frames_multicopter/dji_f450_cuav_5plus.md index 8fbd134973..60e86e05be 100644 --- a/docs/zh/frames_multicopter/dji_f450_cuav_5plus.md +++ b/docs/zh/frames_multicopter/dji_f450_cuav_5plus.md @@ -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 | diff --git a/docs/zh/frames_multicopter/holybro_s500_v2_pixhawk4.md b/docs/zh/frames_multicopter/holybro_s500_v2_pixhawk4.md index 57b595740f..5f1a97d4ff 100644 --- a/docs/zh/frames_multicopter/holybro_s500_v2_pixhawk4.md +++ b/docs/zh/frames_multicopter/holybro_s500_v2_pixhawk4.md @@ -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). diff --git a/docs/zh/frames_multicopter/holybro_x500V2_pixhawk5x.md b/docs/zh/frames_multicopter/holybro_x500V2_pixhawk5x.md index 723a3bb23b..a898733d96 100644 --- a/docs/zh/frames_multicopter/holybro_x500V2_pixhawk5x.md +++ b/docs/zh/frames_multicopter/holybro_x500V2_pixhawk5x.md @@ -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). diff --git a/docs/zh/frames_multicopter/holybro_x500_pixhawk4.md b/docs/zh/frames_multicopter/holybro_x500_pixhawk4.md index babc343497..e9c021c823 100644 --- a/docs/zh/frames_multicopter/holybro_x500_pixhawk4.md +++ b/docs/zh/frames_multicopter/holybro_x500_pixhawk4.md @@ -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). diff --git a/docs/zh/frames_multicopter/holybro_x500v2_pixhawk6c.md b/docs/zh/frames_multicopter/holybro_x500v2_pixhawk6c.md index a7a4bec9bb..4b45fdeeab 100644 --- a/docs/zh/frames_multicopter/holybro_x500v2_pixhawk6c.md +++ b/docs/zh/frames_multicopter/holybro_x500v2_pixhawk6c.md @@ -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). diff --git a/docs/zh/frames_multicopter/qav_r_5_kiss_esc_racer.md b/docs/zh/frames_multicopter/qav_r_5_kiss_esc_racer.md index 9fbeb29890..31a05cffaf 100644 --- a/docs/zh/frames_multicopter/qav_r_5_kiss_esc_racer.md +++ b/docs/zh/frames_multicopter/qav_r_5_kiss_esc_racer.md @@ -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). diff --git a/docs/zh/frames_rover/index.md b/docs/zh/frames_rover/index.md index 76b1749d4f..7c6b4bffbc 100644 --- a/docs/zh/frames_rover/index.md +++ b/docs/zh/frames_rover/index.md @@ -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) diff --git a/docs/zh/gps_compass/ark_sam_gps.md b/docs/zh/gps_compass/ark_sam_gps.md index 8354054a20..8c2301c671 100644 --- a/docs/zh/gps_compass/ark_sam_gps.md +++ b/docs/zh/gps_compass/ark_sam_gps.md @@ -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) diff --git a/docs/zh/gps_compass/index.md b/docs/zh/gps_compass/index.md index db0a4584d9..3f846a2f4a 100644 --- a/docs/zh/gps_compass/index.md +++ b/docs/zh/gps_compass/index.md @@ -197,6 +197,14 @@ It is possible to have low DOP (good satellite geometry) but still have high EPH EPH/EPV values therefore provide a more immediate and practical estimate of the actual GPS accuracy you can expect under current conditions. +### GNSS Position Fusion + +GNSS position fusion will not begin until yaw alignment is established. +If a magnetometer is available, the EKF aligns yaw using the magnetic heading, allowing GPS position fusion to start soon after boot. +If no magnetometer is present, the system must rely on GPS yaw (from a dual-antenna setup) or movement-based yaw estimation. +Until one of these provides a valid heading, the EKF will not start GPS position fusion, and the vehicle will remain in a “no position” state even though attitude data is valid. +This behavior prevents large position errors that could occur when the yaw reference is uncertain. + ## 开发人员信息 - GPS/RTK-GPS diff --git a/docs/zh/hardware/serial_port_mapping.md b/docs/zh/hardware/serial_port_mapping.md index 9799e398b4..3a3bdca5b9 100644 --- a/docs/zh/hardware/serial_port_mapping.md +++ b/docs/zh/hardware/serial_port_mapping.md @@ -1,27 +1,27 @@ # 串口映射 -This topic shows how to determine the mapping between USART/UART serial port device names (e.g. "ttyS0") and the associated ports on a flight controller, such as `TELEM1`, `TELEM2`, `GPS1`, `RC SBUS`, `Debug console`. +本主题说明如何确定USART/UART串行端口（下称串口）设备名称(例如“ttyS0”)与飞行控制器上对应端口（如`TELEM1`、`TELEM2`、`GPS1`、`RC SBUS`、`调试控制台(Debug console)`）之间的映射关系。 -The instructions are used to generate serial port mapping tables in flight controller documentation. -For example: [Pixhawk 4 > Serial Port Mapping](../flight_controller/pixhawk4.md#serial-port-mapping). +这份说明用于在飞行控制器文档中生成串行端口映射表。 +例如： [Pixhawk 4 > Serial Port Mapping](../flight_controller/pixhawk4.md#serial-port-mapping)。 :::info -The function assigned to each port does not _have to_ match the name (in most cases), and is set using a [Serial Port Configuration](../peripherals/serial_configuration.md). -Usually the port function is configured to match the name, which is why the port labelled `GPS1` will work with a GPS out of the box. +每个端口分配的功能不必与名称匹配（大多数情况下），并通过[串行端口配置](../peripherals/serial_configuration.md)。 +通常情况下端口功能是与名称相匹配的，因此标记为`GPS1`的端口可直接连接GPS设备。 ::: -## NuttX on STMxxyyy +## NuttX 在 STMxxyyy 上 -This section shows how to get the mappings for NuttX builds on STMxxyyy architectures by inspecting the board configuration files. -The instructions use FMUv5, but can similarly be extended for other FMU versions/NuttX boards. +本节将展示如何通过检查板载配置文件，获取在STMxxyyy架构上构建NuttX所需的映射信息。 +该说明使用FMUv5，但同样可扩展至其他FMU版本/NuttX开发板。 -### default.px4board +### -The **default.px4board** lists a number of serial port mappings (search for the text "SERIAL_PORTS"). +**default.px4board** 文件列出了若干串行端口映射（搜索文本“SERIAL_PORTS”）。 -From [/boards/px4/fmu-v5/default.px4board](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/default.px4board): +来自 [/boards/px4/fmu-v5/default.px4board](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/default.px4board): ``` CONFIG_BOARD_SERIAL_GPS1="/dev/ttyS0" @@ -30,7 +30,7 @@ CONFIG_BOARD_SERIAL_TEL2="/dev/ttyS2" CONFIG_BOARD_SERIAL_TEL4="/dev/ttyS3" ``` -Alternatively you can launch boardconfig using `make px4_fmu-v5 boardconfig` and access the serial port menu +或者，您可以通过执行 `make px4_fmu-v5 boardconfig` 启动板配置工具，并进入串口菜单。 ``` Serial ports ---> @@ -48,12 +48,12 @@ Alternatively you can launch boardconfig using `make px4_fmu-v5 boardconfig` and ### nsh/defconfig -The _nsh/defconfig_ allows you to determine which ports are defined, whether they are UART or USARTs, and the mapping between USART/UART and device. -You can also determine which port is used for the [serial/debug console](../debug/system_console.md). +_nsh/defconfig_ 允许您确定哪些端口被定义，它们是 UART 还是 USART，以及 USART/UART 与设备之间的映射关系。 +您还可以确定用于该功能的端口[serial/debug console](../debug/system_console.md)。 -Open the board's defconfig file, for example: [/boards/px4/fmu-v5/nuttx-config/nsh/defconfig](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/nuttx-config/nsh/defconfig#L215-L221) +打开板载的 defconfig 配置文件，例如：[/boards/px4/fmu-v5/nuttx-config/nsh/defconfig](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/nuttx-config/nsh/defconfig#L215-L221) -Search for the text "ART" until you find a section like with entries formatted like `CONFIG_STM32xx_USARTn=y` (where `xx` is a processor type and `n` is a port number). +搜索文本“ART”，直到找到类似以下格式的条目：`CONFIG_STM32xx_USARTn=y`（其中`xx`表示处理器类型，`n`表示端口号）。 例如： ``` @@ -66,10 +66,10 @@ CONFIG_STM32F7_USART3=y CONFIG_STM32F7_USART6=y ``` -The entries tell you which ports are defined, and whether they are UART or USART. +这些条目会告知您哪些端口已被定义，以及它们属于UART还是USART。 -Copy the section above and reorder numerically by "n". -Increment the device number _ttyS**n**_ alongside (zero based) to get the device-to-serial-port mapping. +复制上方段落，按“n”进行数字排序。 +同时递增设备编号ttySn（基于零的计数），以获取设备到串行端口的映射关系。 ``` ttyS0 CONFIG_STM32F7_USART1=y @@ -81,8 +81,8 @@ ttyS5 CONFIG_STM32F7_UART7=y ttyS6 CONFIG_STM32F7_UART8=y ``` -To get the DEBUG console mapping we search the [defconfig file](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/nuttx-config/nsh/defconfig#L212) for `SERIAL_CONSOLE`. -Below we see that the console is on UART7: +要获取调试控制台映射，我们需在[defconfig file](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/nuttx-config/nsh/defconfig#L212) 搜索 `SERIAL_CONSOLE`. +下面我们看到控制台位于UART7： ``` CONFIG_UART7_SERIAL_CONSOLE=y @@ -90,9 +90,9 @@ CONFIG_UART7_SERIAL_CONSOLE=y ### board_config.h -For flight controllers that have an IO board, determine the PX4IO connection from **board_config.h** by searching for `PX4IO_SERIAL_DEVICE`. +对于配备IO板的飞行控制器，请通过在**board_config.h**文件中搜索`PX4IO_SERIAL_DEVICE`来确定PX4IO连接。 -For example, [/boards/px4/fmu-v5/src/board_config.h](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/src/board_config.h#L59): +例如 [/boards/px4/fmu-v5/src/board_config.h](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v5/src/board_config.h#L59)： ``` #define PX4IO_SERIAL_DEVICE "/dev/ttyS6" @@ -101,11 +101,11 @@ For example, [/boards/px4/fmu-v5/src/board_config.h](https://github.com/PX4/PX4- #define PX4IO_SERIAL_BASE STM32_UART8_BASE ``` -So the PX4IO is on `ttyS6` (we can also see that this maps to UART8, which we already knew from the preceding section). +PX4IO 位于 `ttyS6` 上（我们还可以看到它映射到 UART8，这一点我们从前一节已经知道）。 -### Putting it all together +### 整合所有内容 -The final mapping is: +最终映射表如下： ``` ttyS0 CONFIG_STM32F7_USART1=y GPS1 @@ -117,17 +117,17 @@ ttyS5 CONFIG_STM32F7_UART7=y DEBUG ttyS6 CONFIG_STM32F7_UART8=y PX4IO ``` -In the [flight controller docs](../flight_controller/pixhawk4.md#serial-port-mapping) the resulting table is: +在 [flight controller docs]../flight_controller/pixhawk4.md#serial-port-mapping最终生成的表格如下： -| 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 | ## Other Architectures @@ -135,7 +135,7 @@ In the [flight controller docs](../flight_controller/pixhawk4.md#serial-port-map Contributions welcome! ::: -## See Also +## 另见 - [Serial Port Configuration](../peripherals/serial_configuration.md) - [MAVLink Telemetry (OSD/GCS)](../peripherals/mavlink_peripherals.md) diff --git a/docs/zh/middleware/uorb.md b/docs/zh/middleware/uorb.md index 54af3bd7e9..2f190bb439 100644 --- a/docs/zh/middleware/uorb.md +++ b/docs/zh/middleware/uorb.md @@ -278,7 +278,7 @@ For more information see: [Plotting uORB Topic Data in Real Time using PlotJuggl -## See Also +## 另见 - _PX4 uORB Explained_ Blog series - [Part 1](https://px4.io/px4-uorb-explained-part-1/) diff --git a/docs/zh/middleware/uxrce_dds.md b/docs/zh/middleware/uxrce_dds.md index 91e1a4c87a..93908a76ee 100644 --- a/docs/zh/middleware/uxrce_dds.md +++ b/docs/zh/middleware/uxrce_dds.md @@ -516,6 +516,11 @@ publications: - topic: /fmu/out/vehicle_trajectory_waypoint_desired type: px4_msgs::msg::VehicleTrajectoryWaypoint + - topic: /fmu/out/vehicle_imu + type: px4_msgs::msg::VehicleImu + rate_limit: 50. + instance: 1 # OPTIONAL + subscriptions: - topic: /fmu/in/offboard_control_mode @@ -548,6 +553,9 @@ Each (`topic`,`type`) pairs defines: 4. The message type (`VehicleOdometry`, `VehicleStatus`, `OffboardControlMode`, etc.) and the ROS 2 package (`px4_msgs`) that is expected to provide the message definition. 5. **(Optional)**: An additional `rate_limit` field (only for publication entries), which specifies the maximum rate (Hz) at which messages will be published on this topic by PX4 to ROS 2. If left unspecified, the maximum publication rate limit is set to 100 Hz. +6. **(Optional)**: An additional `instance` field (only for publication entries), which lets you select which instance of a [multi-instance topic](./uorb.md#multi-instance) you want to be published to ROS 2. + If provided, this option changes the ROS 2 topic name of the advertised uORB topic appending the instance number: `fmu/out/[uorb topic name][instance]` (plus eventual namespace and message version). + In the example above the final topic name would be `/fmu/out/vehicle_imu1`. `subscriptions` and `subscriptions_multi` allow us to choose the uORB topic instance that ROS 2 topics are routed to: either a shared instance that may also be getting updates from internal PX4 uORB publishers, or a separate instance that is reserved for ROS2 publications, respectively. Without this mechanism all ROS 2 messages would be routed to the _same_ uORB topic instance (because ROS 2 does not have the concept of [multiple topic instances](../middleware/uorb.md#multi-instance)), and it would not be possible for PX4 subscribers to differentiate between streams from ROS 2 or PX4 publishers. diff --git a/docs/zh/modules/hello_sky.md b/docs/zh/modules/hello_sky.md index 02e2a97e82..e1c185d810 100644 --- a/docs/zh/modules/hello_sky.md +++ b/docs/zh/modules/hello_sky.md @@ -440,6 +440,7 @@ The [complete example code](https://github.com/PX4/PX4-Autopilot/blob/main/src/e */ #include +#include #include #include #include diff --git a/docs/zh/peripherals/mavlink_peripherals.md b/docs/zh/peripherals/mavlink_peripherals.md index ed88794411..94f8cc82cf 100644 --- a/docs/zh/peripherals/mavlink_peripherals.md +++ b/docs/zh/peripherals/mavlink_peripherals.md @@ -119,7 +119,7 @@ Links to setup instructions for specific MAVLink components: - [MAVLink Cameras (Camera Protocol v2) > PX4 Configuration](../camera/mavlink_v2_camera.md#px4-configuration) - [Gimbal Configuration > MAVLink Gimbal (MNT_MODE_OUT=MAVLINK)](../advanced/gimbal_control.md#mavlink-gimbal-mnt-mode-out-mavlink) -## See Also +## 另见 - [Serial Port Configuration](../peripherals/serial_configuration.md) - [PX4 Ethernet Setup > PX4 MAVLink Serial Port Configuration](../advanced_config/ethernet_setup.md#px4-mavlink-serial-port-configuration) diff --git a/docs/zh/peripherals/remote_id.md b/docs/zh/peripherals/remote_id.md index b3188fb10c..3cfc7bcde4 100644 --- a/docs/zh/peripherals/remote_id.md +++ b/docs/zh/peripherals/remote_id.md @@ -257,6 +257,6 @@ If the Remote ID CAN node is present and the messages are not being received, th Once configured, check the MAVLink Inspector again and check that the `OPEN_DRONE_ID_BASIC_ID` and `OPEN_DRONE_ID_LOCATION` messages are now present. -## See Also +## 另见 - [Remote Identification of Drones](https://www.faa.gov/uas/getting_started/remote_id) (FAA) diff --git a/docs/zh/power_module/ark_12s_pab_power_module.md b/docs/zh/power_module/ark_12s_pab_power_module.md index 21c3e5ca77..4f262920bd 100644 --- a/docs/zh/power_module/ark_12s_pab_power_module.md +++ b/docs/zh/power_module/ark_12s_pab_power_module.md @@ -47,6 +47,6 @@ Order this module from: - Set the `INA238_SHUNT` parameter to 0.0001. - Reboot the flight controller. -## See Also +## 另见 - [ARK 12S PAB Power Module Documentation](https://arkelectron.gitbook.io/ark-documentation/power/ark-12s-pab-power-module) (ARK Docs) diff --git a/docs/zh/power_module/ark_pab_power_module.md b/docs/zh/power_module/ark_pab_power_module.md index 24bd243862..a2d3977bd7 100644 --- a/docs/zh/power_module/ark_pab_power_module.md +++ b/docs/zh/power_module/ark_pab_power_module.md @@ -48,6 +48,6 @@ Order this module from: - Enable the SENS_EN_INA226 parameter if it not enabled. - Reboot the flight controller. -## See Also +## 另见 - [ARK PAB Power Module Documentation](https://arkelectron.gitbook.io/ark-documentation/power/ark-pab-power-module) (ARK Docs) diff --git a/docs/zh/power_module/holybro_pm02d.md b/docs/zh/power_module/holybro_pm02d.md index 1de3c25724..5660abda66 100644 --- a/docs/zh/power_module/holybro_pm02d.md +++ b/docs/zh/power_module/holybro_pm02d.md @@ -49,6 +49,6 @@ For this module you must instead enable parameter [SENS_EN_INA226](../advanced_c Note that the current divider and voltage divider should not be set in the [Battery Configuration](../config/battery.md) (the default values are accurate within 5%). -## See Also +## 另见 - [Digital Power Module (PM) Setup](https://docs.holybro.com/power-module-and-pdb/power-module/digital-power-module-pm-setup#px4-setup) (Manufacturer guide) diff --git a/docs/zh/ros/mavros_installation.md b/docs/zh/ros/mavros_installation.md index 91c41c9fc5..6568e755d3 100644 --- a/docs/zh/ros/mavros_installation.md +++ b/docs/zh/ros/mavros_installation.md @@ -201,7 +201,7 @@ The [MAVROS Offboard Example (C++)](../ros/mavros_offboard_cpp.md), will show yo If you have an example app using the PX4 Autopilot and MAVROS, we can help you get it on our docs. ::: -## See Also +## 另见 - [mavros ROS Package Summary](https://wiki.ros.org/mavros#mavros.2BAC8-Plugins.sys_status) - [mavros source](https://github.com/mavlink/mavros/) diff --git a/docs/zh/ros2/offboard_control.md b/docs/zh/ros2/offboard_control.md index 5ae2e2973d..07945ac9ea 100644 --- a/docs/zh/ros2/offboard_control.md +++ b/docs/zh/ros2/offboard_control.md @@ -217,6 +217,6 @@ void OffboardControl::publish_vehicle_command(uint16_t command, float param1, fl 参数字段和 指令字段对应于 [MAVLink commands](https://mavlink.io/en/messages/common.html#mav_commands)以及他们的参数值 ::: -## See Also +## 另见 - [Python ROS2 offboard examples with PX4](https://github.com/Jaeyoung-Lim/px4-offboard) (Jaeyoung-Lim/px4-offboard). diff --git a/docs/zh/sensor/airspeed.md b/docs/zh/sensor/airspeed.md index 6e5a796164..0442aae34f 100644 --- a/docs/zh/sensor/airspeed.md +++ b/docs/zh/sensor/airspeed.md @@ -73,7 +73,7 @@ Airspeed sensors should be calibrated by following the instructions: [Basic Conf For more advanced validation, configuration and debugging see [Airspeed Validation](../advanced_config/airspeed_validation.md). -## See Also +## 另见 - [Using PX4's Navigation Filter (EKF2) > Airspeed](../advanced_config/tuning_the_ecl_ekf.md#airspeed) - [Airspeed drivers](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/differential_pressure) (source code) diff --git a/docs/zh/telemetry/crsf_telemetry.md b/docs/zh/telemetry/crsf_telemetry.md index b265e83580..cbb8abf219 100644 --- a/docs/zh/telemetry/crsf_telemetry.md +++ b/docs/zh/telemetry/crsf_telemetry.md @@ -213,7 +213,7 @@ The supported telemetry messages and their source are listed below (this table i | FM | Flight mode | FC | | VSPD | Barometer | FC | -## See Also +## 另见 - [TBS Crossfire Manual](https://www.team-blacksheep.com/media/files/tbs-crossfire-manual.pdf) - [ExpressLRS Documentation](https://www.expresslrs.org/quick-start/getting-started/)