Skip to content

Commit c3f90af

Browse files
docs(i18n): PX4 guide translations (Crowdin) - ko (#26976)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
1 parent a5e55ff commit c3f90af

18 files changed

+636
-231
lines changed

docs/ko/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,7 @@
172172
- [CUAV V5 nano (FMUv5)](flight_controller/cuav_v5_nano.md)
173173
- [CUAV V5 nano 배선 퀵 스타트](assembly/quick_start_cuav_v5_nano.md)
174174
- [CUAV X25 EVO](flight_controller/cuav_x25-evo.md)
175+
- [CUAV X25 EVO Wiring Quick Start](assembly/quick_start_cuav_x25_evo.md)
175176
- [CUAV X25 SUPER](flight_controller/cuav_x25-super.md)
176177
- [CubePilot Cube Orange+ (CubePilot)](flight_controller/cubepilot_cube_orangeplus.md)
177178
- [CubePilot Cube Orange (CubePilot)](flight_controller/cubepilot_cube_orange.md)

docs/ko/advanced_config/ethernet_setup.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Supported flight controllers include:
2727

2828
- [ARK Electronics ARKV6X](../flight_controller/ark_v6x.md)
2929
- [CUAV Pixhawk V6X](../flight_controller/cuav_pixhawk_v6x.md)
30+
- [CUAV X25 EVO](../flight_controller/cuav_x25-evo.md)
31+
- [CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
3032
- [Holybro Pixhawk 5X](../flight_controller/pixhawk5x.md)
3133
- [Holybro Pixhawk 6X](../flight_controller/pixhawk6x.md)
3234
- [RaccoonLab FMUv6X Autopilot](../flight_controller/raccoonlab_fmu6x.md)

docs/ko/assembly/_assembly.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -410,6 +410,7 @@ They recommend sensors, power systems, and other components from the same manufa
410410
- [CUAV Pixhawk V6X Wiring QuickStart](../assembly/quick_start_cuav_pixhawk_v6x.md)
411411
- [CUAV V5+ Wiring Quickstart](../assembly/quick_start_cuav_v5_plus.md)
412412
- [CUAV V5 nano Wiring Quickstart](../assembly/quick_start_cuav_v5_nano.md)
413+
- [CUAV X25 EVO Wiring Quickstart](../assembly/quick_start_cuav_x25_evo.md)
413414
- [Holybro Pixhawk 6C Wiring Quickstart](../assembly/quick_start_pixhawk6c.md)
414415
- [Holybro Pixhawk 6X Wiring Quickstart](../assembly/quick_start_pixhawk6x.md)
415416
- [Holybro Pixhawk 5X Wiring Quickstart](../assembly/quick_start_pixhawk5x.md)
Lines changed: 154 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,154 @@
1+
# CUAV X25 EVO Wiring Quick Start
2+
3+
:::warning
4+
PX4 does not manufacture this (or any) autopilot.
5+
Contact the [manufacturer](https://store.cuav.net/) for hardware support or compliance issues.
6+
:::
7+
8+
This quick start guide shows how to power the [X25 EVO](../flight_controller/cuav_x25-evo.md) flight controller and connect its most important peripherals.
9+
10+
:::info
11+
The following flight controller models are applicable to this quick start guide.
12+
[CUAV X25 SUPER](../flight_controller/cuav_x25-super.md)
13+
:::
14+
15+
## 배선 개요
16+
17+
아래의 이미지는 주요 센서와 주변 장치(모터 및 서보 출력 제외)들의 연결 방법을 설명합니다.
18+
다음 섹션에서 각 장치에 대하여 자세히 설명합니다.
19+
20+
![wiring](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_01.jpg)
21+
22+
| 인터페이스 | **Function** |
23+
| :----------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
24+
| POWER C1/C2 | Connect the PMU2 Lite to this port; this port is used for connecting the DroneCAN power module |
25+
| M1 ~ M16 | PWM signal output ports, usable for controlling motors or servos; support 3.3V/5V PWM configuration |
26+
| RC IN | Connect remote controller receivers with one-way protocols (e.g., SBUS/DSM/PPM). Note: ELRS/CRSF receivers should be connected to any serial port, not RC IN |
27+
| RSSI | For connecting signal strength feedback modules |
28+
| GPS&SAFETY | Connect Neo-series GPS or C-RTK-series RTK; this port includes interfaces for GPS, safety switch, and buzzer |
29+
| GPS2 | Usable for connecting additional GPS/RTK modules |
30+
| DEBUG (DSU) | For FMU chip debugging and reading debug device information; with ArduPilot firmware, it can be configured for other serial port functions |
31+
| ADC3V3 | For analog level signal detection; the maximum detectable level signal is 3.3V |
32+
| ADC6V6 | For analog level signal detection; the maximum detectable level signal is 6.6V (PX4 is not supported.) |
33+
| TF CARD | Insert an SD card here to enable log storage functionality |
34+
| ETH | Ethernet port, usable for connecting Ethernet devices such as companion computers |
35+
| I2C1/2/3 | Connect external I2C devices (e.g., external compasses) for communication between the controller and I2C devices |
36+
| TELEM1/TELEM2 | Connect telemetry modules (for data transmission) to enable MAVLINK data interaction |
37+
| CAN1/2 | For communication between the controller and DroneCAN devices (e.g., connecting NEO4 SE GPS) |
38+
| TYPE C | USB port of the controller, usable for connecting to the ground station, flashing firmware, and other operations |
39+
| SPI6 | SPI port for external expansion; generally not used |
40+
41+
## Vehicle Front
42+
43+
:::info
44+
If the controller cannot be mounted in the recommended/default orientation (e.g. due to space constraints) you will need to configure the autopilot software with the orientation that you actually used: [Flight Controller Orientation](../config/flight_controller_orientation.md).
45+
:::
46+
47+
![front](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_02.jpg)
48+
49+
## GPS + 나침반 + 부저 + 안전 스위치 + LED
50+
51+
We recommend using a CAN GPS/RTK (such as [Neo 4SE](https://store.cuav.net/shop/cuav-neo-4-se-gps-module/)); simply connect it to the **CAN 1** or **CAN 2** port.
52+
53+
You can also use a standard GPS/RTK module(such as [NEO3 GPS](https://store.cuav.net/shop/neo-3/) (10-pin connector)) by connecting it to the **GPS&SAFETY** port.
54+
Most commonly used GPS modules today integrate GPS, compass, safety switch, buzzer, and LED status light.
55+
56+
If you need to use assisted GPS, connect to the **GPS2** port.
57+
58+
The GPS/compass should be [mounted on the frame](../assembly/mount_gps_compass.md) as far away from other electronics as possible (separating the compass from other electronics will reduce interference), with the direction markings towards the front of the vehicle (the arrow on the NEO GPS should match the arrow on the flight controller).
59+
60+
![GPS](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_03.jpg)
61+
62+
:::info
63+
The GPS module's integrated safety switch is enabled _by default_ (when enabled, PX4 will not let you arm the vehicle).
64+
To disable the safety, press and hold the safety switch for 1 second.
65+
안전 스위치를 다시 눌러 안전 장치를 활성화하고 기체 시동을 끌 수 있습니다.
66+
조종기나 지상국 프로그램에서 기체 시동을 끌 수 없는 상황에서 유용합니다.
67+
:::
68+
69+
## 무선 조종
70+
71+
A remote control (RC) radio system is required if you want to _manually_ control your vehicle (PX4 does not require a radio system for autonomous flight modes).
72+
73+
You will need to [select a compatible transmitter/receiver](../getting_started/rc_transmitter_receiver.md) and then _bind_ them so that they communicate (read the instructions that come with your specific transmitter/receiver).
74+
75+
Connection methods vary by remote controller and receiver type:
76+
77+
### Android Remote Controllers
78+
79+
Take the H16 as an example:
80+
81+
![H16 control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_04.jpg)
82+
83+
Connect **TELEM1/TELEM2** to the UART0 port of the H16 remote controller, and link the H16’s SBUS pin to the **RC IN** port.
84+
85+
### SBUS/DSM/PPM Protocol Receivers
86+
87+
![SBUS/DSM/PPM control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_05.jpg)
88+
89+
Use wires to connect the receiver to the **RC IN** port at the rear of the controller.
90+
91+
### ELRS/CRSF Receivers
92+
93+
![ELRS/CRSF control](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_06.jpg)
94+
95+
Connect the [ELRS/CRSF](../telemetry/crsf_telemetry.md) receiver to any UART serial port of the X25 EVO (e.g., **TELEM2**).
96+
97+
## 전원
98+
99+
The X25 EVO comes standard with the PMU2 Lite power module, which supports 20–70V input and can measure a maximum current of 220A.
100+
It can be directly connected to the **Power C1/C2** port of the X25 EVO and is plug-and-play (no configuration required).
101+
102+
![Power](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_07.png)
103+
104+
## Telemetry (Radio) System
105+
106+
[Telemetry system](../telemetry/index.md) allows you to communicate with the unmanned system via ground station software, enabling you to monitor and control the UAV’s status during flight. Connect the on-board unit of the telemetry system to the **TELEM1** or **TELEM2** port.
107+
108+
You can also purchase telemetry radios from the [CUAV store](https://store.cuav.net/uav-telemetry-module/).
109+
110+
![Telemetry system](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_04.jpg)
111+
112+
## SD 카드
113+
114+
SD cards are highly recommended as they are required for [recording and analyzing flight details](../getting_started/flight_reporting.md), running tasks and using UAVCAN bus hardware.
115+
An SD card is already installed on X25 EVO when it leaves the factory.
116+
117+
:::tip
118+
For more information see [Basic Concepts > SD Cards (Removable Memory)](../getting_started/px4_basic_concepts.md#sd-cards-removable-memory).
119+
:::
120+
121+
## Motors/Servo
122+
123+
Motors/servos are connected to the **M1~M16** ports in the order specified for your vehicle in the [Airframe Reference](../airframes/airframe_reference.md).
124+
125+
![Motors](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_08.jpg)
126+
127+
## Servo Power Supply
128+
129+
The X25 EVO does not supply power to servos. If you need to power servos:
130+
131+
1. Connect a BEC to the positive and negative terminals of any column among **M1 ~ M16** (the positive and negative terminals of **M1 ~ M16** are interconnected).
132+
2. Then connect the servos to the same column.
133+
134+
![servo power supply](../../assets/flight_controller/cuav_x25-evo/x25_evo_quickstart_09.jpg)
135+
136+
:::info
137+
The power rail voltage must be appropriate for the servo being used!
138+
:::
139+
140+
## 기타 주변 장치
141+
142+
The wiring and configuration of optional/less common components is covered within the topics for individual [peripherals](../peripherals/index.md).
143+
144+
## 설정
145+
146+
General configuration information is covered in: [Autopilot Configuration](../config/index.md).
147+
148+
QuadPlane-specific configuration is covered here: [QuadPlane VTOL Configuration](../config_vtol/vtol_quad_configuration.md)
149+
150+
## 추가 정보
151+
152+
- [CUAV Docs](https://doc.cuav.net/) (CUAV)
153+
- [X25 EVO](../flight_controller/cuav_x25-evo.md) (PX4 Doc Overview page)
154+
- [X25 SUPER](../flight_controller/cuav_x25-super.md) (PX4 Doc Overview page)

docs/ko/config/actuators.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ The fields are:
176176

177177
#### Flap Scale and Spoiler Scale Configuration
178178

179-
"Flap-control" and "Spoiler-control" are aerodynamic configurations that can either be commanded manually by the pilot (using RC, say), or are set automatically by the controller.
179+
"Flap-control" and "Spoiler-control" are aerodynamic configurations that can either be commanded manually by the pilot (using RC or a Joystick, say) (see [Flaps and Spoiler Control with Manual Control](#flaps-and-spoiler-control-with-manual-control)), or are set automatically by the controller.
180180
For example, a pilot or the landing system might engage "Spoiler-control" in order to reduce the airspeed before landing.
181181

182182
The configurations are an _abstract_ way for the controller to tell the allocator how much it should adjust the aerodynamic properties of the wings relative to the "full flaps" or "full spoiler" configuration (between `[0,1]`, where "1" indicates the full range).
@@ -199,6 +199,20 @@ In the following example, the vehicle has two ailerons, one elevator, one rudder
199199
These are the elevator deflections added to compensate for the pitching moments generated by the flaps and spoiler actuators.
200200
In the case here the elevator would be deflected 0.3 up when the flaps are fully deployed to counteract the pitching down moment caused by the flaps.
201201

202+
#### Flaps and Spoiler Control with Manual Control
203+
204+
The preferred method to manually actuate spoilers and flaps is to map a manual control switch to an `AUX` output (see [Generic Actuator Control with RC](#generic-actuator-control-with-rc)), and then map that AUX output to the flap or spoiler function using [FW_FLAPS_MAN](../advanced_config/parameter_reference.md#FW_FLAPS_MAN) or [FW_SPOILERS_MAN](../advanced_config/parameter_reference.md#FW_SPOILERS_MAN).
205+
The source for the manual control can be RC or MAVLink.
206+
207+
:::warning
208+
The following method is not recommended, and will be removed in a future release.
209+
If using it you should migrate to using the AUX-based method.
210+
211+
It is also possible to define a flaps channel directly on the RC using [RC_MAP_FLAPS](../advanced_config/parameter_reference.md#RC_MAP_FLAPS).
212+
This channel can also be used to control the spoilers by setting [FW_SPOILERS_MAN](../advanced_config/parameter_reference.md#FW_SPOILERS_MAN) to `Flaps channel`.
213+
This method is not possible when the source for the manual control is MAVLink.
214+
:::
215+
202216
#### 액추에이터 롤, 피치 및 요 스케일링
203217

204218
:::info

0 commit comments

Comments
 (0)