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/messages/common.md
+8-3Lines changed: 8 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,12 @@ The general system state. If the system is following the MAVLink standard, the s
84
84
85
85
### SYSTEM_TIME (2) {#SYSTEM_TIME}
86
86
87
-
The system time is the time of the master clock, typically the computer clock of the main onboard computer.
87
+
The system time is the time of the master clock.
88
+
89
+
This can be emitted by flight controllers, onboard computers, or other components in the MAVLink network.
90
+
Components that are using a less reliable time source, such as a battery-backed real time clock, can choose to match their system clock to that of a [SYSTEM_TYPE](#SYSTEM_TYPE) that indicates a more recent time.
91
+
This allows more broadly accurate date stamping of logs, and so on.
92
+
If precise time synchronization is needed then use TIMESYNC instead.
@@ -1881,7 +1886,7 @@ Battery information. Updates GCS with flight controller battery status. Smart ba
1881
1886
| <span class='ext'>time_remaining</span> <a href='#mav2_extension_field'>++</a> | `int32_t` | s | invalid:0 | Remaining battery time, 0: autopilot does not provide remaining battery time estimate |
1882
1887
| <span class='ext'>charge_state</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | | [MAV_BATTERY_CHARGE_STATE](#MAV_BATTERY_CHARGE_STATE) | State for extent of discharge, provided by autopilot for warning or external reactions |
1883
1888
| <span class='ext'>voltages_ext</span> <a href='#mav2_extension_field'>++</a> | `uint16_t[4]` | mV | invalid:[0] | Battery voltages for cells 11 to 14. Cells above the valid cell count for this battery should have a value of 0, where zero indicates not supported (note, this is different than for the voltages field and allows empty byte truncation). If the measured value is 0 then 1 should be sent instead. |
1884
-
| <span class='ext'>mode</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | | [MAV_BATTERY_MODE](#MAV_BATTERY_MODE) | Smart battery mode. Default (0) is that battery mode reporting is not supported or battery is in normal-use mode. |
1889
+
| <span class='ext'>mode</span> <a href='#mav2_extension_field'>++</a> | `uint8_t` | | [MAV_BATTERY_MODE](#MAV_BATTERY_MODE) | Battery mode. Default (0) is that battery mode reporting is not supported or battery is in normal-use mode. |
1885
1890
| <span class='ext'>fault_bitmask</span> <a href='#mav2_extension_field'>++</a> | `uint32_t` | | [MAV_BATTERY_FAULT](#MAV_BATTERY_FAULT) | Fault/health indications. These should be set when charge_state is [MAV_BATTERY_CHARGE_STATE_FAILED](#MAV_BATTERY_CHARGE_STATE_FAILED) or [MAV_BATTERY_CHARGE_STATE_UNHEALTHY](#MAV_BATTERY_CHARGE_STATE_UNHEALTHY) (if not, fault reporting is not supported). |
1886
1891
1887
1892
### AUTOPILOT_VERSION (148) {#AUTOPILOT_VERSION}
@@ -4634,7 +4639,7 @@ Enumeration for battery charge states.
4634
4639
4635
4640
### MAV_BATTERY_MODE {#MAV_BATTERY_MODE}
4636
4641
4637
-
Smart battery mode. Note, the normal operation mode (i.e. when flying) should be reported as [MAV_BATTERY_MODE_UNKNOWN](#MAV_BATTERY_MODE_UNKNOWN) to allow message trimming in normal flight.
4642
+
Battery mode. Note, the normal operation mode (i.e. when flying) should be reported as [MAV_BATTERY_MODE_UNKNOWN](#MAV_BATTERY_MODE_UNKNOWN) to allow message trimming in normal flight.
The [C-UART Interface Example](https://github.com/mavlink/c_uart_interface_example) is a simple C example of a MAVLink to UART interface for Unix-like systems.
The example source code demonstrates how to set up serial communication between Pixhawk and an offboard computer via USB or a telemetry radio, how to put the vehicle in offboard mode, and how to send and receive MAVLink messages over the interface.
Source code and instructions for how to run the example can be found in the Github repo: [mavlink/c_uart_interface_example](https://github.com/mavlink/c_uart_interface_example)
-[ArduPilot/pymavlink/examples](https://github.com/ArduPilot/pymavlink/tree/master/examples) - The Pymavlink submodule contains a number of simple examples.
6
-
-[ArduSub Pymavlink Docs](https://www.ardusub.com/developers/pymavlink.html) - A number of useful examples, which use ArduSub and MAVProxy
-[MAVProxy](http://ardupilot.github.io/MAVProxy/html/development/index.html)is a command line, console based UAV ground station software package for MAVLink based systems built on Pymavlink.
11
-
-It demonstrates most of the features of using the MAVLink module.
12
-
-The source code can be found here: https://github.com/ArduPilot/MAVProxy
0 commit comments