I believe I found the cause. Missing sanity checks in Plane.
Home and therefore home altitude is taken regardless of VDOP and not checked against terrain data which would have likely had the correct altitude. VDOP also does not appear to be logged but maybe I’m searching wrong.
thanks for the log! It is a bug and the fix is here:
the problem is a bug in the handling of MIS_OPTIONS. The bug resulted in the “continue after landing” option being used
It will be fixed in the next beta (beta5)
I think this is the right place to post this. My two different tilt rotor vtols are make strange motor noise
The motors make a crunching knocking sound only during fixed wing flight. Its a matek f405 TE running bdshot. Going back to 4.5.7 the noise goes away. Any idea what it could be?
No logs but ill make one today. It will Make the noise even with the plane on the bench. When i hold the plane while in fbwa. I hope this is ok. I rather not fly the plane. The knock is loud i can hear it when the plane was flying. Even at 100m altitude I could hear it.
I’m curious about this noise. My T1 was making a knocking sound in fixed wing mode. I assumed it was mechanical so I didn’t mention it. Certainly throttle related, because when I pull the throttle back to glide it goes quiet.
If it helps: Bluejay ESCs. Using ESC telemetry for the notch filter. BDshot. Matek F405-VTOL. No noise in hover mode. This is a fresh (re)build so I’m not finished tuning it yet, but generally it flies well.
It didn’t make the sound when I flew it last fall, but that was on a different controller and a lot has happened since then.
Yup, just tested this on the bench without props. It’s a thing. In manual mode the front motors sound of the T1 ranger like they’re full of gravel but as soon as I switch to QStab the sound cleans up and they sound normal, even as they transition to the vertical position.
Update: Just rolled back to 4.5.7 and the problem went away. The motors sound fine in both QStab and Manual mode. I can’t say if the issue was in the other betas, I only flew this on beta 4.
When looking into the ESC telemetry, you can see that there are always 2 motors with RPM and 2 motors with 0 RPM. The selection goes merry-go-around. That should be impossible.
That’s probably a key point. I’m running Dshot 600. I tried with Dshot 300 and it didn’t change. I also tried turning off the multi source filtering. Nothing made any changes, other than reverting to 4.5.7.
IMO the effect hinges on BDSHOT. Something takes the RPM into some loop / governor and then randomly stops a motor for a fraction of a second. Potential Risk to burn the ESCs.