Did you get a chance to look for the MA? It's likely that it came to rest at the location I showed you in post # 21. That's coordinates Longitude 18.812661°, Latitude -34.099026°.Thank you BudWalker this was a problem coming, now I know. Just wish I can find the drone.
Hi BudWalker,Hi BudWalker, yes we looked in the spot for day`s. Area was a security area back in the day`s. ( they use to test explosives) I was granted permission to search there. The spot is so overgrown that you could be 1 meter away and not see it. The only hope is the the craft had my cell number on an someone (with reward) will find it. I do get some feed back form DJI and I expect to get a result from them soon. I`ll let you know.
Thanks for you concern.
Nah, I've taken off from 999 compass spots and it works fine.There are a few possible explanations for this behavior, but the txt log doesn't contain the necessary data to distinguish between them. The problem was a disagreement between the IMU velocity and position data, triggered by a CCW full rotation at 566 seconds:
View attachment 79897
Looking in position rather than velocity space:
View attachment 79898
It might have been a yaw error due to an incorrectly initialized IMU yaw value caused by taking off from a magnetically distorted location, a compass calibration issue, or simply a failure of the IMU inertial sensor package. The lack of any problems for most of the flight generally makes the first two options less likely, but IMU failure is much less common. The answer will likely be in the DAT file (FLY060.DAT) data if you want to retrieve and post that.
Mobile device DAT file: How to retrieve a V3.DAT from the tablet
You are a bit late to the discussion. This one was resolved several days ago and yes - what I posted in #4 was correct. The details, from the DAT file, are discussed in posts #18 and #20.