Today I discovered that my autotune flight for ROLL, somehow changed the value of MOT_SPIN_ARM. It changed it to 0.23 - which is higher than MOT_SPIN_MIN - which is 0.15. (both values were set to their defaults)
I discovered this when I tried to take off again, and I got an arming error that MOT_SPIN_ARM was higher than MOT_SPIN_MIN. It won’t arm with that condition.
I can’t recall ever reading anything about autotune changing MOT_SPIN_ARM. But maybe I missed it.
If you look at the parameters in the BIN file you’ll find the following.
As these parameters are from a BIN file - clearly this anomaly was created during this flight - the arming check wouldn’t have allowed a take off when these values.
I don’t think anyone is making any strong accusations, but the most plausible cause is accidental user input.
Here is the GCS message timeline showing autotune completion and saved gains after landing, indicating that autotune parameter saving completed at time 11:40:07:
A brief search through the Copter-4.3 branch shows no automatic routine that appears to change MOT_SPIN_ARM, and no mention of that parameter in the autotune libraries. Admittedly, my search was only cursory.
Is it possible you accidentally changed MOT_SPIN_ARM (maybe intending to change MOT_THST_HOVER, whose value is close to 0.22-0.23) or clicked on something like the motor test page and mistakenly made an input?
I mentally retraced my steps. After landing from the roll autotune leg, I used QGC on my HereLink to uncheck “roll” and to check “pitch” in the autotune section of the “tuning” tab.
Turns out that right above that is a slider for MOT_SPIN_ARM.
No doubt I accidently bumped that slider when changing the autotune options.
I’m sorry to put you to all the trouble of looking into this - I feel pretty stupid.
In flight log, I can see CAN related messages as shown below are flooded. What is the significance of these messages and how to suppress them to appear from log, if they are not important.
