search

railcore / configs

Configs for RailCore Printers
MIT License
15 stars 20 forks source link

Fix for BL-touch users. #49

Open dandancheeseandham opened 5 years ago

dandancheeseandham commented 5 years ago

RiskyBirdness 16th April 2019 at 00:58 GMT (on 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, 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.

dandancheeseandham commented 5 years ago

Nate, You have a BLtouch. Can you take a look at this when you have a mo please?

natewalck commented 5 years ago

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.

natewalck commented 5 years ago

Aha its ; BLTouch alarm release

natewalck commented 5 years ago

Deploy Probe - S10 Alarm Releast & Touch SW Mode - S60 Retract Probe - S90 Self-test - S120 Alarm Release & Probe Up - S160

xepherys commented 5 years ago

Doesn't this run the risk of executing print gcode when the BL-t is in alarm for some more legitimate reason?