Labroides
Captain
Flight distance : 9991457 ft
Australia
Offline
|
This is what that data looks like:
https://www.phantomhelp.com/LogViewer/YYR8UR0UTALYTHKLE68D/
So today I went to an area where I have flown heaps of times, (absolutely no chance of magnetic or other interferance)
There may well have been magnetic interference at the launch spot.
Your flight data shows, a Yaw Error at 4:25.2 and compass errors at 5:26.2, 7:33.2, 7:56.6, 8:18.2, 9:27.6, 9:28.8, 9:31.2, 9:38.9 & 10:10.5.
This was probably unrelated to the lost GPS issue but without seeing data from the previous flight at a different location, I can't be certain.
You are lucky the yaw error was only a small one.
Most yaw errors are unrecoverable and end badly.
What direction was the drone facing at the launch spot?
What was the surface you launched from?
All seems perfect prior to and at launch, but within a very short period I get the ATTI mode message again. I bring the drone back to take-off point in the hope that it will hook up to GPS satelites again - but no.
I continued to fly visually but soon lost even the 'Tracking Map' on the screen, well I say I lost it. What I mean is that it froze at it's last position.
During this time the drone is reacting perfectly to the control input - so the link between the RC and the drone is good, however the GPS/satelites are gone.
To my mind this sounds like possibly an electronic component is breaking down after a short 'warm-up' period ????
Your satellite numbers dropped from 13-14 to zero and jumped back to 13-14 at:
0:31.3, 0:33.4, 0:51.4, 1:01.8, 1:04, 3:55.9, 4:07.6, 4:08.7, 4:11.8, 4:14.1
They dropped to zero again at 4:28.5 and stayed at zero until the end of the flight, which is why the tracking appeared frozen.
This looks a lot like an intermittent (at least for the first half of the flight) hardware problem.
Either a faulty GPS unit or a poor connection.
If you power up outdoors now, does the drone find satellites?
|
|