Please fill out the following before requesting review on this PR
Description
Was debugging why Chopper sometimes autochip on startup. Couldn't find anything wrong that our software is doing.
What I did to test:
print out power loop status messages
print out power loop command messages
we don't end up calling the poll function because after it autochips, Chopper's SPI communication with the motors fail
I don't think this fix resolves the autochip issue but setting up a safe default explicitly is always a good thing in case.
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
[ ] Function & Class comments: All function definitions (usually in the .h file) should have a javadoc style comment at the start of them. For examples, see the functions defined in thunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.
[ ] Remove all commented out code
[ ] Remove extra print statements: for example, those just used for testing
[ ] Resolve all TODO's: All TODO (or similar) statements should either be completed or associated with a github issue
Please fill out the following before requesting review on this PR
Description
Was debugging why Chopper sometimes autochip on startup. Couldn't find anything wrong that our software is doing.
What I did to test:
poll
function because after it autochips, Chopper's SPI communication with the motors failI don't think this fix resolves the autochip issue but setting up a safe default explicitly is always a good thing in case.
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
.h
file) 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