I looked at the .DAT for a incident that
@erkme73 provided. I'm posting the results here since that incident is very similar to the ones being discussed in this thread. I'll describe what happened but since this is my first Mavic incident I can only speculate why it happened.
This was a ToiletBowling incident which happened here.
View attachment 1711
It appears to me that switching to Sport mode caused the Z axis magnetometer to become noisy.
The magZ noise is actually pretty severe with a minimum of 35 and a maximum of 1800. I've not seen anything like this on the P3.
DatCon has a computed field called magYaw that is the heading computed from the magnetometers and is different than Yaw which comes from the Flight Controller. Usually, magYaw is the same as Yaw. When the Z magnetometer became noisy magYaw began to separate from Yaw.
The Yaw/magYaw separation had been 5 degrees but slowly grew to 30 degrees at 850 secs when ToiletBowling was obvious.
With the P3 this amount of Yaw/magYaw separation often leads to a nonGPSCause error (presented as a compass error in the DJI Go App) and a switch to ATTI mode. In this incident there was no switch to ATTI mode. I'll speculate that the ToiletBowling actually started at 823 but didn't become apparent until 848 secs when the pilot removed control stick input. At this point the Mavic should've just hovered without stick input but was moving (ToiletBowling).
I'm speculating the magZ noise was caused, at least partly, by the switch to Sport mode. I've asked
@erkme73 if the other ToiletBowling incidents happened only after a switch to Sport mode.
A compass calibration issue can be seen by looking at the behavior of Yaw and magYaw. There was no indication of a compass calibration issue in this flight.
The .csv used here has been attached here as a .zip for those interested in looking this incident.