Skip to content

Commit 97fe4e0

Browse files
committed
docs: Update tuning guide, usecases and screenshots.
1 parent ddf8f40 commit 97fe4e0

17 files changed

Lines changed: 391 additions & 190 deletions

TUNING_GUIDE_ArduCopter.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -131,14 +131,29 @@ So, [start the ArduPilot Methodic Configurator and select a vehicle that resembl
131131

132132
1. Close Mission Planner, if it is open on the PC.
133133
1. Connect the flight controller to the PC via a USB cable and wait 7 seconds.
134-
1. Open *ArduPilot Methodic Configurator*, and [connect it to the vehicle](USERMANUAL.md#step-1-flight-controller-connection).
134+
1. Open *ArduPilot Methodic Configurator*, and [connect it to the vehicle](USERMANUAL.md#step-1-flight-controller-connection).<br>
135135
![FC connection and parameter download](images/App_screenshot_FC_info_and_param_download.png)
136-
1. Now using [New](USERMANUAL.md#new) subsection
137-
![New vehicle](images/App_screenshot_Vehicle_directory1.png)
138-
1. From the existing templates, select the one most similar to your vehicle:
136+
1. Press the *Create a vehicle configuration directory from template* button.<br>
137+
![Create a vehicle configuration directory from template](images/App_screenshot_Vehicle_directory_create_from_template.png)
138+
1. Now using [New](USERMANUAL.md#new) subsection<br>
139+
![New vehicle](images/App_screenshot_Vehicle_directory_create_from_template_source.png)
140+
1. From the existing templates, select the one most similar to your vehicle:<br>
139141
![New vehicle](images/App_screenshot_Vehicle_overview.png)
140-
1. select the destination directory, give it a name and press `Create a vehicle configuration directory from template`
141-
1. On the component editor window, **add all the details of the components of your system** as we did in [Section 1.2](#12-our-example-vehicle):
142+
1. Select the options that meet your requirements:
143+
- *Copy vehicle image from template* - Use the template vehicle image in your created vehicle configuration directory. This image helps identify the vehicle configuration.
144+
- *Blank component data* - Create a new blank vehicle configuration, with no component data from the template.
145+
- *Reset flight controller parameters to their defaults* - Reset the flight controller parameters to their default values when creating a new vehicle configuration.
146+
Helps avoid issues caused by incorrect or incompatible parameter settings. WARNING: This will delete all parameters stored on the flight controller.
147+
- *Infer component specifications and FC connections from FC parameters, not from template files* - When creating a new vehicle configuration, extract component
148+
specifications and connection information directly from the connected flight controller instead of using the specifications defined in the template files.
149+
This helps ensure the configuration accurately matches your actual hardware.
150+
Note: you will not see the information from the correctly configured vehicle template. This option is only available when a flight controller is connected.
151+
- *Use parameter values from connected FC, not from template files* - Use the parameter values from the connected flight controller instead of the template files when
152+
creating a new vehicle configuration directory from a template.
153+
Only makes sense if your FC has already been correctly configured. This option is only available when a flight controller is connected.
154+
- *Blank parameter change reason* - Do not use the parameters change reason from the template.
155+
1. Select the destination directory, give it a name, and press the *Create a vehicle configuration directory from template* button.
156+
1. On the component editor window, **add all the details of the components of your system** as we did in [Section 1.2](#12-our-example-vehicle):<br>
142157
![Component editor window](images/App_screenshot_Component_Editor.png)
143158

144159
Most optional information fields are only visible in `normal` GUI complexity mode.

TUNING_GUIDE_ArduPlane.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ So, [start the ArduPilot Methodic Configurator and select a vehicle that resembl
134134
1. Open *ArduPilot Methodic Configurator*, and [connect it to the vehicle](USERMANUAL.md#step-1-flight-controller-connection).
135135
![FC connection and parameter download](images/App_screenshot_FC_info_and_param_download.png)
136136
1. Now using [New](USERMANUAL.md#new) subsection
137-
![New vehicle](images/App_screenshot_Vehicle_directory1.png)
137+
![New vehicle](images/App_screenshot_Vehicle_directory_create_from_template_source.png)
138138
1. From the existing templates, select the one most similar to your vehicle:
139139
![New vehicle](images/App_screenshot_Vehicle_overview.png)
140140
1. select the destination directory, give it a name and press `Create a vehicle configuration directory from template`

TUNING_GUIDE_Heli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ So, [start the ArduPilot Methodic Configurator and select a vehicle that resembl
133133
1. Open *ArduPilot Methodic Configurator*, and [connect it to the vehicle](USERMANUAL.md#step-1-flight-controller-connection).
134134
![FC connection and parameter download](images/App_screenshot_FC_info_and_param_download.png)
135135
1. Now using [New](USERMANUAL.md#new) subsection
136-
![New vehicle](images/App_screenshot_Vehicle_directory1.png)
136+
![New vehicle](images/App_screenshot_Vehicle_directory_create_from_template_source.png)
137137
1. From the existing templates, select the one most similar to your vehicle:
138138
![New vehicle](images/App_screenshot_Vehicle_overview.png)
139139
1. select the destination directory, give it a name and press `Create a vehicle configuration directory from template`

TUNING_GUIDE_Rover.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ So, [start the ArduPilot Methodic Configurator and select a vehicle that resembl
134134
1. Open *ArduPilot Methodic Configurator*, and [connect it to the vehicle](USERMANUAL.md#step-1-flight-controller-connection).
135135
![FC connection and parameter download](images/App_screenshot_FC_info_and_param_download.png)
136136
1. Now using [New](USERMANUAL.md#new) subsection
137-
![New vehicle](images/App_screenshot_Vehicle_directory1.png)
137+
![New vehicle](images/App_screenshot_Vehicle_directory_create_from_template_source.png)
138138
1. From the existing templates, select the one most similar to your vehicle:
139139
![New vehicle](images/App_screenshot_Vehicle_overview.png)
140140
1. select the destination directory, give it a name and press `Create a vehicle configuration directory from template`

0 commit comments

Comments
 (0)