New Crowdin translations - zh-CN (#26488)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-05-26 17:36:40 +08:00 · 2026-02-18 16:44:34 +11:00
parent 7ef57f6262
commit 47d5971f42
314 changed files with 11960 additions and 1374 deletions
@@ -179,6 +179,7 @@
      - [CubePilot Cube Orange (CubePilot)](flight_controller/cubepilot_cube_orange.md)
      - [CubePilot Cube Yellow (CubePilot)](flight_controller/cubepilot_cube_yellow.md)
        - [Cube Wiring Quickstart](assembly/quick_start_cube.md)
+      - [Gear Up AirBrainH743](flight_controller/gearup_airbrainh743.md)
      - [Holybro Kakute H7v2](flight_controller/kakuteh7v2.md)
      - [Holybro Kakute H7mini](flight_controller/kakuteh7mini.md)
      - [Holybro Kakute H7](flight_controller/kakuteh7.md)
@@ -255,7 +256,7 @@
      - [北醒 TFmini 激光雷达](sensor/tfmini.md)
      - [LeddarOne 激光雷达](sensor/leddar_one.md)
      - [Lidar-Lite](sensor/lidar_lite.md)
-      - [Lightware Lidars (SF/LW)](sensor/sfxx_lidar.md)
+      - [Lightware Lidars (SF/LW/GRF)](sensor/sfxx_lidar.md)
        - [Lightware SF45 Rotary Lidar](sensor/sf45_rotating_lidar.md)
      - [TeraRanger](sensor/teraranger.md)
      - [✘ Lanbao PSK-CM8JL65-CC5](sensor/cm8jl65_ir_distance_sensor.md)
@@ -932,6 +933,7 @@
  - [许可证](contribute/licenses.md)

 - [版本发布](releases/index.md)
+  - [Release Process](releases/release_process.md)
  - [main (alpha)](releases/main.md)
  - [1.17 (alpha)](releases/1.17.md)
  - [1.16 (stable)](releases/1.16.md)
@@ -12,19 +12,16 @@ The [ARK Jetson Pixhawk Autopilot Bus (PAB) Carrier](https://arkelectron.gitbook
 ## 产品规格

 - **Power Requirements**
-
  - 5V
  - 4A minimum (dependent on usage and peripherals)

 - **Additional Features**
-
  - Pixhawk Autopilot Bus (PAB) Form Factor ([PAB Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-010%20Pixhawk%20Autopilot%20Bus%20Standard.pdf))
  - MicroSD Slot
  - USA-built, NDAA compliant
  - Integrated 1W heater for sensor stability in extreme conditions

 - **Physical Details**
-
  - Weight:
    - Without Jetson and Flight Controller – 80g
    - With Jetson, no heatsink or Flight Controller – 108g
@@ -170,7 +170,6 @@ To enable this MAVLink instance on the FC:
   ![Image of baseboard showing FC USB-C connector](../../assets/companion_computer/holybro_pixhawk_rpi_cm4_baseboard/baseboard_fc_usb_c.jpg)

 2. [Set the parameters](../advanced_config/parameters.md):
-
   - `MAV_1_CONFIG` = `102`
   - `MAV_1_MODE = 2`
   - `SER_TEL2_BAUD` = `921600`
@@ -184,7 +183,6 @@ On the RPi side:
 1. Connect to the RPi (using WiFi, a router, or a WiFi Dongle).

 2. Enable the RPi serial port by running `RPi-config`
-
   - Go to `3 Interface Options`, then `I6 Serial Port`.
     Then choose:
     - `login shell accessible over serial → No`
@@ -145,7 +145,6 @@ Enter the following commands (in sequence) a terminal to configure Ubuntu for RP
   ```

 3. Go to the **Interface Option** and then click **Serial Port**.
-
   - Select **No** to disable serial login shell.
   - Select **Yes** to enable the serial interface.
   - Click **Finish** and restart the RPi.
@@ -164,7 +163,6 @@ Enter the following commands (in sequence) a terminal to configure Ubuntu for RP
   ```

 6. Then save the file and restart the RPi.
-
   - In `nano` you can save the file using the following sequence of keyboard shortcuts: **ctrl+x**, **ctrl+y**, **Enter**.

 7. Check that the serial port is available.
@@ -214,7 +214,6 @@ The Lua script works by extracting the `obstacle_distance_fused` data at each ti

 3. Open PlotJuggler and navigate to the **Tools > Reactive Script Editor** section.
   In the **Script Editor** tab, add following scripts in the appropriate sections:
-
   - **Global code, executed once:**

     ```lua
@@ -33,7 +33,6 @@ The instructions below might be used to create a task named _MyTask_:
   - FlightTaskMyTask.cpp

 3. Update **CMakeLists.txt** for the new task
-
   - Copy the contents of the **CMakeLists.txt** for another task - e.g. [Orbit/CMakeLists.txt](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/flight_mode_manager/tasks/Orbit/CMakeLists.txt)

   - Update the copyright to the current year
@@ -84,16 +84,9 @@ The test steps are:
   If an [Enable/Disable Autotune Switch](#enable-disable-autotune-switch) is configured you can just toggle the switch to the "enabled" position.

   </div></div>
-
   1. In QGroundControl, open the menu **Vehicle setup > PID Tuning**:

-      ![Tuning Setup > Autotune Enabled](../../assets/qgc/setup/autotune/autotune.png)
-
-   2. Select either the _Rate Controller_ or _Attitude Controller_ tabs.
-
-   3. Ensure that the **Autotune enabled** button is enabled (this will display the **Autotune** button and remove the manual tuning selectors).
-
-   4. Read the warning popup and click on **OK** to start tuning.
+   ![Tuning Setup > Autotune Enabled](../../assets/qgc/setup/autotune/autotune.png) 2. Select either the _Rate Controller_ or _Attitude Controller_ tabs. 3. Ensure that the **Autotune enabled** button is enabled (this will display the **Autotune** button and remove the manual tuning selectors). 4. Read the warning popup and click on **OK** to start tuning.

 <div style="display: inline;" v-if="$frontmatter.frame === 'Multicopter'">

@@ -22,7 +22,6 @@ To level the horizon:
 :::

 4. Place the vehicle in its level flight orientation on a level surface:
-
   - For planes this is the position during level flight (planes tend to have their wings slightly pitched up!)
   - For copters this is the hover position.

@@ -77,7 +77,6 @@ To setup and configure a helicopter:
 3. Remove the rotor blades and propellers

 4. Assign motors and servos to outputs and test (also in [Actuator configuration](../config/actuators.md)):
-
   1. Assign the [motors and servos to the outputs](../config/actuators.md#actuator-outputs).
   2. Power the vehicle with a battery and use the [actuator testing sliders](../config/actuators.md#actuator-testing) to validate correct servo and motor assignment and direction.

@@ -140,7 +140,6 @@ The tuning procedure is:
 13. Repeat the tuning process for the attitude controller on all the axes.

 14. Repeat the tuning process for the velocity and positions controllers (on all the axes).
-
    - Use Position mode when tuning these controllers
    - Select the **Simple position control** option in the _Position control mode ..._ selector (this allows direct control for the generation of step inputs)

@@ -18,28 +18,37 @@ A drive mode will only work properly if all the configuration for the preceding

 ## Flashing the Rover Build

-Rovers use a custom build that must be flashed onto your flight controller instead of the default PX4 build:
+Rover is built as a [firmware variant](../dev_setup/building_px4.md#px4-make-build-targets), and must be installed as "Custom Firmware" in QGC (other vehicles are present in the default variant).

-1. First build the rover firmware for your flight controller from the `main` branch (there is no release build, so you can't just select this build from QGroundControl).
+The release versions of Rover firmware for different boards are attached to the associated GitHub release tag.
+For example, you can find `px4_fmu-v5x_rover.px4` on [PX4-Autopilot/releases/tag/v1.16.1](https://github.com/PX4/PX4-Autopilot/releases/tag/v1.16.1).
+For the `main` branch version of Rover you will need to [build the firmware](#building-rover).

-   To build for rover with the `make` command, replace the `_default` suffix with `_rover`.
-   For example, to build rover for px4_fmu-v6x boards, you would use the command:
+Load the firmware onto your flight controller as "Custom Firmware" (see [Loading Firmware > Installing PX4 Main, Beta or Custom Firmware](../config/firmware.md#installing-px4-main-beta-or-custom-firmware)).

-   ```sh
-   make px4_fmu-v6x_rover
-   ```
+## Building Rover

-   ::: info
-   You can also enable the modules in default builds by adding these lines to your [board configuration](../hardware/porting_guide_config.md) (e.g. for fmu-v6x you might add them to [`main/boards/px4/fmu-v6x/default.px4board`](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v6x/default.px4board)):
+Rover is built as the `rover` [firmware variant](../dev_setup/building_px4.md#px4-make-build-targets).
+What this means is that when building the firmware with the `make` command, you replace the `_default` suffix in the configuration target with `_rover`.

-   ```sh
-   CONFIG_MODULES_ROVER_ACKERMANN=y
-   CONFIG_MODULES_ROVER_DIFFERENTIAL=y
-   CONFIG_MODULES_ROVER_MECANUM=y
-   ```
+For example, to build rover for `px4_fmu-v6x` boards, you would use the following command:

-   Note that adding the rover modules may lead to flash overflow, in which case you will need to disable modules that you do not plan to use (such as those related to multicopter or fixed wing).
+```sh
+make px4_fmu-v6x_rover
+```

+Note that configuration targets are constructed with the format "VENDOR_MODEL_VARIANT".
+
+The built firmware can be installed as custom firmware, as shown above in in [Flashing the Rover Build](#flashing-the-rover-build).
+
+:::info
+You can also enable the modules in default builds by adding these lines to your [board configuration](../hardware/porting_guide_config.md) (e.g. for fmu-v6x you might add them to [`main/boards/px4/fmu-v6x/default.px4board`](https://github.com/PX4/PX4-Autopilot/blob/main/boards/px4/fmu-v6x/default.px4board)):
+
+```sh
+CONFIG_MODULES_ROVER_ACKERMANN=y
+CONFIG_MODULES_ROVER_DIFFERENTIAL=y
+CONFIG_MODULES_ROVER_MECANUM=y
+```
+
+Adding the rover modules may lead to flash overflow, in which case you will need to disable modules that you do not plan to use (such as those related to multicopter or fixed wing).
 :::
-
-2. Load the **custom firmware** that you just built onto your flight controller (see [Loading Firmware > Installing PX4 Main, Beta or Custom Firmware](../config/firmware.md#installing-px4-main-beta-or-custom-firmware)).
@@ -307,7 +307,6 @@ If the airframe is for a **new group** you additionally need to:
   ```

 3. Update _QGroundControl_:
-
   - Add the svg image for the group into: [src/AutopilotPlugins/Common/images](https://github.com/mavlink/qgroundcontrol/tree/master/src/AutoPilotPlugins/Common/Images)
   - Add reference to the svg image into [qgcimages.qrc](https://github.com/mavlink/qgroundcontrol/blob/master/qgcimages.qrc), following the pattern below:

@@ -39,16 +39,6 @@ git clone https://github.com/PX4/PX4-Autopilot.git --recursive
 make px4_sitl gz_x500
 ```

-:::details
-如果您安装的是 Gazebo Classic
-使用以下命令启动 [Gazebo SITL](../sim_gazebo_classic/index.md)：
-
-```sh
-make px4_sitl gazebo-classic
-```
-
-:::
-
 这将显示 PX4 控制台：

 ![PX4 控制台](../../assets/toolchain/console_gazebo.png)
@@ -89,6 +79,16 @@ cd PX4-Autopilot
 make px4_fmu-v5_default
 ```

+:::tip
+You can also build using the [px4-dev Docker container](../test_and_ci/docker.md) without installing the toolchain locally.
+From the PX4-Autopilot directory:
+
+```sh
+./Tools/docker_run.sh 'make px4_fmu-v5_default'
+```
+
+:::
+
 运行成功后将输出类似结果：

 ```sh
@@ -145,7 +145,8 @@ make px4_fmu-v5_default
 - [Pixhawk 1 (FMUv2)](../flight_controller/pixhawk.md): `make px4_fmu-v2_default`

  :::warning
-  您**必须**使用受支持的GCC版本来构建此开发板（例如与[CI/docker](../test_and_ci/docker.md)中使用的相同版本），否则需从构建中移除相关模块。 使用不受支持的GCC进行构建可能会失败，因为PX4接近板载1MB闪存的容量限制。
+  You **must** use a supported version of GCC to build this board (e.g. the `gcc-arm-none-eabi` package from the current Ubuntu LTS, which is the same toolchain used by CI) or remove modules from the build.
+  使用不受支持的GCC进行构建可能会失败，因为PX4接近板载1MB闪存的容量限制。

 :::

@@ -211,7 +212,7 @@ make distclean
 这对于`make px4_fmu-v2_default` 构建是常见的，它的 flash 大小被限制在 1MB。

 如果您正在构建_vanilla_master 分支，最可能的原因是使用不支持的 GCC版本。
-在这种情况下，安装[开发者工具链](../dev_setup/dev_env.md)说明中指定的版本。
+In this case, install the `gcc-arm-none-eabi` package from the current Ubuntu LTS as described in the [Developer Toolchain](../dev_setup/dev_env.md) instructions.

 如果在构建自己的分支，您可能已将固件大小增加到超过1MB的限制。
 在这种情况下，您需要从构建中删除您不需要的任何驱动程序/模块。
@@ -224,7 +225,7 @@ PX4构建系统打开大量文件，因此您可能会超出此数量。
 构建工具链为很多文件报 `Too many open files`，如下所示：

 ```sh
-/usr/local/Cellar/gcc-arm-none-eabi/20171218/bin/../lib/gcc/arm-none-eabi/7.2.1/../../../../arm-none-eabi/bin/ld: cannot find NuttX/nuttx/fs/libfs.a: Too many open files
+arm-none-eabi-ld: cannot find NuttX/nuttx/fs/libfs.a: Too many open files
 ```

 解决方案是增加允许打开文件的最大数量（例如增加到300）。
@@ -247,34 +248,9 @@ xcode-select --install
 sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/* /usr/local/include/
 ```

-### Ubuntu 18.04：涉及arm_none_eabi_gcc的编译错误
-
-与 arm_none_eabi_gcc 相关的构建问题可能是由于损坏的g++工具链安装引起的。
-您可以通过检查缺少的依赖项来验证这一点：
-
-```sh
-arm-none-eabi-gcc --version
-arm-none-eabi-g++ --version
-arm-none-eabi-gdb --version
-arm-none-eabi-size --version
-```
-
-缺少依赖项的 bash 输出示例：
-
-```sh
-arm-none-eabi-gdb --version
-arm-none-eabi-gdb: command not found
-```
-
-这个问题可以通过删除和[重新安装编译器](https://askubuntu.com/questions/1243252/how-to-install-arm-none-eabi-gdb-on-ubuntu-20-04-lts-focal-fossa)来解决。
-
-### Ubuntu 18.04：Visual Studio Code 无法监视此大型工作区中的文件更改
-
-请参阅[Visual Studio 代码 IDE (VSCode) > 疑难解答](../dev_setup/vscode.md#troubleshooting)。
-
 ### 导入Python软件包失败

-在运行 `make px4_sitl jmavsim` 命令时，“导入失败”错误表示某些Python 软件包未安装(如预期般安装)。
+"Failed to import" errors when running the `make px4_sitl gz_x500` command indicates that some Python packages are not installed (where expected).

 ```sh
 Failed to import jinja2: No module named 'jinja2'
@@ -282,12 +258,12 @@ Failed to import jinja2: No module named 'jinja2'
    pip3 install --user jinja2
 ```

-如果您已经安装了这些依赖关系，这可能是因为计算机上存在多个 Python 版本（例如 Python 2.7.16 和 Python 3.8.3），并且该模块不存在于构建工具链使用的版本中。
+If you have already installed these dependencies this may be because there is more than one Python version on the computer (e.g. Python 2.7.16 and Python 3.8.3), and the module is not present in the version used by the build toolchain.

-您应该能够按照所示明确安装依赖项来解决此问题。
+You should be able to fix this by installing the dependencies from the repository's requirements file:

 ```sh
-pip3 install --user pyserial empty toml numpy pandas jinja2 pyyaml pyros-genmsg packaging
+pip3 install --user -r Tools/setup/requirements.txt
 ```

 ## PX4 创建生成目标
@@ -23,7 +23,7 @@ A Taranis RC and a mid-range Android tablet make a very inexpensive field kit.

  - Lenovo Thinkpad with i5-core running Windows 11
  - MacBook Pro (early 2015 and later) with macOS 10.15 or later
-  - Lenovo Thinkpad i5 with Ubuntu Linux 20.04 or later
+  - Lenovo Thinkpad i5 with Ubuntu Linux 22.04 or later

 - **Ground control station** (computer or tablet):
  - iPad (may require Wifi telemetry adapter)
@@ -2,7 +2,7 @@

 The _supported platforms_ for PX4 development are:

- [Ubuntu Linux (24.04/22.04)](../dev_setup/dev_env_linux_ubuntu.md) — Recommended
+- [Ubuntu Linux (24.04/22.04)](../dev_setup/dev_env_linux_ubuntu.md)
 - [Windows (10/11)](../dev_setup/dev_env_windows_wsl.md) — via WSL2
 - [macOS](../dev_setup/dev_env_mac.md)

@@ -15,9 +15,9 @@ The _supported platforms_ for PX4 development are:
 | **NuttX based hardware:** [Pixhawk Series](../flight_controller/pixhawk_series.md), [Crazyflie](../complete_vehicles_mc/crazyflie2.md) |    &check;    | &check; | &check; |
 | **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md)                                              |    &check;    |                             |                             |
 | **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md)                                                                               |    &check;    | &check; | &check; |
-| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md)                                                                  |    &check;    | &check; | &check; |
-| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md)                                                              |    &check;    |                             | &check; |
 | **Simulation:** ROS 2 with Gazebo                                                                                                      |    &check;    |                             | &check; |
+| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md)                                                                  |                                   | &check; | &check; |
+| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md)                                                              |                                   |                             | &check; |

 Experienced Docker users can also build with the containers used by our continuous integration system: [Docker Containers](../test_and_ci/docker.md)

@@ -39,8 +39,9 @@ You may want to also install `python-pip` and `screen`.
 Execute the script below to install GCC 7-2017-q4:

 :::warning
-This version of GCC is out of date.
-At time of writing the current version on Ubuntu is `9-2020-q2-update` (see [focal nuttx docker file](https://github.com/PX4/PX4-containers/blob/master/docker/Dockerfile_nuttx-focal#L28))
+This version of GCC is very outdated.
+PX4 now uses the `gcc-arm-none-eabi` package from the current Ubuntu LTS (GCC 13.2.1 on Ubuntu 24.04).
+This CentOS guide is community-maintained and may not produce working builds.
 :::

 ```sh
@@ -4,21 +4,14 @@ The following instructions use a bash script to set up the PX4 development envir

 The environment includes:

- [Gazebo Simulator](../sim_gazebo_gz/index.md) ("Harmonic")
- [Build toolchain for Pixhawk (and other NuttX-based hardware)](../dev_setup/building_px4.md#nuttx-pixhawk-based-boards).
-
-On Ubuntu 22.04:
-
- [Gazebo Classic Simulator](../sim_gazebo_classic/index.md) can be used instead of Gazebo.
-  Gazebo is nearing feature-parity with Gazebo-Classic on PX4, and will soon replace it for all use cases.
+- [Gazebo Simulator](../sim_gazebo_gz/index.md) (Gazebo Harmonic)
+- [Build toolchain for Pixhawk (and other NuttX-based hardware)](../dev_setup/building_px4.md#nuttx-pixhawk-based-boards) using the `gcc-arm-none-eabi` compiler from the Ubuntu package manager.

 The build toolchain for other flight controllers, simulators, and working with ROS are discussed in the [Other Targets](#other-targets) section below.

-:::details
-Can I use an older version of Ubuntu?
-PX4 supports the current and last Ubuntu LTS release where possible.
-Older releases are not supported (so you can't raise defects against them), but may still work.
-For example, Gazebo Classic setup is included in our standard build instructions for macOS, Ubuntu 18.04 and 20.04, and Windows on WSL2 for the same hosts.
+:::info
+PX4 targets the **current Ubuntu LTS** (24.04) for CI and release builds, with the **previous LTS** (22.04) also supported.
+Older Ubuntu versions are not supported and may not work.
 :::

 ## Simulation and NuttX (Pixhawk) Targets
@@ -52,9 +45,7 @@ To install the toolchain:
   - 在安装过程中确认并通过所有的提示。
   - You can use the `--no-nuttx` and `--no-sim-tools` options to omit the NuttX and/or simulation tools.

-3. If you need Gazebo Classic (Ubuntu 22.04 only) then you can manually remove Gazebo and install it by following the instructions in [Gazebo Classic > Installation](../sim_gazebo_classic/index.md#installation).
-
-4. 完成后重新启动计算机。
+3. 完成后重新启动计算机。

 :::details
 Additional notes
@@ -63,10 +54,11 @@ These notes are provided "for information only":
 - This setup is supported by the PX4 Dev Team.
  The instructions may also work on other Debian Linux based systems.

- You can verify the NuttX installation by confirming the `gcc` version as shown:
+- You can verify the NuttX installation by confirming `gcc` is available.
+  The version depends on your Ubuntu release (e.g. GCC 13.2.1 on Ubuntu 24.04):

  ```sh
-  $arm-none-eabi-gcc --version
+  $ arm-none-eabi-gcc --version

  arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
  Copyright (C) 2023 Free Software Foundation, Inc.
@@ -61,20 +61,20 @@ To install WSL2 with Ubuntu on a new installation of Windows 10 or 11:
     wsl --install
     ```

-   - Ubuntu 20.04 ([Gazebo-Classic Simulation](../sim_gazebo_classic/index.md))
-
-     ```sh
-     wsl --install -d Ubuntu-20.04
-     ```
-
   - Ubuntu 22.04 ([Gazebo Simulation](../sim_gazebo_gz/index.md))

     ```sh
     wsl --install -d Ubuntu-22.04
     ```

+   - Ubuntu 24.04 ([Gazebo Simulation](../sim_gazebo_gz/index.md))
+
+     ```sh
+     wsl --install -d Ubuntu-24.04
+     ```
+
   ::: info
-   You can also install[Ubuntu 20.04](https://www.microsoft.com/store/productId/9MTTCL66CPXJ) and [Ubuntu 22.04](https://www.microsoft.com/store/productId/9PN20MSR04DW) from the store, which allows you to delete the application using the normal Windows Add/Remove settings:
+   You can also [Ubuntu 24.04](https://www.microsoft.com/store/productId/9nz3klhxdjp5) or [Ubuntu 22.04](https://www.microsoft.com/store/productId/9PN20MSR04DW) from Microsoft Store, which allows you to delete the application using the normal Windows Add/Remove settings.

 :::

@@ -110,7 +110,7 @@ To open a WSL shell using a command prompt:
   ```

   ```sh
-   wsl -d Ubuntu-20.04
+   wsl -d Ubuntu-24.04
   ```

   If you only have one version of Ubuntu, you can just use `wsl`.
@@ -61,7 +61,6 @@ You must already have installed the command line [PX4 developer environment](../
 To build:

 1. Select your build target ("cmake build config"):
-
   - The current _cmake build target_ is shown on the blue _config_ bar at the bottom (if this is already your desired target, skip to next step).
     ![Select Cmake build target](../../assets/toolchain/vscode/cmake_build_config.jpg)

@@ -133,10 +132,10 @@ Once that is done you don't need to do anything else; the toolchain will automat

 This section includes guidance on setup and build errors.

-### Ubuntu 18.04: "Visual Studio Code is unable to watch for file changes in this large workspace"
+### "Visual Studio Code is unable to watch for file changes in this large workspace"

 This error surfaces on startup.
-On some systems, there is an upper-limit of 8192 file handles imposed on applications, which means that VSCode might not be able to detect file modifications in `/PX4-Autopilot`.
+On some systems, there is an upper-limit on file handles imposed on applications, which means that VSCode might not be able to detect file modifications in `/PX4-Autopilot`.

 You can increase this limit to avoid the error, at the expense of memory consumption.
 Follow the [instructions here](https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc).
@@ -100,7 +100,6 @@ In order to use dual ZED-F9P GPS heading in PX4, follow these steps:
 3. Components should be visible on the left panel.
   Click on the first `_Component_<ID#>` that maps to the ZED-F9P DroneCAN node (below shown as _Component 124_).
 4. Click on the _GPS_ subsection and configure the parameters listed below:
-
   - `GPS_TYPE`: Either set to `17` for moving baseline _base_, or set to `18` to be the moving baseline _rover_.
     One F9P MUST be _rover_, and the other MUST be _base_.
   - `GPS_AUTO_CONFIG`: set to 1 for both the rover and base
@@ -39,12 +39,10 @@ Order this module from:
 - 10 Pin JST-SH Debug

 - Motor & Battery Connectors (with-connector version)
-
  - MR30 Connector Limit Per Motor: 30A Continuous, 40A Burst
  - Four MR30 Motor Connectors

 - Dimensions (with connectors)
-
  - Size: 77.00mm x 42.00mm x 9.43mm
  - Mounting Pattern: 30.5mm
  - Weight: 24g
@@ -26,7 +26,6 @@ AIRLink has two computers and integrated LTE Module:
 ## 产品规格

 - **Sensors**
-
  - 3x Accelerometers, 3x Gyroscopes, 3x Magnetometers, 3x Pressure sensorss
  - GNSS, Rangefinders, Lidars, Optical Flow, Cameras
  - 3x-redundant IMU
@@ -34,7 +33,6 @@ AIRLink has two computers and integrated LTE Module:
  - Temperature stabilization

 - **Flight Controller**
-
  - STM32F7, ARM Cortex M7 with FPU, 216 MHz, 2MB Flash, 512 kB RAM
  - STM32F1, I/O co-processor
  - Ethernet, 10/100 Mbps
@@ -51,7 +49,6 @@ AIRLink has two computers and integrated LTE Module:
  - Safety switch / LED option

 - **AI Mission Computer**
-
  - 6-Core CPU: Dual-Core Cortex-A72 + Quad-Core Cortex-A53
  - GPU Mali-T864, OpenGL ES1.1/2.0/3.0/3.1
  - VPU with 4K VP8/9, 4K 10bits H265/H264 60fps Decoding
@@ -65,7 +62,6 @@ AIRLink has two computers and integrated LTE Module:
  - 2x Video: 4-Lane MIPI CSI (FPV Camera) and 4-Lane MIPI CSI with HMDI Input (Payload Camera)

 - **LTE/5G Connectivity Module**
-
  - Up to 600 Mbps bandwidth
  - 5G sub-6 and mmWave, SA and NSA operations
  - 4G Cat 20, up to 7xCA, 256-QAM DL/UL, 2xCA UL
@@ -142,7 +138,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
 ![Left side](../../assets/flight_controller/airlink/airlink-interfaces-left.jpg)

 - **Left side interfaces:**
-
  - Power input with voltage & current monitoring
  - AI Mission Computer micro SD card
  - Flight Controller micro SD card
@@ -170,13 +165,13 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production

 - **RC Connector - JST GH SM06B-GHS-TB**

-  | Pin number | Pin name                      | 方向  | Voltage               | 功能          |   |     |        |
-  | ---------- | ----------------------------- | --- | --------------------- | ----------- | - | --- | ------ |
-  | 1          | 5V                            | OUT | +5V                   | 5V output   |   |     |        |
-  | 2          | PPM_IN   | IN  | +3.3V | PPM 输入      |   |     |        |
-  | 3          | RSSI_IN  | IN  | +3.3V | RSSI 输入     |   |     |        |
-  | 4          | FAN_OUT  | OUT | +5V                   | Fan output  |   |     |        |
-  | 5          | SBUS_OUT | OUT | +3.3V | SBUS output | 6 | GND | Ground |
+  \| Pin number | Pin name | Direction | Voltage | Function    |
+  \| ---------- | -------- | --------- | ------- | ----------- | --- | --- | ------ |
+  \| 1          | 5V       | OUT       | +5V     | 5V output   |
+  \| 2          | PPM_IN   | IN        | +3.3V   | PPM input   |
+  \| 3          | RSSI_IN  | IN        | +3.3V   | RSSI input  |
+  \| 4          | FAN_OUT  | OUT       | +5V     | Fan output  |
+  \| 5          | SBUS_OUT | OUT       | +3.3V   | SBUS output | 6   | GND | Ground |

 * **FMU SD card - microSD**

@@ -185,7 +180,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
 ![Right side](../../assets/flight_controller/airlink/airlink-interfaces-right.jpg)

 - **Right side interfaces:**
-
  - Ethernet port with power output
  - Telemetry port
  - Second GPS port
@@ -251,7 +245,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
 ![Front side](../../assets/flight_controller/airlink/airlink-interfaces-front.jpg)

 - **Front side interfaces:**
-
  - Main GNSS and compass port
  - Main telemetry port
  - CSI camera input
@@ -309,7 +302,6 @@ SmartAP AIRLink's Core edition is intended for medium to high volume production
 ![Back side](../../assets/flight_controller/airlink/airlink-interfaces-back.jpg)

 - **Rear side interfaces:**
-
  - SBUS input
  - 16 PWM output channels
  - 2x LTE antenna sockets (MIMO)
@@ -25,6 +25,7 @@ The boards in this category are:
 - [CubePilot Cube Orange+](../flight_controller/cubepilot_cube_orangeplus.md)
 - [CubePilot Cube Orange](../flight_controller/cubepilot_cube_orange.md)
 - [CubePilot Cube Yellow](../flight_controller/cubepilot_cube_yellow.md)
+- [Gear Up AirBrainH743](../flight_controller/gearup_airbrainh743.md)
 - [Holybro Kakute H7v2](../flight_controller/kakuteh7v2.md)
 - [Holybro Kakute H7mini](../flight_controller/kakuteh7mini.md)
 - [Holybro Kakute H7](../flight_controller/kakuteh7.md)
@@ -0,0 +1,96 @@
+# Gear Up AirBrainH743
+
+:::warning
+PX4 does not manufacture this (or any) autopilot.
+Contact the [manufacturer](https://takeyourgear.com/) for hardware support.
+:::
+
+:::info
+This flight controller is [manufacturer supported](../flight_controller/autopilot_manufacturer_supported.md).
+:::
+
+Purchase from [takeyourgear.com](https://takeyourgear.com/pages/products/airbrain).
+
+For more information and pinout, check the [GitHub documentation](https://github.com/GearUp-Company/AirBrainH743).
+
+## 主要特性
+
+- MCU: STM32H743 32-bit processor running at 480 MHz
+- IMU: ICM42688P
+- Barometer: DPS310
+- Magnetometer: LIS2MDL (internal)
+- 128MB NAND Flash for logging (W25N)
+- 7x UARTs
+- I2C, SPI
+- 9x PWM Outputs (8 Motor outputs, 1 LED strip)
+- Battery input voltage: 3S-10S
+- Battery voltage/current monitoring
+- 5V@2A and 10V@2.5A BEC outputs
+- USB Type-C (IP68)
+- EMC and ESD protection
+
+## Connectors and Pins
+
+:::warning
+The pin order is different from the Pixhawk standard (compatible to the Betaflight standard).
+:::
+
+### UARTs
+
+Current UART configuration:
+
+| UART   | 设备         | 功能                                      |
+| ------ | ---------- | --------------------------------------- |
+| USART1 | /dev/ttyS0 | Console/Debug                           |
+| USART2 | /dev/ttyS1 | RC Input                                |
+| USART3 | /dev/ttyS2 | TEL4 (DJI/MSP)       |
+| UART4  | /dev/ttyS3 | TEL1                                    |
+| UART5  | /dev/ttyS4 | TEL2                                    |
+| UART7  | /dev/ttyS5 | TEL3 (ESC Telemetry) |
+| UART8  | /dev/ttyS6 | GPS1                                    |
+
+### Motor/Servo Outputs
+
+| Connector | 针脚 | 功能                           |
+| --------- | -- | ---------------------------- |
+| ESC       | M1 | Motor 1                      |
+| ESC       | M2 | Motor 2                      |
+| ESC       | M3 | Motor 3                      |
+| ESC       | M4 | Motor 4                      |
+| PWM       | M5 | Motor 5                      |
+| PWM       | M6 | Motor 6                      |
+| PWM       | M7 | Motor 7                      |
+| PWM       | M8 | Motor 8                      |
+| AUX       | M9 | LED/PWM/etc. |
+
+<a id="bootloader"></a>
+
+## PX4 Bootloader Update
+
+Before PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
+Download the [gearup_airbrainh743_bootloader.bin](https://github.com/PX4/PX4-Autopilot/blob/main/boards/gearup/airbrainh743/extras/gearup_airbrainh743_bootloader.bin) bootloader binary and read [this page](../advanced_config/bootloader_update_from_betaflight.md) for flashing instructions.
+
+## 编译固件
+
+To [build PX4](../dev_setup/building_px4.md) for this target:
+
+```
+make gearup_airbrainh743_default
+```
+
+## Installing PX4 Firmware
+
+Firmware can be installed in any of the normal ways:
+
+- Build and upload the source:
+
+  ```
+  make gearup_airbrainh743_default upload
+  ```
+
+- [Load the firmware](../config/firmware.md) using _QGroundControl_.
+  You can use either pre-built firmware or your own custom firmware.
+
+### 系统控制台
+
+UART1 (ttyS0) is configured for use as the [System Console](../debug/system_console.md).
@@ -231,7 +231,7 @@ Ackermann rovers do not support the yaw setpoint.

    - Position setpoint **and** velocity setpoint (the velocity setpoint is used as feedforward; it is added to the output of the position controller and the result is used as the input to the velocity controller).

-  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_GLOBAL](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL).
+  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_GLOBAL_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_INT), [MAV_FRAME_GLOBAL_RELATIVE_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_RELATIVE_ALT_INT), [MAV_FRAME_GLOBAL_TERRAIN_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_TERRAIN_ALT_INT).

 - [SET_ATTITUDE_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET)
  - 支持以下输入组合：
@@ -278,7 +278,7 @@ Ackermann rovers do not support the yaw setpoint.
        - 12288：悬停设定值（以设定值为中心绕圈飞行）。
        - 16384：空闲设定值（油门为0， 横滚 / 俯仰为0）。

-  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_GLOBAL](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL).
+  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_GLOBAL_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_INT), [MAV_FRAME_GLOBAL_RELATIVE_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_RELATIVE_ALT_INT), [MAV_FRAME_GLOBAL_TERRAIN_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_TERRAIN_ALT_INT).

 - [SET_ATTITUDE_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET)
  - 支持以下输入组合：
@@ -287,7 +287,29 @@ Ackermann rovers do not support the yaw setpoint.

 ### 无人车

-Rover does not support a MAVLink offboard API (ROS2 is supported).
+Rover supports offboard control using the generic MAVLink position/velocity setpoint messages listed below.
+These are converted into a [TrajectorySetpoint](../msg_docs/TrajectorySetpoint.md) internally, and then into rover setpoints by the rover offboard modes.
+For rover-specific control setpoints and better behaviour we recommend using the [Rover Setpoints](#rover-setpoints) via ROS 2.
+
+:::info
+Rover MAVLink setpoints are gated by the MAVLink parameter [MAV_FWDEXTSP](../advanced_config/parameter_reference.md#MAV_FWDEXTSP) (Forward external setpoint messages).
+:::
+
+- [SET_POSITION_TARGET_LOCAL_NED](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_LOCAL_NED)
+  - Position setpoint: `x`, `y` in [MAV_FRAME_LOCAL_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_NED) (`z` is ignored by rover modules).
+  - Velocity setpoint: `vx`, `vy` in [MAV_FRAME_LOCAL_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_LOCAL_NED) or [MAV_FRAME_BODY_NED](https://mavlink.io/en/messages/common.html#MAV_FRAME_BODY_NED).
+  - `yaw`/`yaw_rate`:
+    - Ackermann/Differential: ignored (in velocity control the yaw setpoint is derived from the velocity direction).
+    - Mecanum: can be controlled independently (decoupled) using `yaw`/`yaw_rate`.
+  - Acceleration setpoints (`afx`, `afy`, `afz`) are ignored by rover modules.
+
+- [SET_POSITION_TARGET_GLOBAL_INT](https://mavlink.io/en/messages/common.html#SET_POSITION_TARGET_GLOBAL_INT)
+  - Position setpoint: `lat_int`, `lon_int`, `alt` (converted into local NED internally; rover modules only use the horizontal components).
+  - Velocity setpoint: `vx`, `vy`, `vz` (rover modules use only the horizontal components).
+  - PX4 supports the following `coordinate_frame` values (only): [MAV_FRAME_GLOBAL_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_INT), [MAV_FRAME_GLOBAL_RELATIVE_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_RELATIVE_ALT_INT), [MAV_FRAME_GLOBAL_TERRAIN_ALT_INT](https://mavlink.io/en/messages/common.html#MAV_FRAME_GLOBAL_TERRAIN_ALT_INT).
+
+- [SET_ATTITUDE_TARGET](https://mavlink.io/en/messages/common.html#SET_ATTITUDE_TARGET)
+  - Not supported for rover offboard control.

 ## Offboard参数

@@ -28,7 +28,6 @@ Missions are uploaded onto a SD card that needs to be inserted **before** bootin
 At high level all vehicle types behave in the same way when MISSION mode is engaged:

 1. If no mission is stored, or if PX4 has finished executing all mission commands, or if the [mission is not feasible](#mission-feasibility-checks):
-
   - If flying the vehicle will loiter.
   - If landed the vehicle will "wait".

@@ -115,7 +115,6 @@ The altitude control mode determine whether the vehicle altitude is relative to
  The relative distance to the drone to the target will change as you ascend and descend (use with care in hilly terrain).

 - `2D + Terrain` makes the drone follow at a fixed height relative to the terrain underneath it, using information from a distance sensor.
-
  - If the vehicle does not have a distance sensor following will be identical to `2D tracking`.
  - Distance sensors aren't always accurate and vehicles may be "jumpy" when flying in this mode.
  - Note that that height is relative to the ground underneath the vehicle, not the follow target.
@@ -30,7 +30,6 @@ Missions are uploaded onto a SD card that needs to be inserted **before** bootin
 At high level all vehicle types behave in the same way when MISSION mode is engaged:

 1. If no mission is stored, or if PX4 has finished executing all mission commands, or if the [mission is not feasible](#mission-feasibility-checks):
-
   - If flying the vehicle will hold.
   - If landed the vehicle will "wait".

@@ -49,7 +49,6 @@ If returning as a fixed-wing, the vehicle:
  A mission landing pattern for a VTOL vehicle consists of a [MAV_CMD_DO_LAND_START](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_LAND_START), one or more position waypoints, and a [MAV_CMD_NAV_VTOL_LAND](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_VTOL_LAND).

 - If the destination is a rally point or home it will:
-
  - Loiter/spiral down to [RTL_DESCEND_ALT](#RTL_DESCEND_ALT).
  - Circle for a short time, as defined by [RTL_LAND_DELAY](#RTL_LAND_DELAY).
  - Yaw towards the destination (centre of loiter).
@@ -30,7 +30,7 @@ The diagrams use the standard [PX4 notation](../contribute/notation.md) (and eac

  ::: info
  The IMU pipeline is:
-  gyro data > apply calibration parameters > remove estimated bias > notch filter (`IMU_GYRO_NF0_BW` and `IMU_GYRO_NF0_FRQ`) > low-pass filter (`IMU_GYRO_CUTOFF`) > vehicle_angular_velocity (_filtered angular rate used by the P and I controllers_) > derivative -> low-pass filter (`IMU_DGYRO_CUTOFF`) > vehicle_angular_acceleration (_filtered angular acceleration used by the D controller_)
+  gyro data > apply calibration parameters > remove estimated bias > notch filter (`IMU_GYRO_NF0_BW` and `IMU_GYRO_NF0_FRQ`) > low-pass filter (`IMU_GYRO_CUTOFF`) > vehicle_angular_velocity (\_filtered angular rate used by the P and I controllers_) > derivative -> low-pass filter (`IMU_DGYRO_CUTOFF`) > vehicle_angular_acceleration (\_filtered angular acceleration used by the D controller_)

  ![IMU pipeline](../../assets/diagrams/px4_imu_pipeline.png)

@@ -177,7 +177,7 @@ The angular position of the control effectors (ailerons, elevators, rudders, ...
 此外，由于控制面在高速时更有效，而在低速时效率较低，因此根据巡航速度调整的控制器使用空速测量值进行缩放（如果使用这样的传感器）。

 :::info
-If no airspeed sensor is used then gain scheduling for the FW attitude controller is  disabled (it's open loop); no correction is/can be made in TECS using airspeed feedback.
+If no airspeed sensor is used then gain scheduling for the FW attitude controller is disabled (it's open loop); no correction is/can be made in TECS using airspeed feedback.
 :::

 前馈增益用于补偿空气动力阻尼。
@@ -187,7 +187,7 @@ If no airspeed sensor is used then gain scheduling for the FW attitude controlle
 ### Turn coordination

 滚转和俯仰控制器具有相同的结构，并且假设纵向和横向动力学足够解耦，可以独立工作。
-但是，为了将飞机侧滑产生的侧向加速度最小化，偏航控制器利用转向协调约束产生偏航速率设定值。  The turn coordination algorithm is based solely on coordinated turn geometry calculation.
+但是，为了将飞机侧滑产生的侧向加速度最小化，偏航控制器利用转向协调约束产生偏航速率设定值。 The turn coordination algorithm is based solely on coordinated turn geometry calculation.

 $$\dot{\Psi}_{sp} = \frac{g}{V_T} \tan{\phi_{sp}} \cos{\theta_{sp}}$$

@@ -33,7 +33,6 @@ To create a package delivery mission (with a Gripper):
 1. Create a normal mission with a `Takeoff` mission item, and additional waypoints for your required flight path.

 2. Add a waypoint on the map for where you'd like to release the package.
-
   - To drop the package while flying set an appropriate altitude for the waypoint (and ensure the waypoint is at a safe location to drop the package).

   - If you'd like to land the vehicle to make the delivery you will need to change the `Waypoint` to a `Land` mission item.
@@ -7,6 +7,12 @@ Support for rover is [experimental](../airframes/index.md#experimental-vehicles)
 Maintainer volunteers, [contribution](../contribute/index.md) of new features, new frame configurations, or other improvements would all be very welcome!
 :::

+:::tip
+Rover is not in the default PX4 firmware downloaded from QGC.
+Unlike for other vehicle types you will need to install it as custom firmware.
+For more information see [Flashing the Rover Build](../config_rover/index.md#flashing-the-rover-build).
+:::
+
 ![Rovers](../../assets/airframes/rover/rovers.png)

 PX4 provides support for the three most common types of rovers:
@@ -20,7 +20,7 @@ It is possible to have a GPS lock (Green LED) and still not be able to arm the v
 :::

 :::tip
-In the event of an error (blinking red), or if the vehicle can't achieve GPS lock (change from blue to green),   check for more detailed status information in _QGroundControl_ including calibration status, and errors messages reported by the [Preflight Checks (Internal)](../flying/pre_flight_checks.md).
+In the event of an error (blinking red), or if the vehicle can't achieve GPS lock (change from blue to green), check for more detailed status information in _QGroundControl_ including calibration status, and errors messages reported by the [Preflight Checks (Internal)](../flying/pre_flight_checks.md).
 还要检查GPS模块是否正确连接，Pixhawk是否正确读取GPS信息，GPS是否发送正确的GPS位置。
 :::

@@ -47,7 +47,8 @@ In the event of an error (blinking red), or if the vehicle can't achieve GPS loc
  在故障保护模式时，飞行器将试图返回起飞位置，或者降落在当前位置。

 - **[Solid Amber] Low Battery Warning:** Indicates your vehicle's battery is running dangerously low.
-  在某一点之后，飞行器将进入故障保护模式。 但是，此模式警告此次飞行应该结束。
+  在某一点之后，飞行器将进入故障保护模式。 However, this mode should signal caution that it's time to end
+  this flight.

 - **[Blinking Red] Error / Setup Required:** Indicates that your autopilot needs to be configured or calibrated before flying.
  将飞行器连接到地面站以找出问题所在。
@@ -77,11 +78,11 @@ The LED labels shown above are commonly used, but might differ on some boards.

 下面给出了LED更详细的信息(“x”表示任意状态)

-| 红色/琥珀色 | 蓝色 | 绿色    | 含义                                                                                                                                                                                   |
-| ------ | -- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 10Hz   | x  | x     | Overload CPU load > 80%, or RAM usage > 98%                                                                                                                                          |
-| 关闭     | x  | x     | Overload CPU load <= 80%, or RAM usage <= 98%                                                                                      |
-| 不可用    | 关闭 | 4 赫兹  | actuator_armed->armed && failsafe                                                                                       |
-| 不可用    | 打开 | 4 赫兹  | actuator_armed->armed && !failsafe                                                                                      |
-| 不可用    | 关闭 | 1 赫兹  | !actuator_armed-> armed && actuator_armed->ready_to_arm  |
-| 不可用    | 关闭 | 10 赫兹 | !actuator_armed->armed  && !actuator_armed->ready_to_arm |
+| 红色/琥珀色 | 蓝色 | 绿色    | 含义                                                                                                                                                                                  |
+| ------ | -- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10Hz   | x  | x     | Overload CPU load > 80%, or RAM usage > 98%                                                                                                                                         |
+| 关闭     | x  | x     | Overload CPU load <= 80%, or RAM usage <= 98%                                                                                     |
+| 不可用    | 关闭 | 4 赫兹  | actuator_armed->armed && failsafe                                                                                      |
+| 不可用    | 打开 | 4 赫兹  | actuator_armed->armed && !failsafe                                                                                     |
+| 不可用    | 关闭 | 1 赫兹  | !actuator_armed-> armed && actuator_armed->ready_to_arm |
+| 不可用    | 关闭 | 10 赫兹 | !actuator_armed->armed && !actuator_armed->ready_to_arm |
@@ -13,7 +13,7 @@ You can search for tune use using the string `TUNE_ID_name`(e.g. \`TUNE_ID_PARAC

 These tunes are played during the boot sequence.

-<!-- https://github.com/PX4/PX4-Autopilot/blob/main/ROMFS/px4fmu_common/init.d/rcS --> 
+<!-- https://github.com/PX4/PX4-Autopilot/blob/main/ROMFS/px4fmu_common/init.d/rcS -->

 #### 启动声音

@@ -152,7 +152,6 @@ The RTK GPS connection is essentially plug and play:
   ![survey-in](../../assets/qgc/setup/rtk/qgc_rtk_survey-in.png)

 4. 测量完成：
-
   - The RTK GPS icon changes to white and _QGroundControl_ starts to stream position data to the vehicle:

     ![RTK streaming](../../assets/qgc/setup/rtk/qgc_rtk_streaming.png)
@@ -3,19 +3,11 @@ import { useData } from 'vitepress'
 const { site } = useData();
 </script>

-<div style="float:right; padding:10px; margin-right:20px;"><a href="https://px4.io/"><img src="../assets/site/logo_pro_small.png" title="PX4 Logo" width="180px" /></a></div>
-
 # PX4 自动驾驶仪用户指南

 [![Releases](https://img.shields.io/badge/release-main-blue.svg)](https://github.com/PX4/PX4-Autopilot/releases) [![Discuss](https://img.shields.io/badge/discuss-px4-ff69b4.svg)](https://discuss.px4.io//) [![Discord](https://discordapp.com/api/guilds/1022170275984457759/widget.png?style=shield)](https://discord.gg/dronecode)

-_PX4_ 是一款专业级飞控。
-它由来自业界和学术界的世界级开发商开发，并得到活跃的全球社区的支持，为从竞速和物流无人机到地面车辆和潜水艇的各种载具提供动力。
-
-:::tip
-这份指南包含组装、配置、安全使用 PX4 的设备的各种只是。
-对贡献感兴趣吗 查看 [Development](development/development.md) 部分。
-:::
+PX4 is an open-source autopilot for drones and autonomous vehicles. It runs on multirotors, fixed-wing, VTOL, helicopters, rovers, and more. This guide covers everything from assembly and configuration to flight operations and development.

 <div v-if="site.title == 'PX4 Guide (main)'">

@@ -29,83 +21,43 @@ _PX4_ 是一款专业级飞控。

 </div>

-## 如何开始？
+## For Developers

-所有用户都应该先阅读[基本概念](getting_started/px4_basic_concepts.md) ！
-它概述了PX4，包括由飞行堆栈提供的功能（飞行模式和安全特征）和支持的硬件（飞行控制器、载具类型、数传系统、遥控控制系统）。
+:::tip
+Building on PX4 or extending the platform? Start here: [Development Guide](development/development.md). Set up your [dev environment](dev_setup/config_initial.md), [build from source](dev_setup/building_px4.md), run [SITL simulation](simulation/index.md), or integrate via [ROS 2](ros2/index.md) and [MAVSDK](https://mavsdk.mavlink.io/).
+:::

-根据您想要实现的目标，以下提示将帮助您浏览本指南：
+## 入门指南

-### 我想要一个能与PX4配合使用的载具
+Start with [Basic Concepts](getting_started/px4_basic_concepts.md) for an overview of the flight stack, flight modes, safety features, and supported hardware.

-在 [多旋翼](frames_multicopter/index.md), [VTOL](frames_vtol/index.md), 和 [飞机(固定翼)](frames_plane/index.md)部分你会找到如下主题（这些链接针对多旋翼飞行器）：
+## Build a Vehicle

- [完整的载具](complete_vehicles_mc/index.md)列出了到手飞(RTF)的硬件
- [套件(frames_multicopter/kits.md) 列出了需要你利用一组预先选定的部件自行组装的无人机。
- [DIY 组装](frames_multicopter/diy_builds.md) 展示了一些使用单独采购的零部件组装而成的无人机示例。
+Pick your frame type: [Multicopter](frames_multicopter/index.md), [Fixed-Wing](frames_plane/index.md), [VTOL](frames_vtol/index.md), [Helicopter](frames_helicopter/index.md), or [Rover](frames_rover/index.md). Each section covers complete vehicles, kits, and DIY builds. For assembly instructions see [Assembling a Multicopter](assembly/assembly_mc.md) or the equivalent for your frame.

-无论是套件还是成品飞行器，通常都包含你所需的一切，除了电池和遥控系统。
-套装通常不难建造，可以很好地介绍无人机如何合在一起，而且费用相对较低。
-我们提供了一般的组装指示，例如[组装一个多旋翼机](assembly/assembly_mc.md)，大多数套装也附有具体的指示。
+## Configure and Tune

-如果套件和成品无人机不太符合你的需求，那么你可以从零开始打造一架飞行器，但这需要更多专业知识。
-[机身构建](airframes/index.md) 列出了受支持的机身起点，让你了解哪些方案是可行的。
+Once assembled, follow the configuration guide for your vehicle type (e.g. [Multicopter Configuration](config_mc/index.md)). This covers sensor calibration, flight mode setup, and tuning.

-一旦你拥有支持PX4的载具，你将需要配置它并校准传感器。
-每种飞行器类型都有其专属的配置章节，阐述主要步骤，比如[多旋翼飞行器配置 / 调校](config_mc/index.md))。
+## 硬件

-### 我想添加一个有效载荷/相机
+The [Hardware Selection & Setup](hardware/drone_parts.md) section covers flight controllers, sensors, telemetry, RC systems, and payloads. See [Payloads](payloads/index.md) for camera and delivery integrations.

-[有效载荷](payloads/index.md)部分描述了如何添加相机，以及如何配置 PX4 以实现交付包裹。
+## Fly

-### 我正在修改一个支持的载具
+Read [Operations](config/operations.md) to understand safety features and failsafe behavior before your first flight. Then see [Basic Flying (Multicopter)](flying/basic_flying_mc.md) or the equivalent for your frame type.

-[硬件选择和设置](hardware/drone_parts.md)部分提供了关于您可能使用 PX4 的硬件及其配置的高层次和特定产品信息。
-如果你想改装无人机并添加新组件，这里是你首先应该查看的地方。
+## 技术支持

-### 我想飞行
-
-在飞行之前，您应该阅读 [Operations](config/operations.md)来了解如何设置您的载具的安全性能和所有机型的常见特性。
-完成后，你可以准备飞行。
-
-每种飞行器类型的基本飞行说明在各自对应部分给出，例如[基本飞行（多旋翼飞行器）](flying/basic_flying_mc.md)。
-
-### 我想在一个新的飞行控制器上运行 PX4并扩展平台
-
-[开发](development/development.md)部分解释了如何支持新的机体和车辆类型，修改飞行算法添加新模式，整合新的硬件，与飞行控制器外的 PX4 进行沟通，并为PX4 作出贡献。
-
-## 获取帮助
-
-[支持](contribute/support.md)页解释了如何从核心开发团队和更广泛的社区获得帮助。
-
-除此以外，它还包括了：
-
- [您可以获得帮助的论坛](contribute/support.md#forums-and-chat)
- [诊断问题](contribute/support.md#diagnosing-problems)
- [如何报告bug](contribute/support.md#issue-bug-reporting)
- [每周开发会议](contribute/support.md#weekly-dev-call)
-
-## 报告错误和问题
-
-如果您在使用 PX4 首次发布时遇到任何问题，请在[支持论坛](contribute/support.md#forums-and-chat) 上(因为它们可能是由载具配置引起)。
-
-如果开发团队指示，代码问题可以在 [Github](https://github.com/PX4/PX4-Autopilot/issues) 上提出。
-尽可能提供 [飞行日志](getting_started/flight_reporting.md) 和问题模板中要求的其他信息。
+Get help on the [discussion forums](https://discuss.px4.io/) or [Discord](https://discord.gg/dronecode). See the [Support](contribute/support.md) page for diagnosing problems, reporting bugs, and joining the [weekly dev call](contribute/dev_call.md).

 ## 参与贡献

-如何贡献代码和文档的信息可以在 [贡献](contribute/index.md部分中找到：
-
- [代码](contribute/index.md)
- [Documentation](contribute/docs.md)
- [Translation](contribute/translation.md)
+See the [Contributing](contribute/index.md) section for code, [documentation](contribute/docs.md), and [translation](contribute/translation.md) guidelines.

 ## 翻译

-本指南有多种 [译文](contribute/translation.md)。
-您可以从语言菜单中访问到它们 （右上角）：
-
-![语言选择器](../assets/vuepress/language_selector.png)
+本指南有多种 [译文](contribute/translation.md)。 Use the language selector in the top navigation.

 <!--@include: _contributors.md-->

@@ -141,9 +93,9 @@ _Dronecode 日历_ 展示了面向平台用户和开发者的重要社区活动

 ## 治理

-PX4 飞行控制架构由[Dronecode Project](https://dronecode.org/)负责管理。
+The PX4 Autopilot project is hosted by the [Dronecode Foundation](https://www.dronecode.org/), a [Linux Foundation](https://www.linuxfoundation.org/) Collaborative Project. Dronecode holds all PX4 trademarks and serves as the project's legal guardian, ensuring vendor-neutral stewardship. No single company owns the name or controls the roadmap. The source code is licensed under the [BSD 3-Clause](https://opensource.org/license/BSD-3-Clause) license, so you are free to use, modify, and distribute it in your own projects.

-<a href="https://dronecode.org/" style="padding:20px" ><img src="../assets/site/logo_dronecode.png" alt="Dronecode Logo" width="110px"/></a> <a href="https://www.linuxfoundation.org/projects" style="padding:20px;"><img src="../assets/site/logo_linux_foundation.png" alt="Linux Foundation Logo" width="80px" /></a>
+<a href="https://www.dronecode.org/" style="padding:20px"><img src="../assets/site/dronecode_logo.svg" alt="Dronecode Logo" width="140px"/></a> <a href="https://www.linuxfoundation.org/projects" style="padding:20px;"><img src="../assets/site/logo_linux_foundation.png" alt="Linux Foundation Logo" width="80px" /></a>

 <div style="padding:10px">&nbsp;</div>

@@ -95,192 +95,200 @@ They are not build into the module, and hence are neither published or subscribe
 :::details
 See messages

- [BatteryInfo](../msg_docs/BatteryInfo.md)
- [TakeoffStatus](../msg_docs/TakeoffStatus.md)
- [SensorGnssStatus](../msg_docs/SensorGnssStatus.md)
- [Airspeed](../msg_docs/Airspeed.md)
- [PpsCapture](../msg_docs/PpsCapture.md)
- [ActuatorControlsStatus](../msg_docs/ActuatorControlsStatus.md)
- [CameraCapture](../msg_docs/CameraCapture.md)
- [Px4ioStatus](../msg_docs/Px4ioStatus.md)
- [FuelTankStatus](../msg_docs/FuelTankStatus.md)
- [VehicleAngularVelocity](../msg_docs/VehicleAngularVelocity.md)
- [VehicleOpticalFlow](../msg_docs/VehicleOpticalFlow.md)
- [AirspeedWind](../msg_docs/AirspeedWind.md)
- [OrbTest](../msg_docs/OrbTest.md)
- [GimbalDeviceInformation](../msg_docs/GimbalDeviceInformation.md)
- [GpioOut](../msg_docs/GpioOut.md)
- [PurePursuitStatus](../msg_docs/PurePursuitStatus.md)
- [Gripper](../msg_docs/Gripper.md)
- [VehicleAirData](../msg_docs/VehicleAirData.md)
- [TuneControl](../msg_docs/TuneControl.md)
- [DebugVect](../msg_docs/DebugVect.md)
- [HoverThrustEstimate](../msg_docs/HoverThrustEstimate.md)
- [HomePositionV0](../msg_docs/HomePositionV0.md)
- [SensorsStatusImu](../msg_docs/SensorsStatusImu.md)
- [EstimatorAidSource3d](../msg_docs/EstimatorAidSource3d.md)
- [EstimatorBias](../msg_docs/EstimatorBias.md)
- [GpioConfig](../msg_docs/GpioConfig.md)
- [SystemPower](../msg_docs/SystemPower.md)
- [RateCtrlStatus](../msg_docs/RateCtrlStatus.md)
- [MissionResult](../msg_docs/MissionResult.md)
- [PowerButtonState](../msg_docs/PowerButtonState.md)
- [EscStatus](../msg_docs/EscStatus.md)
- [HealthReport](../msg_docs/HealthReport.md)
- [VehicleMagnetometer](../msg_docs/VehicleMagnetometer.md)
- [SensorGyro](../msg_docs/SensorGyro.md)
- [GpioRequest](../msg_docs/GpioRequest.md)
- [DebugKeyValue](../msg_docs/DebugKeyValue.md)
- [DistanceSensorModeChangeRequest](../msg_docs/DistanceSensorModeChangeRequest.md)
- [ParameterUpdate](../msg_docs/ParameterUpdate.md)
- [SensorAirflow](../msg_docs/SensorAirflow.md)
- [UavcanParameterValue](../msg_docs/UavcanParameterValue.md)
- [EstimatorSensorBias](../msg_docs/EstimatorSensorBias.md)
- [CanInterfaceStatus](../msg_docs/CanInterfaceStatus.md)
- [GimbalDeviceSetAttitude](../msg_docs/GimbalDeviceSetAttitude.md)
- [ActionRequest](../msg_docs/ActionRequest.md)
- [LandingTargetInnovations](../msg_docs/LandingTargetInnovations.md)
- [PwmInput](../msg_docs/PwmInput.md)
- [PowerMonitor](../msg_docs/PowerMonitor.md)
- [Mission](../msg_docs/Mission.md)
- [ArmingCheckReplyV0](../msg_docs/ArmingCheckReplyV0.md)
- [FigureEightStatus](../msg_docs/FigureEightStatus.md)
- [RadioStatus](../msg_docs/RadioStatus.md)
- [VehicleRoi](../msg_docs/VehicleRoi.md)
- [RtlTimeEstimate](../msg_docs/RtlTimeEstimate.md)
- [GimbalManagerStatus](../msg_docs/GimbalManagerStatus.md)
- [EstimatorSelectorStatus](../msg_docs/EstimatorSelectorStatus.md)
- [Rpm](../msg_docs/Rpm.md)
- [VehicleAngularAccelerationSetpoint](../msg_docs/VehicleAngularAccelerationSetpoint.md)
- [Ping](../msg_docs/Ping.md)
- [QshellReq](../msg_docs/QshellReq.md)
- [SensorMag](../msg_docs/SensorMag.md)
- [EstimatorStates](../msg_docs/EstimatorStates.md)
- [SensorUwb](../msg_docs/SensorUwb.md)
- [OpenDroneIdArmStatus](../msg_docs/OpenDroneIdArmStatus.md)
- [TiltrotorExtraControls](../msg_docs/TiltrotorExtraControls.md)
- [ControlAllocatorStatus](../msg_docs/ControlAllocatorStatus.md)
- [ParameterResetRequest](../msg_docs/ParameterResetRequest.md)
- [SensorHygrometer](../msg_docs/SensorHygrometer.md)
- [VehicleLocalPositionSetpoint](../msg_docs/VehicleLocalPositionSetpoint.md)
- [AdcReport](../msg_docs/AdcReport.md)
- [DronecanNodeStatus](../msg_docs/DronecanNodeStatus.md)
- [EstimatorAidSource2d](../msg_docs/EstimatorAidSource2d.md)
- [SensorAccelFifo](../msg_docs/SensorAccelFifo.md)
- [RoverAttitudeStatus](../msg_docs/RoverAttitudeStatus.md)
- [SensorCorrection](../msg_docs/SensorCorrection.md)
- [UlogStream](../msg_docs/UlogStream.md)
- [PositionControllerLandingStatus](../msg_docs/PositionControllerLandingStatus.md)
- [GpsInjectData](../msg_docs/GpsInjectData.md)
- [MagnetometerBiasEstimate](../msg_docs/MagnetometerBiasEstimate.md)
- [LoggerStatus](../msg_docs/LoggerStatus.md)
- [ParameterSetValueRequest](../msg_docs/ParameterSetValueRequest.md)
- [SensorBaro](../msg_docs/SensorBaro.md)
- [OrbTestMedium](../msg_docs/OrbTestMedium.md)
- [RoverSpeedStatus](../msg_docs/RoverSpeedStatus.md)
- [FollowTargetStatus](../msg_docs/FollowTargetStatus.md)
- [ParameterSetUsedRequest](../msg_docs/ParameterSetUsedRequest.md)
- [PositionControllerStatus](../msg_docs/PositionControllerStatus.md)
- [UlogStreamAck](../msg_docs/UlogStreamAck.md)
- [DatamanRequest](../msg_docs/DatamanRequest.md)
- [InternalCombustionEngineControl](../msg_docs/InternalCombustionEngineControl.md)
- [PositionSetpoint](../msg_docs/PositionSetpoint.md)
- [DatamanResponse](../msg_docs/DatamanResponse.md)
- [LedControl](../msg_docs/LedControl.md)
- [MavlinkTunnel](../msg_docs/MavlinkTunnel.md)
- [VehicleLocalPositionV0](../msg_docs/VehicleLocalPositionV0.md)
- [Event](../msg_docs/Event.md)
- [ActuatorArmed](../msg_docs/ActuatorArmed.md)
 - [GpioIn](../msg_docs/GpioIn.md)
- [SensorGyroFft](../msg_docs/SensorGyroFft.md)
- [SensorAccel](../msg_docs/SensorAccel.md)
- [SensorsStatus](../msg_docs/SensorsStatus.md)
- [VehicleAttitudeSetpointV0](../msg_docs/VehicleAttitudeSetpointV0.md)
- [GeneratorStatus](../msg_docs/GeneratorStatus.md)
- [DifferentialPressure](../msg_docs/DifferentialPressure.md)
- [FixedWingRunwayControl](../msg_docs/FixedWingRunwayControl.md)
- [NormalizedUnsignedSetpoint](../msg_docs/NormalizedUnsignedSetpoint.md)
- [TrajectorySetpoint6dof](../msg_docs/TrajectorySetpoint6dof.md)
- [LaunchDetectionStatus](../msg_docs/LaunchDetectionStatus.md)
- [RoverRateStatus](../msg_docs/RoverRateStatus.md)
- [AirspeedValidatedV0](../msg_docs/AirspeedValidatedV0.md)
- [GimbalManagerSetAttitude](../msg_docs/GimbalManagerSetAttitude.md)
- [VelocityLimits](../msg_docs/VelocityLimits.md)
- [MagWorkerData](../msg_docs/MagWorkerData.md)
- [Cpuload](../msg_docs/Cpuload.md)
- [InternalCombustionEngineStatus](../msg_docs/InternalCombustionEngineStatus.md)
- [SensorGnssRelative](../msg_docs/SensorGnssRelative.md)
- [MavlinkLog](../msg_docs/MavlinkLog.md)
- [SensorTemp](../msg_docs/SensorTemp.md)
- [LandingGearWheel](../msg_docs/LandingGearWheel.md)
- [OrbTestLarge](../msg_docs/OrbTestLarge.md)
- [FollowTargetEstimator](../msg_docs/FollowTargetEstimator.md)
- [CellularStatus](../msg_docs/CellularStatus.md)
- [QshellRetval](../msg_docs/QshellRetval.md)
- [OrbitStatus](../msg_docs/OrbitStatus.md)
- [VehicleStatusV0](../msg_docs/VehicleStatusV0.md)
- [FailureDetectorStatus](../msg_docs/FailureDetectorStatus.md)
- [LogMessage](../msg_docs/LogMessage.md)
- [SatelliteInfo](../msg_docs/SatelliteInfo.md)
- [SensorPreflightMag](../msg_docs/SensorPreflightMag.md)
- [NavigatorMissionItem](../msg_docs/NavigatorMissionItem.md)
- [FixedWingLateralGuidanceStatus](../msg_docs/FixedWingLateralGuidanceStatus.md)
- [BatteryStatusV0](../msg_docs/BatteryStatusV0.md)
- [EstimatorInnovations](../msg_docs/EstimatorInnovations.md)
- [EstimatorStatus](../msg_docs/EstimatorStatus.md)
- [NeuralControl](../msg_docs/NeuralControl.md)
- [TaskStackInfo](../msg_docs/TaskStackInfo.md)
- [RcParameterMap](../msg_docs/RcParameterMap.md)
- [SensorSelection](../msg_docs/SensorSelection.md)
- [FlightPhaseEstimation](../msg_docs/FlightPhaseEstimation.md)
- [ParameterSetValueResponse](../msg_docs/ParameterSetValueResponse.md)
- [ActuatorTest](../msg_docs/ActuatorTest.md)
- [VehicleImuStatus](../msg_docs/VehicleImuStatus.md)
- [MountOrientation](../msg_docs/MountOrientation.md)
- [CameraStatus](../msg_docs/CameraStatus.md)
- [AutotuneAttitudeControlStatus](../msg_docs/AutotuneAttitudeControlStatus.md)
- [FollowTarget](../msg_docs/FollowTarget.md)
- [EstimatorGpsStatus](../msg_docs/EstimatorGpsStatus.md)
- [ButtonEvent](../msg_docs/ButtonEvent.md)
- [DebugArray](../msg_docs/DebugArray.md)
- [Ekf2Timestamps](../msg_docs/Ekf2Timestamps.md)
- [GimbalManagerSetManualControl](../msg_docs/GimbalManagerSetManualControl.md)
- [IridiumsbdStatus](../msg_docs/IridiumsbdStatus.md)
- [OpenDroneIdSystem](../msg_docs/OpenDroneIdSystem.md)
- [VehicleImu](../msg_docs/VehicleImu.md)
- [GpsDump](../msg_docs/GpsDump.md)
- [WheelEncoders](../msg_docs/WheelEncoders.md)
- [EstimatorEventFlags](../msg_docs/EstimatorEventFlags.md)
- [DebugValue](../msg_docs/DebugValue.md)
+- [SystemPower](../msg_docs/SystemPower.md)
+- [LandingTargetInnovations](../msg_docs/LandingTargetInnovations.md)
+- [VehicleOpticalFlow](../msg_docs/VehicleOpticalFlow.md)
 - [LandingTargetPose](../msg_docs/LandingTargetPose.md)
- [OpenDroneIdOperatorId](../msg_docs/OpenDroneIdOperatorId.md)
- [VehicleOpticalFlowVel](../msg_docs/VehicleOpticalFlowVel.md)
- [RtlStatus](../msg_docs/RtlStatus.md)
- [VehicleAcceleration](../msg_docs/VehicleAcceleration.md)
- [GimbalControls](../msg_docs/GimbalControls.md)
- [ActuatorServosTrim](../msg_docs/ActuatorServosTrim.md)
- [FixedWingLateralStatus](../msg_docs/FixedWingLateralStatus.md)
- [HeaterStatus](../msg_docs/HeaterStatus.md)
- [YawEstimatorStatus](../msg_docs/YawEstimatorStatus.md)
- [RcChannels](../msg_docs/RcChannels.md)
- [TecsStatus](../msg_docs/TecsStatus.md)
- [EstimatorAidSource1d](../msg_docs/EstimatorAidSource1d.md)
- [InputRc](../msg_docs/InputRc.md)
- [SensorGyroFifo](../msg_docs/SensorGyroFifo.md)
- [GeofenceResult](../msg_docs/GeofenceResult.md)
- [OpenDroneIdSelfId](../msg_docs/OpenDroneIdSelfId.md)
- [UavcanParameterRequest](../msg_docs/UavcanParameterRequest.md)
- [ManualControlSwitches](../msg_docs/ManualControlSwitches.md)
- [NavigatorStatus](../msg_docs/NavigatorStatus.md)
- [CameraTrigger](../msg_docs/CameraTrigger.md)
- [EscReport](../msg_docs/EscReport.md)
- [EstimatorBias3d](../msg_docs/EstimatorBias3d.md)
- [GeofenceStatus](../msg_docs/GeofenceStatus.md)
- [GimbalManagerInformation](../msg_docs/GimbalManagerInformation.md)
- [ActuatorOutputs](../msg_docs/ActuatorOutputs.md)
- [EventV0](../msg_docs/EventV0.md)
- [ArmingCheckRequestV0](../msg_docs/ArmingCheckRequestV0.md)
+- [EstimatorGpsStatus](../msg_docs/EstimatorGpsStatus.md)
+- [EstimatorBias](../msg_docs/EstimatorBias.md)
+- [ParameterSetValueResponse](../msg_docs/ParameterSetValueResponse.md)
+- [LogMessage](../msg_docs/LogMessage.md)
+- [PowerMonitor](../msg_docs/PowerMonitor.md)
 - [VehicleConstraints](../msg_docs/VehicleConstraints.md)
+- [SensorAirflow](../msg_docs/SensorAirflow.md)
+- [ArmingCheckRequestV0](../msg_docs/ArmingCheckRequestV0.md)
+- [ActuatorArmed](../msg_docs/ActuatorArmed.md)
+- [HoverThrustEstimate](../msg_docs/HoverThrustEstimate.md)
+- [LaunchDetectionStatus](../msg_docs/LaunchDetectionStatus.md)
+- [DifferentialPressure](../msg_docs/DifferentialPressure.md)
+- [MagnetometerBiasEstimate](../msg_docs/MagnetometerBiasEstimate.md)
+- [PwmInput](../msg_docs/PwmInput.md)
+- [OrbTestMedium](../msg_docs/OrbTestMedium.md)
+- [QshellReq](../msg_docs/QshellReq.md)
+- [GeofenceStatus](../msg_docs/GeofenceStatus.md)
+- [RcChannels](../msg_docs/RcChannels.md)
+- [Cpuload](../msg_docs/Cpuload.md)
+- [DebugArray](../msg_docs/DebugArray.md)
+- [FlightPhaseEstimation](../msg_docs/FlightPhaseEstimation.md)
+- [Mission](../msg_docs/Mission.md)
+- [Airspeed](../msg_docs/Airspeed.md)
+- [LedControl](../msg_docs/LedControl.md)
+- [HealthReport](../msg_docs/HealthReport.md)
+- [FixedWingLateralGuidanceStatus](../msg_docs/FixedWingLateralGuidanceStatus.md)
+- [FigureEightStatus](../msg_docs/FigureEightStatus.md)
+- [EstimatorInnovations](../msg_docs/EstimatorInnovations.md)
+- [VehicleImuStatus](../msg_docs/VehicleImuStatus.md)
+- [VehicleLocalPositionSetpoint](../msg_docs/VehicleLocalPositionSetpoint.md)
+- [InputRc](../msg_docs/InputRc.md)
+- [UavcanParameterRequest](../msg_docs/UavcanParameterRequest.md)
+- [FixedWingRunwayControl](../msg_docs/FixedWingRunwayControl.md)
+- [SensorCorrection](../msg_docs/SensorCorrection.md)
+- [ControlAllocatorStatus](../msg_docs/ControlAllocatorStatus.md)
+- [AirspeedValidatedV0](../msg_docs/AirspeedValidatedV0.md)
+- [CanInterfaceStatus](../msg_docs/CanInterfaceStatus.md)
+- [SensorSelection](../msg_docs/SensorSelection.md)
+- [DeviceInformation](../msg_docs/DeviceInformation.md)
+- [CameraTrigger](../msg_docs/CameraTrigger.md)
+- [SensorAccel](../msg_docs/SensorAccel.md)
+- [ActuatorServosTrim](../msg_docs/ActuatorServosTrim.md)
+- [SensorsStatusImu](../msg_docs/SensorsStatusImu.md)
+- [EstimatorBias3d](../msg_docs/EstimatorBias3d.md)
+- [GimbalManagerStatus](../msg_docs/GimbalManagerStatus.md)
+- [BatteryStatusV0](../msg_docs/BatteryStatusV0.md)
+- [OpenDroneIdSelfId](../msg_docs/OpenDroneIdSelfId.md)
+- [VehicleImu](../msg_docs/VehicleImu.md)
+- [MissionResult](../msg_docs/MissionResult.md)
+- [SensorAccelFifo](../msg_docs/SensorAccelFifo.md)
+- [DistanceSensorModeChangeRequest](../msg_docs/DistanceSensorModeChangeRequest.md)
+- [SensorPreflightMag](../msg_docs/SensorPreflightMag.md)
+- [OrbTest](../msg_docs/OrbTest.md)
+- [PositionControllerLandingStatus](../msg_docs/PositionControllerLandingStatus.md)
+- [FuelTankStatus](../msg_docs/FuelTankStatus.md)
+- [OpenDroneIdSystem](../msg_docs/OpenDroneIdSystem.md)
+- [OrbitStatus](../msg_docs/OrbitStatus.md)
+- [Px4ioStatus](../msg_docs/Px4ioStatus.md)
+- [RtlStatus](../msg_docs/RtlStatus.md)
+- [ButtonEvent](../msg_docs/ButtonEvent.md)
+- [VehicleLocalPositionV0](../msg_docs/VehicleLocalPositionV0.md)
+- [DebugValue](../msg_docs/DebugValue.md)
+- [ParameterSetUsedRequest](../msg_docs/ParameterSetUsedRequest.md)
+- [RoverSpeedStatus](../msg_docs/RoverSpeedStatus.md)
+- [SensorHygrometer](../msg_docs/SensorHygrometer.md)
+- [OpenDroneIdOperatorId](../msg_docs/OpenDroneIdOperatorId.md)
+- [InternalCombustionEngineStatus](../msg_docs/InternalCombustionEngineStatus.md)
+- [GpioOut](../msg_docs/GpioOut.md)
+- [ActuatorTest](../msg_docs/ActuatorTest.md)
+- [SensorBaro](../msg_docs/SensorBaro.md)
+- [PositionControllerStatus](../msg_docs/PositionControllerStatus.md)
+- [PurePursuitStatus](../msg_docs/PurePursuitStatus.md)
+- [RoverRateStatus](../msg_docs/RoverRateStatus.md)
+- [TecsStatus](../msg_docs/TecsStatus.md)
+- [PpsCapture](../msg_docs/PpsCapture.md)
+- [RaptorStatus](../msg_docs/RaptorStatus.md)
+- [EventV0](../msg_docs/EventV0.md)
+- [GpioRequest](../msg_docs/GpioRequest.md)
+- [FollowTargetEstimator](../msg_docs/FollowTargetEstimator.md)
+- [MagWorkerData](../msg_docs/MagWorkerData.md)
+- [FollowTarget](../msg_docs/FollowTarget.md)
+- [EstimatorAidSource1d](../msg_docs/EstimatorAidSource1d.md)
+- [GimbalDeviceSetAttitude](../msg_docs/GimbalDeviceSetAttitude.md)
+- [SensorGnssRelative](../msg_docs/SensorGnssRelative.md)
+- [ActionRequest](../msg_docs/ActionRequest.md)
+- [NavigatorMissionItem](../msg_docs/NavigatorMissionItem.md)
+- [GpsInjectData](../msg_docs/GpsInjectData.md)
+- [VehicleStatusV0](../msg_docs/VehicleStatusV0.md)
+- [DronecanNodeStatus](../msg_docs/DronecanNodeStatus.md)
+- [UlogStream](../msg_docs/UlogStream.md)
+- [DebugKeyValue](../msg_docs/DebugKeyValue.md)
+- [NavigatorStatus](../msg_docs/NavigatorStatus.md)
+- [MountOrientation](../msg_docs/MountOrientation.md)
+- [RcParameterMap](../msg_docs/RcParameterMap.md)
+- [AdcReport](../msg_docs/AdcReport.md)
+- [EstimatorSensorBias](../msg_docs/EstimatorSensorBias.md)
+- [InternalCombustionEngineControl](../msg_docs/InternalCombustionEngineControl.md)
+- [MavlinkLog](../msg_docs/MavlinkLog.md)
+- [VehicleMagnetometer](../msg_docs/VehicleMagnetometer.md)
+- [GpioConfig](../msg_docs/GpioConfig.md)
+- [GainCompression](../msg_docs/GainCompression.md)
+- [DebugVect](../msg_docs/DebugVect.md)
+- [ArmingCheckReplyV0](../msg_docs/ArmingCheckReplyV0.md)
+- [VehicleAttitudeSetpointV0](../msg_docs/VehicleAttitudeSetpointV0.md)
+- [FollowTargetStatus](../msg_docs/FollowTargetStatus.md)
+- [RtlTimeEstimate](../msg_docs/RtlTimeEstimate.md)
+- [RoverAttitudeStatus](../msg_docs/RoverAttitudeStatus.md)
+- [SensorUwb](../msg_docs/SensorUwb.md)
+- [YawEstimatorStatus](../msg_docs/YawEstimatorStatus.md)
+- [VelocityLimits](../msg_docs/VelocityLimits.md)
+- [TrajectorySetpoint6dof](../msg_docs/TrajectorySetpoint6dof.md)
+- [OpenDroneIdArmStatus](../msg_docs/OpenDroneIdArmStatus.md)
+- [EscStatus](../msg_docs/EscStatus.md)
+- [GimbalManagerInformation](../msg_docs/GimbalManagerInformation.md)
+- [HeaterStatus](../msg_docs/HeaterStatus.md)
+- [EstimatorSelectorStatus](../msg_docs/EstimatorSelectorStatus.md)
+- [GeofenceResult](../msg_docs/GeofenceResult.md)
+- [PowerButtonState](../msg_docs/PowerButtonState.md)
+- [Rpm](../msg_docs/Rpm.md)
+- [WheelEncoders](../msg_docs/WheelEncoders.md)
+- [LoggerStatus](../msg_docs/LoggerStatus.md)
+- [CellularStatus](../msg_docs/CellularStatus.md)
+- [TuneControl](../msg_docs/TuneControl.md)
+- [ConfigOverridesV0](../msg_docs/ConfigOverridesV0.md)
+- [GimbalManagerSetAttitude](../msg_docs/GimbalManagerSetAttitude.md)
+- [OrbTestLarge](../msg_docs/OrbTestLarge.md)
+- [BatteryInfo](../msg_docs/BatteryInfo.md)
+- [CameraStatus](../msg_docs/CameraStatus.md)
+- [QshellRetval](../msg_docs/QshellRetval.md)
+- [SensorMag](../msg_docs/SensorMag.md)
+- [RateCtrlStatus](../msg_docs/RateCtrlStatus.md)
+- [TaskStackInfo](../msg_docs/TaskStackInfo.md)
+- [EstimatorAidSource2d](../msg_docs/EstimatorAidSource2d.md)
+- [AirspeedWind](../msg_docs/AirspeedWind.md)
+- [AutotuneAttitudeControlStatus](../msg_docs/AutotuneAttitudeControlStatus.md)
+- [GimbalDeviceInformation](../msg_docs/GimbalDeviceInformation.md)
+- [GpsDump](../msg_docs/GpsDump.md)
+- [SensorTemp](../msg_docs/SensorTemp.md)
+- [ParameterResetRequest](../msg_docs/ParameterResetRequest.md)
+- [TiltrotorExtraControls](../msg_docs/TiltrotorExtraControls.md)
+- [SensorsStatus](../msg_docs/SensorsStatus.md)
+- [EstimatorStatus](../msg_docs/EstimatorStatus.md)
+- [FailureDetectorStatus](../msg_docs/FailureDetectorStatus.md)
+- [VehicleAirData](../msg_docs/VehicleAirData.md)
+- [ActuatorControlsStatus](../msg_docs/ActuatorControlsStatus.md)
+- [TakeoffStatus](../msg_docs/TakeoffStatus.md)
+- [GeneratorStatus](../msg_docs/GeneratorStatus.md)
+- [SensorGyroFifo](../msg_docs/SensorGyroFifo.md)
+- [VehicleAngularVelocity](../msg_docs/VehicleAngularVelocity.md)
+- [LandingGearWheel](../msg_docs/LandingGearWheel.md)
+- [ParameterSetValueRequest](../msg_docs/ParameterSetValueRequest.md)
+- [RegisterExtComponentReplyV0](../msg_docs/RegisterExtComponentReplyV0.md)
+- [RaptorInput](../msg_docs/RaptorInput.md)
+- [SensorGyro](../msg_docs/SensorGyro.md)
+- [ParameterUpdate](../msg_docs/ParameterUpdate.md)
+- [NormalizedUnsignedSetpoint](../msg_docs/NormalizedUnsignedSetpoint.md)
+- [PositionSetpoint](../msg_docs/PositionSetpoint.md)
+- [EstimatorStates](../msg_docs/EstimatorStates.md)
+- [ActuatorOutputs](../msg_docs/ActuatorOutputs.md)
+- [ManualControlSwitches](../msg_docs/ManualControlSwitches.md)
+- [UavcanParameterValue](../msg_docs/UavcanParameterValue.md)
+- [VehicleAngularAccelerationSetpoint](../msg_docs/VehicleAngularAccelerationSetpoint.md)
+- [EstimatorEventFlags](../msg_docs/EstimatorEventFlags.md)
+- [SensorGnssStatus](../msg_docs/SensorGnssStatus.md)
+- [GimbalManagerSetManualControl](../msg_docs/GimbalManagerSetManualControl.md)
+- [HomePositionV0](../msg_docs/HomePositionV0.md)
+- [FixedWingLateralStatus](../msg_docs/FixedWingLateralStatus.md)
+- [SatelliteInfo](../msg_docs/SatelliteInfo.md)
 - [IrlockReport](../msg_docs/IrlockReport.md)
+- [Ping](../msg_docs/Ping.md)
+- [CameraCapture](../msg_docs/CameraCapture.md)
+- [Vtx](../msg_docs/Vtx.md)
+- [Ekf2Timestamps](../msg_docs/Ekf2Timestamps.md)
+- [RegisterExtComponentRequestV0](../msg_docs/RegisterExtComponentRequestV0.md)
+- [EscReport](../msg_docs/EscReport.md)
+- [Gripper](../msg_docs/Gripper.md)
+- [UlogStreamAck](../msg_docs/UlogStreamAck.md)
+- [SensorGyroFft](../msg_docs/SensorGyroFft.md)
+- [VehicleRoi](../msg_docs/VehicleRoi.md)
+- [VehicleAcceleration](../msg_docs/VehicleAcceleration.md)
+- [NeuralControl](../msg_docs/NeuralControl.md)
+- [DatamanResponse](../msg_docs/DatamanResponse.md)
+- [GimbalControls](../msg_docs/GimbalControls.md)
+- [MavlinkTunnel](../msg_docs/MavlinkTunnel.md)
+- [EstimatorAidSource3d](../msg_docs/EstimatorAidSource3d.md)
+- [DatamanRequest](../msg_docs/DatamanRequest.md)
+- [Event](../msg_docs/Event.md)
+- [RadioStatus](../msg_docs/RadioStatus.md)
+- [VehicleOpticalFlowVel](../msg_docs/VehicleOpticalFlowVel.md)
+- [IridiumsbdStatus](../msg_docs/IridiumsbdStatus.md)

 :::
@@ -35,8 +35,8 @@ PX4-Autopilot contains a template for writing a new application (module) that ru

   ```cpp
   WorkItemExample::WorkItemExample() :
-       ModuleParams(nullptr),
-       ScheduledWorkItem(MODULE_NAME, px4::wq_configurations::test1)
+      ModuleParams(nullptr),
+      ScheduledWorkItem(MODULE_NAME, px4::wq_configurations::test1)
   {
   }
   ```
@@ -45,6 +45,26 @@ atxxxx <command> [arguments...]
   status        print status info
 ```

+## auterion_autostarter
+
+Source: [drivers/auterion_autostarter](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/auterion_autostarter)
+
+### 描述
+
+Driver for starting and auto-detecting different power monitors.
+
+### Usage {#auterion_autostarter_usage}
+
+```
+auterion_autostarter <command> [arguments...]
+ Commands:
+   start
+
+   stop
+
+   status        print status info
+```
+
 ## batmon

 Source: [drivers/smart_battery/batmon](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/smart_battery/batmon)
@@ -925,26 +945,6 @@ pca9685_pwm_out <command> [arguments...]
   status        print status info
 ```

-## pm_selector_auterion
-
-Source: [drivers/power_monitor/pm_selector_auterion](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/power_monitor/pm_selector_auterion)
-
-### 描述
-
-Driver for starting and auto-detecting different power monitors.
-
-### Usage {#pm_selector_auterion_usage}
-
-```
-pm_selector_auterion <command> [arguments...]
- Commands:
-   start
-
-   stop
-
-   status        print status info
-```
-
 ## pmw3901

 Source: [drivers/optical_flow/pmw3901](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/optical_flow/pmw3901)
@@ -1109,7 +1109,7 @@ px4io <command> [arguments...]

 ## rgbled

-Source: [drivers/lights/rgbled_ncp5623c](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/lights/rgbled_ncp5623c)
+Source: [drivers/lights/rgbled](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/lights/rgbled)

 ### Usage {#rgbled_usage}

@@ -1124,9 +1124,7 @@ rgbled <command> [arguments...]
     [-f <val>]  bus frequency in kHz
     [-q]        quiet startup (no message if no device found)
     [-a <val>]  I2C address
-                 default: 57
-     [-o <val>]  RGB PWM Assignment
-                 default: 123
+                 default: 85

   stop

@@ -1438,6 +1436,30 @@ tap_esc <command> [arguments...]
                 default: 4
 ```

+## tmp102
+
+Source: [drivers/temperature_sensor/tmp102](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/temperature_sensor/tmp102)
+
+### Usage {#tmp102_usage}
+
+```
+tmp102 <command> [arguments...]
+ Commands:
+   start
+     [-I]        Internal I2C bus(es)
+     [-X]        External I2C bus(es)
+     [-b <val>]  board-specific bus (default=all) (external SPI: n-th bus
+                 (default=1))
+     [-f <val>]  bus frequency in kHz
+     [-q]        quiet startup (no message if no device found)
+     [-a <val>]  I2C address
+                 default: 72
+
+   stop
+
+   status        print status info
+```
+
 ## tone_alarm

 Source: [drivers/tone_alarm](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/tone_alarm)
@@ -1627,6 +1649,76 @@ voxlpm [arguments...]
   status        print status info
 ```

+## vtx
+
+Source: [drivers/vtx](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/vtx)
+
+### 描述
+
+This module communicates with a VTX camera via serial port. It can be used to
+configure the camera settings and to control the camera's video transmission.
+Supported protocols are:
+
+- SmartAudio v1, v2.0, v2.1
+- Tramp
+
+### Usage {#vtx_usage}
+
+```
+vtx <command> [arguments...]
+ Commands:
+   start
+     -d <val>    VTX device
+                 values: <file:dev>
+
+   <int>         Sets an entry in the mapping table: <index> <aux channel>
+                 <band> <channel> <power level> <start range> <end range>
+
+   stop
+
+   status        print status info
+```
+
+## vtxtable
+
+Source: [drivers/vtxtable](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/vtxtable)
+
+### 描述
+
+Manages the VTX frequency, power level and RC mapping table for VTX configuration.
+
+### Usage {#vtxtable_usage}
+
+```
+vtxtable <command> [arguments...]
+ Commands:
+   status        Shows the current VTX table configuration.
+
+   name          Sets the VTX table name: <string>
+
+   bands         Sets the number of bands: <int>
+
+   band          Sets the band frequencies: <1-index> <name> <letter>
+                 <attribute> <frequencies...>
+
+   channels      Sets the number of channels: <int>
+
+   powerlevels   Sets number of power levels: <int>
+
+   powervalues   Sets the power level values: <int...>
+
+   powerlabels   Sets the power level labels: <3 chars...>
+
+   <int>         Sets an entry in the mapping table: <0-index> <aux channel>
+                 <band> <channel> <power level> <start range> <end range>
+
+   clear         Clears the VTX table configuration.
+
+   save          Saves the VTX config to a file: <file>
+
+   load          Loads the VTX config from a file: <file>
+```
+
 ## zenoh

 Source: [modules/zenoh](https://github.com/PX4/PX4-Autopilot/tree/main/src/modules/zenoh)
@@ -1,5 +1,36 @@
 # 模块参考: 模板

+## mc_raptor
+
+Source: [modules/mc_raptor](https://github.com/PX4/PX4-Autopilot/tree/main/src/modules/mc_raptor)
+
+### 描述
+
+RAPTOR Policy Flight Mode
+
+### Usage {#mc_raptor_usage}
+
+```
+mc_raptor <command> [arguments...]
+ Commands:
+   start
+
+   intref        Modify internal reference
+     lissajous   Set Lissajous trajectory parameters
+     <A>         Amplitude X [m]
+     <B>         Amplitude Y [m]
+     <C>         Amplitude Z [m]
+     <fa>        Frequency a
+     <fb>        Frequency b
+     <fc>        Frequency c
+     <duration>  Total duration [s]
+     <ramp>      Ramp duration [s]
+
+   stop
+
+   status        print status info
+```
+
 ## 模块

 Source: [templates/template_module](https://github.com/PX4/PX4-Autopilot/tree/main/src/templates/template_module)
@@ -1,12 +1,57 @@
+---
+pageClass: is-wide-page
+---
+
 # ActionRequest (UORB message)

-Action request for the vehicle's main state
+Action request for the vehicle's main state.

 Message represents actions requested by a PX4 internal component towards the main state machine such as a request to arm or switch mode.
 It allows mapping triggers from various external interfaces like RC channels or MAVLink to cause an action.
 Request are published by `manual_control` and subscribed by the `commander` and `vtol_att_control` modules.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActionRequest.msg)
+**TOPICS:** action_request
+
+## Fields
+
+| 参数名       | 类型       | Unit [Frame] | Range/Enum        | 描述                                                                                                                                                                                                               |
+| --------- | -------- | ---------------------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| timestamp | `uint64` | us                                                               |                   | Time since system start                                                                                                                                                                                          |
+| action    | `uint8`  |                                                                  | [ACTION](#ACTION) | Requested action                                                                                                                                                                                                 |
+| source    | `uint8`  |                                                                  | [SOURCE](#SOURCE) | Request trigger type, such as a switch, button or gesture                                                                                                                                                        |
+| mode      | `uint8`  |                                                                  |                   | Requested mode. Only applies when `action` is `ACTION_SWITCH_MODE`. Values for this field are defined by the `vehicle_status_s::NAVIGATION_STATE_*` enumeration. |
+
+## Enums
+
+### ACTION {#ACTION}
+
+| 参数名                                                                                                                                                                             | 类型      | 值 | 描述                                                                                       |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | - | ---------------------------------------------------------------------------------------- |
+| <a href="#ACTION_DISARM"></a> ACTION_DISARM                                                                                                                | `uint8` | 0 | Disarm vehicle                                                                           |
+| <a href="#ACTION_ARM"></a> ACTION_ARM                                                                                                                      | `uint8` | 1 | Arm vehicle                                                                              |
+| <a href="#ACTION_TOGGLE_ARMING"></a> ACTION_TOGGLE_ARMING                                                                             | `uint8` | 2 | Toggle arming                                                                            |
+| <a href="#ACTION_UNKILL"></a> ACTION_UNKILL                                                                                                                | `uint8` | 3 | Revert a kill action                                                                     |
+| <a href="#ACTION_KILL"></a> ACTION_KILL                                                                                                                    | `uint8` | 4 | Kill vehicle (instantly stop the motors)                              |
+| <a href="#ACTION_SWITCH_MODE"></a> ACTION_SWITCH_MODE                                                                                 | `uint8` | 5 | Switch mode. The target mode is set in the `mode` field. |
+| <a href="#ACTION_VTOL_TRANSITION_TO_MULTICOPTER"></a> ACTION_VTOL_TRANSITION_TO_MULTICOPTER | `uint8` | 6 | Transition to hover flight                                                               |
+| <a href="#ACTION_VTOL_TRANSITION_TO_FIXEDWING"></a> ACTION_VTOL_TRANSITION_TO_FIXEDWING     | `uint8` | 7 | Transition to fast forward flight                                                        |
+| <a href="#ACTION_TERMINATION"></a> ACTION_TERMINATION                                                                                                      | `uint8` | 8 | Irreversibly output failsafe values on all outputs, trigger parachute                    |
+
+### SOURCE {#SOURCE}
+
+| 参数名                                                                                                                    | 类型      | 值 | 描述                                                              |
+| ---------------------------------------------------------------------------------------------------------------------- | ------- | - | --------------------------------------------------------------- |
+| <a href="#SOURCE_STICK_GESTURE"></a> SOURCE_STICK_GESTURE                    | `uint8` | 0 | Triggered by holding the sticks in a certain position           |
+| <a href="#SOURCE_RC_SWITCH"></a> SOURCE_RC_SWITCH                            | `uint8` | 1 | Triggered by an RC switch moving into a certain position        |
+| <a href="#SOURCE_RC_BUTTON"></a> SOURCE_RC_BUTTON                            | `uint8` | 2 | Triggered by a momentary button on the RC being pressed or held |
+| <a href="#SOURCE_RC_MODE_SLOT"></a> SOURCE_RC_MODE_SLOT | `uint8` | 3 | Mode change through the RC mode selection mechanism             |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActionRequest.msg)
+
+:::details
+Click here to see original file

 ```c
 # Action request for the vehicle's main state
@@ -35,5 +80,6 @@ uint8 SOURCE_RC_BUTTON = 2      # Triggered by a momentary button on the RC bein
 uint8 SOURCE_RC_MODE_SLOT = 3   # Mode change through the RC mode selection mechanism

 uint8 mode  # Requested mode. Only applies when `action` is `ACTION_SWITCH_MODE`. Values for this field are defined by the `vehicle_status_s::NAVIGATION_STATE_*` enumeration.
-
 ```
+
+:::
@@ -1,6 +1,30 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorArmed (UORB message)

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorArmed.msg)
+**TOPICS:** actuator_armed
+
+## Fields
+
+| 参数名                                                                                    | 类型       | Unit [Frame] | Range/Enum | 描述                                                                                                 |
+| -------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------- |
+| timestamp                                                                              | `uint64` |                                                                  |            | time since system start (microseconds)                                          |
+| armed                                                                                  | `bool`   |                                                                  |            | Set to true if system is armed                                                                     |
+| prearmed                                                                               | `bool`   |                                                                  |            | Set to true if the actuator safety is disabled but motors are not armed                            |
+| ready_to_arm                                 | `bool`   |                                                                  |            | Set to true if system is ready to be armed                                                         |
+| lockdown                                                                               | `bool`   |                                                                  |            | Set to true if actuators are forced to being disabled (due to emergency or HIL) |
+| kill                                                                                   | `bool`   |                                                                  |            | Set to true if manual throttle kill switch is engaged                                              |
+| termination                                                                            | `bool`   |                                                                  |            | Send out failsafe (by default same as disarmed) output                          |
+| in_esc_calibration_mode | `bool`   |                                                                  |            | IO/FMU should ignore messages from the actuator controls topics                                    |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorArmed.msg)
+
+:::details
+Click here to see original file

 ```c
 uint64 timestamp	# time since system start (microseconds)
@@ -12,5 +36,6 @@ bool lockdown		# Set to true if actuators are forced to being disabled (due to e
 bool kill               # Set to true if manual throttle kill switch is engaged
 bool termination        # Send out failsafe (by default same as disarmed) output
 bool in_esc_calibration_mode # IO/FMU should ignore messages from the actuator controls topics
-
 ```
+
+:::
@@ -1,6 +1,24 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorControlsStatus (UORB message)

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorControlsStatus.msg)
+**TOPICS:** actuator_controls_status_0 actuator_controls_status_1
+
+## Fields
+
+| 参数名                                | 类型           | Unit [Frame] | Range/Enum | 描述                                                        |
+| ---------------------------------- | ------------ | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------- |
+| timestamp                          | `uint64`     |                                                                  |            | time since system start (microseconds) |
+| control_power | `float32[3]` |                                                                  |            |                                                           |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorControlsStatus.msg)
+
+:::details
+Click here to see original file

 ```c
 uint64 timestamp			# time since system start (microseconds)
@@ -8,5 +26,6 @@ uint64 timestamp			# time since system start (microseconds)
 float32[3] control_power

 # TOPICS actuator_controls_status_0 actuator_controls_status_1
-
 ```
+
+:::
@@ -1,11 +1,39 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorMotors (UORB message)

-Motor control message
+Motor control message.

 Normalised thrust setpoint for up to 12 motors.
 Published by the vehicle's allocation and consumed by the ESC protocol drivers e.g. PWM, DSHOT, UAVCAN.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/ActuatorMotors.msg)
+**TOPICS:** actuator_motors
+
+## Fields
+
+| 参数名                                   | 类型            | Unit [Frame] | Range/Enum                                                                   | 描述                                                                                                                                                                                                                                                                    |
+| ------------------------------------- | ------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| timestamp                             | `uint64`      | us                                                               |                                                                              | Time since system start                                                                                                                                                                                                                                               |
+| timestamp_sample | `uint64`      | us                                                               |                                                                              | Sampling timestamp of the data this control response is based on                                                                                                                                                                                                      |
+| reversible_flags | `uint16`      |                                                                  |                                                                              | Bitset indicating which motors are configured to be reversible                                                                                                                                                                                                        |
+| control                               | `float32[12]` |                                                                  | [-1 : 1] | Normalized thrust. where 1 means maximum positive thrust, -1 maximum negative (if not supported by the output, <0 maps to NaN). NaN maps to disarmed (stop the motors) |
+
+## Constants
+
+| 参数名                                                                                                         | 类型       | 值   | 描述 |
+| ----------------------------------------------------------------------------------------------------------- | -------- | --- | -- |
+| <a href="#MESSAGE_VERSION"></a> MESSAGE_VERSION                                        | `uint32` | 0   |    |
+| <a href="#ACTUATOR_FUNCTION_MOTOR1"></a> ACTUATOR_FUNCTION_MOTOR1 | `uint8`  | 101 |    |
+| <a href="#NUM_CONTROLS"></a> NUM_CONTROLS                                              | `uint8`  | 12  |    |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/ActuatorMotors.msg)
+
+:::details
+Click here to see original file

 ```c
 # Motor control message
@@ -24,5 +52,6 @@ uint8 ACTUATOR_FUNCTION_MOTOR1 = 101 #

 uint8 NUM_CONTROLS = 12  #
 float32[12] control      # [@range -1, 1] Normalized thrust. where 1 means maximum positive thrust, -1 maximum negative (if not supported by the output, <0 maps to NaN). NaN maps to disarmed (stop the motors)
-
 ```
+
+:::
@@ -1,6 +1,32 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorOutputs (UORB message)

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorOutputs.msg)
+**TOPICS:** actuator_outputs actuator_outputs_sim actuator_outputs_debug
+
+## Fields
+
+| 参数名       | 类型            | Unit [Frame] | Range/Enum | 描述                                                        |
+| --------- | ------------- | ---------------------------------------------------------------- | ---------- | --------------------------------------------------------- |
+| timestamp | `uint64`      |                                                                  |            | time since system start (microseconds) |
+| noutputs  | `uint32`      |                                                                  |            | valid outputs                                             |
+| output    | `float32[16]` |                                                                  |            | output data, in natural output units                      |
+
+## Constants
+
+| 参数名                                                                                                                                   | 类型      | 值  | 描述                  |
+| ------------------------------------------------------------------------------------------------------------------------------------- | ------- | -- | ------------------- |
+| <a href="#NUM_ACTUATOR_OUTPUTS"></a> NUM_ACTUATOR_OUTPUTS                                   | `uint8` | 16 |                     |
+| <a href="#NUM_ACTUATOR_OUTPUT_GROUPS	"></a> NUM_ACTUATOR_OUTPUT_GROUPS | `uint8` | 4  | for sanity checking |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorOutputs.msg)
+
+:::details
+Click here to see original file

 ```c
 uint64 timestamp				# time since system start (microseconds)
@@ -11,5 +37,6 @@ float32[16] output				# output data, in natural output units

 # actuator_outputs_sim is used for SITL, HITL & SIH (with an output range of [-1, 1])
 # TOPICS actuator_outputs actuator_outputs_sim actuator_outputs_debug
-
 ```
+
+:::
@@ -1,11 +1,37 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorServos (UORB message)

-Servo control message
+Servo control message.

 Normalised output setpoint for up to 8 servos.
 Published by the vehicle's allocation and consumed by the actuator output drivers.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/ActuatorServos.msg)
+**TOPICS:** actuator_servos
+
+## Fields
+
+| 参数名                                   | 类型           | Unit [Frame] | Range/Enum                                                                   | 描述                                                                                                                                                                                                                                                                     |
+| ------------------------------------- | ------------ | ---------------------------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| timestamp                             | `uint64`     | us                                                               |                                                                              | Time since system start                                                                                                                                                                                                                                                |
+| timestamp_sample | `uint64`     | us                                                               |                                                                              | Sampling timestamp of the data this control response is based on                                                                                                                                                                                                       |
+| control                               | `float32[8]` |                                                                  | [-1 : 1] | Normalized output. 1 means maximum positive position. -1 maximum negative position (if not supported by the output, <0 maps to NaN). NaN maps to disarmed. |
+
+## Constants
+
+| 参数名                                                                  | 类型       | 值 | 描述 |
+| -------------------------------------------------------------------- | -------- | - | -- |
+| <a href="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 |    |
+| <a href="#NUM_CONTROLS"></a> NUM_CONTROLS       | `uint8`  | 8 |    |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/versioned/ActuatorServos.msg)
+
+:::details
+Click here to see original file

 ```c
 # Servo control message
@@ -20,5 +46,6 @@ uint64 timestamp_sample  # [us] Sampling timestamp of the data this control resp

 uint8 NUM_CONTROLS = 8  #
 float32[8] control      # [-] [@range -1, 1] Normalized output. 1 means maximum positive position. -1 maximum negative position (if not supported by the output, <0 maps to NaN). NaN maps to disarmed.
-
 ```
+
+:::
@@ -1,8 +1,32 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorServosTrim (UORB message)

-Servo trims, added as offset to servo outputs
+Servo trims, added as offset to servo outputs.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorServosTrim.msg)
+**TOPICS:** actuator_servostrim
+
+## Fields
+
+| 参数名       | 类型           | Unit [Frame] | Range/Enum | 描述                                                                                 |
+| --------- | ------------ | ---------------------------------------------------------------- | ---------- | ---------------------------------------------------------------------------------- |
+| timestamp | `uint64`     |                                                                  |            | time since system start (microseconds)                          |
+| trim      | `float32[8]` |                                                                  |            | range: [-1, 1] |
+
+## Constants
+
+| 参数名                                                            | 类型      | 值 | 描述 |
+| -------------------------------------------------------------- | ------- | - | -- |
+| <a href="#NUM_CONTROLS"></a> NUM_CONTROLS | `uint8` | 8 |    |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorServosTrim.msg)
+
+:::details
+Click here to see original file

 ```c
 # Servo trims, added as offset to servo outputs
@@ -10,5 +34,6 @@ uint64 timestamp			# time since system start (microseconds)

 uint8 NUM_CONTROLS = 8
 float32[8] trim    # range: [-1, 1]
-
 ```
+
+:::
@@ -1,6 +1,39 @@
+---
+pageClass: is-wide-page
+---
+
 # ActuatorTest (UORB message)

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorTest.msg)
+**TOPICS:** actuator_test
+
+## Fields
+
+| 参数名                             | 类型        | Unit [Frame] | Range/Enum | 描述                                                                                                                         |
+| ------------------------------- | --------- | ---------------------------------------------------------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------- |
+| timestamp                       | `uint64`  |                                                                  |            | time since system start (microseconds)                                                                  |
+| action                          | `uint8`   |                                                                  |            | one of ACTION\_\*                                                                                    |
+| function                        | `uint16`  |                                                                  |            | actuator output function                                                                                                   |
+| value                           | `float32` |                                                                  |            | range: [-1, 1], where 1 means maximum positive output, |
+| timeout_ms | `uint32`  |                                                                  |            | timeout in ms after which to exit test mode (if 0, do not time out)                                     |
+
+## Constants
+
+| 参数名                                                                                                     | 类型      | 值   | 描述                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------- | ------- | --- | -------------------------------------------------------------------------------------------------------------------- |
+| <a href="#ACTION_RELEASE_CONTROL"></a> ACTION_RELEASE_CONTROL | `uint8` | 0   | exit test mode for the given function                                                                                |
+| <a href="#ACTION_DO_CONTROL"></a> ACTION_DO_CONTROL           | `uint8` | 1   | enable actuator test mode                                                                                            |
+| <a href="#FUNCTION_MOTOR1"></a> FUNCTION_MOTOR1                                    | `uint8` | 101 |                                                                                                                      |
+| <a href="#MAX_NUM_MOTORS"></a> MAX_NUM_MOTORS                 | `uint8` | 12  |                                                                                                                      |
+| <a href="#FUNCTION_SERVO1"></a> FUNCTION_SERVO1                                    | `uint8` | 201 |                                                                                                                      |
+| <a href="#MAX_NUM_SERVOS"></a> MAX_NUM_SERVOS                 | `uint8` | 8   |                                                                                                                      |
+| <a href="#ORB_QUEUE_LENGTH"></a> ORB_QUEUE_LENGTH             | `uint8` | 16  | > = MAX_NUM_MOTORS to support code in esc_calibration |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/ActuatorTest.msg)
+
+:::details
+Click here to see original file

 ```c
 uint64 timestamp				# time since system start (microseconds)
@@ -24,5 +57,6 @@ float32 value					# range: [-1, 1], where 1 means maximum positive output,
 uint32 timeout_ms				# timeout in ms after which to exit test mode (if 0, do not time out)

 uint8 ORB_QUEUE_LENGTH = 16                     # >= MAX_NUM_MOTORS to support code in esc_calibration
-
 ```
+
+:::
@@ -1,10 +1,32 @@
+---
+pageClass: is-wide-page
+---
+
 # AdcReport (UORB message)

 ADC raw data.

 Communicates raw data from an analog-to-digital converter (ADC) to other modules, such as battery status.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/AdcReport.msg)
+**TOPICS:** adc_report
+
+## Fields
+
+| 参数名                             | 类型          | Unit [Frame] | Range/Enum | 描述                                                                                                   |
+| ------------------------------- | ----------- | ---------------------------------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------- |
+| timestamp                       | `uint64`    | us                                                               |            | Time since system start                                                                              |
+| device_id  | `uint32`    |                                                                  |            | unique device ID for the sensor that does not change between power cycles                            |
+| channel_id | `int16[16]` |                                                                  |            | ADC channel IDs, negative for non-existent, TODO: should be kept same as array index |
+| raw_data   | `int32[16]` |                                                                  |            | ADC channel raw value, accept negative value, valid if channel ID is positive                        |
+| resolution                      | `uint32`    |                                                                  |            | ADC channel resolution                                                                               |
+| v_ref      | `float32`   | V                                                                |            | ADC channel voltage reference, use to calculate LSB voltage(lsb=scale/resolution) |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/AdcReport.msg)
+
+:::details
+Click here to see original file

 ```c
 # ADC raw data.
@@ -17,5 +39,6 @@ int16[16] channel_id  # [-] ADC channel IDs, negative for non-existent, TODO: sh
 int32[16] raw_data    # [-] ADC channel raw value, accept negative value, valid if channel ID is positive
 uint32 resolution     # [-] ADC channel resolution
 float32 v_ref         # [V] ADC channel voltage reference, use to calculate LSB voltage(lsb=scale/resolution)
-
 ```
+
+:::
@@ -1,11 +1,32 @@
+---
+pageClass: is-wide-page
+---
+
 # Airspeed (UORB message)

-Airspeed data from sensors
+Airspeed data from sensors.

 This is published by airspeed sensor drivers, CAN airspeed sensors, simulators.
 It is subscribed by the airspeed selector module, which validates the data from multiple sensors and passes on a single estimation to the EKF, controllers and telemetry providers.

-[source file](https://github.com/PX4/PX4-Autopilot/blob/main/msg/Airspeed.msg)
+**TOPICS:** airspeed
+
+## Fields
+
+| 参数名                                                                                   | 类型        | Unit [Frame] | Range/Enum                                                                  | 描述                               |
+| ------------------------------------------------------------------------------------- | --------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------- |
+| timestamp                                                                             | `uint64`  | us                                                               |                                                                             | Time since system start          |
+| timestamp_sample                                                 | `uint64`  | us                                                               |                                                                             | Timestamp of the raw data        |
+| indicated_airspeed_m_s | `float32` | 米/秒                                                              |                                                                             | Indicated airspeed               |
+| true_airspeed_m_s      | `float32` | 米/秒                                                              |                                                                             | True airspeed                    |
+| confidence                                                                            | `float32` |                                                                  | [0 : 1] | Confidence value for this sensor |
+
+## Source Message
+
+[Source file (GitHub)](https://github.com/PX4/PX4-Autopilot/blob/main/msg/Airspeed.msg)
+
+:::details
+Click here to see original file

 ```c
 # Airspeed data from sensors
@@ -18,5 +39,6 @@ uint64 timestamp_sample          # [us] Timestamp of the raw data
 float32 indicated_airspeed_m_s   # [m/s] Indicated airspeed
 float32 true_airspeed_m_s        # [m/s] True airspeed
 float32 confidence               # [@range 0,1] Confidence value for this sensor
-
 ```
+
+:::
--- a/Show More
+++ b/Show More