Duet stops permanently and freezes mid-print

EDG5000

After having freezes of short durations, which I was able to avoid completely by switching away from Simplify3D.

After a few successful prints with KISSlicer and Cura, I have now encountered the printer completely stopping mid-print, and staying frozen. The heaters were of as well as the cooling fan. The extruder was still in its last position from while it was still printing. When opening DWC, no error was displayed. I noticed the XYZ positions were all at 0, indicating a reset must have happened. I ran dianostics using M122 before resetting the printer again.

Does anyone have an idea what might be going on?

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC3 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6J1FJ-3SN6P-KVTR9
Used output buffers: 1 of 24 (6 max)
=== RTOS ===
Static ram: 27916
Dynamic ram: 92244 of which 44 recycled
Exception stack ram used: 208
Never used ram: 10660
Tasks: NETWORK(ready,732) HEAT(blocked,1240) MAIN(running,1860) IDLE(ready,76)
Owned mutexes:
=== Platform ===
Last reset 08:05:04 ago, cause: power up
Last software reset at 2020-03-06 07:47, reason: User, spinning module GCodes, available RAM 10412 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 20.4, current 20.9, max 23.9
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-03-09 19:10:21
Cache data hit count 4294967295
Slowest loop: 7.38ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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 ready with "M122 " in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial 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
daemon is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 7.45ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex

dc42

The data you posted indicates that the Duet didn't reset itself:

Last reset 08:05:04 ago, cause: power up

Does 8 hours ago corresponds to when the print stopped? If so then it indicates a power problem. and you should check that the VIN terminal block screws are still tight.

EDG5000

@dc42 It is quite feasible that the print did indeed stop 8 hours ago, considering the print progress. However, my VIN wires are soldered directly onto the board.
Also, the minimum voltage reported by the diagnostics is 23.9v, so I assumed the power situation was OK.

dc42

@HC3D said in Duet stops permanently and freezes mid-print:

@dc42 It is quite feasible that the print did indeed stop 8 hours ago, considering the print progress. However, my VIN wires are soldered directly onto the board.
Also, the minimum voltage reported by the diagnostics is 23.9v, so I assumed the power situation was OK.

The M122 report only gives the minimum recorded since the last power up. If the print did stop 8 hours ago, then my guess is that you had a power brownout. The other main possibility is a problem with your PSU.

EDG5000

@dc42 Are you talking about a mains brownout or a DC brownout? In both cases, I could connect a scope/data recorder and just record during long prints.

PS I am printing the same model now, which is still not finished, and it has already had more progress than the last print, so it does not fail at a fixed point.

dc42

@HC3D said in Duet stops permanently and freezes mid-print:

@dc42 Are you talking about a mains brownout or a DC brownout? In both cases, I could connect a scope/data recorder and just record during long prints.

There's no reason for you to get a DC brownout unless you are overloading the PSU or it is overheating, or something is occasionally shorting VIN or +3.3V or +5V to ground. I meant a mains brownout.

Phaedrux

Do you happen to be using x256 microstepping on all axis?

EDG5000

@Phaedrux No, using 1/16 on all axis.