Differences

This shows you the differences between two versions of the page.

--- projects:crazyflie:userguide:troubleshooting [2013-06-01 07:39]
macke
+++ projects:crazyflie:userguide:troubleshooting [2014-10-10 21:34]
chad [When I start the Crazyflie the red LED blinks 5 times and I can't fly it?] Sentence structure.
@@ Line 9: / Line 9: @@
 ==== When I start the Crazyflie the red LED blinks 5 times and I can't fly it? ====
 {{:projects:crazyflie:userguide:cf-client_console.png?direct |}}
-During the start-up all the mounted sensors run a self test. If either of these test fail it will cause the 5 red blinks. It is possible to see exactly what failed by connecting to the Crazyflie with the cf-client and open up the console tab.
+During the start-up all the mounted sensors run a self test. If any of these tests fail, the failure will cause the red LED to flash 5 times. It is possible to see exactly what failed by connecting to the Crazyflie with the cf-client and open up the console tab.
-The picture shows the console tab with no errors but when you have an error it might say e.g //MPU6050: Self test acc Y [FAIL]. low: 0.300000, high: 0.949999, measured: 0.0.// This example means that the accelerometer Y axis didn't pass the self test and is probably defective. It is possible to get this error also if the Crazyflie is moved to much during the self test so try putting it on a sable surface before you power it on.
+The picture shows the console tab with no errors but when you have an error it might say e.g //MPU6050: Self test acc Y [FAIL]. low: 0.300000, high: 0.949999, measured: 0.0.// This example means that the accelerometer Y axis didn't pass the self test and is probably defective. It is possible to get 5 blink error also if the Crazyflie is moved to much during the self test, so try putting it on a sable surface before you power it on.
-Another thing to try, if you get an accelerometer self test error with measured value 0.0, is to tap/bang it on the sides. E.g. use a table edge to tap/bangit against, and tap/bang the rounded corners of the PCB (where the LEDs are). This could in theory release the accelerometer lock-up. If you managed to fix it this way please let us know as well because it is just theory now.
+Another thing to try, if you get an accelerometer self test error with measured value 0.0, is to tap/bang it on the sides. E.g. use a table edge to tap/bang it against, and tap/bang the rounded corners of the PCB (where the LEDs are). This could in theory release the accelerometer lock-up. We have had several successful cases doing this and if you managed to fix it this way please let us know.
 If anything of the above didn't fix it you probably have a broken sensor and the sensor needs to be replaced. Contact [[https://www.seeedstudio.com/depot/index.php?main_page=customer_service|Seeedstudio customer support]] and they will help you out. You can also visit the forum and especially [[http://forum.bitcraze.se/viewtopic.php?f=5&t=120|this thread]].
@@ Line 22: / Line 22: @@
-When the PCB arm breaks it breaks it almost always break as in the picture. Since there is a bit of it left it can be used to fix it.
+When the PCB arm breaks it almost always break as in the picture. Since there is a bit of it left it can be used to fix it.
 {{:projects:crazyflie:userguide:pcbfix_broken_point.jpg?direct&200}}
@@ Line 53: / Line 53: @@
 ==== I'm having strange problems with the sensor test not passing/motors not spinning/horizon not moving when connected? ====
 Try to flash the latest firmware using the instructions [[projects:crazyflie:pc_utils:qt_ui#crazyflie_service|here]] and firmware [[https://bitbucket.org/bitcraze/crazyflie-firmware/downloads|here]].
+==== I upgraded the firmware on the Crazyflie and now it doesn't start ====
+If you get errors during the upgrade or you upgrade to your own custom software that has bugs you might not be able to start the firmware. The typical behaviour for this during power on is that the red/gre LEDs blink and then nothing else happens. No sensor test is run (i.e no more blinking LEDs) and you cannot connect with the Crazyradio.
+When upgrading the firmware the bootloader cannot be overwritten or modified so you always have the option of going into bootloader mode and upgrading the firmware again. [[projects:crazyflie:pc_utils:qt_ui#bootloader|Here]] are the instructions for upgrading the firmware.
+==== I'm having problems entering the bootloader mode ====
+Try the following steps:
+  - Power off the Crazyflie
+  - Un-plug and insert the Crazyradio again
+  - Start the cfclient
+  - Go to the menu //Crazyflie→Bootloader// and click //Initiate bootloader cold boot//
+  - Power on the Crazyflie (not using USB, only battery) within 1-5 seconds after initiating the bootloader
+  - Flash new firmware **without** the //Verify// option enabled

Bitcraze Wiki

User Tools

Site Tools

Differences

Page Tools