Resetting the 3d printer while printing

Kevvv

Hi, When I printing a model, the printer resets at roughly the 4th or 5th layer. I made 15 tries with the same effect. My aim is that the code contained in the line "software reset code" is the same as in the case of my colleague. Could you please help me, I am trying to find out what is causing the whole week but to no avail.
The same software reset code:
https://forum.duet3d.com/topic/22656/error-short-to-ground-reported-by-driver-s-3

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1rc2 (2022-05-25 11:49:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6JKDG-3SJ6R-KB0QG
Used output buffers: 9 of 40 (20 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96988 of which 0 recycled
Never used RAM 102420, free system stack 138 words
Tasks: NETWORK(ready,9.7%,251) ETHERNET(notifyWait,0.0%,168) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,267) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,333) TMC(notifyWait,8.5%,58) MAIN(running,81.7%,1101) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:35 ago, cause: software
Last software reset at 2021-03-10 12:23, reason: User, GCodes spinning, available RAM 115216, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 150
MCU temperature: min 31.9, current 34.0, max 34.0
Supply voltage: min 28.1, current 28.5, max 29.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 984, reads 7919, writes 21 timeouts 0
Driver 1: standstill, SG min 0, mspos 744, reads 7919, writes 21 timeouts 0
Driver 2: standstill, SG min 0, mspos 680, reads 7919, writes 21 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 7925, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 440, reads 7920, writes 21 timeouts 0
Driver 5: standstill, SG min 0, mspos 760, reads 7920, writes 21 timeouts 0
Date/time: 2021-03-10 12:25:47
Slowest loop: 3.80ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 11, maxWait 16327ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 25, completed 25, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
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
Code queue is empty
=== CAN ===
Messages queued 1401, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 779/0/0
Tx timeouts 0,0,778,0,0,621 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 7.10ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 5 2 2 2 0 0 0

and next code after half hour

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1rc2 (2022-05-25 11:49:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6JKDG-3SJ6R-KB0QG
Used output buffers: 1 of 40 (20 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96988 of which 0 recycled
Never used RAM 102420, free system stack 142 words
Tasks: NETWORK(ready,11.4%,231) ETHERNET(notifyWait,0.0%,168) HEAT(notifyWait,0.0%,325) Move(notifyWait,0.0%,267) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,333) TMC(notifyWait,8.4%,58) MAIN(running,80.1%,1101) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:54 ago, cause: software
Last software reset at 2021-03-10 12:42, reason: User, GCodes spinning, available RAM 102348, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 130
MCU temperature: min 33.3, current 34.0, max 34.2
Supply voltage: min 28.0, current 28.5, max 29.5, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 40, reads 46209, writes 21 timeouts 0
Driver 1: standstill, SG min 0, mspos 760, reads 46209, writes 21 timeouts 0
Driver 2: standstill, SG min 0, mspos 104, reads 46209, writes 21 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 46215, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 408, reads 46210, writes 21 timeouts 0
Driver 5: standstill, SG min 0, mspos 104, reads 46210, writes 21 timeouts 0
Date/time: 2021-03-10 12:26:06
Slowest loop: 3.80ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 11, maxWait 16459ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 26, completed 26, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
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
Code queue is empty
=== CAN ===
Messages queued 1568, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 872/0/0
Tx timeouts 0,0,871,0,0,695 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 7.31ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

Kevvv

config.g

I would like add that today I update a firmware but this problem is still (in old firmware and new)

Phaedrux

So you're getting short to ground on driver 3 errors? Or am I not understanding?

Kevvv

@phaedrux no no,
my printer own reset after view layers, and when I analize M122 my and akayoshi I found that

Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a

is the same.

Phaedrux

Is it always the same gcode file that it fails on, or is it any gcode file?

Did this start only after updating the firmware to 3.4.1 rc2?

Kevvv

@phaedrux on one g.code it was f.e. 5th layer but in the second g.code reset is on a first layer.

Kevvv

no, it was also on an older firmware version

dc42

@kevvv software reset code 3 means that the software reset was deliberate, caused by upgrading the firmware, by using the M999 command, or by using the Emergency Stop button on DWC or on PanelDue.

If you are certain that none of the above was done deliberately, then I guess that the command must have been executed unintentionally, perhaps because of interference. If you have an attached PanelDue display then I suggest you run PanelDueFirmware 3.4.1-pre2 on it and RRF 3.4.1 on the main board, so that the commands are protected by a CRC check instead of a checksum.

Kevvv

@dc42 Thank you for help. Tommorow I check it.
I have other question, I know that this topic does not apply to this, but my table heater is constantly warming, regardless of the temperature set, and it exceeds it significantly. Do you know what could be the reason for this?

Phaedrux

@kevvv said in Resetting the 3d printer while printing:

my table heater is constantly warming, regardless of the temperature set, and it exceeds it significantly. Do you know what could be the reason for this?

Either the configuration is wrong and it's turning on the heater instead on by default, or the mosfet/ssr you are using has failed in the on state, or the wiring is incorrect.

Share your config.g and more details about your heater wiring and setup.

Kevvv

@phaedrux

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Thu Feb 11 2021 20:03:31 GMT+0100 (czas środkowoeuropejski standardowy)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Innko"                                     ; set printer name

; Network
M551 P"Innko1994"                              ; set password
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S0                                     ; disable FTP
M586 P2 S0                                     ; disable Telnet

; Drives
M569 P0.0 S1 D3 V100                                     ; physical drive 0.0 goes forwards (X)
M569 P0.1 S0 D3 V100                                     ; physical drive 0.1 goes forwards (Y)
M569 P0.2 S0 D3 V100                                     ; physical drive 0.2 goes forwards (Z)
M569 P0.3 S1 D3 V100                                     ; physical drive 0.3 goes forwards (E0)
M569 P0.4 S0 D3 V100                                     ; physical drive 0.4 goes forwards (X)
M569 P0.5 S0 D3 V100                                     ; physical drive 0.5 goes forwards (Z)
M584 X0.0:0.4 Y0.1 Z0.2:0.5 E0.3                  		 ; set drive mapping
M593 F30												 ; anulowanie dzwonienia przy 40,5 Hz
M667 S0												     ; Cartesian mode
M671 X467:467 Y1150:-200 S5			 				     ; leadscrews at left and right, max. korekcja 5 mm
M92 X91.43 Y91.43 Z91.43 E268.05          		         ; set steps per mm
M350 X16 Y16 Z16 E16 I1                           		 ; configure microstepping with interpolation
M566 X1200.00 Y1200.00 Z600.00 E20.00                 	 ; set maximum instantaneous speed changes (mm/min)
M201 X200.00 Y200.00 Z200.00 E50.00                		 ; set accelerations (mm/s^2)
M203 X15000.00 Y15000.00 Z4000.00 E2500.00           	 ; set maximum speeds (mm/min)
M906 X2400 Y3000 Z4500 E5500 I30                   		 ; set motor currents (mA) and motor idle factor in per cent 6200 (change to lower currents if loud motor yet!!!!!!)
;M915 P0.0:0.1:0.2:0.3:0.4:0.5 S3 H1000		   			 ; motor stall detection
M84 S30                                           		 ; Set idle timeout
;M564 H0						  						 ; limit axis off

; Axis Limits
M208 X-10 Y-10 Z0 S1                               	     ; set axis minima
M208 X935 Y950 Z1010 S0                         		 ; set axis maxima

; Endstops
M574 X2 S1 P"io1.in+io4.in"                   		     ; configure active-high endstop for high end on X via pin !io1.in+!io4.in
M574 Y2 S1 P"io2.in"                         		     ; configure active-high endstop for high end on Y via pin !io2.in
;M574 Z1 S1 P"io3.in+io5.in"			  				 ; configure active-high endstop for high end on Z via pin !io3.in+!io5.in
M574 Z1 S2                                		         ; configure Z-probe endstop for high end on Z

; Z-Probe
M558 P8 C"^io7.in" H2 F450 T6000        			     ; set Z probe type to modulated and the dive height + speeds
;M558 H20                                      		     ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P50 X10.8 Y-1.5 Z3.5                                 		; set Z probe trigger value, offset and trigger height


; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950  			; configure sensor 0 as thermistor on pin temp0 
M950 H0 C"out0" T0                           			; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 S1.00                             			; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                     			; map heated bed to heater 0
M143 H1 S120                                 			; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"pt1000" 		       			; configure sensor 0 as thermocouple via CS pin spi.cs0
M950 H1 C"out1" T1                           	         	; create nozzle heater output on out0 and map it to sensor 0
M307 H1 R0.274 C1443.9 D89.85 S1.00 B0            	     	; disable bang-bang mode for heater  and set PWM limit (AUTO TUNING) V25.7
M143 H1 S350                                      		; set temperature limit for heater 1 to 350C
;M570 H0 P15 T20						; heater fault detection
M308 S2 P"temp2" Y"pt1000"			      		; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H2 C"out2" T2                             		     	; create nozzle heater output on out2 and map it to sensor 1
M307 H2 R0.274 C1443.9 D89.85 S1.00 B0            	     	; disable bang-bang mode for heater  and set PWM limit (AUTO TUNING)
M143 H2 S350                                      		; set temperature limit for heater 2 to 350C
;M570 H0 P15 T20						; heater fault detection


; Fans
M950 F0 C"out7" Q500                               ; create fan 0 on pin out7 and set its frequency
M106 P0 S1 H-1 C"Duet_processor_1"                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500                               ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H-1 C"Duet_processor_1"                 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"out9" Q500                               ; create fan 1 on pin out9 and set its frequency
M106 P2 S1 H-1 C"Nozzle_1"                         ; set fan 2 value. Thermostatic control is turned off


; Tools
M563 P0 S"Nozzle" D0 H1:2 F-1                      ; 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
M302 P1						  				   ; cold extrusion


; Miscellaneous
M575 P1 S1 B57600                                  ; enable support for PanelDue
T1                                                 ; select first tool
M20						  						   ; initialize SD card
M905 P2021-03-10 S12: 23: 12 T „Europa / Berlin”   ; Set local date and time
G32						 						   ; bed leveling
; M374											   ; save height map
; M375											   ; load height map

power cables are approx. 1.5 meters long due to the size of the printer (working space almost 1 cubic meter),
silicone heater 300x300mm 24v 350W

power connected in accordance with the documentation

Do you need any more information?

Phaedrux

Can you post a photo of the Duet board where you have the bed wired?

It's only a 24v heater?

Kevvv

@phaedrux

![alt text]( image url)

Phaedrux

Can you remove the SD card from the Duet and power it on? Does the heated bed still heat up immediately?

Kevvv

@phaedrux
![alt text]( image url)

Led is always on.

Phaedrux

I think the mosfet has failed in the on position. If this is the case a warranty replacement would be required. When and where did you purchase the Duet3?

Kevvv

@phaedrux
I bought it on August 4, 2020, in the Hobbystore store in Poland (he is your distributor).

Phaedrux

When did the bed heating issue begin? Did it ever work correctly?

Kevvv

@phaedrux
I connected the bed heater a few days ago but this is my first attempt with this heater and I noticed that the diode is on all the time.

Phaedrux

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.