Page 1 of 1
[SOLVED] Crazyflie 2.0 red flashing
Posted: Tue May 12, 2015 12:03 pm
by Basse
Can't fly my Crazyflie 2.0. Red is flashing (rapidly). Android + BLE. Help!
Re: Crazyflie 2.0 red flashing
Posted: Thu May 14, 2015 1:02 am
by derf
Sorry, but "Can't fly my Crazyflie" is not a very meaningful description of a problem.
Please provide more details what exactly does not work for you.
E.g.
-Did you manage to get a connection to the Crazyflie (green light blinking rapidly) after clicking on the connect button (the one with the two arrows)?
-Did you see any error messages?
Re: Crazyflie 2.0 red flashing
Posted: Fri May 15, 2015 7:53 am
by Basse
The app is started. Switch on Crazyflie and the selftest goes well. The blue ones are lighting. The red is flashing. What does it mean? What is the message?
Click the connect button. After 10 seconds I get the message Conection lost.
Re: Crazyflie 2.0 red flashing
Posted: Fri May 15, 2015 8:09 pm
by derf
For an explanation of the LEDs see:
https://wiki.bitcraze.io/projects:crazy ... uide:index
What kind of Android device do you use?
Which Android version are you running?
Do you have a Crazyradio to test the connection?
Re: Crazyflie 2.0 red flashing
Posted: Sun May 17, 2015 1:42 pm
by Basse
I can't see any explanation of this flashing in the guide.
I have a Samsung Galaxy Tab S.
Android version 5.0.2
I have not a Crazyradio.
Re: Crazyflie 2.0 red flashing
Posted: Sun May 17, 2015 2:39 pm
by derf
Sorry, this link should explain the blinking pattern better (it's for the CF1 but should still apply for the CF2):
https://wiki.bitcraze.io/projects:crazy ... uide:index
To isolate the problem please try a different Android device from a friend (Android 4.4+ with BLE support).
[Solved]Crazyflie 2.0 red flashing
Posted: Mon May 18, 2015 8:05 am
by Basse
Yes, it flies with Android 4.4.2
When will it be compatible with Anroid 5.0.n?
Re: Crazyflie 2.0 red flashing
Posted: Mon May 18, 2015 9:33 am
by derf
I'm sorry that the Android client is not compatible with your device. It is compatible with Android 5.0.0 and 5.0.1, at least on a Nexus 5 and I doubt that 5.0.2 broke the compatibility.
Without the device in front of me it's hard to isolate the problem. I will try to implement a debug log in one of the next versions (due in the beginning of June).