-
Notifications
You must be signed in to change notification settings - Fork 122
Changes to Powerloop for Power Board 4.1 #3485
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
base: master
Are you sure you want to change the base?
Changes to Powerloop for Power Board 4.1 #3485
Conversation
…kha/Software into william/power-board-4.1
| ansible.builtin.command: "/home/{{ ansible_user }}/hash_thunderloop_binary.sh" | ||
| register: result | ||
| changed_when: true | ||
| # - name: Compute Thunderloop MD5 Hash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems accidental
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems accidental
| */ | ||
| static void oneShotPulse(int duration, int pin); | ||
|
|
||
| static void setChargeHigh(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs
| static volatile bool on_cooldown; | ||
| static constexpr int COOLDOWN_MICROSECONDS = 3 * MICROSECONDS_IN_SECOND; | ||
|
|
||
| static constexpr unsigned int CHRG_DONE_PIN = 25; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like these could be private
itsarune
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this overdue cleanup
Description
Testing Done
Resolved Issues
Length Justification and Key Files to Review
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.hfile) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO(or similar) statements should either be completed or associated with a github issue