slup, thanks for the help. I couldn't find it in that area, but I assume someone picked it up as it was likely just lying there on the beach for a while and it's pretty crowded today. But I appreciate you pointing out what I did wrong. Makes total sense now that I think about it as I got the updated HomePoint message in the area you mentioned. Should have known to look there first, but oh well.When you lost the connection you were up on 146ft ... way above that house in the end of the known flight path. The RTH height was set to 98ft which was below the altitude zone of 197ft & the failsafe action was set to RTH. Also nothing in the log indicate that your Mini hit something just in the end.
View attachment 134058
The wind speeds seems to have been low, nothing that would have made your Mini Blow away ...
View attachment 134056
But it's a bit odd that this is logged in the .TXT message stream though ... was it mild winds?
View attachment 134063
So in the end everything points to that your Mini should have returned home on 146ft against a pretty mild wind after you lost connection.
But here I'm pretty sure we see the reason for why you didn't see the Mini return ...
You launched in a hurry ... you didn't have a HP recorded when you got airborne ... the HP was recorded later along the flight path ... at 47sec into the flight, by then your Mini was out over the beach. And if you didn't know this you searched for your Mini in the wrong location.
Here below in the chart I've placed the markers where the HP was recorded ... you can read off latitude & longitude for the recorded HP in the legend below the chart.
(Click on the chart to make it larger)
View attachment 134064
Here a part of the flight path on a sat picture ... the green star marks the HP. Your Mini most probably waiting for you there ... go get it ?
View attachment 134065
Got it, thanks again.During normal circumstances & not with anything wonky going on with the connection It should have reconnected ... but if you pointed the RC wrongly and/or if the area was full of WiFi interference (all the hotels I see there in GE) it perhaps failed to do that.
It most probably did, but not to the location the OP thought, check post #2. And by the way... Airdata's HP position is wrong.Yup. Don't know why it didn't come back though.
Such an amazing report!! ???When you lost the connection you were up on 146ft ... way above that house in the end of the known flight path. The RTH height was set to 98ft which was below the altitude zone of 197ft & the failsafe action was set to RTH. Also nothing in the log indicate that your Mini hit something just in the end.
View attachment 134058
The wind speeds seems to have been low, nothing that would have made your Mini Blow away ...
View attachment 134056
But it's a bit odd that this is logged in the .TXT message stream though ... was it mild winds?
View attachment 134063
So in the end everything points to that your Mini should have returned home on 146ft against a pretty mild wind after you lost connection.
But here I'm pretty sure we see the reason for why you didn't see the Mini return ...
You launched in a hurry ... you didn't have a HP recorded when you got airborne ... the HP was recorded later along the flight path ... at 47sec into the flight, by then your Mini was out over the beach. And if you didn't know this you searched for your Mini in the wrong location.
Here below in the chart I've placed the markers where the HP was recorded ... you can read off latitude & longitude for the recorded HP in the legend below the chart.
(Click on the chart to make it larger)
View attachment 134064
Here a part of the flight path on a sat picture ... the green star marks the HP. Your Mini most probably waiting for you there ... go get it ?
View attachment 134065
Saw this report and immediately went and registered with AirData. So far I'm just doing the tier 1 free level but I uploaded today's log and was pleasantly surprised with the detail in the presentation. In looking a the report you posted, I'm wondering if the first image that shows the "curtain" view of the flight path, which allows one to see a 3D image of both the path plus altitude, was generated with AirData.When you lost the connection you were up on 146ft ... way above that house in the end of the known flight path. The RTH height was set to 98ft which was below the altitude zone of 197ft & the failsafe action was set to RTH. Also nothing in the log indicate that your Mini hit something just in the end.
View attachment 134058
The wind speeds seems to have been low, nothing that would have made your Mini Blow away ...
View attachment 134056
But it's a bit odd that this is logged in the .TXT message stream though ... was it mild winds?
View attachment 134063
So in the end everything points to that your Mini should have returned home on 146ft against a pretty mild wind after you lost connection.
But here I'm pretty sure we see the reason for why you didn't see the Mini return ...
You launched in a hurry ... you didn't have a HP recorded when you got airborne ... the HP was recorded later along the flight path ... at 47sec into the flight, by then your Mini was out over the beach. And if you didn't know this you searched for your Mini in the wrong location.
Here below in the chart I've placed the markers where the HP was recorded ... you can read off latitude & longitude for the recorded HP in the legend below the chart.
(Click on the chart to make it larger)
View attachment 134064
Here a part of the flight path on a sat picture ... the green star marks the HP. Your Mini most probably waiting for you there ... go get it ?
View attachment 134065
Sort of ... It's generated from the downloaded .KML file from Airdata. (Note that the HP is wrong in Airdata)...I'm wondering if the first image that shows the "curtain" view of the flight path, which allows one to see a 3D image of both the path plus altitude, was generated with AirData.
Thanks for the great illustrated instructions slup! I'll give it a try!Sort of ... It's generated from the downloaded .KML file from Airdata. (Note that the HP is wrong in Airdata)
View attachment 134210
You can also upload the mobile device .TXT log to DJI Flight Log Viewer | Phantom Help & from there download their .KML file. (Here the HP is in the correct spot, totally corresponding with what's written in the original .TXT log)
(Click on the pic to make it larger)
View attachment 134211
Once you have a .KML file over the flight locally on your computer you open it with Google Earth ... find the path in the left pane, right click on it & chose "Properties"
(Click on the pic to make it larger)
View attachment 134212
In the Properties, open the Altitude tab & check the "Extend path to ground" box ...
View attachment 134213
Then open the Style, Color tab & set it to "Filled" & adjust the opacity to your liking ...
View attachment 134215
Hit OK in the "Properties" window ... & you're done.
We use essential cookies to make this site work, and optional cookies to enhance your experience.