Anyone can help a newbie out. Building a cinelifter with Arducopter everything flys great when the Harmonic Notch filter is disabled but once I enable it using the FFT instead of esc telemetry to handle noise the quad start to oscillate terribly. I’m flying the Swol 10in x8 configuration. Using the initial parameters.
First set this
you didnt make a mistake, this should be the new default.
In the first log with “No Notch” you got an configuration error, the second notch filter is enabled.
This is not a big problem, but I would set
Then in the second log with oscillations you’ve got a different error when you enabled the first notch filter
this will be filtering out desired movements and all sorts of things, since the FFT-derived frequency is 90Hz. This would have been the cause of the oscillations.
I would set this for throttle based notch filter now that you’ve got reasonable values to work with from the live FFT.
FFT was also giving a very wide bandwidth, and I think the reason is there’s quite a weight imbalance.
Rear motors are working a lot harder to lift, making a broader spread of frequencies.
Actually maybe just the excessive bandwidth alone might not cause the oscillations, but maybe having that and the seconds notch filter all working in the same space may have caused problems.
Normally the first and second notch would be working with different ranges of frequencies.
That’s quite good for stabilise mode and all default PIDs.
You can adjust these:
Sorting out the balance really helped to bring those motor outputs together and narrow down the range of frequencies to filter.
See on the map, your IMU estimated position and the GPS position don’t align yet you’ve got good low vibrations. I suspect this is because of houses and trees.
But you could still set this to give a better GPS 3D Fix - there tends to be less certainty when the GPS units are using all available constellations and they can get overwhelmed.
Also I would consider changing these:
You wont be able to arm and fly until there’s a good 3D Fix and Home can be set - seems to take a while but think of your copter and payload disappearing off to Sea of Japan…
BATT_FS_CRT_ACT,3 usually set to 1 for Land, it’s unlikely to be able to return home with a critical battery level. Maybe BATT_FS_LOW_ACT would be good to have as 3 Smart RTL
Most often a BATT_FS_LOW_ACT has already initiated RTL (or Smart RTL) and the copter is half way home, now reached critical battery level. The only viable option will be to land.
FS_OPTIONS,16 to 24 so it will “Continue if landing on any failsafe” and not start all over again if already landing.
If you have a spring-centered throttle then I set this too:
After all that, get out in a big open space and run Autotune!
Set a switch position to Autotune mode, switch into it once flying and let it complete (twitching stops) and then reposition, land and disarm WITHOUT touching any switches! After a few seconds the new values are saved and you can arm and fly again.
Use plenty of Althold and Loiter
Note: There is a message in the log I haven’t seen before. Not sure what to make of it:
This is the reason:
we check and restore the ICM20602 Y offset high register
on every update. We don’t mark the IMU unhealthy when we
do this. This is a workaround for a bug in the ICM-20602
where this register can change in flight. We log these
events to help with log analysis, but don’t shout at the
GCS to prevent possible flood