- Joined
- Mar 14, 2016
- Messages
- 310
- Reaction score
- 39
- Age
- 36
working on the file retrievalIm mildly amazed by all the insistence on getting the .dat uploaded.
Reasonable expectation is if it is made available for analysis here (doubtful, its a trivial process to extract the .dat from the bird and plenty of help available if the op had difficulty. It seems there in no intent to make available here) it would be demonstrated that;
1. The bird managed to initiate follow from just after launch (operator initiated) and unfortunately the power lines where in the path between the mission engage point and the commanded location.
2. The operator became aware of the likiehood of the collision and seemingly madly executed a serious of perhaps approprate however ultimately pointless stick movements (the phantom was diligently executing the commission with any control inputs disregarded while in F mode) to avoid the collisiom.
3. The operator, not understandimg how to correctly perform a CSC command put themself in harms way trying to power down the phantom.
There may have been a failure of the GPS subsystem to provide correct coordinates or a variety of other software issues in play here however switching out of F mode would have almost certainly returned control to the operator and likley avoided the outcome.
Return it to DJI, they will take care of it if it is a "technology failure" as claimed.
Alternatively learn from it, pay the money to have it fixed and enjoy it.
your 1st conclusion is not 100% accurate
your 2nd conclusion is false
your 3rd conclusion is that csc was perform but did not work.
to put it simply it was as though the RC had no affect after the fly away, also dji has my bird and RC as of today and im not paying dji a dime.
Sent from my iPad using PhantomPilots mobile app
Last edited: