Labroides
Core User of DJI
Flight distance : 9991457 ft
Australia
Offline
|
djiuser_e08k81qRTMOd Posted at 3-22 15:26
Hi JJB, thanks for the in-depth analysis. Looking at the graphs/charts, Is see a few things, such as the drone heading and drone moving are going in the opposite directions. I also noticed the drone rising in altitude on the day of the flight.
Do you know if the Gps value 17 displays the number of satellites locked. Thank you for the visual representation. Just so I'm clear, would it be down to Software issues or the drone operators error or any other factor I've not taken into account?
GPS had no problems and 17 sats were locked at the end of the flight.
Here's what I see in the data.
The problem first showed up at 2:06.8 when you tried left stick full down from 90 feet.
Despite ful stick down the drone climbed at approx 2 m/s and climbed to 150 ft.
You briefly tried pushing the left stick up and the drone climbed a little further.
The first thing I look at with drones that won't descend is the VPS sensors, but yours look to have been working perfectly.
With the left stick in the centre position, the drone kept climbing.
At 2:34, with the left stick in the neutral position, it was climbing at 4 m/s (nearly max climbing speed).
The altitude sensor was working properly and the drone recognised that it had reached the Max Altitude Limit at 400 ft and kept going without any throttle input.
The climbing kept going regardless of the drone's heading, so obstacle avoidance can be discounted as an issue.
At 3:14.7 full down stick had some effect and the drone descended 42 feet before it started to climb again (with no throttle).
At 3:40, down stick again had some effect (30 ft) but by 6:46 the drone was climbing again despite full down stick.
There was a problem that seriously affected the drone's ability to hold altitude or sespond properly to left stick input.
This was a genuine serious rare hardware fault and there appears to have been nothing you could do to save it.
The number of times the "Excessive attitude angle detected, forward obstacle avoidance has stopped working" message shows up is another odd thing, probably indicating more issues.
In P-GPS the drone was frequently exceeding 30 degree tilt.
You lost signal at 5:25.8 with the drone up 1450 feet and being blown backwards by the upper level winds.
Signal was regained a minute later with the drone now in RTH at 2277 ft and finally lost again at 6:53.6.
The drone will have blown further until reaching critical low voltage and (if things worked normally) it would have descended, possibly a couple of miles further to the northeast from where signal was lost.
If the drone was less than one year old, this will be a warrranty issue.
Even without the drone or wreckage, the flight data should be enough to prove the incident was a hardware failure. |
|