slup
lvl.4
Flight distance : 1607103 ft
Sweden
Offline
|
Hi Gavin,
I'm late into this ... but have lately already seen several similar cases regarding uncommanded descents over at MavicPilots.com. Unfortunately nobody have been able to conclude what the reason is yet, we suspect some kind of fw fault in this stage.
My advise is to report this to DJI & ask them to investigate the event ... they have a much greater possibility to access more data as they can read the encrypted DAT log stored in the Mini.
All of below is harder to interpret as you used the prop guards outside ... it's a major no, no to do that as they act as sails & make the usually underpowered Mini even weaker in the slightest wind.
First just a look at the messages in the log ... the Mini was clearly under strain ...
What we have found so far that is common between all uncommanded descend cases is a sudden larger pitch movement just when the descend starts (found in the graph below were the colored markers is). Just there the drone pick up descend speed & drops fast ... this together with a flight instability. Unfortunately you lose the downlink just after the event starts & when it returns the Mini have descended 18 meters in approx 8 sec. It's there you try to act, you release the rudder and by mistake command full negative throttle shortly, change your mind & push throttle up & again start inputs to the rudder ... but everything in vain, the Mini goes down pitching wildly between +7 & -6 degrees.
This had nothing to do with the VPS sensors, temperature, wind (luckily considering the guards) or fog ... the sensors were reporting correctly, the Mini were reported to be in "sky" so no auto landing were commanded.
If you have the possibility to provide the DAT file stored in your phone it could give us more data regarding the engines ... below how you do it (hopefully the Fly app have created it). The right one ends with FLY030.
Mobile device DAT files (DJI GO 4 & DJI Fly)
The DAT file naming convention, based on the date and time of the start of the file, is: YY-MM-DD-hr-min-sec_FLYXXX.DAT., where XXX is the flight recorder file index from the HOME_dataRecorderFileIndex field in the txt log.
These are retrieved by the same method as the TXT logs. Under both iOS and Android they are in a subfolder, MCDatFlightRecords, in the folder that contains the TXT logs. In some cases, for reasons not fully explained but possibly mobile-device hardware related, and most often under Android, DAT files are not created and that folder is empty. Uninstalling and reinstalling the app sometimes fixes that. One user also found that the process required manual deletion of the app folder (apparently not deleted automatically in the uninstall process) before reinstalling the app. |
|