Fix for BL-touch users. #49
Conversation
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
left a comment
natewalck
left a comment
There was a problem hiding this comment.
Add a description of what S160 does. I added the list of all the commands to the main comment thread.
|
Doesn't this run the risk of executing print gcode when the BL-t is in alarm for some more legitimate reason? |
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.