BLTouch Probe Won't Deploy
-
homex.g
; Voron. ; 0:/sys/homex.g ; Called to home the X axis via G28 X. ; 2020/10/24/20:00 G91 ; Set axes (not extruders) to relative positioning mode. G1 H2 Z5 F6000 ; Lift Z relative to current position. G1 H1 X355 F6000 ; Move quickly to X endstop (1 of 2 passes). G1 H0 X-3 F6000 ; Move away from X endstop. G1 H1 X10 F360 ; Move slowly to X axis endstop once more (2 of 2 passes). G1 H2 Z-5 F6000 ; Lower Z relative to current position. G90 ; Set axes (not extruders) to absolute positioning mode.
homey.g
; Voron ; 0:/sys/homey.g ; Called to home the Y axis via G28 Y. ; 2020/10/24/20:01 G91 ; Set axes (not extruders) to relative positioning mode. G1 H2 Z5 F6000 ; Lift Z relative to current position. G1 H1 Y360 F6000 ; Move quickly to Y endstop (1 of 2 passes). G1 H0 Y-3 F6000 ; Move away from Y endstop. G1 H1 Y10 F360 ; Move slowly to X axis endstop once more (2 of 2 passes). G1 H2 Z-5 F6000 ; Lower Z relative to current position. G90 ; Set axes (not extruders) to absolute positioning mode.
homeall.g
; Voron. ; 0:/sys/homeall.g ; Called to home all axes via G28. ; 2020/10/24/21:00 G91 ; Set axes (not extruders) to relative positioning mode. G1 H2 Z5 F6000 ; Lift Z relative to current position. G1 H1 X355 Y360 F6000 ; Move quickly to X or Y axis endstop and stop there. G1 H1 X355 F6000 ; Move quickly to X endstop and stop there. G1 H1 Y360 F6000 ; Move quickly to Y endstop and stop there. G1 H0 X-3 Y-3 F6000 ; Move away from X and Y endstops. G1 H1 X10 F360 ; Move slowly to X endstop once more. G1 H1 Y10 F360 ; Move slowly to Y endstop once more. G90 ; Set axes (not extruders) to absolute positioning mode. G1 X175 Y151.5 F6000 ; Move X and Y axes so the Z probe is at the center of the bed. M558 F600 H2 A1 ; Set Z probe. Feed rate: 600 mm/min. Dive height: 2 mm. Times to probe: 1. G30 ; Z probe quickly (1 of 2 passes). M558 F120 H5 A1 ; Set Z probe. Feed rate: 120 mm/min. Dive height: 5 mm. Times to probe: 1. G30 ; Home Z by probing the bed slowly (2 of 2 passes).
-
@charlie you may need to exchange the order or M950 and M558:
in the M950 documentation https://duet3d.dozuki.com/Wiki/M950 :
"M950 must come before any commands that refer to the device being created."
So M950, then M558 which uses the servo part of BLTouch.I am not sure about this. In the examples I know, M950 is first, M558 next, but the two commands don't have a reference to each other. But it's worth a try. M558 may expect to know the M950 values.
-
@fcwilt
That is correct. Homing just Z doesnt work.It also doesnt work if I use "Home All".
-
@charlie said in BLTouch Probe Won't Deploy:
@fcwilt
That is correct. Homing just Z doesnt work.It also doesnt work if I use "Home All".
OK let's take the homing code out of the picture.
Can you reset the printer and successfully home X and Y?
Frederick
-
@charlie a last additional idea: M208 has Z minimum 0 and the BLTouch starts at 3 mm height. It may be that it cannot probe below 0 because of M208. This was changed in 3.4 somewhere if I remember correct, but if you use 3.3 firmware, it may be a try to set the M208 Z limit below 0.
-
@fcwilt
Im assuming that "reset" means sending anM999
command, or powering off the duet. In that case, X and Y works wonderfully when I home them individually. Furthermore, the X and Y portions of the Home All function work as intended as well. -
@joergs5
Unfortunately, this did not fix the issue. I appreciate the attempt though! -
@charlie said in BLTouch Probe Won't Deploy:
@fcwilt
Im assuming that "reset" means sending anM999
command, or powering off the duet. In that case, X and Y works wonderfully when I home them individually. Furthermore, the X and Y portions of the Home All function work as intended as well.Great.
So with X and Y homed:
- move X and Y to center of the bed either by jogging or issuing G1 commands
- issue a G92 Z3 to force Z to be marked as homed (this allows jogging Z)
- jog Z to 3 mm off the bed (now the logical and physical Z positions are in sync)
- change to the DWC Console page
- issue a G30
Post what happens.
Frederick
-
@fcwilt
So I did this, but with one exception. I didnt jog the z to be 3mm off the bed, as I was concerned about crashing the nozzle.The probe did not deploy, and the error: "Error: Probe was not triggered during probing move" was displayed on the console.
-
@joergs5 said in BLTouch Probe Won't Deploy:
@charlie a last additional idea: M208 has Z minimum 0 and the BLTouch starts at 3 mm height. It may be that it cannot probe below 0 because of M208. This was changed in 3.4 somewhere if I remember correct, but if you use 3.3 firmware, it may be a try to set the M208 Z limit below 0.
Something odd happened that may help those smarter than I!
I issued an
M208 S1 Z-100
command in the DWC console (which is along the lines of what I believed you asked me to do). I then issued aG30
command. Please keep in mind that this was after I did what @fcwilt asked, which was to issue aG92 Z3
command.The print head seemed to move down around 3mm, and then the probe deployed.
-
I made a post but came back to find your new post.
I need to think.
-
-
@fcwilt
Here is the current Z Probe section of the config.g file, containing the M950, M558, and G31.; Z Probe M558 K0 P9 F120 H3 R0 T6000 A1 B0 C"0.io4.in" ; Set Z probe type. ; K (Z probe number): 0 (1). ; P (Z Probe type): 9 (BLTouch probe). ; F (Feed rate. Probing speed [mm/min]): 120. ; H (Dive height [mm]): 3. ; R (Recovery time [seconds]): 0. ; T (Travel speed [mm/min]): 6,000. ; A (Max number of times to probe each point): 1. ; B (Heaters): 0 (Leave all heaters on while probing). ; C (Endstop input): 0. (Mainboard) io4.in. M950 S0 C"0.io4.out" ; Create GPIO/servo pin. ; S (Output/servo pin number): 0. ; C (Pin name): 0. (Mainboard) io4.out. G31 P500 X0 Y22.0 Z3.105 K0 ; Set Z probe. ; P (Trigger value): 500. ; X (Probe X offset [mm]): 0. ; Y (Probe Y offset [mm]): 22.000. ; Z (Probe Z offset [mm]): 3.105 (This is modified for Z probe calibration. A higher offset number moves the nozzle closer to the bed.). ; K (Z probe number): 0. M557 X25:325 Y25:313.5 P3 ; Define Z probe mesh grid (This is the probe point grid, not the nozzle grid). ; X (Min:Max X coordinates to probe [mm]): 35 (Min) : 325 (Max). ; Y (Min:Max Y coordinates to probe [mm]): 25 (Min) : 313.5 (Max). ; P (Points to probe in each direction): 3.
-
Thanks.
Let's changes things just a bit:
M950 S0 C"0.io4.out" M558 P9 C"0.io4.in" H3 T6000 F120 A1 R0.2 B0 G31 P25 X0 Y22.0 Z3.105
Reset and try what I suggested before BUT lets use G92 Z7 instead of G92 Z3
Frederick
-
@fcwilt
Same problem. Probe did not deploy. Same error: "Error: Probe was not triggered during probing move" -
@charlie said in BLTouch Probe Won't Deploy:
Same problem. Probe did not deploy. Same error: "Error: Probe was not triggered during probing move"
And yet when you issued the M208 S1 Z-100 and then the G30 it seemed to work?
Frederick
-
@fcwilt
This is correct, but I cant seem to replicate the scenario in which it worked. -
@charlie said in BLTouch Probe Won't Deploy:
@fcwilt
This is correct, but I cant seem to replicate the scenario in which it worked.Well we are overlooking something simple.
Did you post what the DWC Z Probe readout value is?
Frederick
-
@fcwilt
Z Probe readout value is 0, and remains 0 for the entire homing attempt. -
Im unsure as to whether this means anything, but the BLTouch light remains a solid red when the machine is idle, as well as before and during the homing process. Of course the light shuts off when I power off the machine to prevent crashing, but the probe also deploys when power is turned off while the Z probe is occuring.