Call send_notify_setpoint_stop() #413
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 thesend_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