I have been struggling with tuning a collective-pitch quadcopter to get rid of oscillation, and haven’t been able to clearly determine what effect some of my changes have - specifically in the “ATC_[ ]” PID-type parameters.
I am using the WLToys V383 airframe, but I have extensively modified it, mainly due to crash repairs and difficult parts availability. I had started out with Tridge’s original parameter file for this airframe, really hoping to not be re-inventing the wheel with this one. But unfortunately, that’s not how it’s turned out for me.
My question is this: What effect does an out-of-range, zero, or blank value have when the parameters are loaded into the flight controller?
I have gotten warnings from the parameter list in Mission Planner, where it says the values are out of range, even though they are the ones in the original file - so I am assuming that MP has been updated along the way to expect the latest firmware version’s parameter range. If I put a value in a parameter that is well below the range, does it get written anyway, or is it automatically reset to the minimum allowed value? If I put a zero for that parameter, does the zero get used? If I leave it blank does it go to some default value? When does the default value show up? Am I blowing up the FC’s calculations by putting in an out of range value (especially a zero)?
Also, where can I find the default values? I barely know anything about C++ (I only know a little about C), so digging through all of the *.h and *.cpp files isn’t an easy task for me with the object-oriented things, and it’s hard for me to follow the logic of what’s coming from where. But I am trying to learn this as I go, so any help is appreciated.
I know this is actually multiple questions, but maybe there is an easy answer.