UAV-develop/PX4-Autopilot
1
0
Fork 0
mirror of https://github.com/PX4/PX4-Autopilot.git synced 2026-07-27 00:48:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(i18n): PX4 guide translations (Crowdin) - ko (#27701)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2026-06-22 09:05:09 +10:00
committed by GitHub
parent 605e82136d
commit 0a1c99117b
2 changed files with 39 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/ko/advanced/gimbal_control.md
View File

@@ -23,6 +23,9 @@ You should set `MNT_MODE_IN` to one of: `RC (1)`, `MAVlink gimbal protocol v2 (4
If you select `Auto (0)`, the gimbal will automatically select either RC or MAVLink input based on the latest input.
Note that the auto-switch from MAVLink to RC requires a large stick motion!
To hold a fixed attitude that the pilot cannot control (e.g. for RF/Satellite receiver stabilization), set `MNT_MODE_IN` to `Fixed attitude (5)`.
See [Fixed Attitude Gimbal](#fixed-attitude-gimbal) below.
The output is set using the [MNT_MODE_OUT](../advanced_config/parameter_reference.md#MNT_MODE_OUT) parameter.
By default the output is set to a PXM port (`AUX (0)`).
If the [MAVLink Gimbal Protocol v2](https://mavlink.io/en/services/gimbal_v2.html) is supported by your gimbal, you should instead select `MAVLink gimbal protocol v2 (2)`.
@@ -77,6 +80,20 @@ For example, you might have the following settings to assign the gimbal roll, pi
The PWM values to use for the disarmed, maximum, center and minimum values can be determined in the same way as other servo, using the [Actuator Test sliders](../config/actuators.md#actuator-testing) to confirm that each slider moves the appropriate axis, and changing the values so that the gimbal is in the appropriate position at the disarmed, low, center and high position in the slider.
The values may also be provided in gimbal documentation.
## Fixed Attitude Gimbal
A fixed-attitude gimbal holds a constant world-frame attitude and cannot be controlled by the pilot.
This is useful for stabilizing a payload that must keep pointing in a fixed direction regardless of vehicle motion, such as an RF or satellite receiver antenna.
To enable it, set [MNT_MODE_IN](../advanced_config/parameter_reference.md#MNT_MODE_IN) to `Fixed attitude (5)` and reboot.
In this mode no RC or MAVLink input is created, so the attitude cannot be commanded from a transmitter or ground station.
The gimbal holds roll and yaw level (roll at 0, yaw at north), and pitch at the angle set in [MNT_FIXED_PITCH](../advanced_config/parameter_reference.md#MNT_FIXED_PITCH) (in degrees, world frame).
Because the setpoint is in the world frame, stabilization against vehicle motion must be enabled with [MNT_DO_STAB](../advanced_config/parameter_reference.md#MNT_DO_STAB):
- Set `MNT_DO_STAB` to `Stabilize all axis (1)` for the typical servo (AUX) gimbal.
## Gimbal Control in Missions
[Gimbal Manager commands](https://mavlink.io/en/services/gimbal_v2.html#gimbal-manager-messages) may be used in missions if supported by the vehicle type.

39
docs/ko/dev_setup/dev_env_windows_wsl.md
View File

@@ -22,18 +22,21 @@ With this environment developers can:
- Build any simulator or hardware target supported by [Ubuntu Development Environment](../dev_setup/dev_env_linux_ubuntu.md) in the WSL Shell.
(Ubuntu is the best supported and tested PX4 development platform).
- [Update firmware](#flash-a-flight-control-board) on a real vehicle _using the command line_.
- Debug code in [Visual Studio Code](dev_env_windows_wsl.md#visual-studio-code-integration) running on Windows.
- Monitor a _simulation_ using _QGroundControl for Linux_ running in WSL.
QGC for Linux connects automatically to the simulation.
_QGroundControl for Windows_ is additionally required if you need to:
- [Update firmware](#flash-a-flight-control-board) on a real vehicle.
- [Update firmware](#flash-a-flight-control-board) using the QGC UI.
- Monitor a real vehicle.
Note that you can also use it to monitor a simulation, but you must manually [connect to the simulation running in WSL](#qgroundcontrol-on-windows).
:::info
Connecting to an USB device from within WSL is not natively supported, however it can still be achieved by using the [USBIPD-WIN](https://learn.microsoft.com/en-us/windows/wsl/connect-usb) project. With this you can automatically upload firmware from the command line in WSL using the [`upload`](../dev_setup/building_px4.md#uploading-firmware-flashing-the-board) function.
:::tip
Connecting to an USB device from within WSL is not natively supported, but can be enabled via [USBIPD-WIN](https://learn.microsoft.com/en-us/windows/wsl/connect-usb).
From PX4 v1.18, you can upload PX4 firmware over USB from the WSL command line using the [`upload`](../dev_setup/building_px4.md#uploading-firmware-flashing-the-board) target (this uses the Windows Python interpreter on WSL to access the flight controller through the Windows COM port).
:::
:::info
@@ -229,7 +232,7 @@ To set up the integration:
## QGroundControl
You can run QGroundControl in either WSL or Windows to connect to the running simulation.
If you need to [flash a flight control board](#flash-a-flight-control-board) with new firmware you can only do this from the QGroundControl for Windows.
If you want to flash a flight control board using the QGroundControl GUI, you _must_ use QGroundControl for Windows.
### QGroundControl in WSL
@@ -292,38 +295,40 @@ You will have to update the WSL comm link in QGC every time WSL restarts (becaus
## Flash a Flight Control Board
Flashing a custom built PX4 binary has to be done using [QGroundControl for Windows](#qgroundcontrol-on-windows).
Custom PX4 firmware built in WSL can be uploaded directly from the WSL command line using the [`upload`](../dev_setup/building_px4.md#uploading-firmware-flashing-the-board) target.
:::info
WSL2 does not natively offer direct access to serial/USB devices like Pixhawk flight controllers connected to your computer.
That means you can't connect QGC running inside WSL2 to a flight controller to install firmware, or use the `upload` command to [upload firmware as it is built](../dev_setup/building_px4.md#uploading-firmware-flashing-the-board).
Instead you connect [QGroundControl for Windows](#qgroundcontrol-on-windows) to PX4 running in WSL2 and to the Flight controller in order to upload the firmware.
The PX4 `upload` target works around this by using the Windows Python interpreter from WSL to access the flight controller through the Windows COM port.
:::
Do the following steps to flash your custom binary built in WSL:
To flash your custom binary from WSL:
1. If you haven't already built the binary in WSL e.g. with a [WSL shell](dev_env_windows_wsl.md#opening-a-wsl-shell) and by running:
1. Connect the flight controller to your computer with a USB cable.
2. Open a [WSL shell](dev_env_windows_wsl.md#opening-a-wsl-shell), switch to the PX4 repository, and specify `upload` after your make target:
```sh
cd ~/PX4-Autopilot
make px4_fmu-v5
make px4_fmu-v5 upload
```
::: tip
This builds `px4_fmu-v5`.
Use the correct `make` target for your board.
`px4_fmu-v5` can be used for a Pixhawk 4 board.
:::
2. Detach the USB cable of your Pixhawk board from the computer if it was connected.
You can also flash a custom binary built in WSL using [QGroundControl for Windows](#qgroundcontrol-on-windows):
3. Open QGC and navigate to **Q > Vehicle Setup > Firmware**.
1. Detach the USB cable of your Pixhawk board from the computer if it was connected.
4. Plug your Pixhawk board via USB
2. Open QGC and navigate to **Q > Vehicle Setup > Firmware**.
5. Once connected select "PX4 Flight Stack", check **Advanced settings** and choose _Custom firmware file ..._ from the drop down below.
3. Plug your Pixhawk board via USB
6. Continue and select the firmware binary you just built in WSL.
4. Once connected select "PX4 Flight Stack", check **Advanced settings** and choose _Custom firmware file ..._ from the drop down below.
5. Continue and select the firmware binary you just built in WSL.
In the open dialog look for the "Linux" location with the penguin icon in the left pane.
It's usually all the way at the bottom.
@@ -334,7 +339,7 @@ Do the following steps to flash your custom binary built in WSL:
:::
7. Start the flashing.
6. Start the flashing.
For more information see [Installing PX4 Main, Beta or Custom Firmware (Loading Firmware)](../config/firmware.md#installing-px4-main-beta-or-custom-firmware).