Hi, first post here, not a newbie but always plenty to learn
Had a miserable crash today with my Hex:
Arducopter 3.1.3 (probably had this problem before)
External compass+GPS (neo-6m)
Managed to load 3DR config to GPS even though its old style GPS connector (all red wires…)
Copter took of great in stabilized, almost looks like loiter or alt hold.
Moved to AltHold
Moved to Loiter
Started going a little
Then copter starts rolling to the right (maybe pitch backwards) agressivly
Move to AltHold while it zooms towards a tree, can’t get control, lower motors… not sure what stopped it before it hit the ground - i.e. did i gain control or did it just crash…
I must admit, the same happened flight before that, it moved very aggressively backwards, I moved to althold, regained control and continued a great ~10 minutes more flight, the second time hasn’t ended well…
This was about the 10th flight of the hex and i’m pretty sure I had these events on some other flights but very very brief (like half a second) so I dismissed them, might even had them when this APM wasn’t an hex…
My diagnostics seen this: there was a gps error 1 on the logs (lost gps lock for more than 5 seconds) follow by gps error 2 (got gps lock back)
everything configuration wise is almost default so
GPS Failsafe is on 1 - Land.
My guess is that once lock came back it tried to fix the position,
But I never seen loiter move this fast, it was really aggressive.
If it lost GPS for 5 second and failsafe was on 1, why didn’t it try to land? now I will change the default to switch to AltHold, seems more reasonable (unless the GPS is lost after a radio loss…)
Attached are the logs -
Small log is the crash
Big log is the save at the start and then a long flight.
Please help me to understand, i’m suspecting there is something wrong in the way arducopter handled this situation although I would love to know if there is a physical problem that caused the gps loss.
Did i loose signal or lock (bad gps connection)? does arducopter just keep the last position? so if i move in those 5+ seconds it tries to go to the original position before the loss? maybe the gps glitch patch gets confused?