Crazyflie 2 board fails POST out of box.

[mayhemer]

Hi, here's another one with the same problem, bought CF2 from Seeed a week ago. Started to manifest after some time (few smaller crashes.)

I'd like to ask if there is one of the following options available:
- either send it for repair to you (I'm located in central Europe) rather than to Seeed located in China
- or expose a video on how exactly to fix the problem myself (which chip and how), since I may have access to a hot air rework station (I have soldering experience, but no SMD/hot air experience)

Thanks.

[tobias]

@mayhemer
I've sent you a PM.

[GeEom]

I have just got my board back from seed repaired.
I'm not in the air yet but things seem to be working!

Obviously this has mitigated my initial excitement somewhat. If I hadn't bought on ~launch day, or from a more established institution, I'd have demanded a refund and reordered. This probably would have cut into the three month wait a bit.

[qubitter]

I also have this issue except mine only says it once rather than 20 times. Please help!

I am using the CF 2 for a school project. I need this!

Thanks!!

[tobias]

qubitter I sent you a PM.

[muxa]

Hi guys!

I bought crazyflie 2.0 recently, it's arrived last Monday. Everything was perfectly fine, it worked like a charm. However, one day it hasn't passed self-test (bloody red led fast blinking). The issue disappeared itself after a while. It appeared again, though, after couple of flights. I cheked it for any noticeable damage, and found nothing. After being reassembled it worked again for couple of minutes, but this bloody red led started blinking fast again after rebooting.

Log:

Code: Select all

ng!
SYS: Build 0:29624e7f6e3b (2014.12.1) CLEAN
SYS: I am 0x31343835313347012C003E 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 1 memories.
EXPBRD: Info board 0:
 -Header:EB
 -Pins  :0xA000
 -Vid   :BC
 -Pid   :2
 -crc   :9D
EEPROM: I2C connection [OK].
OW: Found 1.
OW: Serial 0xD B9 DF 8 0 0 0 84.
EB 0 A0 0 0 BC 2 9D 0 9 1 
Status 0
0 9 1 4 62 63 51 69 2 1 42 C6 
Status 0
30 78 42 43 0 50 0 0 0 0 0 0 0 0 0 7D 
Status 0
EB 0 A0 0 0 BC 2 9D 0 9 1 
Status 0
EB 0 A0 0 0 BC 2 9D 0 9 1 
Status 0
0 9 1 4 62 63 51 69 2 1 42 C6 
Status 0
0 9 1 4 62 63 51 69 2 1 42 C6 
Status 0
30 78 42 43 0 50 0 0 0 0 0 0 0 0 0 7D 
Status 0
EB 0 A0 0 0 BC 2 9D 0 9 1 
Status 0
EB 0 A0 0 0 BC 2 9D 0 9 1 
Status 0
0 9 1 4 62 63 51 69 2 1 42 C6 
Status 0
0 9 1 4 62 63 51 69 2 1 42 C6 
Status 0

What should I do? Can I count on some sort of refund, or board replacement, or whatever?

Cheers!

UPDATE: (I cleared out previous updates, since they are redundant)

Tapping from the top (basically, tapping the battery) solves the problem of self-test fail. It works ok as a temporary solution, but it's not good. Even worse: something happens to the sensors at flight, and CF makes some weird flip (or just rushes to a weird direction) and of course crashes. Self-test is failed then after reboot. My suggestion is that something happens to the sensors during flight so CF cannot stabilize and becomes irresponsive. Bad news: it happens more and more often.

My recent investigations shown that sensors goes crazy after any vibrations: either landing or vibration of motors. When I launch it, I have 10-15 seconds of stable flight, then sensors are stuck, CF crashes. Self-test is not passed after reboot (log is the same as I posted). Same weird behaviour was at the very first flight: I had to reboot the drone every time it has been landed, otherwise it wasn't stable. Now it becomes more and more annoying.

[tobias]

@muxa I sent you a PM

[mattbinarys]

Hi!

Like other people on this form I am getting the 5 blinking error lights and the following console readout once I connect my crazyflie 2.0

SYS: Build 164:0dbbb77772a9 (production1.1) CLEAN
SYS: I am 0x313238323133470128002E 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 64 2 0 0 0 0 0 0 0 0 93
Status 0
30 78 42 43 0 64 2 0 0 0 0 0 0 0 0 93
Status 0

I am using this for a school project and REALLY need it to work. Can someone please help me?

[Tirebiter]

Hi guys,
Nice job on the 2.0. Perfect quad for the indoor winter season fling. My new quad is having erratic problems also. If I land hard it wants to flip over on subsequent takeoffs. I cycle the battery to fix but I think I have a solder issue also. I am going to look into a hot air soldering station. You guys rock. I will continue to fly until it gets to bad to continue.
Thanks,
Steve
Can I get a PM to show which chip and any safety procedures while soldering. Contacted Seeed Studio but they are closed celebrating their new year.

[moejetz]

Hi all,

I have a similar problem with my CF2.0.
70-80% when I turn it on, the self-test fails.
When it passes, most of the time I can fly for only 1-2 seconds before it flips and crashes. In this case the log looks like this:

Code: Select all

IMU: LPS25H I2C connection [OK].
DECK_DRIVERS: Found 4 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
LPS25H: Self test [OK].
SYS: Free heap: 3048 bytes
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 1024
I2CDEV: Error callback nr: 512

(the last three lines are added at the moment the CF flips).

When the self-test fails, the log looks like this:

Code: Select all

h!
CFGBLK: v1, verification [OK]
IMU: MPU9250 I2C connection [OK].
IMU: AK8963 I2C connection [OK].
I2CDEV: Error callback nr: 1024
IMU: LPS25H I2C connection [FAIL].
DECK_DRIVERS: Found 4 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
EEPROM: I2C connection [OK].
AK8963: Self test [OK].

What can I do about that? I see it's most likely a soldering issue, but I'm not very talented at soldering so I can't fix it by myself (and I don't want to lose my warranty).
Also, does this interfere with the expansion connectors? I realized that from the very first moment on the pin headers loose friction very fast so that the battery gets loose. But what worries me most is that a few times the male expansion connectors even lost friction on the (female expansion connectors of the) CF board, not only on the battery holder board. Maybe this is related to the I2C errors that appear?

Any help would be appreciated!
Thanks a lot in advance,
Moe