BL Touch not stopping when triggered
-
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
-
I think 2.9V should be plenty. You do not need to configure a pullup resistor.
If you are getting 0V out of it when it is not triggered and 2.9V when triggered, and you have connected that output pin to the IN pin of the Z probe connector on the Duet 085, then it should indicate "Z probe: not triggered" when it is not triggered and "at min stop" when it is triggered. Check that the output wire it making contact with the Z probe connector IN pin.
You could also try Z probe type P1 in the M558 command and look at the Z probe reading in DWC. It should be close to 0 when not triggered, and about (2.9/3.3)*1024 = 900 when triggered.
HTH David
-
David,
Is Zin - AD12 on the wiring diagram? From here, http://www.reprap.org/wiki/Duet_Wiring
P1 it is, as simple as that! I get 920 when triggered and 0 when not.
The probe is probing away - the end of the probe is a little high - nozzle is hitting the bed at some points, but I am super excited to see the probe in action!! It has been a few months of trying things, mistakenly putting the servo signal in pin 19, didn't help either.
Regards, Andrew
-
Yes, Z Probe In is AD12, at one end of the Z probe connector.
I still don't understand why P5 didn't work for you, unless you are using a very old version of RepRapFirmware (1.18.2 is latest stable, and 1.19RC4 is latest edge).
