ardupilot

History

Andrew Tridgell 6d059b8eba Revert "added support for AP_ADC MAVLink packet" This reverts commit a65a2dda2c1bfa95437880227a3abddc95b329f5. I am reverting this not for any sane reason, but because my 3 APM boards now lock up on any I2C operation, and I don't know why. I can't see how this change could have caused it, but I don't want to take the chance.		2011-09-10 22:00:29 +02:00
..
doc	Mavlink update	2011-02-11 11:04:52 +00:00
include	Revert "added support for AP_ADC MAVLink packet"	2011-09-10 22:00:29 +02:00
message_definitions	Revert "added support for AP_ADC MAVLink packet"	2011-09-10 22:00:29 +02: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	BetterSerial has txspace() now	2011-09-04 22:52:22 +00:00
GCS_MAVLink.h	BetterSerial has txspace() now	2011-09-04 22:52:22 +00: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>