If I cancel a print and home X or Y manually, head crash in bed

Zoltan3D

Hello all,

I sucessfully setup my Duet 6HC with 1LC with my giant cartesian printer (900x900x900mm)

For homing and bed mesh I use a BLTouch,
everything work like a charm after some optimisation and prints

If I home X or Y manually with homing button on SBC web control, it's perfect : Z rize some mm, home X or Y or both and go back to the previous Z height

But last day and today i made an error in the print, and Pause and after Cancelled it, After this I removed the print and hit X home button,
Z rize like normally, X go home, and at the moment when the X homing finished, Z go down without never stopping, no stop at 0, no BTtouch deploy, nothing, it crash into the bed and nearly broke my completly new setup ...

I made this 2 times, and after I tried on purpose, with a print cancel, and X or Y home, and it reproduce this 100% of time, even after a hard reboot . and with multiple different gcode in case of..

What file can I give to you to find from where this problem comes N because it's really dangerous for the printer

Also I have one other question : If I fail a print on the first layer, and for some reason I hit emergency stop or unplug, when the printer restart, BLTouch directly try to self test, but the probe hit the bed (normal it's too low to self test) the only way I found to go out of this situation is to make a M564 H0 to disable security and after this up Z and restart the printer to remove the BLtouch error signal.
Is there a way with gcode or a config file to make the Z directly go up 5/10mm when you plug in the printer and AFTER this make a BLTouch initialisation ?

Thanks a lot

fcwilt

@Zoltan3D

Is there some code in config.g that is executing the BLTouch self-test?

I have a couple of printers with BLTouch devices and have never seen this behavior BUT I don't used the Duets with SBCs.

Frederick

Phaedrux

Share your config.g, homing files, cancel.g, pause.g etc
Also the results of sending M122 and M98 P"config.g" in the gcode console.

deckingman

@Zoltan3D As @Phaedrux has said, we need to see your homing files and other files. The most likely cause of the homing failing after a print is cancelled is that in pause.g or cancel.g is a G90 command that sets positioning to absolute and your homing files are lacking a G91 to set the positioning to relative. So instead of moving an axis by a few mm, it tries to move the axis to a position a few mm away from zero.