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

Call send_notify_setpoint_stop() #413

Merged
merged 1 commit into from
Aug 29, 2023
Merged

Call send_notify_setpoint_stop() #413

merged 1 commit into from
Aug 29, 2023

Conversation

krichardsson
Copy link
Contributor

Since the re-work of the supervisor, the behavior of some scripts has changed. When sending setpoints and then calling send_stop_setpoint() will lock up the Crazyfile after a time out and a restart is required to run the script again (see bitcraze/crazyflie-firmware#1297). The reason is that no more set points are sent from the client (script) and the firmware interprets this as the connection is lost. By calling the send_notify_setpoint_stop() function we tell the the firmware to switch back to the high level commander and the time out will not happen.

This PR updates some example scripts and adds a call to send_notify_setpoint_stop() to make it possible to run them over and over again

@tobbeanton tobbeanton merged commit f173601 into master Aug 29, 2023
1 check passed
@tobbeanton tobbeanton deleted the krichardsson/stop branch August 29, 2023 12:24
@knmcguire knmcguire added this to the next-release milestone Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants