in BIN format, so it can be loaded to filter review tool 
Sorry for confusion
Sorry, I do not share bin as it loaded with private data.
Thanks for help.
This applies to software based filters? It makes sense if you install physical dampening.
Doesn’t really matter as long as the proper logging is set up.
Yes, what I said there was in reference to software filters. Experience here has shown that unless you’re running a gas engine most builds don’t need physical damping. But that’s a different topic all together.
1 Like
That log is no use - can you upload a .bin log please?
You can PM it to me if you do not want a .bin log out in the wild.
I think your configuration is probably way too complex.
A throttle-based notch is best if you do not have an RPM source.
FFT-based notch is like a 10 tonne hammer to crack a peanut - it usually settles on a mid-range frequency that does not really match any peak, and applies an extremely broad bandwidth.
The FFT parameters require quite some tailoring before the FFT reliably tracks any noise - I’ve tried a bunch of times with a variety of copters. It may work Ok on small copters, but I’ve only been dealing with medium to large
A second harmonic notch is usually only needed if you have some external noise source that does not relate to the copters own motor noise, like a generator or rotating LIDAR onboard.
You only need this: LOG_BITMASK,180222
1 Like
I replaced props and take special care for balancing.
Set I used for test before was a kind of crash dummies.
Vibs changed dramatically.
I will perform new test flights and Autotune, but with those vibrations’ levels, I would prefer just dynamic FFT as the only notch source, even if it’s a hammer. It’s simple, will do the job and will change in time with copter state. Once I have more time I will try Throttle as well.
@dkemxr advice to post bin file without GPS data, what I’m willing to do if only have time. Tomorrow is my last day on the field with this copter so want test it as much as I can.
Is GPS a must?
Can’t arm after I set serials to None and GPS_AUTO_CONFIG to Disabled.
The msgs are:
14.03.2025 12:58:36 : EKF3 waiting for GPS config data
14.03.2025 12:58:36 : EKF3 waiting for GPS config data
14.03.2025 12:58:26 : EKF3 waiting for GPS config data
14.03.2025 12:58:26 : EKF3 waiting for GPS config data
14.03.2025 12:58:17 : r reboot
14.03.2025 12:58:17 : PreArm: AHRS: EKF3 Yaw inconsistent 48 deg. Wait o
14.03.2025 12:58:17 : PreArm: EKF attitude is bad
14.03.2025 12:58:17 : PreArm: RC not found
14.03.2025 12:58:16 : EKF3 waiting for GPS config data
14.03.2025 12:58:16 : EKF3 waiting for GPS config data
14.03.2025 12:58:06 : EKF3 waiting for GPS config data
Unless you’ve specifically setup for non-GPS then yes, GPS is a must.
So I can’t collect anon bin.
But have and interested change in vibrations. Here are vibrations with new propellers. There are 3 parts here: smooth AltHold, then with some thrust, and then Stab with harder thrust at the end.
Looks better, is’t it?
Why not? You don’t have to disable GPS just uncheck it from the Log Bitmask.
1 Like
Sure, sorry I was fixed on other issues.
So tomorrow may be… Last chance in the coming days
.
Yea. Then open the file in Mission Planner and check the “map” box and see where it puts you.
Sure but I asked for other options as well. Are IMU and ATT good?
I would like to diagnose the failed Autotune as well.
Usually, more data isn’t a bad thing when looking at the log (other than bloat). So whatever you’re comfortable sending, go for it.
Set LOG_BITMASK,180218 which is 180222 minus the GPS setting. This is what you want.
Much of the additional logging, Fast {anything} or Raw {anything}, makes much bigger log files for no real gain - unless you know how to make use of all that extra data.
Sorry guys, it does not work.
GPS track got flatten and turn around few axis by 45 deg, that’s all.
Thank’s you for your time. I will try to write some code to remove GPS from bin once I will have some free time.
So, finally I wrote a piece of script to drop GNSS related data from Mavlink bin stream.
Not sure how good is it, so will send you a PM with link.
There are 3 files there.
- One is an attempt to test FFT and dynamic notches.
- Second is a log of failed autotune mode. @dkemxr that’s for you. Sorry, had no time to fly it without filtering.
- Third is a log of strange flight-away while landing. Could be someone can figure out what happened.
Thank you so much for your time and patience.
I could be wrong, so pls do keep files private.