@tcamguil said in [3.6.0-rc.2] Z-probe hits bed and U not moving running Mesh:

;Kliky L M558 P8 C"10.io0.in" H2:0.25 F1200:120 T18000 K1 R0.0 A15 S0.005 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X42.00 Y0.00 Z-25.000 K1 ; set Z probe trigger value, offset and trigger height ... ;Kliky R M558 P8 C"11.io0,in" H2:0.25 F1200:120 T18000 K1 R0.0 A15 S0.005 ; set Z probe type to bltouch and the dive height + speeds

Do you have one Klicky probe, or two? You seem to be defining two, on different IO inputs. Or is it the same Klicky, but it depends which tool head picks it up?

You have K1 set as the probe number for both probes, so most likely only one of them is actually being configured; the second effectively overwrites the first, so when the 1st toolhead (using the CAN '10' board) picks it up, it's looking on the wrong input for the probe response. Same for G31. Send M558 K# to check what probes are defined. Use a different K number for each probe. I don't know which probe number you are using in your 'pickupprobe.g' etc macros, but you could pass a parameter to the macro based on the tool number.

As far as I'm aware, the mesh should be applied to both tools. Please post your full config.g, maybe it's a config issue.

There is an issue running mesh probing on the U axis, it has been reported before, and your third issue sounds similar to this: https://forum.duet3d.com/topic/37165/issue-with-szp-on-secondary-idex-toolhead

Ian

@dwuk3d this particular bug was new in 3.6.0-rc.1.

Programming Z probes connected to expansion boards is not yet supported. For now you need to temporarily connect the Smart Effector to the main board if you want to change its sensitivity. I've logged this issue: https://github.com/Duet3D/RepRapFirmware/issues/815

dc42 created this issue in Duet3D/RepRapFirmware open Support programming Smart Effector sensitivity when the effector is connected to an expansion board #815

@Cognirit we've also integrated the scanning Z probe into our new Revo Roto Tool Board.

@o_lampe said in "Cat whiskers" sensor as Z-probe?:

@arhi
It only makes sense to spend more money than a BLTouch would cost, when the result is equal or better.

To me it would make sense investing time if it would solve a problem that exist and is not solved. TBH I don't see what unsolved problem this could solve except to work as underbed probe. ATTM I don't know of reliable underbed probe. Probing from the top, I doubt it can have smaller footprint than some piezo/bltouch/easytouch/.. sensor .. and as for precission and repeatability a simple microswitch is "good enough" so

but a real winner would be the heatsink-necklace as it has zero offset and requires less force than piezos.

I can't visualize how would this work

can you please share your config? this can help me too