Yesterday I made a feeble attempt to help another user with his notch tuning. The files and my bumbling can be seen here:
I’ve been trying to configure a Throttle Based Dynamic Notch filter recently, and wondered if anyone would be able to review these logs for me and tell me if I’m moving in the right direction/doing things correctly. I work in education, so unfortunately the hardware I’m flying this on is quite dated, but I believe the notch is working so far. I’m flying a Flamewheel 450 type frame, and using a Pixhawk 1 “clone”. 5000mAh 3S battery. I’ve been following the instructions on this page
I processed the same log file on two different computers, and got very different results.
Mission Planner on Windows:
Mission Planner on Ubuntu Budgie
MavProxy on Ubuntu Budgie
The amplitude on all three are different, and the Hz of the first peak is different (Although Mavproxy and MP on windows are similar enough for setting filters).
Both installations of Mission Planner are 1.3.76 Build 1.3.8063.11439. I’m not sure how to find the version of MavExplorer that was used but I have done the beta update to MavProxy in the last week or so. If it’s important tell me how to find the version number and I’ll gladly get it for you.
Why would the same version MP give such different results?
I am interested in the real reason as well.
I could make some estimated guesses of possible reasons (like the number definitions per platform).
Most of the basic functionality is available on a emulated platform however in case of using the advanced features here and there short comings will be visible.
All I can say after experimenting with different GCS software’s on various platforms (Win, Linux (ARM and x86), Android etc).
Nothing beats a native application.
That’s fair regarding Mission Planner in Linux. But what about Mavproxy in Linux?
Mavproxy in Linux
still works flawless for me. That’s what our developers use.
So it should be good enough for me too.
It’s been fine for me, except for the FFT values.