The creator 5 pro goes into "pause" mode if a clog is detected. - #23
Open
RedAces wants to merge 1 commit into
Open
The creator 5 pro goes into "pause" mode if a clog is detected.#23RedAces wants to merge 1 commit into
RedAces wants to merge 1 commit into
Conversation
In error code it returns "E0163", but this code is undocumented. Fix the error-detection to include an error code returned from the machine. add a printer_state.py to read the current state of the printer for debugging
This file contains hidden or 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
1 participant
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.
In error code it returns "E0163", but this code is undocumented. (See https://wiki.flashforge.com/en/creator-series/creator-5-series/error_code_creator_5)
Fix the error-detection to include an error code returned from the machine.
add a printer_state.py to read the current state of the printer for debugging
It would be nice if the "error" entity wouldnt only display "problem" but WHICH problem! e. g. either the raw error code or a short value ("Clog detected!"). For this I'd need to activate the inactive error code entity and add a mapping from code to description. What do you say?