I’ve made an improvement to my Python script that compares parameter values from two .bin log files. I now allow the user to select the “initial” or “final” parameter values.
This allows comparing a log file against itself - to see what changed over the course of a flight.
One of the places this may be helpful is in reviewing changes from an autotune flight.
It’s been interesting to look into the log file data. Programs such as Mission Planner and MavExplorer do a great job of plotting data, but some of the data isn’t numeric and can’t be charted.
MavExplorer allows creating custom charts - also helpful. It isn’t a well publicized feature and it isn’t too difficult to use - it can be really useful. I’ve been thinking about useful reports that I haven’t found other ways to produce. Maybe most of them exist, I just haven’t found them yet.
My “log explorer” scripts make it easy to look around the data - by allowing the user to drill down by message type and field. One handy use of this is the ability to report all the mavlink messages for a flight.
I’m curious what sort of reports might assist in tuning. There are step charts that can show where there is a problem, but I’ve not found prescriptive reports that show what changes should be made.
I believe your Methodic Configurator touches on the structure of tuning loops - inner, middle and outer.
I didn’t learn about this until I used AI to help me understand the Flight-Review charts for PX4 to help me manually tune. And of course it all translates to ArduPilot.
In my opinion, ArduPilot relies too heavily on AutoTune and the available wiki has too little information about how it all works. As I understand it better, I’m hoping to be able to provide some improved tuning support tools. Yes - the Methodic Configurator has the same goal. So I’m sure you understand my interest in exploring it all myself.
Here’s an AI generated synopsis of the ArduPilot tuning loops.
Yes, of course it does. We start by removing the loop noise, then we tune the inner loops and proceed to the outer loops. If I remember correctly you said: “I do not have time to use ArduPilot methodic configurator”. If you would have had time, and used it, you would have learned all that a lot sooner
But I’m glad you finally get it.
No, it does not rely too heavily on Autotune. Autotune is the best tool for the job, so we use it.
You keep on complaining that you need to understand this stuff. But you do not use it.
Use autotune and you will understand it. Use AMC and you will understand it.
