Error: Probe already triggered at start of probing move

joe92

can nobody help me ? the probe is active all the time even if i disconnect the cables. I loaded the config on my second print for testing and I can't find any errors there (both prints are voron 2)

Phaedrux

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

I loaded the config on my second print for testing and I can't find any errors there

If the same config works on the other printer with the same hardware that would mean there is a wiring problem with the probe.

joe92

@phaedrux at the moment only x and x are homing. at z comes the error message but then tried g30 s-1 and the probe works normally. I also disconnected the probe from the board but the value on the web control remains at 1000

Phaedrux

Can you send M122 and M98 P"config.g" and post the results?

joe92

@phaedrux m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJ3S0-7JKFJ-3SD6M-1TFHG
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75852 of which 28 recycled
Never used RAM 14660, free system stack 174 words
Tasks: NETWORK(ready,12.9%,237) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) DUEX(notifyWait,0.0%,24) MAIN(running,86.5%,443) IDLE(ready,0.4%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:59 ago, cause: power up
Last software reset at 2022-01-25 19:19, reason: User, GCodes spinning, available RAM 11676, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 31.8, current 37.5, max 37.7
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-01-26 05:40:12
Cache data hit count 4294967295
Slowest loop: 6.95ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== DueX ===
Read count 1, 0.33 reads/min
=== Network ===
Slowest loop: 15.91ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 8c:aa:b5:d5:7e:45
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23968
WiFi IP address 192.168.0.67
WiFi signal strength -39dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0

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