Self test acc X [FAIL]

[ion]

Hello all,

Just as the topic states, I have a unique issue I have tried to search for but only find (Self test acc Y) replies.


Since my last thread (Battery mod) my crazyflie has been operating normally up until today.

I haven't crashed it too hard, or got it wet, but it seems when try to fly it, forward pitch will make it go left or right.

The board does not appear to be damaged or scuffed in any way, but I cannot get it to fly in any direction besides left or right (whichever it decides to use).

My bootlog is here:

SYS: Crazyflie is up and running!
SYS: Build 89:54fa51cb6ea0 (2014.01.0) CLEAN
SYS: I am 0x8721571956497850676FF48 and I have 128KB of flasIMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
14.01.0) CLEAN
SYS: I am 0x8721571956497850676FF48 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
SYS: Crazyflie is up and running!
SYS: Build 89:54fa51cb6ea0 (2014.01.0) CLEAN
SYS: I am 0x8721571956497850676FF48 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
14.01.0) CLEAN
SYS: I am 0x8721571956497850676FF48 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OKMPU6050: Self test acc X [FAIL]. low: 0.30, high: 0.95, measured: 0.24
14.01.0) CLEAN
SYS: I am 0x8721571956497850676FF48 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].

Do note: I tried to restarted it a few times prior, but this is the first time seeing this.
I do not have the proper soldering skills to replace any components on the board, sadly

[tobias]

Failed self tests can happen when the board is moved to much during calibration as well so it might be that. How does the artificial horizon respond in the cfclient when you move the Crazyflie around?

[ion]

Failed self tests can happen when the board is moved to much during calibration as well so it might be that. How does the artificial horizon respond in the cfclient when you move the Crazyflie around?

Both X/Y respond what looks like to be normal. I noticed it does not actually start sending the data until I set it on a flat, non-moving surface.

But I've tried to remap the controller countless times thinking it has to do with the Roll/Pitch.

It keeps doing the same thing and I haven't changed the calibration for weeks after I got it.

It just likes to fly right or left, and does not go forward or backward.

[ion]

Also I must note my crazyflie does not stay on, for some reason. Sometimes I have to hold the power button down, but it will still shut off (This started today).


I left it charging for 2 hours today. It just shuts off now after I tried to fly it today once.

[ion]

I've pinpointed what seems to be one of the 2 problems.

It seems when it gets any vibration or if I set it down on the desk (without being extremely careful), it will shut off.

But if I leave it plugged into USB, it does not do this.

However I still cannot make it stay on long enough to get it to hover anymore

[tobias]

Hmm, tricky problem. My first guess is a glitch somewhere in the battery power path or on/off logic. Can you try to investigate if there is a glitch in the battery cables or in the push button?

[ion]

Hmm, tricky problem. My first guess is a glitch somewhere in the battery power path or on/off logic. Can you try to investigate if there is a glitch in the battery cables or in the push button?

I've fixed the shut-off issue.

This was an adventure. I thought when I replaced my battery, the charging circuit on the battery itself would be fine.

Turns out putting my multimeter on the output pads to the copter were sketchy unless I tried to bend the pcb. The battery itself has a nice voltage of 4~v.

I found an old bluetooth keyboard - well I'll spare the details. The battery is too long but it still flies (minus the sideways problem this thread is about.






Problem 1 out of 2 fixed - but the hovering problem still exists and I'm not sure why it just started doing this one day...

Are there any tests I can run while flying?

[chad]

but the hovering problem still exists and I'm not sure why it just started doing this one day...

Just an observation... I don't think that copper wire on top of the radio antenna is helping matters.

[tobias]

I'm thinking you have created a balance problem and that is why it doesn't respond. Since the battery is pretty long it will load that axis with more weight as well as disturbing the air flow. Therefor this axis will become unresponsive. You need a smaller more square battery. I like your creativity though

[ion]

As a reply to both of you, the balance issue started long before I replaced the battery with this long one you see above.

The copper wire isn't always on and was a test to see if I could get the battery to stay in position.

Hoewever, as a strange stroke of luck, that fixed my shut-off issues and it flies nearly the same as when it did when I got it - besides a sideways drift when I take off.

I could find something else to take apart and salvage another battery, but I use all the other things that have one!

The last battery mod: http://forum.bitcraze.se/viewtopic.php?f=6&t=1091

This is a very tricky issue and it seems the more I mess with it, things change for better or worse.

I've never had it fly to well though (since I've gotten it) - but the new battery, sadly IS too long.