Thank you for providing this easy-to-use ROS package for interecting with crazyflie!
Recently I'm trying to hover a single crazyflie using the Python script "Hover.py" under crazyflie_demo. As instruction I installed this ros package and run "roslaunch crazyflie_demo hover.lunch". I know this script allows for two crazyflies so I comment the code to ignore one of them.
Everything looks normal after I run "roslaunch crazyflie_demo hover.lunch", the motors start spining fast and it seems to be taking off. But after a few seconds, the motors just stop and the drone could not take off during this period (just slightly moving on the ground). It seems the program has been executed but no hovering effect happens.
I check rostopic echo /cmd_vel and shows nothing after the motors stop spining. I use the latest firmware release 2020.02 and I do not use flow deck during this test. I thought the barometer may be enough to finsh the taking-off task (even if not very stable). But now I don't know where is the problem. Is this because the thrust is not large enough? But that does not make sense. Obviously the drone should adjust its thrust to take off.
I'd appreciate it if you could help me with this. Thank you!
Hi @whoenig
Thank you for providing this easy-to-use ROS package for interecting with crazyflie!
Recently I'm trying to hover a single crazyflie using the Python script "Hover.py" under crazyflie_demo. As instruction I installed this ros package and run "roslaunch crazyflie_demo hover.lunch". I know this script allows for two crazyflies so I comment the code to ignore one of them.
Everything looks normal after I run "roslaunch crazyflie_demo hover.lunch", the motors start spining fast and it seems to be taking off. But after a few seconds, the motors just stop and the drone could not take off during this period (just slightly moving on the ground). It seems the program has been executed but no hovering effect happens.
I check rostopic echo /cmd_vel and shows nothing after the motors stop spining. I use the latest firmware release 2020.02 and I do not use flow deck during this test. I thought the barometer may be enough to finsh the taking-off task (even if not very stable). But now I don't know where is the problem. Is this because the thrust is not large enough? But that does not make sense. Obviously the drone should adjust its thrust to take off.
I'd appreciate it if you could help me with this. Thank you!