Sean-bumble-bee
 Core User of DJI
Flight distance : 15997 ft
United Kingdom
Offline
|
"Does this mean the drone has a fault?"
I don't know, sorry.
Did you check the values of RC.Rudder ? At a guess 1024 = no rudder.
I don't have any Mini 4 logs with which to compare your log ....... but I am a bit puzzled about the differences in the values of
a) OSD.yaw when compared to Gimbal.yaw
b) OSD.yaw[360] when compared to Gimbal.yaw[360].
My mini 3 logs are from 'troubled flights' so I don't know how reliable they would be.
I have looked at randomly chosen 'untroubled' logs for my Mavic Mini and Mini 2 and in general OSD.yaw is in reasonable agreement with Gimbal.yaw.
Likewise OSD.yaw[360] is generally in reasonable agreement with Gimbal.yaw[360].
"in reasonable agreement" = 'say' +- 5 deg.
The only time they are out of reasonable agreement seems to be when I was yawing/turning the drone but the disparity was nowhere near 100deg.
Hover the drone in front of you and watch what happens to the gimbal when you give rudder input.
It might also be worth hovering the drone in front of you and watch to see whether or not the drone yaws/turns on its own with no rudder command.
Unfortunately though, the validity of that test may be compromised by the fact that when you are hovering it low enough to be able to see, in detail, the drone turn the drone will probably be low enough to have VPS available to it to aid position holding. For the video's flight the drone almost certainly did not have VPS available to it, too high & too dark.
I suppose you might as well check what happens to the gimbal AFTER you have stopped giving rudder i.e. does the gimbal take a long period of time to 're-center' itself.
Really we need someone with an untroubled Mini 4 Pro to comment.
|
|