You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ko/about/faq.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,8 @@
21
21
</dd>
22
22
23
23
<dt>What version of MAVLink should I use?</dt>
24
-
<dd>You should use the <ahref="../guide/mavlink_2.md">MAVLink 2</a> protocol where at all possible (it fixes a number of limitations of earlier versions).
25
-
The <em>MAVLink 2</em> libraries also support <em>MAVLink 1</em>, so you can use them to communicate with legacy systems if needed.
24
+
<dd>You should use the <ahref="../guide/mavlink_2.md">MAVLink 2</a> protocol where at all possible (it fixes a number of limitations of earlier versions).
25
+
The <em>MAVLink 2</em> libraries also support <em>MAVLink 1</em>, so you can use them to communicate with legacy systems if needed.
26
26
</dd>
27
27
28
28
<dt>How often is MAVLink updated/released?</dt>
@@ -58,12 +58,14 @@
58
58
<dd>MAVLink는 무인 항공 시스템의 안전에 중요한 구성 요소의 일부입니다. 많은 패킷을 버리는 나쁜 통신 링크는 비행체의 안전을 위협할 수 있고, 모니터링이 필요합니다. 헤더에 시퀀스를 가지는 것은 MAVLink가 패킷 손실률에 관한 피드백을 지속적으로 제공할 수 있도록 하여 비행체나 관제국이 조치를 취할수 있도록 합니다.</dd>
59
59
60
60
<dt>왜 CRC_EXTRA가 패킷 무결성 체크섬에 필요한가요?</dt>
61
-
<dd>CRC_EXTRA의 CRC는 송수신자 각자가 지정 메시지의 유선 형식을 이해하는지 검증하는 용도로 활용합니다 (프로토콜 구조가 단순하여 메시지 구조에 페이로드가 들어있지 않기 때문에 필요함).
62
-
MAVLink 0.9에서는 CRC를 사용하지 않았습니다(다만 길이 검사는 진행했습니다).
63
-
메시지를 설명하는 XML이 메시지 길이 변화 없이 변경되는 소수의 케이스가 있었는데, 이것은 메시지를 읽을 때 심각하게 손상된 필드로 이어졌습니다.</dd>
61
+
<dd>The CRC_EXTRA CRC is used to verify that the sender and receiver have a shared understanding of the over-the-wire format of a particular message
62
+
(required because as a lightweight protocol, the message structure isn't included in the payload).
63
+
MAVLink 0.9에서는 CRC를 사용하지 않았습니다(다만 길이 검사는 진행했습니다).
64
+
There were a small number of cases where XML describing a message changed without changing the message length,
65
+
leading to badly corrupted fields when messages were read.</dd>
64
66
65
67
<dt>디코딩/인코딩 루틴이나 다른 요소들을 개선하는데 도움을 주고 싶습니다. MAVLink가 바뀔 수도 있나요?</dt>
66
-
<dd>매우 엄밀한 안전 테스트를 거치는 경우에 그럴 수 있습니다.
68
+
<dd>매우 엄밀한 안전 테스트를 거치는 경우에 그럴 수 있습니다.
67
69
MAVLink는 많은 autopilot 시스템에서 중요한 안전 요소로 사용되기 때문에 다년간의 시험을 거칩니다. Please suggest new features on the MAVLink <ahref="../index.md#support">support channels</a>.</dd>
68
70
69
71
<dt>How can I further reduce the generated C library size?</dt>
Copy file name to clipboardExpand all lines: ko/messages/dialects.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,20 +17,19 @@ Dialects are not managed by this project!
17
17
18
18
The dialect definitions are:
19
19
20
-
-[csAirLink.xml](csAirLink.md)
20
+
-[storm32.xml](storm32.md)
21
+
-[paparazzi.xml](paparazzi.md)
22
+
-[stemstudios.xml](stemstudios.md)
23
+
-[AVSSUAS.xml](AVSSUAS.md)
24
+
-[uAvionix.xml](uAvionix.md)
21
25
-[loweheiser.xml](loweheiser.md)
22
-
-[cubepilot.xml](cubepilot.md)
23
26
-[ASLUAV.xml](ASLUAV.md)
24
27
-[ardupilotmega.xml](ardupilotmega.md)
25
-
-[matrixpilot.xml](matrixpilot.md)
26
28
-[marsh.xml](marsh.md)
27
-
-[uAvionix.xml](uAvionix.md)
28
-
-[AVSSUAS.xml](AVSSUAS.md)
29
-
-[storm32.xml](storm32.md)
30
-
-[ualberta.xml](ualberta.md)
31
-
-[paparazzi.xml](paparazzi.md)
29
+
-[csAirLink.xml](csAirLink.md)
32
30
-[icarous.xml](icarous.md)
33
-
-[stemstudios.xml](stemstudios.md)
31
+
-[cubepilot.xml](cubepilot.md)
32
+
-[ualberta.xml](ualberta.md)
34
33
35
34
Note that dialects may `include`[MAVLink-Standard Definitions](index.md) or other dialects.
36
35
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).
Arm authorizer->>Drone: COMMAND_ACK result=MAV_RESULT_IN_PROGRESS
43
43
Arm authorizer->>Drone: (optional)Request information about mission, battery level and etc.
44
-
Arm authorizer->>Internet: (optional)Request information about weather, aerospace trafic and etc.
44
+
Arm authorizer->>Internet: (optional)Request information about weather, aerospace traffic and etc.
45
45
Arm authorizer->>Drone: COMMAND_ACK command=MAV_CMD_ARM_AUTHORIZATION_REQUEST result=ACCEPTED, TEMPORARILY_REJECTED or DENIED
46
46
Drone->>Remote control/QCS: QCS STATUSTEXT text=Arm authorization was approved or denied
47
47
@@ -65,7 +65,7 @@ COMMAND_ACK
65
65
command=MAV_CMD_ARM_AUTHORIZATION_REQUEST
66
66
result=ACCEPTED, TEMPORARILY_REJECTED or DENIED
67
67
progress/result_param1=if result is TEMPORARILY_REJECTED or DENIED the reason should be set MAV_ARM_AUTH_DENIED_REASON otherwise it should be set as 0
68
-
result_param2=if result is ACCEPTED the it should be set with the time in seconds that this authorization is valid otherwise an aditional information about why it was denied should be set. example: for result_param1=MAV_ARM_AUTH_DENIED_REASON_INVALID_WAYPOINT or MAV_ARM_AUTH_DENIED_REASON_AIRSPACE_IN_USE it may have the index of the waypoint that caused it to be denied.
68
+
result_param2=if result is ACCEPTED the it should be set with the time in seconds that this authorization is valid otherwise an additional information about why it was denied should be set. example: for result_param1=MAV_ARM_AUTH_DENIED_REASON_INVALID_WAYPOINT or MAV_ARM_AUTH_DENIED_REASON_AIRSPACE_IN_USE it may have the index of the waypoint that caused it to be denied.
0 commit comments