I really tried to fix it myself it on my own.

[A Former User]

This post is deleted!

[dc42]

@TOFUATSU a few questions:

1. What happens when you try to home Z?
2. If you send M401 does the pin deploy, and when you send M402 does it retract?
3. If so, then after you send M401 to deploy the pin, what is the Z probe reading shown in Duet Web Control? Does it change if you push the pin up?

[TOFUATSU]

@dc42

All that happens when I run the homez.g is the bed moves down 5 mm then I get a G28 Z failed error.

The pin deploys with M401 and retracts with M402: The Z-probe reading never changes

I just changed the line in my Confing.g from
M557 X15:215 Y15:195 S20 to
M557 X15:215 Y15:195 P12

I copied and pasted the homez.g file thet Herve_Smith just supplied above. Now everything looks like it's gonna work. The bed moves down a bit, the pin deploys. The bed moves up, hits the pin on the CRTouch and pushes it up and keeps going until the bed crashed into the nozzle.

This is progress.

Thank you for the help so far.

[A Former User]

This post is deleted!

[TOFUATSU]

@Herve_Smith. I checked continuity, my crimps are sufficient.

I tried that homez and pushed the pin while it was traveling. It didn’t stop it.

There is no reading for the probe on the web interface.

I also noticed that after the M401 command, if I press the pin in, I cannot get it to redeploy with another M401. I tried to send M402 then M401. M280 does nothing either. I have to reset the firmware to get it to deploy again.

[A Former User]

This post is deleted!

[TOFUATSU]

@Herve_Smith

Duet. - CRTouch. - Wire
3.3v - none. - none
IN - OUT - Blue
GND - GND - Red and White
OUT - Control - Yellow
+5V - +5V - black

[A Former User]

This post is deleted!

[TOFUATSU]

@Herve_Smith off to Microcenter then… should I try a different io on the board?

[dc42]

@TOFUATSU said in I really tried to fix it myself it on my own.:

The Z-probe reading never changes

Yes, but what is the Z probe reading? is it 0, 1000, or something else?

The reading never changing suggests either a faulty CRTouch, a bad connection (e.g. bad crimp) in the wire from the CRTouch output to the Duet, a problem with that input on the Duet, or an error in configuring the sensor on the Duet.

If it's a genuine UK-manufactured Duet then the input will have been tested by our ATE (automated test equipment). So:

• Check that you have continuity in the blue wire from the CRTouch OUT pin to the Duet IN pin. A bad crimp connection is the most likely fault. If the crimp connection is open circuit then you will get a Z probe reading of 1000 all the time. OTOH if the pin is shorted to ground, you will get a reading of zero all the time (although this could also mean that the pullup resistor on the Duet is missing or open circuit).
• Check that you have plugged the connector into the IO3 port, not some other port.

[TOFUATSU]

@dc42

Thank you so much!

Solved

The CRTouch was fried and my code was bunk.

I’ll dedicate the first Benchy to you guys