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: en/messages/common.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1443,7 +1443,7 @@ The message is used for both timesync requests and responses.
1443
1443
The request is sent with `ts1=syncing component timestamp` and `tc1=0`, and may be broadcast or targeted to a specific system/component.
1444
1444
The response is sent with `ts1=syncing component timestamp` (mirror back unchanged), and `tc1=responding component timestamp`, with the `target_system` and `target_component` set to ids of the original request.
1445
1445
Systems can determine if they are receiving a request or response based on the value of `tc`.
1446
-
If the response has `target_system==target_component==0` the remote system has not been updated to use the component IDs and cannot reliably timesync; the requestor may report an error.
1446
+
If the response has `target_system==target_component==0` the remote system has not been updated to use the component IDs and cannot reliably timesync; the requester may report an error.
1447
1447
Timestamps are UNIX Epoch time or time since system boot in nanoseconds (the timestamp format can be inferred by checking for the magnitude of the number; generally it doesn't matter as only the offset is used).
1448
1448
The message sequence is repeated numerous times with results being filtered/averaged to estimate the offset.
1449
1449
See also: https://mavlink.io/en/services/timesync.html.
@@ -1919,7 +1919,7 @@ The autopilot is requesting a resource (file, binary, other type of data)
1919
1919
1920
1920
Field Name | Type | Description
1921
1921
--- | --- | ---
1922
-
request_id | `uint8_t` | Request ID. This ID should be re-used when sending back URI contents
1922
+
request_id | `uint8_t` | Request ID. This ID should be reused when sending back URI contents
1923
1923
uri_type | `uint8_t` | The type of requested URI. 0 = a file via URL. 1 = a UAVCAN binary
1924
1924
uri | `uint8_t[120]` | The requested unique resource identifier (URI). It is not necessarily a straight domain name (depends on the URI type enum)
1925
1925
transfer_type | `uint8_t` | The way the autopilot wants to receive the URI. 0 = MAVLink FTP. 1 = binary stream.
speed_vertical | `int16_t` | cm/s | | The vertical speed. Up is positive. If unknown: 6300 cm/s. If speed is larger than 6200 cm/s, use 6200 cm/s. If lower than -6200 cm/s, use -6200 cm/s.
3828
3828
latitude | `int32_t` | degE7 | invalid:0 | Current latitude of the unmanned aircraft. If unknown: 0 (both Lat/Lon).
3829
3829
longitude | `int32_t` | degE7 | invalid:0 | Current longitude of the unmanned aircraft. If unknown: 0 (both Lat/Lon).
3830
-
altitude_barometric | `float` | m | invalid:-1000 | The altitude calculated from the barometric pressue. Reference is against 29.92inHg or 1013.2mb. If unknown: -1000 m.
3830
+
altitude_barometric | `float` | m | invalid:-1000 | The altitude calculated from the barometric pressure. Reference is against 29.92inHg or 1013.2mb. If unknown: -1000 m.
3831
3831
altitude_geodetic | `float` | m | invalid:-1000 | The geodetic altitude as defined by WGS84. If unknown: -1000 m.
3832
3832
height_reference | `uint8_t` | | [MAV_ODID_HEIGHT_REF](#MAV_ODID_HEIGHT_REF) | Indicates the reference point for the height field.
3833
3833
height | `float` | m | invalid:-1000 | The current height of the unmanned aircraft above the take-off location or the ground as indicated by height_reference. If unknown: -1000 m.
@@ -7312,7 +7312,7 @@ Flight stacks typically reset the setting to system defaults on reboot.
2 (Types) | Fence types to enable or disable as a bitmask. 0: field is unused/all fences should be enabled or disabled (for compatiblity reasons). Parameter is ignored if param1=2. | [FENCE_TYPE](#FENCE_TYPE)
7315
+
2 (Types) | Fence types to enable or disable as a bitmask. 0: field is unused/all fences should be enabled or disabled (for compatibility reasons). Parameter is ignored if param1=2. | [FENCE_TYPE](#FENCE_TYPE)
7316
7316
3 | Empty |
7317
7317
4 | Empty |
7318
7318
5 | Empty |
@@ -7387,7 +7387,7 @@ Enable/disable autotune.
7387
7387
Param (Label) | Description | Values
7388
7388
--- | --- | ---
7389
7389
1 (Enable) | Enable autotune (BOOL_FALSE: disable autotune). Values not equal to 0 or 1 are invalid. | BOOL
7390
-
2 (Axis) | Specify axes for which autotuning is enabled/disabled. 0 indicates the field is unused (for compatiblity reasons). If 0 the autopilot will follow its default behaviour, which is usually to tune all axes. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS)
7390
+
2 (Axis) | Specify axes for which autotuning is enabled/disabled. 0 indicates the field is unused (for compatibility reasons). If 0 the autopilot will follow its default behaviour, which is usually to tune all axes. | [AUTOTUNE_AXIS](#AUTOTUNE_AXIS)
Copy file name to clipboardExpand all lines: en/messages/development.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -554,8 +554,8 @@ The system manager component should then stream [CONTROL_STATUS](#CONTROL_STATUS
554
554
If the system manager component cannot grant control (because takeover requires permission), the request should be rejected with [MAV_RESULT_FAILED](#MAV_RESULT_FAILED).
555
555
The system manager component should then send this same command to the current owning GCS in order to notify of the request.
556
556
The owning GCS would ACK with [MAV_RESULT_ACCEPTED](#MAV_RESULT_ACCEPTED), and might choose to release control of the vehicle, or re-request control with the takeover bit set to allow permission.
557
-
In case it choses to re-request control with takeover bit set to allow permission, requestor GCS will only have 10 seconds to get control, otherwise owning GCS will re-request control with takeover bit set to disallow permission, and requestor GCS will need repeat the request if still interested in getting control.
558
-
Note that the pilots of both GCS should co-ordinate safe handover offline.
557
+
In case it choses to re-request control with takeover bit set to allow permission, requester GCS will only have 10 seconds to get control, otherwise owning GCS will re-request control with takeover bit set to disallow permission, and requester GCS will need repeat the request if still interested in getting control.
558
+
Note that the pilots of both GCS should coordinate safe handover offline.
559
559
560
560
Note that in most systems the only controlled component will be the "system manager component", and that will be the autopilot.
561
561
However separate GCS control of a particular component is also permitted, if supported by the component.
1 (Sysid requesting control) | System ID of GCS requesting control. 0 when command sent from GCS to autopilot (autopilot determines requesting GCS sysid from message header). Sysid of GCS requesting control when command sent by autopilot to controlling GCS. | |
3 (Allow takeover) | Enable automatic granting of ownership on request (by default reject request and notify current owner). 0: Ask current owner and reject request, 1: Allow automatic takeover. | |
572
-
4 (Request timeout) | Timeout in seconds before a request to a GCS to allow takeover is assumed to be rejected. This is used to display the timeout graphically on requestor and GCS in control. | min: 3 max: 60 | s
572
+
4 (Request timeout) | Timeout in seconds before a request to a GCS to allow takeover is assumed to be rejected. This is used to display the timeout graphically on requester and GCS in control. | min: 3 max: 60 | s
0 commit comments