MethodicConfigurator

Quick start guide

Do you need this software at all?

1. Quick overview of the entire process

To methodically build, configure and tune ArduPilot vehicles follow this sequence of steps:

1.1 Select the vehicle components

• while choosing an Autopilot and other hardware components avoid these components
• Use ecalc for multirotor to select the propulsion system.
• follow hardware best practices

1.2 Install Software

• Install ArduPilot Methodic Configurator
• Install Mission Planner
• Install ArduPilot

1.3 Input vehicle components and component connections into ArduPilot Methodic Configurator

The software needs this information to automatically pre-select configuration settings relevant to your specific vehicle

• Start the ArduPilot Methodic Configurator and input select a vehicle that resembles yours and input vehicle components and component connections information into the ArduPilot Methodic Configurator component editor window

1.4 Perform IMU temperature calibration before assembling the autopilot into the vehicle (optional)

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.

• start the software
• Perform IMU temperature calibration

1.5 Assemble all components except the propellers

Assemble and connect all components. Make sure you follow best practices

1.6 Basic mandatory configuration

Again using the ArduPilot Methodic configurator software GUI perform the following steps:

• 04_board_orientation.param flight controller orientation
• 05_remote_controller.param remote controller connections and protocol
• 06_telemetry.param telemetry transceiver connections and protocol (optional)
• 07_esc.param Electronic-Speed-Controller connections and protocol
• 08_batt1.param Battery health and state of charge monitoring
• 10_gnss.param GNSS receiver connection and protocol
• 11_initial_atc.param initial attitude PID gains (vehicle size dependent)

Now use Mission Planner to do:

• 12_mp_setup_mandatory_hardware.param calibrate vehicle sensors

And continue with the ArduPilot Methodic configurator software GUI:

• 13_general_configuration.param general misc configuration
• Test if the hardware diagnostics are OK
• 14_logging.param configure Dataflash/SDCard logging (black box data)
• 15_motor.param motor order and direction tests. ESC linearization.
• 16_pid_adjustment.parm attitude PID gains (vehicle size dependent)
• 17_remote_id.param required by law in many countries
• 18_notch_filter_setup.param to remove motor noise, reduce power consumption and increase flight stability

1.7 Assemble propellers and perform the first flight

Now that all mandatory configuration steps are done you can perform the first flight

1.8 Minimalistic mandatory tuning

These are the very minimum tuning steps required for a stable flight:

• Load the .bin log file from the first flight into Notch filter webtool
• 19_notch_filter_results.param use the webtool information to configure the notch filter(s)
• 20_throttle_controller.param the altitude controller depends on the power-to-thrust ratio found in the first flight
• 21_ekf_config.param sometimes the EKF3 needs a tune to maintain altitude
• 22_quick_tune_setup.param and 23_quick_tune_results.param, you need lua scripting support to do this if not available you can tune manually.

That is it, if you are impatient and do not want an optimized vehicle you can skip to everyday use.

1.9 Standard tuning (optional)

These are the standard tuning steps required for an optimized flight:

• 24_inflight_magnetometer_fit_setup.param, use lua scripted flight path or fly manually, store the results using 25_inflight_magnetometer_fit_results.param, use the magfit webtool to calculate a file that the ardupilot methodic configurator can use
• 26_quick_tune_setup.param and 27_quick_tune_results.param Redo quick-tune now that the compass magnetic interference is fully calibrated
• 28_evaluate_the_aircraft_tune_ff_disable.param and 29_evaluate_the_aircraft_tune_ff_enable.param
• 30_autotune_roll_setup.param and 31_autotune_roll_results.param tune roll axis rate and angle PIDs
• 32_autotune_pitch_setup.param and 33_autotune_pitch_results.param tune pitch axis rate and angle PIDs
• 34_autotune_yaw_setup.param and 35_autotune_yaw_results.param tune yaw axis rate and angle PIDs
• 36_autotune_yawd_setup.param and 37_autotune_yawd_results.param tune yawd axis rate and angle PIDs
• 38_autotune_roll_pitch_retune_setup.param and 39_autotune_roll_pitch_retune_results.param re-tune roll and pitch pitch axis rate and angle PIDs

Now the standard tuning is complete you can skip to everyday use

1.10 Improve altitude under windy conditions (optional)

• 40_windspeed_estimation.param estimates the wind speed
• 41_barometer_compensation.param Uses the estimated wind speed to improve altitude stability

1.11 System identification for analytical PID optimization (optional)

• 42_system_id_roll.param, 43_system_id_pitch.param, 44_system_id_yaw.param
• 46_analytical_pid_optimization.param

1.12 Position controller tuning (optional)

• 47_position_controller.param, 48_guided_operation.param, 49_precision_land.param

1.13 Everyday use

Now that tuning and configuration are done, some logging and tests can be disabled and some more safety features enabled:

• 53_everyday_use.param

Enjoy your properly configured vehicle.

The following sections describe each step of the procedure in more detail.

2. Install ArduPilot Methodic Configurator software on a PC or Mac

1. Download and install ArduPilot Methodic Configurator software.

3. Install Mission Planner software on a PC or Mac

1. Download and install Mission Planner.
2. Make sure to install all the recommended device drivers when asked to.

4. Install ArduPilot firmware on the flight controller

1. Connect the flight controller to the computer using a USB cable.
2. Open Mission Planner software.
3. Go to SETUP > Install Firmware select your vehicle type and install version 4.3.8 or newer of the ArduPilot firmware onto the flight controller.
4. Wait until the firmware download is complete.
5. Disconnect the USB cable from the flight controller.

5. Use the ArduPilot Methodic Configurator software for the first time

1. Close all other GCS software (MissionPlanner, QGroundControl, MAVProxy, DroneKit-Python, APM Planner 2.0, UgCS, LOGOS, Tower, AndroPilot, etc) the ArduPilot Methodic Configurator needs connection exclusivity.
2. Connect the flight controller to the computer using a USB cable.
3. Wait at least 7 seconds.
4. Open the ArduPilot Methodic Configurator software.
5. The software should now automatically detect and connect to your flight controller.
6. Select source template directory to use.
7. Select the vehicle template that better resembles your vehicle, it does not need to fully match your vehicle.
8. Give a name to your vehicle.
9. Press Create vehicle configuration from template.
10. Edit all the components of your vehicle to match your own in the Vehicle Component Editor window. Please scroll down and make sure you do not miss a property.
11. Press Save data and start configuration.
12. The application will validate your input. If issues are found the problematic fields’ background will be marked in red color. Correct those entries and press the Save data and start configuration button again.
13. You should now see the Parameter file editor and uploader window.

If something is not clear, read the ArduPilot Methodic Configurator user manual

6. Configure the vehicle’s parameters in a traceable way

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:

• Read all the documentation links displayed at the top of the GUI (marked with the big red number 4),
• Edit the parameter’s New value and Reason changed fields to match your vehicle (marked with the big red number 5),
  • The Reason changed field is extremely important because:
    • if forces you to think, causing rational decisions instead of impulsive ones
    • justifies your decisions on a vehicle certification process required in most countries
    • allows for someone else to see if you know what you are doing
    • allows for someone else (or yourself after a few weeks) to understand your rationale
• Press Del and/or Add buttons to delete or add parameters respectively (marked with the big red number 5),
• If necessary scroll down using the scroll bar on the right and make sure you edit all parameters,
• Press Upload selected params to FC, and advance to next param file (marked with the big red number 7),
• Repeat from the top until the program automatically closes.

7. Use the ArduPilot Methodic Configurator software after having created a vehicle from a template

1. Close all other GCS software (MissionPlanner, QGroundControl, MAVProxy, DroneKit-Python, APM Planner 2.0, UgCS, LOGOS, Tower, AndroPilot, etc) the ArduPilot Methodic Configurator needs connection exclusivity.
2. Connect the flight controller to the computer using a USB cable.
3. Wait at least 7 seconds.
4. Open the ArduPilot Methodic Configurator software.
5. The software should now automatically detect and connect to your flight controller.
6. Open the vehicle configuration directory that you created in the Use the ArduPilot Methodic Configurator software for the first time. double-click and step inside the directory that you want to use, not just select it
7. Edit all the components of your vehicle to match your own. Please scroll down and make sure you do not miss a property.
8. Press Save data and start configuration.
9. You should now see the Parameter file editor and uploader window.
10. Proceed as explained in Section 6

Congratulations your flight controller is now fully configured in the safest and fastest way publicly known.

There is also documentation on other use cases.

This site is open source. Improve this page.