Prusa Mk2.5S Pinda V2 Probe issue

nat495

Hi,

I have converted an old Prusa MK2.5S to the Duet 3 Mini5+ Ethernet from stock. I was following the CNCkitchen guide and I am having difficulties with the PindaV2 probe. When I run the Z probe trigger height. The G30 S-1 command triggers an "Error: Probe was not triggered during probing move". I notice that in the user interface the probe triggers, going from 0 to 1000 as the probe approaches the bed. The probe light also turns off when it hits 1000.

In addition, when I try to run G32, the printer will do the first 3 probe sections and then stop at the 4th with multiple errors: Error: SetPositions called when DDA ring not empty
Error: Probe already triggered at start of probing move

Any thoughts on how to solve these issue?

Firmware: FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet 3 Mini5plus Ethernet FIRMWARE_DATE: 2022-11-30 19:41:16

Thank you.

config.g

droftarts

@nat495 Here's you config for the probe

; ##### Z-Probe Settings for PINDA 2
M558 P5 C"io2.in" H1 F1000 T6000 A3                      ; Prusa PindaV2 Endstop
M308 S2 P"temp2" A"Pinda V2" Y"thermistor" T100000 B3950 ; Prusa PindaV2 Thermistor
;G31 P1000 X23 Y5 Z1.4 S21 H2 T0.02                      ; Nozzle offset - Powder Coated Sheet with temperature compensation (0.02mm/°C)
G31 P1000 X23 Y5 Z1.1 S21 H2 T0.02                       ; Nozzle offset - Smooth Sheet
M574 Z1 S2                                               ; Set Z axis endstop, controlled by probe
M557 X24:228 Y6:210 P5                                   ; Define mesh grid for probing
M376 H5							 ; Fade height 5mm

Try setting G31 P parameter to P500. Also set M558 P parameter to P8 (unfiltered switch, faster response).

Ian

nat495

@droftarts Hi Ian,

Thank you for responding. I have made the following changes to my config. However, I'm still having some odd behavior. Now I'm noticing that when I run G30 S-1 close to the bed when the probe is already triggered I get the error Error: Probe already triggered at the start of probing move. When I run the same code a bit further from the bed and the trigger is not already triggered, I get the error: Error: Probe was not triggered during probing move. The Z-Axis will move until the probe triggers and then stops.

Running G32 now gets the following errors and does not complete:
G32
Error: SetPositions called when DDA ring not empty
Error: Probe already triggered at start of probing move
Error: Probe already triggered at start of probing move
Error: SetPositions called when DDA ring not empty
Error: Probe was not triggered during probing move
Error: Probe was not triggered during probing move

Thanks,
Nathan

; ##### Z-Probe Settings for PINDA 2
M558 P8 C"io2.in" H1 F1000 T6000 A3              				; Prusa PindaV2 Endstop
M308 S2 P"temp2" A"Pinda V2" Y"thermistor" T100000 B3950      		; Prusa PindaV2 Thermistor
;G31 P500 X23 Y5 Z1.4 S21 H2 T0.02                         			; Nozzle offset - Powder Coated Sheet with temperature compensation (0.02mm/°C)
G31 P500 X23 Y5 Z1.1 S21 H2 T0.02                                    			; Nozzle offset - Smooth Sheet
M574 Z1 S2                                                 			; Set Z axis endstop, controlled by probe
M557 X24:228 Y6:210 P5                                    			; Define mesh grid for probing
M376 H5																; Fade height 5mm

jay_s_uk

@nat495 best downgrade to 3.4.4. The DDA issue seems to only occur in 3.4.5

nat495

@jay_s_uk

Thank you. Reverting the firmware solved the issue. The printer is printing a test print now.

Thank you.

dc42

@nat495 the issue with firmware 3.4.5 on the Duet 3 Mini is resolved. Please see https://forum.duet3d.com/topic/30814/homing-issues-with-rrf-3-4-5.