Yet another BLtouch problem

Macgyver

Here is the pic as requested, Nothing connected except BLtouch and i7 screen

Now I have the 401 and 402 working, there was an illegal T switch added to the commands in the deployprobe.g and retractprobe.g

Phaedrux

Sounds like you've got it working now?

Macgyver

I would call it working with one exception, When I start the machine and M401 and M402 work, not an issue.

I have everything moved back to the D600 and have the rest of the machine put together. Moved all the firmware over and updated the config. g file with the error I found on the test bench. Kinda a small issue left

When I try to call the G28 it fails on the Z-axis with the error of
G28 Z
Error: Failed to enable endstops

X and Y axis work, not an issue, Pin will not deploy when it starts the Z home, however, the bed does move down 10 mm as expected and requested.

pretty sure this is going to be something in one of the macros, Going to chase it down today. If you have a suggestion where to start looking that would be appreciated.

Phaedrux

It sounds like you just need to update your homeall to use a G30 to use the probe instead of a G1 H1 Z move to use an endstop.

danzaywer

@macgyver
If you want to use probe as endstop then you have to set

M574 Z1 S2                               						    ; Set endstops controlled by probe

and use G30 instead of G1 H1 as @Phaedrux said

engikeneer

@danzaywer
You don't need the M574 line in there. I think the config generator just puts that line in by default but it's not needed (and may actually mean something else if you dig in the docs...)

@Macgyver Just make sure your homing files have a G30 command in like @Phaedrux said

danzaywer

@engikeneer said in Yet another BLtouch problem:

You don't need the M574 line in there. I think the config generator just puts that line in by default but it's not needed (and may actually mean something else if you dig in the docs...)

So can it be omitted?

engikeneer

@danzaywer yes, from the docs for M574 in RRF3:

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

I think the intended use of the S2 parameter would be to set your x or y axis to use the z probe as an endstop (like the ormerod printer does). Don't think it does any harm though as it is, which is why it hasn't been taken out from the config tool (though it has caused some confusion for a few people.on here!)

dc42

@engikeneer said in Yet another BLtouch problem:

I think the intended use of the S2 parameter would be to set your x or y axis to use the z probe as an endstop (like the ormerod printer does).

That's correct.

Macgyver

Hi Guys

Sorry for going AWOL on this, unfortunately got Covid but finally back in the office and back on this machine.

Going to work through it and update it shortly.

Macgyver

So after much trying to figure out what's going on with this machine, turns out had a weak spot in one of the ground lines in my BLtouch, It would work sometimes and randomly just not trigger. Ran 5 new lines all from the BLtouch through the drag chain to the mainboard (about 17 ft) and now its working 100% predictability.

Just going to post my configuration here in case others want something to ref that is working. All this is done on RRF 3

Config .g file

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)

; Endstops
M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop

; Z-Probe
M950 S0 C"exp.8" ; Assign GPIO port 0 to Heater3/Pin8 on exp conn, Servo Mode
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to 9 BL Touch and the dive height + speeds
G31 P500 X0 Y0 Z6.3 ; set Z probe trigger value, offset and trigger height
M557 X15:585 Y15:585 S28.5 ; define mesh grid

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

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-605 Y-605 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-605 Y-605 F360 ; move slowly to X and Y axis endstops once more (second pass)
G30
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G30
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

Phaedrux

@macgyver said in Yet another BLtouch problem:

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G30
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

Are you sure you want to force the Z position to zero AFTER using the probe to set the actual offset?

Macgyver

Actually a good point, I missed that,

Not sure where that one came from

Macgyver

you can mark this thread as solved, Hopefully, someone else can find it and make use of the information.

Thanks again for your help guys Truly appreciate it.