New Crowdin translations - ko (#24547)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-10-17 06:23:34 +08:00 · 2025-03-19 15:54:47 +11:00
parent c77f3887aa
commit 77df2c97ec
179 changed files with 2407 additions and 2400 deletions
@@ -47,7 +47,7 @@ PX4 v1.14 (and later) supports the [LightWare LiDAR SF45](../sensor/sf45_rotatin

 - Attach and configure the distance sensor on a particular port (see [sensor-specific docs](../sensor/rangefinders.md)) and enable collision prevention using [CP_DIST](#CP_DIST).
 - 방향을 설정하려면 드라이버를 수정하십시오.
-  This should be done by mimicking the `SENS_CM8JL65_R_0` parameter (though you might also hard-code the orientation in the sensor _module.yaml_ file to something like `sf0x start -d ${SERIAL_DEV} -R 25` - where 25 is equivalent to `ROTATION_DOWNWARD_FACING`).
+ This should be done by mimicking the `SENS_CM8JL65_R_0` parameter (though you might also hard-code the orientation in the sensor _module.yaml_ file to something like `sf0x start -d ${SERIAL_DEV} -R 25` - where 25 is equivalent to `ROTATION_DOWNWARD_FACING`).
 - Modify the driver to set the _field of view_ in the distance sensor UORB topic (`distance_sensor_s.h_fov`).

 ## PX4 (Software) Setup
@@ -184,7 +184,7 @@ Next, adjust the relevant parameters to the appropriate values and add arbitrary

 The diagram below shows a simulation of collision prevention as viewed in Gazebo.

-![RViz image of collision detection using the x500\_lidar\_2d model in Gazebo](../../assets/simulation/gazebo/vehicles/x500_lidar_2d_viz.png)
+![RViz image of collision detection using the x500_lidar_2d model in Gazebo](../../assets/simulation/gazebo/vehicles/x500_lidar_2d_viz.png)

 ## Development Information/Tools

@@ -203,85 +203,85 @@ The Lua script works by extracting the `obstacle_distance_fused` data at each ti

 2. Configure PX4 to publish obstacle distance data (so that it is available to PlotJuggler):

-   Add the [`obstacle_distance_fused`](../msg_docs/ObstacleDistance.md) UORB topic to your [`dds_topics.yaml`](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/uxrce_dds_client/dds_topics.yaml) so that it is published by PX4:
+ Add the [`obstacle_distance_fused`](../msg_docs/ObstacleDistance.md) UORB topic to your [`dds_topics.yaml`](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/uxrce_dds_client/dds_topics.yaml) so that it is published by PX4:

-   ```sh
-   - topic: /fmu/out/obstacle_distance_fused
-     type: px4_msgs::msg::ObstacleDistance
-   ```
+ ```sh
+ - topic: /fmu/out/obstacle_distance_fused
+   type: px4_msgs::msg::ObstacleDistance
+ ```

-   For more information see [DDS Topics YAML](../middleware/uxrce_dds.md#dds-topics-yaml) in _uXRCE-DDS (PX4-ROS 2/DDS Bridge)_.
+ For more information see [DDS Topics YAML](../middleware/uxrce_dds.md#dds-topics-yaml) in _uXRCE-DDS (PX4-ROS 2/DDS Bridge)_.

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

-   - **Global code, executed once:**
+ - **Global code, executed once:**

-     ```lua
-     obs_dist_fused_xy = ScatterXY.new("obstacle_distance_fused_xy")
-     obs_dist_min = Timeseries.new("obstacle_distance_minimum")
-     ```
+  ```lua
+  obs_dist_fused_xy = ScatterXY.new("obstacle_distance_fused_xy")
+  obs_dist_min = Timeseries.new("obstacle_distance_minimum")
+  ```

-   - **function(tracker_time)**
+ - **function(tracker_time)**

-     ```lua
-     obs_dist_fused_xy:clear()
+  ```lua
+  obs_dist_fused_xy:clear()

-     i = 0
-     angle_offset = TimeseriesView.find("/fmu/out/obstacle_distance_fused/angle_offset")
-     increment = TimeseriesView.find("/fmu/out/obstacle_distance_fused/increment")
-     min_dist = 65535
+  i = 0
+  angle_offset = TimeseriesView.find("/fmu/out/obstacle_distance_fused/angle_offset")
+  increment = TimeseriesView.find("/fmu/out/obstacle_distance_fused/increment")
+  min_dist = 65535

-     -- Cache increment and angle_offset values at tracker_time to avoid repeated calls
-     local angle_offset_value = angle_offset:atTime(tracker_time)
-     local increment_value = increment:atTime(tracker_time)
+  -- Cache increment and angle_offset values at tracker_time to avoid repeated calls
+  local angle_offset_value = angle_offset:atTime(tracker_time)
+  local increment_value = increment:atTime(tracker_time)

-     if increment_value == nil or increment_value <= 0 then
-         print("Invalid increment value: " .. tostring(increment_value))
-         return
-     end
+  if increment_value == nil or increment_value <= 0 then
+      print("Invalid increment value: " .. tostring(increment_value))
+      return
+  end

-     local max_steps = math.floor(360 / increment_value)
+  local max_steps = math.floor(360 / increment_value)

-     while i < max_steps do
-         local str = string.format("/fmu/out/obstacle_distance_fused/distances[%d]", i)
-         local distance = TimeseriesView.find(str)
-         if distance == nil then
-             print("No distance data for: " .. str)
-             break
-         end
+  while i < max_steps do
+      local str = string.format("/fmu/out/obstacle_distance_fused/distances[%d]", i)
+      local distance = TimeseriesView.find(str)
+      if distance == nil then
+          print("No distance data for: " .. str)
+          break
+      end

-         local dist = distance:atTime(tracker_time)
-         if dist ~= nil and dist < 65535 then
-             -- Calculate angle and Cartesian coordinates
-             local angle = angle_offset_value + i * increment_value
-             local y = dist * math.cos(math.rad(angle))
-             local x = dist * math.sin(math.rad(angle))
+      local dist = distance:atTime(tracker_time)
+      if dist ~= nil and dist < 65535 then
+          -- Calculate angle and Cartesian coordinates
+          local angle = angle_offset_value + i * increment_value
+          local y = dist * math.cos(math.rad(angle))
+          local x = dist * math.sin(math.rad(angle))

-             obs_dist_fused_xy:push_back(x, y)
+          obs_dist_fused_xy:push_back(x, y)

-             -- Update minimum distance
-             if dist < min_dist then
-                 min_dist = dist
-             end
-         end
+          -- Update minimum distance
+          if dist < min_dist then
+              min_dist = dist
+          end
+      end

-         i = i + 1
-     end
+      i = i + 1
+  end

-     -- Push minimum distance once after the loop
-     if min_dist < 65535 then
-         obs_dist_min:push_back(tracker_time, min_dist)
-     else
-         print("No valid minimum distance found")
-     end
-     ```
+  -- Push minimum distance once after the loop
+  if min_dist < 65535 then
+      obs_dist_min:push_back(tracker_time, min_dist)
+  else
+      print("No valid minimum distance found")
+  end
+  ```

 4. Enter a name for the script on the top right, and press **Save**.
-   Once saved, the script should appear in the _Active Scripts_ section.
+ Once saved, the script should appear in the _Active Scripts_ section.

 5. Start streaming the data using the approach described in [Plotting uORB Topic Data in Real Time using PlotJuggler](../debug/plotting_realtime_uorb_data.md).
-   You should see the `obstacle_distance_fused_xy` and `obstacle_distance_minimum` timeseries on the left.
+ You should see the `obstacle_distance_fused_xy` and `obstacle_distance_minimum` timeseries on the left.

 Note that you have to press **Save** again to re-enable the scripts after loading a new log file or otherwise clearing data.

@@ -293,7 +293,7 @@ New sensor data is compared to the existing map, and used to update any sections

 The angles in the `obstacle_distance` topic are defined as follows:

-![Obstacle\_Distance Angles](../../assets/computer_vision/collision_prevention/obstacle_distance_def.svg)
+![Obstacle_Distance Angles](../../assets/computer_vision/collision_prevention/obstacle_distance_def.svg)

 The data from rangefinders, rotary lidars, or companion computers, is processed differently, as described below.

@@ -1,6 +1,6 @@
 # Path Planning Interface

-<Badge type="warning" text="Removed" />
+<Badge type="warning" text="Removed PX4 v1.15" />

 :::warning
 The **Path Planning Interface**, along with the features **Obstacle avoidance in Missions** and **Safe Landing** are no longer supported or maintained, and _should not_ be used in any PX4 version.
@@ -96,7 +96,7 @@ It is rare that a system is set up with an entirely synchronised chain!

 IMU 속도와 EV 속도 사이의 오프셋을 확인하여 로그에서 대략적인 지연 추정치를 얻을 수 있습니다.

-![ekf2\_ev\_delay log](../../assets/ekf2/ekf2_ev_delay_tuning.png)
+![ekf2_ev_delay log](../../assets/ekf2/ekf2_ev_delay_tuning.png)

 :::info
 A plot of external data vs. onboard estimate (as above) can be generated using [FlightPlot](../log/flight_log_analysis.md#flightplot) or similar flight analysis tools.
@@ -132,15 +132,15 @@ Perform the following checks to verify that VIO is working properly _before_ you
 이러한 단계가 유지되면, 첫 번째 비행을 시도할 수 있습니다.

 1. Put the vehicle on the ground and start streaming `ODOMETRY` feedback (as above).
-   스로틀 스틱을 내리고 모터를 작동시키십시오.
+  스로틀 스틱을 내리고 모터를 작동시키십시오.

-   이때 왼쪽 스틱을 가장 낮은 위치에 놓고, 위치 제어로 전환합니다.
-   초록불이 켜져야 합니다.
-   녹색 표시등은 위치 피드백을 사용할 수 있고, 위치 제어가 활성화되었음을 알려줍니다.
+  이때 왼쪽 스틱을 가장 낮은 위치에 놓고, 위치 제어로 전환합니다.
+  초록불이 켜져야 합니다.
+  녹색 표시등은 위치 피드백을 사용할 수 있고, 위치 제어가 활성화되었음을 알려줍니다.

 2. 기체가 고도를 유지하도록 스로틀 스틱을 중간(데드 존)에 놓습니다.
-   스틱을 올리면 기준 고도가 증가하고 값을 낮추면 감소합니다.
-   Similarly, the other stick will change the position over the ground.
+  스틱을 올리면 기준 고도가 증가하고 값을 낮추면 감소합니다.
+  Similarly, the other stick will change the position over the ground.

 3. Increase the value of the throttle stick and the vehicle will take off. Move it back to the middle immediately afterwards.