BLTouch doesn't always deploy Duet 3 6HC

SneakyTiki

@dc42 That I can confirm, it was the exact same code that ran at start-up, my macros just happened to call it multiple times throughout normal printer operation after initial power on (It lived in a file called printer_bedmesh.g, which was called by config.g on startup, but also by homez.g, homeall.g, and bed.g)

And when I was narrowing it down after your question, I literally just powered on the printer, sent M401, M402 to confirm operation, then sent M558 P9 and M401 and M402 no longer responded.

fcwilt

@SneakyTiki said in BLTouch doesn't always deploy Duet 3 6HC:

@fcwilt Yes, it was the full config code for the sensor.

Here is my probe configuration macro. It is called in several places.

M950 S0 C"duex.pwm5"                                ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H2 F120 T12000 R0.2 A1 S0.03  ; set type for BLtouch and set default parameters
G31 P25 X0 Y24.5 Z2.400                             ; set trigger value, offset and trigger height (larger = closer)

BUT this is under firmware 3.2.0 running on a Duet 2 WiFi/Duex 5 combo.

I have a spare BLTouch - I will connect it to my Duet 3 MB6HC and set what happens.

Frederick

SneakyTiki

@fcwilt I was also surprised to find an issue that sounded similar to mine considering the user had completely different hardware and firmware to me. But hey, glad I looked, helped me fix my issue. Maybe it'll help someone else

Nuramori

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.

Veti

@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.

ctilley79

@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.

ComedianTF2

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

Nuramori

@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.

ctilley79

@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?

Nuramori

@ctilley79 It was that it would deploy but not trigger.

ctilley79

@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.

User3D

@ctilley79 I wanna know if you have deployprobe.g and retractprobe.g in /sys only !!!!! (If you do , can you post them here)

ctilley79

@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 BLTouch

M280 P0 S90 ; retract BLTouch

User3D

@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 .

ctilley79

Any update on this? just broke a bltouch probe because of this issue.

SJI

I was having issues on IO_6, no deploy. checked wiring etc, all ok from that end. Changed to IO_7, now it works.

Phaedrux

@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?

bzad

Hi was this issue solved? I’m having this issue ive brand new bltouch connected to io7

Phaedrux

@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.