I'm considering buying a Droidworx AD-8 HL for AP/AV use and would like to fly a Canon DSLR with it. I'm looking at the 5D mkII or 7D. I'm wondering who here has a similar setup and any opinions or recommendations on which camera is more suitable. Also, what lenses work best for such an application.

Originally Posted by crazyj

To you have an ACCL or NK attached? I think the software is dependent on those sensors for cam stab.

Cheers,
CJ

Opps! forgot to put that in there. I am using the 6DOF Freeflight IMU. The ACC is on when the gear switch is high

I feel kinda sheepish

I just saw that I forgot to check the camera stab check boxes in the Multiconfig

Thanks aways lol

Originally Posted by hamburger

so theory stands corrected, for the moment.
What brand of ESCs do you use here, please?

They're Hobbywing Volcanos, 30amp.

Brand new batteries, servo, and ESC's, too.

Pretty weird!

So I was just floating around my flying area and... I fell out of the sky.

Turns out my front right motor disassembled itself while in flight! Haven't completed rebuilding it yet, but it seems that I may only have to replace one motor and maybe a speed controller.

The MWC took a hard hit; landed right on my board mounting frame. It bent several header pins and such, and mangled the FTDI pins on the arduino, but after some careful work with some needle-nose pliers, the board still works fine!

I do have one motor that's twitching though.. the other 3 power up but this one seems to have a timing fight... never turns fully, just jerks. I haven't had a chance to start diagnosing it yet, but does anyone have any guesses about what's causing that? It isn't the esc/motor that fell apart, it's on the opposite end. No visible damage to the ESC either, but I do need to inspect it more closely, likely tomorrow evening.

spag

Motor Falling Apart in Flight (0 min 40 sec)

Originally Posted by spagoziak

I do have one motor that's twitching though.. the other 3 power up but this one seems to have a timing fight... never turns fully, just jerks. I haven't had a chance to start diagnosing it yet, but does anyone have any guesses about what's causing that?...

Sorry to see the crash.

Had a motor that would work sometimes and jerk other times. Turned out to be one of the three motor wires had broken loose inside the motor near where they come together in the shrink wrap.

Originally Posted by BlueAngel2000

Here is a video of my new Mini Wii Copter:
http://vimeo.com/24628161

WiiM+ Clone with ITG3205 (direct chip mod)
Arduino Pro Mini 328

250mm

4x Turnigy 2211 2300kv
4x Plush 10A
FrSky V8R4
4x 5x3 3-Blade left and right rotating

300g with 3s1p 610mAh

works very good.
thanks again for your great work Alex.

hi blue angel
sorry for the stupid question but 250mm is the distance between the motors?

Originally Posted by Alexinparis

Hi Mariano,
No, it's not normal. I rewrote some parts of sensor code, but the orientation should still be the same.
What about the other axis ?

I all,
May be it' lost "acc_1G = 200;" after acc init. I had the same problem when enabled NUNCHACK (acc Nunchuk stand alone).
Please alex confirm this is the problem.

Bye, Carlo

Originally Posted by carlonb

I all,
May be it' lost "acc_1G = 200;" after acc init. I had the same problem when enabled NUNCHACK (acc Nunchuk stand alone).
Please alex confirm this is the problem.

Bye, Carlo

Hi,
you're right about the standalone Nunchuck. acc_1G was lost.

But for BMA020:


old code:

#if defined(BMA020)
static uint8_t rawADC_BMA020[6];

void i2c_ACC_init(){
byte control;

i2c_rep_start(0x70); // I2C write direction
i2c_write(0x15); //
i2c_write(0x80); // Write B10000000 at 0x15 init BMA020

i2c_rep_start(0x70); //
i2c_write(0x14); //
i2c_write(0x71); //
i2c_rep_start(0x71); //
control = i2c_readNak();

control = control >> 5; //ensure the value of three fist bits of reg 0x14 see BMA020 documentation page 9
control = control << 2;
control = control | 0x00; //Range 2G 00
control = control << 3;
control = control | 0x00; //Bandwidth 25 Hz 000

i2c_rep_start(0x70); // I2C write direction
i2c_write(0x14); // Start multiple read at reg 0x32 ADX
i2c_write(control);

acc_1G = 240;
acc_25deg = 101; // = acc_1G * sin(25 deg)
accPresent = 1;
}

void i2c_ACC_getADC(){
TWBR = ((16000000L / 400000L) - 16) / 2;
i2c_rep_start(0x70); // I2C write direction
i2c_write(0x02); // Start multiple read at reg 0x32 ADX
i2c_write(0x71);
i2c_rep_start(0x71); //I2C read direction => 1
for(uint8_t i = 0; i < 5; i++) {
rawADC_BMA020[i]=i2c_readAck();}
rawADC_BMA020[5]= i2c_readNak();

accADC[ROLL] = (((rawADC_BMA020[1])<<8) | ((rawADC_BMA020[0]>>1)<<1))/64;
accADC[PITCH] = (((rawADC_BMA020[3])<<8) | ((rawADC_BMA020[2]>>1)<<1))/64;
accADC[YAW] = -(((rawADC_BMA020[5])<<8) | ((rawADC_BMA020[4]>>1)<<1))/64;
}
#endif

#define ACC_ORIENTATION(X, Y, Z) {accADC[ROLL] = X; accADC[PITCH] = Y; accADC[YAW] = Z;}

...

#if defined(BMA020)
void ACC_init(){
byte control;
i2c_writeReg(0x70,0x15,0x80); // Write B10000000 at 0x15 init BMA020
i2c_writeReg(0x70,0x14,0x71);

i2c_rep_start(0x71);
control = i2c_readNak();

control = control >> 5; //ensure the value of three fist bits of reg 0x14 see BMA020 documentation page 9
control = control << 2;
control = control | 0x00; //Range 2G 00
control = control << 3;
control = control | 0x00; //Bandwidth 25 Hz 000

i2c_writeReg(0x70,0x14,control);

acc_1G = 240;
}

void ACC_getADC(){
TWBR = ((16000000L / 400000L) - 16) / 2;
i2c_getSixRawADC(0x70,0x02);

ACC_ORIENTATION( (((rawADC[1])<<8) | ((rawADC[0]>>1)<<1))/64 ,
(((rawADC[3])<<8) | ((rawADC[2]>>1)<<1))/64 ,
- (((rawADC[5])<<8) | ((rawADC[4]>>1)<<1))/64 );
ACC_Common();
}
#endif

accADC[YAW] should be the same for both and acc_1G is well defined in both cases.

Originally Posted by tsoumelman

hi blue angel
sorry for the stupid question but 250mm is the distance between the motors?

Hi,

Yes, 250mm between the motors.
so, its a ~10" frame.

Originally Posted by BlueAngel2000

Here is a video of my new Mini Wii Copter:
http://vimeo.com/24628161

WiiM+ Clone with ITG3205 (direct chip mod)
Arduino Pro Mini 328

250mm

4x Turnigy 2211 2300kv
4x Plush 10A
FrSky V8R4
4x 5x3 3-Blade left and right rotating

300g with 3s1p 610mAh

works very good.
thanks again for your great work Alex.

I like a lot this one. It's not frequent to see a quad acting as a racer

Originally Posted by Alexinparis

Hi,
you're right about the standalone Nunchuck. acc_1G was lost.

But for BMA020:


old code:




accADC[YAW] should be the same for both and acc_1G is well defined in both cases.

yes, i see the code is ok.

By now the only way to solve the problen is:
#define ACC_ORIENTATION(X, Y, Z) {accADC[ROLL] = X; accADC[PITCH] = Y; accADC[YAW] = - Z;}

But probably there is a bug in some place.

Can other BMA020 user confirm the problem?

Originally Posted by cwisbg

I have seen the spider hex design, has anyone come up with a quad version?

Not flyduquad, i meant spiderquad

Hi,

I´m in progress to finish my spider(with 4 legs:-)) quad.

I thougt the design would be a good ideo concerning the FOV when using cameras and Fpv.
Will post some more pictures and information when it´s finished

regards

Originally Posted by mgros

yes, i see the code is ok.

By now the only way to solve the problen is:
#define ACC_ORIENTATION(X, Y, Z) {accADC[ROLL] = X; accADC[PITCH] = Y; accADC[YAW] = - Z;}

But probably there is a bug in some place.

Can other BMA020 user confirm the problem?

Ok, my fault, I forgot to change a sign in the BMA020 part dur to new ACC calibration code.
I did it well for BMA180 but not for others.
I will update a new dev.

should be corrected here:

  ACC_ORIENTATION(  (((rawADC[1])<<8) | ((rawADC[0]>>1)<<1))/64 ,
                    (((rawADC[3])<<8) | ((rawADC[2]>>1)<<1))/64 ,
                    (((rawADC[5])<<8) | ((rawADC[4]>>1)<<1))/64 );

Originally Posted by Alexinparis

Ok, my fault, I forgot to change a sign in the BMA020 part dur to new ACC calibration code.
I did it well for BMA180 but not for others.
I will update a new dev.

should be corrected here:

  ACC_ORIENTATION(  (((rawADC[1])<<8) | ((rawADC[0]>>1)<<1))/64 ,
                    (((rawADC[3])<<8) | ((rawADC[2]>>1)<<1))/64 ,
                    (((rawADC[5])<<8) | ((rawADC[4]>>1)<<1))/64 );

Many thanks Alex!
Merci beaucoup.