Thanks for your reply, spag. I did what you said. So basically, if i roll the quad to the left, the front right and rear right motors will decrease while the opposite motors will increase and vice versa, right? That is showing in the GUI.
One thing I noticed, the throttle of the rear left motor is lower than the rest. Is that normal?

Any changes that I could make to the code? I am a noob at changes in the code...

Thanks for your reply, spag. I did what you said. So basically, if i roll the quad to the left, the front right and rear right motors will decrease while the opposite motors will increase and vice versa, right? That is showing in the GUI.
One thing I noticed, the throttle of the rear left motor is lower than the rest. Is that normal?

Any changes that I could make to the code? I am a noob at changes in the code...

Yes, I've reverse the yaw to-1 in the code. Is it normal that the arm/ disarm changes every now and then. Awhile ago, I armed and disarmed the motors using the throttle stick. Now I do the same actions using the roll stick. How could that be?

Can anyone send me an original or working 1.7 sketch for Quadx? I think I messed my sketch real bad with my noobness, LOL.

Yes, I've reverse the yaw to-1 in the code. Is it normal that the arm/ disarm changes every now and then. Awhile ago, I armed and disarmed the motors using the throttle stick. Now I do the same actions using the roll stick. How could that be?

Can anyone send me an original or working 1.7 sketch for Quadx? I think I messed my sketch real bad with my noobness, LOL.

Gent

The arm/disarm via roll is normal too! That was added so that folks with tricopters would stop stuffing their rear props into the dirt.

I'd be happy to send you my working quadx--I've got it right here. PM me your email (to avoid the bots)!

OSD should detect 115200 MWC baudrate .
After motors are armed will made Save_Home function and type "MWC ARMED" - this message is generated by MWC , is possible to generate any message on OSD .
Also will start to show AH .

I tested it on terminal - but if anyone have OSD and want to play - please refer progress.

I taked time frame from ISR of servos added AH_flag++ variable , so if AH_flag is bigger than AH_Freq - so serial print of data begin and AH_Freq is reset . That is possible control data frequency update .

Sadly, I couldn't get the MWC to do *anything* with this... just a blinking green light, maybe lit every .5 seconds then off for .5. The config wouldn't pick it up and the OSD didn't show signs of seeing it either.

My pitch gimbal for stabilization didn't respond to tipping, either, so I suppose I did something wrong in the code? It compiled ok though...

You did a nice hack which cheap things
As you wrote, one I2C function assumes a simultaneous STOP and START order. It avoids some bits on the I2C bus, but there are few situations where devices are not happy with this.
I will add an option to separate th 2 orders, which would be more in line with the expected I2C standard.

Thanks, Alex!
Yes, I realized it's somewhere in those shortcuts to save some bus cycles that didn't work with the clone, but I also didn't want to switch to that huge standard Wire library because your code is much more effective and simple, so I just plugged in that version from Peter Fleury that made my Nunchuk clone happier.

Existing init code for BMA180 is changing offset X trimming lsb bits offset_x<3:0> (register 0x35) that are calibrated at production line with those lines (so I removed that range set to 3g completely, because default range +/-2g should work just fine):

I also changed the accADC calculation which was... uhmm... a bit incorrect on negative values.
Raw data 4096 @ 1g (0.25 mg/LSB), it is 14 bit value (13:6 | 5:0) but located in bits 15:2, so we need to divide it /4 (not shift it >>2 because it is a signed int value in 2's complement format). Also with default range +/-2g we need to divide it /20 to get value ~200 (to match other sensors) - total divisor is /4/20 = /80

I think you said you are running Windows 7 64 bit version. By chance did you install Java 64 bit runtime? If so that could be the issue. I found that the MultiWiiConfig only ran under the x86 32 bit version of java.

No, no. I'm using win XP 32 with service pack 3. the problem is that it takes about 20 minutes to open the multiwii conf..

Hello all
I am still learning to fly my quad...
But the orientation of a tri seems more easy to me still learning.
What is the smallest tri multiwii you know?
And it would be cool to fly inside house. Maybe something with the size of a tx...
What do you guys think?