Printer stuck in Probing Loop

[sunToxx]

I was printing small test objects for a filament chamber i am building and suddenly my printer gets stuck in a probing loop. It always probes the bed before print and so far all worked fine. And now I am suddenly getting this for no apparent reason

16.3.2022, 23:15:43	Cancelled printing file 0:/gcodes/fila chamber triangle test_0.1mm_PLA_MK3S_1h7m.gcode, print time was 0h 2m
!!! ABORTED !!! Failed to achieve < 0.01 deviation. Current deviation is 0.032mm.
16.3.2022, 23:14:08	Error: Z probe readings not consistent
16.3.2022, 23:13:30	Leadscrew adjustments made: -0.237 -0.361, points used 2, (mean, deviation) before (-0.303, 0.039) after (-0.000, 0.000)
16.3.2022, 23:13:04	Leadscrew adjustments made: -0.286 -0.136, points used 2, (mean, deviation) before (-0.207, 0.047) after (-0.000, 0.000)
16.3.2022, 23:12:46	M32 "0:/gcodes/fila chamber triangle test_0.1mm_PLA_MK3S_1h7m.gcode"
File 0:/gcodes/fila chamber triangle test_0.1mm_PLA_MK3S_1h7m.gcode selected for printing

16.3.2022, 23:22:44	Cancelled printing file 0:/gcodes/calib first layer 0_0.1mm_PLA_MK3S_5m.gcode, print time was 0h 3m
!!! ABORTED !!! Failed to achieve < 0.01 deviation. Current deviation is 0.014mm.
16.3.2022, 23:21:09	Leadscrew adjustments made: -0.276 -0.323, points used 2, (mean, deviation) before (-0.301, 0.014) after (-0.000, 0.000)
16.3.2022, 23:20:39	Leadscrew adjustments made: -0.268 -0.203, points used 2, (mean, deviation) before (-0.234, 0.020) after (0.000, 0.000)
16.3.2022, 23:20:09	Leadscrew adjustments made: -0.258 -0.372, points used 2, (mean, deviation) before (-0.318, 0.036) after (-0.000, 0.000)
16.3.2022, 23:19:43	M32 "0:/gcodes/calib first layer 0_0.1mm_PLA_MK3S_5m.gcode"
File 0:/gcodes/calib first layer 0_0.1mm_PLA_MK3S_5m.gcode selected for printing

Any idea what is going on? It is a CaribouDuet which came assembled and calibrated and so far all was fine.

[fcwilt]

@suntoxx

Hi,

Please copy-and-paste your bed.g file using the </> tag.

Thanks.

Frederick

[sunToxx]

@fcwilt thanks for the response! It seems the print that failed before the problem appeared, left a small blob of filament on the tip of the nozzle and that interfered with the BLToch, because the BLTouch had moved up a tiny bit.