We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now nero message is sent in a few spots. That's ugly, we should trigger it periodically in one location preferably not the default task.
Nero message is sent in one spot.
Move around what calls it, possibly move the actual sending of the can message itself.
The text was updated successfully, but these errors were encountered:
Will include stop spamming state transitions via faults lolol
Sorry, something went wrong.
To do this, see my WIP branch linked to this issue (not nearly ready to be merged and out of date). Also see this pseduocode: https://nu-electric-racing.slack.com/archives/C01D7FG80ET/p1732938738790099
jr1221
When branches are created from issues, their pull requests are automatically linked.
Description
Right now nero message is sent in a few spots. That's ugly, we should trigger it periodically in one location preferably not the default task.
Acceptance Criteria
Nero message is sent in one spot.
Proposed Solution
Move around what calls it, possibly move the actual sending of the can message itself.
The text was updated successfully, but these errors were encountered: