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 up badges refering to main/v116 to just be 116

Browse Source
This commit is contained in:
Hamish Willee 2025-06-04 12:26:35 +10:00
parent c3946ff56f
commit 3a4dc784eb
13 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/dev_log/log_encryption.md
View File

@ -12,7 +12,7 @@ To use it you will need to build firmware with this feature enabled and then upl
:::
::: tip
Log encryption was has been improved in PX4 main (v1.16+) to generate a single encrypted log file that contains both encrypted log data, and an encrypted symmetric key that you can use to decrypt it (provided you can decrypt the symmetric key).
Log encryption was has been improved in PX4 v1.16 to generate a single encrypted log file that contains both encrypted log data, and an encrypted symmetric key that you can use to decrypt it (provided you can decrypt the symmetric key).
In earlier versions the encrypted symmetric key was stored in a separate file.
For more information see the [Log Encryption (PX4 v1.15)](https://docs.px4.io/v1.15/en/dev_log/log_encryption.html).

10
docs/en/flight_controller/kakuteh7-wing.md
View File

@ -1,4 +1,6 @@
# Holybro Kakute H7 V2
# Holybro Kakute H743-Wing
<Badge type="tip" text="PX4 v1.16" />
:::warning
PX4 does not manufacture this (or any) autopilot.
@ -33,9 +35,7 @@ The board can be bought from one of the following shops (for example):
| Buz-, Buz+ | Piezo buzzer | |
| M1 to M14 | Motor signal outputs | |
<a id="bootloader"></a>
## PX4 Bootloader Update
## PX4 Bootloader Update {#bootloader}
The board comes pre-installed with [Betaflight](https://github.com/betaflight/betaflight/wiki).
Before the PX4 firmware can be installed, the _PX4 bootloader_ must be flashed.
@ -52,7 +52,7 @@ make holybro_kakuteh7-wing_default
## Installing PX4 Firmware
::: info
KakuteH7-wing is supported with PX4 master & PX4 v1.16 or newer..
KakuteH7-wing is supported in PX4 v1.16 or newer.
Prior to that release you will need to manually build and install the firmware.
:::

2
docs/en/flight_modes_rover/ackermann.md
View File

@ -135,7 +135,7 @@ The mission is typically created and uploaded with a Ground Control Station (GCS
#### Mission commands
The following commands can be used in missions at time of writing (`main`/planned for `PX4 v1.16+`):
The following commands can be used in missions at time of writing (PX4 v1.16):
| QGC mission item | Command | Description |
| ------------------- | ------------------------------------------------------------ | ------------------------------------------------- |

2
docs/en/flight_modes_rover/differential.md
View File

@ -114,7 +114,7 @@ The mission is typically created and uploaded with a Ground Control Station (GCS
#### Mission commands
The following commands can be used in missions at time of writing (`main`/planned for `PX4 v1.16+`):
The following commands can be used in missions at time of writing (PX4 v1.16):
| QGC mission item | Command | Description |
| ------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------- |

2
docs/en/flight_modes_rover/mecanum.md
View File

@ -139,7 +139,7 @@ The mission is typically created and uploaded with a Ground Control Station (GCS
#### Mission commands
The following commands can be used in missions at time of writing (`main`/planned for `PX4 v1.16+`):
The following commands can be used in missions at time of writing (PX4 v1.16):
| QGC mission item | Command | Description |
| ------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------- |

2
docs/en/frames_rover/ackermann.md
View File

@ -1,6 +1,6 @@
# Ackermann Rovers
<Badge type="tip" text="main (planned for: PX4 v1.16+)" /> <Badge type="warning" text="Experimental" />
<Badge type="tip" text="PX4 v1.16" /> <Badge type="warning" text="Experimental" />
An _Ackermann rover_ controls its direction by pointing the front wheels in the direction of travel — the [Ackermann steering geometry](https://en.wikipedia.org/wiki/Ackermann_steering_geometry) compensates for the fact that wheels on the inside and outside of the turn move at different rates.
This kind of steering is used on most commercial vehicles, including cars, trucks etc.

2
docs/en/frames_rover/differential.md
View File

@ -1,6 +1,6 @@
# Differential Rovers
<Badge type="tip" text="main (planned for: PX4 v1.16+)" /> <Badge type="warning" text="Experimental" />
<Badge type="tip" text="PX4 v1.16" /> <Badge type="warning" text="Experimental" />
A differential rover's motion is controlled using a differential drive mechanism, where the left and right wheel speeds are adjusted independently to achieve the desired forward speed and yaw rate.
Forward motion is achieved by driving both wheels at the same speed in the same direction.

2
docs/en/frames_rover/mecanum.md
View File

@ -1,6 +1,6 @@
# Mecanum Rovers
<Badge type="tip" text="main (planned for: PX4 v1.16+)" /> <Badge type="warning" text="Experimental" />
<Badge type="tip" text="PX4 v1.16" /> <Badge type="warning" text="Experimental" />
A Mecanum rover is a type of mobile robot that uses Mecanum wheels to achieve omnidirectional movement. These wheels are unique because they have rollers mounted at a 45-degree angle around their circumference, allowing the rover to move not only forward and backward but also side-to-side and diagonally without needing to rotate first.
Each wheel is driven by its own motor, and by controlling the speed and direction of each motor, the rover can move in any direction or spin in place.

4
docs/en/middleware/uorb.md
View File

@ -116,9 +116,9 @@ As there are external tools using uORB messages from log files, such as [Flight
## Message Versioning
<Badge type="tip" text="main (planned for: PX4 v1.16+)" />
<Badge type="tip" text="PX4 v1.16" />
Optional message versioning was introduced in the `main` branch (planned for PX4 v1.16+) to make it easier to maintain compatibility between PX4 and ROS 2 versions compiled against different message definitions.
Optional message versioning was introduced PX4 v1.16 to make it easier to maintain compatibility between PX4 and ROS 2 versions compiled against different message definitions.
Versioned messages are designed to remain more stable over time compared to their non-versioned counterparts, as they are intended to be used across multiple releases of PX4 and external systems, ensuring greater compatibility over longer periods.
Versioned messages include an additional field `uint32 MESSAGE_VERSION = x`, where `x` corresponds to the current version of the message.

6
docs/en/ros2/px4_ros2_control_interface.md
View File

@ -341,7 +341,7 @@ The used types also define the compatibility with different vehicle types.
The following sections provide a list of supported setpoint types:
- [GotoSetpointType](#go-to-setpoint-gotosetpointtype): Smooth position and (optionally) heading control
- [FwLateralLongitudinalSetpointType](#fixed-wing-lateral-and-longitudinal-setpoint-fwlaterallongitudinalsetpointtype): Direct control of lateral and longitudinal fixed wing dynamics
- [FwLateralLongitudinalSetpointType](#fixed-wing-lateral-and-longitudinal-setpoint-fwlaterallongitudinalsetpointtype): <Badge type="tip" text="main (planned for: PX4 v1.17)" /> Direct control of lateral and longitudinal fixed wing dynamics
- [DirectActuatorsSetpointType](#direct-actuator-control-setpoint-directactuatorssetpointtype): Direct control of motors and flight surface servo setpoints
:::tip
@ -403,7 +403,7 @@ _goto_setpoint->update(
#### Fixed-Wing Lateral and Longitudinal Setpoint (FwLateralLongitudinalSetpointType)
<Badge type="warning" text="Fixed wing only" />
<Badge type="warning" text="Fixed wing only" /> <Badge type="tip" text="main (planned for: PX4 v1.17)" />
::: info
This setpoint type is supported for fixed-wing vehicles and for VTOLs in fixed-wing mode.
@ -545,7 +545,7 @@ If you want to control an actuator that does not control the vehicle's motion, b
### Controlling a VTOL
<Badge type="warning" text="Experimental" />
<Badge type="tip" text="main (planned for: PX4 v1.17)" /> <Badge type="warning" text="Experimental" />
To control a VTOL in an external flight mode, ensure you're returning the correct setpoint type based on the current flight configuration:

4
docs/en/ros2/px4_ros2_msg_translation_node.md
View File

@ -1,6 +1,6 @@
# PX4 ROS 2 Message Translation Node
<Badge type="tip" text="main (planned for: PX4 v1.16+)" /> <Badge type="warning" text="Experimental" />
<Badge type="tip" text="PX4 v1.16" /> <Badge type="warning" text="Experimental" />
The message translation node allows ROS 2 applications that were compiled against different versions of the PX4 messages to interwork with newer versions of PX4, and vice versa, without having to change either the application or the PX4 side.
@ -207,7 +207,7 @@ Message translations can be either _direct_ or _generic_.
### File Structure
Starting from PX4 v1.16 (main), the PX4-Autopilot `msg/` and `srv/` directories are structured as follows:
Starting from PX4 v1.16, the PX4-Autopilot `msg/` and `srv/` directories are structured as follows:
```
PX4-Autopilot

4
docs/en/ros2/user_guide.md
View File

@ -34,7 +34,7 @@ The generator uses the uORB message definitions in the source tree: [PX4-Autopil
ROS 2 applications need to be built in a workspace that has the _same_ message definitions that were used to create the uXRCE-DDS client module in the PX4 Firmware.
You can include these by cloning the interface package [PX4/px4_msgs](https://github.com/PX4/px4_msgs) into your ROS 2 workspace (branches in the repo correspond to the messages for different PX4 releases).
Starting from PX4 v1.16 (main) in which [message versioning](../middleware/uorb.md#message-versioning) was introduced, ROS2 applications may use a different version of message definitions than those used to build PX4.
Starting from PX4 v1.16, in which [message versioning](../middleware/uorb.md#message-versioning) was introduced, ROS2 applications may use a different version of message definitions than those used to build PX4.
This requires the [ROS 2 Message Translation Node](../ros2/px4_ros2_msg_translation_node.md) to be running to ensure that messages can be converted and exchanged correctly.
Note that the micro XRCE-DDS _agent_ itself has no dependency on client-side code.
@ -367,7 +367,7 @@ accelerometer_integral_dt: 4739
#### (Optional) Starting the Translation Node
<Badge type="tip" text="main (planned for: PX4 v1.16+)" /> <Badge type="tip" /> <Badge type="warning" text="Experimental" />
<Badge type="tip" text="PX4 v1.16" /> <Badge type="warning" text="Experimental" />
This example is built with PX4 and ROS2 versions that use the same message definitions.
If you were to use incompatible [message versions](../middleware/uorb.md#message-versioning) you would need to install and run the [Message Translation Node](./px4_ros2_msg_translation_node.md) as well, before running the example:

2
docs/en/sim_gazebo_gz/worlds.md
View File

@ -75,7 +75,7 @@ World with walls that is designed for testing [collision prevention](../computer
## Moving Platform
<Badge type="tip" text="main (planned for: PX4 v1.16+)" />
<Badge type="tip" text="PX4 v1.16" />
[Empty world](#default) with the addition of a flat moving platform, to simulate drone operations from moving vehicles like ships or trucks. The platform is controlled by a plugin which is included in the world. The platform is at a height of 2m, so place the vehicle on it with: