I tried to find out what value should go in the INS_HNTCH_FREQ, BW but am not really sure whether 50 and 30 are right values for them.
Is INS_HNTCH_FREQ possible to be found out in the graph or do I need to somehow calculate it utilizing ESC RPM average? If it were throttle based notch, I would confidently put 55 in there but is it same when it is ESC telemetry based notch?
Also, why do I see that many harmonics in the graph? Does it indicate any vibration on frame or arms? Do I need set up 2nd/3rd harmonics or use second notch filter in this case?
I’d appreciate if anyone can give me an example notch setting for my copter based on the log file. I’m planning to apply mutisource and update at loop rate option later if it is OK and practical to do so.
Thank you for taking the time to read and explain this. Also, any suggestion to improve the system is welcomed.
Use Estimated Post Filter. Check the Show Notch 1 box. Does the notch band align with the peaks? No? Why not? Perhaps the default Pole number for those motors is not correct?
Sorry, It seems I got it completely wrong. I counted something right next to the coil not the magnets on motor cap. Yes, there were 24 poles when I just counted.
Thanks for pointing it out. I will give it a try again.
If you would have used ArduPilot methodic configurator software that and 80 more parameters would have been automatically set to their optimal values. And you would have been guided step by step in configuring just the other 200 required for safe flight while never seeing the remaining 1000 parameters that are irrelevant for you.
I actually tried few days ago with the configurator software and had to stop not long after beginning as I was not sure about my hardware specs and afraid of putting wrong information in there.
This parameter is going to be saved for future reference and I’m thinking of restarting from the scratch using the configurator tool. Copter is throwing a couple of errors now. It settles down in about a minute or two but it needs compass calibration after replacing battery, Need position error for a while after reboot until it changes IMU. Even after settling down and gets ready to arm in loiter, now it won’t allow quik-tune which was loaded in script initially. I can only guess it might be interference issue and it is finally the time for me to try Magfit which I always have been avoiding last few years.
Looks good! Disable Raw Logging once the filter parameters are set or you will have some huge log files.
And BTW-That is only useful on higher performance processors (H743, etc) with a Sd card. Slow dog’s like F405’s, all SpeedyBee’s for example, will choke.