I know I'm not the first person to complain of this, but I've been scouring the forums trying to find answer, and none have pointed to a solution that worked for me. I have a beefy octocopter in an X8 configuration using a Pixhawk and APM firmware 3.3.3. I've been flying in stabilize mode, and whenever I give it a hard yaw left the drone pitches back (nose up) and rolls to the right. Yawing hard to the right does not appear to cause a problem. The same pitching back & up happens when I throttle up very hard as well.
I've tried to address all the possible culprits that other forums have suggested:
The copter is definitely not lacking in power. It appears to hover around 30% throttle, which I know is a little low. Can that cause issues like this?
Here's a link to a log file (sorry 15mb was too big to attach directly to the post, so here it is in Google drive) from a short flight where I intentionally gave several hard yaw and throttle commands that exhibited the behavior. I tried to analyze the log myself, but I'm no good at this stuff. Maybe someone can help me uncover what's going on?
Seeing you log - I think you can try to reduce vibrations, they are awful - be happy it flies at all :)
Interesting. The Pixhawk is on a layer of vibration dampening foam. I'm going to do some propeller balancing and see if it gets better. Can you tell me which log values you examined to find the vibrations?
Actually I just learned about the VIBE set of values in the logs. According to those I think my x and y vibrations are OK, but the z one is a little high. I've seen a copter suffer from high vibrations before and this definitely wasn't exhibiting the jumpy behavior you get from that. It sounds like vibration issues like this have a greater effect when it's trying to do inertial navigation, but it's not doing that in stabilize mode.
So I wanted to see if perhaps the copter is way too powerful for it's own good, so I found a big LiPo lying around strapped it on just for added weight. I didn't even do a good job centering it. It now hovers around 40% throttle. The heavy pitch/roll from hard throttle didn't go away, but the wobble from a hard yaw, though still there, is much less pronounced. I can now apply a full-power yaw left indefinitely and it will drift from where it's hovering, but it doesn't lose control. This is great news because I was planning on getting a MUCH bigger battery (wanna go from 8,000 mah -> 20,000 mah).
@Lee, per your question: I'm using these motors (700kv), these props (12x4.5) for the top motors and these props (11x4.7) for the bottom ones. These are huge motors and props for such a tiny frame (picture below), and I'm wondering now if the extreme power means that any small imbalances in power show immediately with something that has such a small moment of inertia. I think the solution may just be to add more weight to the frame (through batteries, probably) and set limits on the maximum acceleration in ascent rate.
Frame should handle it ok. This is the same frame with bigger props (15") and motors (380kv) and it flies well. Weighs in at 6.2lbs
Regarding vibrations, I'd check your wiring to see if its vibrating against other wires or the flight controller. If that is ok, check your motor bell housings. I had motors that were sloppy up and down that was causing high z axis vibrations.
Right. I was referring to the fact that motors are so close together, and that there's 8 of them, which is a lot of power. I'm wondering if I wouldn't see these issues if I got larger arms, like you do, and spread the motors apart. Thoughts?
Could you provide the .bin log. The one you provided doesn't have all the parameters in it. If you could also send your .param file after exporting your parameters that would be great.
It looks like your motors are slightly off in angle but not too bad.
I suspect this is largely a tuning issue. I can't see your parameters but I suspect you have not run autotune and are running without input conditioning turned on.
Its possible but it seems more like a parameter or PID value. Can't remember the exact parameter name, something like yaw_filt_hz but it was on 5 on mine and should have been 20. Checked my other MR's running pixhawks and they too had it on 5, and yaw worked much better on 20
I would put longer arms on yours just for getting the props out past the body. Looks like you're losing some thrust as the prop overlaps the frame
The yaw filter is normally in the range of 2.5 to 5 Hz for a good tune. A well executed autotune will sort this out.
I noticed improved yaw performance going to 20hz