RRF 3.0RC1 Z Homing Issue (Analogue Mode)

tekkydave

I think there might be an issue with z homing using an analogue probe (type P1 in M558).
I have a piezo probe using the Precision Piezo Universal PCB V2.85 which has both analogue and digital outputs.
Defined as follows

; Analogue Mode
;M558 P1 C"^!zprobe.in" R0.5 H3 F360 T9000 A5 S0.03   	; P1 = Analogue mode (V36)
;G31 X0 Y0 Z-0.1 P530                      		; X, Y, Z offsets, P530 = trigger threshold 	(V37)

; Digital Mode
M558 P8 C"^!zprobe.in" R0.5 H3 F240 T9000 A5 S0.03   	; P8 = Digital mode (unfiltered)		(V35)
G31 X0 Y0 Z-0.1 P100                      		; X, Y, Z offsets, P100 = debounce interval 	(V32)

I have both modes setup for testing and can easily switch between them.

The analogue mode works fine on 3.0beta12 despite the 1/3 slowdown, which I have mentioned in another post.
I upgraded to 3.0RC1 this morning and getting lots of "Error: Z probe was not triggered during probing move" errors. It seems to do the first probe which triggers ok, however the 2nd probe always stops about 1mm short and the error is reported. This is the same regardless of using homeall or homez and trying different dive heights, trigger thresholds etc. I have also downgraded back to 3.0beta12 and the fault disappears. It reappears on upgrading to 3.0RC1 again.

Here are the relevant homing files.
homeall.g

;------------------------------------------------------------------------------------------
;   X and Y Homing
;------------------------------------------------------------------------------------------
G91                    ; relative positioning
G1 Z5 F360 H2          ; lift Z relative to current position
G1 H1 X-320 Y320 F4000 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-320 F4000      ; home X axis
G1 H1 Y320 F4000       ; home Y axis
G1 X5 Y-5 F1800        ; go back a few mm
G1 H1 X-320 F360       ; move slowly to X axis endstop once more (second pass)
G1 H1 Y320 F360        ; then move slowly to Y axis endstop
G90                    ; absolute positioning
;------------------------------------------------------------------------------------------

;------------------------------------------------------------------------------------------
;   Z Homing
;------------------------------------------------------------------------------------------
G1 X150 Y150 F9000      ; go to centre of bed
G30                     ; home Z by probing the bed
G1 Z5 F360              ; uncomment this line to lift the nozzle after homing
;------------------------------------------------------------------------------------------

homez.g

G91                 	; relative positioning
G1 Z3 F360 H2       	; lift Z relative to current position
G90                 	; absolute positioning
G1 X150 Y150 F9000 	; go to centre of bed
G30                 	; home Z by probing the bed


; Uncomment the following lines to lift Z after probing
G91                 	; relative positioning
G1 Z3 F600          	; lift Z relative to current position
G90                 	; absolute positioning

I will post full config.g or any other info required.
I have reverted to using digital mode for now but I would prefer to use analogue mode as it avoids having to fiddle with the tiny, fragile pots on the PP PCB.
Cheers
Dave

tekkydave

Not sure if relevant but I have 3 independent z motors with 2 of them on a Duex2.
Cheers
Dave

tekkydave

My config.g
config.g.txt

dc42

I've put this on my list to look at.

dc42

Does the digital mode still work in 3.0RC1?

tekkydave

@dc42 Yes. No problems with digital mode.

dc42

I think I have found the reason for the problem, although I don't have a printer using an analog probe at present so I can't test the fix. Please try the Duet2CombinedFirmware.bin file at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

tekkydave

I'll test it asap. Will be tomorrow now.

tekkydave

@dc42 said in RRF 3.0RC1 Z Homing Issue (Analogue Mode):

I think I have found the reason for the problem, although I don't have a printer using an analog probe at present so I can't test the fix. Please try the Duet2CombinedFirmware.bin file at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

Yes, that has solved the problem. Many thanks and a Merry Christmas