Todd in Chicago
Second Officer
Flight distance : 513757 ft
United States
Offline
|
Folks...
I was able to download all of my DAT files from the aircraft, and open them in the viewer, but that is not an easy program to use, and I was not really able to learn anything from that. Also, all that data appears to be numerical in nature meaning values that are changing vs. error messages or conditions. I'll try again tomorrow but tonight was not really able to make any progress with understanding the DAT files, so nothing happening on that front yet.
When my patience wore down there, I went back to studying the downloaded CSV file from PhantomHelp.
Overall throughout my flight I had very decent satellite coverage with about 14-18 satellites.
One thing I noticed was that I never had any "drops" until I was coming home. I was literally out to 5,000 feet with no drops. When I decided to come home, that is when the trouble started. Even though I was pretty high, about 240 feet or so and only 2,500 feet from home, that is when I started to have the disconnects for who knows what reason (these things happen). Just an interesting note.
At 9m 38.9 seconds I received my first series (4 in a row) of mysterious GPS Position NoMatch messages, which Google doesn't seem to know the answer about. From what I've been able to gather, DJI has not provided the answer for what this message is, nor does it appear on screen when it occurs, it is simply noted in the log files.
At 9m 41.9 seconds I received my second series (3 in a row) of GPS Position NoMatch messages.
10m 20.9 seconds next series (5 in a row) NoMatch messages.
10m 40.9 seconds next series (5 in a row) NoMatch messages.
I received my final series of NoMatch messages for this flight at 10m 52.9 seconds (4 in a row)
See a pattern there? ;-)
Since all of these messages were received at a xMins xx.9 seconds, this is probably some cyclical timing thing. Weird, but probably makes sense as I'm guessing GPS is all about timing.
About a minute and a half later I reached my furthest distance of 5,054.10 feet at 12m 5.4 seconds and begin flying back.
I'm coming back at a speed of about 16-17mph.
About almost 2 mins later at 13m 57.7 seconds I lose connection for almost 4 seconds. I have reduced the distance from my furthest point to my home point to 2,877.8 feet.
About 1 minute 9 seconds later I lose connection again, this time for about 2.5 seconds at 14m 6s.
18 seconds later I lose connection again for 2.3 seconds at 14m 24 seconds.
5 seconds later I lose connection again for 2.2 seconds 14m 29.5 seconds.
About 15 seconds later I lose my connection for the last time, but this time for 11 seconds at 14m 44.7.
The very next entry, which is when the downlink is restored, the flight mode is showing Go Home. It does not say if that was requested by me or if the aircraft itself initiated the RTH. At this point my RTH distance has been reduced to 2,358 feet.
At 15m 1.3 seconds the Phantom has turned around and is starting to fly in the opposite direction and makes it as far as 2,393.7 feet which is 36 feet from where it turned around. I had cancelled the RTH function as I saw that it was flying in the opposite direction, but the logs do not seem to show the cancellation command.
At 15 10.7 seconds P4P is out of RTH mode and back in GPS mode.
At 15 17.3 seconds I switch into Sport mode and try to get back as fast as I can.
Logs show another series of 5 in a row of the NoMatch errors, again on the .9 (16m 10.9 seconds)
At 17m 9.4 seconds I'm back home....roughly 2 minutes after the P4P had started going in the wrong direction.
Whew.
Ok....so I'll do some testing to see what happens if the P4P loses connection to the controller. Does anyone know if it starts to backtrack, does it actually turn around? It would seem to me that it would just fly backwards...?
If anyone knows how I can coax the RTH data from the DAT file or can point me to where I can learn to do that, I've to take a whack at it.
Cheers...
Todd in Chicago |
|