I'd like to see if anyone can help me figure out what is going on here. I have flown my hexacopter successfully several times in stabilize, alt-hold, and loiter modes, and have tried going into auto a few times before.
Previously, I had uploaded a flight path via USB, read it to double check it had been written, then taken it out to the field. When I switch into auto nothing seemed to happen, it would just loiter.
This time, however, I was using a 3DR telemtry radio, programmed and re-read the WPs before takeoff (I'm fairly sure a home position/alt was set) and when going into auto mode, it decided to head northeast and for the ground, doing a cartwheel in the grass before landing upside down in the road spinning uncontrollably resulting in a rather brutal crash.
Any ideas why my auto mode wasn't going to the waypoints the first few times I tried auto, then last time headed northeast? I attached the log, kmz file, but the path can be seen below. Red is my stabilize mode, orange is alt-hold, and yellow is auto. The only waypoint on the KMZ file points torward 0,0 when right clicked, but when clicking Read WPs, even after the crash, waypoint 1 is obviously not 0,0.
My setup consists of the most recent Hexa-B revision sold on the store, an APM2.5, uBlox-LEA6 GPS, 880Kv motors, 10" props.
Images of the damage: http://imgur.com/a/GOov8. Luckily I was able to straighten out the base of the motors, and I have 2 new arms on the way. Not too bad for what was a rather ugly crash.
Screenshots of the mission:
Replies
I'd fly about 10x higher. Can't crash in the air, and it gives you a chance to recover a problem.
The early issues were caused by flying without GPS lock.
Did you command the stick when you began to fly Auto? It looks good for a moment, Then suddenly it's commanded a 55° pitch. The AP only commanded a 30° pitch. I'll look into it more.
Jason