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

New Crowdin translations - ko (#24547)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-03-19 15:54:47 +11:00
committed by GitHub
co-authored by Crowdin Bot
parent c77f3887aa
commit 77df2c97ec
179 changed files with 2407 additions and 2400 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ko/camera/fc_connected_camera.md
+6 -6
View File
@@ -188,16 +188,16 @@ The following sections are out of date and need retesting.
1. On the PX4 console:
```shell
camera_trigger test
```
```shell
camera_trigger test
```
2. From _QGroundControl_:
Click on **Trigger Camera** in the main instrument panel.
These shots are not logged or counted for geotagging.
Click on **Trigger Camera** in the main instrument panel.
These shots are not logged or counted for geotagging.
![QGC Test Camera](../../assets/camera/qgc_test_camera.png)
![QGC Test Camera](../../assets/camera/qgc_test_camera.png)
## Sony QX-1 example (Photogrammetry)
docs/ko/camera/index.md
+1 -1
View File
@@ -17,4 +17,4 @@ If a camera does not support this prototol, a [camera manager](../camera/mavlink
## See Also
- [Gimbal (Camera Mount)](../advanced/gimbal_control.md)
- [Camera Integration/Architecture](../camera/camera_architecture.md) (PX4 Developers)
- [Camera Integration/Architecture](../camera/camera_architecture.md) (PX4 Developers)
docs/ko/camera/mavlink_v1_camera.md
+1 -1
View File
@@ -86,7 +86,7 @@ The document explains how, but in summary:
1. Modify an unused `MAV_n_CONFIG` parameter, such as [MAV_2_CONFIG](../advanced_config/parameter_reference.md#MAV_2_CONFIG), so that it is assigned to port to which your camera is connected.
2. Set the corresponding [MAV_2_MODE](../advanced_config/parameter_reference.md#MAV_2_MODE) to `2` (Onboard).
This ensures that the right set of MAVLink messages are emitted and forwarded.
This ensures that the right set of MAVLink messages are emitted and forwarded.
3. You may need to set some of the other parameters, depending on your connection - such as the baud rate.
Then connect and configure the camera as recommended in its user guide.
docs/ko/camera/mavlink_v2_camera.md
+1 -1
View File
@@ -112,7 +112,7 @@ The linked document explains how, but in summary:
1. Modify an unused `MAV_n_CONFIG` parameter, such as [MAV_2_CONFIG](../advanced_config/parameter_reference.md#MAV_2_CONFIG), so that it is assigned to port to which you connected the camera/companion computer.
2. Set the corresponding [MAV_2_MODE](../advanced_config/parameter_reference.md#MAV_2_MODE) to `2` (Onboard).
This ensures that the right set of MAVLink messages are emitted for a companion computer (or camera).
This ensures that the right set of MAVLink messages are emitted for a companion computer (or camera).
3. Set [MAV_2_FORWARD](../advanced_config/parameter_reference.md#MAV_2_FORWARD) to enable forwarding of communications from the port to other ports, such as the one that is connected to the ground station.
4. You may need to set some of the other parameters, depending on your connection type and any particular requirements of the camera on the expected baud rate, and so on.