BLTouch - Deploys but won't retract

fus3d

I'm having trouble with my BLtouch 3.1 (same results with 2.0 or 2.1 though). When I startup it tests properly probe is extended and retracted twice. Once in Duet I can send an M401 or M280 P3 S10 to get the probe to extend but then M402 or M280 P3 S90 fails to retract it. If you do one of those commands and then push the probe back it will extend again with a M401 or S10 command.

I've tried changing the logic mode between 5V and 3.3V. It seems to work better at 3.3V (with 5V it won't extend at all).

This same probe was working on an SKR1.3 before this. All I'm doing is switching the board out. I switched the BLTouch out with some older ones and the results seem identical.

Running 2.04RC Duet Wifi 1.02.

Config settings:

; Z-Probe
M574 Z1 S2                              ; set endstops controlled by probe
M307 H3 A-1 C-1 D-1                     ; disable heater on PWM channel for BLTouch
M558 P9 H5 F3000 T6000                   ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X27 Y15 Z2.5                   ; set Z probe trigger value, offset and trigger height
M557 X10:290 Y10:290 S20                ; define mesh grid

Wiring is done exactly as shown here:

alt text
Thoughts?

A Former User

@fus3d said in BLTouch - Deploys but won't retract:

M280 P3 S90

did you maybe tried other values for S ..

M280 P3 S80
M280 P3 S85
M280 P3 S95
M280 P3 S100

dc42

@fus3d, which particular 2.04RC version are you running? There was a known issue in this area in 2.04RC3 which was fixed in 2.04RC4.

fus3d

@smece said in BLTouch - Deploys but won't retract:

did you maybe tried other values for S ..

Tried those no luck

@dc42 said in BLTouch - Deploys but won't retract:

@fus3d, which particular 2.04RC version are you running? There was a known issue in this area in 2.04RC3 which was fixed in 2.04RC4.

That's the version I'm running will upgrade today and report back.

fus3d

@fus3d, which particular 2.04RC version are you running? There was a known issue in this area in 2.04RC3 which was fixed in 2.04RC4.

That's the version I'm running will upgrade today and report back.

Well that was easier than the first time I updated the firmware. RC4 fixed it. Wish I had checked back sooner, that was a painful diagnostic.

Thanks!