Bitcraze Forums

After powering the CF on and trying to connect to client nothing happens unless I shake my crazyflie. Only then I start seeing some feedback in the client. Then the horizon looks all wrong (of course) and the CF is very hard to control. What could the reason for this be? I assembled my CF yesterday evening and wanted to start flying it tonight.

My setup: Xbox360 wireless controller on osx 10.8. I've flashed the CF firmware to the latest and here's the log from the console (client):

SYS: Crazyflie is up and running!
SYS: Build 31:ba1d111112ad (2013.4) CLEAN
SYS: I am 0x8711415054568549672FF50 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].

I get some other errors in the terminal from the client:
NFO:cflib.crazyflie.log:Have successfully logging for block=9
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [2]
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [2]
(..)
WARNING:cflib.crazyflie.log:Error when adding blockId=14, should tell listenders...
WARNING:cflib.crazyflie.log:Error when adding blockId=15, should tell listenders...
INFO:cflib.crazyflie.log:Have successfully logging for block=10
INFO:cflib.crazyflie.log:Have successfully logging for block=11
INFO:cflib.crazyflie.log:Have successfully logging for block=12
INFO:cflib.crazyflie.log:Have successfully logging for block=13

Hi,

Do you shake the Crazyflie directly after powering it on? If so then that explains the strange behavior.

If you just place it on a stable surface, power it on and press the Connect button in the UI do you find any URIs except for debug://0/0?

Shaking indicates an defective contact somewhere.. or your Accelerometer is very noisy.. or you having heavy interfearence with a wifi.

I would try:

1: Dont shake it after conect
2: You could try using this firmware from DesTinY to check your accelerometer and propellers
3: Try setting the bandwith to 1Mbit and choose another channel