Sean-bumble-bee
 Core User of DJI
Flight distance : 15997 ft
United Kingdom
Offline
|
great though I am surprised it required rooting the phone.
Jeepers that's a long way out.
In what follows I am not being nasty, the following comments are based on what I see in the csv.
1) It didn't RTH on disconnection because failsafe was set to hover, column DO in the Phantomhelp CSV.
That said I have to ask, did you cancel a low battery RTH at some point in the flight?
If so that would explain why it didn't ''Low Battery RTH'' after the disconnection.
Low battery RTH is, as far as I know, a ''one time only per flight'' offer, cancel it and the drone will not offer another automated low battery RTH during that flight.
I assume you did cancel a low battery RTH because I would have expected the low battery RTH to kick in somewhere from the 14th minute onwards.
2) You launched the drone with the battery at 82%. That is, in my opinion, not a good idea for such a long flight. You should have launched with a fully charged battery and NOT used approximately 1/2 the available charge during the out bound flight.
3) If you did not cancel a Low Battery RTH then you got VERY lucky in this flight. If a Low Battery RTH had kicked in after the disconnection then the drone would, almost certainly, have entered low-battery forced-landing whilst en-route to the home point, possibly over the fields and possibly whilst still disconnected.
Finding it would then have meant a long careful walk along the RTH flight path.
4) You lost connection because of the drone's height and distance, which meant that the line of sight between the drone and the controller was, I think, 1/2deg above the horizontal and going straight through a fair bit of forest, forest eats signal.
5) I think the flight goes down as pilot error even if ''Low Battery RTH'' failed to kick in.
I think you were very, very lucky that it landed at a 'known' position, I strongly suggest you do not ''push your luck'' so far again, otherwise I think you are going to lose the drone.
|
|