Duet 2 with Duex 5, cannot get BLtouch to function

Macgyver

so just to make sure that I understand, the P0 ref is just a arbraturary number that you assign to PWM5 by ref both in the same M950 command?

Similar in Marlin to making a ref call to the pins file, but instead of pins you call the Duex.pwm5 file?

instead of just fixing it trying to understand where the call is coming from that's all.

I think this is correct?

Phaedrux

@macgyver basically. M950 S0 creates servo pin 0. It's an index number. You can have many servo pins. S1 S2 S3 etc. And each one has a physical pin assigned to it. In this case duex.pwm5.

And when you want to target that servo pin you target the index number in your servo movement command. M280 p0 or p1 p2 etc.

Macgyver

@phaedrux

that's awesome, thank you for the info,

I appreciate the time 2 you both.

Macgyver

still have a bit of an issue, when I am doing the dynamic testing I run the M401 and M402 and now the probe deploys and retracts as it should,

(note; the blue light only comes on after I deploy the first time, will not come on at boot)

The Probe status in the dashboard shows zero "0"
when I run the M401 / M402 the BLtouch status does not change

However when I unplug one of the white/black wire the BLtouch status the status goes to "1000"

this tells me that the BLtouch is triggering however the input is not being seen by the Duet.

My M574 is defined with a type S2, and I have removed the M307 from the config.g as I am using firmware version 3X.

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X5 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:485 Y15:485 S23.5 ; define mesh grid

Macgyver

Looks like I may have it,

originally in my config.g I had the following
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

I read in a note about version 3 firmware that the S2 switch is intended for non-Z axis only.

Updated the command to

M574 Z1 S1 ; configure Z-probe endstop for low end on Z

now when the probe is triggered the bed stops and pulls down as it should.

Still no blue light on boot up but all functionality tests appear to work. After the first deployment of the BLtouch the blue light comes on not an issue. is this something I should rectify?

Phaedrux

@macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

The Probe status in the dashboard shows zero "0"
when I run the M401 / M402 the BLtouch status does not change

That's not what the trigger status is watching for. Deployment is totally separate. It will only show triggered very briefly when the pin is deployed and gets pushed back up. It will only change the display for a split second and go back to un triggered. You may not even see it there.

@macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

M574 Z1 S1 ; configure Z-probe endstop for low end on Z

M574 will have no effect on the probe settings. Just M558 and G31 apply to the probe.

@macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

but all functionality tests appear to work

That's all that matters.

Macgyver

ok, thanks again for your time, I appreciate it.

dc42

@macgyver is it working now?

matej1006

@dc42 Hello sorry for stealing this topic but i have same problem and on web shows 1000 for Z-PROBE
when i unplug bl touch goes to zero?

Phaedrux

@matej1006 said in Duet 2 with Duex 5, cannot get BLtouch to function:

@dc42 Hello sorry for stealing this topic but i have same problem and on web shows 1000 for Z-PROBE
when i unplug bl touch goes to zero?

Please create a new thread.

Macgyver

Hi Guys

Sorry, I missed the update, Yes all is working now. thanks again for your help.

Up to the last tests I was doing it was a coding issue, as it turns out somewhere along the line the BLtouch sensor went bad. I wrote a script to probe 10 times and report the divination. the number was never the same, or even close for that point. turned out the touch was bad.