Do you have another printer you can use to reprint the lower orion mount? I have made some changes to it which I believe will improve repeatability and mechanical reliability.

I haven't a chance to test properly but if you want to give it a shot, you are welcome to.

I'm using red 40-A-L o-rings on the bottom of the piezo, with about 20% compression by tightening the 4x mounting screws. I've modified the mount so that the o-ring compression is enough to keep the hotend steady but the contact on the peizo is much lighter than before.

Reduced the height and diameter of those bosses so they only located the o-rings.

Reduced the height of the center ring to match about 20% compression on the o-rings.

Tighten evenly until the centre ring is touching the piezo. You should still have a rigid mount but with 0.2-0.5mm compression when tapping.

Here is the .stl, make sure you print in 0.1mm layer height or similar.
0_1537990342746_PiezoOrionRemix.stl

These are the o-rings:

[http://www.wasdkeyboards.com/index.php/products/keyboard-accessories/cherry-mx-rubber-o-ring-switch-dampeners-125pcs.html](link url)

I will hopefully be able to spend some time testing it in the next few weeks but for now if anyone is able to share their thoughts that would be very helpful.

I don't know anything about that C parameter in M558 but from what I can see in the docs, it's not needed for P9.
Your G31 also doesn't look correct. X0 Y0 offset would only be for a peizo type probe.
I didn't even know you could buy the duet 3 yet, I'm trying to make sense of the wiring diagram. Do you need to use one of the IO_# for the probe? is that why your using "C"io1.in""

Here is my setup for my BLtouch on Duet2 wifi, probably of no use to you though

; Endstops
M574 X1 Y2 S1                          ; Set active high endstops
; Z-Probe
M574 Z1 S2                             ; Set endstops controlled by probe
M558 P9 H5 F2000 T2000 X0 Y0 Z1        ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X20 Y0 Z1.383 P25             ; Set Z probe trigger value, offset and trigger height
M557 X20:140 Y20:140 P3:3              ; Define mesh grid

I just gave it a quick test and can confirm this has made a substantial improvement. I'm currently in the middle of moving house but will definitely spend some more time testing when I can. There are a few other improvements to be made when I get the time. Compression when tapping lightly is actually much less than 0.2mm, I would say 0.05-0.1mm depending on how tight the screws are.

Yeah G31 should have the offset in X and Y which is the distance in mm from the centre of the nozzle.

Are you able to get the probe to deply when doing a G30?

@joergs5

Thankyou, although my graphics drivers were up to date, I reinstalled chrome which solved the issue.

I did infact have M106 P1 S255 in my starting gcode which is now removed. Nothing in ending script or start.g/stop.g

Removing it from my starting script solved the problem, Thanks mate!

Yeah G31 should have the offset in X and Y which is the distance in mm from the centre of the nozzle.

Are you able to get the probe to deply when doing a G30?

I don't know anything about that C parameter in M558 but from what I can see in the docs, it's not needed for P9.
Your G31 also doesn't look correct. X0 Y0 offset would only be for a peizo type probe.
I didn't even know you could buy the duet 3 yet, I'm trying to make sense of the wiring diagram. Do you need to use one of the IO_# for the probe? is that why your using "C"io1.in""

Here is my setup for my BLtouch on Duet2 wifi, probably of no use to you though

; Endstops
M574 X1 Y2 S1                          ; Set active high endstops
; Z-Probe
M574 Z1 S2                             ; Set endstops controlled by probe
M558 P9 H5 F2000 T2000 X0 Y0 Z1        ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X20 Y0 Z1.383 P25             ; Set Z probe trigger value, offset and trigger height
M557 X20:140 Y20:140 P3:3              ; Define mesh grid

Solved: It was my Gcode that was changing the fan because I was using P0 for the hotend fan when I should have been using P1. M106 in the gcode controls P0 by default.

Solved: I wired up as per the second diagram since I have a new revision of the Duet WIFI so the z probe in is ok with 12v

Shouldn't L255 be forcing my hotend/heatsink fan to 100% minimum speed? It keeps running at weird ranges for each print.

The fans seems to be running at 100% despite the displayed value though.
It's a genuine E3D 12v fan and I'm getting 11.9v while printing.

; Fans
M106 P1 S0 I0 F255 H-1 C"Part Cooling"      ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P0 S1 I0 L255 F255 H1 T40 C"Hotend"    ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

What are you trying to achieve by retracting the nozzle? Interesting idea but I can't see the purpose.

Yes, my board is rev 1.04b.

So i still need to add a 10k resistor regardless of whatever that is in the diagram?

I'm converting one of my Printrbots to a Duet 2 wifi and the last thing to do is the Z probe.
I've read through the docs and want to clarify some things so I don't fry another board like I did last year.

My probe is a PNP LJ12A3-4-Z/BY, the diagram shows what I think is a resistor between the GND and signal wire. Is this an inbuilt pull up resistor or do I still need to add one if I go for the second option described?

Ok so I ran G29 another 5 times with the bed and hotend off and still got an incrementing error as before.

Changed the probing speed to F100 as suggested and this has solved the problem, have also changed to P25 from P10 in the G31 line.

Thanks for your help.

New lines:

M558 P9 H3 F100 T6000    ; Set Z Probe to type Switch or Digital output where Z probe connector is used.
G31 X20 Y0 Z1.35 P25     ; Set Z probe trigger value, offset and trigger height

Hi dc42,

Thanks for the reply, yes I can confirm I ran nothing but G29 in between each one, the last one I ran M561 and then G29.

My hotend was at 215c and bed at 50c at each one, I'm wondering if my new probe is too close to the hotend and the cause is EMI. I've read some vague mentions of this from a few google results.

I will test again tomorrow night with a cold hotend and report back.