One more TimerTooClose story for troubleshooting #113
+2
−0
Conversation
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
|
Ohh I had the same issue. One cable was broken. I did not find why it was that, but It was initially running in the drag chains. Maybe that's the reason. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It took weeks to figure this one out, so I hope this can help others. Feel free to rephrase as needed.
What made me find it was ending up with a reliable repro (as in, my cable eventually was broken enough to prevent me from homing), prior to that the printer was simply "unreliable" and would randomly lose communication with the toolhead, sometimes mid-print, sometimes idling... sometimes it was fine for days.