It looks like your midpoints are off too far. Take off the props and enable the ESC's. Arm the copter and push the the throttle up until the motors spin... Now watch the four motor levels in the gui, I suspect two of them will spin up higher by themselves and continue to accelerate without you touching the throttle.
Mine did that until I correctly trimmed my TX, if you cannot edit your transmitters subtrim you'll have to edit in the gui itself.
Anyway, Tphilips96, you can use the trim switches instead just to check... if you don't have arming issues, great! Otherwise, you might need to set MIDRC... also, make sure those trim switches are in the middle... there's a chance you moved them just so you can arm it... but that'll cause you the mid-point problems.
You'll have to edit the config.h file in the Arduino IDE and reflash the firmware. Before doing that, you might want to check to see if in fact your trim switches are centered. I'm not familiar with that TX, but on most with digital trim switches (which is what that looks like), you need to push them up / down until you hear a unique tone that's not going up nor down in pitch.
The link I sent earlier has details on MIDRC, and based on your pictures, I would probably set it to 1483 or so... whatever value works to get that UI display to show 1500 on roll, pitch, yaw with neutral sticks.
Doing a static, full throttle test with no props on will give you different results depending on how you've placed your quad. If you look at your roll and pitch indicators, they aren't fully level, so the board will try to compensate by giving different thrust... in this case, it almost looks like it's trying to yaw. I don't know, but I don't think that's a very good test.
The MIDRC wouldn't affect throttle, or at least make any difference. It only makes a difference for the roll, pitch and yaw channels because the flight controller has to know what "neutral" is -- or middle for those channels. If it sees anything other than 1500, it thinks you're trying to input roll, pitch, yaw, or all of the above... which is actually what I think that graphic shows. Not only is the quad not level, but you're sending command input of about 1485 to roll, pitch, and yaw... so that would kind of explain why those motors are being commanded with different levels.
A quick test might be to use those trim buttons to try to get your midrc points to 1500, then see if it does the same thing in the gui when you throttle up.
Your roll, pitch, and yaw midpoints are VERY far off the 1500 midpoint. I think you'll need to adjust MIDRC in your config.h if you can't adjust your TX subtrims:
http://www.multiwii.com/wiki/index.p..._configuration
Assuming your TX trims are already in the middle/centered, then the right value might be 1484 or so...
Is the motor you moved spinning in the correct direction? You didn't mention double checking motor direction.
Does the motor itself spin freely?
Even with a weak motor, I would think the flight controller could compensate unless the motor doesn't spin at all.
I would do the test where you remove props, run up throttle to about half, and dip each arm down, bring to level and repeat a few times. It should speed up that motor that is lowest the most. Verify that on the gui.
Quote Originally Posted by makattack View Post
I would do the test where you remove props, run up throttle to about half, and dip each arm down, bring to level and repeat a few times. It should speed up that motor that is lowest the most. Verify that on the gui.
Have you tried erasing the EEPROM and reflashing the software?
Another thing... the motors don't seem to behave as I would expect. Have you tried erasing the EEPROM and reflashing the software?
No I have not tried erasing the EEPROM. How is this done?