Fix for BL-touch users. #49
Open
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
RiskyBirdness 16th April 2019 at 00:58 GMT Discord PUBLIC SERVICE ANNOUNCEMENT FOR BLTOUCH USERS.. When you power up your printer the BLTouch runs an internal test routine and deploys the probe twice. If the nozzle height is close to the bed at the time the routine is run the probe will not fully deploy and BLTouch will enter an alarm state(flashing). In this state it will be non functional but the Duet has no way of knowing this. If you perform a Z home in this state you will get a nozzle crash, damage your BLTouch probe, and damage your print surface. The solution is to always clear your BLTouch alarm at the top of your homeZ.g and homeall.g scripts using M280 P3 S160. Not sure whether to uncomment it and make it "standard" or not. Will have to test to see if it affects other probes such as IR.
dandancheeseandham
requested review from
lostapathy and
natewalck
and removed request for
lostapathy
|
Nate, |
|
I'll have to give it a test. I'm not sure what this gcode does exactly except specify the servo again in the homez. What does S160 do? I use these https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/deployprobe.g and https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/retractprobe.g But never tried S160. |
|
Aha its ; BLTouch alarm release |
|
Deploy Probe - S10 |
natewalck
requested changes
Apr 24, 2019
|
Doesn't this run the risk of executing print gcode when the BL-t is in alarm for some more legitimate reason? |
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.
RiskyBirdness 16th April 2019 at 00:58 GMT (on Discord)
Not sure whether to uncomment it and make it "standard" or not, but putting it in while the information presented itself.
I'll have to test to see if it affects other probes such as IR if inserted.