I believe that is why people were pointing out that if you could see the drone you could fly it without phone/tablet. The Controller can still have contact with the drone even if the phone doesn't. You can then monitor the telemetry data on the controller to see if the mavic is getting closer as you fly it forward, adjust direction until you can see the distance decrease. This is how I would get my non-DJI drones back, without a video feed.
Lost Mavic 1 Pro
- Thread starter Global man
- Start date
I'm a bit late to the party, but I had a look at the logs. The log has a picture looking straight at the crash site. So I used the two ski-lifts and the top down view to pinpoint the crash site on the actual picture of the location.
this with the GPS coordinates from @sar104 should make it easy to find unless someone else found and took it already.
this with the GPS coordinates from @sar104 should make it easy to find unless someone else found and took it already.
Or fly up to height that you KNOW will clear obstacles, then signal RTH. Remote does provide essential telemetry, except direction. However you might be able to figure relative direction to you based on change in distance as you fly straight.
Or, just stay put until you get the app back up. App crashed a few times so I know how it feels. Even close to me I had issues as I was under a park pavilion and in tight landing quarters, remote tethered to a tablet.
Or, just stay put until you get the app back up. App crashed a few times so I know how it feels. Even close to me I had issues as I was under a park pavilion and in tight landing quarters, remote tethered to a tablet.
As I mentioned earlier, at no point was the connection between the aircraft and the RC lost, and the DJI GO app on your phone logged the flight until just before it crashed. The actual impact was not recorded but seldom is at that speed due to the latency in the telemetry transmission. The disconnect could, completely coincidentally, have happened just before the impact or, more likely, was due to the impact.
Simply because on the trajectory recorded it was less than 2 seconds from impact with that stand of trees, even if it made it there which is dependent on the altitude and DEM data being accurate. In other words it was unquestionably about to crash. Firstly, it would be a remarkable coincidence if a disconnect randomly occurred at the same time for a separate reason and, secondly, even if it had disconnected and been able to stop before impact (not at all likely at that speed), then it would have either reconnected or executed a failsafe RTH which, obviously it did neither of.
DRONE RECOVERED!!! SAR104 a million thank yous! We were able to retrieve the drone pretty much right where you said it would be! At first look only one propeller has been damaged. Have to have Global Man inspect it thoroughly but I just picked it up and it looks in very good shape minus some dirt and grass stains. It seems to have gone down the path into the woods near the coordinates you provided and luckily appears that it just clipped something then went down! Amazing! Thank you again. I will have Global Man report further on its condition.
Last edited:
KeithLa
Well-Known Member
Looking at the trajectories in the photo on your first explanation post, I was wondering if it's possible the intervening stand of trees might have diminished and ultimately broken the aircraft connection. Until the AC flew behind that stand of trees and towards the ski slope, it appears to have had nice high LOS to the RC. Where I fly over a forested greenbelt near my home, the Ocusynch connection plummets quickly as more treetops intervene.
In that event, and IF (big "if") it was still higher than the trees, AND aircraft disconnect was set to "land" or "hover" instead of RTH, might the AC have avoided impact and either landed intact, or crashed upon automatic landing into the trees.
Given the high approach speed that's a great outcome. I'm glad that you found it.
KeithLa
Well-Known Member
Agreed, congratulations on the recovery, and kudos as always to sar104 on the analysis.
To finish the story, I'd love to see @sar104 analysis on the detailed flight log recovered from the aircraft itself, to ascertain whether there was AC disconnect, impact, failsafe RTH, or some combo of those. IMO AC disconnect due to the intervening trees, followed by failsafe RTH or land still seems plausible, vs. direct impact.
To finish the story, I'd love to see @sar104 analysis on the detailed flight log recovered from the aircraft itself, to ascertain whether there was AC disconnect, impact, failsafe RTH, or some combo of those. IMO AC disconnect due to the intervening trees, followed by failsafe RTH or land still seems plausible, vs. direct impact.
My brother who recovered the drone says it appears to have flown successfully in the forest for a short distance before it crashed so perhaps the signal was impaired by the forest as you say.
Drone is in very good shape, I am so happy. Propellers took the bulk of the damage. Even left out in the rain it is not ruined as it was protected by the trees. Attached are the two most recent .dat files from the flight. SAR104 interested to hear what you learn. I had to change the file extensions to .txt in order to upload. These are the .dat files.
Those are DAT files from the mobile device, and so don't contain anything after the end of the txt log. We need FLY096.DAT from the aircraft itself if you can retrieve it.
How to retrieve a V3 .DAT File from the AC
Not seeing that file name on the drone itself got a few DJI Assistant export files but there wasn't one from September 25th when it crashed. Just Sept 27th when I tested the propellers afer I got it back. Should I upload that?
Similar threads
DJI Drone Deals
New Threads
-
-
Litchi needs permission to start and control phone conversations & record audio?!
- Started by Ronny St.
- Replies: 0
-
-
-
Forum statistics
