fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-30 07:23:33 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#25483)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-09-11 08:29:25 +10:00
committed by GitHub
co-authored by Crowdin Bot
parent 472e0657b5
commit 2e84e55d93
123 changed files with 2858 additions and 2621 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/dronecan/holybro_h_rtk_zed_f9p_gps.md
+10 -10
View File
@@ -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.
@@ -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)
docs/zh/dronecan/pomegranate_systems_pm.md
+5 -5
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:
docs/zh/dronecan/raccoonlab_power.md
+2 -2
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.