When issuing G28, my printer no longer moves the Z-axis up, the X and Y axes home normally, the printer moves to the probing point (X&Y only), the pin comes down, and I get a “BL Touch failed to deploy” message when the probe contacts the bed. This was working prior to today.
My printer is heavily modified, but the only change I made today was switching the Y-axis stepper motor. Is there anything in the log that would indicate the probe itself failed? It isn’t particular old/worn.
I did replace the sensor and wiring, and ran through the initial tests which produced the expected results. Still have the issue when issuing G28 I’ve also noticed that the printer no longer raises Z 10mm when homing
You have z_offset = -0.305 which would mean your nozzle hits the bed before the probe triggers → Set it to 5 and then repeat PROBE_CALIBRATE as per documentation
Also, when homing, the Z axis does not raise 10mm anymore (safe home is not working). When I manually raise the z axis and try to trigger the probe early, I get the same behavior
Hmm, I cannot see anything apparently wrong in your config.
You are sure that the complete “Initial Tests” including the debug commands work as they should?
I ran through the initial tests again and commented out the lines suggested. When I ran G28 this time, the error changed to Failed to verify BLTouch probe is raised; retrying
I did see that section, and none of the listed steps apply. All of the initial tests work as expected, pin_up moves the pin up, pin_down moves the pin down, the probe shows open in both positions unless touch mode is active and the pin is touched.
What isn’t working is the G28 command. Z no longer goes up 10mm like it used to, and I get the bltouch failed to deploy message. If I set probe_with_touch_mode: False then I get Failed to verify BLTouch probe is raised; retrying in addition to bltouch failed to deploy
I’d like to point out that this is not a new config. This probe was working until just before I submitted this post. I had changed the Y motor on the printer and then when I reassembled everything I had this issue.