BL Touch not stopping when triggered
-
okay it a just touch it, it will go up and come right back down. if I touch it and make it stay up I get the red 1000, but it goes into alarm mode and needs reset. Otherwise I don't get it. I wonder if the adjustment screw on top needs adjusted since its now on 3.3v vs the 5v it had before. Also I find it odd that the ground isn't hooked up for the wire going to the E0.
-
OK on a lark I ran a G32 with my hand on the power switch and it seems to be working. the deviation is a little high i think @ 0.236, but its a start.
-
Ground is ground, it doesn't matter where you get it in this case. There are two Ground wires coming out of the BLTouch, you can use either one, they are the same thing, this is just for convenience.
You didn't say if you had an older or a newer BLTouch. Mine is an old one (requires the 240 ohm resistor in parallel with GND on the endstop signal wire as seen here). There is nothing else to adjust with regards to 5V or 3.3V, at least on the old ones.
If you can control the BLTouch pin up/down, and see the red 1000 when the pin is up (with M402 and M280 P3 S60 I1, don't force it up), then you can be sure your wiring is OK and the problem is elsewhere. What I put above was all I needed to get the BLTouch to work for me.
It is strange that your BLTouch pin is coming back down, this does not happen for me from the Gcode console. If I do M401 the pin goes down, and if I touch the pin it retracts and stays up until I send more Gcode that changes the pin state (homing, printing, explicit M401 or M280…).
Cheers,
Ben. -
are you trying to home the printer with the Z probe?
in your homeall.g and homez.g files what is the command you use when telling the printer to dive for the Z height?
you should probably look at
http://reprap.org/wiki/G-code#G30:_Single_Z-Probe
edit:
If you are jsut testing the probe, the standard motion of the probe is to trigger and drop back down, so that it is ready to probe the next point. At the end of any probe using script you must use the Gcode to store the probe or use a macro like retractprobe.g that has the store gcode in it to retract the probe back up to get it out of the way. -
If you are jsut testing the probe, the standard motion of the probe is to trigger and drop back down
Right, but it is generally unwise to test a Z probe by issuing a G29 or G32 and hoping for the best
If I find some time I will update the wiki because the secret to debugging the BLTouch is to use its test mode, this is not mentioned in the BLTouch setup thread. When probing the trigger signal is too short to be visible from DWC so you don't know if you got it right or not.
Cheers,
Ben. -
Hi Fulg you mention updating the Wiki, I am happy to do this but without a BLtouch I am not exactly sure what needs to change. Do you mind letting me know (in this thread is fine) and I will make the updates, otherwise you can update the wiki directly if you like.
Cheers
Tony
-
Hey Tony. For one there is no mention of the proper commands to send (inverting the signal polarity is mandatory, i.e. M280 P3 S10 I1). It is also not mentioned that you should set up deployprobe.g and retractprobe.cfg to M280 P3 S10 I1 and M280 P3 S90 I1 respectively. I also wanted to add that you can test the BLTouch before probing by issuing M280 P3 S60 I1, which makes it maintain the signal forever instead of the normal 5ms pulse during homing/probing, so you can see the output in DWC.
Most of the troubles I had setting up my BLTouch is that the only documentation is the Wiki and that 8-page thread, which does not give the complete answer to all setup questions until about page three.
I think some of the confusion also comes from the fact that the initial set up was done on an older Duet; as you can see in the very first post of this thread people are still unsure which pin should be used for the servo PWM.
I can let you make the edits if you prefer, I guess you are worried about my low comment count, I can understand that…
EDIT: fixed the deployprobe.g and retractprobe.g sequences, that's what I get for repeating them from memory.
-
Just as an added data point, I have a BLTouch working in my printer, using Mode 5, and the probe input connector.
I used the connections as shown in the chart in the wiki, but did have to install the resistor across the probe pins, and had the pins reversed on the probe connector the first time I tried it.
Once I got that straightened out, it has worked, other than my slow approach to wrapping my head around the probing g-code commands.I did notice that the normal operation of my probe is that when it touches the surface and triggers, it will click up to the retracted position with the light lit, and then extends again automatically.
The only time it stays retracted is when I send the probe retract command, or it goes into error when it can't fully extend again after being triggered. -
If you extend the BLTouch pin with M280 P3 S10 I1 (or M401 if you set up your deployprobe.g correctly), then touch the pin to make it retract, it will not come back down. This is different than when doing probing, in which case the firmware itself is redeploying the pin to be ready for the next probe point.
The BLTouch itself does not know you are probing, it is just a sensor. As far as it knows it was asked to redeploy after a trigger and the pin was blocked from doing so, either due to not enough clearance to fully extend or some other obstruction, therefore it switches to its error mode.
Cheers,
Ben. -
I do have it working now, I adjust the screw a 1/4 turn and it is behaving normally.
Sniffle, I have a Delta, it does a home all to max only.
T3P3Tony, I have 2 codes you can add to the file, I tested them, and set them up as Macros.
Alarm Release: M280 P3 S160 I1
BLT Self Test: M280 P3 S120 I1
note the pin inversion -
Ive had my bltouch setup for so long now I have to refer back to the large post i made on the original BLTouch forum post, as well. Mine is still setup on P4 as well… I just havent seen the need to change it. If i remeber correctly I made that post as a type of overall information gather for the wiki page. I'm sure some of it needs to be updated to be correct, which I think is the parts already on the wiki.
-
Grr This is back again, it seems to work when I manually trigger it with my finger, but as soon as I try to probe the bed it won't trigger. I checked my wires and they are all where they should be, and I haven't touched the bed probe, or any of my marcos.
-
When I run M114 with the pin up or down the result is the same. "X: 0.000 Y: 0.000 Z: 0.000 E0: 0.0 E1: 0.0 " one of the E should change. I lowered my trigger in G31 to 20, no effect, and tried to change the type from P4 to P5. the sensor was constantly triggered and never off.
-
Whether you need type P4 or P5 in your M558 command depends on whether you have connected the probe output to the E0 endstop input or the Z probe input.
-
Whether you need type P4 or P5 in your M558 command depends on whether you have connected the probe output to the E0 endstop input or the Z probe input.
I get that but I haven't been able to get it to work with either set of setting so far.
-
-
I'm having the same issue
-
Whether you need type P4 or P5 in your M558 command depends on whether you have connected the probe output to the E0 endstop input or the Z probe input.
I get that but I haven't been able to get it to work with either set of setting so far.
How have you connected it to the Duet? See https://duet3d.com/wiki/Connecting_a_Z_probe#BLTouch and https://www.duet3d.com/forum/thread.php?id=1863.
-
Found out my issue was because I had the probe wires backwards in the Z probe header. Reversed them and it works like a charm. Doing my first calibration print now.
-
Hi Everyone,
First of all thanks to everyone that posts here. I finally got me wiring correct and learnt about the S60 test mode. Unfortunately, what to do when S60 does not produce a 0 value is not covered anywhere, that I have found.
Getting my BLTouch to register that the probe has been triggered on my Duet 0.8.5 board is where I am currently at and looking for advice.
Connected the servo leads to pins 1, 2 and 21.
Probe leads, White - Zin/ AD12 and Black - GND.Config.g is setup as:
M307 H3 A-1 C-1 D-1 ; reserve heater 3 (pin
for BLTouch PWM
M558 P5 X0 Y0 Z0 H5 F100 T2000 ; Z0 for delta
G31 X0 Y0 Z0.3 P25 ; Set the probe XY offset, Z height and signal thresholdBLTouch retracts and deploys twice on power cycle and Red LED stays lit.
When deployed:
M280 P3 S10 I1; Red LED is unlit, Probe extended and Prove voltage in 0 v
M119 ;Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: at min stop
DWC - Z Probe Red 1000 valueWhen in test mode and probe triggered:
M280 P3 S60 I1; Red LED is lit, probe stays up, Probe voltage is 2.9 v
M119 ;Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: at min stop
DWC - Z Probe Red 1000 valueExpected behaviour:
M119 - should show Z probe triggered
DWC Z Probe value should be 0Question:
Is the Z Probe voltage of 2.9 v too low for the Duet electronics to register that the Z Probe has been triggered? If, so, then what trigger voltage is required for the Z Probe?
Additionally, is there a "pull-up" resistor that needs to be set on the Z-Probe in config.g that I am not setting that is causing this behaviour?
Firmware Version: 1.19beta10+2 (2017-07-20)
Web Interface Version: 1.17+1Thanks, Andrew
