I need help understanding what happened during my flights today.
I have a 360 class quad with 4 MT2208s, 8045 props, and a 3000mah battery.
With my first battery it was flying pretty well. I did some high speed maneuvers in loiter/althold/poshold and it worked without issue. I also tested RTL a couple of times with no issue. I stupidly over discharged the battery, and luckily had a pretty soft landing. I did not attach the log file for this, but I can if you guys think its relevant.
After that flight, things started to go wrong.
I put in a new battery, and after power up I got some GPS errors. I waited until they cleared, and then tried to take off. I don’t exactly remember what I was doing. The log says I was in stabilize mode, but I thought I was in loiter. Anyways, the quad started climbing erroneously, and I hit RTL. It just kept climbing (above the RTL altitude). I frantically tried switching between a couple of modes, with no response. I finally got it to come down with land/stabilize, and noticed the error tone from the buzzer.
My first impression was that maybe the altitude was messed up, and RTL wasn’t working. The log file clearly shows the GPS and baro alt looking good. So I have no clue as to what might have caused it to continue to climb so much.
After my nerves calmed down a bit, I tried to do another flight. I then had issues trying to arm it in loiter, even thought I had a good hdop. I don’t exactly recall what it was complaining about (How do I get mission planner to spit out the error messages it encountered when looking at the dataflash logs? ) I eventually said screw it, and tried to take off in stabilize to see if it would “settle down”. The flight performance was very off-nominal, and I immediately landed it. I spent a lot of time trying to debug after this flight, but unfortunately did not record dataflash logs. I kept getting numerous pre-arm check errors. The most apparent complaint by mission planner was that the altitude was jumping, and the yaw kept spinning slowly.
I also unplugged the battery for 10 minutes and then plugged it back in to see if that would affect anything – no dice.
several hours later, I powered it back up in my living room. GPS had no issue getting a lock (even though hdop was poor), and it was not exhibiting the spinning yaw issue.
Any help would be greatly appreciated.
- ek