BLTouch doesn't always deploy Duet 3 6HC
-
Your “P500” in your config.g may be too high. I had a similar issue a while back, and I have mine set at P100. I haven’t had an issue since.
-
@Nuramori said in BLTouch doesn't always deploy Duet 3 6HC:
Your “P500” in your config.g may be too high. I had a similar issue a while back, and I have mine set at P100. I haven’t had an issue since.
the bltouch is digital. the signal is either 0 or 1000.
-
@dc42 said in BLTouch doesn't always deploy Duet 3 6HC:
In my case, g29 isn’t really involved. I ran g29 several times in succession and that didn’t seem to lock up the probe. I can home the machine, deploy and retract the probe just fine, walk away for an hour, and when I come back the probe is unresponsive. I’ll do some more investigation today. Switching io ports didn’t help for me.
-
I've had a similar issue, and managed it to narrow it down to the yellow BLTouch cable not being connected properly. I did a quick check disconnecting the cables one by one, and homing, and these are the results:
- white cable: no self-test, red LED on like normal, Z-probe value 1000, ejects pin but instantly retracts it and errors out
- black cable: no self-test, red led like normal, z-probe value 0 until homing, then goes to 1000 and errors out
- Yellow cable: completes self test, red LED works like it should, the Z-probe value is 0, but does not detect the homing, and will continue to move down even after pin gets disturbed
- red cable: does not do self test, no red LED, Z-probe value 1000
- brown cable: completes self test, red LED works, Z-probe value 0, ejects pin, works like normal
Note that my bltouch does not always do the self-test on bootup, and I'm not sure why so that part of the test might not be accurate
This is with a Duet 2 on RRF2 by the way
-
@Veti there was an issue in a previous firmware version that P500 was a problem, and reducing it to P100 would help, per David’s suggestion. It did. After that version I went back to P500 as a mid value and the problem re-emerged. Going to P100 fixed it, so I’ve kept the value.
-
@Nuramori Is your issue that the probe deploys and doesn't trigger, or are you having an issue with the probe not deploying at all?
-
@ctilley79 It was that it would deploy but not trigger.
-
@Nuramori ok. That’s different than my issue. If I can get mine to deploy, it works flawlessly. Mine is not reacting to m401 or m402 commands after a given period of time.
-
@ctilley79 I wanna know if you have deployprobe.g and retractprobe.g in /sys only !!!!! (If you do , can you post them here)
-
@User3D Yes. They are automatically generated if you select P9 as the probe type if i'm not mistaken. Here's a copy of mine
M280 P0 S10 ; deploy BLTouchM280 P0 S90 ; retract BLTouch -
@ctilley79 said in BLTouch doesn't always deploy Duet 3 6HC:
@User3D Yes. They are automatically generated if you select P9 as the probe type if i'm not mistaken. Here's a copy of mine
Yes they are, I just wanted to see if you've changed something that is causing all .
-
Any update on this? just broke a bltouch probe because of this issue.
-
I was having issues on IO_6, no deploy. checked wiring etc, all ok from that end. Changed to IO_7, now it works.
-
@ctilley79 said in BLTouch doesn't always deploy Duet 3 6HC:
Any update on this? just broke a bltouch probe because of this issue.
I've poked DC42 to take a look again when he has a moment.
Were you able to try a different BLTouch?
-
Hi was this issue solved? I’m having this issue ive brand new bltouch connected to io7
-
@bzad said in BLTouch doesn't always deploy Duet 3 6HC:
Hi was this issue solved? I’m having this issue ive brand new bltouch connected to io7
Probably best to start a new thread with your issue.
