The software is meant to guide you a in sequence of procedural steps to configure and tune your vehicle in a safe and time-efficient way.
Hence the two main use cases are:
- Use the ArduPilot Methodic Configurator software for the first time to create a vehicle configuration based on a pre-existing template
- Use the ArduPilot Methodic Configurator software after having created a vehicle from a template to edit existing vehicle configuration files to configure and tune a vehicle
But there are other use cases as well:
- Create a vehicle configuration based on a correctly configured vehicle
- Review and or edit configuration files without having the vehicle FC
- Use the correct default values
- Re-run the procedure after changing a vehicle component
- 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.
- Connect the flight controller to the computer using a USB cable.
- Wait at least 7 seconds.
- Open the ArduPilot Methodic Configurator software.
- The software should now automatically detect and connect to your flight controller.
- Select source template directory to use.
- Select the vehicle template that better resembles your vehicle, it does not need to fully match your vehicle.
- Give a name to your vehicle.
- Press Create vehicle configuration from template.
- 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.
- Press Save data and start configuration.
- 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. - You should now see the Parameter file editor and uploader window.
If something is not clear, read the ArduPilot Methodic Configurator user manual
- 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.
- Connect the flight controller to the computer using a USB cable.
- Wait at least 7 seconds.
- Open the ArduPilot Methodic Configurator software.
- The software should now automatically detect and connect to your flight controller.
- 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
- Edit all the components of your vehicle to match your own. Please scroll down and make sure you do not miss a property.
- Press Save data and start configuration.
- You should now see the Parameter file editor and uploader window.
- Proceed as explained in Section 6
If something is not clear, read the ArduPilot Methodic Configurator user manual
- Connect the flight controller to the computer using a USB cable.
- Wait at least 7 seconds.
- Open the ArduPilot Methodic Configurator software.
- The software should now automatically detect and connect to your flight controller.
- Select the vehicle template that better resembles your vehicle.
- select the
Use parameter values from connected FC, not from template files
checkbox - Give a name to your vehicle.
- Press Create vehicle configuration from template.
- Edit all the components of your vehicle to match your own in the Vehicle Component Editor window.
- Press Save data and start configuration.
- 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. - You should now see the Parameter file editor and uploader window.
- Follow the procedure to configure the vehicle parameters
If something is not clear, read the ArduPilot Methodic Configurator user manual
- Open the ArduPilot Methodic Configurator software.
- Select
Skip FC connection, just edit .param files on disk
button. - Open the vehicle configuration directory that you want to edit or review. double-click and step inside the directory that you want to use, not just select it
- Edit all the components of your vehicle to match your own in the Vehicle Component Editor window.
- Press Save data and start configuration.
- 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. - You should now see the Parameter file editor and uploader window.
the
Upload selected params to FC, and advance to next param file
button will be grayed out because there is no FC connected. - Follow the procedure to configure the vehicle parameters
If something is not clear, read the ArduPilot Methodic Configurator user manual
To get the correct default values for your board (if it does not support MAVFTP) you need to do:
cd VehicleConfigurarationDirectory
extract_param_defaults bin_log_file.bin > 00_default.param
- Connect the flight controller to the computer using a USB cable.
- Wait at least 7 seconds.
- Open the ArduPilot Methodic Configurator software.
- The software should now automatically detect and connect to your flight controller.
- Open the vehicle configuration directory that you want to edit or review. double-click and step inside the directory that you want to use, not just select it
- Edit all the components of your vehicle to match the component and/or connections changes you made in the Vehicle Component Editor window.
- Press Save data and start configuration.
- 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. - You should now see the Parameter file editor and uploader window.
- Now depending of the changes you made you will need to re-do some steps and can skip some others:
- FC changed - Need to redo all steps
- Frame and/or Take-off-weight - redo steps 19 and above
- RC Controller - redo step 05 and the RC parts of step 12
- RC Transmitter - Redo step 05 and the RC parts of step 12
- RC Receiver - redo step 05 and the RC parts of step 12
- Telemetry - redo step 06
- Battery Monitor - redo step 08
- Battery - redo step 08 and 19 and above if the weight changed
- ESC - redo step 07 and 19 and above
- motors - redo step 07 and 19 and above
- props - redo step 07, and 11 and above
- GNSS receiver - redo step 10
- Follow the procedure to configure the vehicle parameters
If something is not clear, read the ArduPilot Methodic Configurator user manual