Bitcraze Forums

Hello...again
i have one crazyflie drone that has a strange issue: it starts regularly but the red led that should blink each second after the calibration, actually blinks each 2 seconds. As it can't initialize properly.
Within the client i can connect with the crazyradio PA but i can't see any output on the flight data. So the sensors seem not work properly.
I flashed it with the updated firmware...but nothing.

Do you think it is an hardware problem?
Gianni

Hi,

It could be. What is the text displayed in the console when connecting the the Crazyflie. You can see the console by opening the tab with view/tabs/Console.

arnaud wrote: ↑Mon Oct 09, 2017 11:27 am Hi,

It could be. What is the text displayed in the console when connecting the the Crazyflie. You can see the console by opening the tab with view/tabs/Console.

Thanks Arnaud! I'll check later and I'll post the message of the console.
Bye
Gianni

I have the exact same problem with my crazyflie 2. I've checked the console message and it says:

---
SYS: Crazyflie 2.0 is up and running!
SYS: Build 0:7b0041f2edb7 (2019.01) CLEAN
SYS: I am 0x343834383033470800310038 and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 16 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
CONTROLLER: Using controller 1
EEPROM: I2C connection [OK].
MPU6500: Self test acc Z [FAIL]. low: -14.0, high: 14.0, measured: 24.06
MPU6500: Self test acc Z [FAIL]. low: -14.0, high: 14.0, measured: 40.24
AK8963: Self test [OK].
SYS: Free heap: 16056 bytes

I see that the MPU6500 self-test for acc Z fails. After a couple of minutes, I decided to make the test again and the console message changed for the following:

SYS: ----------------------------
SYS: Crazyflie 2.0 is up and running!
SYS: Build 0:7b0041f2edb7 (2019.01) CLEAN
SYS: I am 0x343834383033470800310038 and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 16 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
CONTROLLER: Using controller 1
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
SYS: Free heap: 16056 bytes

And the LED M1 is still blinking once every 2 secs, indicating sensor calibration fail. What should I do now?

If you start the CF2 on a stable surface do you ever get the MPU6500 error?

I'm always using a stable surface for testing. The first test (the one with the MPU6500 error) happened only once. The remaining tests gave results similar to this second test I've shown. The fact is that, independently of what is printed on the console, the LED M1 keeps blinking once every two seconds and there is no response from the motors neither the sensors in the cfclient.

I have this crazyflie for a while now, and it has flown before, but I always had to reset it a couple of times so that the calibration could work, and now I keep resetting it on a stable surface and nothing!
Do you think it is a hardware problem or there are more tests I can do to figure out what is happening?

It then sounds like a HW problem with the sensor. Please send an email to support (at) bitcraze.io and we will help you out.