BLTouch passes self test, will not manually deploy.

alankilian

@Design THIS LINK should help you get it working.

Phaedrux

Here's what the config tool gives me.

; Z-Probe
M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds

; deployprobe.g
; called to deploy a physical Z probe
;
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
;
M280 P0 S90 ; retract BLTouch

Then test deployment with M401 and M402

Design

@Phaedrux said in BLTouch passes self test, will not manually deploy.:

Here's what the config tool gives me.

; Z-Probe
M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds

; deployprobe.g
; called to deploy a physical Z probe
;
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
;
M280 P0 S90 ; retract BLTouch

Then test deployment with M401 and M402

I have implemented the requested changes.

Config.g

; Z-Probe
;M558 P9 C"zprobe.in" H3 F100 T9000 R0.5						; BLTouch probing settings
;M950 S0 C"duex.pwm5"											; sets the BLTouch probe
M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds
M376 H100			                						; Height (mm) over which to taper off the bed compensation
G31 P500 X-25.5 Y26.9										; BLTouch X and Y offset
M557 X{move.axes[0].min + sensors.probes[0].offsets[0] + 1, move.axes[0].max + sensors.probes[0].offsets[0] - 1} Y{move.axes[1].min + sensors.probes[0].offsets[1] + 1, move.axes[1].max + sensors.probes[0].offsets[1] - 1} P10:10
; The M557 is used to define the mesh grid area. It uses the P parameter to set the amount of probing points. P10:10 would be a 10x10 grid. Supports up to a 21x21 grid. 
M98 P"config_probe.g"										; Load the Z-offset from the config_probe.g file
; The Z_offset value is now set in config_probe.g, not in config.g
; Adjust the values there, do not adjust anything here.

deployprobe.g

; deployprobe.g
; called to deploy a physical Z probe
M280 P0 S10			; deploy BLTouch

retractprobe.g

; retractprobe.g
; called to retract a physical Z probe
;
M280 P0 S90 		; retract BLTouch

The pin still does not deploy or retract when using m401 and m402. When sending the M401 command, the blue light on the BLTouch turns on dim. When running M402, the light becomes brighter. When running M401, the light becomes dim again. This seems that the BLTouch is getting the command, but the pin is still not deploying.

When running M280 P0 S60, the pin will deploy down.

Phaedrux

And you say it works correctly on another machine? Very strange. It sounds like it's behaving like the pin is dirty or stuck, but then it wouldn't deploy correctly during the startup test or connected to another machine, yet it seems to be correctly getting the commands as the LEDs are changing.

Do you have another free PWM port on the Duex? It may be worth trying a different port.

Design

@Phaedrux I can change it to a different PWN port. It deploys with the M280 P0 S60 command. Maybe I need a different duty cycle?

Phaedrux

@Design said in BLTouch passes self test, will not manually deploy.:

It deploys with the M280 P0 S60 command.

This is putting it in test mode.

Design

@Phaedrux but the pin still deploys, so at least it is getting the command correctly. Could it be voltage drop?

Phaedrux

@Design said in BLTouch passes self test, will not manually deploy.:

Could it be voltage drop?

Do you have a multimeter to test the voltage at the bltouch?

Design

@Phaedrux I just swapped it to PWM4 and it's working flawlessly now with m401/m402. However, now I'm getting driver short/over temperature errors for one of the drivers on the duex5. Could the board be faulty? It seems like issue after issue is coming up with it. It's brand new, haven't even been able to print on it yet. The most I've been able to do is jog the axes.

Phaedrux

Can you try removing and reinstalling the ribbon cable between the Duet and Duex?