I would have added more to my response on the last post but I kept falling asleep and waking up with a couple thousand different letters I had to keep deleting. lol!
I have yet to get a chance to work with ilovecoffee's GS app, but it crossed my mind as a possibility to why the flight path appeared.
Were you able to see what happened(the crash) from the point in which the data stopped?
Did the quad attempt to land but just landed in something like a tree or bush?
Did the quad gradually lose altitude as it was flying, and until it hit something?
Or did it just go straight down at the crash site?
I can not see there being any way your actual gps module failed. But based on my own personal experience, it looks to me exactly like the GPS Plug Connection issue I posted about. Did you ever get a chance to secure your plug at all? I did mine by wedging a piece of plastic wire tie in between the plug & connector. Once added I never experience another issue. But prior to adding the fix, the quad would get totally confused because the gps was unable to give a proper reading. My quad would begin descending on it's own at a rapid rate until I would notice it and switch the S1 switch in & out of GPS Mode. That seem to reset the GPS and it then knew where it was again. Had I not flipped the switch the quad would have crashed into the ground at 40-50mph.
A couple of things to point out about the flytrex. With the flytrex or most any device they will not save data to the point of loosing current. They have to be powered down properly so they can close the file cleanly.
The other thing is the way the flytrex current reads Speed. It currently ONLY records the Speed when the quad is in a horizontal flight. It does not see any speed when the quad moving Up or Down. I have shown the Flytrex Tech's their devices already read that data. they just need to add in the soft along with the others and we will have a good piece of logged info that we can use. Btw, this is why on a dashware gauge doesn't display any vertical movement. And it really sucks! Especially when it is such an easy addition. The gauge will show your quad as not moving and look like a dot. Anyway, so when you look at speed/mph reading on your .csv file it shows a inconsistent pattern in your speed/mph column.
I have yet to get a chance to work with ilovecoffee's GS app, but it crossed my mind as a possibility to why the flight path appeared.
Were you able to see what happened(the crash) from the point in which the data stopped?
Did the quad attempt to land but just landed in something like a tree or bush?
Did the quad gradually lose altitude as it was flying, and until it hit something?
Or did it just go straight down at the crash site?
I can not see there being any way your actual gps module failed. But based on my own personal experience, it looks to me exactly like the GPS Plug Connection issue I posted about. Did you ever get a chance to secure your plug at all? I did mine by wedging a piece of plastic wire tie in between the plug & connector. Once added I never experience another issue. But prior to adding the fix, the quad would get totally confused because the gps was unable to give a proper reading. My quad would begin descending on it's own at a rapid rate until I would notice it and switch the S1 switch in & out of GPS Mode. That seem to reset the GPS and it then knew where it was again. Had I not flipped the switch the quad would have crashed into the ground at 40-50mph.
A couple of things to point out about the flytrex. With the flytrex or most any device they will not save data to the point of loosing current. They have to be powered down properly so they can close the file cleanly.
The other thing is the way the flytrex current reads Speed. It currently ONLY records the Speed when the quad is in a horizontal flight. It does not see any speed when the quad moving Up or Down. I have shown the Flytrex Tech's their devices already read that data. they just need to add in the soft along with the others and we will have a good piece of logged info that we can use. Btw, this is why on a dashware gauge doesn't display any vertical movement. And it really sucks! Especially when it is such an easy addition. The gauge will show your quad as not moving and look like a dot. Anyway, so when you look at speed/mph reading on your .csv file it shows a inconsistent pattern in your speed/mph column.