Z probe wont stop on homing

Jaran

you have a bad naming for the deploy and retract
[c]https://duet3d.com/wiki/Connecting_a_Z_probe[/c]

[[language]]
2\. Create a deployprobe.g file (in the /sys folder of the SD card) it should contain the following single command:

M280 P3 S10 I1

3\. Create a retractprobe.g file (in the /sys folder of the SD card) it should contain the following single command:

M280 P3 S90 I1

Im using a diffrent pin, so P7 is what it should be.

pao_wikhan

then change 3 to 7

Jaran

@pao_wikhan:

then change 3 to 7

Uh, I can give that a go a bit later on, but I can't see how this is a solution. It has been working with the current setup for a long time, and suddenly it does not. No idea if it is due to the changes I have made or not.

Jaran

Changed it over to P3 now and it made no diffrence. Still facing the same issue.

Edit: I guess I missread your first reply. I do have the macros you quoted, and I have them assigned to the right pins. The macros work as intended when deploying them. The Z Prode does deploy when homing starts, but when the probe is triggered by the glass plate the homing does not stop, it ignores the triggering point.

Dan-dekalb

I'm just completing a conversion to a Duet, and I'm seeing the exact same thing. The BLTouch is not in error state (red LED flashing). If I issue:
M280 P3 S10 I1 ; BLTouch Sensor deploy
The probe deploys. Then every time I trip the probe, it extends again. If I issue:
M280 P3 S10 I1 ; BLTouch Sensor deploy
M280 PS3 S60 I1 ; BLTouch Sensor test mode
The probe deploys, Z-Probe value is initially 0. When I trip the sensor, it shows Z-Probe value of 1000.
When I try to run a G32, the probe deploys, and if I manually trip it, it just keeps going down. If I let it hit the bed, the servo's skip when it hits the bed and then it moves to the next test point. It never raises up to go to the next point.

I am running 1.21RC1, but have tried 1.20 and 1.19, same result with each. I'd greatly appreciate any hints or thoughts.

Thanks in advance.

Jaran

@Dan-dekalb:

I'm just completing a conversion to a Duet, and I'm seeing the exact same thing. The BLTouch is not in error state (red LED flashing). If I issue:
M280 P3 S10 I1 ; BLTouch Sensor deploy
The probe deploys. Then every time I trip the probe, it extends again. If I issue:
M280 P3 S10 I1 ; BLTouch Sensor deploy
M280 PS3 S60 I1 ; BLTouch Sensor test mode
The probe deploys, Z-Probe value is initially 0. When I trip the sensor, it shows Z-Probe value of 1000.
When I try to run a G32, the probe deploys, and if I manually trip it, it just keeps going down. If I let it hit the bed, the servo's skip when it hits the bed and then it moves to the next test point. It never raises up to go to the next point.

I am running 1.21RC1, but have tried 1.20 and 1.19, same result with each. I'd greatly appreciate any hints or thoughts.

Thanks in advance.

I had the same issue with a 3DTouch which is pretty much the same as a bltouch, and then I bought a genuine bltouch. Now the bltouch has the same issue, so think the sensor itself is bricked, which does not really make sense as I havent touched mine. Atleast when I swapped out the 3DTouch for a bltouch it was working fine until yesterday.

dc42

Can you confirm that you have the black and whites wires connected to the Z probe connector Gnd and In pins?

Jaran

@dc42:

Can you confirm that you have the black and whites wires connected to the Z probe connector Gnd and In pins?

I do have that, yes.

dc42

I suggest you work through https://duet3d.com/wiki/Test_and_calibrate_the_Z_probe. If you can't get Z movement to stop when the probe is triggered while executing G30, that points to insufficient output from the probe. I think I read recently that someone had to change a resistor value. You could also try using P1 in the M558 command and a low threshold such as P250 in the G31 command.

Jaran

@dc42:

I suggest you work through https://duet3d.com/wiki/Test_and_calibrate_the_Z_probe. If you can't get Z movement to stop when the probe is triggered while executing G30, that points to insufficient output from the probe. I think instead recently that someone had to change a resistor value. You could also try using P1 in the M558 command and a low threshold such as P250 in the G31 command.

I have checked out the test and calibration page you linked, and it all seems to work as intended - except that the trigger point is not beeing picked up. The pin is getting pushed down as soon as its triggered and repeats. I did try out P1 too without any success.

I havent changed any wiring or done any editing in the configs from the last point it was working, all I did was update the firmware. If the firmware did not do any changes regarding this, I guess its safe to say the sensor is broken? Can't say I understand how though..