Duet3 6HC not deploying BL touch for mesh bed leveling

fcwilt

Hi,

Regards the command M574 Z1 S2 P"!io7.in"

From the docs for M574:

Snnn 1 = switch-type (eg microswitch) endstop input, 2 = Z probe (when used to home an axis other than Z), 3 = single motor load detection, 4 = multiple motor load detection (see Notes).

Given that you try to use io7.in twice I would not be surprised if the configuration of the Z probe is failing.

Do this for us please:

From the console execute M98 P"config.g" and check for any error messages.

Frederick

autopilot.exe

Screenshot 2021-03-09 135242.jpg

So before adding the P"io7.in" after the M574 command the bltouch would work for the initial home z but if I tried to home z again the probe would not deploy. The toolhead would go the the correct X and Y location and the bed would move without deploying the probe. The only way to "release" the probe would be to power cycle the machine. For some reason adding that P parameter fixed this issue. I agree it is unusual since it should just be M574 Z1 S2.

fcwilt

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

For some reason adding that P parameter fixed this issue. I agree it is unusual since it should just be M574 Z1 S2.

Please read the docs again where it says:

2 = Z probe (when used to home an axis other than Z)

You should not have that command at all unless it is specifying a normal endstop sensor for Z.

Frederick

Phaedrux

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

M98 P"homec.g" ; Home C (ToolHead) M98 P"homex.g" ; Home X M98 P"homey.g" ; Home Y M98 P"homez.g" ; Home Z

Post these macros please.

autopilot.exe

@fcwilt wait...? are you saying it should just read M574 Z1? no s parameter or P parameter?

fcwilt

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

@fcwilt wait...? are you saying it should just read M574 Z1? no s parameter or P parameter?

Hi,

A M574 is not needed for configuring a Z probe.

If you don't have a Z endstop sensor you would have M574 Z0.

If you do have a Z endstop sensor then you use M574 Z(1 or 2) S1 and specify the input pin name.

In your case your were trying to use the same input twice - which you cannot do.

Frederick

autopilot.exe

@fcwilt so I commented it out to test.
good news: the probe still deploys for homing Z.
Bad news: the probe macros are all non responsive now and the mesh bed leveling still fails to deploy the probe

Screenshot 2021-03-10 103035.jpg

fcwilt

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

@fcwilt so I commented it out to test.
good news: the probe still deploys for homing Z.
Bad news: the probe macros are all non responsive now and the mesh bed leveling still fails to deploy the probe

Just FYI you don't have to post screen shots - you can copy and paste code right into a </> tag.

If the probe deploys for homing it should deploy everywhere - unless something is configured wrong.

Do M401 and M402 always work?

Frederick

autopilot.exe

@Phaedrux

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Mar 05 2021 11:02:45 GMT-0600 (Central Standard Time)
G91               ; relative positioning
G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-605 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-605 F360  ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000   ; lower Z again
G90               ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Mar 05 2021 11:02:46 GMT-0600 (Central Standard Time)
G91               ; relative positioning
G1 H2 Z15 F6000    ; lift Z relative to current position
G1 H1 Y-555 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000    ; go back a few mm
G1 H1 Y-555 F360  ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-10 F6000   ; lower Z again
G90               ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 11:26:03 GMT-0600 (Central Standard Time)
G91                ; relative positioning
G1 H2 Z5 F6000     ; lift Z relative to current position
G90                ; absolute positioning
G1 X163 Y161 F6000 ; go to first probe point
G30                ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91               ; relative positioning
;G1 Z5 F100        ; lift Z relative to current position
;G90               ; absolute positioning

; homec.g
; called to home the C axis (coupler)

;crashc
G92 C260
M913 C40			; C MOTOR TO 40% CURRENT
G1 C-260 F2400  ; drive the C-axis to the stop
M913 C100			; C MOTOR TO 100% CURRENT
G1 C1 F50000
G92 C0

;Open Coupler
M98 P/macros/Coupler - Unlock

note: the homec.g file was directly copied from e3d's documentation.

fcwilt

@autopilot-exe

According to the docs M98 requires double quotes around the file name in v3 firmware.

Frederick

autopilot.exe

@fcwilt the duet doesn't spit out any errors. I typed "m401" and I get a green notification, but nothing moves on the machine. I type "m402", same thing happens.

Phaedrux

Can you confirm that your deploy and retract probe macros are in the /sys folder?

autopilot.exe

@fcwilt in my homeall.g there are quotes around the file names. Home C,X, and Y are all executed correctly. when it gets to home z, the probe still doesn't deploy. I just tried it after removing the M574 command earlier.

autopilot.exe

@Phaedrux Screenshot 2021-03-10 105107.jpg

Can confirm.

fcwilt

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

@fcwilt the duet doesn't spit out any errors. I typed "m401" and I get a green notification, but nothing moves on the machine. I type "m402", same thing happens.

Hmm...

At this point I suppose we should verify the contents of deployprobe.g and retractprobe.g.

Frederick

autopilot.exe

@fcwilt

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 11:26:03 GMT-0600 (Central Standard Time)
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 11:26:03 GMT-0600 (Central Standard Time)
M280 P0 S90 ; retract BLTouch

fcwilt

Thanks.

Does the probe run it's self-test routine when you power on the printer?

Did you verify that it is connected to the correct input and output pins?

Frederick

autopilot.exe

@fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

fcwilt

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

@fcwilt the self test is working, I have it wired correctly according to the documentation. (3.3v: nothing, io7.in: white, GND: black and brown soldered together going to a single pin, io7.out: orange, 5 volt: red)

Running out of ideas.

I have a Duet 3 setup on my workbench and BLTouch units in inventory.

All boards (6HC, 3HC, 1LC) are running 3.2.2.

I will get a BLTouch out and connect and configure as you have.

Frederick

autopilot.exe

@fcwilt A possibility that I just considered: the firmware generator tool that I used as a base is v3.2.3. Could the mismatch be from there? i.e, the RepRapFirmware Configuration tool version not being in line with the firmware version?