40 | These messages define the common message set, which is the reference message set implemented by most ground control stations and autopilots. 41 |
42 | 43 | transformToXML($xml_doc)) 46 | { 47 | echo $html; 48 | } 49 | else 50 | { 51 | trigger_error("XSL transformation failed",E_USER_ERROR); 52 | } 53 | 54 | ?> 55 | 56 |
60 | Messages are defined by the common.xml file. The C packing/unpacking code is generated from this specification, as well as the HTML documentaiton in the section above.
61 |
62 | The XML displayed here is updated on every commit and therefore up-to-date.
63 |
Including files:
Field Name | 39 |Type | 40 |Description | 41 |
---|
60 | The Official MAVLink message documentation contains additional information, including field units and enum values. 61 |
62 | 63 |The current MAVLink version is 2.
Value | 80 |Field Name | 81 |Description | 82 |
---|
MAVLink Include Files:
16 |MAVLink commands (MAV_CMD) and messages are different! These commands define the values of up to 7 parameters that are packaged INSIDE specific messages used in the Mission Protocol and Command Protocol. Use commands for actions in missions or if you need acknowledgment and/or retry logic from a request. Otherwise use messages.
[Message]
39 |
Field Name | 45 |Type | 46 | 47 |Units | 49 |Values | 53 |Description | 56 |
---|
The current MAVLink version is 2.
This file has protocol dialect:
Value | 113 |Field Name | 114 |Description | 115 |
---|
Param (:Label) | 141 |Description | 142 | 143 |Values | 145 |Units | 149 |
---|
WORK IN PROGRESS:
DEPRECATED: