How to backup parameters from current copter?

[lida2003 (Daniel Li)]

As title says.

I have a few copters which were tuned and fly well.
Right now, I hope to save thoes parameters as a starting point.

And my fist job is to save thoes parameters with MethodicConfigurator.

But when I createded with connect FC (with MethodicConfigurator), it seems the UART ports are wrong.
e.g. I have connected GPS to UART2, but it’s connected to UART3 and there is no UART2 connection.

So my question are:
a) Can MethodicConfigurator save the initial params from connected FC?
b) How to backup parameters from current copter?

— EDIT: check with MP

[xfacta (Shawn)]

There are multiple ways.
If you still have the copter, just connect to MissionPlanner, go to Full Parameter List and “save to file” at top right of the screen.

If you dont have the copter handy, but you have the logs, you can go to “Review a Log” , select the log, select the small check box near the bottom to “Show Params” then save to file.

[lida2003 (Daniel Li)]

I need to save param file as MethodicConfigurator does (multiple-classified-param-files).

[amilcarlucas]

@lida2003

a) Can MethodicConfigurator save the initial params from connected FC?

Yes, it can, but you need to manually edit all entries in the “component editor” window yourself. That is not yet automated.

@lida2003

b) How to backup parameters from current copter?

The way you are doing it is correct, but for now you need to take responsibility for the “component editor” window data correctness.

[lida2003 (Daniel Li)]

@amilcarlucas

for now you need to take responsibility for the “component editor” window data correctness.

All the edit box values in thoese steps (including the very first one I have posted, which is not yet automated) need to be checked by myself for comparing configuration from MP’s param dump file?

Is it possible for MethodicConfigurator to use params from connected FC to automatically filling thoese edit box with correct value?

[amilcarlucas]

I went and looked at the code. It already uses parameters from the FC (if connected) to pre-fill the “component editor” window data: Code search results · GitHub

So, you might have either found a regression, or you did not had an FC connected.

Most of the “component editor” data is not found in any FC parameter anyway, like the motor model or RC transmitter FW version.

Why are you using version 0.8.9 when 0.9.2 is available?

[lida2003 (Daniel Li)]

OK, upgraded to 0.9.2

1. FC connected
2. version installed 0.9.2, previously 0.8.9
3. GPS still on UART port 3 // should be on UART2

[amilcarlucas]

It was a regression. I have fixed it here:

IMPROVEMENT use parameter metadata if available instead of harcoding

Can you re-test it by installing this new version?
https://github.com/ArduPilot/MethodicConfigurator/actions/runs/10402548868/artifacts/1815355742

[lida2003 (Daniel Li)]

Certainly, you can attach a debug version. I would be delighted to test it.

[amilcarlucas]

I updated the link above

[lida2003 (Daniel Li)]

GUI just gone when my copter param folder created.

Test Video: MethodicConfigurator-PR39-TEST01.mp4 - Google Drive

— EDIT

I got the screen, see below:

[amilcarlucas]

Thanks for testing.

A new installer will be available here shortly: IMPROVEMENT: Output less error messages when opening the com port for… · ArduPilot/MethodicConfigurator@976f835 · GitHub

[lida2003 (Daniel Li)]

GNSS Receiver issue?

MethodicConfigurator-PR39-TEST02.mp4

—EDIT:

Powered FC with battery: GPS module is ON. No difference, still GUI disappear.

PS: I’ll test tomorrow Thanks for support @amilcarlucas

[amilcarlucas]

https://github.com/ArduPilot/MethodicConfigurator/actions/runs/10416786908/artifacts/1819247992

Can you test that version?

[lida2003 (Daniel Li)]

==> GPS OK

==> Motor poles OK

==> There is NO SERIAL5_ params

==> It seems NOT correct

==> OK, but firmware version ???

==> OK Telemetry

==> OK , RC receiver

==> Firmware OK

It seems NOT all params are correct, I attached my param file for comparison. BTW there is no more window disappear issue.

H743DualCopter5.zip (6.2 KB)

[amilcarlucas]

1. Battery specifications need to be entered manually, it is very error prone to calculate them from the parameters in the FC.

2. Battery Monitor Product and Firmware fields need to be entered manually. Most battery monitors have a firmware version that I can not access.

3. What is your Battery Monitor > FC connection > type?

The only issue seams to be battery settings and battery monitor, please enter them manually.

I will release that version now. Thanks for testing!

[lida2003 (Daniel Li)]

1. SERIAL5 & BDShot configuration is NOT correct.

2. This is not smart battery, no digital interface, just analog VCC data right now.

3. I didn’t go through all steps right now. If all the above issues are solved, I will continue my try with MethodicConfigurator, which is apparently easy for params maintenance.

[amilcarlucas]

@lida2003

SERIAL5 & BDShot configuration is NOT correct.

I will take a look at your parameters and see if I can improve it.

@lida2003

This is not smart battery, no digital interface, just analog VCC data right now.

Because it is not a smart battery the software can not access any information about it, So you need to enter the data manually.

[lida2003 (Daniel Li)]

Is there any progress or new debug version that I can try?

[amilcarlucas]

Try the new development version