Error: Probe already triggered at start of probing move

joe92

@phaedrux M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Pin 'zstop' is not free
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 558C

joe92

Error: Pin 'zstop' is not free
Is something broken on the board or is it a config setting?

Phaedrux

@joe92 said in Error: Probe already triggered at start of probing move:

Error: Pin 'zstop' is not free
Is something broken on the board or is it a config setting?

No I think that's because your zstop pin is already been used when you run M98 P"config.g"

0:/macros/Probe_Scripts/activate_z_switch.g
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
M558 P5 C"zstop" H5 F400 T3000 ;Z Probe connector to Z endstop

This macro gets called and uses zstop. And when you send M98 config.g it tries to use zstop again in your m574 command, but it's already in use from that macro.

@joe92 said in Error: Probe already triggered at start of probing move:

have this error message when homing the z axis.

Can you post your homing files and bed.g/mesh.g files as well?

joe92

@phaedrux ;

bed.g
; called to perform automatic bed compensation via G32
; setup for quad belt gantry

M561 ; Clear any existing bed transform
G28 ; home

M98 P"/macros/probe_scripts/activate_z_probe.g" ;activate inductive z-probe

; Probe bed at these 4 points:
G30 P0 X290 Y290 H0 Z-99999
G30 P1 X290 Y60 H0 Z-99999
G30 P2 X60 Y60 H0 Z-99999
G30 P3 X60 Y290 H0 Z-99999 S4

G28 Z ; Home Z Axis

; homeall.g
; called to home all axes

G91 ; Relative

G1 H2 Z5 F2000 S2 ; Lower bed 15mm
G1 H1 X-300 Y-300 F2000 S1 ; Coarse home X and Y
G1 H1 X-300 S1 ; Coarse X in case Y homed first
G1 H1 Y-300 S1 ; Coarse Y in case X homed first
G1 H0 X5 Y5 F2000 ; Move away from the endstops
G1 H1 X-300 F360 S1 ; Fine home X
G1 H1 Y-300 F360 S1 ; Fine home Y

M98 P"/macros/print_scripts/xy_current_high.g" ; Restore motor currents
G90 ; Absolute positioning

; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z Switch

G30 Z-99999 ; Probe Z Switch

G0 Z5

M98 P"/macros/probe_scripts/goto_nozzle_scrubber_and_scrub.g" ; Scrub Nozzle

; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z Switch

G30 Z-99999 ; Probe Z Switch

G0 Z20

M98 P"/macros/probe_scripts/activate_z_probe.g" ; Activate Z Probe

joe92

@phaedrux

; homez.g
; called to home the Z axis
;

; Lift Z relatively to current position
G91
G1 H2 Z5 F2000 S2

; Back to absolute positioning
G90

; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z Switch

G30 Z-99999 ; Probe Z Switch

G0 Z5

M98 P"/macros/probe_scripts/goto_nozzle_scrubber_and_scrub.g" ; Scrub Nozzle

; Go to z switch and home z axis
M98 P"/macros/probe_scripts/activate_z_switch.g" ; Activate Z Switch
M98 P"/macros/probe_scripts/goto_z_switch.g" ; Go To Z Switch

G30 Z-99999 ; Probe Z Switch

G0 Z20

M98 P"/macros/probe_scripts/activate_z_probe.g" ; Activate Z Probe

Phaedrux

What is the order of operations that gets you to the error message?

Turn on the printer and press homeall in DWC?

Just trying to understand the flow of gcode commands.

However, if it's worked for 500 hours without issue up until now with the same config, and the same config works on your other printer, then I have to think it's a hardware issue. Most likely with the probe itself or with it's wiring.

joe92

@phaedrux
Yes, home all is the first thing I do, but I have now installed the duet from the other printer and everything works. I completely erased the board with the defect and wrote it with the latest software, but the error is still there in the other printer

Phaedrux

can you tell me/show me the wiring for your probe?

Can you grab some photos of the board with the problem?

joe92

@phaedrux

joe92

@phaedrux I can take the photos after work

joe92

found the fault in the cable to the z switch. a broken wire has trigged the z stop