Motors Spinning on Connection

Firmware/software/electronics/mechanics
Post Reply
alanj853
Beginner
Posts: 3
Joined: Fri Nov 13, 2015 12:16 pm
Location: Ireland

Motors Spinning on Connection

Post by alanj853 »

Hi,

I have recently been given a Crazyflie 2.0 by my college as part of a project. I have managed to set up the VM and have been flying the CF with an Xbox 360 remote control. The problem I am having is when I initially connect to the CF using the CF python client provided. When I initially connect to the CF, the motors spin very fast by themselves, and the CF is unresponsive to any input from the remote control. The only way I have found to stop them spinning is by clicking the "Crazyflie" tab, and then "Configure 2.0", and then clicking "write" with all of the default values. When I click this, the motors stop instantly, and the CF can be flown as normal. Also, once this has been clicked I can hit "Disconnect" and disconnect from the CF and then reconnect with no problem, provided the CF itself has not been turned off. If the CF has been turned off, the same problem occurs.

I have updated the code using the "Update all projects" application, but still have the same problem. Is there some bit of code I need to change to prevent the motors from spinning like this on connection?

Thanks
arnaud
Bitcraze
Posts: 2538
Joined: Tue Feb 06, 2007 12:36 pm

Re: Motors Spinning on Connection

Post by arnaud »

Hi,

I have never seen this problem related to the copter itself, it is usually related to the way the gamepad is configured.

You can try to update the Crazyflie to the latest version using the bootloader: https://github.com/bitcraze/crazyflie-release/releases

To see if the problem comes from the gamepad you can look at the thrust setpoint in the client before connecting, it should be at 0.
alanj853
Beginner
Posts: 3
Joined: Fri Nov 13, 2015 12:16 pm
Location: Ireland

Re: Motors Spinning on Connection

Post by alanj853 »

Thanks arnaud, I re downloaded the a fresh version of the VM and updated the firmware code on the CF with the code that was on the new VM and the problem was fixed.
Post Reply