Solved Dual Z homing issue - only one motor moves

[happycaribou77fr]

Hello,

I have passed quite a few hours on trying to troubleshoot the dual Z homing on my duet:

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3 (2021-06-15)
Duet WiFi Server Version: 1.26

upon startup, if I manual enter in the console:
G91
G1 H2 Z30 F6000
G1 H2 Z-30 F6000
All good, as both motors are moving in the right direction and the bed is moving +/-3cm.
M122:
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 192210, 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

if I run after
G1 H1 Z-30 F1800
only 1 motor moves... which is an issue for homing. I have no clue what is wrong.....

Could you please help?

Below is my config.g
I tried switch motor cables Z1<->Z2 and it just changed the problem to the other motor.

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.9 on Sat Nov 28 2020 20:40:10 GMT+0100 (Central European Standard Time)

; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"HyperCube"                             ; set printer name
M669 K1                                        ; select CoreXY mode

; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0 S0                                     ; physical drive 0 goes forwards
M569 P1 S0                                     ; physical drive 1 goes forwards
M569 P2 S0                                     ; physical drive 2 goes forwards
M569 P3 S1                                     ; physical drive 3 goes forwards
M569 P4 S0                                     ; physical drive 4 goes forwards
M584 X1 Y0 Z2:4 E3                             ; set drive mapping
M350 X256 Y256 Z256 E64 I0                     ; configure microstepping without interpolation
M92 X1597.00 Y1597.00 Z6407.00 E1560.00        ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00            ; set maximum instantaneous speed changes (mm/min)
M203 X50000.00 Y50000.00 Z1800.00 E15000.00    ; set maximum speeds (mm/min) 
M201 X500.00 Y500.00 Z20.00 E3000.00           ; set accelerations (mm/s^2)
M906 X800 Y800 Z1200 E800 I30                  ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout

M671 X-35:200 Y442:200 

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X400 Y400 Z380 S0                         ; set axis maxima

; 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 S1 P"zstop+e1stop"                     ; configure active-high endstop for low end on Z via pin zstop

; Z-Probe
;BL Touch
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater
M950 S5 C"exp.heater7"
M558 P9 C"^zprobe.in" H5 F120 T6000 A10 S0.01      ; 10 number of times to probe each point and Tolerance when probing multiple times, default 0.01mm
G31 X28 Y20 Z0.7 P25

;Piezzo sensor
;M558 P1 C"!zprobe.in" R0.6 H6 F1800 A20 S0.005 K0             
;G31 P250 X0 Y0 Z0                            ; set Z probe trigger value, offset and trigger height

; define mesh grid - probe from X=10 to 190, Y=10 to 190mm with a mesh spacing of 20mm
M557 X30:395 Y25:395 S20                      

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                          ; create bed heater output on bedheat and map it to sensor 0
M307 H0 A175.3 C811.3 D1.6 S1.00 V23.8 B0      ; Auto-Pid values
M140 H0                                        ; map heated bed to heater 0
M143 H0 S120                                   ; set temperature limit for heater 0 to 120C

M308 S1 P"e0temp" Y"thermistor" T100000 B4138  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 R2.108 C184.8 D5.15 S1.00 V24.1
M143 H1 S280                                   ; set temperature limit for heater 1 to 280C

M308 S2 Y"drivers" A"DRIVERS"   ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S4 Y"mcu-temp" A"MCU"   ; configure sensor 3 as thermistor on pin e1temp for left stepper

; Fans
M950 F0 C"fan0" Q10000                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned on

M950 F1 C"fan1" Q4                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T50

;M950 F2 C"fan2" Q30                           ; create fan 2 on pin fan1 and set its frequency - not used
;M106 P2 H2:4 L0.0 X0.05 B0.5 T45:55            ; set fan 2 value, turn on at 50% if the CPU temperature reaches 45C, and increase to full speed gradually as the temperature rises to 55C

; Tools
M563 P0 D0 H1 F0                               ; 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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                              ; enable support for PanelDue


; Led Strip
M950 P0 C"exp.heater4" Q500 		; Red
M950 P1 C"exp.heater3" Q500 		; Green
M950 P2 C"exp.heater5" Q500 		; Bleu
M950 P3 C"exp.heater6" Q500 		; White

; Calibrating the CPU temperature
M912 P0 S1.5

;Configuring low power automatic pause and save
M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

;
M929 P"eventlog.txt" S3
;Activating the mesh bed compensation
;G29 S1

[jay_s_uk]

@happycaribou77fr it may be unrelated but running 256 steps is really not recommended as it will overload the CPU.
Best to run them at 16 microsteps with interpolation

[droftarts]

@happycaribou77fr I’d guess one of the endstops is already triggered. Probably faulty wiring, or connected to the wrong pins on the Duet. What does M119 (check endstop status) report when you press each endstop? Or install the endstop status plugin in DWC.

Ian

[happycaribou77fr]

@droftarts
I tried the end stop idea. Change the cables and end stops but nothing.

M119
Endstops - X: at min stop, Y: at min stop, Z: at min stop, Z probe: at min stop

As I have 2 independent Z stops, M119 stays the same in 4 states of 2 Z stops (open/open, triggered/open, open/triggered, triggered/triggered).
The board seems to detect it correctly as the open or triggered state are in adequation with the status of the led (light/no light) on the board.
I tried also to remove all the other cable connections except the 2 motor cables and 2 Z stops and doing a Z homing. No change.

[Phaedrux]

@happycaribou77fr said in Dual Z homing issue - only one motor moves:

As I have 2 independent Z stops, M119 stays the same in 4 states of 2 Z stops

Change your endstop mapping to have separate endstops and check it again.

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

[happycaribou77fr]

Thank you all for your feedback!
In the end, I found that the issue: A bad crimp (home made) inside the connector of the endstop to the board..... and the same for the second cable tested..... bad luck or bad crimping skills
Not visible at first. But now all is back to normal