A simple workround for PrusaSlicer is to add a custom gcode to the Printer Settings:
DBot, Duet WiFi.
I've just removed the ^ too and as expected - makes no difference.
Correct setup for analog is
M558 P1 C"zprobe.in" R0.5 H3 F360 T9000 A5 S0.03 ; P1 = Analogue mode G31 X0 Y0 Z-0.1 P530 ; X, Y, Z offsets, P530 = trigger threshold
and for digital:
M558 P8 C"^!zprobe.in" R0.5 H3 F240 T9000 A5 S0.03 ; P8 = Digital mode (unfiltered) G31 X0 Y0 Z-0.1 P100 ; X, Y, Z offsets, P100 = debounce interval
No bug as far as I can tell. I've just tested it on my Duet2 using DWC V2.0. It just seems very fussy about where you click to start the selection. If you start in the margin area to the left of the first character the selection doesn't work. If you are spot on the first character it works as expected. It is sometimes easier to select backwards then you don't need to be so accurate with your mouse positioning.
I can see the sense in the slowdown for other analog sensors but not for piezos. The analog output is constant until the nozzle makes contact with the bed.
Can I suggest 2 possible solutions:
If you haven't already done so try adjusting the nozzle height whilst the first layer is printing using the 'Z Babystepping' controls on the DWC Status page. If you can find a height that works then adjust the G31 Z value in your config.g by that amount.
If it helps I have the universal board v2.85. Here are the analogue and digital settings that work with my Duet Wifi. Use one or the other. I use the analogue mode to avoid having to fiddle with the tiny pots on the PCB. You also need to connect to the correct pin (A or D) on the PCB according to which mode you use.
; Analogue Mode M558 P1 C"^!zprobe.in" R0.5 H3 F360 T9000 A5 S0.03 ; P1 = Analogue mode G31 X0 Y0 Z-0.1 P530 ; X, Y, Z offsets, P530 = trigger threshold ; Digital Mode M558 P8 C"^!zprobe.in" R0.5 H3 F240 T9000 A5 S0.03 ; P8 = Digital mode (unfiltered) G31 X0 Y0 Z-0.1 P100 ; X, Y, Z offsets, P100 = debounce interval
You will need to adjust the Pxxx in the G31 to suit your printer if using analogue mode. A good starting point is 5 above the value in DWC when not triggered.
Also be aware that when using analogue mode the probe will home at 1/3 speed. @dc42 has said this will change at some point in a future RRF release so piezo probes home at full speed.
@gloomyandy I bought one from that seller. The board seems to indicate a LIS3DSH but the chip has 3CH on it which is a LIS3DH. Have you connected it up & what does the Duet report?
I bought two boards from different sellers. One should be a LIS3DH and the other a LIS3DSH. They look identical to me and both have 3CH on the chip.
The only difference is one has OED26 after the 3CH and the other OED27.
I have only connected the OED26 to the Duet so far.
They both look like this on the back:
I'm assuming that the Duet will report the correct chip.
Edit: I have soldered a connector to the other one (OED27) and tested it with the Duet. Also get same message as the other one
Accelerometer 0 type LIS3DH with orientation 14 samples at 1344Hz with 10-bit resolution, SPI frequency 2000000
Further tests connecting the device to an Arduino confirm it is a LIS3DH as it returns device id = 51 (0x33). So despite it being advertised as a LIS3DSH and the pcb indicating that it is - well it isn't. So be careful when buying these folks and check the code on the chip:
3CH = LIS3DH
DSH = LIS3DSH
I have ordered another one from the link given by @dc42 above. Let's see what turns up
@phaedrux I can't disagree with the number of parameters on M558 but equally I can't understand why we have the Z lift speed being controlled by a parameter intended for XY movement.
In theory I could have my Z max speed set to a crazy value but it not affect any other movements as they all have their own speeds specified. Only M558 will cause issues when it tries to lift the probe at say 150mm/s.
Sure every printer should have it's limits set up correctly but for me it's an inconsistency in the probing process that needs looking at.
@fcwilt Just tested it by changing my M558 from:
M558 P1 C"zprobe.in" R0.25 H3 F360 T9000 A5 S0.03
M558 P1 C"zprobe.in" R0.25 H3 F360 T540 A5 S0.03
and the lift speed went down from 10mm/s (z max speed) to 9mm/s (540mm/min)
so yes - it is using the T param to control the Z speed.