Odd. From my perspective, there is no "perfect" PID tuning, so this function is confusing. I fly drones, and I adjust the PID tunings depending on how I'm flying: acrobatics, racing, filming, instruction, etc. Is there a function to tune the tuner? :) What I mean is: changing P impacts responsiveness to the transmitter controls, D affects wind gusts and sudden changes (fast loops anyone?), I is more for racing, its a bit more complex than that but you get the gist. Why pick one set?
EDIT: (a) I didn't actually use the Webapp, after using it, there's more to it than my oversimplification. (b) I'm referring to the rates, not the PIDs. Thanks to the folks below ('pdituner' and 'somehnguy').
That is true, that is why there is a slider in the tool that allows you to trade-off performance for robustness. The bode plot is also an indication on how the closed loop performs in frequency domain, so you would normally choose different tunings according to specific use cases (e.g. some frequency response for tracking and a different one for just regulating)
You know, after I posted I noticed there was a "next" button and started using it (I thought it was GitHub only). You pretty much captured a lot of the tradeoffs. Very nicely, might I add: the UI/UX funneling is clever! I'm off to cram a step function into my flight controller... :)
Are you sure you don’t adjust the rates depending how you’re flying? The PID tune can be objectively good or bad, and is highly dependent on your specific hardware setup. It controls how stable the drone is, you wouldn’t want to change your PIDs based on flying style as you would just be making it fly worse. For different flying styles you adjust your rates depending on how smooth/snappy you want it to feel and the desired deg/s of rotation.
Some flight controllers have two levels of PID. One on rates, and the other on attitude angles. The higher level PID's command mixes into the lower level PID's input, perhaps along side some joystick inputs depending on the configured control mode.
EDIT: (a) I didn't actually use the Webapp, after using it, there's more to it than my oversimplification. (b) I'm referring to the rates, not the PIDs. Thanks to the folks below ('pdituner' and 'somehnguy').