fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-19 04:53:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#24563)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-03-19 20:59:57 +11:00
committed by GitHub
co-authored by Crowdin Bot
parent bd0a59eb1f
commit d04e6695ac
180 changed files with 2417 additions and 2402 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/flight_modes_mc/follow_me.md
+6 -6
View File
@@ -151,19 +151,19 @@ The follow-me behavior can be configured using the following parameters:
1. Set the [follow distance](#FLW_TGT_DST) to more than 12 meters (8 meters is a "recommended minimum").
There is an inherent position bias (3 ~ 5 meters) between the target and the drone's GPS sensor, which makes the drone follow a 'ghost target' somewhere near the actual target. This is more obvious when the follow distance is very small. We recommend that the follow distance is set to be large enough such that the GPS bias is not significant.
This is more obvious when the follow distance is very small.
We recommend that the follow distance is set to be large enough such that the GPS bias is not significant.
There is an inherent position bias (3 ~ 5 meters) between the target and the drone's GPS sensor, which makes the drone follow a 'ghost target' somewhere near the actual target. This is more obvious when the follow distance is very small. We recommend that the follow distance is set to be large enough such that the GPS bias is not significant.
This is more obvious when the follow distance is very small.
We recommend that the follow distance is set to be large enough such that the GPS bias is not significant.
2. The speed at which you can change the follow angle depends on the [maximum tangential velocity](#FLW_TGT_MAX_VEL) setting.
Experimentation shows that values between `5 m/s` are `10 m/s` are usually suitable.
Experimentation shows that values between `5 m/s` are `10 m/s` are usually suitable.
3. Using the RC Adjustment for height, distance and angle, you can get some creative camera shots.
<lite-youtube videoid="o3DhvCL_M1E" title="YUN0012 almostCinematic"/>
<lite-youtube videoid="o3DhvCL_M1E" title="YUN0012 almostCinematic"/>
This video demonstrates a Google-Earth view perspective, by adjusting the height to around 50 meters (high), distance to 1 meter (close). Which allows a perspective as shot from a satellite.
This video demonstrates a Google-Earth view perspective, by adjusting the height to around 50 meters (high), distance to 1 meter (close). Which allows a perspective as shot from a satellite.
## 已知的问题
docs/zh/flight_modes_mc/mission.md
+13 -13
View File
@@ -31,33 +31,33 @@ At high level all vehicle types behave in the same way when MISSION mode is enga
1. If no mission is stored, or if PX4 has finished executing all mission commands, or if the [mission is not feasible](#mission-feasibility-checks):
- If flying the vehicle will hold.
- If landed the vehicle will "wait".
- If flying the vehicle will hold.
- If landed the vehicle will "wait".
2. If a mission is stored and PX4 is flying it will execute the [mission/flight plan](../flying/missions.md) from the current step.
- A `TAKEOFF` item is treated as a normal waypoint.
- A `TAKEOFF` item is treated as a normal waypoint.
3. If a mission is stored and PX4 is landed:
- PX4 will execute the [mission/flight plan](../flying/missions.md).
- If the mission does not have a `TAKEOFF` item then PX4 will fly the vehicle to the minimum altitude before executing the remainder of the flight plan from the current step.
- PX4 will execute the [mission/flight plan](../flying/missions.md).
- If the mission does not have a `TAKEOFF` item then PX4 will fly the vehicle to the minimum altitude before executing the remainder of the flight plan from the current step.
4. If no mission is stored, or if PX4 has finished executing all mission commands:
- If flying the vehicle will hold.
- If landed the vehicle will "wait".
- If flying the vehicle will hold.
- If landed the vehicle will "wait".
5. You can manually change the current mission command by selecting it in _QGroundControl_.
::: info
If you have a _Jump to item_ command in the mission, moving to another item will **not** reset the loop counter.
One implication is that if you change the current mission command to 1 this will not "fully restart" the mission.
::: info
If you have a _Jump to item_ command in the mission, moving to another item will **not** reset the loop counter.
One implication is that if you change the current mission command to 1 this will not "fully restart" the mission.
:::
6. The mission will only reset when the vehicle is disarmed or when a new mission is uploaded.
:::tip
To automatically disarm the vehicle after it lands, in _QGroundControl_ go to [Vehicle Setup > Safety](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/safety.html), navigate to _Land Mode Settings_ and check the box labeled _Disarm after_.
Enter the time to wait after landing before disarming the vehicle.
:::tip
To automatically disarm the vehicle after it lands, in _QGroundControl_ go to [Vehicle Setup > Safety](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/setup_view/safety.html), navigate to _Land Mode Settings_ and check the box labeled _Disarm after_.
Enter the time to wait after landing before disarming the vehicle.
:::
docs/zh/flight_modes_mc/throw_launch.md
+14 -14
View File
@@ -43,16 +43,16 @@ Also ensure that the propellers do not spin on arming after enabling the feature
In addition:
1. Wear safety equipment.
Eye protection and work gloves are recommended.
Eye protection and work gloves are recommended.
2. Have an easily accessible and tested [kill switch](../config/safety.md#kill-switch).
Remind the operator to be attentive and use the kill switch if needed.
Pilots tend to forget that vehicles are replaceable, but they are not!
Remind the operator to be attentive and use the kill switch if needed.
Pilots tend to forget that vehicles are replaceable, but they are not!
3. Test as much as possible without propellers.
Keep the tools for removing propellers nearby/readily accessible.
Keep the tools for removing propellers nearby/readily accessible.
4. Test this feature with at least two people — one handling the aircraft, the other one the remote control.
5. Keep in mind that after the throw, the exact behavior of the aircraft might be hard to predict as it depends heavily on the way it is thrown.
Sometimes it will stay perfectly in place, but sometimes (e.g., due to extensive roll), it might drift to one side while stabilizing.
Keep a safe distance!
Sometimes it will stay perfectly in place, but sometimes (e.g., due to extensive roll), it might drift to one side while stabilizing.
Keep a safe distance!
On first flight of a new vehicle we recommend performing a [Throw Launch test without propellers](#throw-launch-pretest) (see below).
@@ -65,13 +65,13 @@ The steps for this test are:
1. Dismount the propellers.
2. Set [COM_THROW_EN](../advanced_config/parameter_reference.md#COM_THROW_EN) to `Enabled`.
3. Arm the aircraft.
The engines should not spin, but the vehicle should be armed and keep playing the arming tune.
The engines should not spin, but the vehicle should be armed and keep playing the arming tune.
4. Throw the aircraft about 2m into the air.
If the aircraft is not thrown high enough, the motors will not turn on.
If the aircraft is not thrown high enough, the motors will not turn on.
5. The engines should start just after crossing the apex.
6. Engage the kill switch (ideally a second person operating the RC should do this).
7. Catch the drone.
Remember to use safety gloves!
Remember to use safety gloves!
## Throw Launch
@@ -79,12 +79,12 @@ The steps for a throw launch are:
1. Set [COM_THROW_EN](../advanced_config/parameter_reference.md#COM_THROW_EN) to `Enabled`.
2. Arm the aircraft.
The propellers should not spin, but the vehicle should be armed and keep playing the arming tune.
The propellers should not spin, but the vehicle should be armed and keep playing the arming tune.
3. Throw the aircraft away from you, forward and up (about 2m away and 2m up is recommended).
- The vehicle must reach the speed of [COM_THROW_SPEED](../advanced_config/parameter_reference.md#COM_THROW_SPEED) to detect launch, which by default is set to 5 m/s.
If this speed is not achieved, the motors will not start and the aircraft will fall to the ground.
- Try to avoid excessive rotation during the throw, as this might cause the drone to fail or behave unpredictably.
The exact meaning of "excessive rotation" depends on the platform: for instance, [PX4Vision](../complete_vehicles_mc/px4_vision_kit.md) used for the testing, still managed to recover after 2-3 full rotations.
- The vehicle must reach the speed of [COM_THROW_SPEED](../advanced_config/parameter_reference.md#COM_THROW_SPEED) to detect launch, which by default is set to 5 m/s.
If this speed is not achieved, the motors will not start and the aircraft will fall to the ground.
- Try to avoid excessive rotation during the throw, as this might cause the drone to fail or behave unpredictably.
The exact meaning of "excessive rotation" depends on the platform: for instance, [PX4Vision](../complete_vehicles_mc/px4_vision_kit.md) used for the testing, still managed to recover after 2-3 full rotations.
4. After a downward velocity is detected (the vehicle reaches its apex and starts falling down), the motors should turn on and the vehicle will start flying in the current mode.
## 参数