Lint | Quality | Test | Deploy | Maintain |
---|---|---|---|---|
![]() |
||||
ArduPilot Methodic Configurator is a software, developed by ArduPilot developers, that semi-automates a clear, proven and safe configuration sequence for ArduCopter drones. We are working on extending it to ArduPlane, Heli and Rover vehicles. But for those it is still very incomplete.
Let’s compare it with the traditional tool used to configure ArduPilot: a generalist Ground Control Station (GCS) software.
Feature | Mission Planner, QGroundControl, … etc | ArduPilot Methodic Configurator |
---|---|---|
configuration type | manual 1 | semi-automated 2 |
explains what to do | No | Yes |
explains when to do something | No, leaves you lost | Yes, explains the path |
explains why do something | No | Yes |
configuration method | a different menu for each task, some tasks have no menu, so you need to dig into the 1200 parameters | each task only presents you a relevant subset of parameters |
parameter documentation | Yes, only on the full-parameter tree view | Yes |
displays relevant documentation | No | Yes |
makes sure you do not forget a step | No | Yes |
checks that parameters get correctly uploaded | No | Yes |
reuse params in other vehicles | No, unless you hand edit files | Yes, out-of-the-box |
documents why you changed each parameter | No | Yes |
tutorials and learning resources | No, scattered and not integrated | Yes, context-aware help integrated |
auto. install lua scripts on the FC | No | Yes |
It’s simple graphical user interface (GUI) manages and visualizes ArduPilot parameters, parameter files and documentation.
No visible menus, no hidden menus, no complicated options, what you see is what gets changed.
To methodically build, configure and tune ArduPilot vehicles follow this sequence of steps:
The software needs this information to automatically pre-select configuration settings relevant to your specific vehicle
IMU temperature calibration reduces the probability of Accel inconsistent and Gyro inconsistent errors and reduces the time required to arm the vehicle. IMU temperature calibration requires lowering the temperature of the autopilot (flight controller) to circa -20°C. That is harder to do once the autopilot is assembled inside the vehicle, hence it is done now.
Assemble and connect all components. Make sure you follow best practices
Again using the ArduPilot Methodic configurator software GUI perform the following steps:
Now use Mission Planner to do:
And continue with the ArduPilot Methodic configurator software GUI :
Now that all mandatory configuration steps are done you can perform the first flight
These are the very minimum tuning steps required for a stable flight:
.bin
log file from the first flight into Notch filter webtoolThat is it, if you are impatient and do not want an optimized vehicle you can skip to everyday use.
These are the standard tuning steps required for an optimized flight:
Now the standard tuning is complete you can skip to everyday use
Now that tuning and configuration are done, some logging and tests can be disabled and some more safety features enabled:
Enjoy your properly configured vehicle.
The following sections describe each step of the procedure in more detail.
Install ArduPilot Methodic Configurator on MS windows, linux or MacOS
Install the latest Mission Planner version
Install the latest ArduPilot firmware on your flight controller board
See the Use the ArduPilot Methodic Configurator software for the first time usecase.
The following simple loop is presented as welcome instructions:
Now do this in a loop until the software automatically closes or you are asked to close the software:
See the Use the ArduPilot Methodic Configurator software after having created a vehicle from a template usecase.
Congratulations your flight controller is now fully configured in the safest and fastest way publicly known.
There is also documentation on other use cases and a detailed but generic Usermanual.
See the install instructions
Need help or support
Want to help us and contribute?
To meet the Software requirements a software architecture was designed and implemented.
The software is available in multiple languages.
On MS Windows the language is selected during install and that selection is stored in the desktop icon.
You can manually create multiple desktop icons, each will run the software in a different language.
On linux and MacOS the language is selectable by the --language
command line argument.
See contributing page if you want to help us translate the software into your language.
To use and develop this software you must obey the ArduPilot Methodic Configurator Code of Conduct.
This software is cost free. This project is licensed under the GNU General Public License v3.0.
It builds upon other open-source software packages