New Crowdin translations - ko (#24547)

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
+18 -18
View File
@@ -43,13 +43,13 @@ To make sure the vehicle is stable enough for auto-tuning:
2. Take off and <div style="display: inline;" v-if="$frontmatter.frame === 'Multicopter'">hover at 1m above ground in [Altitude mode](../flight_modes_mc/altitude.md) or [Stabilized mode](../flight_modes_mc/manual_stabilized.md)</div><div style="display: inline;" v-else-if="$frontmatter.frame === 'Plane'">fly at cruise speed in [Position mode](../flight_modes_fw/position.md) or [Altitude mode](../flight_modes_fw/altitude.md)</div>.
3. Use the RC transmitter roll stick to perform the following maneuver, tilting the vehicle just a few degrees: _roll left > roll right > center_ (The whole maneuver should take about 3 seconds).
기체는 2번의 진동 이내에서 안정화되어야 합니다.
기체는 2번의 진동 이내에서 안정화되어야 합니다.
4. 각각의 시도에서 더 큰 진폭으로 기울이면서 기동을 반복합니다.
기체가 ~20도에서 2번의 진동 내에서 안정화될 수 있으면 다음 단계로 이동합니다.
기체가 ~20도에서 2번의 진동 내에서 안정화될 수 있으면 다음 단계로 이동합니다.
5. 피치 축에서 동일한 동작을 반복합니다.
As above, start with small angles and confirm that the vehicle can stabilise itself within 2 oscillations before increasing the tilt.
As above, start with small angles and confirm that the vehicle can stabilise itself within 2 oscillations before increasing the tilt.
If the drone can stabilize itself within 2 oscillations it is ready for the [auto-tuning procedure](#auto-tuning-procedure).
@@ -72,35 +72,35 @@ The test steps are:
1. Perform the [pre-tuning test](#pre-tuning-test).
2. Takeoff using RC control <div style="display: inline;" v-if="$frontmatter.frame === 'Multicopter'">in [Altitude mode](../flight_modes_mc/altitude.md).
Hover the vehicle at a safe distance and at a few meters above ground (between 4 and 20m).</div><div v-else-if="$frontmatter.frame === 'Plane'">
Once flying at cruise speed, activate [Hold mode](../flight_modes_fw/hold.md).
This will guide the plane to fly in circle at constant altitude and speed.</div>
Hover the vehicle at a safe distance and at a few meters above ground (between 4 and 20m).</div><div v-else-if="$frontmatter.frame === 'Plane'">
Once flying at cruise speed, activate [Hold mode](../flight_modes_fw/hold.md).
This will guide the plane to fly in circle at constant altitude and speed.</div>
3. Enable autotune.
<div v-if="$frontmatter.frame === 'Plane'">
<div class="tip custom-block"><p class="custom-block-title">TIP</p>
<div v-if="$frontmatter.frame === 'Plane'">
<div class="tip custom-block"><p class="custom-block-title">TIP</p>
If an [Enable/Disable Autotune Switch](#enable-disable-autotune-switch) is configured you can just toggle the switch to the "enabled" position.
If an [Enable/Disable Autotune Switch](#enable-disable-autotune-switch) is configured you can just toggle the switch to the "enabled" position.
</div></div>
</div></div>
1. In QGroundControl, open the menu **Vehicle setup > PID Tuning**:
1. In QGroundControl, open the menu **Vehicle setup > PID Tuning**:
![Tuning Setup > Autotune Enabled](../../assets/qgc/setup/autotune/autotune.png)
![Tuning Setup > Autotune Enabled](../../assets/qgc/setup/autotune/autotune.png)
2. Select either the _Rate Controller_ or _Attitude Controller_ tabs.
2. Select either the _Rate Controller_ or _Attitude Controller_ tabs.
3. Ensure that the **Autotune enabled** button is enabled (this will display the **Autotune** button and remove the manual tuning selectors).
3. Ensure that the **Autotune enabled** button is enabled (this will display the **Autotune** button and remove the manual tuning selectors).
4. Read the warning popup and click on **OK** to start tuning.
4. Read the warning popup and click on **OK** to start tuning.
4. 드론은 먼저 빠른 롤 동작을 수행한 후 피치 및 요 동작을 수행합니다.
The progress is shown in the progress bar, next to the _Autotune_ button.
The progress is shown in the progress bar, next to the _Autotune_ button.
5. <div style="display: inline;" v-if="$frontmatter.frame === 'Multicopter'">Manually land and disarm to apply the new tuning parameters.
Takeoff carefully and manually test that the vehicle is stable.</div><div v-else-if="$frontmatter.frame === 'Plane'">The tuning will be immediately/automatically be applied and tested in flight (by default).
그런 다음, PX4는 4초 테스트를 실행하고 문제가 감지되면 튜닝 작업의 이전 상태로 복원합니다.</div>
Takeoff carefully and manually test that the vehicle is stable.</div><div v-else-if="$frontmatter.frame === 'Plane'">The tuning will be immediately/automatically be applied and tested in flight (by default).
그런 다음, PX4는 4초 테스트를 실행하고 문제가 감지되면 튜닝 작업의 이전 상태로 복원합니다.</div>
:::warning
If any strong oscillations occur, land immediately and follow the instructions in the [Troubleshooting](#troubleshooting) section below.
+46 -46
View File
@@ -448,9 +448,9 @@ Instructions:
4. One motor will start spinning (click **Spin Motor Again** if it stops spinning too quickly to note.)
지오메트리 섹션에서 해당 모터를 선택합니다.
지오메트리 섹션에서 해당 모터를 선택합니다.
![Screenshot showing how to identify/assign motors](../../assets/config/actuators/identify_motors_in_progress.png)
![Screenshot showing how to identify/assign motors](../../assets/config/actuators/identify_motors_in_progress.png)
5. 모든 모터를 할당한 후 도구는 출력에 대한 올바른 모터 매핑을 설정한 다음 종료됩니다.
@@ -467,15 +467,15 @@ To assign an actuator:
1. First assign functions to the outputs that you think are _likely_ to be correct in the _Actuator Outputs_ section.
2. Toggle the **Enable sliders** switch in _Actuator Testing_ section.
3. 테스트하려는 액추에이터의 슬라이더를 이동합니다.
- 모터는 최소 추력 위치로 이동하여야 합니다.
- 서보는 중간 위치 근처로 이동하여야 합니다.
- 모터는 최소 추력 위치로 이동하여야 합니다.
- 서보는 중간 위치 근처로 이동하여야 합니다.
4. 어떤 액츄에이터가 차량에서 움직이는 지 확인하십시오.
This should match the actuator positions for your geometry (the [airframe reference](../airframes/airframe_reference.md) shows motor positions for a number of standard airframes).
- 올바른 액츄에이터가 움직이면 다음 단계로 진행합니다.
- 잘못된 액츄에이터가 움직이면 출력 할당을 변경합니다.
- 아무 것도 움직이지 않으면, 슬라이더를 범위 중간에 늘리고 필요한 경우 더 높입니다.
그 후 아무 것도 움직이지 않으면, 출력이 연결되지 않거나 모터에 전원이 공급되지 않거나 출력 설정에 오류가 있을 수 있습니다.
문제를 해결하여야 합니다("무엇이든"이 움직이는지 확인하기 위하여 다른 액추에이터 출력을 시도할 수 있음).
This should match the actuator positions for your geometry (the [airframe reference](../airframes/airframe_reference.md) shows motor positions for a number of standard airframes).
- 올바른 액츄에이터가 움직이면 다음 단계로 진행합니다.
- 잘못된 액츄에이터가 움직이면 출력 할당을 변경합니다.
- 아무 것도 움직이지 않으면, 슬라이더를 범위 중간에 늘리고 필요한 경우 더 높입니다.
그 후 아무 것도 움직이지 않으면, 출력이 연결되지 않거나 모터에 전원이 공급되지 않거나 출력 설정에 오류가 있을 수 있습니다.
문제를 해결하여야 합니다("무엇이든"이 움직이는지 확인하기 위하여 다른 액추에이터 출력을 시도할 수 있음).
5. 슬라이더를 "무장 해제" 위치로 되돌립니다(모터의 경우 슬라이더 하단, 서보의 경우 슬라이더 중앙).
6. 모든 액추에이터에 대하여 반복합니다.
@@ -501,34 +501,34 @@ Remove propellers!
For each motor:
1. 모터 슬라이더를 아래로 당겨서 아래쪽에 찰칵 소리가 나도록 합니다.
In this position the motor is set to the outputs `disarmed` value.
- 모터가 이 위치에서 회전하지 않는 지 확인하십시오.
- If the motor spins, reduce the corresponding PWM `disarmed` value in the [Actuator Outputs](#actuator-outputs) section to below the level at which it still spins.
In this position the motor is set to the outputs `disarmed` value.
- 모터가 이 위치에서 회전하지 않는 지 확인하십시오.
- If the motor spins, reduce the corresponding PWM `disarmed` value in the [Actuator Outputs](#actuator-outputs) section to below the level at which it still spins.
2. Slowly move the slider up until it snaps to the _minimum_ position.
In this position the motor is set to the outputs `minimum` value.
In this position the motor is set to the outputs `minimum` value.
- 이 위치에서 모터가 매우 느리게 회전하는 지 확인합니다.
- If the motor is not spinning, or spinning too fast you will need to adjust the corresponding PWM `minimum` value in the [Actuator Outputs](#actuator-outputs) such that the motors barely spin.
- 이 위치에서 모터가 매우 느리게 회전하는 지 확인합니다.
- If the motor is not spinning, or spinning too fast you will need to adjust the corresponding PWM `minimum` value in the [Actuator Outputs](#actuator-outputs) such that the motors barely spin.
![PWM Minimum Output](../../assets/config/actuators/pwm_minimum_output.png)
::: info
For DShot output, this is not required.
![PWM Minimum Output](../../assets/config/actuators/pwm_minimum_output.png)
::: info
For DShot output, this is not required.
:::
3. Increase the slider value to a level where you can verify that the motor is spinning in the correct direction and that it would give a positive thrust in the expected direction.
- The expected thrust direction can vary by vehicle type.
For example in multicopters the thrust should always point upwards, while in a fixed-wing vehicle the thrust will push the vehicle forwards.
- For VTOL, thrust should point upwards when the Tilt Servo is at 0 degrees as defined the [Tilt Servo Convention](#tilt-servo-coordinate-system).
Testing of the [Tilt Servo](#tilt-servo-setup) is covered below as well.
- If thrust is in the wrong direction, you may need to [reverse the motors](#reversing-motors).
- The expected thrust direction can vary by vehicle type.
For example in multicopters the thrust should always point upwards, while in a fixed-wing vehicle the thrust will push the vehicle forwards.
- For VTOL, thrust should point upwards when the Tilt Servo is at 0 degrees as defined the [Tilt Servo Convention](#tilt-servo-coordinate-system).
Testing of the [Tilt Servo](#tilt-servo-setup) is covered below as well.
- If thrust is in the wrong direction, you may need to [reverse the motors](#reversing-motors).
4. Increase the slider value to the maximum value, so the motor is spinning quickly.
Reduce the value of the PWM output's `maximum` value just below the default.
Listen to the tone of the motors as you increase the value in small (25us) increments.
The "optimal" maximum value is the value at which you last hear a change in the tone.
Reduce the value of the PWM output's `maximum` value just below the default.
Listen to the tone of the motors as you increase the value in small (25us) increments.
The "optimal" maximum value is the value at which you last hear a change in the tone.
### 조종면 설정
@@ -551,34 +551,34 @@ Control surfaces that move either direction around a neutral point include: aile
To set these up:
1. Set the `Disarmed` value so that the surfaces will stay at neutral position when disarmed.
This is usually around `1500` for PWM servos (near the centre of the servo range).
This is usually around `1500` for PWM servos (near the centre of the servo range).
![Control Surface Disarmed 1500 Setting](../../assets/config/actuators/control_surface_aileron_setup.png)
![Control Surface Disarmed 1500 Setting](../../assets/config/actuators/control_surface_aileron_setup.png)
2. Move the slider for the surface upwards (positive command) and verify that it moves in the direction defined in the [Control Surface Convention](#control-surface-deflection-convention).
- Ailerons, elevons, V-Tails, A-Tails, and other horizontal surfaces should move up.
- Rudders and other "purely vertical" surfaces should move right.
- Ailerons, elevons, V-Tails, A-Tails, and other horizontal surfaces should move up.
- Rudders and other "purely vertical" surfaces should move right.
::: tip
It is important that the slider movement matches the control surface convention, in order to normalize control for different servo mountings (moving the slider up may actually decrease the output value sent to the servo).
::: tip
It is important that the slider movement matches the control surface convention, in order to normalize control for different servo mountings (moving the slider up may actually decrease the output value sent to the servo).
:::
If the control surface moves in the opposite direction, click on the `Rev Range` checkbox to reverse the range.
If the control surface moves in the opposite direction, click on the `Rev Range` checkbox to reverse the range.
3. Move the slider again to the middle and check if the Control Surfaces are aligned in the neutral position of the wing.
- If it is not aligned, you can set the **Trim** value for the control surface.
- If it is not aligned, you can set the **Trim** value for the control surface.
::: info
This is done in the `Trim` setting of the Geometry panel, usually by "trial and error".
![Control Surface Trimming](../../assets/config/actuators/control_surface_trim.png)
::: info
This is done in the `Trim` setting of the Geometry panel, usually by "trial and error".
![Control Surface Trimming](../../assets/config/actuators/control_surface_trim.png)
:::
- After setting the trim for a control surface, move its slider away from the centre, release, and then back into disarmed (middle) position.
Confirm that surface is in the neutral position.
- After setting the trim for a control surface, move its slider away from the centre, release, and then back into disarmed (middle) position.
Confirm that surface is in the neutral position.
:::info
Another way to test without using the sliders would be to set the [`COM_PREARM_MODE`](../advanced_config/parameter_reference.md#COM_PREARM_MODE) parameter to `Always`:
@@ -600,13 +600,13 @@ One approach for setting these up is:
1. Set values `Disarmed` to `1500`, `Min` to `1200`, `Max` to `1700` so that the values are around the centre of the servo range.
2. Move the corresponding slider up and check the control moves and that it is extending (moving away from the disarmed position).
If not, click on the `Rev Range` checkbox to reverse the range.
If not, click on the `Rev Range` checkbox to reverse the range.
3. Enable slider in the disarmed position, them change the value of the `Disarmed` signal until the control is retracted/flush with wing.
This may require that the `Disarmed` value is increased or decreased:
- If the value was decreased towards `Min`, then set `Min` to match `Disarmed`.
- If the value was increased towards `Max`, then set `Max` to match `Disarmed`.
This may require that the `Disarmed` value is increased or decreased:
- If the value was decreased towards `Min`, then set `Min` to match `Disarmed`.
- If the value was increased towards `Max`, then set `Max` to match `Disarmed`.
4. The value that you did _not_ set to match `Disarmed` controls the maximum amount that the control surface can extend.
Set the slider to the top of the control, then change the value (`Max` or `Min`) so that the control surface is fully extended when the slider is at top.
Set the slider to the top of the control, then change the value (`Max` or `Min`) so that the control surface is fully extended when the slider is at top.
:::info Special note for flaps
In some vehicle builds, flaps may be configured such that both flaps are controlled from a single output.
@@ -630,7 +630,7 @@ For each of the tilt servos:
2. Position the slider for the servo in the lowest position, and verify that a positive value increase will point towards the `Angle at Min Tilt` (defined in the Geometry section).
![Tilt Servo Geometry Setup](../../assets/config/actuators/tilt_servo_geometry_config.png)
![Tilt Servo Geometry Setup](../../assets/config/actuators/tilt_servo_geometry_config.png)
3. Position the slider for the servo in the highest position, and verify that positive motor thrust will point towards the `Angle at Max Tilt` (as defined in the Geometry section).
+5 -5
View File
@@ -27,18 +27,18 @@ Before calibration they must be [enabled via the corresponding parameter](../adv
4. Click the **Airspeed** sensor button.
![Airspeed calibration](../../assets/qgc/setup/sensor/sensor_airspeed.jpg)
![Airspeed calibration](../../assets/qgc/setup/sensor/sensor_airspeed.jpg)
5. 센서로 부는 바람을 막으십시오 (예: 손을 컵 모양으로 감쌀 수 있습니다).
피톳 튜브의 구멍을 막지 않도록 주의하십시오.
피톳 튜브의 구멍을 막지 않도록 주의하십시오.
6. Click **OK** to start the calibration.
7. 피톳 튜브의 끝에 입으로 바람을 불어 보정 완료 신호를 보냅니다.
:::tip
Blowing into the tube is also a basic check that the dynamic and static ports are installed correctly.
교체한 센서는 튜브에 바람을 불어 넣을 때 큰 음의 차압을 판독하고 보정이 오류와 함께 중단됩니다.
:::tip
Blowing into the tube is also a basic check that the dynamic and static ports are installed correctly.
교체한 센서는 튜브에 바람을 불어 넣을 때 큰 음의 차압을 판독하고 보정이 오류와 함께 중단됩니다.
:::
+15 -15
View File
@@ -23,9 +23,9 @@ If any external magnetometers are available, it then disables the internal magne
Several types of compass calibration are available:
1. [Complete](#complete-calibration): This calibration is required after installing the autopilot on an airframe for the first time or when the configuration of the vehicle has changed significantly.
It compensates for hard and soft iron effects by estimating an offset and a scale factor for each axis.
It compensates for hard and soft iron effects by estimating an offset and a scale factor for each axis.
2. [Partial](#partial-quick-calibration): This calibration can be performed as a routine when preparing the vehicle for a flight, after changing the payload, or simply when the compass rose seems inaccurate.
This type of calibration only estimates the offsets to compensate for a hard iron effect.
This type of calibration only estimates the offsets to compensate for a hard iron effect.
3. [Large vehicle](#large-vehicle-calibration): This calibration can be performed when the vehicle is too large or heavy to perform a complete calibration. This type of calibration only estimates the offsets to compensate for a hard iron effect.
## 보정 절차
@@ -35,13 +35,13 @@ Several types of compass calibration are available:
Before starting the calibration:
1. 큰 금속 물체등과 같이 자기장이 강한 곳에서 멀리 떨어진 위치를 선택하십시오.
:::tip
Metal is not always obvious! 사무실 테이블 위에서나 (종종 금속 막대 포함) 또는 차량 옆에서 보정하지 마십시오.
철근이 고르지 않게 분포된 콘크리트 슬래브 근처 장소들도 보정에 영향을 미칠 수 있습니다.
:::tip
Metal is not always obvious! 사무실 테이블 위에서나 (종종 금속 막대 포함) 또는 차량 옆에서 보정하지 마십시오.
철근이 고르지 않게 분포된 콘크리트 슬래브 근처 장소들도 보정에 영향을 미칠 수 있습니다.
:::
2. Connect via telemetry radio rather than USB if at all possible.
USB can potentially cause significant magnetic interference.
USB can potentially cause significant magnetic interference.
3. If using an external compass (or a combined GPS/compass module), make sure it is [mounted](../assembly/mount_gps_compass.md) as far as possible from other electronics in order to reduce magnetic interference, and in a _supported orientation_.
### Complete Calibration
@@ -54,10 +54,10 @@ Before starting the calibration:
3. Click the **Compass** sensor button.
![Select Compass calibration PX4](../../assets/qgc/setup/sensor/sensor_compass_select_px4.png)
![Select Compass calibration PX4](../../assets/qgc/setup/sensor/sensor_compass_select_px4.png)
::: info
You should already have set the [Autopilot Orientation](../config/flight_controller_orientation.md). 미리 설정하지 않았다면, 여기에서 설정할 수 있습니다.
::: info
You should already have set the [Autopilot Orientation](../config/flight_controller_orientation.md). 미리 설정하지 않았다면, 여기에서 설정할 수 있습니다.
:::
@@ -65,7 +65,7 @@ Before starting the calibration:
5. 기체를 아래에 표시된 자세로 놓고 그대로 유지해주십시오 메시지가 표시되면(방향 이미지가 노란색으로 변함) 기체를 지정축을 기준으로 한 방향으로 회전시킵니다. 현재 방향에 대해 보정이 완료되면 화면의 그림이 녹색으로 바뀝니다.
![Compass calibration steps on PX4](../../assets/qgc/setup/sensor/sensor_compass_calibrate_px4.png)
![Compass calibration steps on PX4](../../assets/qgc/setup/sensor/sensor_compass_calibrate_px4.png)
6. 드론의 모든 방향에 대해 보정 과정을 반복합니다.
@@ -76,7 +76,7 @@ Once you've calibrated the vehicle in all the positions _QGroundControl_ will di
This calibration is similar to the well-known figure-8 compass calibration done on a smartphone:
1. Hold the vehicle in front of you and randomly perform partial rotations on all its axes.
2-3 oscillations of ~30 degrees in every direction is usually sufficient.
2-3 oscillations of ~30 degrees in every direction is usually sufficient.
2. Wait for the heading estimate to stabilize and verify that the compass rose is pointing to the correct direction (this can take a couple of seconds).
참고:
@@ -94,12 +94,12 @@ This calibration process leverages external knowledge of vehicle's orientation a
1. Ensure GNSS Fix. This is required to find the expected Earth magnetic field in WMM tables.
2. Align the vehicle to face True North.
Be as accurate as possible for best results.
Be as accurate as possible for best results.
3. Open the [QGroundControl MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html) and send the following command:
```sh
commander calibrate mag quick
```
```sh
commander calibrate mag quick
```
참고:
+2 -2
View File
@@ -61,10 +61,10 @@ Next you will need to specify the [vehicle airframe](../config/airframe.md) (and
2. Check **Advanced settings** and select the version from the dropdown list:
- **Standard Version (stable):** The default version (i.e. no need to use advanced settings to install this!)
- **Beta Testing (beta):** A beta/candidate release.
신규 버전 출시 이전에 테스트 할 경우에만 사용할 수 있습니다.
신규 버전 출시 이전에 테스트 할 경우에만 사용할 수 있습니다.
- **Developer Build (master):** The latest build of PX4/PX4-Autopilot _main_ branch.
- **Custom Firmware file...:** A custom firmware file (e.g. [that you have built locally](../dev_setup/building_px4.md)).
사용자 정의 펌웨어 파일을 선택한 경우 다음 단계에서 파일 시스템에서 사용자 정의 펌웨어를 선택하여야 합니다.
사용자 정의 펌웨어 파일을 선택한 경우 다음 단계에서 파일 시스템에서 사용자 정의 펌웨어를 선택하여야 합니다.
그러면 펌웨어 업데이트가 이전과 같이 계속됩니다.
+10 -10
View File
@@ -40,24 +40,24 @@ You can also separately specify channels for mapping a kill switch, return to la
3. Select **"Q" icon > Vehicle Setup > Flight Modes** (sidebar) to open _Flight Modes Setup_.
![Flight modes single-channel](../../assets/qgc/setup/flight_modes/flight_modes_single_channel.jpg)
![Flight modes single-channel](../../assets/qgc/setup/flight_modes/flight_modes_single_channel.jpg)
4. Specify _Flight Mode Settings_:
- Select the **Mode channel** (above this shown as Channel 5, but this will depend on your transmitter configuration).
- Move the transmitter switch (or switches) that you have set up for mode selection through the available positions.
The mode slot matching your current switch position will be highlighted (above this is _Flight Mode 1_).
::: info
While you can set flight modes in any of the 6 slots, only the channels that are mapped to switch positions will be highlighted/used.
- Select the **Mode channel** (above this shown as Channel 5, but this will depend on your transmitter configuration).
- Move the transmitter switch (or switches) that you have set up for mode selection through the available positions.
The mode slot matching your current switch position will be highlighted (above this is _Flight Mode 1_).
::: info
While you can set flight modes in any of the 6 slots, only the channels that are mapped to switch positions will be highlighted/used.
:::
- Select the flight mode that you want triggered for each switch position.
- Select the flight mode that you want triggered for each switch position.
5. Specify _Switch Settings_:
- Select the channels that you want to map to specific actions - e.g.: _Return_ mode, _Kill switch_, _offboard_ mode, etc. (if you have spare switches and channels on your transmitter).
- Select the channels that you want to map to specific actions - e.g.: _Return_ mode, _Kill switch_, _offboard_ mode, etc. (if you have spare switches and channels on your transmitter).
6. Test that the modes are mapped to the right transmitter switches:
- Check the _Channel Monitor_ to confirm that the expected channel is changed by each switch.
- Select each mode switch on your transmitter in turn, and check that the desired flight mode is activated (the text turns yellow on _QGroundControl_ for the active mode).
- Check the _Channel Monitor_ to confirm that the expected channel is changed by each switch.
- Select each mode switch on your transmitter in turn, and check that the desired flight mode is activated (the text turns yellow on _QGroundControl_ for the active mode).
All values are automatically saved as they are changed.
+2 -1
View File
@@ -14,7 +14,7 @@ To use it:
2. Set the vehicle type
3. Set the other values in the **State** or any of the flags under **Conditions**
- The **Intended Mode** corresponds to the commanded mode via RC or GCS (or external script).
The failsafe state machine can override this in case of a failsafe.
The failsafe state machine can override this in case of a failsafe.
4. Check the action under **Output**
5. Check what happens when changing mode or **Move the RC sticks**
6. Play with different settings and conditions!
@@ -30,3 +30,4 @@ make run_failsafe_web_server
<script setup>
import { withBase } from 'vitepress';
</script>