Differences

This shows you the differences between two versions of the page.

Link to this comparison view

mavlink:start [2018/02/14 05:21]
hamishwillee
mavlink:start [2018/02/25 23:21] (current)
hamishwillee Remove a few more broken links to migrated content
Line 1: Line 1:
 ~~NOTOC~~ ~~NOTOC~~
  
-[[https://​mavlink.io/​en/​|MAVLINK DOCUMENTATION HAS MOVED HERE!]] The remainder of this documentation is being migrated and deleted.+**[[https://​mavlink.io/​en/​|MAVLINK DOCUMENTATION HAS MOVED HERE!]] The remainder of this documentation is being migrated and deleted. 
 +** 
 +**Broken links, etc should be ignored - the content has either been moved or is no longer relevant.**
  
 ====== MAVLink Micro Air Vehicle Communication Protocol ====== ====== MAVLink Micro Air Vehicle Communication Protocol ======
- 
- 
  
 {{:​mavlink:​mavlink-logo.png?​400&​nolink|MAVLink Logo}} {{:​mavlink:​mavlink-logo.png?​400&​nolink|MAVLink Logo}}
Line 32: Line 32:
   * [[release_11]]   * [[release_11]]
   * [[mission_interface]]   * [[mission_interface]]
-    * [[waypoint_protocol]] 
-    * [[parameter_protocol]] 
-    * [[image_transmission_protocol]] 
     * [[control_interface]]     * [[control_interface]]
-  * [[http://​mavlink.org/​messages/​common|Common MAVLink Messages]] 
  
  
Line 43: Line 39:
  
 ====== MAVLink Code and Generator ====== ====== MAVLink Code and Generator ======
- 
-There is a "​common message set" containing widely used messages, which is distributed as header-only C library. If you like to use your own custom messages, you can generate these with the [[:​mavlink:​generator]] or [[http://​qgroundcontrol.org|QGroundControl]]. 
- 
-The MAVLink message definitions and generator code is hosted at: 
- 
-  * https://​github.com/​mavlink/​mavlink/​ 
- 
-Installation / usage instructions can be found at: 
- 
-  * [[:​mavlink:​installation]] 
- 
-Instructions how to use the generator can be found at: 
- 
-  * [[:​mavlink:​generator]] 
  
 Instructions how to package MAVLink releases (**developers only**) can be found here: Instructions how to package MAVLink releases (**developers only**) can be found here:
Line 65: Line 47:
  
 There are by now many systems and software packages using MAVLink: There are by now many systems and software packages using MAVLink:
- 
-==== MAVLink Mailing List and Developers ==== 
- 
-  * Mailing list http://​groups.google.com/​group/​mavlink 
-  * Maintainer: Lorenz Meier, <​lm@inf.ethz.ch>​ 
-  * Developer team: Lorenz Meier, Andrew Tridgell, James Goppert 
  
 ==== Autopilots using MAVLink ==== ==== Autopilots using MAVLink ====
Line 113: Line 89:
  
 ====== Frequently Asked Questions (FAQ) ====== ====== Frequently Asked Questions (FAQ) ======
- 
-=== Upgrading from 0.9.0 to 1.0.0 === 
- 
-  * **Q: Is the upgrade easily done?** - Yes, v.1.0.0 is almost fully API-compatible with v.0.9.0. Only a few messages have changed, all protocol-functions like the message parsing (mavlink_parse_char) are fully compatible. 
-  * **Q: What are the main benefits from upgrading?​** - 1. MAVLink now uses the little-endian wire encoding, which makes is a lot more efficient on most platforms. It still supports little and big endian platforms. 2. It now checks the packet format of each message, so if two communication partners have different formats for the same message it will detect this mismatch. 3. It now has support for smaller message buffers. 4. The parameter protocol now supports 32 unsigned and signed integer and float values. 5. MAVLink now supports IEEE 754 double precision floating point numbers. 6. All messages are tested with an automatically generated test suite, making the protocol even safer to use. 7. Some messages have been cleaned up to better suit actual flight use. 8. MAVLink comes per default now with C/C++ and Python support. 
-  * **Q: Is the new version to be used soon?** - Yes, QGroundControl is fully ported to it and ArduPilotMega and PIXHAWK already are porting their software. Soon all adopters will have ported to the new version, simply because it is not too much effort. 
  
  
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported