From bf41daa62d56180c483b0d0fe9febf2745f6f696 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 6 May 2026 09:28:46 +1000 Subject: [PATCH 1/6] New translations common.md (Korean) [ci skip] --- ko/messages/common.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/ko/messages/common.md b/ko/messages/common.md index 959f56eef..421d946f2 100644 --- a/ko/messages/common.md +++ b/ko/messages/common.md @@ -5999,15 +5999,16 @@ See https://mavlink.io/en/services/standard_modes.html Source for [GLOBAL_POSITION](#GLOBAL_POSITION) measurement or estimate. -| Value | Name | Description | -| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 0 | [GLOBAL_POSITION_SRC_UNKNOWN](#GLOBAL_POSITION_SRC_UNKNOWN) | Source is unknown or not one of the listed types. | -| 1 | [GLOBAL_POSITION_SRC_GNSS](#GLOBAL_POSITION_SRC_GNSS) | Global Navigation Satellite System (e.g.: GPS, Galileo, Glonass, BeiDou). | -| 2 | [GLOBAL_POSITION_SRC_VISION](#GLOBAL_POSITION_SRC_VISION) | Vision system (e.g.: map matching). | -| 3 | [GLOBAL_POSITION_SRC_PSEUDOLITES](#GLOBAL_POSITION_SRC_PSEUDOLITES) | A pseudo-satellite system using transceiver beacons to perform GNSS-like positioning. | -| 4 | [GLOBAL_POSITION_SRC_TERRAIN](#GLOBAL_POSITION_SRC_TERRAIN) | Terrain referenced navigation. | -| 5 | [GLOBAL_POSITION_SRC_MAGNETIC](#GLOBAL_POSITION_SRC_MAGNETIC) | Magnetic positioning. | -| 6 | [GLOBAL_POSITION_SRC_ESTIMATOR](#GLOBAL_POSITION_SRC_ESTIMATOR) | Estimated position based on various sensors (eg. a Kalman Filter). | +| Value | Name | Description | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0 | [GLOBAL_POSITION_SRC_UNKNOWN](#GLOBAL_POSITION_SRC_UNKNOWN) | Source is unknown or not one of the listed types. | +| 1 | [GLOBAL_POSITION_SRC_GNSS](#GLOBAL_POSITION_SRC_GNSS) | Global Navigation Satellite System (e.g.: GPS, Galileo, Glonass, BeiDou). | +| 2 | [GLOBAL_POSITION_SRC_VISION](#GLOBAL_POSITION_SRC_VISION) | Vision system (e.g.: map matching). | +| 3 | [GLOBAL_POSITION_SRC_PSEUDOLITES](#GLOBAL_POSITION_SRC_PSEUDOLITES) | A pseudo-satellite system using transceiver beacons to perform GNSS-like positioning. | +| 4 | [GLOBAL_POSITION_SRC_TERRAIN](#GLOBAL_POSITION_SRC_TERRAIN) | Terrain referenced navigation. | +| 5 | [GLOBAL_POSITION_SRC_MAGNETIC](#GLOBAL_POSITION_SRC_MAGNETIC) | Magnetic positioning. | +| 6 | [GLOBAL_POSITION_SRC_ESTIMATOR](#GLOBAL_POSITION_SRC_ESTIMATOR) | Estimated position based on various sensors (eg. a Kalman Filter). | +| 7 | [GLOBAL_POSITION_SRC_LEO](#GLOBAL_POSITION_SRC_LEO) | Low Earth Orbit satellite-based positioning (e.g.: Starlink, Xona PULSAR). | ### GLOBAL_POSITION_FLAGS {#GLOBAL_POSITION_FLAGS} From 2e208387029d1296d61ec442512eb5f8a6cf011b Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Wed, 6 May 2026 09:30:42 +1000 Subject: [PATCH 2/6] New translations common.md (Chinese Simplified) [ci skip] --- zh/messages/common.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/zh/messages/common.md b/zh/messages/common.md index 1929f8e23..3a3b7b214 100644 --- a/zh/messages/common.md +++ b/zh/messages/common.md @@ -5999,15 +5999,16 @@ See https://mavlink.io/en/services/standard_modes.html Source for [GLOBAL_POSITION](#GLOBAL_POSITION) measurement or estimate. -| 值 | Name | 描述 | -| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 0 | [GLOBAL_POSITION_SRC_UNKNOWN](#GLOBAL_POSITION_SRC_UNKNOWN) | Source is unknown or not one of the listed types. | -| 1 | [GLOBAL_POSITION_SRC_GNSS](#GLOBAL_POSITION_SRC_GNSS) | Global Navigation Satellite System (e.g.: GPS, Galileo, Glonass, BeiDou). | -| 2 | [GLOBAL_POSITION_SRC_VISION](#GLOBAL_POSITION_SRC_VISION) | Vision system (e.g.: map matching). | -| 3 | [GLOBAL_POSITION_SRC_PSEUDOLITES](#GLOBAL_POSITION_SRC_PSEUDOLITES) | A pseudo-satellite system using transceiver beacons to perform GNSS-like positioning. | -| 4 | [GLOBAL_POSITION_SRC_TERRAIN](#GLOBAL_POSITION_SRC_TERRAIN) | Terrain referenced navigation. | -| 5 | [GLOBAL_POSITION_SRC_MAGNETIC](#GLOBAL_POSITION_SRC_MAGNETIC) | Magnetic positioning. | -| 6 | [GLOBAL_POSITION_SRC_ESTIMATOR](#GLOBAL_POSITION_SRC_ESTIMATOR) | Estimated position based on various sensors (eg. a Kalman Filter). | +| 值 | Name | 描述 | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 0 | [GLOBAL_POSITION_SRC_UNKNOWN](#GLOBAL_POSITION_SRC_UNKNOWN) | Source is unknown or not one of the listed types. | +| 1 | [GLOBAL_POSITION_SRC_GNSS](#GLOBAL_POSITION_SRC_GNSS) | Global Navigation Satellite System (e.g.: GPS, Galileo, Glonass, BeiDou). | +| 2 | [GLOBAL_POSITION_SRC_VISION](#GLOBAL_POSITION_SRC_VISION) | Vision system (e.g.: map matching). | +| 3 | [GLOBAL_POSITION_SRC_PSEUDOLITES](#GLOBAL_POSITION_SRC_PSEUDOLITES) | A pseudo-satellite system using transceiver beacons to perform GNSS-like positioning. | +| 4 | [GLOBAL_POSITION_SRC_TERRAIN](#GLOBAL_POSITION_SRC_TERRAIN) | Terrain referenced navigation. | +| 5 | [GLOBAL_POSITION_SRC_MAGNETIC](#GLOBAL_POSITION_SRC_MAGNETIC) | Magnetic positioning. | +| 6 | [GLOBAL_POSITION_SRC_ESTIMATOR](#GLOBAL_POSITION_SRC_ESTIMATOR) | Estimated position based on various sensors (eg. a Kalman Filter). | +| 7 | [GLOBAL_POSITION_SRC_LEO](#GLOBAL_POSITION_SRC_LEO) | Low Earth Orbit satellite-based positioning (e.g.: Starlink, Xona PULSAR). | ### GLOBAL_POSITION_FLAGS {#GLOBAL_POSITION_FLAGS} From 28bad7993d5c1f4e34581b66388c75ad36cb30af Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Thu, 7 May 2026 12:14:41 +1000 Subject: [PATCH 3/6] New translations common.md (Korean) [ci skip] --- ko/messages/common.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/ko/messages/common.md b/ko/messages/common.md index 421d946f2..3aa1fa515 100644 --- a/ko/messages/common.md +++ b/ko/messages/common.md @@ -2156,7 +2156,7 @@ The position must be set automatically by the system during the takeoff, and may The global and local positions encode the position in the respective coordinate frames, while the q parameter encodes the orientation of the surface. Under normal conditions it describes the heading and terrain slope, which can be used by the aircraft to adjust the approach. The approach 3D vector describes the point to which the system should fly in normal flight mode and then perform a landing sequence along the vector. -Note: this message can be requested by sending the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) with param1=242 (or the deprecated [MAV_CMD_GET_HOME_POSITION](#MAV_CMD_GET_HOME_POSITION) command). +Note: this message can be requested by sending the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) with param1=242. | Field Name | Type | Units | Description | | ---------------------------------------------------------------------------------------------- | ---------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -2203,7 +2203,6 @@ Note: the current home position may be emitted in a [HOME_POSITION](#HOME_POSITI The interval between messages for a particular MAVLink message ID. This message is sent in response to the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) command with param1=244 (this message) and param2=message_id (the id of the message for which the interval is required). -It may also be sent in response to [MAV_CMD_GET_MESSAGE_INTERVAL](#MAV_CMD_GET_MESSAGE_INTERVAL). This interface replaces [DATA_STREAM](#DATA_STREAM). | Field Name | Type | Units | Description | @@ -2941,7 +2940,13 @@ General status information of an UAVCAN node. Please refer to the definition of ### UAVCAN_NODE_INFO (311) {#UAVCAN_NODE_INFO} -General information describing a particular UAVCAN node. Please refer to the definition of the UAVCAN service "uavcan.protocol.GetNodeInfo" for the background information. This message should be emitted by the system whenever a new node appears online, or an existing node reboots. Additionally, it can be emitted upon request from the other end of the MAVLink channel (see [MAV_CMD_UAVCAN_GET_NODE_INFO](#MAV_CMD_UAVCAN_GET_NODE_INFO)). It is also not prohibited to emit this message unconditionally at a low frequency. The UAVCAN specification is available at http://uavcan.org. +General information describing a particular UAVCAN node. + +Please refer to the definition of the UAVCAN service "uavcan.protocol.GetNodeInfo" for the background information. +This message should be emitted by the system whenever a new node appears online, or an existing node reboots. +The message may also be explicitly requested using [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE). +It is also not prohibited to emit this message unconditionally at a low frequency. +The DroneCAN specification is available at https://dronecan.github.io/Specification/1._Introduction/. | Field Name | Type | Units | Description | | ---------------------------------------------------------- | ------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -8313,7 +8318,9 @@ Rally point. You can have multiple rally points defined. | 6 (Longitude) | Longitude | | | 7 (Altitude) | Altitude | m | -### MAV_CMD_UAVCAN_GET_NODE_INFO (5200) {#MAV_CMD_UAVCAN_GET_NODE_INFO} +### MAV_CMD_UAVCAN_GET_NODE_INFO (5200) — [SUP] {#MAV_CMD_UAVCAN_GET_NODE_INFO} + +**SUPERSEDED:** Replaced By [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) (2026-05) Commands the vehicle to respond with a sequence of messages [UAVCAN_NODE_INFO](#UAVCAN_NODE_INFO), one message per every UAVCAN node that is online. Note that some of the response messages can be lost, which the receiver can detect easily by checking whether every received [UAVCAN_NODE_STATUS](#UAVCAN_NODE_STATUS) has a matching message [UAVCAN_NODE_INFO](#UAVCAN_NODE_INFO) received earlier; if not, this command should be sent again in order to request re-transmission of the node information messages. From b5fc2817079ae840afcca9a756806a35ffca5ac9 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Thu, 7 May 2026 12:16:38 +1000 Subject: [PATCH 4/6] New translations common.md (Chinese Simplified) [ci skip] --- zh/messages/common.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/zh/messages/common.md b/zh/messages/common.md index 3a3b7b214..188f1872c 100644 --- a/zh/messages/common.md +++ b/zh/messages/common.md @@ -2156,7 +2156,7 @@ The position must be set automatically by the system during the takeoff, and may The global and local positions encode the position in the respective coordinate frames, while the q parameter encodes the orientation of the surface. Under normal conditions it describes the heading and terrain slope, which can be used by the aircraft to adjust the approach. The approach 3D vector describes the point to which the system should fly in normal flight mode and then perform a landing sequence along the vector. -Note: this message can be requested by sending the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) with param1=242 (or the deprecated [MAV_CMD_GET_HOME_POSITION](#MAV_CMD_GET_HOME_POSITION) command). +Note: this message can be requested by sending the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) with param1=242. | Field Name | Type | Units | 描述 | | ---------------------------------------------------------------------------------------------- | ---------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -2203,7 +2203,6 @@ Note: the current home position may be emitted in a [HOME_POSITION](#HOME_POSITI The interval between messages for a particular MAVLink message ID. This message is sent in response to the [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) command with param1=244 (this message) and param2=message_id (the id of the message for which the interval is required). -It may also be sent in response to [MAV_CMD_GET_MESSAGE_INTERVAL](#MAV_CMD_GET_MESSAGE_INTERVAL). This interface replaces [DATA_STREAM](#DATA_STREAM). | Field Name | Type | Units | 描述 | @@ -2941,7 +2940,13 @@ General status information of an UAVCAN node. Please refer to the definition of ### UAVCAN_NODE_INFO (311) {#UAVCAN_NODE_INFO} -General information describing a particular UAVCAN node. Please refer to the definition of the UAVCAN service "uavcan.protocol.GetNodeInfo" for the background information. This message should be emitted by the system whenever a new node appears online, or an existing node reboots. Additionally, it can be emitted upon request from the other end of the MAVLink channel (see [MAV_CMD_UAVCAN_GET_NODE_INFO](#MAV_CMD_UAVCAN_GET_NODE_INFO)). It is also not prohibited to emit this message unconditionally at a low frequency. The UAVCAN specification is available at http://uavcan.org. +General information describing a particular UAVCAN node. + +Please refer to the definition of the UAVCAN service "uavcan.protocol.GetNodeInfo" for the background information. +This message should be emitted by the system whenever a new node appears online, or an existing node reboots. +The message may also be explicitly requested using [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE). +It is also not prohibited to emit this message unconditionally at a low frequency. +The DroneCAN specification is available at https://dronecan.github.io/Specification/1._Introduction/. | Field Name | Type | Units | 描述 | | ---------------------------------------------------------- | ------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -8313,7 +8318,9 @@ Rally point. You can have multiple rally points defined. | 6 (Longitude) | Longitude | | | 7 (Altitude) | Altitude | m | -### MAV_CMD_UAVCAN_GET_NODE_INFO (5200) {#MAV_CMD_UAVCAN_GET_NODE_INFO} +### MAV_CMD_UAVCAN_GET_NODE_INFO (5200) — [SUP] {#MAV_CMD_UAVCAN_GET_NODE_INFO} + +**SUPERSEDED:** Replaced By [MAV_CMD_REQUEST_MESSAGE](#MAV_CMD_REQUEST_MESSAGE) (2026-05) Commands the vehicle to respond with a sequence of messages [UAVCAN_NODE_INFO](#UAVCAN_NODE_INFO), one message per every UAVCAN node that is online. Note that some of the response messages can be lost, which the receiver can detect easily by checking whether every received [UAVCAN_NODE_STATUS](#UAVCAN_NODE_STATUS) has a matching message [UAVCAN_NODE_INFO](#UAVCAN_NODE_INFO) received earlier; if not, this command should be sent again in order to request re-transmission of the node information messages. From b4c91cd00e7315ab6e2b1c0573d5992ea4da0031 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Thu, 7 May 2026 12:16:43 +1000 Subject: [PATCH 5/6] New translations development.md (Korean) [ci skip] --- ko/messages/development.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/ko/messages/development.md b/ko/messages/development.md index b562d119c..2a6d54076 100644 --- a/ko/messages/development.md +++ b/ko/messages/development.md @@ -469,12 +469,15 @@ State of RAIM processing. Actuator groups to test in [MAV_CMD_ACTUATOR_GROUP_TEST](#MAV_CMD_ACTUATOR_GROUP_TEST). -| Value | Name | Description | -| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | -| 0 | [ACTUATOR_TEST_GROUP_ROLL_TORQUE](#ACTUATOR_TEST_GROUP_ROLL_TORQUE) | Actuators that contribute to roll torque. | -| 1 | [ACTUATOR_TEST_GROUP_PITCH_TORQUE](#ACTUATOR_TEST_GROUP_PITCH_TORQUE) | Actuators that contribute to pitch torque. | -| 2 | [ACTUATOR_TEST_GROUP_YAW_TORQUE](#ACTUATOR_TEST_GROUP_YAW_TORQUE) | Actuators that contribute to yaw torque. | -| 3 | [ACTUATOR_TEST_GROUP_COLLECTIVE_TILT](#ACTUATOR_TEST_GROUP_COLLECTIVE_TILT) | Actuators that affect collective tilt. | +| Value | Name | Description | +| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | +| 0 | [ACTUATOR_TEST_GROUP_ROLL_TORQUE](#ACTUATOR_TEST_GROUP_ROLL_TORQUE) | Actuators that contribute to roll torque. | +| 1 | [ACTUATOR_TEST_GROUP_PITCH_TORQUE](#ACTUATOR_TEST_GROUP_PITCH_TORQUE) | Actuators that contribute to pitch torque. | +| 2 | [ACTUATOR_TEST_GROUP_YAW_TORQUE](#ACTUATOR_TEST_GROUP_YAW_TORQUE) | Actuators that contribute to yaw torque. | +| 3 | [ACTUATOR_TEST_GROUP_COLLECTIVE_TILT](#ACTUATOR_TEST_GROUP_COLLECTIVE_TILT) | Actuators that affect collective tilt. | +| 4 | [ACTUATOR_TEST_GROUP_X_THRUST](#ACTUATOR_TEST_GROUP_X_THRUST) | Actuators that contribute to x (longitudinal, positive = forward) thrust. | +| 5 | [ACTUATOR_TEST_GROUP_Y_THRUST](#ACTUATOR_TEST_GROUP_Y_THRUST) | Actuators that contribute to y (lateral, positive = right) thrust. | +| 6 | [ACTUATOR_TEST_GROUP_Z_THRUST](#ACTUATOR_TEST_GROUP_Z_THRUST) | Actuators that contribute to z (vertical, positive = down) thrust. | ### ESC_FIRMWARE — [WIP] {#ESC_FIRMWARE} From 813e53194d22931b8508468ca3fe1d09e9058bc0 Mon Sep 17 00:00:00 2001 From: PX4 Build Bot Date: Thu, 7 May 2026 12:16:58 +1000 Subject: [PATCH 6/6] New translations development.md (Chinese Simplified) [ci skip] --- zh/messages/development.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/zh/messages/development.md b/zh/messages/development.md index e147c3522..81e3b3115 100644 --- a/zh/messages/development.md +++ b/zh/messages/development.md @@ -469,12 +469,15 @@ State of RAIM processing. Actuator groups to test in [MAV_CMD_ACTUATOR_GROUP_TEST](#MAV_CMD_ACTUATOR_GROUP_TEST). -| 值 | Name | 描述 | -| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | -| 0 | [ACTUATOR_TEST_GROUP_ROLL_TORQUE](#ACTUATOR_TEST_GROUP_ROLL_TORQUE) | Actuators that contribute to roll torque. | -| 1 | [ACTUATOR_TEST_GROUP_PITCH_TORQUE](#ACTUATOR_TEST_GROUP_PITCH_TORQUE) | Actuators that contribute to pitch torque. | -| 2 | [ACTUATOR_TEST_GROUP_YAW_TORQUE](#ACTUATOR_TEST_GROUP_YAW_TORQUE) | Actuators that contribute to yaw torque. | -| 3 | [ACTUATOR_TEST_GROUP_COLLECTIVE_TILT](#ACTUATOR_TEST_GROUP_COLLECTIVE_TILT) | Actuators that affect collective tilt. | +| 值 | Name | 描述 | +| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | +| 0 | [ACTUATOR_TEST_GROUP_ROLL_TORQUE](#ACTUATOR_TEST_GROUP_ROLL_TORQUE) | Actuators that contribute to roll torque. | +| 1 | [ACTUATOR_TEST_GROUP_PITCH_TORQUE](#ACTUATOR_TEST_GROUP_PITCH_TORQUE) | Actuators that contribute to pitch torque. | +| 2 | [ACTUATOR_TEST_GROUP_YAW_TORQUE](#ACTUATOR_TEST_GROUP_YAW_TORQUE) | Actuators that contribute to yaw torque. | +| 3 | [ACTUATOR_TEST_GROUP_COLLECTIVE_TILT](#ACTUATOR_TEST_GROUP_COLLECTIVE_TILT) | Actuators that affect collective tilt. | +| 4 | [ACTUATOR_TEST_GROUP_X_THRUST](#ACTUATOR_TEST_GROUP_X_THRUST) | Actuators that contribute to x (longitudinal, positive = forward) thrust. | +| 5 | [ACTUATOR_TEST_GROUP_Y_THRUST](#ACTUATOR_TEST_GROUP_Y_THRUST) | Actuators that contribute to y (lateral, positive = right) thrust. | +| 6 | [ACTUATOR_TEST_GROUP_Z_THRUST](#ACTUATOR_TEST_GROUP_Z_THRUST) | Actuators that contribute to z (vertical, positive = down) thrust. | ### ESC_FIRMWARE — [WIP] {#ESC_FIRMWARE}