BL-Touch V3.1 not automatically deploying
-
@commie said in BL-Touch V3.1 not automatically deploying:
; Tools
M563 P0 S"Change nozzle" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z100 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0CThe G10 ... Z100 tool 0 offset is causing the Z height to be set to 100 after sending G92 Z0. Change it to Z0.
Do you still get the "Error: G30: Zprobe 0 not found" message?
Just before running G30, send M558 on it's own to check probe is defined.
Ian
-
@droftarts Thank you amended tool Z setting to 0.
@droftarts said in BL-Touch V3.1 not automatically deploying:
Do you still get the "Error: G30: Zprobe 0 not found" message?
No. That only occurred when I tried rewiring white wire to zstop, changing pin in config G accordingly.
m558
Z Probe 0: type 9, input pin zprobe.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 12000mm/min, recovery time 0.50 sec, heaters normal, max taps 1, max diff 0.00However, there's still no triggering when probe touches the bed.
This is getting weird. When my Anet board died I first tried to move GT2560 board from Geeetech (I urgently needed direct drive extrusion) and configure it under Marlin 2.0.7. 3D touch didn't work no matter whatever I tried to do, even with help from Marlin devs. Now similar picture with Duet. BUT sensor works perfectly when I put GT2560 back on Geetech, flashed Marlin 1.1.8 config provided by them and connected the sensor.
-
@commie What is reported in DWC for the Z-probe value? When not triggered it should be 0, when triggered it should be 1000. If it's constantly 1000, try changing M558 to:
M558 P9 C"!^zprobe.in" H5 F120 T12000 R0.5 S0.003 ; set Z probe type to bltouch and the dive height + speedsNote the extra ! in the pin name, to invert the signal. There have been other people who have struggled with clone BLTouch.
Ian
-
@droftarts If I invert it G28 returns an error "Probe already triggered at start of probing move" and probe value sets to 1000.
-
@commie If the probe isn't registering as triggering in DWC (ie going from 0 to 1000) then either the wiring isn't right (no signal recieved on the white wire, so check continuity from probe to Duet pin) or there is something strange about the output of the clone BLTouch; maybe it doesn't output a high enough voltage to trigger the Duet. If it works like a real BLTouch, you could try changing the mode to 5V (the probe pin on the Duet is 30V tolerant). See the "Logic Voltage Conversion (writing to EEPROM) " section here: https://www.antclabs.com/bltouch-v3
Ian
-
@droftarts Could be the case with the output, yes, although I still can't figure out why does it work in one case and doesn't in another. I'll try messing around with voltages and see what happens. Original BLTouch was ordered a few days ago too (to see and try, as both of these 3D touch sensors were bought few years ago and something might have been changed in hardware logic since), but shipping from China might take up to a month. I guess in the mean time I'll try to DIY a probe from and optical switch and micro servo and see if that works. Thanks for all the help anyway, I really appreciate it.
-
-
@jay_s_uk awww metal ones weren't available so I ordered a plastic RC SG90
-
-
@jay_s_uk 7 quid for servo, 12 quid shipping it to Thailand. Thanks but no thanks
Living on a remote island has its disadvantages too LOL -
@commie said in BL-Touch V3.1 not automatically deploying:
12 quid shipping it to Thailand. Thanks but no thanks
Living on a remote island has its disadvantages too LOLworthy trade off, no doubt.
