I think I know now what happened to the OP - it happened to me today!
Since having video lag etc often on the K1 tablet, I thought I give it a try with my Google Pixel XL phone (Android 7)
Bad idea!
I managed to go quite some distance over a river, I was standing next to it on a dike.
No signal problems. Just as I turned around the app crashed.
I restarted the app and continued to fly home.
When I checked the flight at Air Data I realized that upon restarting, the Go4 app automatically set a new homepoint - at the AC, over Water!
I'm lucky I didn't rigger RTH. The drone would have gone for a swim.
Since multiple app crashes are being reported, there should be an option in the app:
"Do not record homepoint automatically"
My suggestion:
IF THE APP CRASHES, DON'T RESTART IT! Trigger RTH on the remote!
See top left in the image:
It says "H" for homepoint at the moment where the app was back up working.
My actual homepoint was to the right at the bottom.
View attachment 79603
Your Airdata screenshot above is not necessarily showing the home point was reset since Airdata always shows an "H" at the first data point on the map. Please upload your TXT flight logs here and post the links back here so we can see what you're describing.But when the app crashed that initial home point was gone.
I guess an app crash results in some info loss compared to closing an app.
Your Airdata screenshot above is not necessarily showing the home point was reset since Airdata always shows an "H" at the first data point on the map. Please upload your TXT flight logs here and post the links back here so we can see what you're describing.
That's why it's important to look at the flight log data itself.In the second log you see at 10m43.4s a flag and "Home Point Set".
That wasn't me!
Can you explain where you're seeing this home point being recorded in the flight log?The automated mid-air homepoint is at the beinning of the second log, where the flag is.
That's the one I have been wondering about and which shouldn't have been recorded.
The "Home Point Set" message is just showing the home point was set in the log. It doesn't mean the home point was changed. I just removed that message from my log viewer since it seems to be more confusing than helpful.
Click the "Download CSV" link to download the flight data in CSV format. You'll be able to see the home point coordinates are as shown in my image above. The home point was never set to the flag icon in your image above.
Thank you for looking into this!
These two home points are in the first log at the very beginning.
First HP was the automated recording upon start up. 14s later I chose HP at AC.
The automated mid-air homepoint is at the beinning of the second log, where the flag is.
That's the one I have been wondering about and which shouldn't have been recorded.
The cvs file of the second log (after app restart) shows only one home point: At the flag.
That was automatically set when the app re-connected to the AC.
Those HPs in the first log (in your screen shot) were lost when the app crashed.
They are not shown in the 2nd log.
I bet my K1 on it ;-)
If I had triggered RTH it would have gone to that mid-air home point until battery is empty.
And then for a swim...
We use essential cookies to make this site work, and optional cookies to enhance your experience.