Skip to content

Commit e7176e2

Browse files
committed
docs(usecases): Explain when to reset to default parameters
1 parent 846340e commit e7176e2

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

USECASES.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,16 @@ But there are other use cases as well:
1818

1919
## Use the *ArduPilot Methodic Configurator* software for the first time
2020

21+
It is recommended to start with default parameter values on your flight controller as it guarantees that all parameters have sane values and
22+
provides a clean baseline for the configuration process.
23+
This is especially important for new vehicles or when you've made significant changes to your setup.
24+
25+
If your vehicle is already operating correctly and you're just making minor adjustments, you do not need to reset the parameters to their default values
26+
as this would require reconfiguring everything from scratch.
27+
28+
The ArduPilot documentation explains [how to reset all parameters to their default value](https://ardupilot.org/copter/docs/common-parameter-reset.html)
29+
if you decide this is the best approach for your situation.
30+
2131
1. Close all other GCS software (MissionPlanner, QGroundControl, MAVProxy, DroneKit-Python, APM Planner 2.0, UgCS, LOGOS, Tower, AndroPilot, etc)
2232
the *ArduPilot Methodic Configurator* needs connection exclusivity.
2333
1. Connect the flight controller to the computer using a USB cable.

0 commit comments

Comments
 (0)