I’ve assembled a quadcopter with the following specifications:
T Motor MN7005 230KV Motor
Air 40A ESC
T motor 24in prop
Pixhawk 2.4.8 Flight Control Board (FCB)
Here 3+ GNSS connected via CAN to FCB
I conducted several flights with default parameters, including an auto mission covering 2 km. The copter performed adequately but exhibited suboptimal attitudes. After a while, I began experiencing EKF Line switch and EKF yaw reset errors. The flight mode switched immediately to stabilize, leading to a landing. This occurred multiple times, prompting me to initiate the tuning process.
I meticulously followed the tuning procedures, initializing with all initial parameters. During the first flight, I observed noticeable vibrations in the frame, prompting a manual tune to elevate the vehicle. Subsequent testing for extreme stick inputs indicated stability. However, upon attempting Autotune, I encountered EKF errors, causing Autotune to fail.
At this point, I’m uncertain if there are specific considerations I should address. I am unfamiliar with the usage of the new ArduPilot web tools for setting magfit, PID review, and other configurations. Any support or guidance you can provide would be greatly appreciated.
Thanks , I’ll for sure check it. Yesterday I updated my fcb from 2.4.8 to cube orange and found the vibration levels reportrd in the log reduced from 25 to less than 10. Will update the logs
Hello,
Today, I successfully conducted a few flights, incorporating some manual adjustments before engaging in the autotune process. I attempted to set harmonic notches to the best of my knowledge using ArduCopter web tools. Subsequently, I executed autotune in the pitch axis, achieving positive results. Upon inspecting the pitch response post-tuning, it was deemed quite satisfactory. However, a log analysis revealed that the R*out values in pitch exceeded 0.1, a parameter that many forums suggest should remain below this threshold.
Nevertheless, despite this observation, the tuned pitch demonstrated a high level of responsiveness.
If this is still the copter with 24inch props, all the parameters I gave before still apply.
I had the frequency wrong because I had to guess a bit before because the batch logging wasnt enabled, but now it is I can say for sure you want:
BATT_FS_CRT_ACT,1
GPS_GNSS_MODE,5
INS_ACCEL_FILTER,10
INS_HNTC2_ENABLE,0 // no need for another notch filter, disable it
INS_HNTCH_BW,20
INS_HNTCH_FREQ,46
INS_HNTCH_FM_RAT,0.7
INS_HNTCH_REF,0.34
MOT_THST_EXPO,0.74
PSC_ACCZ_I,0.8
PSC_ACCZ_P,0.4
Around 46Hz is the motor/prop base frequency, even though it’s not very apparent because of the strong 2nd harmonic.
The anomaly here is that double peak in the 2nd harmonic, at about 76Hz (it will be in the base harmonic too, but not very obvious). That is because you’ve got one motor running at quite a different output from the others. This would be something to try and fix.
The Autotune worked OK despite that, copy the new values over to the other axis. If you get that motor output issue fixed, then run Autotune again on pitch and roll in one session.
I conducted several flights today. Following the auto-tune process for roll and yaw axes, the drone appears to be stable in flight with satisfactory attitudes. I’ll certainly test out the notch suggestions you provided, although I came across the post a bit late. Attached are the flight logs from today after completing the auto-tune for all three axes. Could you please provide feedback on the overall PID performance? I’m still uncertain about the values for Rout, Pout, and Yout.
