New Crowdin translations - uk (#24548)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-03-19 15:53:22 +11:00
committed by GitHub
parent 6cab668270
commit c77f3887aa
178 changed files with 2398 additions and 2391 deletions

View File

@@ -65,7 +65,7 @@ Set the following parameters in _QGroundControl_ [Vehicle Setup > Parameters](..
- [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT): set to: _Raw data_
![QGC - Set UAVCAN\_SUB\_BAT parameter to raw data](../../assets/hardware/power_module/cuav_can/qgc_set_usavcan_sub_bat.png)
![QGC - Set UAVCAN_SUB_BAT parameter to raw data](../../assets/hardware/power_module/cuav_can/qgc_set_usavcan_sub_bat.png)
## Подальша інформація

View File

@@ -54,7 +54,7 @@ The high-precision PNI RM3100 compass ensures accurate orientation and stability
The Holybro ZED-F9P GPS is connected to the CAN bus using a Pixhawk standard 4 pin JST GH cable.
For more information, refer to the [CAN Wiring](../can/index.md#wiring) instructions.
For dual F9P setups leveraging GPS yaw, connect both F9P CAN connectors to the same bus via a CAN or I2C expansion splitter or [hub](https://holybro.com/products/can-hub?_pos=1&_sid=eeb6b74b2&_ss=r).
For dual F9P setups leveraging GPS yaw, connect both F9P CAN connectors to the same bus via a CAN or I2C expansion splitter or hub.
## Налаштування прошивки
@@ -64,10 +64,10 @@ To update the "AP Periph" firmware to the latest version:
1. [Download the latest binary](https://firmware.ardupilot.org/AP_Periph/latest/HolybroG4_GPS/).
2. Update the firmware using either of the following approaches:
- Using ArduPilot:
1. Install _Ardupilot_ firmware on your flight controller and the Mission Planner GCS on your computer.
2. Update the binary by following the instructions in the [DroneCAN FW Upgrade](https://docs.holybro.com/gps-and-rtk-system/zed-f9p-h-rtk-series/dronecan-fw-upgrade) guide.
- Use a serial-to-can converter (such as the [Zubax Babel](https://github.com/Zubax/canface_cf1?tab=readme-ov-file)) and the [DroneCAN GUI Tool](https://dronecan.github.io/Implementations/Libuavcan/Tutorials/11._Firmware_update/).
- Using ArduPilot:
1. Install _Ardupilot_ firmware on your flight controller and the Mission Planner GCS on your computer.
2. Update the binary by following the instructions in the [DroneCAN FW Upgrade](https://docs.holybro.com/gps-and-rtk-system/zed-f9p-h-rtk-series/dronecan-fw-upgrade) guide.
- Use a serial-to-can converter (such as the [Zubax Babel](https://github.com/Zubax/canface_cf1?tab=readme-ov-file)) and the [DroneCAN GUI Tool](https://dronecan.github.io/Implementations/Libuavcan/Tutorials/11._Firmware_update/).
Remember to change the firmware on the flight controller back to PX4 afterwards.
@@ -88,7 +88,7 @@ DroneCAN configuration in PX4 is explained in more detail in [DroneCAN > Enablin
- For the the single Rover the module should be mounted with the included mast.
- For the Dual ZED-F9P setup (moving baseline), the DroneCAN modules should be placed at least 30cm apart on the airframe and elevated on a mast also.
See the following [mast](https://holybro.com/products/30-antenna-mount?_pos=20&_sid=67b49d76b&_ss=r).
See the following mast.
- F9P module arrow(s) should be pointing forward with respect to the autopilot orientation.
## Dual ZED-F9P DroneCAN Modules For Heading
@@ -98,14 +98,14 @@ In order to use dual ZED-F9P GPS heading in PX4, follow these steps:
1. Open the QGroundControl parameters page.
2. On the left side next to the parameters list, double-click on the _System_ section (this hides the section).
3. Components should be visible on the left panel.
Click on the first `_Component_<ID#>` that maps to the ZED-F9P DroneCAN node (below shown as _Component 124_).
Click on the first `_Component_<ID#>` that maps to the ZED-F9P DroneCAN node (below shown as _Component 124_).
4. Click on the _GPS_ subsection and configure the parameters listed below:
- `GPS_TYPE`: Either set to `17` for moving baseline _base_, or set to `18` to be the moving baseline _rover_.
One F9P MUST be _rover_, and the other MUST be _base_.
- `GPS_AUTO_CONFIG`: set to 1 for both the rover and base
- `GPS_POS_X`, `GPS_POS_Y`, `GPS_POS_Z`: This is the antenna placement, which for the F9P is internal to the module.
This is the local offset (FRD) with respect to the autopilot.
- `GPS_TYPE`: Either set to `17` for moving baseline _base_, or set to `18` to be the moving baseline _rover_.
One F9P MUST be _rover_, and the other MUST be _base_.
- `GPS_AUTO_CONFIG`: set to 1 for both the rover and base
- `GPS_POS_X`, `GPS_POS_Y`, `GPS_POS_Z`: This is the antenna placement, which for the F9P is internal to the module.
This is the local offset (FRD) with respect to the autopilot.
![QGC Setup](../../assets/hardware/gps/holybro_h_rtk_zed_f9p_rover/holybro_f9p_gps_qgc_setup.png)

View File

@@ -45,11 +45,11 @@ Source code and build instructions can be found on [the bitbucket](https://bitbu
1. Enable DroneCAN by setting the [UAVCAN_ENABLE](../advanced_config/parameter_reference.md#UAVCAN_ENABLE) parameter to `2` (Sensors Automatic Config) or `3`.
2. Enable DroneCAN battery monitoring by setting [UAVCAN_SUB_BAT](../advanced_config/parameter_reference.md#UAVCAN_SUB_BAT) to `1` or `2` ( depending on your battery).
3. Set the following module parameters using the [MAVLink console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html):
- Battery capacity in mAh: `battery_capacity_mAh`
- Battery voltage when _full_: `battery_full_V`,
- Battery voltage when _empty_: `battery_empty_V`
- Turn on current integration: `enable_current_track`
- (optional) Turn Off CANbus termination resistor :`enable_can_term`
- Battery capacity in mAh: `battery_capacity_mAh`
- Battery voltage when _full_: `battery_full_V`,
- Battery voltage when _empty_: `battery_empty_V`
- Turn on current integration: `enable_current_track`
- (optional) Turn Off CANbus termination resistor :`enable_can_term`
**Example:** A Power Module with UAVCAN node id `125` connected to a `3S` LiPo with capacity of `5000mAh` can be configured with the following commands:

View File

@@ -7,9 +7,9 @@ CAN power connectors are designed for light unmanned aerial (UAV) and other vehi
There are two types of devices:
1. `CAN-MUX` devices provide power from XT30 connector to CAN.
There are 2 variation of this type of the device with different number of connectors.
There are 2 variation of this type of the device with different number of connectors.
2. `Power connector node` is designed to pass current (up to 60A) to power load and CAN, measure voltage and current on load.
It behaves as Cyphal/DroneCAN node.
It behaves as Cyphal/DroneCAN node.
Please refer to the RaccoonLab docs [CAN Power Connectors](https://docs.raccoonlab.co/guide/pmu/power/) page.

View File

@@ -81,15 +81,15 @@ You can skip this section if there is only one ESC in your setup, because the ES
3. Start the process of ESC auto-enumeration by pressing the **Start Assignment** button, as shown on the screenshot below.
![QGC - DroneCAN ESC auto-enumeration](../../assets/peripherals/esc_qgc/qgc_uavcan_settings.jpg)
![QGC - DroneCAN ESC auto-enumeration](../../assets/peripherals/esc_qgc/qgc_uavcan_settings.jpg)
Ви почуєте звук, що вказує на те, що керування польотом увійшло в режим переліку ESC.
Ви почуєте звук, що вказує на те, що керування польотом увійшло в режим переліку ESC.
4. Manually turn each motor in the correct direction of its rotation (as specified in the [Airframe Reference](../airframes/airframe_reference.md)), starting from the first motor and finishing with the last motor.
Кожного разу, коли ви ввімкнете мотор, ви повинні почути підтвердний сигнал.
Кожного разу, коли ви ввімкнете мотор, ви повинні почути підтвердний сигнал.
::: info
Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration).
::: info
Make sure to turn each of the motors in the correct direction, as the ESC will automatically learn and remember the direction (i.e. motors that spin clockwise during normal operation must also be turned clockwise during enumeration).
:::