You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Thank you for putting in all the hard work to build a Crazyflie simulator with Gazebo - without it my research project would be MUCH harder.
I need to use a roll/pitch/yaw/thrust controller with the Crazyflie, and I see that you've emulated the CrazyFlie's builtin controller for your position_controller, but I'm not sure how to use that.
In other words: How could I use the crazyflie_onboard_controller so that I can accept roll/pitch/yaw/thrust messages (like those sent with crazyflie_ros) and have the model behave just like the actual firmware would make it?
The text was updated successfully, but these errors were encountered:
Thank you for finding CrazyS interesting for you. As reported in the README.md file, if you are using the simulator in the search for the publication/project, please cite the reference paper. We are writing a further paper to explain in more detail how the code works (it will help developers and researchers to use CrazyS for research) and how to use it to simulate the Crazyflie 2.0
What do you mean exactly with "roll/pitch/yaw/thrust controller"? Did you emulate the joypad?
You should use the SetControlSignals, SetDroneState and RateController functions (described in the "crazyflie_onboard_controller.cpp" file), as shown in line 185 of the "position_controller.cpp" file and in Figure 7 of the reference paper.
Hello! Thank you for putting in all the hard work to build a Crazyflie simulator with Gazebo - without it my research project would be MUCH harder.
I need to use a roll/pitch/yaw/thrust controller with the Crazyflie, and I see that you've emulated the CrazyFlie's builtin controller for your position_controller, but I'm not sure how to use that.
In other words: How could I use the
crazyflie_onboard_controller
so that I can accept roll/pitch/yaw/thrust messages (like those sent withcrazyflie_ros
) and have the model behave just like the actual firmware would make it?The text was updated successfully, but these errors were encountered: