Bitcraze Forums

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

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.

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...

Thanks,

this worked quit nicely, I´ve looked in all the .json files except for this one.

is it possible to change the increasing/deceasing amount of the trim values set by the controller ? At the moment each press on the controller buttons changes the trim values for +/- 1 but i wold like to set this value much lower e.g. 0.1-0.5 to get a better hoover behavior. It (CF2) hoovers quite g...

i´ve had a similar event, but not as dramatic as yours.

The flie was hovering over the ground (indoor) and both front motors went up to 100% without any reason.
It crashed into the furniture but nothing was broken and it is still working.

for me the newest version dosen´t work at all: INFO:cfclient.cfclient:Disabling STL printouts INFO:cfclient.utils.config:Dist config read from /usr/cfclient/configs/config.json INFO:cfclient.utils.config:Config file read from [/root/.local/cfclient/config.json] ===== 2014.12.22 09:12:01 ===== Traceb...

i´ve tried the workaround and it´s working.

I have the same issue on an opensuse 13.1.
Exactly like you said, by starting "configure device mapping" and by closing the gui i get a segmentation fault.
A (bad) workaround for me is to change the mappings and then start "configure device mapping" this works.

This script is relay nice. I had to change the length of the array but now it is working. And the funny thing is that the axis won´t be recognized. All buttons and axis are working but i can´t get a signal for the left stick x-axis. So it looks like something more deep like a driver problem. -------...