Duet 3 BLTouch probing issues
-
should i change it back to 3 point to try to figure this out?
-
I would change back to 3 points.
Just make sure they're in the same order as your M671. So front left, front right and rear middle -
with the 3 point i still get this:
G32
Leadscrew adjustments made: -5.000 -5.000 -5.000, points used 3, (mean, deviation) before (-5.000, 0.000) after (-0.000, 0.000) -
Can you post your homeall and homez file?
-
homez:
; homez.g
; called to home the Z axis
;
G91
G1 Z5 F800 H2
G90
G1 X182 Y118 F2400
G30
G1 Z2 F200
homeall:
M98 P"homex.g"
M98 P"homey.g"
M98 P"homez.g" -
I can't see anything in there that would cause the issue.
Could you reboot the board and run the probing again?
Could you also post the updated bed file? -
Updated bed.g:
M561 ; clear any existing bed transform
;G1 Z5 H2
G28 ; home
G30 P0 X2 Y2 Z-99999
G30 P1 X2 Y229 Z-99999
G30 P2 X240 Y116 Z-99999 S3
G1 X0 Y0 F5000 ; move the head to the corner (optional) -
Rebooted, ran g32:
G32
Leadscrew adjustments made: -5.000 -5.000 -5.000, points used 3, (mean, deviation) before (-5.000, 0.000) after (-0.000, 0.000) -
-
@Vampora said in Duet 3 BLTouch probing issues:
G31 X-30 Y0 Z0.75 P25 ; Set the offsets for the bltouch
change to P1000
P25 could be triggered by interference. -
@Veti said in Duet 3 BLTouch probing issues:
@Vampora said in Duet 3 BLTouch probing issues:
G31 X-30 Y0 Z0.75 P25 ; Set the offsets for the bltouch
change to P1000
P25 could be triggered by interference.No change
G32
Leadscrew adjustments made: -5.000 -5.000 -5.000, points used 3, (mean, deviation) before (-5.000, 0.000) after (-0.000, 0.000) -
I just want to make sure..... does anyone think it is the bltouch not being v3.1? I'm debating ordering one since I don't have one, but my gut tells me that is not the issue.
-
@Vampora said in Duet 3 BLTouch probing issues:
M558 P9 C"^io7.in" H5 R1 F120 T6000 A5 S0.02 B1 ; Define the bltouch input on io7.in
can you change the H5 to H6 and see if the result changes?
-
I actually just tried bumping it to 10 and this is what I got.
It just changes everything to -10 instead of -5
M98 P"0:/macros/Probe_Test"
G32 bed probe heights: -10.000 -10.000 -10.000 -10.000 -10.000 -10.000 -10.000 -10.000 -10.000 -10.000, mean -10.000, deviation from mean 0.000 -
this suggests there is a problem with your bltouch.
how many probing of the bed does it actually do when you run the macro?
-
It does 10
-
is there an error in the console?
this suggest that the bltouch is already triggered.
whats the z value in the ui? -
What I don't understand is the probes work just fine on my other railcores with duet 2 boards.
The first time it probes z it will set the z to 0.75 which is the same as my offset. The next time it probes it will say -4.25, and the 3rd will also say -4.25
When the command is given to raise to Z5 it says 5.75.
Would a video help shed light on it at all?
I usually do get random sporadic errors saying that say:
G29
Error: Z probe was not triggered during probing move -
This post is deleted! -
this suggests that there is a wiring problem. maybe a bad crimp on the extension cable.
