New Crowdin translations - ko (#26487)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-05-10 06:39:25 +08:00 · 2026-02-18 16:44:57 +11:00
parent 602add3ec1
commit 18c176beef
314 changed files with 11938 additions and 1357 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 배선 퀵 스타트](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 @@
      - [Benewake 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 @@ Performing this calibration step is only recommended if the autopilot's orientat
 :::

 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 @@ Make sure to have assigned a [Kill switch](../config/safety.md#emergency-switche
 13. 모든 축에서 자세 콘트롤러에 대하여 튜닝 프로세스를 반복하십시오.

 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 @@ Navigate into the **PX4-Autopilot** directory and start [Gazebo SITL](../sim_gaz
 make px4_sitl gz_x500
 ```

-:::details
-If you installed Gazebo Classic
-Start  [Gazebo Classic SITL](../sim_gazebo_classic/index.md) using the following command:
-
-```sh
-make px4_sitl gazebo-classic
-```
-
-:::
-
 This will bring up the PX4 console:

 ![PX4 Console](../../assets/toolchain/console_gazebo.png)
@@ -89,6 +79,16 @@ cd PX4-Autopilot
 make px4_fmu-v4_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'
+```
+
+:::
+
 A successful run will end with similar output to:

 ```sh
@@ -145,7 +145,8 @@ The following list shows the build commands for the [Pixhawk standard](../flight
 - [Pixhawk 1 (FMUv2)](../flight_controller/pixhawk.md): `make px4_fmu-v2_default`

  :::warning
-  You **must** use a supported version of GCC to build this board (e.g. the same as used by [CI/docker](../test_and_ci/docker.md)) or remove modules from the build. PX4가 보드의 1MB 플래시 제한에 가깝기 때문에, 지원되지 않는 GCC로 빌드가 실패할 수 있습니다.
+  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.
+  PX4가 보드의 1MB 플래시 제한에 가깝기 때문에, 지원되지 않는 GCC로 빌드가 실패할 수 있습니다.

 :::

@@ -211,7 +212,7 @@ The `region 'flash' overflowed by XXXX bytes` error indicates that the firmware
 This is common for `make px4_fmu-v2_default` builds, where the flash size is limited to 1MB.

 If you're building the _vanilla_ master branch, the most likely cause is using an unsupported version of GCC.
-In this case, install the version specified in the [Developer Toolchain](../dev_setup/dev_env.md) instructions.
+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.

 If building your own branch, it is possible that you have increased the firmware size over the 1MB limit.
 PX4 빌드 시스템은 많은 수의 파일을 오픈하므로, 이 갯수를 초과할 수 있습니다.
@@ -224,7 +225,7 @@ The PX4 build system opens a large number of files, so you may exceed this numbe
 The build toolchain will then report `Too many open files` for many files, as shown below:

 ```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
 ```

 The solution is to increase the maximum allowed number of open files (e.g. to 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와 관련된 컴파일 오류
-
-Build issues related to `arm_none_eabi_gcc`may be due to a broken g++ toolchain installation.
-You can verify that this is the case by checking for missing dependencies using:
-
-```sh
-arm-none-eabi-gcc --version
-arm-none-eabi-g++ --version
-arm-none-eabi-gdb --version
-arm-none-eabi-size --version
-```
-
-Example of bash output with missing dependencies:
-
-```sh
-arm-none-eabi-gdb --version
-arm-none-eabi-gdb: command not found
-```
-
-This can be resolved by removing and [reinstalling the compiler](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는 이 큰 작업 영역에서 파일 변경 사항을 감시할 수 없습니다.
-
-See [Visual Studio Code IDE (VSCode) > Troubleshooting](../dev_setup/vscode.md#troubleshooting).
-
 ### Python 패키지를 가져오지 못했습니다.

-"Failed to import" errors when running the `make px4_sitl jmavsim` command indicates that some Python packages are not installed (where expected).
+"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 @@ You may need to install it using:
    pip3 install --user jinja2
 ```

-다음과 같이 종속성을 명시적으로 설치하여, 이 문제를 해결할 수 있습니다.
+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 explicitly installing the dependencies as shown:
+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) |                 ✓                 |   ✓   |  ✓  |
 | **Linux-based hardware:** [Raspberry Pi 2/3](../flight_controller/raspberry_pi_navio2.md)                                              |                 ✓                 |       |     |
 | **Simulation:** [Gazebo SITL](../sim_gazebo_gz/index.md)                                                                               |                 ✓                 |   ✓   |  ✓  |
-| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md)                                                                  |                 ✓                 |   ✓   |  ✓  |
-| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md)                                                              |                 ✓                 |       |  ✓  |
 | **Simulation:** ROS 2 with Gazebo                                                                                                      |                 ✓                 |       |  ✓  |
+| **Simulation:** [Gazebo Classic SITL](../sim_gazebo_classic/index.md)                                                                  |                                   |   ✓   |  ✓  |
+| **Simulation:** [ROS with Gazebo Classic](../simulation/ros_interface.md)                                                              |                                   |       |  ✓  |

 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`.
 아래 스크립트로 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 @@ The script is intended to be run on _clean_ Ubuntu LTS installations, and may no
   - 스크립트가 진행되는 동안 모든 프롬프트를 확인합니다.
   - 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](../
 빌드를 진행하려면:

 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)

@@ -134,10 +133,10 @@ In order for the code completion to work (and other IntelliSense magic) you need

 이 섹션에는 설정 및 빌드 오류에 대한 지침이 포함되어 있습니다.

-### Ubuntu 18.04: "Visual Studio Code는 이 큰 작업 영역에서 파일 변경 사항을 감시할 수 없습니다."
+### "Visual Studio Code is unable to watch for file changes in this large workspace"

 이 오류는 시작시에 나타납니다.
-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`.

 메모리 소비를 희생시키면서 오류를 방지하기 위해 이 제한을 늘릴 수 있습니다.
 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                      | 방향  | 전압                    | 기능          |   |     |    |
-  | ---------- | ----------------------------- | --- | --------------------- | ----------- | - | --- | -- |
-  | 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 | 접지 |
+  \| 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 @@ This category includes boards that are not fully compliant with the pixhawk stan
 - [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
+
+## 커넥터 및 핀
+
+:::warning
+The pin order is different from the Pixhawk standard (compatible to the Betaflight standard).
+:::
+
+### UART
+
+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
+
+| 커넥터 | 핀  | 기능                           |
+| --- | -- | ---------------------------- |
+| 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>
+
+## 부트로더 업데이트
+
+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
+```
+
+## 펌웨어 설치
+
+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_.
+  미리 빌드된 펌웨어나 사용자 지정 펌웨어를 사용할 수 있습니다.
+
+### 시스템 콘솔
+
+UART1 (ttyS0) is configured for use as the [System Console](../debug/system_console.md).
@@ -231,7 +231,7 @@ The following MAVLink messages and their particular fields and field values are

    - 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 @@ The following MAVLink messages and their particular fields and field values are
        - 12288 : Loiter 설정점 (설정점을 중심으로 선회 비행합니다).
        - 16384 : 유휴 설정점 (제로 스로틀, 제로 롤/피치).

-  - 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 @@ The following MAVLink messages and their particular fields and field values are

 ### 탐사선

-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.

 ## 오프보드 매개변수

@@ -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 위치를 전송 여부를 확인하십시오.
 :::

@@ -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%                                                                                                                                          |
-| OFF   | x   | x     | Overload CPU load <= 80%, or RAM usage <= 98%                                                                                      |
-| NA    | OFF | 4 Hz  | actuator_armed->armed && failsafe                                                                                       |
-| NA    | ON  | 4 Hz  | actuator_armed->armed && !failsafe                                                                                      |
-| NA    | OFF | 1 Hz  | !actuator_armed-> armed && actuator_armed->ready_to_arm  |
-| NA    | OFF | 10 Hz | !actuator_armed->armed  && !actuator_armed->ready_to_arm |
+| 적색/황색 | 청색  | 녹색    | 설명                                                                                                                                                                                  |
+| ----- | --- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 10Hz  | x   | x     | Overload CPU load > 80%, or RAM usage > 98%                                                                                                                                         |
+| OFF   | x   | x     | Overload CPU load <= 80%, or RAM usage <= 98%                                                                                     |
+| NA    | OFF | 4 Hz  | actuator_armed->armed && failsafe                                                                                      |
+| NA    | ON  | 4 Hz  | actuator_armed->armed && !failsafe                                                                                     |
+| NA    | OFF | 1 Hz  | !actuator_armed-> armed && actuator_armed->ready_to_arm |
+| NA    | OFF | 10 Hz | !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

 부팅중에 재생되는 톤들입니다.

-<!-- 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 -->

 #### 시작 톤

@@ -153,7 +153,6 @@ RTK GPS 연결은 기본적으로 플러그앤플레이입니다.
   ![survey-in](../../assets/qgc/setup/rtk/qgc_rtk_survey-in.png)

 4. Survey-in이 완료되면 :
-
   - 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,20 +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 Autopilot 사용자 안내서

 [![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 is the _Professional Autopilot_.
-세계적인 수준의 개발자들이 산업계와 학계에서 참여하여 개발하였으며,
-세계 각국에서 활동중인 여러 단체들의 지원을 받을 수 있습니다. PX4는 레이싱 드론, 운송용 드론, 자동차와 선박 등의 다양한 운송체에 적용하여 사용할 수 있습니다.
-
-:::tip
-This guide contains everything you need to assemble, configure, and safely fly a PX4-based vehicle.
-이 프로젝트에 기여하시려면,  Check out the [Development](development/development.md) section.
-:::
+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)'">

@@ -30,83 +21,43 @@ Documented changes since the stable release are captured in the evolving [releas

 </div>

+## For Developers
+
+:::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/).
+:::
+
 ## 시작하기

-[Basic Concepts](getting_started/px4_basic_concepts.md) should be read by all users!
-비행 스택(비행 모드 및 안전 기능)과 지원 하드웨어(비행 제어장치, 기체 형식, 텔레메트리, 원격 제어 시스템) 등 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.

-이 안내서를 위한 팁들은 아래과 같습니다.
+## Build a Vehicle

-### PX4로 동작하는 기체를 만들려고 합니다
+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.

-In the [Multicopter](frames_multicopter/index.md), [VTOL](frames_vtol/index.md), and [Plane (Fixed-Wing)](frames_plane/index.md) sections you'll find topics like the following (these links are for multicopter):
+## Configure and Tune

- [Complete Vehicles](complete_vehicles_mc/index.md) list "Ready to Fly" (RTF) pre-built vehicles
- [Kits](frames_multicopter/kits.md) lists drones that you have to build yourself from a set of preselected parts
- [DIY Builds](frames_multicopter/diy_builds.md) shows some examples of drones that have been built using parts that were sourced individually
+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.

-Both kits and complete vehicles usually include everything you need except for a battery and RC System.
-Kits are usually not hard to build, provide a good introduction to how drones fit together, and are relatively inexpensive.
-We provide generic instructions for assembly, such as [Assembling a Multicopter](assembly/assembly_mc.md), and most kits come with specific instructions too.
+## 하드웨어

-If the kits and complete drones aren't quite right for you then you can build a vehicle from scratch, but this requires more knowledge.
-[Airframe Builds](airframes/index.md) lists the supported frame starting points to give you some idea of what is possible.
+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.

-Once you have a vehicle that supports PX4 you will need to configure it and calibrate the sensors.
-Each vehicle type has its own configuration section that explains the main steps, such as [Multicopter Configuration/Tuning](config_mc/index.md).
+## Fly

-### I want to add a payload/camera
+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.

-The [Payloads](payloads/index.md) section describes how to add a camera and how to configure PX4 to enable you to deliver packages.
+## 지원

-### I am modifying a supported vehicle
-
-The [Hardware Selection & Setup](hardware/drone_parts.md) section provides both high level and product-specific information about hardware that you might use with PX4 and its configuration.
-This is the first place you should look if you want to modify a drone and add new components.
-
-### I want to fly
-
-Before you fly you should read [Operations](config/operations.md) to understand how to set up the safety features of your vehicle and the common behaviours of all frame types.
-Once you've done that you're ready to fly.
-
-Basic instructions for flying each vehicle type are provided in the respective sections, such as [Basic Flying (Multicopter)](flying/basic_flying_mc.md).
-
-### I want to run PX4 on a new Flight Controller and extend the platform
-
-The [Development](development/development.md) section explains how to support new airframes and types of vehicles, modify flight algorithms, add new modes, integrate new hardware, communicate with PX4 from outside the flight controller, and contribute to PX4.
-
-## 도움 받기
-
-The [Support](contribute/support.md) page explains how to get help from the core dev team and the wider community.
-
-다음과 같은 내용을 다룹니다.
-
- [Forums where you can get help](contribute/support.md#forums-and-chat)
- [Diagnosing issues](contribute/support.md#diagnosing-problems)
- [How to report bugs](contribute/support.md#issue-bug-reporting)
- [Weekly dev call](contribute/support.md#weekly-dev-call)
-
-## Reporting Bugs & Issues
-
-If you have any problems using PX4 first post them on the [support forums](contribute/support.md#forums-and-chat) (as they may be caused by vehicle configuration).
-
-If directed by the development team, code issues may be raised on [Github here](https://github.com/PX4/PX4-Autopilot/issues).
-Where possible provide [flight logs](getting_started/flight_reporting.md) and other information requested in the issue template.
+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).

 ## 기여

-Information on how to contribute to code and documentation can be found in the [Contributing](contribute/index.md) section:
-
- [Code](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.

 ## 번역

-There are several [translations](contribute/translation.md) of this guide.
-우상단의 언어 메뉴에서 원하시는 번역본을 선택할 수 있습니다:
-
-![Language Selector](../assets/vuepress/language_selector.png)
+There are several [translations](contribute/translation.md) of this guide. Use the language selector in the top navigation.

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

@@ -143,9 +94,9 @@ The calendar default timezone is Central European Time (CET).

 ## 운영 방법

-The PX4 flight stack is hosted under the governance of the [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
+```
+
 ## module

 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}
+
+| 명칭                                                                                                                                                                              | 형식      | Value | 설명                                                                                       |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | ---------------------------------------------------------------------------------------- |
+| <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}
+
+| 명칭                                                                                                                     | 형식      | Value | 설명                                                              |
+| ---------------------------------------------------------------------------------------------------------------------- | ------- | ----- | --------------------------------------------------------------- |
+| <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
+
+| 명칭                                                                                                          | 형식       | Value | 설명 |
+| ----------------------------------------------------------------------------------------------------------- | -------- | ----- | -- |
+| <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
+
+| 명칭                                                                                                                                    | 형식      | Value | 설명                  |
+| ------------------------------------------------------------------------------------------------------------------------------------- | ------- | ----- | ------------------- |
+| <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
+
+| 명칭                                                                   | 형식       | Value | 설명 |
+| -------------------------------------------------------------------- | -------- | ----- | -- |
+| <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
+
+| 명칭                                                             | 형식      | Value | 설명 |
+| -------------------------------------------------------------- | ------- | ----- | -- |
+| <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
+
+| 명칭                                                                                                      | 형식      | Value | 설명                                                                                                                   |
+| ------------------------------------------------------------------------------------------------------- | ------- | ----- | -------------------------------------------------------------------------------------------------------------------- |
+| <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` | m/s                                                              |                                                                             | Indicated airspeed               |
+| true_airspeed_m_s      | `float32` | m/s                                                              |                                                                             | 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