Unresponsive controls

[jeffphoto]

I was flying our mavic pro inside a large atrium inside our office building. I got a prompt to update firmware and did so. After powering down and back up the controller and the aircraft I lifted off and flew a small slow half circle and was about to land from the table I launched from. I got to the area of the table and let off all the controls. The aircraft kept flying forward toward a large window. I applied full back stick and there was no effect at all. When the aircraft got about a foot or two from the window the obstacle avoidance must have kicked in as the drone stopped. I again tried to apply full backward stick with no result. The drone then continued to drift into the window, crashing and doing major damage. In looking at the flight data it shows weak gps signal at times during the flight but I fail to see why a weak gps signal would render my controller completely unresponsive. I was standing about 5-10 feet from the drone when it stopped responding.
Any ideas what happened?

 

[Pepino Grande]

You need to update the firmware on both the drone and the controller. Don't accept updates when flying.

 

[JLane]

There have been quite a lot of reports from users about the Mavic sometimes being totally unresponsive to stick inputs while in ATTI mode. In fact, some users have begun to affectionately refer to the Mavic's ATTI mode as BATTI mode. As far as I know, there has been no explanation, or even acknowledgement from DJI that the Mavic has any problem in ATTI mode. If you can upload your logs and let some of the users here analyze them, perhaps we might find some kind of an explanation as to what happened.

ps. I don't think this had anything to do with your firmware update. The app won't let you fly with unmatched firmwares.

 

[Robbyg]

I think you got 2 good pieces of advice.

Dont update your firmware during flight and yes there have been cases of the drone switching to Atti mode during mid flight. I have not seen too many recently but it's a possibility.

Without seeing the Logs my first line of thinking is that it went into ATTI mode due to the firmware update possibly rebooting and losing connection with the GPS module. The reason it went forward seems to be due to the IMU losing calibration. If you look at the new firmware post you will see lots of people saying the IMU had to be re-calibrated after the update. I suspect yours updated and when the calibration data went south the drone thought it needed to go forward to hold itself steady. Going fully backwards might not have been enough input for the Mavic to correct for the false data the IMU was feeding the CPU.

Rob