EdisonW1979
Second Officer
Flight distance : 1535679 ft
Canada
Offline
|
Gazoo Posted at 2018-6-30 12:15
The two times it has happened to me have been from a hovering position.
I think my MA just gets impatient and says to hell with you im going flying!
You might want to check out the thread I created a while ago when 0400 was released:
Threads detailing SERIOUS issue with Mavic Air FW v01.00.0400
MANY pilots, including myself, have experienced an IMU error which caused a runaway / crash situation with the MA. And the suggestion by @hallmark007 about the compass being a possible instigator of this problem should be taken with a HUGE grain of salt, he really doesn't know very much, as has been recently exposed.
However, having only 8 GPS sat locks at 4 bars quality at takeoff can definitely be a contributing factor here too, no denying that. I do not try to take off unless I have at LEAST 10 sat locks with 5 bars quality, preferring to wait for 12 or more if I can.
At this point, the only workarounds seem to be a complete re-flash of the FW via DJI Assistant 2. 1.2.4 (note it has to be done with 1.2.4 and not an older version), and then re-calibrate everything, including VPS, RC sticks, everything. When you go to calibrate the VPS, find a COMPLETELY level surface (verify X and Y axis flatness with bubble level), otherwise the IMU calibration will be skewed and cause the drone to act even more "strange"...
Some pilots have reported their issues have gone away, and stayed away, after this process. Others, like myself, have had the issues come back after a few flights. No way to know if you'll be the lucky one until you try.
Only other sensible action is to either ground your drone and wait for DJI to finally issue a fix, or have it replaced, hopefully under warranty, and see if the replacement is any better. I actually went and bought a second unit for testing, and it worked awesome for the first half dozen or so flights, then started going wonky again.
Perhaps you'll have better luck than others here! |
|