Thanks all for your analysis. Possibly there are vibrations in excess, so I’ll correct that. But still there are strange facts:
-Given there are vibrations and FS_VIBE_ENABLE=1, should it go up suddenly?
-There are differences on both autotunes (batteries used), but there was battery voltage compensation (moreless the recommended values):
MOT_BAT_VOLT_MAX,16.94
MOT_BAT_VOLT_MIN,13.5
Is something wrong, as if meaning compensate above 16.94V (absurd) and below 13.5V (absurd)?
Is battery voltage compensation active in autotune?
-Parameters messed, as CTUN.DAlt and CTUN.Alt reaching -80m. This has no sense.
-MOT_BAT_CURR_MAX=40 ignored.
Here is a video of both autotunes tlog capture:
First autotune: shows “AutoTune: success 0/4”, so possibly unsuccessful because of vibrations.
Second autotune:
-Hud shown captured with red bars on EKF, high vibrations and height -66m.
-Autotune starts at 5’35".
-Proceeds normally during around 11" (visually no vibrations, several autotune twitches observed).
-Suddenly goes up at 5’46".
-On Vibration Failsafe it says that when triggered “Vibration compensation ON” will appear on the Ground Station HUD, and when recovering “Vibration compensation OFF” will be displayed on the HUD, but neither appears on above video.
Yes, but vibrations were moderate during 11" of the second autotune, visually no vibrations were observed, and suddenly it went up towards selenites.
11" of normal autotune and then suddenly up towards selenites, with CTUN.DAlt and CTUN.Alt reaching -80m (negative). No holes, unevennesses or similar at the site.
I’ll try to be under the vibration values you say
With adhesive sponge tape. Certainly I’ll substitute it, with a thicker and softer one.