Skip to content

Commit 8057fa2

Browse files
PX4BuildBotPX4BuildBot
authored
New Crowdin updates (#649)
* New translations common.md (Korean) * New translations common.md (Chinese Simplified) * New translations development.md (Korean) * New translations development.md (Chinese Simplified) * New translations mavlink_version.md (Korean) * New translations mavlink_version.md (Chinese Simplified)
1 parent 709900b commit 8057fa2

File tree

6 files changed

+64
-66
lines changed

6 files changed

+64
-66
lines changed

‎ko/guide/mavlink_version.md‎

Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,6 @@ A library's MAVLink support can be determined in a number of ways:
3333
- [HEARTBEAT](../messages/common.md#HEARTBEAT)`.mavlink_version` field contains the minor version number.
3434
This is the `<version>` field defined in the [Message Definitions](../messages/index.md) (`version` in [common.xml](../messages/common.md) for dialects that depend on the common message set).
3535

36-
- [PROTOCOL_VERSION](../messages/common.md#PROTOCOL_VERSION).`version` contains the MAVLink version number multiplied by 100: v1.0 is 100, <!-- v2.0 is 200, --> v2.3 is 203 etc.
37-
Note that the message allows for additional version information, but is not supported on all flight stacks.
38-
3936
:::tip
4037
While messages do not contain version information, an extra CRC is used to ensure that a library will only process compatible messages (see [Serialization > CRC_EXTRA](../guide/serialization.md)).
4138
:::
@@ -46,41 +43,43 @@ Support for _MAVLink 2_ is indicated in the [AUTOPILOT_VERSION](../messages/comm
4643
It can also be inferred from the packet start marker byte.
4744

4845
This is sufficient if the communication link between autopilot and GCS is completely transparent.
49-
However, some communication links are not completely transparent as they include:
46+
Most flight stacks now assume MAVLink 2 support based on the protocol capability or packet start marker.
47+
This is reasonable because the majority of systems and communication links now reliably support MAVLink 2.
48+
49+
### Non-transparent communication links
50+
51+
Most flight stacks assume communication links are transparent.
52+
Possible causes of links not being transparent are:
5053

5154
- Routing, which can can change or reserialize MAVLink packets (for example, there might be an intermediate router that converts between versions).
5255
- Wireless links that rely on fixed length packetization may distort or truncate variable-length MAVLink 2 frames.
56+
For example, older SiK Radios may consume MAVLink 2 messages.
5357

54-
:::info
55-
Some flight stacks assume MAVLink 2 support based on the protocol capability or packet start marker.
56-
This is reasonable because the majority of systems and communication links now reliably support MAVLink 2.
57-
:::
58-
59-
To be certain that a link supports _MAVLink 2_ transparently, a GCS or other component can use the _MAVLink 2_ handshake protocol to test the link.
60-
This is done by sending the [MAV_CMD_REQUEST_MESSAGE](../messages/common.md#MAV_CMD_REQUEST_MESSAGE) command with `param1=300` ([PROTOCOL_VERSION](../messages/common.md#PROTOCOL_VERSION)).
61-
If the system supports _MAVLink 2_ and the handshake it will respond with [PROTOCOL_VERSION](../messages/common.md#PROTOCOL_VERSION) **encoded as MAVLink 2 packet**.
58+
To be certain that a link supports _MAVLink 2_ transparently, a GCS or other component might send the [MAV_CMD_REQUEST_MESSAGE](../messages/common.md#MAV_CMD_REQUEST_MESSAGE) command with `param1` set to the id of a _MAVLink 2_ message (with `id > 256`) that is supported by the flight stack.
59+
If the system supports _MAVLink 2_ and the handshake it will respond with the message **encoded as MAVLink 2 packet**.
6260
If it does not support _MAVLink 2_ it should `NACK` the command.
6361
The GCS should fall back to a timeout in case the command interface is not implemented properly.
6462

65-
:::tip
66-
If the target system does not support `PROTOCOL_VERSION` you can request any other message that it is able to emit.
67-
:::
68-
69-
The diagram below illustrates the complete sequence.
63+
The diagram below illustrates the sequence.
7064

71-
[![Mermaid sequence: Request protocol version](https://mermaid.ink/img/pako:eNptkG1rwjAQx79KuFcbOEkftJoxQWoRma6bdb4YBQntVcNs4mK6J_G7L1bcxmZeHLn_3f93x-0gUzkCgy2-VCgzHAi-1Ly8TiWxb8O1EZnYcGnIMEz-iwOtJB5lW7_q9WqBkUl_vggng8U0eniMktliEiVJfxhdWC8vnRuP0svfLhsZSYwFEyNKVJU5VmvaqX4_jWdxGI8X82iajOI7IuRhzljIZ-KSwoKFXJ7ZZVSQfnhr-W_CZCvcEqN-fGfmnO0jShKNGYpXhAYstciBGV1hA0rUJT-ksDvAUjArLDEFZr85FrxamxRSubc2e7InpcqTU6tquQJW8PXWZtUm5-Z0_z9qlAuj9LeoUeaoQ1VJAyzwazCwHbwDa9NW02tT2mlRt931g6ABH8Achzbdju90A-p4vuN3g30DPutVaLPjUK_luY5tdtuuu_8CvZ-j_w?type=png)](https://mermaid.live/edit#pako:eNptkG1rwjAQx79KuFcbOEkftJoxQWoRma6bdb4YBQntVcNs4mK6J_G7L1bcxmZeHLn_3f93x-0gUzkCgy2-VCgzHAi-1Ly8TiWxb8O1EZnYcGnIMEz-iwOtJB5lW7_q9WqBkUl_vggng8U0eniMktliEiVJfxhdWC8vnRuP0svfLhsZSYwFEyNKVJU5VmvaqX4_jWdxGI8X82iajOI7IuRhzljIZ-KSwoKFXJ7ZZVSQfnhr-W_CZCvcEqN-fGfmnO0jShKNGYpXhAYstciBGV1hA0rUJT-ksDvAUjArLDEFZr85FrxamxRSubc2e7InpcqTU6tquQJW8PXWZtUm5-Z0_z9qlAuj9LeoUeaoQ1VJAyzwazCwHbwDa9NW02tT2mlRt931g6ABH8Achzbdju90A-p4vuN3g30DPutVaLPjUK_luY5tdtuuu_8CvZ-j_w)
65+
[![Mermaid sequence: Check protocol version](https://mermaid.ink/img/pako:eNptUV1rwjAU_SvhPm3QiU0_dBkTpBYR7cbWbQ-jUEJ7W8Ns4mK6L_G_Lyq6sZmHS-4595xzSdZQqBKBwQpfW5QFjgSvNW-uMknsWXJtRCGWXBoyjtL_4EgriXvY8heDwQ5gJBk-5VEyyu_ju8c4fciTOE2H4_jMannjkmsiSqIqkt4mcW5nZ5ObKT0Mnf_2s5WR1NhIYkSDqjV7dpdz5E_ZECG3a8yEfCGUVDZXyPrEqpOKDKOpNXkXppjjihj1ozsVdmqOKEk0FijeEByotSiBGd2iAw3qhm9bWG_NMjBzbDADZq8lVrxdmAwyubEy-6LPSjUHpVZtPQdW8cXKdu2y5ObwPX_QuBRG6SOoUZaoI9VKA8yj3Z0zsDV8APMvw06v5_Wp6_X8IHCpA5_AbNfxe37Xp7RLA9f1Ng587VbpdkLfC_t-2A-oZ7nA3XwDTR6tNw?type=png)](https://mermaid.live/edit#pako:eNptUV1rwjAU_SvhPm3QiU0_dBkTpBYR7cbWbQ-jUEJ7W8Ns4mK6L_G_Lyq6sZmHS-4595xzSdZQqBKBwQpfW5QFjgSvNW-uMknsWXJtRCGWXBoyjtL_4EgriXvY8heDwQ5gJBk-5VEyyu_ju8c4fciTOE2H4_jMannjkmsiSqIqkt4mcW5nZ5ObKT0Mnf_2s5WR1NhIYkSDqjV7dpdz5E_ZECG3a8yEfCGUVDZXyPrEqpOKDKOpNXkXppjjihj1ozsVdmqOKEk0FijeEByotSiBGd2iAw3qhm9bWG_NMjBzbDADZq8lVrxdmAwyubEy-6LPSjUHpVZtPQdW8cXKdu2y5ObwPX_QuBRG6SOoUZaoI9VKA8yj3Z0zsDV8APMvw06v5_Wp6_X8IHCpA5_AbNfxe37Xp7RLA9f1Ng587VbpdkLfC_t-2A-oZ7nA3XwDTR6tNw)
7266

7367
<!-- Original sequence
7468
sequenceDiagram;
7569
participant GCS
7670
participant Drone
77-
GCS->>Drone: MAV_CMD_REQUEST_MESSAGE(param1=300)
71+
GCS->>Drone: MAV_CMD_REQUEST_MESSAGE(param1 = id of SOME_MAVLINK2_MESSAGE)
7872
GCS->>GCS: Start timeout
79-
Drone->>GCS: PROTOCOL_VERSION in MAVLink 2 framing
73+
Drone->>GCS: SOME_MAVLINK2_MESSAGE in MAVLink 2 framing
8074
GCS->>Drone: If ACK: Switches to MAVLink 2
8175
Drone->>GCS: Switches to MAVLink 2 on receive
8276
-->
8377

78+
:::tip
79+
Historically the message used for testing was `PROTOCOL_VERSION`, which is now deprecated.
80+
The protocol should work with any other MAVLink 2 telemetry message supported by the flight stack.
81+
:::
82+
8483
### Semi-Transparent Legacy Radios
8584

8685
Some popular legacy radios (e.g. the SiK radio series) operate in semi-transparent mode by injecting [RADIO_STATUS](../messages/common.md#RADIO_STATUS) messages into the MAVLink message stream.

‎ko/messages/common.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2291,7 +2291,7 @@ Status text message. These messages are printed in yellow in the COMM console of
22912291
| Field Name | Type | Values | Description |
22922292
| ---------------------------------------------------------------------------------------------- | ---------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
22932293
| severity | `uint8_t` | [MAV_SEVERITY](#MAV_SEVERITY) | Severity of status. Relies on the definitions within RFC-5424. |
2294-
| text | `char[50]` | | Status text message, without null termination character |
2294+
| text | `char[50]` | | Status text message, without null termination character. UTF-8 encoded. |
22952295
| <span class='ext'>id</span> <a href='#mav2_extension_field'>++</a> | `uint16_t` | | Unique (opaque) identifier for this statustext message. May be used to reassemble a logical long-statustext message from a sequence of chunks. A value of zero indicates this is the only chunk in the sequence and the message can be emitted immediately. |
22962296
| <span class='ext'>chunk_seq</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | | This chunk's sequence number; indexing is from zero. Any null character in the text field is taken to mean this was the last chunk. |
22972297

‎ko/messages/development.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -385,25 +385,25 @@ Signal authentication state in a GPS receiver.
385385

386386
Signal jamming state in a GPS receiver.
387387

388-
| Value | Name | Description |
389-
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
390-
| <a id='GPS_JAMMING_STATE_UNKNOWN'></a>0 | [GPS_JAMMING_STATE_UNKNOWN](#GPS_JAMMING_STATE_UNKNOWN) | The GPS receiver does not provide GPS signal jamming info. |
391-
| <a id='GPS_JAMMING_STATE_OK'></a>1 | [GPS_JAMMING_STATE_OK](#GPS_JAMMING_STATE_OK) | The GPS receiver detected no signal jamming. |
392-
| <a id='GPS_JAMMING_STATE_MITIGATED'></a>2 | [GPS_JAMMING_STATE_MITIGATED](#GPS_JAMMING_STATE_MITIGATED) | The GPS receiver detected and mitigated signal jamming. |
393-
| <a id='GPS_JAMMING_STATE_DETECTED'></a>3 | [GPS_JAMMING_STATE_DETECTED](#GPS_JAMMING_STATE_DETECTED) | The GPS receiver detected signal jamming. |
388+
| Value | Name | Description |
389+
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
390+
| <a id='GPS_JAMMING_STATE_UNKNOWN'></a>0 | [GPS_JAMMING_STATE_UNKNOWN](#GPS_JAMMING_STATE_UNKNOWN) | The GPS receiver does not provide GPS signal jamming info. |
391+
| <a id='GPS_JAMMING_STATE_NOT_JAMMED'></a>1 | [GPS_JAMMING_STATE_NOT_JAMMED](#GPS_JAMMING_STATE_NOT_JAMMED) | The GPS receiver detected no signal jamming. |
392+
| <a id='GPS_JAMMING_STATE_MITIGATED'></a>2 | [GPS_JAMMING_STATE_MITIGATED](#GPS_JAMMING_STATE_MITIGATED) | The GPS receiver detected and mitigated signal jamming. |
393+
| <a id='GPS_JAMMING_STATE_DETECTED'></a>3 | [GPS_JAMMING_STATE_DETECTED](#GPS_JAMMING_STATE_DETECTED) | The GPS receiver detected signal jamming. |
394394

395395
### GPS_SPOOFING_STATE — [WIP] {#GPS_SPOOFING_STATE}
396396

397397
<span class="warning">**WORK IN PROGRESS**: Do not use in stable production environments (it may change).</span>
398398

399399
Signal spoofing state in a GPS receiver.
400400

401-
| Value | Name | Description |
402-
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
403-
| <a id='GPS_SPOOFING_STATE_UNKNOWN'></a>0 | [GPS_SPOOFING_STATE_UNKNOWN](#GPS_SPOOFING_STATE_UNKNOWN) | The GPS receiver does not provide GPS signal spoofing info. |
404-
| <a id='GPS_SPOOFING_STATE_OK'></a>1 | [GPS_SPOOFING_STATE_OK](#GPS_SPOOFING_STATE_OK) | The GPS receiver detected no signal spoofing. |
405-
| <a id='GPS_SPOOFING_STATE_MITIGATED'></a>2 | [GPS_SPOOFING_STATE_MITIGATED](#GPS_SPOOFING_STATE_MITIGATED) | The GPS receiver detected and mitigated signal spoofing. |
406-
| <a id='GPS_SPOOFING_STATE_DETECTED'></a>3 | [GPS_SPOOFING_STATE_DETECTED](#GPS_SPOOFING_STATE_DETECTED) | The GPS receiver detected signal spoofing but still has a fix. |
401+
| Value | Name | Description |
402+
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
403+
| <a id='GPS_SPOOFING_STATE_UNKNOWN'></a>0 | [GPS_SPOOFING_STATE_UNKNOWN](#GPS_SPOOFING_STATE_UNKNOWN) | The GPS receiver does not provide GPS signal spoofing info. |
404+
| <a id='GPS_SPOOFING_STATE_NOT_SPOOFED'></a>1 | [GPS_SPOOFING_STATE_NOT_SPOOFED](#GPS_SPOOFING_STATE_NOT_SPOOFED) | The GPS receiver detected no signal spoofing. |
405+
| <a id='GPS_SPOOFING_STATE_MITIGATED'></a>2 | [GPS_SPOOFING_STATE_MITIGATED](#GPS_SPOOFING_STATE_MITIGATED) | The GPS receiver detected and mitigated signal spoofing. |
406+
| <a id='GPS_SPOOFING_STATE_DETECTED'></a>3 | [GPS_SPOOFING_STATE_DETECTED](#GPS_SPOOFING_STATE_DETECTED) | The GPS receiver detected signal spoofing but still has a fix. |
407407

408408
### GPS_RAIM_STATE — [WIP] {#GPS_RAIM_STATE}
409409

0 commit comments

Comments
 (0)