Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ about how to tell what messages are supported #112

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add FAQ about how to tell what messages are supported #112

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c890144
Add FAQ about message support
hamishwillee Sep 17, 2018
a55b857
Merge branch 'master' into message_support
hamishwillee Sep 20, 2018
cd1eca5
Fix typo
hamishwillee Sep 20, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions en/about/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,24 @@

<dt>How reliable is MAVLink?</dt>
<dd>Very. MAVLink has been used since 2009 to communicate between many different vehicles, ground stations (and other nodes) over varied and challenging communication channels (high latency/noise). It provides methods for detecting packet drops, and the well-established ITU X.25 checksum for packet corruption detection.</dd>

<dt>How can I tell which messages are supported by a particular system?</dt>
<dd>
Each system is expected to document its own support for MAVLink microservices, messages and commands.

Unfortunately this information is often unavailable and/or difficult to infer from code.
Some links/information that you may find helpful are provided below:

<ul>
<li>Coarse-grained capabilities can be obtained from <a href="../messages/common.md#AUTOPILOT_VERSION">AUTOPILOT_VERSION.capabilities</a> (see <a href="../messages/common.md#MAV_PROTOCOL_CAPABILITY">MAV_PROTOCOL_CAPABILITY</a>).</li>
<li>The basic set of Mission Commands supported in <emphasis>QGroundControl</emphasis> should work on most systems (e.g. commands for takeoff, landing, waypoints).</li>
<li>The messages/commands in a dialect file typically work for the associated system (unless deprecated). <strong>Common.xml</strong> contains some commands that may not be implemented.</li>
<li>ArduPilot lists some (non exhaustive) information about supported messages: <a href="http://ardupilot.org/copter/docs/mission-command-list.html ">Mission Command List (Copter)</a>, <a href="http://ardupilot.org/copter/docs/common-mavlink-mission-command-messages-mav_cmd.html">MAVLink Mission Command Messages (MAV_CMD)</a>, <a href="http://ardupilot.org/dev/docs/copter-commands-in-guided-mode.html">Copter Commands (Guided Mode)</a>, <a href="http://ardupilot.org/dev/docs/plane-commands-in-guided-mode.html">Plane Commands (Guided Mode)</a>.</li>
<li>ArduPilot messages are handled in <a href="https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/GCS_Mavlink.cpp">GCS_Mavlink.cpp</a> (there is a version for each vehicle type). Commands in missions are handled in <a href="https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/mode_auto.cpp">mode_auto.cpp</a> (Copter), <a href="https://github.com/ArduPilot/ardupilot/blob/master/ArduPlane/commands_logic.cpp">commands_logic.cpp</a> (Plane).</li>
<li>PX4 messages are handled in <a href="https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_receiver.cpp">mavlink_receiver.cpp</a> and <a href="https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_messages.cpp">mavlink_messages.cpp</a>. Commands in missions are handled in <a href="https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_mission.cpp">mavlink_mission.cpp</a>.</li>
</ul>
</dd>

</dl>


Expand Down