Printer halts at first Z-probe attempt

I upgraded my CoreXY printer's mainboard to SKR2 Rev.B and having troubles configuring ABL feature. I have z-probe of my own design with optical sensor and electronic circuit identical to the circuits of X, Y and Z end-stops.
Print head needs to move at a certain X, Y positions and push against printer's side panel to mechanically activate the probe. Probe is deactivated (retracted) when print head returns to home position at X-max/Y-max. Z-homing happens at Z-max.
When probe is retracted (not used) M119 shows it as TRIGGERED. Here is the output in Home position:

Send: M119
Recv: Reporting endstop status
Recv: x_max: TRIGGERED
Recv: y_max: TRIGGERED
Recv: z_max: TRIGGERED
Recv: z_probe: TRIGGERED
Recv: ok

When it is released the state changes to Open. Here is the output with activated probe at position X100 Y100 Z80

Send: M119
Recv: Reporting endstop status
Recv: x_max: open
Recv: y_max: open
Recv: z_max: open
Recv: z_probe: open
Recv: ok

When bed moves up and touches activated probe, the state changes from open to TRIGGERED.

My issue is - after activating the probe and executing G29 print head moves to the initial measurement position as per PROBING_MARGIN, bed starts raising and as soon as the bed touches the probe printer halts with the error shown below:

Send: G29
Recv: echo:G29
Recv: >>> G29  X100.00 Y100.00 Z88.00
Recv: Machine Type: CoreCartesian
Recv: Probe: FIX_MOUNTED_PROBE
Recv: Probe Offset X-34.40 Y10.60 Z4.50 (Left-Back & Above Nozzle)
Recv: Auto Bed Leveling: BILINEAR (disabled)
Recv: 
Recv:   current_position= X100.00 Y100.00 Z88.00 : Probe::set_deployed
Recv: deploy: 1
Recv: Probe::do_z_raise(10.00)
Recv: >>> do_blocking_move_to  X100.00 Y100.00 Z88.00
Recv: >  X100.00 Y100.00 Z88.00
Recv: <<< do_blocking_move_to  X100.00 Y100.00 Z88.00
Recv: >>> do_blocking_move_to  X100.00 Y100.00 Z88.00
Recv: >  X100.00 Y100.00 Z88.00
Recv: <<< do_blocking_move_to  X100.00 Y100.00 Z88.00
Recv: reset_bed_level
Recv: >>> Probe::probe_at_point  X100.00 Y100.00 Z88.00
Recv: ...(20.00, 20.00, raise, 0, probe_relative)
Recv:   current_position= X100.00 Y100.00 Z88.00 :
Recv: >>> do_blocking_move_to  X100.00 Y100.00 Z88.00
Recv: >  X54.40 Y9.40 Z88.00
[...]
Recv: <<< do_blocking_move_to  X54.40 Y9.40 Z88.00
Recv:   current_position= X54.40 Y9.40 Z88.00 : Probe::set_deployed
Recv: deploy: 1
Recv: >>> Probe::run_z_probe  X54.40 Y9.40 Z88.00
Recv: >>> Probe::probe_down_to_z  X54.40 Y9.40 Z88.00
Recv: >>> do_blocking_move_to  X54.40 Y9.40 Z88.00
Recv: >  X54.40 Y9.40 Z-24.50
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
[...]
Recv: echo:busy: processing
Recv: <<< do_blocking_move_to  X54.40 Y9.40 Z-24.50
Recv:   current_position= X54.40 Y9.40 Z4.04 : sync_plan_position
Recv: <<< Probe::probe_down_to_z  X54.40 Y9.40 Z4.04
Recv: FAST Probe fail! - Triggered early.
Recv: <<< Probe::run_z_probe  X54.40 Y9.40 Z4.04
Recv:   current_position= X54.40 Y9.40 Z4.04 : Probe::set_deployed
Recv: deploy: 0
Recv: >>> do_blocking_move_to  X54.40 Y9.40 Z4.04
Recv: >  X54.40 Y9.40 Z4.04
Recv: <<< do_blocking_move_to  X54.40 Y9.40 Z4.04
Recv: Errorrobing Failed
Changing monitoring state from "Operational" to "Error"
Send: M112

Here is additional information. The same probe worked fine with old motherboard running Repetier 1.04.
Marlin version 2.0.9.3.
Configuration settings relevant to probing are:

#define Z_MIN_PROBE_ENDSTOP_INVERTING false // Set to true to invert the logic of the probe.
#define FIX_MOUNTED_PROBE
#define AUTO_BED_LEVELING_BILINEAR
#define RESTORE_LEVELING_AFTER_G28
#define PROBING_MARGIN 20
#define NOZZLE_TO_PROBE_OFFSET { -34.4, 10.6, 3.7 }
#define MULTIPLE_PROBING 2
#define GRID_MAX_POINTS_X 7 
#define GRID_MAX_POINTS_Y GRID_MAX_POINTS_X
#define Z_CLEARANCE_DEPLOY_PROBE   10 // Z Clearance for Deploy/Stow
#define Z_CLEARANCE_BETWEEN_PROBES  5 // Z Clearance between probe points
#define Z_CLEARANCE_MULTI_PROBE     5 // Z Clearance between multiple probes
#define Z_PROBE_LOW_POINT          -20
#define Z_PROBE_OFFSET_RANGE_MIN -20
#define Z_PROBE_OFFSET_RANGE_MAX 20
#define XY_PROBE_FEEDRATE (133*60)
#define Z_PROBE_FEEDRATE_FAST (4*60)
#define Z_PROBE_FEEDRATE_SLOW (Z_PROBE_FEEDRATE_FAST / 2)
#define Z_SAFE_HOMING

I have tried inverting Z_MIN_PROBE_ENDSTOP_INVERTING but that did not help.

Has anyone experienced something similar? What am I missing here?

Thanks

Edited 3 time(s). Last edit at 04/11/2022 03:06PM by lmcbmai.

Try this

#define Z_MIN_ENDSTOP_INVERTING false // set to true for SN-04N false for TL-W3MC2.

#define Z_MIN_PROBE_ENDSTOP_INVERTING false // set to same logic as "Z_MIN_ENDSTOP_INVERTING".

---

Computer Programmer / Electronics Technician

During my tests Z_MIN_ENDSTOP_INVERTING and Z_MIN_PROBE_ENDSTOP_INVERTING were both set to false. I tried to set them both to true, but then printer halts even earlier, right after moving print head into the 1st measurement position. Bed does not even move up towards the probe.

Thanks

Edited 5 time(s). Last edit at 04/11/2022 05:12PM by lmcbmai.

It appears you have tested endstops maybe missed something in the firmware.
Post your configuration.h an configuration_adv.h will take a quick peek

---

Computer Programmer / Electronics Technician

Here are my configuration files.

Thanks

I don't think it is related but still want to mention just in case - I also have an issue reported here [github.com] If I leave firmware microSD card in SKR2 the board reboots on its own every 2-3 minutes.

Thanks

Quote
lmcbmai
I have z-probe of my own design with optical sensor and electronic circuit identical to the circuits of X, Y and Z end-stops.

My Probe hardware has electronic circuit identical to the circuits of X, Y and Z end-stops as well, though in my firmware Need to enable the following.

#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
#define FIX_MOUNTED_PROBE

---

Computer Programmer / Electronics Technician

Fixed the issue by increasing #define Z_CLEARANCE_BETWEEN_PROBES from 5 to 10.

Probe would trigger at Z=4.08. NOZZLE_TO_PROBE_OFFSET for Z was set to 3.7 and with clearance 5 the following condition 4.08 > -3.7+5 was causing early_fail to become true in line 607 of probe.cpp

 early_fail = (scheck && current_position.z > -offset.z + clearance); // Probe triggered too high?

Z-offset will need tuning but that should not be a problem.

Roberts_Clif many Thanks for your help!