New Crowdin translations - ko

This commit is contained in:
Crowdin Bot
2025-07-06 00:11:18 +00:00
committed by Hamish Willee
parent 389b76bd3a
commit 29a40f37e2
163 changed files with 798 additions and 676 deletions
+5 -5
View File
@@ -9,7 +9,7 @@ Keeping flight logs is a legal requirement in some jurisdictions.
## 비행 콘트롤러에서 로그 다운로드
Logs can be downloaded using [QGroundControl](http://qgroundcontrol.com/): **[Analyze View > Log Download](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/log_download.html)**.
Logs can be downloaded using [QGroundControl](https://qgroundcontrol.com/): **[Analyze View > Log Download](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/log_download.html)**.
![Flight Log Download](../../assets/qgc/analyze/log_download.jpg)
@@ -21,7 +21,7 @@ You can also host a [private Flight Review server](../dev_log/log_encryption.md#
## 로그 분석
Upload the log file to the online [Flight Review](http://logs.px4.io) tool.
Upload the log file to the online [Flight Review](https://logs.px4.io/) tool.
After upload you'll be emailed a link to the analysis page for the log.
[Log Analysis using Flight Review](../log/flight_review.md) explains how to interpret the plots, and can help you to verify/reject the causes of common problems: excessive vibration, poor PID tuning, saturated controllers, imbalanced vehicles, GPS noise, etc.
@@ -38,17 +38,17 @@ For more information see [Settings > MAVLink Settings > MAVLink 2 Logging (PX4 o
## PX4 개발자가 검토할 로그 파일 공유
The [Flight Review](http://logs.px4.io) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../index.md#reporting-bugs-issues).
The [Flight Review](https://logs.px4.io/) log file link can be shared for discussion in the [support forums](../contribute/support.md#forums-and-chat) or a [Github issue](../index.md#reporting-bugs-issues).
## 로그 설정
The logging system is configured by default to collect sensible logs for use with [Flight Review](http://logs.px4.io).
The logging system is configured by default to collect sensible logs for use with [Flight Review](https://logs.px4.io/).
Logging may further be configured using the [SD Logging](../advanced_config/parameter_reference.md#sd-logging) parameters or with a file on the SD card.
Details on configuration can be found in the [logging configuration documentation](../dev_log/logging.md#configuration).
## 주요 링크
- [Flight Review](http://logs.px4.io)
- [Flight Review](https://logs.px4.io/)
- [Log Analysis using Flight Review](../log/flight_review.md)
- [Flight Log Analysis](../dev_log/flight_log_analysis.md)
@@ -62,9 +62,9 @@ PX4의 주요 특징들은 아래와 같습니다.
- Supports many different vehicle frames/types, including: [multicopters](../frames_multicopter/index.md), [fixed-wing aircraft](../frames_plane/index.md) (planes), [VTOLs](../frames_vtol/index.md) (hybrid multicopter/fixed-wing), [ground vehicles](../frames_rover/index.md), and [underwater vehicles](../frames_sub/index.md).
- Great choice of drone components for [flight controller](#flight-controller), [sensors](#sensors), [payloads](#payloads), and other peripherals.
- Flexible and powerful [flight modes](#flight-modes) and [safety features](#safety-settings-failsafe).
- Robust and deep integration with [companion computers](#offboard-companion-computer) and [robotics APIs](../robotics/index.md) such as [ROS 2](../ros2/user_guide.md) and [MAVSDK](http://mavsdk.mavlink.io).
- Robust and deep integration with [companion computers](#offboard-companion-computer) and [robotics APIs](../robotics/index.md) such as [ROS 2](../ros2/user_guide.md) and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html).
PX4 is a core part of a broader drone platform that includes the [QGroundControl](#qgc) ground station, [Pixhawk hardware](https://pixhawk.org/), and [MAVSDK](http://mavsdk.mavlink.io) for integration with companion computers, cameras and other hardware using the MAVLink protocol.
PX4 is a core part of a broader drone platform that includes the [QGroundControl](#qgc) ground station, [Pixhawk hardware](https://pixhawk.org/), and [MAVSDK](https://mavsdk.mavlink.io/main/en/index.html) for integration with companion computers, cameras and other hardware using the MAVLink protocol.
PX4 is supported by the [Dronecode Project](https://www.dronecode.org/).
## Ground Control Stations
@@ -74,9 +74,9 @@ A subset of the products that are known to work with PX4 are listed below.
### QGroundControl {#qgc}
The Dronecode GCS software is called [QGroundControl](http://qgroundcontrol.com/) ("QGC").
The Dronecode GCS software is called [QGroundControl](https://qgroundcontrol.com/) ("QGC").
It runs on Windows, Android, MacOS or Linux hardware, and supports a wide range of screen form factors.
You can download it (for free) from [here](http://qgroundcontrol.com/downloads/).
You can download it (for free) from [here](https://qgroundcontrol.com/downloads/).
![QGC Main Screen](../../assets/concepts/qgc_fly_view.png)
@@ -99,7 +99,6 @@ _PX4_ and _Pixhawk_ have been validated with:
- PPM sum receivers
- S.BUS and S.BUS2 receivers from:
- Futaba
- FrSky S.BUS and PPM models
- TBS Crossfire with SBUS as output protocol
@@ -131,7 +130,7 @@ The receivers we have tested all now appear to be compatible, but it is possible
- Graupner HoTT receivers: SUMD output must connect to a **SPKT/DSM** input (as above).
- PPM-Sum and S.BUS receivers must connect directly to the **RC** ground, power and signal pins.
This is typically labeled: `RC IN`, `RCIN` or `RC`, but has in some FCs has been labeled `PPM RC` or `PPM`.
- PPM receivers that have an individual wire for each channel must connect to the RCIN channel _via_ a PPM encoder [like this one](http://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
- PPM receivers that have an individual wire for each channel must connect to the RCIN channel _via_ a PPM encoder [like this one](https://www.getfpv.com/radios/radio-accessories/holybro-ppm-encoder-module.html) (PPM-Sum receivers use a single signal wire for all channels).
- TBS Crossfire/Express LRS Receivers using [CRSF Telemetry](../telemetry/crsf_telemetry.md) connect via a spare UART.
Flight controllers usually include appropriate cables for connecting common receiver types.