You need to copy and paste the URL link from the browser. As long as the "link" is sharable we can access that. It is not a "direct share" with a particular individual.I sent the to Dropbox and clicked share. A box come up saying who to share with.
You Sir, are the most patient person I have ever seen on a public forum. THANK YOU, for all the time and effort you put into helping others, you are making it a better place. ?You need to...
@Fly Dawg this looks to be a valid Export...DAT file. But, ExtractDJI isn't able to process it correctly. I'll look into it.Dropbox - File Deleted - Simplify your life
www.dropbox.com
@Fly Dawg this looks to be a valid Export...DAT file. But, ExtractDJI isn't able to process it correctly. I'll look into it.
I thought there was something amiss with that file. Wouldn't extract here either.But, ExtractDJI isn't able to process it correctly.
Ok guys @BudWalker, it looks like FLY029 is the correct file for this flight. The aircraft apparently shutdown at ~378 sec. But what is very odd is that the RC Throttle command continued to record after the shutdown. This one is different than the other shutdowns I have seen. What do you think? @sar104
View attachment 110104
@sar104 ...You are on the clock at your leisure....
@Klloyd99 .....Refer to Post #21 and try to upload your device log for this flight for comparison. According to this data the RC was still recording to the aircraft, although it appears to be a complete power loss. Very odd. I'd like to see the RC data.
@Klloyd99 .....Refer to Post #21 and try to upload your device log for this flight for comparison. According to this data the RC was still recording to the aircraft, although it appears to be a complete power loss. Very odd. I'd like to see the RC data.
@Klloyd99 .....Refer to Post #21 and try to upload your device log for this flight for comparison. According to this data the RC was still recording to the aircraft, although it appears to be a complete power loss. Very odd. I'd like to see the RC data.
I thought that might be the case but went with it anyway. It is the only flight that "appeared" to be close to what the OP what describing. That would also explain the date being 2015. None of the flights from March 29th, ( The date of the incident ) are real flights. Although it also appears that the firmware was changed at FLY034. Not that it means anything. FLY025 had many compass errors and GPS issues, but other than that one and the sim run. I can't locate another flight as the OP described.FLY029 is a simulator run.