Mirrors_Framework/PX4-Autopilot
1
0
Fork 0
mirror of https://github.com/PX4/PX4-Autopilot.git synced 2026-05-26 09:26:25 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#26553)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2026-03-05 14:00:49 +11:00
committed by GitHub
parent 102b64f604
commit 62d0620eff
471 changed files with 4073 additions and 5684 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/msg_docs/RaptorStatus.md
+10 -10
View File
@@ -39,16 +39,16 @@ Raptor Status.
## Constants
| 参数名 | 类型 | 值 | 描述 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a href="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
| <a href="#EXIT_REASON_NONE"></a> EXIT_REASON_NONE | `uint8` | 0 | No exit reason => Raptor control step was executed (actuator_motors should have been published) |
| <a href="#EXIT_REASON_NO_ANGULAR_VELOCITY_UPDATE"></a> EXIT_REASON_NO_ANGULAR_VELOCITY_UPDATE | `uint8` | 1 | We synchronize the control onto the input observation with the highest update frequency, which is vehicle_angular_velocity. If there was no update, we do not need to execute the policy again |
| <a href="#EXIT_REASON_NOT_ALL_OBSERVATIONS_SET"></a> EXIT_REASON_NOT_ALL_OBSERVATIONS_SET | `uint8` | 2 | We can not execute the policy if not all observations are available |
| <a href="#EXIT_REASON_ANGULAR_VELOCITY_STALE"></a> EXIT_REASON_ANGULAR_VELOCITY_STALE | `uint8` | 3 | If OBSERVATION_TIMEOUT_ANGULAR_VELOCITY is exceeded, we treat the vehicle_angular_velocity as stale and can not run the policy |
| <a href="#EXIT_REASON_LOCAL_POSITION_STALE"></a> EXIT_REASON_LOCAL_POSITION_STALE | `uint8` | 4 | If OBSERVATION_TIMEOUT_LOCAL_POSITION is exceeded, we treat the vehicle_local_position as stale and can not run the policy |
| <a href="#EXIT_REASON_ATTITUDE_STALE"></a> EXIT_REASON_ATTITUDE_STALE | `uint8` | 5 | If OBSERVATION_TIMEOUT_ATTITUDE is exceeded, we treat the vehicle_attitude as stale and can not run the policy |
| <a href="#EXIT_REASON_EXECUTOR_STATUS_SOURCE_NOT_CONTROL"></a> EXIT_REASON_EXECUTOR_STATUS_SOURCE_NOT_CONTROL | `uint8` | 6 | The executor that runs the policy can run in oversampling mode, where it decides if the policy should be ran based on the timestamp and not based on fixed synchronization onto the vehicle_angular_velocity. In this case the executor can decide to skip running the policy if the interval is too small, in which case this flag is set. |
| 参数名 | 类型 | 值 | 描述 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <a id="#MESSAGE_VERSION"></a> MESSAGE_VERSION | `uint32` | 0 | |
| <a id="#EXIT_REASON_NONE"></a> EXIT_REASON_NONE | `uint8` | 0 | No exit reason => Raptor control step was executed (actuator_motors should have been published) |
| <a id="#EXIT_REASON_NO_ANGULAR_VELOCITY_UPDATE"></a> EXIT_REASON_NO_ANGULAR_VELOCITY_UPDATE | `uint8` | 1 | We synchronize the control onto the input observation with the highest update frequency, which is vehicle_angular_velocity. If there was no update, we do not need to execute the policy again |
| <a id="#EXIT_REASON_NOT_ALL_OBSERVATIONS_SET"></a> EXIT_REASON_NOT_ALL_OBSERVATIONS_SET | `uint8` | 2 | We can not execute the policy if not all observations are available |
| <a id="#EXIT_REASON_ANGULAR_VELOCITY_STALE"></a> EXIT_REASON_ANGULAR_VELOCITY_STALE | `uint8` | 3 | If OBSERVATION_TIMEOUT_ANGULAR_VELOCITY is exceeded, we treat the vehicle_angular_velocity as stale and can not run the policy |
| <a id="#EXIT_REASON_LOCAL_POSITION_STALE"></a> EXIT_REASON_LOCAL_POSITION_STALE | `uint8` | 4 | If OBSERVATION_TIMEOUT_LOCAL_POSITION is exceeded, we treat the vehicle_local_position as stale and can not run the policy |
| <a id="#EXIT_REASON_ATTITUDE_STALE"></a> EXIT_REASON_ATTITUDE_STALE | `uint8` | 5 | If OBSERVATION_TIMEOUT_ATTITUDE is exceeded, we treat the vehicle_attitude as stale and can not run the policy |
| <a id="#EXIT_REASON_EXECUTOR_STATUS_SOURCE_NOT_CONTROL"></a> EXIT_REASON_EXECUTOR_STATUS_SOURCE_NOT_CONTROL | `uint8` | 6 | The executor that runs the policy can run in oversampling mode, where it decides if the policy should be ran based on the timestamp and not based on fixed synchronization onto the vehicle_angular_velocity. In this case the executor can decide to skip running the policy if the interval is too small, in which case this flag is set. |
## Source Message