BLTouch Probe Won't Deploy

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

What exactly do you have in your deployprobe.g and retractprobe.g files in the sys folder?

deployprobe.g (changed from deployprobe0.g in case this was a part of the issue)

; Voron
; 0:/sys/deployprobe0.g
; Deploy probe file for Duet 3 (firmware version 3.3).
; Called to deploy BLTouch probe via M401.
; 2021/06/30/16:14

M280 P0 S10  ; Set servo position.
             ; P (Servo index): 0 (Based on config.g, Z Probe, M950 S command).
             ; S (Servo angle): 10.

retractprobe.g (changed from retractprobe0.g in case this was a part of the issue)

; Voron
; 0:/sys/retractprobe0.g
; Retract probe file for Duet 3 (firmware version 3.3).
; Called to retract BLTouch probe via M402.
; 2021/06/30/16:14

M280 P0 S90  ; Set servo position.
             ; P (Servo index): 0 (Based on config.g, Z Probe, M950 S command).
             ; S (Servo angle): 90.

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

Does M401 and M402 work to deploy or retract the probe?

Yes, it does.

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

Does the probe deploy when you send G30?

No, it does not.

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

Does the BLTouch pin deploy and retract when power is first applied?

Yes, it goes through a deploy/retract cycle 2 times. Light on BLTouch stays red.

@phaedrux said in BLTouch Probe Won't Deploy:

How exactly is the BLtouch wired?

Wired per Connecting Z Probe: BLTouch For me this is:
White > IO4_IN
Brown and Black tied together > GND
Yellow > IO4_OUT
Red > 5V

Wire material is BNTECHGO 24 Gauge Silicone Ribbon Cable Flexible Cable 24 AWG . Wired through IGUS cable chain as per Voron requirements.

@phaedrux said in BLTouch Probe Won't Deploy:

And The results of M122 and M98 P"config.g"?

M122

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9DG-3S46T-KV2LF
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 62124 of which 132 recycled
Never used RAM 141032, free system stack 202 words
Tasks: SBC(ready,4.9%,338) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.0%,908) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.1%,93) MAIN(running,87.9%,922) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:14:41 ago, cause: power up
Last software reset at 2021-12-10 15:06, reason: User, none spinning, available RAM 141032, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,1
Step timer max interval 134
MCU temperature: min 36.3, current 45.8, max 46.1
Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 22196, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 22196, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 22196, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 22196, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 22196, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 22197, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-12-10 15:31:52
Slowest loop: 0.46ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is assembling a command in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 7844, received 7, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 57573, free buffers 49 (min 48), ts 4410/4406/0
Tx timeouts 0,0,3,0,0,0 last cancelled message type 30 dest 127

=== SBC interface ===
State: 4, failed transfers: 1, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 30678/30678
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 29.79, max wait times: 9.3ms/0.0ms
Codes per second: 0.06
Maximum length of RX/TX data transfers: 2984/284

M98 P"config.g"

M98 P"config.g"

Looks like it runs successfully. CPU temp sensor raises from 45.8C to 2000.0C for less than a second while performing this.

@phaedrux said in BLTouch Probe Won't Deploy:

Also send M558, G31, by themselves are see what they return.

M558

M558
Z Probe 0: type 9, input pin io4.in, output pin nil, dive height 3.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

G31

G31
Z probe 0: current reading 0, threshold 500, trigger height 3.105, offsets X0.0 Y22.0

Charlie

@joergs5 said in BLTouch Probe Won't Deploy:

The code is in GCodes3.cpp DeployZProbe() and RetractZProbe(), and looks ok.

Im not sure what this means. Please let me know if you would like to provide more information.

Charlie

@joergs5 said in BLTouch Probe Won't Deploy:

maybe your BLtouch is too near to the bed, please check

The print head is currently sitting around 200mm from the build plate (to prevent crashing).

BLTouch Body currently sits around 7.6mm from the bed (with the nozzle touching the bed). The pin in its retracted position sits around 2.1mm from the bed (with the nozzle touching the bed).

Phaedrux

@charlie said in BLTouch Probe Won't Deploy:

@phaedrux said in BLTouch Probe Won't Deploy:

Does M401 and M402 work to deploy or retract the probe?

Yes, it does.

In this case, I think the issue is the K0. If you're going to use K0 in your config you're going to have to use it consistently. Your homing file doesn't specify the probe number when you use G30.

@charlie said in BLTouch Probe Won't Deploy:

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).

The G30 and M558 here must have K0 specified if you're going to use that.

https://duet3d.dozuki.com/Wiki/G30

Either remove all instances of K0 from your config and leave the deployprobe.g and retractprobe.g named as such, or convert entirely to using the number probe format. Meaning use retractprobe0.g etc and when using any M558/G30/G31 command elsewhere you must also specify K0.

I think since you only have a single probe it would be best to jsut remove all instances of K0.

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

In this case, I think the issue is the K0. If you're going to use K0 in your config you're going to have to use it consistently. Your homing file doesn't specify the probe number when you use G30.

Okay, that makes total sense. I removed all instances of K0 (in config.g, M558 and G31), but the issue persists.

fcwilt

@charlie

If you have one probe you can leave the K parameter off everywhere. It defaults to 0 in anycase.

My BLTouch connected to a Duet 2 Wifi works fine and I have no K parameters anywhere.

I'm still baffled by your problem. I also still believe we are overlooking something simple.

Frederick

Phaedrux

Are you sure you've removed all cases of K0?

Can you try this?

Power cycle your printer
Before doing anything else, send M401 and M402 to test that the pin deploys and retracts.
If that works, send G30 by itself. Does the pin deploy? Does it give an error? Does the Z axis move?

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

Are you sure you've removed all cases of K0?

Here is the new Z Probe section of the config.g

; Z Probe

M558 P9 F120 H8 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                    ; 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.

homez.g

; Voron.
; 0:/sys/homez.g
; Called to home the Z axis via G28 Z.
; 2020/10/24/20:02

G91                   ; Set axes (not extruders) to relative positioning mode.
G1 H2 Z5 F6000        ; Lift Z relative to current position.
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).

and I no longer have the "0" on the deployprobe and retractprobe file names.

@phaedrux said in BLTouch Probe Won't Deploy:

Does the pin deploy? Does it give an error? Does the Z axis move?

Pin does deploy and retract with M401 and M402 respectively.

When calling G30. I get this error.

g30
Error: G30: Insufficient axes homed for bed probing

fcwilt

@charlie said in BLTouch Probe Won't Deploy:

When calling G30. I get this error.
g30
Error: G30: Insufficient axes homed for bed probing

X and Y have to be homed - are they?

Frederick

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

If that works, send G30 by itself. Does the pin deploy? Does it give an error? Does the Z axis move?

So, after getting this error:

g30
Error: G30: Insufficient axes homed for bed probing

I threw G92 X0, and then G92 Y0 in the console.

The probe did deploy in this instance.

Charlie

@fcwilt
Yes, homed X and Y after getting that error. The probe did deploy in this case.

fcwilt

@charlie

So it seems all is working and it's just a question of you being sure that X and Y are homed before trying to use the probe.

That is one of the reasons I include a Z axis endstop sensor on all my printers so I can home Z without having to worry about homing X and Y first.

Frederick

Charlie

@fcwilt said in BLTouch Probe Won't Deploy:

So it seems all is working and it's just a question of you being sure that X and Y are homed before trying to use the probe.
That is one of the reasons I include a Z axis endstop sensor on all my printers so I can home Z without having to worry about homing X and Y first.

The problem is that the probe isnt deploying when I am actually calling a homez.g or homeall.g. It is only deploying when I am following the exact workflow that @Phaedrux outlines here.
@Phaedrux

Power cycle your printer
Before doing anything else, send M401 and M402 to test that the pin deploys and retracts.
If that works, send G30 by itself. Does the pin deploy? Does it give an error? Does the Z axis move?

Phaedrux

@charlie said in BLTouch Probe Won't Deploy:

M558 F600 H2 A1 ; Set Z probe. Feed rate: 600 mm/min. Dive height: 2 mm. Times to probe: 1.

I wonder if it has something to do with your homeall setting the dive height to be less than the trigger height.

@charlie said in BLTouch Probe Won't Deploy:

G31 P500 X0 Y22.0 Z3.105

I also thought that G30 would work regardless of X and Y being homed since it should only trigger movement in Z.

Phaedrux

The only other thing I can recommend for troubleshooting is to generate a basic config using the online tool and only customizing it manually to account for the basics and seeing if it works as expected.

Are you using toolboards or expansion boards or just the 6HC?

Charlie

@phaedrux said in BLTouch Probe Won't Deploy:

I wonder if it has something to do with your homeall setting the dive height to be less than the trigger height.

In this instance of attempting to home, I am using the "Home Z" button on the DWC. Here is my most current homez.g file.

; Voron.
; 0:/sys/homez.g
; Called to home the Z axis via G28 Z.
; 2020/10/24/20:02

G91                   ; Set axes (not extruders) to relative positioning mode.
G1 H2 Z5 F6000        ; Lift Z relative to current position.
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).

Phaedrux

M558 F600 H2 A1

This sets your dive height to 2mm, but your probe trigger height is over 3mm.

Do you see how that could be an issue?