-
Notifications
You must be signed in to change notification settings - Fork 21
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
Understandable message for /reset_error if major alarm is active #298
Conversation
Here is the necessary motoros2_interfaces pr |
@jimmy-mcelwain I just restructured a bit for consistency with the rest of the code. |
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.
@jimmy-mcelwain Let me know if you have any issue with my changes. Otherwise, I think it's good
as a final request: @jimmy-mcelwain: could you maybe squash your commits (and @ted-miller's fixup)? This change doesn't seem to need 4 commits :) |
…or, and add MotionNotReady code for major alarm to differentiate from minor alarms
a717abc
to
aef5d3b
Compare
Thanks @jimmy-mcelwain 👍 |
We'll need to fix CI after Yaskawa-Global/motoros2_interfaces#23 is merged. |
In reference to #181. Now if a major alarm is active upon calling
/reset_error
, motoros2 will not make any effort to reset alarms, and it will give a better response message. I also added aMotionNotReadyCode
for major alarms, separating it from minor alarms.