Crash detect #174
Merged
Crash detect #174
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
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.
Resolves #[Add issue number here]
Changes:
This PR adds crash detection capabilities to the jubilee python interface. See the docs for more details on what this looks like on Jubilee. This PR modifys the machine.gcode method to monitor for a 'crash detected' message published by duet if a tool ball trigger is detected. It also adds utils/Handlers.py, which currently contains a slack error handler that can be used to message a user on slack and wait for input to proceed after detecting a crash.
PR Checklist