Skip to content
New issue

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

Make more send_setpoint functions #152

Closed
knmcguire opened this issue May 11, 2020 · 4 comments · Fixed by #452
Closed

Make more send_setpoint functions #152

knmcguire opened this issue May 11, 2020 · 4 comments · Fixed by #452

Comments

@knmcguire
Copy link
Contributor

Currently there is no way to send a setpoint from the library for attitude rate, which has been requested from this issue from the firmware: bitcraze/crazyflie-firmware#572. This used to be possible but that was before the current commander framework was implemented a few years ago.

@jonasdn
Copy link
Contributor

jonasdn commented Sep 6, 2021

@knmcguire do you have any tips for anyone looking to implement this?

@knmcguire
Copy link
Contributor Author

The flightmode.stabmoderoll/pitch seems to be needed to put to one in order to make the crazyflie react to the attitude setpoints in a rate PID manner.

@knmcguire
Copy link
Contributor Author

knmcguire commented Apr 24, 2024

So this is already possible if this function is used:

send_setpoint(self, roll, pitch, yawrate, thrust)

while the flightmode.stabmodroll/pitch are set to 1

I'll add this to the documentation so that this is clear to the users that this is possible.

We also heard from some people that they'll like to set the motors directly but that would require starting a new commander crtp port and a setpoint structure for the rpm/volt per motor, so that should be a new issue.

@knmcguire
Copy link
Contributor Author

made new issue in firmware to address making an crtp commander port to set motors bitcraze/crazyflie-firmware#1372

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants