Hoping someone here can help. I currently have a lost drone that I would very much like to find. Situation is identical to Drone lost and Airdata logs don't even show last flight, but I was using an iOS device. I know the data I need to find my drone is on my phone somewhere but DD support has been no help in getting access to the data. Does anyone know if I upgrade to an enterprise account and thus get access to the Flight Logs feature whether the app will show my last flight and thus give clues on the drone location?
I was able to find a way to access the airdata log files on my iPhone. I now have all the DJIFlightRecord…txt files in my possession. However they are binary files that I don’t know how to read. I see in the previous post that I should upload them to Airdata but don’t know how to do that.
Can you help this pilot?
Rob, through some digging I’ve been able to figure out everything for myself.
- Download an app called iMazing to access all the DroneDeploy files on my iPhone
- Grab the flight record .txt file. Which is stored by DroneDeploy, not DJI
- Upload the flight record to AirData
I’ve attached the flight record. I’m hoping your team can determine why the mode was changed to AutoLanding when it wasn’t at the Home location.
(Attachment DJIFlightRecord_2023-05-17_[11-27-34].txt is missing)
Hi Jason I was using an IOS device as well. I was able to manually load my flight legs to Airdata and find the flight. Have you been able to locate them on your phone yet?
Hi Carl, yes, it took some searching but found an app that would give me access to DD’s files on my phone. I uploaded the flight log to AirData which provided me with the last known position. Long story short, the drone is now back home. I’m hoping someone at DD will take a look at the log and determine why their app triggered an auto landing somewhere other than the home position.
Congrats on getting it back! Hopefully you get some answers from DD
You need an AirData account to view the BIN and you can get the rest off the iDevices through iTunes.
I have had this happen only one time when the battery reached critically low levels and triggered an immediate landing where it was at. The situation was a long return-to-home distance against a stiff headwind that the drone was unable to account for when calculating the return-to-home threshold. I think the battery was at 11% when it stopped returning and descended from 400’. Does this pattern match your flight logs?
…I uploaded the flight log to AirData which provided me with the last known position. Long story short, the drone is now back home…
Curious, as the log uploaded to AirData provided the last known position, did it not provide Battery data, Sensors (Signal error data), GPS & Compass data?
Man, I feel your pain times two I have I have hundreds of hours of flight experience. I’ve done at least 100 waypoint missions and have managed to lose two drones in the past four days both while flying an automated waypoint mission for joan deploy considering I do these all the time I’m starting to wonder what the heck is going on because that’s two drones never returned within four days of each other.
I am so so unhappy as I know that it was not user error and it seems like the only other issue is that I’ve been seeing tons of interference warnings well I’ve been trying to find them
P4p x 7
Mini 3 pro x 2
You could say I’m a loyal customer, but this is really making me unhappy
Wow, that kind of loss should make all Drone Deploy app users nervous to say the least!
As a frequent flyer and DD automated map user reading this, I sure am.
I would you (and jasonsue) attach & post your flight log files on this message thread in a reply?
There has to be a DD User (or employee) reading this that could download and dissect the log to help determine what the issue was.
That would be extremely beneficial to us all.
I’ll be using Maps Made Easy for my next few trips unfortunately - - - - I have a feeling that Drone Deploy will say that I’m just a personal user, and not really offer me any support unless I upgrade to ENTERPRISE.