Crazyflie has to be restarted after motion_commander_demo script runs #969
-
|
Hi, I'm working my way through CRTP by using the motion_commander_demo.py example as a reference. I've modified the script to do a basic takeoff and land like this in this code snippet: It works well but for some reason if I run it again Crazyflie will ignore any packets. I have to restart my drone to get the script to work again. I've experienced this behavior with two different Crazyflies. Is there something I should be checking/resetting to get it to run subsequent times? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
I can confirm. With the old way: The mc.take_off and land are commented out as they already are initiated with the initialization and closing of the motioncommander instance. Then I don't see this problem when reconnecting With the similar script as yours: Upon reconnection it does indeed not respond. Eventhough the enter and exit functions do exactly the same... maybe something to do with the threads not being properly stopped? This is more of an issue actually so I'll create one! |
Beta Was this translation helpful? Give feedback.
-
|
I don't think there is any difference in the two flavors of calling the Motion commander, if you see a difference it is perhaps due to timing? Anyway, fixed in bitcraze/crazyflie-lib-python#420 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the quick response and resolution. This is working well for me. It's refreshing to work with a company that is responsive and provides incredible support for their product! |
Beta Was this translation helpful? Give feedback.
I don't think there is any difference in the two flavors of calling the Motion commander, if you see a difference it is perhaps due to timing?
Anyway, fixed in bitcraze/crazyflie-lib-python#420