I am having an issue with AC3.2.1 not taking off predictably after an auto mission is started. After the quad is put into Auto mode and throttle lifted on the rc transmitter, the autopilot seems to set a prop rpm that is too low for takeoff. I spent a few seconds moving the transmitter sticks around to trigger a takeoff but nothing occurred until I put the transmitter into the disable position. The quad took off as I held the disable position and I watched it yaw and climb.
I have 2 quads with identical hardware that are experiencing this same issue. I can't think to any hardware or software change that would have triggered this effect.
The procedure I've been following is:
1. Load mission
2. Arm quad
3. Set Auto
4. Throttle up
I tried to gather some information from the logs and have been able to confirm what I've observed but not the reason as to why it occurred.
Start of Auto mission:
Beginning of actual takeoff (Transmitter in disable position):
RCOUT:
I've attached the log file of the flight and can collect more if needed. I'd appreciate it if someone could take a look to help me figure out why the autopilot isn't triggering a successful takeoff predictably.
Thanks!
Replies
I solved this issue.
I am using afro 30A escs with 880kv 3dr motors. The rapid change from 0 throttle to 100% throttle caused a glitch in the ESCs that wouldn't provide full power to the props. Human controlled flight never triggered this condition making it difficult to discover. I solved the issue by re-flashing the ESCs with blheli firmware.
Is anyone else experiencing this issue? The auto takeoff is underpowered and then the quad tips over. The quad flies fine under manual control in stabilize.
Log file from a second vehicle. I should note that I've been flying successful missions with these vehicles for a few months.
15-04-02_13-18-24.bin