Can't get BL Touch working
-
When I power up the printer the probe deploys and retracts a couple of times before staying retracted and lit up red. When I send G30 the probe deploys but pin contact doesn't trigger, the pin also doesnt jump back into the retracted position. Notably, the z probe information on the web control never moves away from zero.
i've tested the cables for continuity from the back of the probe to the control board and connection is just fine.deploy command works fine using m401 or M280 P3 S10 I1
retract command works fine using m402 or M280 P3 S90 I1
(its connected to pwm heater 3 btw)if it helps, i've modifying my firmware from a fully working inductive probe setup so wondering if something i'd configured for that is causing this issue.
I started with this article: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
and also went over to this one to double check things. https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/
INFO:
bltouch v3.1 genuine
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.04RC1 (2019-07-14b1)
WiFi Server Version: 1.21
Web Interface Version: 1.22.6TIA for any help, this has been driving me up the wall since 10am this morning.
-
post your config.g
-
-
@Adam-V3D said in Can't get BL Touch working:
doesn't trigger, the pin also doesnt jump back into the retracted position. Notably, the z probe information on the web control never moves away from zero.
config looks fine regarding bltouch.
the z probe information only pulses once very quickly upon triggering with a bltouch. most of the time you will not see it in the ui.check the wiring for the z probe pin. a lot of users hard problems with the extension cable and the crimps of the bltouch.
-
I did continuity test and seems to be just fine
-
could it be a faulty BL touch?
-
I guess its a possibility. If the code is all correct, and i'm confident hardware is ok, then there aren't many other options.
-
@Adam-V3D said in Can't get BL Touch working:
the pin also doesnt jump back into the retracted position.
that tells me there is a problem with your bltouch.
after issuing the deploy probe a small push on the pin should cause the bltouch to pull up the pin.
-
Looks like i'm going to have to try and get a replacement probe then. I feel like that's going to be easier said than done.
Feeling like this might be my first and last experience with BL touch...
-
i am using this as an alternative to the bltouch.
https://www.thingiverse.com/thing:3303618 -
well thats another project added to the list! Thanks.
-
@Veti There is a version 2 of it: https://www.thingiverse.com/thing:3756428
Thank you for your information about the thing. -
Please don't shot me if is not related but missing here your bed.g can you try to give a look here:
https://forum.duet3d.com/topic/10455/solved-bl-touch-deploy-only-one-time-with-2-03rc1If you have this in your bed.g:
M98 Pdeployprobe.g ;
Try removing this as stated in that link.
-
@giostark
any help that people are trying to give is appreciated.
we are here to learn from each other.he stated that
When I send G30 the probe deploys but pin contact doesn't trigger, the pin also doesnt jump back into the retracted position.
the G30 command however does not execute the bed.g file.
The G32 command executes the bed.g.
see
https://duet3d.dozuki.com/Wiki/Gcode#Section_G32_Probe_Z_and_calculate_Z_plane -
@Adam-V3D said in Can't get BL Touch working:
Firmware Version: 2.04RC1 (2019-07-14b1)
please update to the latest 2.04RC4. There were some fixes regarding BLtouch V3
-
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.04RC4 (2019-10-19b1)
Duet WiFi Server Version: 1.23Updated as above. no change to bltouch functionality
-
Flipped over the two pins that go to the Z probe header and now it works. Bit odd because i'm sure it was wired correctly.
-
@Adam-V3D said in Can't get BL Touch working:
Flipped over the two pins that go to the Z probe header and now it works. Bit odd because i'm sure it was wired correctly.
Glad to hear it's working.
But clearly it wasn't wired correctly and is now
Frederick