This user guide is meant to be the main provider of support for QGroundControl. If you find incorrect or missing information please report an Issue.
Questions about how to use QGroundControl should be raised in the discussion server for the associated flight stack:
QGroundControl developers (and many regular/deeply-involved users) can be found on the #QGroundControl Slack channel.
This channel is a good place to keep up to date with the latest and greatest changes in QGroundControl.
The QGroundControl Gitter channel will be discontinued in March 2020.
Issues are used to track bugs against QGroundControl as well as feature requests for later versions. The current list of issues can be found on GitHub here.
Please contact our developers using the IM channels before creating GitHub issues!
Feature Requests should first be discussed on a developer IM channel. The developer team will direct you to create a feature request on Github if necessary (or refer you to the appropriate existing feature).
Bug reports should first be discussed on a developer IM channel (there are many cases where something that seems like a bug is actually a vehicle setup problem). The developer team will direct you to create an issue if necessary.
If you are directed to create an issue, please provide all information needed to reproduce the problem (OS, QGroundControl version/build, Autopilot version/release etc). The sections below explain how to get additional information that can help with debugging issues.
Console Logs can be helpful when diagnosing QGroundControl problems. For more information see: Console Logging.
Reporting Crashes from Windows Builds
When QGC crashes a crash dump file will be place in the Users LocalAppData directory. To navigate to that directory use the Start/Run command. You can bring this up window WinKey+R. Type into that
%localappdata% for Open and click Ok. Crash dumps will be in a
QGCCrashDumps folder in that directory. You should find a new .dmp file there. Add a link to that file in a GitHub Issue when reporting you problem.
Reporting Hangs from Windows Builds
If Windows is telling you the QGroundControl program is unresponsive use the following steps to report the hang:
- Open Task Manager (right-click TaskBar, select Task Manager)
- Switch to the Processes tab and local qgroundcontrol.exe
- Right-click on groundcontrol.exe and select Create Dump File
- Place the dump file in a public location
- Add a link to the .dmp file and above details in the GitHub issue.
Troubleshooting information is provided in two topics:
- QGC Installation/Configuration Problems - problems/solutions related to running QGroundControl on the host computer.
- QGC/Vehicle Interaction Problems - problems/solutions related to using QGroundControl to interact with a vehicle.
Help Improve these Docs!
Just like QGroundControl itself, the user guide is an open source, user created and supported GitBook. We welcome Pull Requests against the guide for fixes and/or updates.