IR stop backwards?

quixotic120

Hello,

I have a dc42 differential IR stop hooked up to a duet wifi 1.02. Default P value/z-probe reading is 1000 (or over) and when I trigger it it drops to ~464. Wiring is verified, LED flashes 4 times on start, and LED flashes when triggers. My understanding is that this indicates it is working correctly, which it appears to be doing, just backwards.

M558 P1 I1 H10 R0.1 F1800 T3000 A1 B1 ;IR is what im using with a P threshold of 500 in my G31.

I intend to use it as a probe only, i have a mechanical switch z stop as well. However, because of this behavior duet reports triggered at start of probing move. It worked before without issue so I assume I have something incorrect software wise?

firmware 2.01 if that matters. Thanks!

Jacotheron

My not triggered probe reading is 0, and then goes up to over 500.

Under your Z-Probe settings, what do you have there? Full set of related settings.

Mine is:

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P1 H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.7 ; Set Z probe trigger value, offset and trigger height

I may be wrong about this, but as I see it, an axis end can/should only have a single endstop type enabled. If one have 2 separately controlled motors for the same axis, each may have their own endstop.

dc42

Remove the I1 parameter from the M558 command.

quixotic120

removing I1 fixed it, thanks so much!!