Cyberpower678
Well-Known Member
- Joined
- Jan 11, 2017
- Messages
- 3,881
- Reactions
- 1,782
Yep. It will make the flight available for us to see.
Please also upload your TXT flight log to my log viewer above. Healthy Drones is not going to provide much useful data.
Just having a look at the sensor info - point (j)states it was at 157.5m altitude at 20'30" so was obviously in auto landing mode but my calcs suggest that total flight time of 20'51" so from 157.5m to 0m in 21 seconds is a decent speed of 7.5m per second ............. that's almost the same flight characteristics as a brick ! Not sure what will be left of the Mavic dude.
It looks like you lost connection during the landing process. Analyzing the trajectory it had, and assuming it didn't lose power during landing, it looks to have landed around the coordinates 46° 2'10.91"N and 95°27'46.54"W. It appears to be an open field, so it should be fair easy to find.Hopefully I did this correctly.
HealthyDrones.com - Innovative flight data analysis that matters
looking forward to learning more about this data from those who review it.
There appears to be a 'dead end' track just north of the road. i don't know what
this is.
HealthyDrones.com - Innovative flight data analysis that matters
Open field just north of Indian Lake Road NW
As someone who's expecting a mavic on Monday, do you get confirmation of sufficient GPS and a lock on home point or is it easy to miss this?I'm also seeing another concern that resulted in RTH failing. You took off without sufficient GPS strength to lock on the home point before take off. Consequently, the log doesn't indicate the home point was set on take off. I'm also seeing several compass errors in your compass subsystem. It looks like the RTH was trying to use the compass to come home, only that it wigged out midway through.
If the volume is turned up on your mobile device, DJI GO will announce when the home point has been marked after starting the motors.do you get confirmation of sufficient GPS and a lock on home point or is it easy to miss this?
It looks like you lost connection during the landing process. Analyzing the trajectory it had, and assuming it didn't lose power during landing, it looks to have landed around the coordinates 46° 2'10.91"N and 95°27'46.54"W. It appears to be an open field, so it should be fair easy to find.
Keep in mind that these coordinates are an approximation I made through a rough analysis. Also, since it's been raining, you should let your Mavic dry out first before sticking in a fresh battery, else you may damage the Mavic by shorting out some components.I have been out most of the morning looking for it. The area where the green line ends, is an open field of modest rolling hills. Raining for the last 12 hours so the snow cover is disappearing. The ground is covered with prairie weeds, clumps not more than 18" high.
I started the search by studing the flight lines from CyberPowers flight data, the one with the second by second flight data with the map above it. I then eyeballed the end of the green line in the field and marked what I thought was the end of the green line onto my Navionics navigation app I have on my iPhone. With CyberPower providing the actual coordinates, I am about to head out again to search for the drone.
Keep in mind that these coordinates are an approximation I made through a rough analysis. Also, since it's been raining, you should let your Mavic dry out first before sticking in a fresh battery, else you may damage the Mavic by shorting out some components.[/QUOTE
To all of you who have helped me learn more about my drone, a sincere thanks.
I have benefited greatly from your knowledge and advice. I simply went to where you told me to look and found it, unscathed. None of the rotor were compromised.
I plan on reaching out to DJI directly, sharing the flight logs, to determine what caused the fly away.
Thanks again,
Yellowtennies
When you find it...and you will find it. I would probably use canned air to get the water out of the motors. That should be the only place that water causes an issue.
Sent from my iPad using MavicPilots
We use essential cookies to make this site work, and optional cookies to enhance your experience.