Reboots/resets randomly - RRF 3.5.0-b4

dc42

@RogerPodacter thanks. Can you confirm that you have no daemon.g file in /sys on the SD card?

Exerqtor

@dc42 said in Reboots/resets randomly - RRF 3.5.0-beta4:

@Exerqtor in reply to your question in the firmware announcement thread, you are already running wifi firmware 2.1beta4 according to your M122 reports - but please check that you haven't inadvertently downgraded to 2.1beta3.

Yup, no problem I know intermittent issues can suck to track down

RogerPodacter

@dc42 ah yes, here is my daemon.g.

daemon.g

while global.daemonLoop

;-----------------------------------------------------------------------------
;Heater Checks and Safety
;-----------------------------------------------------------------------------
	;check if Chamber heater fans are running
;	if fans[3].rpm < 100
;		M141 H2 S-273.1 ; disable chamber heater

;-----------------------------------------------------------------------------
;Keeps a lifetime running print time variable for the printer
;-----------------------------------------------------------------------------
	;if global.warmUp = true
	;	echo "setLEDbyTemp = true"
	;	M98 P"0:/macros/set_LED_while_heating.gcode"
	if state.status == "processing"
		if exists(global.runtime)
			set global.runtime = {global.runtime + 10}
			echo >"runtime.g" "global runtime = " ^ {global.runtime} ^ " ; seconds AUTO GENERATED by daemon.g"
			;echo >"runtime.g" "minutes = "^{global.runtime}/60
			;echo >"runtime.g" "hours = "^{global.runtime}/60/60
			;echo >"runtime.g" "days = "^{global.runtime}/60/60/24

;-----------------------------------------------------------------------------
;LED Controls
;-----------------------------------------------------------------------------
	if {state.status} == "paused"
		M150 R255 B255 P255 S2  ; purple
		M300 S4000 P50 G4 P300 M300 S4000 P50 ; double beep
	elif {state.status} == "processing" || {state.status} == "busy"
		M150 R255 U255 B255 W255 P255 S2  ; white
	elif {heat.heaters[0].current} > 50 || {heat.heaters[1].current} > 70
		M150 R255 U0 B0 W0 P255 S2  ; red
	elif {state.status} == "idle"
		M150 R0 U255 B0 W0 P255 S2  ; green
	else
		M150 R150 U0 B150 W0 P255 S2 ; purple

	G4 S10 ;there is a delay of 10 seconds between consecutive executions of daemon.g. This is to avoid SD 
	; card access contention between daemon.g and a file being printed. If you need a smaller delay, put 
	; all that code inside a while-loop, and include a shorter delay (e.g. G4 S1) at the end of the loop.


	;ADD SOMETHING LIKE THIS FOR HEATER SAFETY.  USE REALLY USEFUL EXAMPLE GCODE DAEMON.G FILES.
	;if fans[1].rpm < 100 && heat[1].heaters > 50
	;	abort "No fan motion detected, stopping all macros,  jobs, and  disabling heaters"
	;	M140 P-273.1 ; disable bed heater
	;	M568 P0 A0; set tool 0 to off




;############ from dc42

;while true
;while iterations<10
;
;  while iterations < #sensors.analog
;    var red = sensors.analog[iterations].lastReading
;    var green = 255 - var.red
;    var blue = var.green
;    M150 R{var.red} U{var.green} B{var.blue} S2 F{min(#sensors.analog-iterations-1,1)}
;
;  G4 S3
;  
;#############  
;  
  ; daemeon.g
;
; Adafruit #1426 8 led neopixel
;
; M150 X1
;
; if heat.heaters[1].current > 50 ; temp
;  M150 R0 U255 B0 P255 S2 F1 ;M150 R{var.redValue} U{var.greenValue} B{var.blueValue} P{var.setBrightness} S{var.pixelsPerTool} F{var.F}
;  
; elif heat.heaters[1].current <= 50
;  M150 R0 U0 B255 P255 S2 F1

dc42

@RogerPodacter thanks.

Please also provide your homing files, since you said the machine resets during homing.
Although this doesn't explain the reset, I can see a problem in your config.g file. Your M669 command to set the kinematics at line 7 refers to the U axis, however the U axis doesn't exist until it is created in the M584 command at line 35. You should move the M669 command to be after the M584 command.

Arminas

This post is deleted!

Exerqtor

@dc42
Just as a little update, i have as of today not had any more resets. I'm trying to turn out some small parts, just to see if anything can trigger a reset, but so far no luck =/

dc42

@Exerqtor thanks for the update. I have not yet had a reset either using your files or the file from @RogerPodacter (although I am still waiting for his homing files, and he reported that the reset occurred when homing).

RogerPodacter

@dc42 apologies for the delay. here are my homing files. my printer kinematics didnt work correctly, so i dont know if that was related while i was attempting the homings...

homeall.g

if (move.axes[0].homed && move.axes[1].homed && move.axes[2].homed && move.axes[3].homed)
	echo "already homed, skipping"
else
	;T0
	G91																	; Relative positioning
	G1 Z15 F6000 H2														; Lift Z relative to current position
	
	G1 Y999 F3000 H1												; Move X and Y-axes to the endstops and stop (first pass)
	G1 Y-4 F600														; Move Y-axis to the endstop and stop (first pass)
	G1 Y15 F600 H1														; Move X-axis to the endstop once more (second pass)
	
	G1 X-999 F3000 H1 										; coarse home X, Y and U
	G1 X4 F600 												; move 4mm away from the homing switches
	G1 X-15 H1     												; fine home X, Y and U
	
	G1 U999 F3000 H1 										; coarse home X, Y and U
	G1 U-4 F600 												; move 4mm away from the homing switches
	G1 U15 H1     												; fine home X, Y and U
	
	G90																	; Absolute positioning
	
	M401 ; deploy Z probe (omit if using bltouch)
	
	; Home Z using the Z-Probe
	M290 R0 S0															; Reset baby-stepping to 0
	G1 X183 Y170 F6000											; Move T0 to probing point (X150, Y150), including probe offset
	G30																	; Probe the bed and set Z to the probe offset
	
	M402 ; retract probe (omit if using bltouch)

homex.g

M201 X500.00 U500.00    ; Reduce acceleration for homing moves

G91                     ; Relative positioning
G1 H2 Z5 F6000          ; Lift Z relative to current position

G1 H1 X-625 F3000       ; Move quickly to X endstop and stop there (first pass)
G1 X3 F600              ; Go back a few mm
G1 H1 X-625 F360        ; Move slowly to X endstop once more (second pass)

;G1 H1 U625 F1800
;G1 U-3 F600
;G1 H1 U625 F360

M201 X3000 U6000        ; Return to full acceleration

G1 H2 Z-5 F6000         ; Lower Z relative to current position
G90                     ; Absolute positioning

homey.g

M201 X500.00 Y500.00    ; Reduce acceleration for homing moves

G91                     ; Relative positioning
G1 H2 Z5 F6000          ; Lift Z relative to current position

G1 H1 Y605 F3000        ; Move quickly to Y endstop and stop there (first pass)
G1 Y-3 F600             ; Go back a few mm
G1 H1 Y605 F360         ; Move slowly to Y endstop once more (second pass)

M201 X3000 Y6000        ; Return to full acceleration

G1 H2 Z-5 F6000         ; Lower Z relative to current position
G90                     ; Absolute positioning

homez.g

; ***********************************************************
; Euclid Probe homez.g Example Macro
; RRF3.X Firmware Example
; saveas system/homez.g
; comments and echo statements throughout are provided for convenience
; ***********************************************************


if !move.axes[0].homed || !move.axes[1].homed     ; If the printer hasn't been homed, home it
	M98 P"0:/sys/homexy.g"  

M561                                            ; clear any bed transform
M290 S0 R0                                      ; clear baby steps 

G91                                             ; relative positioning
G1 H2 Z15 F6000                                  ; lift Z relative to current position to clear any obstructions
M400

G1 U380 F2000 ; make sure the U carriage is out of the way

G90                                             ; absolute positioning

; echo "Call deployprobe.g macro" 
M401 P0                                         ; This runs macro file deployprobe

; echo "Return"
G1 X155 Y155 F9000                            ; go to center of bed in advance of probe that point
M400

; echo "G30 Command"
G30                                             ; Probe the bed at the current XY position. When the probe is triggered, 
                                                ; adjust the Z offset of the current tool to make the current position Z=0.

;G1 Z10                                          ; raise Z=10
;M400
;G4 P500

; echo "Call bed4point.g macro"
;M98 P"0:/sys/bed.g"                       ; tram bed

; echo "Return"
;G1 X145 Y162.5 F9000                              ; go back to the first probe point and reprobe 0 in case it moved
;G30

; echo "Call retractprobe.g macro"
M402 P0                                         ; retract probe
 echo "Return"

;G1 Z10 F600                                     ; lift Z relative to current position
G90                                             ; absolute positioning
M564 S1 H0                                      ; reset the bounding limits
; G1 X150 Y0 F9000                              ; move carriage to center front

homeu.g

M201 U500.00 Y500.00    ; Reduce acceleration for homing moves

G91                     ; Relative positioning
G1 H2 Z5 F6000          ; Lift Z relative to current position

G1 H1 U625 F3000       ; Move quickly to X endstop and stop there (first pass)
G1 U-3 F600              ; Go back a few mm
G1 H1 U625 F360        ; Move slowly to X endstop once more (second pass)

M201 U3000 Y6000        ; Return to full acceleration

G1 H2 Z-5 F6000         ; Lower Z relative to current position
G90                     ; Absolute positioning

bed.g

M290 R0 S0    ;  clear baby stepping
M561          ;  reset all bed adjustments
M400          ;  flush move queue

; echo "Running bed4point.g"
;M558 F60 A6 ;A3                              ; fix probe speed to 1mm/s
;G90
;G4 P250

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
	echo "not all axes homed, homing axes first"
	G28

G1 U380 F2000 ; make sure the U carriage is out of the way

M401 ; deploy Z probe (omit if using bltouch)

G30 P0 X46 Y20 Z-99999 ; X41 X30 Y20 Z-99999 ; probe near a leadscrew
G30 P1 X155 Y276 Z-99999 ;Y282 Z-99999 ; probe near a leadscrew
G30 P2 X270 Y20 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
echo "Current rough pass deviation: " ^ move.calibration.initial.deviation


while move.calibration.initial.deviation > 0.005
		if iterations >= 5
			echo "Error: Max attemps failed. Deviation: " ^ move.calibration.initial.deviation
			break
		echo "Deviation over threshold. Executing pass" , iterations+1, "deviation", move.calibration.initial.deviation
		G30 P0 X46 Y20 Z-99999 ; probe near a leadscrew
		G30 P1 X155 Y276 Z-99999 ; probe near a leadscrew
		G30 P2 X270 Y20 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
		echo "Current deviation: " ^ move.calibration.initial.deviation
		continue
echo "Final deviation: " ^ move.calibration.initial.deviation

G0 X155 Y155 Z20 F9000

G30
;G28 Z

M402 ; retract probe (omit if using bltouch)

Exerqtor

@dc42
After a couple days without any resets, it happend again twice yesterday:

power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.4 (2023-06-08 23:40:14)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:09 [warn] HTTP client 192.168.10.100 login succeeded (session key 1366409378)
2023-06-16 01:23:20 [warn] Date and time set at power up + 00:00:09
power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.4 (2023-06-08 23:40:14)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:08 [warn] HTTP client 192.168.10.100 login succeeded (session key 125510966)
2023-06-16 10:24:14 [warn] Date and time set at power up + 00:00:08

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 1 of 40 (30 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 124208 of which 16 recycled
Never used RAM 11980, free system stack 180 words
Tasks: NETWORK(2,nWait,126.9%,219) HEAT(3,nWait,0.5%,327) Move(4,nWait,0.1%,344) CanReceiv(6,nWait,1.1%,672) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.2%,351) TMC(4,delaying,26.0%,108) MAIN(1,running,48.1%,704) IDLE(0,ready,8.9%,29) AIN(4,delaying,18.0%,266), total 229.7%
Owned mutexes:
=== Platform ===
Last reset 26:40:40 ago, cause: software
Last software reset at 2023-06-16 10:24, reason: HardFault invState, Gcodes spinning, available RAM 10580, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011fa8 Task NETW Freestk 482 ok
Stack: 000001ae 00000002 200014ec 00000000 2003335a 0009d43d 00000000 600f0000 00000000 00000000 00000000 00000000 20032174 00000800 20035e68 2002c558 20018670 2002c3f5 20018670 2001e920 0002fe6f 00000000 00000000 00000000 20012058 00000014 b5ddc1d1
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 96040137, completed 96040137, timed out 0, errs 0
MCU temperature: min 35.1, current 36.3, max 39.4
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/28, heap memory allocated/used/recyclable 2048/980/596, gc cycles 3588
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 33, reads 14596, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 14596, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 147, reads 14596, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 147, reads 14595, writes 13, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 150, reads 14595, writes 13, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6a
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 14597, writes 10, timeouts 2, DMA errors 0, CC errors 0, failedOp 0x6a
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 14599, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-06-17 13:04:45
Cache data hit count 4294967295
Slowest loop: 22.78ms; fastest: 0.14ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.5ms, write time 4.2ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, 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 doing "G4 S1                                                                        " in state(s) 0 0, running macro
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
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 864369, received 1920872, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 277, free buffers 18 (min 17), ts 480201/480200/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 22.24ms; 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, notready 0, noresp 0
Firmware version 2.1beta4
MAC address bc:ff:4d:e6:b1:62
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42972
WiFi IP address 192.168.10.50
Signal strength -50dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0

dc42

@Exerqtor that's interesting, it's not the same crash as before but it is the same task (NETW) and probably the same area of code.

If your machine is not being used, please can you do a couple of things to increase the load on it, in the hope that this will make the problem occur more frequently. In particular, try these:

In the DWC Machine Specific config, reduce the polling interval e.g. to 100ms
Reduce the lengths of G4 delay commands that you have in daemon.g.

Exerqtor

@dc42
Guess that's somewhat positive and it would help narrow down the search a little? wishfull thinking

Ok I've set the "Communication update invervals" to 100ms now (if that's the one you were refering to).
What do you suggest changing the daemon.g delay to? It's currently 1second, so reduce it to 300ms or something maybe?

dc42

@Exerqtor I suggest you try 100ms. If that makes the response to console commands such as M122 excessively slow, increase it.

Exerqtor

@dc42
Ok, then both have been set to 100ms. Now it's just to wait for a crash i guess

Exerqtor

@dc42
Don't look like the added stress we were able to muster up with those changes did much, only had one crash since they were changed:

power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.4 (2023-06-08 23:40:14)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:08 [warn] HTTP client 192.168.10.100 login succeeded (session key 775616360)
2023-06-18 04:59:53 [warn] Date and time set at power up + 00:00:08

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 1 of 40 (38 max)
=== RTOS ===
Static ram: 102996
Dynamic ram: 125612 of which 12 recycled
Never used RAM 10580, free system stack 180 words
Tasks: NETWORK(1,ready,84.6%,219) HEAT(3,nWait,0.1%,327) Move(4,nWait,0.0%,344) CanReceiv(6,nWait,0.2%,672) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,nWait,4.9%,108) MAIN(1,running,150.3%,704) IDLE(0,ready,13.1%,29) AIN(4,delaying,3.4%,266), total 256.8%
Owned mutexes:
=== Platform ===
Last reset 04:11:46 ago, cause: software
Last software reset at 2023-06-18 04:59, reason: HardFault invState, Gcodes spinning, available RAM 9444, slot 2
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011fa8 Task NETW Freestk 482 ok
Stack: 000001af 00000002 200014ec 00000000 2003335b 0009d43d 00000000 600f0000 00000000 00000000 00000000 00000000 2003217c 00000800 20035e70 2002c558 20018670 2002c3f5 20018670 2001e920 0002fe6f 00000000 00000000 00000000 20012058 00000014 ffffffff
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 15106363, completed 15106363, timed out 0, errs 0
MCU temperature: min 35.1, current 35.5, max 41.8
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/32, heap memory allocated/used/recyclable 2048/1372/948, gc cycles 4666
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 63, reads 62550, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 63, reads 62549, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 166, reads 62549, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 165, reads 62549, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 168, reads 62550, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 62553, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 62552, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-06-18 09:11:30
Cache data hit count 4294967295
Slowest loop: 37.72ms; fastest: 0.14ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 7.0ms, write time 5.6ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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, 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 doing "G4 P100                                                                       " in state(s) 0 0, running macro
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
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 135965, received 302172, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 306, free buffers 18 (min 17), ts 75532/75531/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 22.11ms; 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, notready 0, noresp 0
Firmware version 2.1beta4
MAC address bc:ff:4d:e6:b1:62
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42960
WiFi IP address 192.168.10.50
Signal strength -55dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0

Exerqtor

@dc42 Have you had any more time or luck with this David?

Mine havent had any news crashes sunday, and been sitting idle since then since it quite frankly ain't stable enough to be used for any duration of time

dc42

@Exerqtor unfortunately I haven't been able to reproduce it.

Exerqtor

@dc42
Haven't had any more crashes here either, though the printer has just been sitting idle since last time it happened.

dc42

@Exerqtor I'm wondering whether it could possibly be a hardware issue, because I haven't been able to reproduce it and nobody else has reported it. Which country are you in and which Duet3D reseller do you use?

Exerqtor

@dc42
Might be the case, this perticular board ain't a original duet3 board but a Fysetc "Big Dipper" (killed the processor on my Duet 2 so I needed a subsitute board ASAP, and couldn't justify cashing out for a original duet 3 mini & addon board to the mrs 🤦‍♂️).

It haven't had a single crash since the last one i reportet two weeks ago though. Even with the extra load we added.

Just started a 2.3hr print on it now to see if it wil act up again.

droftarts

@Exerqtor Please be up-front about using clone Duet boards. It would save a lot of time supporting, and trying to resolve issues with, boards who's quality are beyond the scope of what Duet3D can control.

Regarding the Fysetc Big Dipper board, when the TeamGloomy devs took a look at it, they weren't that impressed. When looking at the schematics, it doesn't include as much filtering, and some other corners have been cut, compared to the Duet 3D Mini 5+.

Ian