Mirror
/
ardupilot
mirror of https://github.com/ArduPilot/ardupilot
5
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ardupilot/libraries/GCS_MAVLink
History
Andrew Tridgell aeb010b6e9 AHRS: added AHRS specific MAVLink headers 2012-03-19 17:35:20 +11:00
..
doc Mavlink update 2011-02-11 11:04:52 +00:00
include AHRS: added AHRS specific MAVLink headers 2012-03-19 17:35:20 +11:00
include_v1.0 AHRS: added AHRS specific MAVLink headers 2012-03-19 17:35:20 +11:00
message_definitions MAVLink: rename DCM message to AHRS 2012-03-19 17:29:01 +11:00
message_definitions_v1.0 MAVLink: rename DCM message to AHRS 2012-03-19 17:29:01 +11:00
missionlib MAVLink: added missing files from recent update 2011-08-13 06:30:29 +00:00
.gitignore MAVLink: added missing files from recent update 2011-08-13 06:30:29 +00:00
GCS_MAVLink.cpp mavlink: make it possible to build with mavlink 1.0 headers 2011-10-24 10:20:36 +11:00
GCS_MAVLink.h mavlink: make it possible to build with mavlink 1.0 headers 2011-10-24 10:20:36 +11:00
Mavlink_compat.h adapt Mavlink_compat.h to AP_Param 2012-02-13 16:22:51 +11:00
README Mavlink update 2011-03-16 10:09:22 +00:00
license.txt MavLink Update 2011-02-08 23:16:58 +00:00
sync Updated GCS_MAVLink to match mavlink master. 2011-08-05 08:18:08 +00:00

README 

MAVLink Micro Air Vehicle Message Marshalling Library

This is a library for lightweight communication between
Micro Air Vehicles (swarm) and/or ground control stations.
It serializes C-structs for serial channels and can be used with
any type of radio modem.

For help, please visit the mailing list: http://groups.google.com/group/mavlink

MAVLink is licensed under the terms of the Lesser General Public License of the Free Software Foundation (LGPL).
As MAVLink is a header-only library, compiling an application with it is considered "using the libary", not a derived work. MAVLink can therefore be used without limits in any closed-source application without publishing the source code of the closed-source application.

To generate/update packets, select mavlink_standard_message.xml
in the QGroundControl station settings view, select mavlink/include as
the output directory and click on "Save and Generate".
You will find the newly generated/updated message_xx.h files in
the mavlink/include/generated folder.

To use MAVLink, #include the <mavlink.h> file, not the individual
message files. In some cases you will have to add the main folder to the include search path as well. To be safe, we recommend these flags:

gcc -I mavlink/include -I mavlink/include/<your message set, e.g. common>

For more information, please visit:

http://qgroundcontrol.org/mavlink/

(c) 2009-2011 Lorenz Meier <mail@qgroundcontrol.org>