fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-26 05:43:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#24875)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-05-18 10:57:05 +10:00
committed by GitHub
co-authored by Crowdin Bot
parent 98a37d8e5d
commit e50d5d8567
8 changed files with 47 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/camera/camera_architecture.md
+1 -1
View File
@@ -60,7 +60,7 @@ The driver tracks these intervals, but with the "MAVLink backend" does not need
When the camera would trigger the driver publishes a [CameraTrigger](../msg_docs/CameraTrigger.md) topic (with `feedback` field set to `false`) that causes a [CAMERA_TRIGGER](https://mavlink.io/en/messages/common.html#CAMERA_TRIGGER) MAVLink message to be emitted.
The `camera_feedback` module should then log a corresponding `CameraCapture` topic.
## Camera Commands in Missions
## 任务中的相机命令
PX4 re-emits camera items found in missions as MAVLink commands for all supported [Camera Protocol v2](https://mavlink.io/en/services/camera.html) and [Camera Protocol v1](https://mavlink.io/en/services/camera.html) commands.
The system id of the emitted commands is the same as the ID of the autopilot.