FT_MOTION: Disable FT-MOTION for homing and probing for Biqu Microprobe

[narno2202]

Description

As the 2 workaround found, are far away from universal. Disable FT_MOTION for homing and probing when a Biqu Microprobe V1 or V2 is present.

Requirements

Benefits

Allow more printers to use FTM and Biqu Microprobe

Configurations

Related Issues

Need feedback and test

[thisiskeithb]

We should be fixing the actual issue instead of adding more sanity checks/workarounds.

[narno2202]

@thisiskeithb ,
I totally agree, but for now I just found those two workarounds to use Biqu Micorprobre with FTM. Do you have the possibility to test this probe? I found strange to solve the failure by lowering the Z motor current : hardware related?.

[thisiskeithb]

Do you have the possibility to test this probe?

I have a BIQU Hurakan with a MicroProbe V2, but it's not easy to test right now since I have several other machines out on the bench for repairs/testing/upgrades. It'll take me a bit to get to it.

[thisiskeithb]

After some testing with a BIQU Hurakan (Manta M4P, TMC2209s, MicroProbe V2) using 3d7ac16, here's what I found:

Enabling or disabling ENDSTOP_INTERRUPTS_FEATURE with FT_MOTION enabled still causes immediate probe trigger as Z homing starts & causes homing to fail.

Halving Z homing speed from 800mA down to 400mA (even testing down to below 300mA), with or without ENDSTOP_INTERRUPTS_FEATUREstill causes immediate probe trigger as Z homing starts & causes homing to fail with FT_MOTION enabled.

There are no homing or probing failures (with or without ENDSTOP_INTERRUPTS_FEATURE) with FT_MOTION disabled or not compiled in.

This sanity check is not a fix and should be removed / moved to FT Motion's docs as a possible troubleshooting step and not a strict requirement:

Marlin/Marlin/src/inc/SanityCheck.h

Lines 1398 to 1400 in 3d7ac16

	#if ENABLED(FT_MOTION) && DISABLED(ENDSTOP_INTERRUPTS_FEATURE)
	#error "BIQU Microprobe requires ENDSTOP_INTERRUPTS_FEATURE with FT_MOTION."
	#endif

Same goes for the changes introduced in this PR. Neither work for my hardware.

More testing needs to be done on wider hardware so we don't end up with overbearing sanity checks or better yet, do as I suggested in #27302 (comment) and temporarily disable FT_MOTION during homing/probing.