Add driver and test code for engineer vehicle arm #60
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
AzulRadio
changed the title
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.
Need 3 A1, 3 M4310, 1 M3508, and a GPIO bool sensor to test this.
All motor IDs, GPIO ports, and other config params should be set in
vehicle/Engineer/arm_config.h.Expected behavior:
vehicle/Engineer/arm.ccis the arm test thread.It should turn each motor for PI/16 degrees every 2 seconds and stop at the defined limitation in
arm_config.h.This has a 2 sec stop before running anything.
vehicle/Engineer/arm_test.ccis the motor test thread.It tests 3 types of motors. One of each type.
Tester should enable 3 motors in lines 39 - 41.
Push the white key and the motors should be enabled.
Then, push the white key and the motors should turn for PI/4. Push again and they should go back.