We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
case 1 : PS4 controller >>cfclient : takeoff ok.
case 2 :
The drone, dont takeoff correctly, what's wrong ? (Falls to the side, the motors do not start at the same time, and do not stop at the same time)
Could you help please ? Thank you
The text was updated successfully, but these errors were encountered:
@TarwiAkka The current joystick mapping is now set to an xbox controller as mentioned in the documentation: https://imrclab.github.io/crazyswarm2/usage.html#teleoperation-controller. Is that done correctly?
Also, the Crazyflie will be locked if the first setpoint it is sent to it are non-zeros, this is an implementation in the firmware but described here in the python API: https://www.bitcraze.io/documentation/repository/crazyflie-lib-python/master/user-guides/python_api/#attitude-setpoints
Sorry, something went wrong.
whoenig
No branches or pull requests
Hello,
case 1 :
PS4 controller >>cfclient : takeoff ok.
case 2 :
-ros2 launch crazyflie launch.py teleop:=True
-remapping and modifiying teleop.yaml
-crazyswarm.yaml : controller: 1
The drone, dont takeoff correctly, what's wrong ?
(Falls to the side, the motors do not start at the same time, and do not stop at the same time)
Could you help please ?
Thank you
The text was updated successfully, but these errors were encountered: