@b2n I had looked at this incident a couple of times and just couldn't determine the root cause.
The first event at time 303.275 lasted for about 6 seconds and seems to have been the result of some unusual control stick inputs. 100% right aileron and 75%elevator were abruptly released followed by some unstable pitching, rolling, and yawing for about 6 seconds and then finally stabilizing. Also during these 6 seconds you pulsed the throttle 3 times. Looked to me like what some of my FC friends would do test the stability of the FC.
But, then 30 seconds later the same instability developed without the control inputs that I thought caused the first instability. Both events were also characterized by the leftBack motorSpeed momentarily dropping to 0 RPM, but that appears to have been commanded.
In summary, all I'm seeing is what happened and can't really say why it happened. The first even could've been the result of exciting some FC instability, but the second event wasn't. The motorSpeeds all appear to have been commanded and not the result of some HW issue.
I seem to recall that you don't want to, or can not, send it to DJI repair. Also, you were speculating that a recent FW update was the cause. This being the situation I'd suggest that you update to the most recent FW and do several test flights in an unpopulated area.
The first event at time 303.275 lasted for about 6 seconds and seems to have been the result of some unusual control stick inputs. 100% right aileron and 75%elevator were abruptly released followed by some unstable pitching, rolling, and yawing for about 6 seconds and then finally stabilizing. Also during these 6 seconds you pulsed the throttle 3 times. Looked to me like what some of my FC friends would do test the stability of the FC.
But, then 30 seconds later the same instability developed without the control inputs that I thought caused the first instability. Both events were also characterized by the leftBack motorSpeed momentarily dropping to 0 RPM, but that appears to have been commanded.
In summary, all I'm seeing is what happened and can't really say why it happened. The first even could've been the result of exciting some FC instability, but the second event wasn't. The motorSpeeds all appear to have been commanded and not the result of some HW issue.
I seem to recall that you don't want to, or can not, send it to DJI repair. Also, you were speculating that a recent FW update was the cause. This being the situation I'd suggest that you update to the most recent FW and do several test flights in an unpopulated area.