Mysterious (to me) disconnect and resulting crash, a few minutes into yesterdays flight.
Silly me managed to close the flight session (and mapview) when turning on the GPS on the device, so with the AC disconnected, unable use the GPS/map position of the device and simply walk towards the last recorded GPS position of the AC, as I did on the one previous disconnect/auto landing a number of years back.
After a few hours, I finally remembered to run the txt. file from the device through Phantomhelp and generate a CSV file that gave me the last coordinates.
Entered those coordinates into Google maps on my phone and lo and behold, we were lucky enough to find the M1P, much thanks to the (audible type) standalone drone finder.
At that point (3 hours), the normal, annoyingly loud beeping sound from the finder was down to a faint clicking, but still sufficient to locate it.
Dense vegetation, so we would very likely have missed the AC w/o the finder, so that one is well worth having.
I need to study and learn the fine art of analyzing data files, tons of info, especially from the .dat file.
The .txt file for some reason reports battery status to fluctuate back and forth between 3% and 70%. That was not the case (not reported by RC/app) but that faulty reporting in the log might indicate something specific being off?
The battery had not disconnected, and was down to one LED blinking when I found it after 3hours.
Minor damage, all considered, with only a snapped camera ribbon wire and missing rubber tabs under one front arm and one under the belly.
Here is the file generated by Phantomhelp:
Also attached the txt. and dat. from the device.
Note: connected the AC to my laptop and tried to retrieve the .dat file from the AC, as that one would have data from post RC disconnect, but I was unable to find it.
The only files that I can see are those that were generated when connecting the AC to the laptop, as well as some old ones (from January and before). Screenshot attached.
Silly me managed to close the flight session (and mapview) when turning on the GPS on the device, so with the AC disconnected, unable use the GPS/map position of the device and simply walk towards the last recorded GPS position of the AC, as I did on the one previous disconnect/auto landing a number of years back.
After a few hours, I finally remembered to run the txt. file from the device through Phantomhelp and generate a CSV file that gave me the last coordinates.
Entered those coordinates into Google maps on my phone and lo and behold, we were lucky enough to find the M1P, much thanks to the (audible type) standalone drone finder.
At that point (3 hours), the normal, annoyingly loud beeping sound from the finder was down to a faint clicking, but still sufficient to locate it.
Dense vegetation, so we would very likely have missed the AC w/o the finder, so that one is well worth having.
I need to study and learn the fine art of analyzing data files, tons of info, especially from the .dat file.
The .txt file for some reason reports battery status to fluctuate back and forth between 3% and 70%. That was not the case (not reported by RC/app) but that faulty reporting in the log might indicate something specific being off?
The battery had not disconnected, and was down to one LED blinking when I found it after 3hours.
Minor damage, all considered, with only a snapped camera ribbon wire and missing rubber tabs under one front arm and one under the belly.
Here is the file generated by Phantomhelp:
Also attached the txt. and dat. from the device.
Note: connected the AC to my laptop and tried to retrieve the .dat file from the AC, as that one would have data from post RC disconnect, but I was unable to find it.
The only files that I can see are those that were generated when connecting the AC to the laptop, as well as some old ones (from January and before). Screenshot attached.
