Bitcraze Forums

Yesterday I crashed the Crazyflie 2 and one of the motor connectors was bend a little.
I pushed it back into position and everything is working fine.

Except the LED M1, usually it was flashing in red (the heartbeat) but now it changes after a short period of time in flight into a permanent red.
What dose that mean ?
Is this related to the twisted motor connector ?

Crashing is a natural part of flying the CF2 I think, although the crashes are getting fewer the more you fly...

The M1 is used both as a heartbeat and a low battery indicator (see http://wiki.bitcraze.se/projects:crazyf ... uide:index), when the battery is low it changes from blink (heartbeat) to solid read. A while after that you will see that the two blue led:s on the back of the flie will start to fade as a result of low voltage, and then the flie will drop out of the sky. I believe that I can fly for about 4-5 minutes with the heartbeat showing, and the last minute or two it will show the low battery indication.

Thanks for the answer,
this makes sense but in the beginning the LED was only flashing, the permanent red behavior started yesterday and i´ve not changed the firmware, kinda funny.

Im just now playing with my CF2 and I am experiencing strange LED behavior too... if I start the plotter the CF2:s led:s change behaviour, the two front ones (LED 4 and 1) are constantly on (expected from LED4 because of RX/TX but not from LED1, heartbeat...) and LED 3 is completely off, but i can still fly ok... I have also experienced that no LED but LED2 is on after startup. I think they might have a few buggs in the FW, have you tried to disconnect the battery? I am not sure that will help anything, but it might be worth a shoot

Hmm, this is indeed strange. My first thought that the soldering cracked but then the LED would not turn on instead of always being on. Sounds like a bug thing or maybe an assert. When en assert happens in the code the blue led will go off and the two red leds on. When hitting an assert the STM32 firmware will stop in an infinite loop though so it won't fly. However the radio link might still be up as that is handled by the nRF51.

Since everything is working fine and I get a nice new feature I think I am fine with the new behavior.