Hm, for some reason it seems to work now, even though I didn't change anything.
I feel like perhaps the DWCs notification system is a bit bugged sometimes,
but I keep you updated in case it comes up again

Hey there!

While my printer is working just fantastic,
I found that the G30 Z-probe homing command can take ages to home,
especially after a print when the bed is far away from the nozzle.

So I tried to write a two pass homing script for the z-axis,
where I first do a quick first pass with G1 S1 Z-160 F600, lift the nozzle a bit
and then do the G30 pass. However, even though I lifted the nozzle 5, or even 10 millimeters,
it always tells me that the "Z probe is already triggered at start of probing move".
It's also interesting that the title of the error is "G28 Z" instead of "G30".

Here's my complete homez.g script:

; homez.g
; called to home the Z axis
;
G91 			; relative mode
G1 Z4 F200 		; raise head 4mm to ensure it is above the Z probe trigger height
G90 			; back to absolute mode
G1 X100 Y100 F6000 	; put head over the centre of the bed, or wherever you want to probe
G1 Z-160 S1 F600	; do quick first homing pass
G1 Z10 F600		; lift up sensor a bit for second pass			
G30 			; lower head, stop when probe triggered and set Z to trigger height

G1 Z5 F600              ; lift Z relative to current position

I'm sorry for bringing this topic up again, but since it helped me out with the same exact problem already, I felt like I don't need to make a whole new post for it. So thanks for that already!

At least for me, this "z-probe configuration as a microswitch instead of a z-probe" was generated by the RRF configuration tool, and as I pretty much just got my board and didn't have a clue about how everything works, I absolute didn't suspect this tool to be the culprit here.

The thing is, when you use the configuration tool, you have a few options for how the Z-probe is going to work, just like you have different modes to set with M558. But I couldn't see the direct connection between the modes and the options presented there.

Since I have a NPN inductive sensor that outputs either 1 or 0 and since I basically used it as a "microswitch" in Marlin, on the Z endstop pins, I felt like setting it up as a "Switch" as the tool calls it would be the best idea. Turns out, the generated homez.g and homeall.g are both setup as if it was an actual switch, using G1 to home instead of G30.

I don't know how much influence you guys have on the RRF config tool, but I think as a new Duet user it is a very handy tool to use and it should be cleared up somehow what the "Switch" option does, or an actual "inductive/capacitive probe" option should be added as well to make it clear.

Just my 2 cents as a Duet newbie. Aside from that, this board is absolutely fantastic!