fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-11-07 03:31:36 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#25559)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-09-16 08:56:46 +10:00
committed by GitHub
co-authored by Crowdin Bot
parent 5d0bbaabb2
commit 0068fea2f5
35 changed files with 665 additions and 228 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/ros2/px4_ros2_msg_translation_node.md
+2 -2
View File
@@ -65,7 +65,7 @@ The translation node will print a warning if it encounters an unknown topic vers
After making a modification in PX4 to the message definitions and/or translation node code, you will need to rerun the steps above from point 2 to update your ROS workspace accordingly.
:::
### In ROS Applications
### 在ROS 应用中
While developing a ROS 2 application that communicates with PX4, it is not necessary to know the specific version of a message being used.
The message version can be added generically to a topic name like this:
@@ -183,7 +183,7 @@ class MinimalPubSub(Node):
On the PX4 side, the DDS client automatically adds the version suffix if a message definition contains the field `uint32 MESSAGE_VERSION = x`.
:::info
Version 0 of a topic means that no `_v<version>` suffix should be added.
主题版本0意味着不应添加`_v<version>`后缀。
:::
## Development