Skip to content

Commit 96e5862

Browse files
New Crowdin translations - uk (#26056)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
1 parent 98d8090 commit 96e5862

File tree

3 files changed

+15
-2
lines changed

3 files changed

+15
-2
lines changed

docs/uk/config_fw/airspeed_scale_handling.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,13 +78,19 @@ Follow these steps:
7878

7979
1. **Set an Initial Scale**
8080

81-
Use a conservative starting point: set the CAS scale (`ASPD_SCALE_n`) slightly under 1.0 (for example 0.95).
82-
This biases the system toward over-speed rather than under-speed, reducing stall risk.
81+
Set the CAS scale (`ASPD_SCALE_n`) to 1.0 (the default value).
82+
When the scale is at exactly 1.0, PX4 automatically accelerates the learning process during the first 5 minutes of flight, allowing faster convergence to the correct scale value.
8383

8484
2. **Perform a Flight**
8585

8686
After takeoff, place the vehicle in loiter for about 15 minutes to allow the scale estimation to converge.
8787

88+
::: tip
89+
Flying in circles (loiter/hold mode) is important as the scale-validation algorithm requires the aircraft to pass through multiple heading segments (12 segments covering all compass directions).
90+
If these heading segments aren’t completed, PX4 cannot validate the estimated scale.
91+
92+
:::
93+
8894
3. **Check Scale Convergence**
8995

9096
After the flight, review the estimated scale in logs.

docs/uk/flight_modes_fw/mission.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,10 @@ PX4 "приймає" наступні команди місії MAVLink у ре
167167
- [MAV_CMD_OBLIQUE_SURVEY](https://mavlink.io/en/messages/common.html#MAV_CMD_OBLIQUE_SURVEY)
168168
- [MAV_CMD_DO_SET_CAMERA_ZOOM](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_CAMERA_ZOOM)
169169
- [MAV_CMD_DO_SET_CAMERA_FOCUS](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_SET_CAMERA_FOCUS)
170+
- [MAV_CMD_DO_AUTOTUNE_ENABLE](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_AUTOTUNE_ENABLE)
171+
- Disabling autotune by setting `param1` to zero is currently not supported. To abort autotune during a mission, switch to another flight mode.
172+
- Axis selection specified in the MAVLink message is ignored (`param2` must be set to 0).
173+
Instead, the axis bitmask defined by [`FW_AT_AXES`](../advanced_config/parameter_reference.md#FW_AT_AXES) is used.
170174

171175
Визначення GeoFence
172176

docs/uk/flight_modes_mc/mission.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,9 @@ PX4 "приймає" наступні команди місії MAVLink у ре
171171
- [MAV_CMD_NAV_VTOL_TAKEOFF](https://mavlink.io/en/messages/common.html#MAV_CMD_NAV_VTOL_TAKEOFF)
172172
- `MAV_CMD_NAV_VTOL_TAKEOFF.param2` (заголовок переходу) ігнорується.
173173
Замість цього напрямок до наступної маршрутної точки використовується для переходу. <!-- at LEAST until PX4 v1.13: https://github.com/PX4/PX4-Autopilot/issues/12660 -->
174+
- [MAV_CMD_DO_AUTOTUNE_ENABLE](https://mavlink.io/en/messages/common.html#MAV_CMD_DO_AUTOTUNE_ENABLE)
175+
- Disabling autotune by setting `param1` to zero is currently not supported. To abort autotune during a mission, switch to another flight mode.
176+
- Axis selection specified in the MAVLink message is ignored (`param2` must be set to 0) .
174177

175178
Визначення GeoFence
176179

0 commit comments

Comments
 (0)