Support for Brushless Crazyflie #168
Open
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.
Added support for the brushless Crazyflie in
interfaces/kr_crazyflie_interface. Unlike the brushed version, the brushless Crazyflie has to be armed before the motors can spin. To get around this, the Crazyflie interface now sends custom arming/disarming packets when Motors On and Motors Off are pressed.Currently, when the drone is disarmed its internal state machine enters a locked state where a reboot is required (unsure if this is by design). The workaround is to send a reboot packet when Motors Off is pressed. During the reboot process, Motors On does not work, so the button is disabled for 3 seconds.
This code was tested on both the brushed and brushless Crazyflies.