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

docs: auto-sync metadata [skip ci]

Browse Source 
Co-Authored-By: PX4 BuildBot <bot@px4.io>
This commit is contained in:
PX4BuildBot
2026-02-11 22:43:01 +00:00
parent 01b348c86b
commit 36b5e1e1bb
374 changed files with 12147 additions and 1765 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/peripherals/gripper.md
-1
View File
@@ -72,7 +72,6 @@ To set the actuation timeout:
There are two easy ways to open and close the gripper.
While the drone is on a bench and the propellers are removed:
- Run the `payload_deliverer` test in the QGC [MAVLink Shell](../debug/mavlink_shell.md):
```sh
docs/en/peripherals/mavlink_peripherals.md
-1
View File
@@ -28,7 +28,6 @@ The parameters for each instance are:
For more information see [Serial Port Configuration](../peripherals/serial_configuration.md).
- <a id="MAV_X_MODE"></a>[MAV_X_MODE](../advanced_config/parameter_reference.md#MAV_0_MODE) - Specify the telemetry mode/target (the set of messages to stream for the current instance and their rate).
The default values are:
- _Normal_: Standard set of messages for a GCS.
- _Custom_ or _Magic_: Nothing (in the default PX4 implementation).
Modes may be used for testing when developing a new mode.
docs/en/peripherals/remote_id.md
+1 -2
View File
@@ -165,7 +165,6 @@ PX4 v1.14 streams these messages by default (in streaming modes: normal, onboard
- [OPEN_DRONE_ID_LOCATION](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_LOCATION) (1 Hz) - UAV location, altitude, direction, and speed.
- [OPEN_DRONE_ID_SYSTEM](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_SYSTEM) (1 Hz) Operator location/altitude, multiple aircraft information (group/swarm, if applicable), full timestamp and possible category/class information.
- Implementation assumes operator is located at vehicle home position (does not yet support getting operator position from GCS).
This is believed to be compliant for broadcast-only Remote IDs.
@@ -243,7 +242,7 @@ If the Remote ID CAN node is present and the messages are not being received, th
2. Navigate to the [Application settings](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/settings_view/general.html): **Application Settings > General > Miscellaneous**.
3. Select `Enable Remote ID`.
The Remote ID tab should appear.
::: info
If this option is not present you may be in a very recent version of QGC.
In that case, open the view at: **Application Settings > Remote ID**.
docs/en/peripherals/serial_configuration.md
-1
View File
@@ -106,7 +106,6 @@ The following ports are commonly mapped to specific functions on all boards:
This is configured by default as a MAVLink port the onboard profile (for companion computers).
The configuration for MAVLink is unique to this port (it doesn't use the `MAV_X_CONFIG` parameters).
- [SYS_USB_AUTO](../advanced_config/parameter_reference.md#SYS_USB_AUTO) sets whether the port is set to no partiular protocol, autodetects the protocol, or sets the comms link to MAVLink.
- [USB_MAV_MODE](../advanced_config/parameter_reference.md#USB_MAV_MODE) sets the MAVLink profile that is used if MAVLink is set or detected.