Require TMCStepper >=0.6.2 for LPC176x controllers #17934
Merged
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
vgadreau
pushed a commit
to vgadreau/Marlin
that referenced
this pull request
May 29, 2020
jmp0x0000
pushed a commit
to jmp0x0000/Marlin
that referenced
this pull request
Aug 7, 2020
njibhu
pushed a commit
to njibhu/Marlin
that referenced
this pull request
Aug 24, 2020
HairingX
pushed a commit
to HairingX/Marlin
that referenced
this pull request
Jun 16, 2021
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.
Description
Update the minimum version of TMCStepper required for LPC1768/9 environments.
Benefits
TMCStepper 0.6.2 includes the following fix, which resolves communication issues when using single-pin software serial. This most significantly impacts SKR 1.4 boards, which use single-pin serial by default.
Without this change impacted boards could sometimes (but not always) fail to properly configure their last TMC driver, usually their extruder. When this occurred TMC status would report OK, but the wrong number of microsteps were often used.
teemuatlut/TMCStepper#101
Related Issues
I'm not aware of currently open issues, but this came to my attention due to a Discord user having issues with their extruder driver travelling the wrong distance. This might not be the root cause, but it is very possible.