Best Z Probe for Duet 3 Mini 5+

tecno

@zapta said in Best Z Probe for Duet 3 Mini 5+:

@tecno, have you used IR with a PEI sheet (e.g. 1mm), if so, what was your experience?

I use PrimaCreator FlexPlate PEI and I usually have to baby step printhead down a bit.
Using backside to print PETG usually no babystep.

No mechanical probes for me anymore as I have had my share of big problems with that shit.

zapta

After reading this thread I decided to replace the Z probe on my printer with a stowaway microswitch kind, so built a Voron Clicky Probe from a swtich and magnets I had and its seems to work quiet well. It is definitely simpler than the standard Voron V2.4 z stop + induction probe arrangement and it measure the actual top surface which I prefer. Also added gcode to the pick/drop macros to verify that the probe is actually picked/dropped as expected for extra safety.

What is a good way to quantify the accuracy or consistency of a probe?

A Former User

This post is deleted!

zapta

@arnold_r_clark said in Best Z Probe for Duet 3 Mini 5+:

with a zero/zero offset to the nozzle

Can you explain this? Do you mean X offset? Y offset? Z offset? Something else?

CR3D

A lot of people use the CR-3D SupCRprobe... a temperature stabilized inductive sensor which works with extremely high repeat accuracy

https://www.cr3d.de/kategorie/elektronik/sensorik/

here e.g. in the C1mini with Duet 3 Mini 5+

pfn

@zapta This is what I do:

M98 P"k/probe-attach.g"
G1 X100 Y100 F18000
G30
G30 P0 X100 Y100 Z-9999
G30 P1 X100 Y100 Z-9999
G30 P2 X100 Y100 Z-9999
G30 P3 X100 Y100 Z-9999
G30 P4 X100 Y100 Z-9999
G30 P5 X100 Y100 Z-9999
G30 P6 X100 Y100 Z-9999
G30 P7 X100 Y100 Z-9999
G30 P8 X100 Y100 Z-9999
G30 P9 X100 Y100 Z-9999 S-1
M98 P"k/probe-detach.g"

If it isn't obvious, I too have a clicky probe (annex quickdraw in this case).

engikeneer

@pfn @zapta, you could even add attach/detach calls in between each of the successive G30's to test the repeatability of the pickup.

I have a similar test macro which does G1 moves between each probe to test for backlash affecting the probe etc

pfn

@engikeneer that's a really good idea, I should try that

zapta

@pfn said in Best Z Probe for Duet 3 Mini 5+:

If it isn't obvious, I too have a clicky probe (annex quickdraw in this case).

attach/detach, I called it picked/drop

Thanks, will give it a try, including attach/detach between each probing.

BTW, I do homing, auth leveling and mesh probing with hot bed, since it can also impact the results.

A Former User

This post is deleted!

PaulHew

My Euclid PCBs arrived today, in the UK.
Have everything ready apart from the magnets, unless I want to spend more on delivery than the magnets from USA.

I have run BLT originals on my RailCore / Voron2.4 and Ender3.
The RailCore struggles with back right corner with a BLT, nothing wants to stick to that area! Always too high.

Hoping the Euclid probe will alleviate that issue!

zapta

@pfn, I run 100 iterations of attach/probe/detach and got the message below

"G32 bed probe heights: -0.129, mean -0.129, deviation from mean 0.000"

Does it mean that I need to increase the Z value in my probe setting?

G31 K0 P500 X-2 Y19 Z9.1

Also, is there a way to get the 100 probing values or at least min and max?

echo "Home all"
G28

while iterations < 100
  ;echo "Probing " ^ {iterations}
  
  M98 P"/macros/clicky_pick"
  M98 P"/macros/z_current_low"
  M98 P"/macros/speed_probing"
  
  G30 P0 X127 Y106 Z-9999
  
  M98 P"/macros/speed_printing"
  M98 P"/macros/z_current_high"  
  M98 P"/macros/clicky_drop"

; ---------------
echo "Last probing"

M98 P"/macros/clicky_pick"
M98 P"/macros/z_current_low"
M98 P"/macros/speed_probing"
  
G30 P9 X127 Y106  Z-9999 S-1

M98 P"/macros/speed_printing"
M98 P"/macros/z_current_high"  
M98 P"/macros/clicky_drop"

echo "Clicky test done"

zapta

@arnold_r_clark said in Best Z Probe for Duet 3 Mini 5+:

The probe is not offset from the nozzle on either the X or Y planes, the switch is picked up from its dock and sits directly under the nozzle at a known distance below the nozzle hence Zero/Zero.

That's very neat. Thanks for the explanation. I thought that this is what you meant but didn't know how it can be designed.

pfn

@zapta your macro has a mistake it should be G30 P{iterations}

So you didn't get an aggregate result

The final G30 should be P100

Also, I'm a bit concerned, it says the probe result was 0.129mm lower than the homing probe. It could mean the mount is inconsistent.

With the correct P arguments, the result for G30 S-1 should list all probe values

zapta

@pfn, yes, you are right. Here it is after fixes. Not sure where the 0.109 offset comes from but my slicer is set to print at z offset of 0.1mm.

Is this a reasonable probe accuracy?

G32 bed probe heights: -0.120 -0.106 -0.110 -0.111 -0.114 -0.111 -0.110 -0.098 -0.111 -0.105 -0.100, mean -0.109, deviation from mean 0.006

var N=10

echo "Home all"
G28

while iterations < var.N
  echo "Iteration " ^ {iterations}
  
  M98 P"/macros/clicky_pick"
  M98 P"/macros/z_current_low"
  M98 P"/macros/speed_probing"
  
  G30 P{iterations} X127 Y106 Z-9999
  
  M98 P"/macros/speed_printing"
  M98 P"/macros/z_current_high"  
  M98 P"/macros/clicky_drop"

; ---------------
echo "Last probing"

M98 P"/macros/clicky_pick"
M98 P"/macros/z_current_low"
M98 P"/macros/speed_probing"
  
G30 P{var.N} X127 Y106 S-1 Z-9999

M98 P"/macros/speed_printing"
M98 P"/macros/z_current_high"  
M98 P"/macros/clicky_drop"

echo "Clicky test done"

pfn

@zapta the 0.1 comes from the probe location, I assume your homez is at a different location. So z=0 at your homing location results in an offset at this x/y

In terms of repeatability, it's pretty good. Bltouch advertises 0.005mm stdev. I got 0.002 on my ir sensor. without unlocking, I got 0.002 on the microswitch. Probing speed can also affect consistency, I normally probe with F100.

All things considered being under 0.01mm is good enough, unless you're pushing like 0.04mm first layer heights... babystep resolution is like 0.01mm at most (and more often 0.04 or 0.02mm)

zapta

Thanks @pfn, I will keep it then. I find this Clicky probe simpler than the Voron V2.4 stock end switch + inductive probe and so far it seems to be reliable, never missed a drop or pickup and the probe stayed in place when I turned the machine over to access the electronics.

BTW, since you mention speed 100, I reduced the M558 speed to F500:100 (was F120) and got slightly lower deviation from mean but I don't know if it's statistically significant.

G32 bed probe heights: -0.140 -0.141 -0.141 -0.151 -0.149 -0.140 -0.146 -0.136 -0.146 -0.143 -0.150, mean -0.144, deviation from mean 0.005

To answer the original question here, Duet Mini5+ and a Clicky probe work well for me.

pfn

@zapta lol, whoops, that was a typo, I meant I normally probe at F300.

Yeah, I'm not sure it's very different to warrant going slower. Don't get rid of the original voron endstop switch tho! Do this!

https://youtu.be/8P1tNT4el8Y

zapta

@pfn, I am using dual speed F500:100, I don't waste much time lowering the Z.

As for the video, that's a nice trick, having a fixed reference point that can home both the nozzle and the Clickey switch. Personally like minimalist systems so throw away whatever I can. I calibrate the Z probe offset with babysteps, setting initial value, than finding a good babystep distance and substracting it from the initial z offset. Once this is set, I do final adjustments, as needed, with the slicer's z offset which is easy to adjust.

As for the trick above, I think it's accurate only if the clickey and static switches trigger at exactly the same time. Otherwise you incur error base on the current travel locations of each of the two switches.

Anyway, I love my Clickey probe and thanks to the test you suggested I also know it's reasonably good.

sinned6915

@paulhew Thanks for your support!
There are many in the Railcore community that are VERY happy with it. From the mounts that we have designed and dock options. We have one that attaches to the corner of the extrusion if you don't have extra nuts in the extrusion channels.
Scan the QR code and enjoy! We are always available on the Discord channel too.