BL "not" touching...
-
So I bought a BL touch and I've been revamping and re-commissioning my printer. Since I was adding the BLTouch, I didn't bother putting the old z-stop on the printer.
So... I got X, Y, and Z all tested and moving. The X and Y endstops check out. I followed the guide in the documentation section to connect the BLTouch, but I also generated a new config with the config tool --- to see what it created as well.
One thing the documentation doesn't cover is that the ZSTOP command in config.g changes to (I think):
M574 Z1 S2
(formerly was M574 Z1 S1 P"!zstop")
... but having done that, these are the other lines I have so far:
M950 S0 C"exp.heater3" ; Duet 2 WiFi/Ethernet
M558 P9 C"^zprobe.in" H5 F120 T6000 ; Duet 2 WiFi/Ethernet, DueX2/5
G31 P25 X35 Y0 Z4
M557 X15:185 Y15:185 S20... now the documentation says P25 for G31, but the generated tool gives P500. Either value, tho, the BLTouch doesn't engage when z-homing.
Now the BLTouch does respond to M280 P0 S10 and M280 P0 S90 ... so the BLTouch itself is working.
Help?
-
@zbeeble adding something to my own data, Duet2wifi, firmware 3.41
-
@zbeeble
My BlTouch on Duet 2 Wifi has the following configuration; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H6 F600:120 T4800 A10 S0.018 R0.5 B1 ; set Z probe type to bltouch and the dive height + speeds - turn off heaters when probing G31 P500 X26.2 Y-1 Z0.96 ; set Z probe trigger value, offset and trigger heightEDIT
Also have you created deployprobe.g & retractprobe.g ?; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v2.1.4 on Sat Jan 04 2020 09:46:45 GMT+1000 (Australian Eastern Standard Time) ;echo "deploying probe" M280 P0 S10 ; deploy BLTouch; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v2.1.4 on Sat Jan 04 2020 09:46:45 GMT+1000 (Australian Eastern Standard Time) ;echo "Retracting probe" M280 P0 S80 ; retract BLTouch -
@owend I have the deployprobe.g and the retractprobe.g (do I have to do anything but name the file?) for P558, can you elucidate on the parameters you have that I don't have? You have A, S, R and B
-
-
@owend They do have that. No comments, tho.
-
@zbeeble said in BL "not" touching...:
M950 S0 C"exp.heater3"
Double check that this is the pin you're actually connected to and that the wire has continuity.
Does the BLtouch pin drop in and out when first powered up?
If you send M401 and M402 does the pin pop in and out?
Does your homing file use G30 for the Z homing section?
Are the deploy and retract files in the sys folder along side config.g?
Can you send M98 P"config.g" and post the response here?
-
@phaedrux said in BL "not" touching...:
@zbeeble said in BL "not" touching...:
M950 S0 C"exp.heater3"
Double check that this is the pin you're actually connected to and that the wire has continuity.
Does the BLtouch pin drop in and out when first powered up?
Drops twice, red light stays on.
If you send M401 and M402 does the pin pop in and out?
M401 -> deploys, light off.
M402 -> retracts, red light back on.
Does your homing file use G30 for the Z homing section?
My homez.g:
G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 Z-205 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this)Are the deploy and retract files in the sys folder along side config.g?
Yes. deployprobe.g contains simply
M280 P0 S10and rectractprobe.g contains simply
M280 P0 S90Can you send M98 P"config.g" and post the response here?
2022-08-06, 3:23:04 p.m. M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled -
Let's make sure we know what you mean by "BL Touch does not touch". This sounds like you mean that when the command to probe is given, the bed stops before getting to the probe. Is this the case? Or is the bed not moving at all?
Also, when connecting a new endstop (or Z probe), a good practice is to trigger the probe by hand far from the stop or probe hitting their target. For the BLtouch, move the print head out to maybe 50mm from the bed, then run zhome.g. You should see the probe deploy, then the printhead with probe moving towards the bed. Reach in and touch the probe with your finger to be sure it triggers and the print head stops moving. Now you know the probe is working, and those 50mm of space give you time to shut off the power before a crash happens if the probe is not working.
Is that your whole config.g? It looks like it is missing everything it needs except the networking. Did you use the configuration tool to generate a config.g? If not, you can use this to create a set of files to start with: https://configtool.reprapfirmware.org/Start
I use a BLTouch and in my config.g I do not configure the BLTouch as an endstop (because it will not be triggered to stop nozzle crash, like a limit switch can). In my config.g, I set up a Z probe. Here are the lines in my config.g:
; Endstops M574 X1 S1 P"!io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in M574 Y2 S1 P"!io8.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io18.in ; Z-Probe 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 G31 P500 X-31 Y-2 Z2.5 ; set Z probe trigger value, offset and trigger heightThe pins you call out in the "S" commands in the M574, M950, and M558 will depend on your board and where you connected the probe and switches.
Then, in my homez.g, I don't use a G1 H1 command. This is because the touch is not an "end stop" and I got scared about whether it would work properly. How does it know to deploy the probe before starting to move? Someone here may explain it better. Instead, I use a G1 to move the probe to the center of the bed, then a simple G30 command to do the probing. G30 is a probe command and knows to deploy the probe before moving.
;################;! Move the probe to the center of the bed quickly. G1 X150 Y125 F6000 ;################;! Probe the bed and set the probe trigger point to Z=0 G30My complete zhome is longer because it looks to see if the X and Y axes are homed and if not it calls the homex.g and homey.g files first, so when it moves to the center of the bed it knows where it it.
-
@mikeabuilder said in BL "not" touching...:
How does it know to deploy the probe before starting to move? Someone here may explain it better. Instead, I use a G1 to move the probe to the center of the bed, then a simple G30 command to do the probing. G30 is a probe command and knows to deploy the probe before moving.
That's the problem.
The OP doesn't have G30, so the probe isn't told to deploy.
G30 calls deployprobe.g and retractprobe.g as required. -
@zbeeble said in BL "not" touching...:
My homez.g:
G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 Z-205 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this)This is the problem.
Remove this
G1 H1 Z-205 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this)And replace it with this
G1 X150 Y150 F6000 G30This would be the same for the homeall.g file if it also has a z homing section.
Alter the X150 Y150 to position the probe wherever you want to set Z0. Usually the center of the bed.
But just to be safe, you should go through this to make sure the probe works in a controlled test first.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing
