Skip to content

Commit bd6b7a0

Browse files
PX4BuildBotPX4BuildBot
authored
New Crowdin updates (#592)
* New translations define_xml_element.md (Korean) * New translations define_xml_element.md (Chinese Simplified) * New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations dialects.md (Korean) * New translations dialects.md (Chinese Simplified) * New translations summary.md (Korean) * New translations index.md (Korean) * New translations trajectory.md (Korean) * New translations summary.md (Chinese Simplified) * New translations index.md (Chinese Simplified) * New translations trajectory.md (Chinese Simplified)
1 parent 8aadd7d commit bd6b7a0

File tree

12 files changed

+76
-62
lines changed

12 files changed

+76
-62
lines changed

‎ko/SUMMARY.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,6 @@
5656
- [File Transfer Protocol (FTP)](services/ftp.md)
5757
- [Landing Target Protocol](services/landing_target.md)
5858
- [Ping Protocol](services/ping.md)
59-
- [Path Planning (Trajectory) Protocol](services/trajectory.md)
6059
- [Battery Protocol](services/battery.md)
6160
- [Terrain Protocol](services/terrain.md)
6261
- [Tunnel Protocol](services/tunnel.md)

‎ko/guide/define_xml_element.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -443,7 +443,7 @@ A typical mission command is ([MAV_CMD_NAV_WAYPOINT](../messages/common.md#MAV_C
443443
<description>Navigate to waypoint.</description>
444444
<param index="1">Hold time in decimal seconds. (ignored by fixed wing, time to stay at waypoint for rotary wing)</param>
445445
<param index="2">Acceptance radius in meters (if the sphere with this radius is hit, the waypoint counts as reached)</param>
446-
<param index="3">0 to pass through the WP, if &amp;gt; 0 radius in meters to pass by WP. Positive value for clockwise orbit, negative value for counter-clockwise orbit. Allows trajectory control.</param>
446+
<param index="3">0 to pass through the WP, if &gt; 0 radius in meters to pass by WP. Positive value for clockwise orbit, negative value for counter-clockwise orbit. Allows trajectory control.</param>
447447
<param index="4">Desired yaw angle at waypoint (rotary wing). NaN for unchanged.</param>
448448
<param index="5">Latitude</param>
449449
<param index="6">Longitude</param>
@@ -491,11 +491,10 @@ In addition, there are some other "standard" prefixes which are used for common
491491
- `MAV_CMD_NAV_`: `NAV` commands are used for navigation/movement commands (commands to go to a particular waypoint or move in a particular way).
492492
- `MAV_CMD_DO_`: `DO` commands are used for setting modes, changing altitude or speed etc.
493493
- `MAV_CMD_CONDITION_`: `CONDITION_` commands are used to define conditions before the mission state machine will move to the next item (e.g. a time after reaching a waypoint before taking a picture).
494-
- `MAV_CMD_REQUEST_`: For requesting information from a system.
495494

496495
:::tip
497496
The rules for the above prefixes are flexible; some DO commands might reasonably be NAV commands.
498-
In some cases a request for information might be a `MAV_CMD_REQUEST_` and in others it might be a stand alone message.
497+
It is not uncommon for `DO_` commands to omit the DO, in particular where the rest of the command makes the function obvious.
499498
:::
500499

501500
### Parameters (param) {#param}

‎ko/messages/common.md

Lines changed: 23 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5838,6 +5838,7 @@ See https://mavlink.io/en/services/standard_modes.html
58385838
| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
58395839
| <a id='MAV_MODE_PROPERTY_ADVANCED'></a>1 | [MAV_MODE_PROPERTY_ADVANCED](#MAV_MODE_PROPERTY_ADVANCED) | If set, this mode is an advanced mode.<br>For example a rate-controlled manual mode might be advanced, whereas a position-controlled manual mode is not.<br>A GCS can optionally use this flag to configure the UI for its intended users. |
58405840
| <a id='MAV_MODE_PROPERTY_NOT_USER_SELECTABLE'></a>2 | [MAV_MODE_PROPERTY_NOT_USER_SELECTABLE](#MAV_MODE_PROPERTY_NOT_USER_SELECTABLE) | If set, this mode should not be added to the list of selectable modes.<br>The mode might still be selected by the FC directly (for example as part of a failsafe). |
5841+
| <a id='MAV_MODE_PROPERTY_AUTO_MODE'></a>4 | [MAV_MODE_PROPERTY_AUTO_MODE](#MAV_MODE_PROPERTY_AUTO_MODE) | If set, this mode is automatically controlled (it may use but does not require a manual controller).<br>If unset the mode is a assumed to require user input (be a manual mode). |
58415842

58425843
### MAV_AUTOPILOT — \[from: [minimal](../messages/minimal.md#MAV_AUTOPILOT)\] {#MAV_AUTOPILOT}
58435844

@@ -7963,29 +7964,33 @@ Fence return point (there can only be one such point in a geofence definition).
79637964

79647965
Fence vertex for an inclusion polygon (the polygon must not be self-intersecting). The vehicle must stay within this area. Minimum of 3 vertices required.
79657966

7966-
| Param (Label) | Description | Values |
7967-
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
7968-
| 1 (Vertex Count) | Polygon vertex count | min: 3 inc: 1 |
7969-
| 2 (Inclusion Group) | Vehicle must be inside ALL inclusion zones in a single group, vehicle must be inside at least one group, must be the same for all points in each polygon | min: 0 inc: 1 |
7970-
| 3 | Reserved | |
7971-
| 4 | Reserved | |
7972-
| 5 (Latitude) | Latitude | |
7973-
| 6 (Longitude) | Longitude | |
7974-
| 7 | Reserved | |
7967+
The vertices for a polygon must be sent sequentially, each with param1 set to the total number of vertices in the polygon.
7968+
7969+
| Param (Label) | Description | Values |
7970+
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- |
7971+
| 1 (Vertex Count) | Polygon vertex count. This is the number of vertices in the current polygon (all vertices will have the same number). | min: 3 inc: 1 |
7972+
| 2 (Inclusion Group) | Vehicle must be inside ALL inclusion zones in a single group, vehicle must be inside at least one group, must be the same for all points in each polygon | min: 0 inc: 1 |
7973+
| 3 | Reserved | |
7974+
| 4 | Reserved | |
7975+
| 5 (Latitude) | Latitude | |
7976+
| 6 (Longitude) | Longitude | |
7977+
| 7 | Reserved | |
79757978

79767979
### MAV_CMD_NAV_FENCE_POLYGON_VERTEX_EXCLUSION (5002) {#MAV_CMD_NAV_FENCE_POLYGON_VERTEX_EXCLUSION}
79777980

79787981
Fence vertex for an exclusion polygon (the polygon must not be self-intersecting). The vehicle must stay outside this area. Minimum of 3 vertices required.
79797982

7980-
| Param (Label) | Description | Values |
7981-
| ----------------------------------- | -------------------- | --------------------------------------------- |
7982-
| 1 (Vertex Count) | Polygon vertex count | min: 3 inc: 1 |
7983-
| 2 | Reserved | |
7984-
| 3 | Reserved | |
7985-
| 4 | Reserved | |
7986-
| 5 (Latitude) | Latitude | |
7987-
| 6 (Longitude) | Longitude | |
7988-
| 7 | Reserved | |
7983+
The vertices for a polygon must be sent sequentially, each with param1 set to the total number of vertices in the polygon.
7984+
7985+
| Param (Label) | Description | Values |
7986+
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- |
7987+
| 1 (Vertex Count) | Polygon vertex count. This is the number of vertices in the current polygon (all vertices will have the same number). | min: 3 inc: 1 |
7988+
| 2 | Reserved | |
7989+
| 3 | Reserved | |
7990+
| 4 | Reserved | |
7991+
| 5 (Latitude) | Latitude | |
7992+
| 6 (Longitude) | Longitude | |
7993+
| 7 | Reserved | |
79897994

79907995
### MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION (5003) {#MAV_CMD_NAV_FENCE_CIRCLE_INCLUSION}
79917996

‎ko/messages/dialects.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,18 @@ Dialects are not managed by this project!
1717

1818
The dialect definitions are:
1919

20+
- [matrixpilot.xml](matrixpilot.md)
21+
- [loweheiser.xml](loweheiser.md)
22+
- [cubepilot.xml](cubepilot.md)
23+
- [AVSSUAS.xml](AVSSUAS.md)
2024
- [paparazzi.xml](paparazzi.md)
21-
- [ardupilotmega.xml](ardupilotmega.md)
22-
- [csAirLink.xml](csAirLink.md)
2325
- [ualberta.xml](ualberta.md)
24-
- [AVSSUAS.xml](AVSSUAS.md)
25-
- [storm32.xml](storm32.md)
26+
- [ASLUAV.xml](ASLUAV.md)
27+
- [csAirLink.xml](csAirLink.md)
2628
- [icarous.xml](icarous.md)
29+
- [storm32.xml](storm32.md)
2730
- [uAvionix.xml](uAvionix.md)
28-
- [ASLUAV.xml](ASLUAV.md)
29-
- [cubepilot.xml](cubepilot.md)
30-
- [matrixpilot.xml](matrixpilot.md)
31-
- [loweheiser.xml](loweheiser.md)
31+
- [ardupilotmega.xml](ardupilotmega.md)
3232

3333
Note that dialects may `include` [MAVLink-Standard Definitions](index.md) or other dialects.
3434
Up to 5 levels of XML file nesting are allowed - see `MAXIMUM_INCLUDE_FILE_NESTING` in [mavgen.py](https://github.com/ArduPilot/pymavlink/blob/master/generator/mavgen.py#L44).

‎ko/services/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,6 @@ The main microservices are shown in the sidebar (most are listed below):
2929
- [File Transfer Protocol (FTP)](../services/ftp.md)
3030
- [Landing Target Protocol](../services/landing_target.md)
3131
- [Ping Protocol](../services/ping.md)
32-
- [Path Planning Protocol](../services/trajectory.md) (Trajectory Interface)
3332
- [Battery Protocol](../services/battery.md)
3433
- [Terrain Protocol](../services/terrain.md)
3534
- [Tunnel Protocol](../services/tunnel.md)

‎ko/services/trajectory.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
# Path Planning Protocol (Trajectory Interface)
22

3+
:::warning
4+
This interface is deprecated.
5+
The interface was present in PX4 v1.11 to PX4 v1.14, but is no longer used in any current flight stacks.
6+
:::
7+
38
The path planning protocol (a.k.a. trajectory interface) is a general-purpose protocol for a system to request dynamic path planning from another system (i.e. for an autopilot to request a path from a companion computer).
49

510
The protocol is primarily intended for cases where constraints on the path to a destination are unknown or may change dynamically, but it can also be used for any other path management activities.

‎zh/SUMMARY.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,6 @@
5656
- [File Transfer Protocol (FTP)](services/ftp.md)
5757
- [Landing Target Protocol](services/landing_target.md)
5858
- [Ping Protocol](services/ping.md)
59-
- [Path Planning (Trajectory) Protocol](services/trajectory.md)
6059
- [Battery Protocol](services/battery.md)
6160
- [Terrain Protocol](services/terrain.md)
6261
- [Tunnel Protocol](services/tunnel.md)

‎zh/guide/define_xml_element.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -443,7 +443,7 @@ A typical mission command is ([MAV_CMD_NAV_WAYPOINT](../messages/common.md#MAV_C
443443
<description>Navigate to waypoint.</description>
444444
<param index="1">Hold time in decimal seconds. (ignored by fixed wing, time to stay at waypoint for rotary wing)</param>
445445
<param index="2">Acceptance radius in meters (if the sphere with this radius is hit, the waypoint counts as reached)</param>
446-
<param index="3">0 to pass through the WP, if &amp;gt; 0 radius in meters to pass by WP. Positive value for clockwise orbit, negative value for counter-clockwise orbit. Allows trajectory control.</param>
446+
<param index="3">0 to pass through the WP, if &gt; 0 radius in meters to pass by WP. Positive value for clockwise orbit, negative value for counter-clockwise orbit. Allows trajectory control.</param>
447447
<param index="4">Desired yaw angle at waypoint (rotary wing). NaN for unchanged.</param>
448448
<param index="5">Latitude</param>
449449
<param index="6">Longitude</param>
@@ -491,11 +491,10 @@ In addition, there are some other "standard" prefixes which are used for common
491491
- `MAV_CMD_NAV_`: `NAV` commands are used for navigation/movement commands (commands to go to a particular waypoint or move in a particular way).
492492
- `MAV_CMD_DO_`: `DO` commands are used for setting modes, changing altitude or speed etc.
493493
- `MAV_CMD_CONDITION_`: `CONDITION_` commands are used to define conditions before the mission state machine will move to the next item (e.g. a time after reaching a waypoint before taking a picture).
494-
- `MAV_CMD_REQUEST_`: For requesting information from a system.
495494

496495
:::tip
497496
The rules for the above prefixes are flexible; some DO commands might reasonably be NAV commands.
498-
In some cases a request for information might be a `MAV_CMD_REQUEST_` and in others it might be a stand alone message.
497+
It is not uncommon for `DO_` commands to omit the DO, in particular where the rest of the command makes the function obvious.
499498
:::
500499

501500
### Parameters (param) {#param}

0 commit comments

Comments
 (0)