BLTouch Trigger not working
-
@mloidl said in BLTouch Trigger not working:
Hi,
When you power on your duet, is the BL-Touch doing a self test? Deploy/Retract several times.
If you have a newer BL-Touch you won't need the 220Ohm resistor any more.
You also don't have to call deployprobe.g and retractprobe.g manually, G30 will do this for you.
No, at power on the BLTouch seems "normal", no self test and no led powered. Only if I move the probe up and down manually the led blink.
I'm not using an original new BLTouch, but a 3DTouch (that was working correctly on the old i3).
-
Since you're not using an original BL-Touch i'm not sure if the start-up behavior is correct or not.
But what i've read is that the controlling the 3DTouch should be the same as for the BL-Touch.Can you deploy/retract the probe when sending M280 P3 S10 I1 / M280 P3 S90 I1, directly?
Maybe you can try to not invert the Servo-Signal. Remove 'I1' from M280.
-
@mloidl said in BLTouch Trigger not working:
Since you're not using an original BL-Touch i'm not sure if the start-up behavior is correct or not.
But what i've read is that the controlling the 3DTouch should be the same as for the BL-Touch.Can you deploy/retract the probe when sending M280 P3 S10 I1 / M280 P3 S90 I1, directly?
Maybe you can try to not invert the Servo-Signal. Remove 'I1' from M280.
I tried sending the gcode manually, but immediately the led of the sensor started to blinking on and off without moving the probe and in DWC there was a constant 1000 as value of the trigger. It continued to blinking (and the trigger value remained 1000) until I restarted the printer power on/off.
After the restart the led was off with the probe down, on if the probe was up with a trigger value of 0 in DWC... until I resend the gcode
-
A blink LED normally indicates an error.
Have you tried removing the I1 from the M280 command.
On my BL-Touch i had to add I1 because it was blinking without it. Maybe that's different for the 3DTouch. -
@mloidl said in BLTouch Trigger not working:
A blink LED normally indicates an error.
Have you tried removing the I1 from the M280 command.
On my BL-Touch i had to add I1 because it was blinking without it. Maybe that's different for the 3DTouch.Yes, I tried all these combinations:
- M280 P3 S10 I1
- M280 P3 S10
- M280 P3 S90 I1
- M280 P3 S90
- M280 P3 S160 I1
- M280 P3 S160
The result is always the same: blinking led.
-
Currently i'm out of ideas.
Maybe it's an wiring issue or 3DTouch does not behave like BL-Touch.
-
Try adding I1 to your m558 command for the 3d touch. It may behave differently than the BLTouch.
How is it wired?
Is the pin clean and straight? Does it move freely by hand?
-
After many tries I found something of interesting
When I power on the printer, I have to move the pin probe up (if it's down) and send a M280 P3 S160 I1 to "unlock" the sensor. After this, I can send all the commands to move the probe pin or to self-test (with the I1).
But if I power on the printer and the probe pin is down the command with S160 will not work and the sensor will start to blinking in error.
So, the simplest solution is to move the pin up before send any command, followed by the "unlock" command (M280 P3 S160 I1).
I modified all my homing config adding the unlock command before any commands, just to be sure that it's not locked in error before the homing.
Now, the question is: the command M280 P3 S160 I1 should not move the pin up automatically? Because it's not always working
-
Sounds like your pin probe needs adjusting, on the bltouch this is done via the small grub screw on the top to set the correct pin height.
-
@boldnuts said in BLTouch Trigger not working:
Sounds like your pin probe needs adjusting, on the bltouch this is done via the small grub screw on the top to set the correct pin height.
But now is working correctly the trigger, are you sure I need to adjust the probe calibration?
-
Does it do the correct up/down bit on power up self test, if so the pin should stay in the up position after this, mine does and I don't need to move it up or down via any commands for it to work.
-
I had a similar issue at first. The pin ended up being a little dirty and would stick a bit causing it to go into error immediately at startup because it couldn't drop consistently. I ended up taking the pin out and cleaning it with a bit of alcohol and some high grit sandpaper. It moved smoothly after that.
