Recent content by mgerety

First of all, let me just say thanks to everyone who is contributing in this thread.. you guys are awesome and I've already learned a ton. I'm off to ship this thing to DroneFly. I'll keep monitoring, this is hugely interesting.

I can see that. There;s a lot more minute variances in the djilogs file. I just want to be sure however, we're still pretty sure this was a crash due to hitting something, and not because the drone operated improperly (causing the crash), correct?

That first image is the LAUNCH point. There is a big difference between the crash points. The djilogs KML shows the drone is much higher, and falls further. The HealthyDrones file shows it much closer to the trees, and less of a descent.

At this log point: 11/15/2015 1:00:08 AM There is a switch to ATTI mode and "SPEED_ERROR _LARGE" and it goes down after that. Would this happen from a strike?

Is that likely at night? Either way, it looks like I hit *something*. What I don't like is the disparity between the djilogs.KML and the HealthyDrones KML. If anyone has any insight on this I'm all ears.

I've attached an image showing the KML exported from djilogs.com. This one shows me WAY above the trees with a much sharper drop. Any idea why this would be? Which one is more accurate?

Care to share a few?

When you say it "broke speed", what does that mean? From everything I've been shown/I can deduce, the crash was due to me hitting a tree because I thought I was 47M above the current location, not 47M above my starting location. 47M = ~155Feet. There was a ~120 foot elevation change between the...

*edit* -grammar I saw this yesterday... Google Earth has come a long way since I last looked at it, and the ability to export the KML from HealthyDrones and import into Google Earth is awesome. This really makes it look like the crash was due to my misunderstanding of the elevation...

Open app. Look in top left. See icon that looks like paper airplane. Click it.

That's awesome. I will ABSOLUTELY try that when I get home. If that's the case, I'll probably ship off to DroneFLY instead of DJI to get it repaired.

ok.. that is likely it then. Thanks a ton for helping me understand what might have happened.

Now THAT might explain it. Is the elevation measured by the app/drone based on the launch point and not relative to current position?

Also, what's up with the switch to Atti mode? -- any idea?