Crazyflie 2.0 I2C FAILURE

[Auriga_Nexus]

I'm getting a similar error:

Code: Select all

SYS: ----------------------------
SYS: Crazyflie is up and running!
SYS: Build 164:0dbbb77772a9 (production1.1) CLEAN
SYS: I am 0x3132383231334712230041 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: 1024
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 46 0 0 0 0 0 0 0 0 0 73 
Status 0
 0 0 73 
Status 0

With me, it worked fine when I first started it up (albeit some balance issues that could be contributed to pilot error). I ran it off the iOS app on my iPhone 5s, then switched to using Crazyradio/Windows Client (on Windows 7 64-bit), with a Logitech 3D Pro joystick for controls. Several times both with the app and joystick controllers, it would collide or end up upside down and would start blinking; i was able to fix by d/c'ing, power-cycling the quad, and r/c'ing. However, whatever happened the last time has caused it to do this every restart.

The only other thing I have noticed is that when it spins up during the POST, the M1 prop doesn't seem to spin as fast as the others. However I can find no damage to the connectors nor anything that might suggest the prop or engine are having issues.

My folks got me the CF2 for my birthday after I bricked the CF1 they got me for Christmas before I could even fly it (sodering accident destroyed the PCB), I'd rather not have to tell them this one's FUBAR too.

EDIT: Using the schematics and placement diagram I was able to locate the component MPU9250 (labeled U9 on the placement diagram). It's a small square chip, located on the top of the board, just inside the expansion board pin strip on the left-hand side - right next to a symbol that looks like it's supposed to point out where the axis directions are.

I have absolutely no bloody clue what that particular component does, but what I DO know is that after I put a small amount of pressure on that chip with my thumb, the CF2 started passing POST again.

So yeah, most likely there are components that are not soldered well on the CF2 (my folks ordered it from Seeedstudio so more than likely it's the same issue everyone else is having with them). For now I want to try and run some additional tests for the stability issues I'm having.

[codeman]

Using the schematics and placement diagram I was able to locate the component MPU9250 (labeled U9 on the placement diagram). It's a small square chip, located on the top of the board, just inside the expansion board pin strip on the left-hand side - right next to a symbol that looks like it's supposed to point out where the axis directions are.

@Auriga_Nexus
Are you talking about the black square chip which says something like 'X792D1 141S' on it?

I tried tapping it with the pencil eraser but doesn't seem to help.
Also, I'm seeing the following values in the client under the actual values:
Pitch: -59
Roll: 36
Yaw: 26
I tried resetting many times but it doesn't correct the gyros.

I don't want to tinker much with it and loose the warranty. I'm waiting to hear back from the support.

[tobias]

Both things sounds like the sensor soldering issue. I've sent you both a PM.

[codeman]

Both things sounds like the sensor soldering issue. I've sent you both a PM.

Thanks a lot Tobias!
I've replied back to your PM.
The message is stuck in my outbox!

[codeman]

I received a replacement board for my Crazyflie ten days back and I'm back on track.

Thanks a lot Tobias!

[grilly]

Hey guys,

I think I experience the same error (console output below). It used to work fine. After three weeks of holidays I wanted to pick up where I left off, then I got this failure. I'm using the latest stock client and firmware.

Code: Select all

SYS: ----------------------------
SYS: Crazyflie is up and running!
SYS: Build 36+:d8c3d8f6effc (2014.12.0) CLEAN
SYS: I am 0x31323832313347153B002B 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: 1024
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 1 50 0 0 0 0 0 0 0 0 0 E7 
Status 0
30 78 42 43 1 50 0 0 0 0 0 0 0 0 0 E7 
Status 0

Once again, I have access to a reflow station, but no advanced soldering skills. Rather than voiding warranty I'd like to hear your input.

P.S. Luckily our second CF2 just came back from a months-long China-Repair-Trip, let's see how that goes.

[saketroongta]

I am getting the same error in my concole when i try to fly it . please help me out.

[tobias]

I sent you a PM @grilly @saketroongta

[qba]

Similar issue here. Recently I've received package with copter and it was working fine for a couple first flights. Now its able to take off and goes crazy just after that. In log its also reporting I2C 1024 error and sometimes prints plain '4' (log attached below). I've also noticed that this is related to motor thrust and even if I hold copter on the ground and give it about 50% thrust error occurs.

Can I fix it somehow, or is it also soldering issue? I tried to update firmware to the latest one, but issue still exists:/

Code: Select all

SYS: ----------------------------
SYS: Crazyflie is up and running!
SYS: Build 32+:7b82012944a9 (2014.12.1) CLEAN
SYS: I am 0x31323832313347043C003B 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 50 1 0 0 0 0 0 0 0 0 E7 
Status 0
30 78 42 43 1 50 1 0 0 0 0 0 0 0 0 E7 
Status 0
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
4
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024

[karan259]

Hey,
I received the crazyflie 2.0 yesterday from Seeed and it worked good for a few hours after which what happens is that crazyflie runs fine for 30 seconds and then starts rotating erratically. The ASL in the PC client suddenly jumps to values from 20000 to 40000 and the orientation is also shown incorrectly on the screen. The debug menu shows this:

Code: Select all

Cfclient
Cfclient version: 2014.01.0
System: win32

Interface status
serial: None
radio: Crazyradio version 0.53
udp: None

Crazyflie
Connected: radio://0/80/250K
Firmware: 1ab92e55c44b (CLEAN)
Sensors found
HMC5883L: 1
MS5611: 1
Sensors tests
HMC5883L: 1
MPU6500: 1
MS5611: 1

When I start MPU6500 is there in sensors found but then it goes away.

The console shows I2C errors like this:

Code: Select all

SYS: Crazyflie is up and running!
SYS: Build 0:1ab92e55c44b (2014.12.0) CLEAN
SYS: I am 0x313438353133470327003F 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: 5712 bytes

4
I2CDEV: Error callback nr: 1024
4
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
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
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
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
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
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
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
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
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
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
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
4
I2CDEV: Error callback nr: 1024
4
4
I2CDEV: Error callback nr: 1024
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
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
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: 102I2CDEV: 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

I am not sure if it's a soldering problem or something else and I have tried flashing a new firmware and have also tried the client on a couple of systems.

Is there anything I can do to get the crazyflie to work.

-Karan