Issue with SZP on Secondary Idex Toolhead

[Superbrain8]

@T3P3Tony here is my homeall file

M400
 
; Home X, Y, U simultaneously
G91
 
; Trinamic tuning
 
G1 H2 X0.00625                                                                      ; 1 microstep movement to energize steppers
 
G4 P150                                                                             ; pause for 150ms
 
G1 H2 Y0.00625                                                                      ; 1 microstep movement to energize steppers
 
G4 P150                                                                             ; pause for 150ms
 
G1 H2 U-0.00625                                                                     ; 1 microstep movement to energize steppers
 
G4 P150                                                                             ; pause for 150ms
 
G1 H2 Z0.0000625                                                                    ; 1 microstep movement to energize steppers
 
G4 P150                                                                             ; pause for 150ms
 
G1 H2 Z20 F2000                                                                     ; raise head 10mm to keep it clear of the bed
G1 H1 X-99999 Y-99999 U99999 F6000                                                  ; coarse home X, Y and U
G1 H2 X4 Y4 U-4 F600                                                                ; move 4mm away from the homing switches
G1 H1 X-10 Y-10 U10                                                                 ; fine home X, Y and U
G1 H1 Z-99999 F6000                                                                 ; coarse home Z
G1 H2 Z4 F6000                                                                      ; move 4mm away from the homing switches
G1 H1 Z-10 F600
G90
G1 Z10 F6000
T0                                                                                  ; Make sure T0 is selected -> ABL Probe
; Now home Z using the Z probe
G1 X{155 - sensors.probes[0].offsets[0]} Y{155+sensors.probes[0].offsets[1]} F10000 ; Move to the center of the bed
G30                                                                                 ; probe the bed and set Z height
G1 Z10 F3000                                                                        ; make sure to clear the bed
G1 X{move.axes[0].min+1} F10000                                                     ; Move Toolhead to parking Position

the issue is not present on 3.5.3

the printer has 2 endstops mounted on Z low to level the gantry when homing

[T3P3Tony]

@Superbrain8

To confirm you have rolled back to 3.5.3 and the same homing file works? Does it work in 3.5.4?

Also please confirm these:

Was the software reset this message applies to the reset 1min 20s before you ran the report? (i.e. did you run that M122 at 15:37 approx today?

When you says it resets the wifi to home the machine, does it actually reset the entire board (i.e. the symptom of DWC disconnecting is actually the board resetting)?

Does this happen everytime you home the machine?

[Superbrain8]

the heattaskstuck error where from updating the firmware.
the software reset where from the homing yea.
rolling back to 3.5.4 keeps the homing in working condition

[T3P3Tony]

@Superbrain8 thanks. also:

When you says it resets the wifi to home the machine, does it actually reset the entire board (i.e. the symptom of DWC disconnecting is actually the board resetting)?

Does this happen everytime you home the machine?

[Superbrain8]

homing the machine causes it to get stuck when attempting to home the Z axis it times out and the wifi module seems to reset, that is atleast what i can see on the panel due that reconnects to the Wifi on timeout

[T3P3Tony]

@Superbrain8 ok interesting. can you run it a couple of times on 3.6.0beta4 and post the M122 after each one. I am looking to see if the error is identical.

[T3P3Tony]

@Superbrain8 also please send a picture of the paneldue console when this happens for me to double check.

[Superbrain8]

Homed 3 times and ran M122 after each unsuccessful home

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-beta.4 (2025-02-11 09:50:58) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
Used output buffers: 1 of 40 (24 max)
=== RTOS ===
Static ram: 94732
Dynamic ram: 97496 of which 12 recycled
Never used RAM 49228, free system stack 196 words
Tasks: NETWORK(1,ready,14.4%,207) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,353) TMC(4,nWait 6,0.8%,99) CanReceiv(6,nWait 1,0.1%,794) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) MAIN(1,running,83.3%,659) IDLE(0,ready,0.5%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:58 ago, cause: software
Last software reset at 2025-02-22 17:15, reason: HeatTaskStuck, Gcodes spinning, available RAM 48832, slot 2
Software reset code 0x0143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200117d8 Task Move Freestk 1018 ok
Stack: 00000000 2001112c 10000000 e000e000 20000f4c 0009f1c5 0009f9b0 61000000 20016de8 20023598 20023598 20023510 00053fd1 00006a74 00000001 00056db3 a5a5a5a5 20023598 20023518 00000000 a5a5a500 4186a760 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 90, r/w errs 0/1, ifcnt 31, reads/writes 3046/14, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 48, r/w errs 0/1, ifcnt 31, reads/writes 3046/14, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 2, r/w errs 0/1, ifcnt 31, reads/writes 3045/14, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 78, r/w errs 0/1, ifcnt 31, reads/writes 3045/14, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 2, r/w errs 0/1, ifcnt 31, reads/writes 3046/14, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000803, drives owned 0x00000803
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== Filament sensors ===
Driver 11: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
Driver 10: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 550, received 2913, lost 0, ignored 0, errs 0, boc 0
Longest wait 3ms for reply type 6061, peak Tx sync delay 186, free buffers 26 (min 25), ts 277/276/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 6.32ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.41, flash size 2097152, free heap 39348
MAC address f0:08:d1:02:e5:fa
IP address 192.168.178.47
Signal strength -39dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-beta.4 (2025-02-11 09:50:58) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
Used output buffers: 1 of 40 (21 max)
=== RTOS ===
Static ram: 94732
Dynamic ram: 97508 of which 0 recycled
Never used RAM 49228, free system stack 192 words
Tasks: NETWORK(1,ready,11.5%,205) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,356) Move(4,nWait 6,0.0%,353) TMC(4,nWait 6,0.8%,103) CanReceiv(6,nWait 1,0.1%,794) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,352) MAIN(1,running,85.2%,659) IDLE(0,ready,1.5%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:18 ago, cause: software
Last software reset at 2025-02-22 17:17, reason: HeatTaskStuck, Gcodes spinning, available RAM 49012, slot 0
Software reset code 0x0143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200117d8 Task Move Freestk 1018 ok
Stack: 00000000 2001112c 10000000 e000e000 20000f4c 0009f1c5 0009f9b0 61000000 20016de8 20023598 20023598 20023510 00053fd1 0001491c 00000001 00056db3 a5a5a5a5 20023598 20023518 00000000 a5a5a500 418357f0 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 92, r/w errs 0/1, ifcnt 48, reads/writes 933/14, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 48, r/w errs 0/1, ifcnt 48, reads/writes 933/14, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/1, ifcnt 48, reads/writes 932/14, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 78, r/w errs 0/1, ifcnt 48, reads/writes 932/14, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/1, ifcnt 48, reads/writes 933/14, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000803, drives owned 0x00000803
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== Filament sensors ===
Driver 11: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
Driver 10: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 199, received 943, lost 0, ignored 0, errs 0, boc 0
Longest wait 3ms for reply type 6061, peak Tx sync delay 6, free buffers 26 (min 25), ts 87/86/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 5.20ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.42, flash size 2097152, free heap 35904
MAC address f0:08:d1:02:e5:fa
IP address 192.168.178.47
Signal strength -41dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-beta.4 (2025-02-11 09:50:58) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
Used output buffers: 2 of 40 (22 max)
=== RTOS ===
Static ram: 94732
Dynamic ram: 97508 of which 0 recycled
Never used RAM 49228, free system stack 194 words
Tasks: NETWORK(2,nWait 7,11.7%,225) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,371) Move(4,nWait 6,0.0%,353) TMC(4,delaying,0.8%,99) CanReceiv(6,nWait 1,0.1%,794) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,353) MAIN(1,running,85.2%,659) IDLE(0,ready,1.3%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,255), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:19 ago, cause: software
Last software reset at 2025-02-22 17:17, reason: HeatTaskStuck, Gcodes spinning, available RAM 49012, slot 1
Software reset code 0x0143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200117d8 Task Move Freestk 1018 ok
Stack: 00000000 2001112c 10000000 e000e000 20000f4c 0009f1c5 0009f9b0 61000000 20016de8 20023598 20023598 20023510 00053fd1 00009760 00000001 00056db3 a5a5a5a5 20023598 20023518 00000000 a5a5a500 41836d80 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 92, r/w errs 0/1, ifcnt 65, reads/writes 1016/14, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 46, r/w errs 0/1, ifcnt 65, reads/writes 1015/14, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/1, ifcnt 65, reads/writes 1015/14, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 78, r/w errs 0/1, ifcnt 65, reads/writes 1015/14, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/1, ifcnt 65, reads/writes 1016/14, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000803, drives owned 0x00000803
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== Filament sensors ===
Driver 11: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
Driver 10: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 213, received 1029, lost 0, ignored 0, errs 0, boc 0
Longest wait 2ms for reply type 6061, peak Tx sync delay 3, free buffers 26 (min 25), ts 94/93/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 5.17ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.42, flash size 2097152, free heap 35908
MAC address f0:08:d1:02:e5:fa
IP address 192.168.178.47
Signal strength -41dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

and here the Picture of the panel due Console

[T3P3Tony]

@Superbrain8

It looks like from the M122 that the whole board is resetting on homing

Here is an experimental build that it would be good to test please.
Duet3Firmware_Mini5plus.uf2

It is an internal build to fix a different issue but that also presented as a heattaskstuck so they may be related,,

[Superbrain8]

@T3P3Tony installed the new firmware, homed the printer but it still fails to home the Z axis
here is a M122 after the failed home attempt

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-beta.4+2 (2025-02-18 10:06:11) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: YQ6KF-K096U-D65J0-40KMG-4G03Z-H28XK
Used output buffers: 1 of 40 (22 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 97496 of which 12 recycled
Never used RAM 49196, free system stack 188 words
Tasks: NETWORK(1,ready,10.2%,235) LASER(5,nWait 7,0.0%,269) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,353) TMC(4,nWait 6,0.8%,99) CanReceiv(6,nWait 1,0.1%,794) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,353) MAIN(1,running,86.2%,659) IDLE(0,ready,1.8%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,269), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:14 ago, cause: software
Last software reset at 2025-02-23 14:59, reason: HeatTaskStuck, Gcodes spinning, available RAM 49124, slot 0
Software reset code 0x0143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200117d8 Task Move Freestk 1018 ok
Stack: 00000000 2001112c 10000000 e000e000 20000f4c 0009f255 0009fa40 61000000 20016e08 200235b8 200235b8 20023530 00053f71 00007ff0 00000001 00056d53 a5a5a5a5 200235b8 20023538 00000000 a5a5a500 418a2040 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 4, r/w errs 0/1, ifcnt 63, reads/writes 741/14, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 10, r/w errs 0/1, ifcnt 63, reads/writes 741/14, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/1, ifcnt 64, reads/writes 741/14, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 2, r/w errs 0/1, ifcnt 63, reads/writes 741/14, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/1, ifcnt 64, reads/writes 741/14, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== Filament sensors ===
Driver 11: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
Driver 10: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 168, received 761, lost 0, ignored 0, errs 0, boc 0
Longest wait 2ms for reply type 6061, peak Tx sync delay 351, free buffers 26 (min 25), ts 70/69/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 5.21ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.42, flash size 2097152, free heap 39332
MAC address f0:08:d1:02:e5:fa
IP address 192.168.178.47
Signal strength -42dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

[gloomyandy]

@Superbrain8 If you reduce the length of the homing moves you are using (they are currently set to -99999) to something like -9999, do you still see the board reset?

[Superbrain8]

@gloomyandy that fixed that issue, thanks.
will see how the original issue for this post is fixed too

[Superbrain8]

no that one still persists, the mesh is scanned in the Y axis instead of the X Axis but is generated as if scanned in the X Axis

[droftarts]

@Superbrain8 said in Issue with SZP on Secondary Idex Toolhead:

no that one still persists, the mesh is scanned in the Y axis instead of the X Axis but is generated as if scanned in the X Axis

I suspect this is because of the axis mapping of the second axis. It will need @dc42 to look at it, and probably fix in firmware.

As a workaround for now, I think your options will be either to put the SZP on the primary toolhead, or swap the X and U axes, so that the second tool is referred to as the X axis, and the first tool is the U axis.

Ian

[dc42]

@Superbrain8 thanks, we created this issue:

https://github.com/Duet3D/RepRapFirmware/issues/1094

It's scheduled to be fixed between 3.6.0-rc.1 and 3.6.0 stable.

gloomyandy created this issue 25 Feb 2025, 19:17 in Duet3D/RepRapFirmware

closed Long homing moves can cause HeatTaskStuck software reset and/or Code 7 halts #1094

[dc42]

@Superbrain8 said in Issue with SZP on Secondary Idex Toolhead:

no that one still persists, the mesh is scanned in the Y axis instead of the X Axis but is generated as if scanned in the X Axis

Please try the 3.6.0-rc.2+1firmware from https://www.dropbox.com/scl/fo/kj7gwwzxg5lhe26twph5z/AAdwkPCTYi6bcogLmIIIup4?rlkey=8oo6z5il7wzk2u5b7qpykf3qv&dl=0.

[Superbrain8]

@dc42 Thanks for the reply,
running this firmware resolves the issue, it now Scans as expected in the X axis and the mesh generated also looks correct.

[dc42]

@Superbrain8 thanks for confirming!