[SOLVED] Problem with the Crazyflie

[KOschi]

here we go with the output at my desktop computer:

Code: Select all

bitcraze@bitcraze-ubuntu:~$ cd ~/projects/crazyflie-pc-client/cfclient/
bitcraze@bitcraze-ubuntu:~/projects/crazyflie-pc-client/cfclient$ python cfclient.py
INFO:__main__:Disabling STL printouts
INFO:utils.input:Parsing [Generic_OS_X.json]
INFO:utils.input:Parsing [PS3_Mode_2.json]
INFO:utils.input:Parsing [PS3_Mode_1.json]
INFO:utils.logconfigreader:Parsing [battery.json]
INFO:utils.logconfigreader:Parsing [memlogtest.json]
INFO:utils.logconfigreader:Parsing [mem_and_toc.json]
INFO:utils.logconfigreader:Parsing [imu_gyro.json]
INFO:utils.logconfigreader:Parsing [imu_acc.json]
INFO:utils.logconfigreader:Parsing [stabalizer.json]
INFO:ui.tabs.FlightTab:Changed flightmode to Safe and Easy
Traceback (most recent call last):
  File "/home/bitcraze/projects/crazyflie-pc-client/cfclient/ui/tabs/ServiceTab.py", line 244, in initiateColdBoot
    if self.loader.coldBoot():
  File "../cflib/bootloader/cloader.py", line 149, in coldBoot
    if self.updateInfo():
  File "../cflib/bootloader/cloader.py", line 171, in updateInfo
    cpuid = struct.unpack("B"*12, pk.data[10:])
struct.error: unpack requires a string argument of length 12

seems pretty like the same output for me. I loaded the VM again from via torrent (so i haven´t used the same maschine like on my laptop).

[marcus]

It seems that the client you are using is too old and not compatible with the new bootloader that is in the Crazyflie.

Could you try to get the latest version and test it again? Just do the following in the VM:

Code: Select all

cd /home/bitcraze/projects
rm -Rf crazyflie-pc-client
hg clone https://bitbucket.org/bitcraze/crazyflie-pc-client
cd crazyflie-pc-client/bin
./cfclient

[KOschi]

With this updated Client i was able to flash the Firmware. Only the verify Flashing option wasn´t working.

BUT now the next thing went wrong. When i power on the Flie the Red LED flashes fast like 5 times (i am not able to count that fast ) then pauses for 2 seconds and flashes again like 5 times.
The Wiki tells me "Tests failed" but not how to resolve it. Also the M1 motor is not rotating during the Self Test, could it be broken and so cause the 5 flashes?

[marcus]

Good to hear that the firmware update is working. Could you post the console output from within the cfclient? It will print information about the self-tests.

[KOschi]

yeah offcourse:

here we go with the terminal output:

Code: Select all

bitcraze@bitcraze-ubuntu:~$ cd /home/bitcraze/projects/crazyflie-pc-client/bin/
bitcraze@bitcraze-ubuntu:~/projects/crazyflie-pc-client/bin$ cfclient
Info: Using config path:  /home/bitcraze/.local/cfclient
Info: sys.path= ['/usr/local', '/home/bitcraze/.local/cfclient', '/usr/local/bin', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages/PIL', '/usr/lib/python2.7/dist-packages/gst-0.10', '/usr/lib/python2.7/dist-packages/gtk-2.0', '/usr/lib/python2.7/dist-packages/ubuntu-sso-client']
INFO:cfclient.cfclient:Disabling STL printouts
INFO:cfclient.utils.config:Dist config read from /usr/local/cfclient/configs/config.json
INFO:cfclient.utils.config:Config file read from [/home/bitcraze/.local/cfclient/config.json]
INFO:cfclient.utils.config_manager:Parsing [xbox360_mode1_linux.json]
INFO:cfclient.utils.config_manager:Parsing [Generic_OS_X.json]
INFO:cfclient.utils.config_manager:Parsing [PS3_Mode_2.json]
INFO:cfclient.utils.config_manager:Parsing [PS3_Mode_1.json]
INFO:cfclient.utils.config_manager:Parsing [xbox360_mode1.json]
INFO:cfclient.utils.logconfigreader:Parsing [stabilizer.json]
INFO:cfclient.ui.tabs.FlightTab:Changed flightmode to Normal
INFO:cflib.crtp.radiodriver:v0.5 dongle with serial N/A found
INFO:cflib.crtp.radiodriver:v0.5 dongle with serial N/A found
INFO:cflib.crazyflie:Callback->Connection initialized[radio://0/10/250K]
INFO:cflib.crazyflie:We are connected[radio://0/10/250K], request connection setup
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
INFO:cflib.crazyflie:Callback->Connected to [radio://0/10/250K]
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
WARNING:cflib.crazyflie:Got link error callback [Dongle communication error (ackStatus==None)] in state [2]
INFO:cflib.crazyflie:Callback->Disconnected from [radio://0/10/250K]
INFO:cflib.crazyflie:Callback->Connectionl ost to [radio://0/10/250K]: Dongle communication error (ackStatus==None)
WARNING:cflib.crazyflie:Got link error callback [RadioDriver: Could not send packet to copter] in state [0]
WARNING:cflib.crazyflie:Got link error callback [RadioDriver: Could not send packet to copter] in state [0]
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
INFO:cflib.crtp.radiodriver:v0.5 dongle with serial N/A found
INFO:cflib.crazyflie:Callback->Connection initialized[radio://0/10/250K]
INFO:cflib.crazyflie:We are connected[radio://0/10/250K], request connection setup
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [5]
INFO:cflib.crazyflie:Callback->Connected to [radio://0/10/250K]
ERROR:cflib.crazyflie.toc:Got packet that was not on TOC channel, TOC fetch will probably not succeed
ERROR:cflib.crazyflie.toc:Got packet that was not on TOC channel, TOC fetch will probably not succeed
ERROR:cflib.crazyflie.toc:Got packet that was not on TOC channel, TOC fetch will probably not succeed
ERROR:cflib.crazyflie.toc:Got packet that was not on TOC channel, TOC fetch will probably not succeed
INFO:cflib.crazyflie.toc:TOC for port [5] found in cache
INFO:cflib.crazyflie:Log TOC finished updating
INFO:cflib.crazyflie.toc:TOC for port [5] found in cache
INFO:cflib.crazyflie:Log TOC finished updating
WARNING:cflib.crazyflie:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [2]
INFO:cflib.crazyflie.toc:TOC for port [2] found in cache
INFO:cflib.crazyflie:Param TOC finished updating
INFO:cflib.crazyflie:Callback->Connection setup finished [radio://0/10/250K]
INFO:cflib.crazyflie.toc:TOC for port [2] found in cache
INFO:cflib.crazyflie:Param TOC finished updating
INFO:cflib.crazyflie:Callback->Connection setup finished [radio://0/10/250K]
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ed50ec>
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ed510c>
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ed512c>
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: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: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: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: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: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: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: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: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: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: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: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: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]
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ed5d8c>
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ec9e2c>
<cfclient.ui.widgets.rtplotwidget.PlotDataSet instance at 0x8ed318c>
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: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: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: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: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: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: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: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: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: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: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:ExpectAnswer: ERROR! Older timer whas running while scheduling new one on [2]
WARNING:cflib.crazyflie.log:Error when adding blockId=9, should tell listenders...
WARNING:cflib.crazyflie.log:Error when adding blockId=10, should tell listenders...
INFO:cflib.crazyflie.log:Have successfully logging for block=1
INFO:cflib.crazyflie.log:Have successfully logging for block=2
INFO:cflib.crazyflie.log:Have successfully logging for block=3
INFO:cflib.crazyflie.log:Have successfully logging for block=4
INFO:cflib.crazyflie.log:Have successfully logging for block=5
INFO:cflib.crazyflie.log:Have successfully logging for block=6
INFO:cflib.crazyflie.log:Have successfully logging for block=7
INFO:cflib.crazyflie.log:Have successfully logging for block=8

and this is what the console in the cfclient is showing:

Code: Select all

SYS: Build 31:ba1d111112ad (2013.4) CLEAN
1FF50 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883L I2C connection [FAIL].
IMU: MS5611 I2C connection [FAIL].
MPU6050: Self test gyro X [FAIL]. low: 10.0, high: 105.0, measured: 0.0

the flie was standing on a flat hard surface.

[DesTinY]

and this is what the console in the cfclient is showing:

Code: Select all

SYS: Build 31:ba1d111112ad (2013.4) CLEAN
1FF50 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883L I2C connection [FAIL].
IMU: MS5611 I2C connection [FAIL].
MPU6050: Self test gyro X [FAIL]. low: 10.0, high: 105.0, measured: 0.0

the flie was standing on a flat hard surface.

The Self test of your gyro fails. Please read the post by tobias to solve this problem http://forum.bitcraze.se/viewtopic.php? ... 1924#p1757

[marcus]

Did it pass the self-test before you flashed new firmware on it? Have you had it flying at some point before?

If you try to power it on while moving it around a bit do you get a different measured value than 0.0?

[KOschi]

I tried to "bang" on all the 4 motorsides but this didn´t help.

Also when i move it around during the powerON it still reads 0,0 as measured value.

The self test was fine before the firmware update (just the M1 Motor wasn´t working) and i also was flying with the flie without problems.

[tobias]

You are definitely unlucky as it looks like the gyro x-axis is broken. I think it is the first time we have a broken gyro as it before only have been the accelerometer. I think it will be very hard fixing the gyro with the "tap/bang" method.
I can make a firmware which prints out all the self tests, just to rule out a possible of a software issue, if you want (very unlikely). Else you will have to contact Seeedstudio customer support to get it replaced.

[KOschi]

so all my problems started after my first attempt to update the firmware, now after the successfull update the hardware is broken? How can this be when the selftest was fine without the update?