Z probe wont stop on homing

Jaran

Hello there! I have been running my printer with a BLTouch for a few months and it has been working perfectly.

However now the printer wont stop when homing the Z axis and the Z probe is beeing triggered. I have done two changes sinse I knew it was working.

First change I did was updating to the latest firmware(1.20), and the second change I have done is swappingout the hotend from a E3D V6 clone to a genuine one.

Here is what I have checked so far:

I have went over the wiring several times(these were never disconnected sinse it was last working)
Tested all macros, they all work as intended. When deploying the probe with "M280 P7 S10 I1" the probe redeploys when beeing pushed up. Is that how it is supposed to be? When running "M280 P7 S60 I1" I get 1000 as Z-Probe value in the duet webcontrolpanel.

Here is my homez file:

[[language]]
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Wed Oct 25 2017 13:35:35 GMT+0200 (Vest-Europa (sommertid))

; Lift Z relatively to current position
G91
G1 Z5 F6000

M98 Pdeployprobe.g

; Move Z down until the switch triggers
;G1 Z-295 S1 F1800
G30

; Back to absolute positioning
G90

; Tell the firmware where we are
G92 Z1.5

M98 Pretractprobe.g

Here is my config file:

[[language]]
; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Oct 25 2017 13:35:35 GMT+0200 (Vest-Europa (sommertid))

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z290 S0 ; Set axis maxima

; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X1 Y1 S1 ; Define active high microswitches
M558 P5 X0 Y0 Z1 H5 F100 T2000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 X0 Y0 Z1.52 P25; Set Z probe trigger value, offset and trigger height ;;;;Z1.57
M557 X0:290 Y0:290 S100 ; Define mesh grid

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z396.08 E108.6 ; Set steps per mm
M566 X900 Y900 Z24 E100 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z400 E10000 ; Set maximum speeds (mm/min) M203 X6000 Y6000 Z400 E10000
M201 X6000 Y6000 Z200 E6000 ; Set accelerations (mm/s^2) M201 X6000 Y6000 Z200 E6000
M906 X800 Y800 Z800 E1600 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S280 ; Set maximum heater temperature to 280C
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 T100000 B4725 C0 R4700 ; Set thermistor + ADC parameters for heater 1    7.06e-8
M307 H7 A-1 C-1 D-1 ;

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured
;M556 S20 X0 Y0 Z0
M579 X1.003 Y1.005

Does anyone have any idea what might have happend?

pao_wikhan

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

Jaran

@pao_wikhan:

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