Crazyflie 2.0 I2C FAILURE

[tobias]

@karan259 I think your issue was solved over email right?

[qba]

So what was the solution? My error log looks pretty much the same.

[tobias]

Sent you a PM @qba.

[ajlitt]

Just unboxed mine, and all of the IMU bus sensors fail. No shorts at the pullups, but IMU_SCL is stuck low.

cfclient log:

Code: Select all

SYS: ----------------------------
SYS: Crazyflie is up and running!
SYS: Build 164:0dbbb77772a9 (production1.1) CLEAN
SYS: I am 0x31323832313347032C002D and I have 1024KB of flash!
I2CDEV: Error callback nr: 1024
IMU: MPU9250 I2C connection [FAIL].
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 102430 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0

I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
IMU: AK8963 I2C connection [FAIL].
I2CDEV: Error callback nr: 1024
IMU: LPS25H I2C connection [FAIL].
EXPBRD: Found 0 memories.
EEPROM: I2C connection [OK].
OW: Found 0.
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0
30 78 42 43 0 50 2 0 0 0 0 0 0 0 0 7F 
Status 0

Edit: nevermind, read the rest of the related threads, reflowed the MPU9250, and all is well.

[shakee93]

I bought a crazyflie few months back. My crazyflie is failing the self test repeatedly. I checked the log and it shows a similar error. Im really upset about it as i couldnt fly it even once properly after buying it. Please help me

[tobias]

Sent you a PM @shakee93

[lorenz]

It seems like I'm facing the same or a similar problem and I have no idea how to solve it.

After a short time of flying, my Crazyflie 2.0 goes crazy. The reason seems to be an IMU problem. The artificial horizon drifts away and after disconnecting and connecting I don't see any IMU data at all anymore. After turning the crazyflie off and waiting a while to let it cool down, I start getting IMU data again, so I assume this is also the mentioned bad soldering problem.

Here the log:

SYS: ----------------------------
SYS: Crazyflie is up and running!
4.12.1) CLEAN
SYS: I am 0x31343835313347023D0030 and I have 1024KB of flash!
IMU: MPU9250 I2C connection [OK].
IMU: AK8963 I2C connection [OK].
IMU: LPS25H I2C connection [OK].
EXPBRD: Found 0 memories.
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
LPS25H: Self test [OK].
OW: Found 0.
SYS: Free heap: 6048 bytes
30 78 42 43 0 50 0 0 0 0 0 0 0 0 0 7D
Status 0
4
I2CDEV: Error callback nr: 1024

[tobias]

sent you a PM @lorenz

[krobro]

I purchased two Crazyflie 2.0s from Diigiit Robotics here in Canada a few weeks ago. In one unit, I have the same "spinning out of control" behaviour and I2C error appearing in the logs. (The second unit has yet to be opened and tested by a colleague I purchased it for ... fingers crossed.)

After a lot of troubleshooting I eventually found this thread. Where do I go from here? Please help.

Code: Select all

SYS: ----------------------------
SYS: Crazyflie is up and running!
SYS: Build 39+:f6637ad54fe5 (2014.12.1) CLEAN
SYS: I am 0x31343835313347012A0039 and I have 1024KB of flash!
IMU: MPU9250 I2C connection [OK].
IMU: AK8963 I2C connection [OK].
IMU: LPS25H I2C connection [OK].
EXPBRD: Found 0 memories.
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
LPS25H: Self test [OK].
OW: Found 0.
SYS: Free heap: 6048 bytes
30 78 42 43 1 2 2 0 0 0 0 0 0 0 0 E7 
Status 0
E7 E7 E7 E7 B5 
Status 0
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 102I2CDEV: Error callback nr: 1024
4
4
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024

[krobro]

Can someone from Bitcraze please reply?