@jay_s_uk said in Endstop with duet3:

stop.g

Make sure to include M0 at the end of your job so that stop.g is called.

I wanted to try installing again same firmware and updates before maybe going to RRF3.
No idea why, but it has solved my issue.

Thank you for your answers and time.

I solved the Problem 😄

You have to PullUp the Pin than it will work.

@Phaedrux Thanks 🙂

Hi ! I know you've solved the problem you initially asked about. I'm wondering it you could give my some info on how tricky putting a Duet board on a WASP delta was? I have a WASP 60100 (build 2017) and would love to upgrade it with a Duetboard and maybe a E3D Volcano hotend. But, I'm not really sure what I'm getting myself into 🙂 Would you mind me asking a couple of newbie questions about your process?

maybe the 5mm requirement makes this possible by means of a trigger

try creating a M581 E0 T2 trigger for E0 endstop, and in the /sys/trigger2.g file do

that should make it move 5mm, and if the trigger condition is still asserted then it should run the trigger again, and again. You may have to experiment with the S parameter for rising or falling edge of the trigger to get the desired effect.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M581_Configure_external_trigger

@dc42 said in PINDA Z-Probe Configuration:

The reading needs to be around 0 when not triggered (no metal under the probe) and 1000 when triggered. Try removing the i1 parameter from your M558 command in config.g.

well, that did the trick. Thanks a lot.

It's not as easy to work with Duet, being used to Marlin for years...

Thanks to all

Just deleting the R does the trick. I read somewhere that on newer boards the defaults are OK.