Duet3 6HC not deploying BL touch for mesh bed leveling

autopilot.exe

Good news: M98 P"config.g" now only returns a blue message about HTTP, FTP, and TELNET. no errors. confirmed. the only drivers being used on the expansion are D0 for extruder 0 and D1 for extruder 1. The BL touch is on io.7 on the mainboard

Phaedrux

What was the error? Your screen shot didn't upload.

Phaedrux

Only other suggestion I have at this point is to try using io_5 instead of 7.

autopilot.exe

G29

Error: Z probe was not triggered during probing move

Phaedrux

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

;deselect tools T-1

Do you happen to have anything in your tool change files?

autopilot.exe

So I just switched it from io.7 to io.5 and edited my config to match

; Axis Limits
M208 X50 Y0 Z0 C0 S1                                                  ; set axis minima
M208 X550 Y550 Z550 C260 S0                                           ; set axis maxima

; Endstops
M574 X1 S1 P"!io1.in"                                                  ; configure active-high endstop for low end on X via pin !io1.in
M574 Y1 S1 P"!io0.in"                                                  ; configure active-high endstop for low end on Y via pin !io0.in
;M574 Z1 S2 P"!io7.in"                                                            ; configure Z-probe endstop for low end on Z

; Stall detection for tool coupler
M915 C S5 F0 H200

; Z-Probe
M950 S0 C"io5.out"
M558 P9 C"io5.in" H2 F120 T6000 R0.2 A1 S0.01 ; 1 reading
;M950 S0 C"io7.out"                                                     ; create servo pin 0 for BLTouch
;M558 P9 C"^io7.in" H5 F120 T6000                                       ; set Z probe type to bltouch and the dive height + speeds
M557 X100:400 Y100:400 S25:25                                          ; define mesh grid
G31 P50 X-63 Y-61 Z2.5                                                 ; set Z probe trigger value, offset and trigger height

Good news: it still works a z endstop. the probe deploys and retracts at the appropriate times.
Bad news: G29 still doesn't deploy the probe

Phaedrux

Is there something about the position of the first probe point for G29 that is causing stress on the servo wiring and making a poor intermittent connection?

Can you try manually placing the print head at the same place it would be when doing G29 and then sending a manual G30? Does it work there?

autopilot.exe

@Phaedrux I do, the FDM Heads are set up in Tpre1, Tpre2 and the corresponding post and free files to make everything dock correctly.

; tpre1.g
; called before tool 1 is selected

;Unlock Coupler
M98 P/macros/Coupler - Unlock

;Move to location
G1 X130 Y350 F6000

;Move in
G1 Y475 F4000

;Collect
G1 Y523 F1500

;Close Coupler
M98 P/macros/Coupler - Lock

;WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING!
;if you are using non-standard length hotends ensure the bed is lowered enough BEFORE undocking the tool!
G91
G1 Z10 F1000
G90

;Move Out
G1 Y350 F3000

; tpost1.g
; called after tool 1 has been selected

;heatup
M116 P1

;prime nozzle
;M98 Pprime.g

;mesh levelling on
G29 S1

;PCF fan on
M106 P2 R2

; tfree1.g
; called when tool 1 is freed

;Drop the bed
G91
G1 Z5 F1000
G90

;mesh levelling off
G29 S2

;Purge nozzle
;M98 Ppurge.g

;Move In
G53 G1 X130 Y350 F6000
G53 G1 Y475 F4000
G53 G1 Y523 F1500

;Open Coupler
M98 P/macros/Coupler - Unlock

;fan off
M106 P2 S0

;Move Out
G53 G1 Y200 F4000

it does error everytime though saying "no heightmap.csv found" since I can't execute g29 to create one.

Phaedrux

Can you create an empty file called heightmap.csv?

autopilot.exe

yes, I just dropped it in /sys

autopilot.exe

G30 does not deploy the probe either. the bed just moves up without the probe shooting down first

fcwilt

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

G30 does not deploy the probe either. the bed just moves up without the probe shooting down first

So what happened since you posted this:

Good news: it still works a z endstop. the probe deploys and retracts at the appropriate times.
Bad news: G29 still doesn't deploy the probe

Frederick

Phaedrux

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

G30 does not deploy the probe either. the bed just moves up without the probe shooting down first

You mean at the same location as the G29 would use?

If so, sounds like intermittent connection.

autopilot.exe

we've come full circle.

the situation as it sits now:

The BL Touch functions correctly after a machine reset. Issuing a G28 Z command sends the BL Touch to the correct spot and the probe deploys, reads, and then retracts. After that the probe becomes completely non responsive.

M401, M402 say green in the console but no action actually happens in real life.

After the first time XYZ, and C are homed the BL Touch wont respond to anything, including M280 S0 macros.

This is leading me to believe that the Duet is not recognizing that servo number as a Z probe, since the location data is still being used but the actual probe is being ignored. i.e my mesh area is 100:400 in both X and Y and my probe offset is X-63 Y-61. When G29 is called, the toolhead moves to X161 Y161 and attempts to probe.

; Endstops
M574 X1 S1 P"!io1.in"                                                  ; configure active-high endstop for low end on X via pin !io1.in
M574 Y1 S1 P"!io0.in"                                                  ; configure active-high endstop for low end on Y via pin !io0.in
;M574 Z1 S2 P"!io7.in"                                                            ; configure Z-probe endstop for low end on Z

; Stall detection for tool coupler
M915 C S5 F0 H200

; Z-Probe
M950 S0 C"io5.out"
M558 P9 C"io5.in" H5 F120 T6000 R0.2 A1 S0.01 ; 1 reading
;M950 S0 C"io7.out"                                                     ; create servo pin 0 for BLTouch
;M558 P9 C"^io7.in" H5 F120 T6000                                       ; set Z probe type to bltouch and the dive height + speeds
M557 X100:400 Y100:400 S25:25                                          ; define mesh grid
G31 P50 X-63 Y-61 Z2.5                                                 ; set Z probe trigger value, offset and trigger height

Phaedrux

Can you direct connect the BLTouch to the board skipping any wire extensions and see if it behaves better?

Either the probe or the wiring are bunko. The config looks fine.

90% of the time it's the wiring with BLtouch issues.

autopilot.exe

Swapped out BL Touch with another unit we had. Still the same issue. I can confirm the wiring is good since we had this same setup with a duet 2 and expansion before switching to the duet 3

Phaedrux

Other than testing a direct connection with the BLTouch I can't think of anything else.

What version of BLtouch is it btw?

autopilot.exe

@Phaedrux v3.1

so I've boiled it down to:

the duet recognizes the BL touch as servo 0 since after power on but before homing z I can use my M280 macros as many times as I want. After the duet calls for the BL touch to be used as a z endstop the first time my macros quit working and none of the commands involving the BL Touch see servo 0 anymore either (G29, G30, G32, M401, M402, and G28 Z). Somehow the device gets "used up" and wont be replaced until a board reset.

Phaedrux

@autopilot-exe said in Duet3 6HC not deploying BL touch for mesh bed leveling:

;Open Coupler M98 P/macros/Coupler - Unlock

What's in this macro then?

autopilot.exe

Update to close out this thread.

I moved away from the BL Touch for mesh bed leveling. I switched to using the mechanical switch included on the bottom of the E3D tool changer. This almost worked out of the box with no modifications to the config file. I actually found another post made by @dc42 where he had walked someone through setting it up. Ever since then things have been great. I appreciate all the help along the way!