I didn't realize that you were talking about the .DATs that I had looked at earlier. The glitch isn't associated with the concatenation of the two .DATs. Using the highest sampling rate it looks like
Seems that the FC thought it was necessary to correct a (small) pitch down, roll left situation. It's not clear, at least to me, why a combination of 100% PWM on the low corner and 10% PWM on the high corner was needed. These messages occurred throughout the eventLog stream
1489.107 : 93594 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
1494.207 : 93849 [L-FMU/LED]action changed. aircraft install warning!:mass center install err(2)
1519.707 : 95124 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
1526.507 : 95464 [L-FMU/LED]action changed. aircraft install warning!:mass center install err(2)
1550.307 : 96654 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
1552.007 : 96739 [L-FMU/LED]action changed. aircraft install warning!:mass center install err(2)
1572.407 : 97759 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
1577.507 : 98014 [L-FMU/LED]action changed. aircraft install warning!:mass center install err(2)
1589.407 : 98609 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
1591.107 : 98694 [L-FMU/LED]action changed. aircraft install warning!:mass center install err(2)
1601.307 : 99204 [L-FMU/LED]action changed. aircraft install warning!:yaw install err(1)
Maybe the Mavic is unbalanced causing the FC to occasionally take seemingly inappropriate actions?
Last edited: