From 85703345f9d8ec3fce01507a86053e9098b6071e Mon Sep 17 00:00:00 2001 From: Dan White <44091159+dandancheeseandham@users.noreply.github.com> Date: Tue, 16 Apr 2019 11:58:09 +0100 Subject: [PATCH] Fix for BL-touch users. 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. --- duet/sys/homez.g | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/duet/sys/homez.g b/duet/sys/homez.g index 9868a05..59a8098 100644 --- a/duet/sys/homez.g +++ b/duet/sys/homez.g @@ -3,6 +3,13 @@ ;Use-case : the machine may be Z-homed from any position at a reasonable pace, without resorting to dangerous options such as M564 H0 - while still retaining accuracy of the final probe. G91 G1 Z5 F800 S2 ; lift z so we don't crash + +;M280 P3 S160 ; Fix for BL-touch users - + ; 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. + G90 G1 X150 Y150 F6000 ; Move to the center of the bed ; M558 Fxxx sets the probing speed.