Skip to content

Commit 118bde2

Browse files
PX4BuildBotPX4BuildBot
authored
New Crowdin updates (#605)
* New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations minimal.md (Korean) * New translations minimal.md (Chinese Simplified) * New translations index.md (Korean) * New translations index.md (Chinese Simplified) * New translations index.md (Korean) * New translations index.md (Chinese Simplified) * New translations mavlink_id_assignment.md (Korean) * New translations mavlink_id_assignment.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations minimal.md (Korean) * New translations minimal.md (Chinese Simplified)
1 parent 1ccd243 commit 118bde2

8 files changed

Lines changed: 124 additions & 44 deletions

File tree

‎ko/messages/common.md‎

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3012,7 +3012,9 @@ Odometry message to communicate odometry information with an external interface.
30123012
| <span class='ext'>estimator_type</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | | [MAV_ESTIMATOR_TYPE](#MAV_ESTIMATOR_TYPE) | Type of estimator that is providing the odometry. |
30133013
| <span class='ext'>quality</span> <a href='#mav2_extension_field'>++</a> | `int8_t` | % | invalid:0 | Optional odometry quality metric as a percentage. -1 = odometry has failed, 0 = unknown/unset quality, 1 = worst quality, 100 = best quality |
30143014

3015-
### TRAJECTORY_REPRESENTATION_WAYPOINTS (332) {#TRAJECTORY_REPRESENTATION_WAYPOINTS}
3015+
### TRAJECTORY_REPRESENTATION_WAYPOINTS (332) — [DEP] {#TRAJECTORY_REPRESENTATION_WAYPOINTS}
3016+
3017+
<span class="warning">**DEPRECATED:** Replaced By Nothing (2025-03) — Implemented PX4 v1.11 to v1.14. Not used in current flight stacks.)</span>
30163018

30173019
Describe a trajectory using an array of up-to 5 waypoints in the local frame ([MAV_FRAME_LOCAL_NED](#MAV_FRAME_LOCAL_NED)).
30183020

@@ -3033,7 +3035,9 @@ Describe a trajectory using an array of up-to 5 waypoints in the local frame ([M
30333035
| vel_yaw | `float[5]` | rad/s | invalid:[NaN] | Yaw rate, set to NaN if not being used |
30343036
| command | `uint16_t[5]` | | invalid:[UINT16_MAX] [MAV_CMD](#mav_commands) | [MAV_CMD](#mav_commands) command id of waypoint, set to UINT16_MAX if not being used. |
30353037

3036-
### TRAJECTORY_REPRESENTATION_BEZIER (333) {#TRAJECTORY_REPRESENTATION_BEZIER}
3038+
### TRAJECTORY_REPRESENTATION_BEZIER (333) — [DEP] {#TRAJECTORY_REPRESENTATION_BEZIER}
3039+
3040+
<span class="warning">**DEPRECATED:** Replaced By Nothing (2025-03) — Implemented PX4 v1.11 to v1.14. Not used in current flight stacks.)</span>
30373041

30383042
Describe a trajectory using an array of up-to 5 bezier control points in the local frame ([MAV_FRAME_LOCAL_NED](#MAV_FRAME_LOCAL_NED)).
30393043

@@ -5933,6 +5937,7 @@ MAVLINK component type reported in HEARTBEAT message. Flight controllers must re
59335937
| <a id='MAV_TYPE_ILLUMINATOR'></a>44 | [MAV_TYPE_ILLUMINATOR](#MAV_TYPE_ILLUMINATOR) | Illuminator. An illuminator is a light source that is used for lighting up dark areas external to the sytstem: e.g. a torch or searchlight (as opposed to a light source for illuminating the system itself, e.g. an indicator light). |
59345938
| <a id='MAV_TYPE_SPACECRAFT_ORBITER'></a>45 | [MAV_TYPE_SPACECRAFT_ORBITER](#MAV_TYPE_SPACECRAFT_ORBITER) | Orbiter spacecraft. Includes satellites orbiting terrestrial and extra-terrestrial bodies. Follows NASA Spacecraft Classification. |
59355939
| <a id='MAV_TYPE_GROUND_QUADRUPED'></a>46 | [MAV_TYPE_GROUND_QUADRUPED](#MAV_TYPE_GROUND_QUADRUPED) | A generic four-legged ground vehicle (e.g., a robot dog). |
5940+
| <a id='MAV_TYPE_VTOL_GYRODYNE'></a>47 | [MAV_TYPE_VTOL_GYRODYNE](#MAV_TYPE_VTOL_GYRODYNE) | VTOL hybrid of helicopter and autogyro. It has a main rotor for lift and separate propellers for forward flight. The rotor must be powered for hover but can autorotate in cruise flight. See: https://en.wikipedia.org/wiki/Gyrodyne |
59365941

59375942
### MAV_MODE_FLAG — \[from: [minimal](../messages/minimal.md#MAV_MODE_FLAG)\] {#MAV_MODE_FLAG}
59385943

@@ -5980,10 +5985,17 @@ MAVLINK component type reported in HEARTBEAT message. Flight controllers must re
59805985

59815986
### MAV_COMPONENT — \[from: [minimal](../messages/minimal.md#MAV_COMPONENT)\] {#MAV_COMPONENT}
59825987

5983-
Component ids (values) for the different types and instances of onboard hardware/software that might make up a MAVLink system (autopilot, cameras, servos, GPS systems, avoidance systems etc.).
5988+
Legacy component ID values for particular types of hardware/software that might make up a MAVLink system (autopilot, cameras, servos, avoidance systems etc.).
5989+
5990+
Components are not required or expected to use IDs with names that correspond to their type or function, but may choose to do so.
5991+
Using an ID that matches the type may slightly reduce the chances of component id clashes, as, for historical reasons, it is less likely to be used by some other type of component.
5992+
System integration will still need to ensure that all components have unique IDs.
5993+
5994+
Component IDs are used for addressing messages to a particular component within a system.
5995+
A component can use any unique ID between 1 and 255 ([MAV_COMP_ID_ALL](#MAV_COMP_ID_ALL) value is the broadcast address, used to send to all components).
59845996

5985-
Components must use the appropriate ID in their source address when sending messages. Components can also use IDs to determine if they are the intended recipient of an incoming message. The [MAV_COMP_ID_ALL](#MAV_COMP_ID_ALL) value is used to indicate messages that must be processed by all components.
5986-
When creating new entries, components that can have multiple instances (e.g. cameras, servos etc.) should be allocated sequential values. An appropriate number of values should be left free after these components to allow the number of instances to be expanded.
5997+
Historically component ID were also used for identifying the type of component.
5998+
New code must not use component IDs to infer the component type, but instead check the [MAV_TYPE](#MAV_TYPE) in the HEARTBEAT message!
59875999

59886000
| Value | Name | Description |
59896001
| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

‎ko/messages/minimal.md‎

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,7 @@ MAVLINK component type reported in HEARTBEAT message. Flight controllers must re
156156
| <a id='MAV_TYPE_ILLUMINATOR'></a>44 | [MAV_TYPE_ILLUMINATOR](#MAV_TYPE_ILLUMINATOR) | Illuminator. An illuminator is a light source that is used for lighting up dark areas external to the sytstem: e.g. a torch or searchlight (as opposed to a light source for illuminating the system itself, e.g. an indicator light). |
157157
| <a id='MAV_TYPE_SPACECRAFT_ORBITER'></a>45 | [MAV_TYPE_SPACECRAFT_ORBITER](#MAV_TYPE_SPACECRAFT_ORBITER) | Orbiter spacecraft. Includes satellites orbiting terrestrial and extra-terrestrial bodies. Follows NASA Spacecraft Classification. |
158158
| <a id='MAV_TYPE_GROUND_QUADRUPED'></a>46 | [MAV_TYPE_GROUND_QUADRUPED](#MAV_TYPE_GROUND_QUADRUPED) | A generic four-legged ground vehicle (e.g., a robot dog). |
159+
| <a id='MAV_TYPE_VTOL_GYRODYNE'></a>47 | [MAV_TYPE_VTOL_GYRODYNE](#MAV_TYPE_VTOL_GYRODYNE) | VTOL hybrid of helicopter and autogyro. It has a main rotor for lift and separate propellers for forward flight. The rotor must be powered for hover but can autorotate in cruise flight. See: https://en.wikipedia.org/wiki/Gyrodyne |
159160

160161
### MAV_MODE_FLAG {#MAV_MODE_FLAG}
161162

@@ -203,10 +204,17 @@ MAVLINK component type reported in HEARTBEAT message. Flight controllers must re
203204

204205
### MAV_COMPONENT {#MAV_COMPONENT}
205206

206-
Component ids (values) for the different types and instances of onboard hardware/software that might make up a MAVLink system (autopilot, cameras, servos, GPS systems, avoidance systems etc.).
207+
Legacy component ID values for particular types of hardware/software that might make up a MAVLink system (autopilot, cameras, servos, avoidance systems etc.).
207208

208-
Components must use the appropriate ID in their source address when sending messages. Components can also use IDs to determine if they are the intended recipient of an incoming message. The [MAV_COMP_ID_ALL](#MAV_COMP_ID_ALL) value is used to indicate messages that must be processed by all components.
209-
When creating new entries, components that can have multiple instances (e.g. cameras, servos etc.) should be allocated sequential values. An appropriate number of values should be left free after these components to allow the number of instances to be expanded.
209+
Components are not required or expected to use IDs with names that correspond to their type or function, but may choose to do so.
210+
Using an ID that matches the type may slightly reduce the chances of component id clashes, as, for historical reasons, it is less likely to be used by some other type of component.
211+
System integration will still need to ensure that all components have unique IDs.
212+
213+
Component IDs are used for addressing messages to a particular component within a system.
214+
A component can use any unique ID between 1 and 255 ([MAV_COMP_ID_ALL](#MAV_COMP_ID_ALL) value is the broadcast address, used to send to all components).
215+
216+
Historically component ID were also used for identifying the type of component.
217+
New code must not use component IDs to infer the component type, but instead check the [MAV_TYPE](#MAV_TYPE) in the HEARTBEAT message!
210218

211219
| Value | Name | Description |
212220
| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

‎ko/services/index.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,5 @@ The main microservices are shown in the sidebar (most are listed below):
3939
- [Payload Protocol](../services/payload.md)
4040
- [Traffic Management (UTM/ADS-B)](../services/traffic_management.md)
4141
- [Events Interface (WIP)](../services/events.md)
42-
- [Standard Flight Modes (WIP)](../services/standard_modes.md)
42+
- [Standard Flight Modes](../services/standard_modes.md)
4343
- [Time Synchronization](../services/timesync.md)
44-
- [Illuminator Protocol](../services/illuminator.md)

0 commit comments

Comments
 (0)