[bugfix-1.1.x] BLTouch v3 fix#13596
Merged
thinkyhead merged 1 commit intoMarlinFirmware:bugfix-1.1.xfrom Apr 7, 2019
Merged
Conversation
The V3 of the BlTouch has a [Alarm Release & Touch mode](https://docs.wixstatic.com/ugd/f5a1c8_77037f55e5d542309d9fc178165c9f3f.pdf) to activate after the probe is deployed. If not activating this mode, the probe will keep on popping out and ends up detecting a collision and get itself in error mode. This was tested on my Creality Ender-3.
Member
|
Thank You!!! |
Contributor
|
Scott had mentioned he didn't intend for more to be pushed to 1.1.x so I didn't bring the 2.0 changes over, but this should match what was done in 2.0 if anything is accepted. |
Member
|
Well.... It is a matter of perspective.... But I would think this is OK to put into the BugFix v1.1.x branch. After all.... it is kind of a 'Bug Fix'. All of a sudden... BL-Touch probes don't work any more. |
thinkyhead
pushed a commit
that referenced
this pull request
Sep 2, 2019
V3 of the BLTouch has an [Alarm Release & Touch mode](https://docs.wixstatic.com/ugd/f5a1c8_77037f55e5d542309d9fc178165c9f3f.pdf) to activate after the probe is deployed. If this mode isn't activated, the BLTouch keeps deploying, ends up detecting a collision and gets itself in error mode. Tested on a Creality Ender-3.
bakaufman
pushed a commit
to bakaufman/Marlin
that referenced
this pull request
Oct 16, 2020
V3 of the BLTouch has an [Alarm Release & Touch mode](https://docs.wixstatic.com/ugd/f5a1c8_77037f55e5d542309d9fc178165c9f3f.pdf) to activate after the probe is deployed. If this mode isn't activated, the BLTouch keeps deploying, ends up detecting a collision and gets itself in error mode. Tested on a Creality Ender-3.
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
4 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.
Description
The V3 of the BlTouch has a Alarm Release & Touch
mode
to activate after the probe is deployed. If not activating this mode, the
probe will keep on popping out and ends up detecting a collision and get
itself in error mode.
This PR simply adds a configuration option BLTOUCH_V3 that set the BlTouch in that mode after deploying the probe.
Benefits
BLTouch V3 is unusable in the current state with Marlin 1.1.x. This fix the erratic behavior given in the description that already led to people sending back the probe.
Related Issues
I couldn't find the same issue on the bug tracker, although I did find several user complained on reddit about that.