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

Fix wording in MAVLink messages documentation

Browse Source
This commit is contained in:
Hamish Willee 2026-02-18 15:26:08 +11:00 committed by GitHub
parent 7ef57f6262
commit b64ba9efe5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/mavlink/adding_messages.md
View File

@ -5,7 +5,7 @@ This topic explains how to add new MAVLink messages and commands that are expect
## Standard MAVLink Messages
The PX4/PX4-Autopilot source code uses only messages that have been standardized by MAVLink.
That is to say, the standard definitions in [common.xml](https://mavlink.io/en/messages/common.html) in releases, and [development.xml](https://mavlink.io/en/messages/development.html) during development.
That is to say, the definitions in [common.xml](https://mavlink.io/en/messages/common.html) or [development.xml](https://mavlink.io/en/messages/development.html) in releases, and [development.xml](https://mavlink.io/en/messages/development.html) during development.
These messages are present in at least one significant flight stack, and members of other flight stacks have accepted them as a reasonable design that would likely be adopted if the same functionality was required.
::: tip