Random Hard Fault resets on Duet 3 Mini WiFi

Exerqtor

Still haven't had one single event on 3.5.3-debug other than that one without any output. So I'm moving back over to 3.6.0-debug again so that I can get some prints done.
With nothing happening in well over 72hours I doubt anything will tbh.

jovo0911

After switching from the Maestro to the Mini 5 WiFi, my printer occasionally stopped or crashed without any apparent reason. I found this thread and installed the 3.6.0-debug firmware from dc42. Since then, I’ve completed over ten prints, including some taller than 150mm and others over 4 hours long, with no crashes. My printer is a CoreXY setup with dual Z-axis and a single extruder.

dc42

@jovo0911 thanks. I've established that this issue does not cause the same type of reset in 3.6.0 beta1 that it does in 3.5.x and 3.4.x. What I don't know is whether it causes any other issues in 3.6.0 beta1. I've also developed a workaround for the issue in 3.5.3.

jovo0911

Should I go back to 3.4.6 and wait? (The Maestro ran fine with that version.) I started with 3.5.0 on the Mini 5 and initially thought the board might have a hardware issue.
But now the printer is running smoothly with the 3.6.0-debug firmware.

dc42

@jovo0911 the issue discussed in this thread is unique to the Duet 3 Mini WiFi.

wschadow

@dc42 Here is some feedback from my side. For about a week I tried 3.6.0-beta1-2 on a Duet3Mini5 where everything was connected directly to the board. Good news: WiFi and printer ran without error. Observations:

YAP connects, but no data is displayed in YAP. M115 does not return anything.
The old home sequence doesn't work without change

; =========================================================================================================
; home y axis
; =========================================================================================================
;
M400                                                                   ; wait for current moves to finish
G1 H2 Y0.5 F1000                                                       ; energise motors to ensure they are not stalled
M400                                                                   ; wait for current moves to finish
G1 H1 Y5 F1000                                                         ; move slowly away
G1 H1 Y-260 F1800                                                      ; move quickly to x axis endstop and stop there (first pass)
G1 H2 Y5 F1000                                                         ; go back a few mm
G1 H1 Y-10 F1800                                                       ; move slowly to x axis endstop once more (second pass)

G28
Error: G1: Homing move abandoned because driver 3 is moving too slowly for stall detection

It had to be changed to

; =========================================================================================================
; home y axis
; =========================================================================================================
;
M400                                                                   ; wait for current moves to finish
G1 H2 Y0.5 F2000                                                       ; energise motors to ensure they are not stalled
M400                                                                   ; wait for current moves to finish
G1 H1 Y5 F2000                                                         ; move slowly away
G1 H1 Y-260 F1800                                                      ; move quickly to x axis endstop and stop there (first pass)
G1 H2 Y5 F2000                                                         ; go back a few mm
G1 H1 Y-10 F1800                                                       ; move slowly to x axis endstop once more (second pass)
;

wschadow

@dc42 Today I tried 3.6.0-beta1-2 on a Dual extruder where the extruders have a can board. So far, this works as well.