diff --git a/QUICKSTART.md b/QUICKSTART.md
new file mode 100644
index 0000000..3f08433
--- /dev/null
+++ b/QUICKSTART.md
@@ -0,0 +1,83 @@
+# Quick start guide
+
+## 1. Install *ArduPilot Methodic Configurator* software on a PC or Mac
+
+1. Download and install [ArduPilot Methodic Configurator](https://github.com/ArduPilot/MethodicConfigurator/releases/tag/latest) software.
+
+
+
+
+
+
+
+
+
+## 2. Install *Mission Planner* software on a PC or Mac
+
+1. Download and install [Mission Planner](https://firmware.ardupilot.org/Tools/MissionPlanner/).
+1. Make sure to install all the recommended device drivers when asked to.
+
+## 3. Install *ArduPilot* firmware on the flight controller
+
+1. Connect the flight controller to the computer using a USB cable.
+1. Open *Mission Planner* software.
+1. 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.
+1. Wait until the firmware download is complete.
+1. Disconnect the USB cable from the flight controller.
+
+## 4. Use the *ArduPilot Methodic Configurator* software for the first time
+
+1. Connect the flight controller to the computer using a USB cable.
+1. Wait at least 7 seconds.
+1. Open the *ArduPilot Methodic Configurator* software.
+1. The software should now automatically detect and connect to your flight controller.
+
+1. Select the vehicle template that better resembles your own vehicle.
+
+
+1. Give a name to your vehicle.
+
+1. Press *Create vehicle configuration from template*.
+
+1. Edit all the components of your vehicle to match your own in the *vehicle Component Editor* window.
+
+1. Press *Save data and start configuration*.
+1. 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.
+1. You should now see the *Parameter file editor and uploader* window.
+
+
+If something is not clear, read the [ArduPilot Methodic Configurator user manual](USERMANUAL.md)
+
+## 5. 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),
+- Press *Del* and/or *Add* buttons to delete or add parameters respectively (marked with the big red number 5),
+- Press *Upload selected params to FC, and advance to next param file* (marked with the big red number 7),
+- Repeat until the program automatically closes.
+
+
+## 6. Use the *ArduPilot Methodic Configurator* software after having created a vehicle from template
+
+1. Connect the flight controller to the computer using a USB cable.
+1. Wait at least 7 seconds.
+1. Open the *ArduPilot Methodic Configurator* software.
+1. The software should now automatically detect and connect to your flight controller.
+
+1. Open the vehicle configuration directory that you created in the [Use the *ArduPilot Methodic Configurator* software for the first time](#4-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
+1. Edit all the components of your vehicle to match your own.
+
+1. Press *Save data and start configuration*.
+1. You should now see the *Parameter file editor and uploader* window.
+
+1. Proceed as explained on [section 5](#5-configure-the-vehicles-parameters-in-a-traceable-way)
+Congratulations your flight controller is now fully configured in the safest and fastest way publicly know.
diff --git a/README.md b/README.md
index 8eacaba..5ab5f27 100644
--- a/README.md
+++ b/README.md
@@ -8,13 +8,16 @@
| | | [](https://github.com/ArduPilot/MethodicConfigurator/actions/workflows/coverage.yml) | [](https://github.com/ArduPilot/MethodicConfigurator/actions/workflows/windows_build.yml) |
Amilcar Lucas's ArduPilot Methodic Configurator is a Python tool that implements a [clear and proven configuration sequence of ArduPilot of drones](https://discuss.ardupilot.org/t/how-to-methodically-tune-almost-any-multicopter-using-arducopter-4-4-x/110842/1).
+
+
+
It provides a graphical user interface (GUI) for managing and visualizing ArduPilot parameters, parameter files and documentation.
## Usage
-Usage is detailed in the [USERMANUAL.md](USERMANUAL.md) file
+There is a [Quick-start guide](QUICKSTART.md) and a more detailed [Usermanual](USERMANUAL.md)
## MS Windows Installation
diff --git a/USERMANUAL.md b/USERMANUAL.md
index 9c2d913..275c577 100644
--- a/USERMANUAL.md
+++ b/USERMANUAL.md
@@ -14,71 +14,86 @@ Before starting the application on your PC you should connect a flight controlle
This interface allows users to select or add a connection to a flight controller **if one was not yet auto-detected**.
-
+
It provides three main options for connecting to a flight controller:
-#### Option 1: Auto-connect
+#### Option 1: Auto-connect to flight controller
This option automatically attempts to connect to a flight controller that has been connected to the PC. The user must wait for at least 7 seconds for the flight controller to fully boot before attempting the connection.
-#### Option 2: Manually Select or Add a Connection
+#### Option 2: Select flight controller connection
-This option allows users to manually select an existing flight controller connection or add a new one. It provides a dropdown menu listing all available connections, including an option to add a new connection.
+Manually select an existing flight controller connection or add a new one.
+It provides a dropdown menu listing all available connections, including an option to add a new connection.
- To select an existing connection, use the dropdown menu to choose the desired connection.
- To add a new connection, select "Add another" from the dropdown menu. A dialog box will prompt you to enter the connection string for the new flight controller.
-#### Option 3: Skip Flight Controller Connection
+#### Option 3: No flight controller Connection
-This option allows users to skip the flight controller connection process. It proceeds with editing the intermediate `.param` files on disk without fetching parameter values nor parameter default parameter values from the flight controller.
+Skip the flight controller connection process.
+It proceeds with editing the intermediate `.param` files on disk without fetching parameter values nor parameter default parameter values from the flight controller.
-### Vehicle Directory Selection Interface
+### Flight Controller Info and parameter download
+
+If a flight controller is connected the software will now get information from it.
+The information is presented in the corresponding window and at the same time all flight controller parameters are downloaded to the PC.
+
+
+
+
+ Flight controller info and parameter download
+
+
+
+### Vehicle Configuration Directory Selection Interface
This interface allows users to select a vehicle directory that contains intermediate parameter files for ArduPilot **if one was not specified with the `--vehicle-dir` command line parameter**.
-
+
It provides three main options for selecting a vehicle directory:
-#### Option 1: Create a New Vehicle Configuration Directory Based on an Existing Template
+#### Option 1: Create a new vehicle configuration directory
Create a new vehicle configuration directory by copying files from an existing template directory.
It's useful for setting up a new vehicle configuration quickly.
-- Use the "Template directory" `...` button to select the existing vehicle template directory containing the intermediate parameter files to be copied.
+- Use the "Template directory" `...` button to select the existing vehicle template directory containing the intermediate parameter files to be copied. Use the overview window to select the template that better matches the components of your own vehicle.
+
- Use the "Base directory" `...` button to select the existing directory where the new vehicle directory will be created.
- Enter the name for the new vehicle directory in the "New vehicle name" field.
- Click the "Create vehicle directory from template" button to create the new vehicle directory on the base directory and copy the template files to it.
-#### Option 2: Use an Existing Vehicle Configuration Directory
+#### Option 2: Open an existing vehicle configuration directory
Select an existing vehicle configuration directory that already contains intermediate parameter files.
It's useful for editing an existing vehicle configuration.
- Use the "Vehicle directory" `...` button to select the existing vehicle directory containing the intermediate parameter files.
-#### Option 3: Use the last used Vehicle Configuration Directory
+#### Option 3: Open the last used vehicle configuration Directory
Select the last used vehicle configuration directory.
-### Component Editor Interface
+### Vehicle Component Editor Interface
Here you specify the components of your vehicle, their properties and how they are connected to the flight controller.
-
+
Change every field to match your vehicle's.
When finished press the `Save data and start configuration` button.
@@ -91,15 +106,15 @@ Correct those entries and press the `Save data and start configuration` button a
Here you sequentially configure the parameters of your flight controller to meet your needs while having all the available documentation at your fingertips.
-
-
+
+ Parameter File Editor and Uploader Window (main application)
-
+
#### 1. See the Current Vehicle Directory (optional)
-- this vehicle contains the files to be edited and uploaded
+- this vehicle configuration directory contains the files to be edited and uploaded
#### 2. Select an Intermediate Parameter File (optional)
@@ -108,11 +123,10 @@ Here you sequentially configure the parameters of your flight controller to meet
- The first available intermediate parameter file not named `00_default.param` will be selected by default
- If the selection changes, the parameter table will update to display the parameters from the selected file.
-#### 3. Select a Flight Controller Connection (optional)
+#### 3. About information and help links (optional)
-- **If a flight controller is detected and the `--device` command-line parameter was not explicitly set, it will connect to it.**
-- The `Flight controller connection:` Combobox lists available connections.
-- Select a connection to establish communication with the flight controller.
+When you click the ArduPilot logo the following window will appear:
+
#### 4. Viewing Documentation
@@ -145,11 +159,16 @@ Here you sequentially configure the parameters of your flight controller to meet
- The entire ArduPilot official parameter documentation is available on the tooltip, no need to use a browser to search for it.
- The `Add` button adds a parameter to the current intermediate parameter file.
-#### 6. Focus on the changed parameters (optional)
+#### 6a. Focus on the changed parameters (optional)
- You can focus on the changed parameters by ticking the "See only changed parameters" checkbox
- Usually, you want to see all parameters and look at their mouse-over tooltips to decide if and how you want to change them
+#### 6b. Annotate parameter metadata information into the parameter files (optional)
+
+Annotate parameter metadata information into the parameter files in the form of comments preceding the respective parameter.
+It will create bigger and harder-to-compare parameter files but is more suitable for text editor editing.
+
#### 7. Uploading Parameters to the Flight Controller
- You can also jump to a particular file using the Combobox as explained in [2. Select an intermediate parameter file](#2-select-an-intermediate-parameter-file-optional)
diff --git a/images/AMC_install_01.png b/images/AMC_install_01.png
new file mode 100644
index 0000000..545981d
Binary files /dev/null and b/images/AMC_install_01.png differ
diff --git a/images/AMC_install_02.png b/images/AMC_install_02.png
new file mode 100644
index 0000000..d954ce1
Binary files /dev/null and b/images/AMC_install_02.png differ
diff --git a/images/AMC_install_03.png b/images/AMC_install_03.png
new file mode 100644
index 0000000..d8194ff
Binary files /dev/null and b/images/AMC_install_03.png differ
diff --git a/images/AMC_install_04.png b/images/AMC_install_04.png
new file mode 100644
index 0000000..fc3c3c3
Binary files /dev/null and b/images/AMC_install_04.png differ
diff --git a/images/AMC_install_05.png b/images/AMC_install_05.png
new file mode 100644
index 0000000..2374d61
Binary files /dev/null and b/images/AMC_install_05.png differ
diff --git a/images/App_screenshot1.png b/images/App_screenshot1.png
index 0b051e0..44842a5 100644
Binary files a/images/App_screenshot1.png and b/images/App_screenshot1.png differ
diff --git a/images/App_screenshot2.png b/images/App_screenshot2.png
index 4f43c35..31f6fbe 100644
Binary files a/images/App_screenshot2.png and b/images/App_screenshot2.png differ
diff --git a/images/App_screenshot_Component_Editor.png b/images/App_screenshot_Component_Editor.png
index f6fdcdf..d1abb8a 100644
Binary files a/images/App_screenshot_Component_Editor.png and b/images/App_screenshot_Component_Editor.png differ
diff --git a/images/App_screenshot_FC_connection.png b/images/App_screenshot_FC_connection.png
index 0c34fd8..b4d9d09 100644
Binary files a/images/App_screenshot_FC_connection.png and b/images/App_screenshot_FC_connection.png differ
diff --git a/images/App_screenshot_FC_info_and_param_download.png b/images/App_screenshot_FC_info_and_param_download.png
new file mode 100644
index 0000000..fca0026
Binary files /dev/null and b/images/App_screenshot_FC_info_and_param_download.png differ
diff --git a/images/App_screenshot_Vehicle_directory.png b/images/App_screenshot_Vehicle_directory.png
index 226833c..e246539 100644
Binary files a/images/App_screenshot_Vehicle_directory.png and b/images/App_screenshot_Vehicle_directory.png differ
diff --git a/images/App_screenshot_Vehicle_directory1.png b/images/App_screenshot_Vehicle_directory1.png
new file mode 100644
index 0000000..284f142
Binary files /dev/null and b/images/App_screenshot_Vehicle_directory1.png differ
diff --git a/images/App_screenshot_Vehicle_directory2.png b/images/App_screenshot_Vehicle_directory2.png
new file mode 100644
index 0000000..aedf5fd
Binary files /dev/null and b/images/App_screenshot_Vehicle_directory2.png differ
diff --git a/images/App_screenshot_Vehicle_directory3.png b/images/App_screenshot_Vehicle_directory3.png
new file mode 100644
index 0000000..f6b2d73
Binary files /dev/null and b/images/App_screenshot_Vehicle_directory3.png differ
diff --git a/images/App_screenshot_Vehicle_directory4.png b/images/App_screenshot_Vehicle_directory4.png
new file mode 100644
index 0000000..63a4f5b
Binary files /dev/null and b/images/App_screenshot_Vehicle_directory4.png differ
diff --git a/images/App_screenshot_Vehicle_overview.png b/images/App_screenshot_Vehicle_overview.png
new file mode 100644
index 0000000..ecd5e76
Binary files /dev/null and b/images/App_screenshot_Vehicle_overview.png differ
diff --git a/images/App_screenshot_about.png b/images/App_screenshot_about.png
new file mode 100644
index 0000000..f5fdf6e
Binary files /dev/null and b/images/App_screenshot_about.png differ
diff --git a/images/App_screenshot_instructions.png b/images/App_screenshot_instructions.png
new file mode 100644
index 0000000..2f86866
Binary files /dev/null and b/images/App_screenshot_instructions.png differ
diff --git a/images/when_to_use_amc.png b/images/when_to_use_amc.png
new file mode 100644
index 0000000..4d61bcf
Binary files /dev/null and b/images/when_to_use_amc.png differ
+
+
+
+
+
+
+
+