Duet 2 wifi - software reset 0x4083
-
Hello everyone!
Can somebody point me to the right direction what is happening?6/11/2022, 11:07:41 AM: M122: === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 78016 of which 12 recycled Never used RAM 7264, free system stack 150 words Tasks: NETWORK(ready,13.5%,217) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,304) DUEX(notifyWait,0.0%,24) MAIN(running,86.5%,466) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:24:38 ago, cause: software Last software reset at 2022-06-11 10:42, reason: StuckInSpinLoop, GCodes spinning, available RAM 5992, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200016bc Task IDLE Freestk 44 ok Stack: 0045cd7d 0045d722 61000000 a5a5a5a5 0045cd7d a5a5a5a5 20002334 0294282d 20002c00 20005c40 200016d4 20005c38 00000004 20001428 20001428 200016d4 00000000 00000001 20001730 4e49414d 00000000 00000000 00000001 00000001 12422a05 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 29.2, current 29.4, max 29.8 Supply voltage: min 1.2, current 1.2, max 1.3, under voltage events: 1, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/494/38, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-06-11 11:07:40 Cache data hit count 4294967295 Slowest loop: 4.20ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.6ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 4, completed 4, 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, 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 Daemon is doing "G4 S4" in state(s) 0 0, running macro Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 202.97ms; fastest: 0.07ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Power up WiFi flash size 4194304, free heap 25040 WiFi IP address 10.57.183.107 WiFi signal strength -41dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0The restart occured after ~16h of printing during a G1 H4 command form a macro.
I've searched the stack trace in Duet2CombinedFirmware.map and the result points me in two directions:.bss._ZL11networkTask 0x20002c00 0x9bc ./src/Networking/Network.o .bss._ZL8mainTask 0x200016d4 0x11b4 ./src/Platform/Tasks.oIs the wifi module failing? It is not getting hot, just warm in operation
-
Can you share your config.g and the gcode file you were printing?
Has this ever happened before? Did you attempt the file again? -
Hello @Phaedrux and thank you for your replay
@phaedrux said in Duet 2 wifi - software reset 0x4083:
Can you share your config.g
Here is my config:
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.0 on Tue Dec 29 2020 16:23:44 GMT+0200 (Eastern European Standard Time) global useMMU = true ; enable or disable Multi Material Unit if global.useMMU = true global useCutter = true ; enable or disable the CUT fnction of the Multi Material Unit global mmuErr = 0 global statusBondtech = 0 global statusFinda = 0 ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves if global.useMMU = true M550 P"Creality CR-10L MMU2S" ; set printer name else M550 P"Creality CR-10L" ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; enable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S0 ; physical drive 2 goes backwards M569 P3 S0 ; physical drive 3 goes forwards if global.useMMU = true M569 P5 S1 M569 P6 S0 M569 P7 S0 M584 X0 Y1 Z2 E3:3:3:3:3 ; set drive mapping M584 X0 Y1 Z2 E3 if global.useMMU = true M584 U5 V6 W7 M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation if global.useMMU = true M350 U16 V16 W16 I1 M92 X80.00 Y80.00 Z400.00 E415.00 ; set steps per mm if global.useMMU = true M92 U400 V145 W26 M566 X600.00 Y600.00 Z24.00 E3000.00 ; set maximum instantaneous speed changes (mm/min) if global.useMMU = true M566 U24 V600 W600 M203 X18000.00 Y18000.00 Z1200.00 E6000.00 ; set maximum speeds (mm/min) if global.useMMU = true M203 U2400 V5400 W3000 M201 X3000.00 Y3000.00 Z100.00 E5000.00 ; set accelerations (mm/s^2) if global.useMMU = true M201 U500 V1500 W1500 M201.1 X500 Y500 Z50 E1000 ;Set reduced acceleration for special move types (mm/s^2) if global.useMMU = true M201.1 U250 V500 W500 M906 X800 Y800 Z800 E600 I40 ; set motor currents (mA) and motor idle factor in per cent I30 if global.useMMU = true M906 U700 V700 W700 ; M906 U800 V800 W800 M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima if global.useMMU = true M208 U0 V-1000 W0 S1 M208 X315 Y311 Z400 S0 ; set axis maxima if global.useMMU = true M208 U75 V1000 W78 S0 ; Endstops M574 X1 S1 P"^xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"^ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S1 P"^zstop" ; configure active-high endstop for low end on Z via pin zstop if global.useMMU = true M574 U2 S3 M574 V0 M574 W1 S3 ; Z-Probe M950 S0 C"!exp.heater7" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 A20 S0.005 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-27.4 Y-28.6 Z2.00 ; set Z probe trigger value, offset and trigger height M557 X8.0:287.6 Y21.6:271.6 P5 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S110 ; set temperature limit for heater 0 to 110C M308 S1 P"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs1 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S400 ; set temperature limit for heater 1 to 400C ; Fans M950 F0 C"fan0" Q10000 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 L0.3 C"Tool" ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1+^exp.pb6" Q25000 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 C"Heatsink" ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets M568 P0 R0 S0 A0 ; set initial tool 0 active and standby temperatures to 0C if global.useMMU = true M563 P1 D1 H1 F0 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets M568 P1 R0 S0 A0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 D2 H1 F0 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets M568 P2 R0 S0 A0 ; set initial tool 2 active and standby temperatures to 0C M563 P3 D3 H1 F0 ; define tool 3 G10 P3 X0 4Y0 Z0 ; set tool 3 axis offsets M568 P3 R0 S0 A0 ; set initial tool 3 active and standby temperatures to 0C M563 P4 D4 H1 F0 ; define tool 4 G10 P4 X0 Y0 Z0 ; set tool 4 axis offsets M568 P4 R0 S0 A0 ; set initial tool 4 active and standby temperatures to 0C ; Custom settings M81 C"pson" ; ATX in stadby mode at boot M308 S2 Y"mcu-temp" A"MCU" ; MCU temperature sensor (sensor 2) M308 S3 Y"drivers" A"TMC Drivers" ; drivers temperature sensors (sensor 3) M912 P0 S-7.2 ; set temperature monitor adjustment (MCU) M307 H0 R0.135 C783.5 D0.39 S1.00 V12.2 ; set the process parameters (bed 60degC) M307 H1 R1.757 K0.275:0.139 D6.31 E1.35 S1.00 B0 V12.2 ; set the process parameters (hotend 210degC) M207 S0.8 F1800 ; set retract length (PLA) M404 N1.75 ; set filament width if global.useMMU = false M591 D0 P1 C"^e0stop" S0 ; filament monitor connected to E0 endstop (Drive 0) M950 J1 C"^e1stop" ; Input 1 uses e2stop pin, pullup enabled (EmergencyStop button) M581 P1 T0 S1 R0 ; external trigger 1, trigger occurs on the active-to-inactive edge, trigger at any time M950 J2 C"^duex.e3stop" ; Input 1 uses e2stop pin, pullup enabled (power feedback for UPS) M581 P2 T2 S1 R1 ; external trigger 1, trigger occurs on the inactive-to-active edge, trigger at any time (UPS Backup power) M581 P2 T3 S0 R2 ; external trigger 1, trigger occurs on the active-to-inactive edge, trigger only when not printing from SD card (AC back, resume prompt) M593 P"ZVD" F30.2 ; use ZVD input shaping to cancel ringing at 30.0Hz M204 P600 T800 ; set printing and travel accelerations (mm/s^2) ;M204 P1500 T2000 M671 X30:30:275:275 Y30:275:275:30 P0.7 F5.0 ; adjusting screws at front left (30,30), back left (30,275), back right (275,275) and front right (275,30). Thread pitch M4 corse: 0.7mm if global.useMMU = true M98 P"0:/sys/MMU Control/settingsPrinter.g" M98 P"0:/sys/MMU Control/settingsDefaultFilament.g" ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memoryI think that my config will not make too much sense without the context so i'll leave you a backup of my SD card, just because my issues occurs during tool changes:
https://drive.google.com/drive/folders/1OcTPiUw0RlYuLT-Skopb6It37nG4u9Io?usp=sharing@phaedrux said in Duet 2 wifi - software reset 0x4083:
the gcode file you were printing?
Unfortunately the gcode that failes is too big to upload it here, but you can find it in the google drive, gcodes folder.
@phaedrux said in Duet 2 wifi - software reset 0x4083:
Has this ever happened before?
Actually yes, many times, different gcodes, never twice at the same point but some worked flawlessly and many more failed (M122 report).
@phaedrux said in Duet 2 wifi - software reset 0x4083:
Did you attempt the file again?
Let's say I got 5 prints done ok and >20 prints failed.
PS, with the network adapter disabled, works better..I'm sure that last time then RRF crashed it was here:
\sys\MMU Control\loadToFinda.gbut I can't say for sure which line was executing
Thank you again
-
Well.. I have an update:
Just finished a print. 16h and 38min.. and work flawlessly, not a single DWC drop during this time, but the diagnostics changed a little bit:m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 78984 of which 256 recycled Never used RAM 5260, free system stack 96 words Tasks: NETWORK(ready,3.6%,143) HEAT(notifyWait,0.4%,308) Move(notifyWait,6.5%,284) DUEX(notifyWait,0.0%,24) MAIN(running,89.3%,421) IDLE(ready,0.2%,30), total 100.0% Owned mutexes: === Platform === Last reset 23:19:41 ago, cause: software Last software reset at 2022-06-14 12:11, reason: User, GCodes spinning, available RAM 7432, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x0c Aux0 errors 0,2,0 Step timer max interval 0 MCU temperature: min 26.8, current 28.6, max 30.1 Supply voltage: min 1.2, current 1.3, max 12.4, under voltage events: 1, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/514/58, gc cycles 25 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: standstill, SG min 0 Driver 6: standstill, SG min 0 Driver 7: standstill, SG min 0 Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-06-15 11:31:17 Cache data hit count 4294967295 Slowest loop: 137.69ms; fastest: 0.10ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 44.6ms, write time 0.6ms, max retries 0 === Move === DMs created 83, segments created 36, maxWait 7041682ms, bed compensation in use: mesh, comp offset -0.005 === MainDDARing === Scheduled moves 475212, completed 475212, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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, 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 Daemon is doing "G4 S4" in state(s) 0 0, running macro Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1489, 2.45 reads/min === Network === Slowest loop: 199.87ms; fastest: 0.07ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 24 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Power up WiFi flash size 4194304, free heap 25040 WiFi IP address 10.57.183.107 WiFi signal strength -35dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0And during the print PanelDue catched this:
A single note: Before starting this print, a reflashed the WiFi module (M997 S1) and that was it.
Now, this rised two questions in my head:
-
Can the WiFi module firmware get corrupted during normal operation?
-
If so.. there will be any early symptoms in this regard?
-
-
@leonard03 the error code along with the fact that the IDLE task was running (which is very usual) indicates that neither the main task nor the network task could run. This is very unusual and should only happen for very brief periods, nowhere near long enough to get the "Stuck in spin loop" reset. It could possibly be caused by a firmware bug (i.e. deadlock), but as nobody else has reported this type of reset, I suspect it was caused by memory corruption, possibly caused by ESD. Please ground the hot end metalwork and the extruder body (if separate) or extruder motor body if you have not already done so. We know that extruding filament causes static charge to build up in some circumstances and this charge flashes over to the thermistor connections.
The "slowing down poll rate" message from PanelDue means that PanelDue was seeing too many missed replies from the Duet, so it reduced the poll rate to lessen the load on the Duet.
It's not impossible that the WiFi module firmware could get corrupted, for example by ESD or by a transient on the +3.3V supply. We don't yet do a CRC check on the WiFi firmware as we do on the main board firmware.
-
Wow thank you very much @dc42, is an honor to receive an answer from you
Up to this point, all problems was is this order:
-
First print, DWC reconnected every couple of seconds. I solved this by increasing the the number of AJAX retries from 1 (I don't know if this was the default) to 20 (why not).
-
After this, 3.4.1-rc2 was released, and the increased number of output buffers for the Duet 2 WiFi made a big difference, but still had issues.
-
Reviewing my config (based from 2.05?) I activated the pullup resistors on all endstops (all being endstops with only two wires). Again, another step in the right direction.
From there on, everything seems to be good so far, at least until I started this topic.
I will try your suggestion about grounding the steppers (at this moment all 8 steppers are isolated - because they are mounted by plastic mounts) and I will post an update
Thank you again for your time analyzing my problem
-
-
undefined Leonard03 marked this topic as a regular topic
-
Hello @dc42 !
Unfortunately grounding the steppers didn't have any effect to this issue
Print stopped last night after around 9h with the same error code and the same reason "stuckinspinloop"...
-
That's too bad. Did you also have the hot end metal grounded? Is the frame itself grounded?
-
Good morning
@Phaedrux do you belive in ghosts? Because this thing is hunted by something
Leaving all jokes aside:
I completed a 12:30 hours print last night without touching any wire of the printer. What changed are two things:
Yesterday PrusaSlicer 2.5.0-alpha2 was released on github and I give it a try.
Second, my WiFi Router has received a firmware upgrade (also yesterday) but the change log says only this:Modifications and Bug Fixes: 1. Updating cloud Services. 2. Enhance device security.And my test looks like this
Any Ideas? It started to become very annoying
-
Well, failed again after 7 hours
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 77920 of which 12 recycled Never used RAM 7360, free system stack 144 words Tasks: NETWORK(ready,12.4%,257) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,306) DUEX(notifyWait,0.0%,24) MAIN(running,87.5%,466) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:36:27 ago, cause: software Last software reset at 2022-07-01 20:34, reason: StuckInSpinLoop, GCodes spinning, available RAM 6064, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041a80f BFAR 0xe000ed38 SP 0x200016bc Task IDLE Freestk 44 ok Stack: 0045cd7d 0045d728 61000000 a5a5a5a5 0045cd7d a5a5a5a5 2000232c 01ba8527 20002c00 20005c40 200016d4 20005c38 00000004 20001428 20001428 200016d4 00000000 00000001 20001730 4e49414d 00000000 00000000 00000001 00000001 cdd7a346 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 31.7, current 33.7, max 35.8 Supply voltage: min 0.4, current 1.2, max 12.9, under voltage events: 1, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/456/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-07-01 21:11:00 Cache data hit count 4294967295 Slowest loop: 10.99ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 4.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 306097ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 7, 0.19 reads/min === Network === Slowest loop: 15.51ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Power up WiFi flash size 4194304, free heap 24640 WiFi IP address 10.57.183.107 WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 4 0 0 0 0 0 0 0But the diagnostics report during printing is pretty interesting:
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5v0.11 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 6 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 78568 of which 12 recycled Never used RAM 6064, free system stack 106 words Tasks: NETWORK(ready,218.0%,215) HEAT(notifyWait,0.9%,324) Move(notifyWait,9.9%,282) DUEX(notifyWait,0.0%,24) MAIN(running,288.6%,421) IDLE(ready,0.4%,30), total 517.8% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 05:23:41 ago, cause: power up Last software reset at 2022-06-23 21:17, reason: StuckInSpinLoop, GCodes spinning, available RAM 6040, slot 2 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200016bc Task IDLE Freestk 44 ok Stack: 0045cd7d 0045d72c 61000000 a5a5a5a5 0045cd7d a5a5a5a5 20002334 020046da 20002c00 20005c40 200016d4 20005c38 00000004 20001428 20001428 200016d4 00000000 00000001 20001730 4e49414d 00000000 00000000 00000001 00000001 4984a1d4 00000000 00000000 Error status: 0x0c Aux0 errors 0,1,0 Step timer max interval 0 MCU temperature: min 21.0, current 34.0, max 34.3 Supply voltage: min 0.0, current 12.2, max 12.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/23, heap memory allocated/used/recyclable 2048/1670/1188, gc cycles 7 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: ok, SG min 0 Driver 4: standstill, SG min n/a Driver 5: standstill, SG min 0 Driver 6: standstill, SG min 0 Driver 7: standstill, SG min 0 Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-07-01 17:54:52 Cache data hit count 4294967295 Slowest loop: 131.43ms; fastest: 0.11ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 6.5ms, write time 11.9ms, max retries 0 === Move === DMs created 83, segments created 30, maxWait 2411303ms, bed compensation in use: mesh, comp offset -0.010 === MainDDARing === Scheduled moves 26975, completed 26974, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state 3 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 0 Movement lock held by File HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 19 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: ok === DueX === Read count 1094, 3.38 reads/min === Network === Slowest loop: 31.81ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Turned on by main processor WiFi flash size 4194304, free heap 26240 WiFi IP address 10.57.183.107 WiFi signal strength -37dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 2 0 0 0 0 0 0Please have a look at tasks percentages
-
I've tried something today. I've left the printer on all day without turning on the main PSU and issued two M122 commands:
7/5/2022, 7:04:56 PM: Connected to 10.57.183.107 7/5/2022, 7:05:11 PM: m122: === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 77920 of which 12 recycled Never used RAM 7432, free system stack 190 words Tasks: NETWORK(ready,149.2%,217) HEAT(notifyWait,0.4%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,329.6%,462) IDLE(ready,0.1%,30), total 479.2% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 04:09:43 ago, cause: software Last software reset at 2022-07-04 23:32, reason: User, GCodes spinning, available RAM 7412, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 31.9, current 33.5, max 33.9 Supply voltage: min 1.2, current 1.3, max 1.4, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/456/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min n/a Driver 1: ok, SG min n/a Driver 2: ok, SG min n/a Driver 3: ok, SG min n/a Driver 4: ok, SG min n/a Driver 5: ok, SG min n/a Driver 6: ok, SG min n/a Driver 7: ok, SG min n/a Driver 8: ok, SG min n/a Driver 9: ok, SG min n/a Driver 10: Driver 11: Date/time: 2022-07-05 19:05:20 Cache data hit count 4294967295 Slowest loop: 16.61ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 4.9ms, write time 1.2ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, 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, 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 200.76ms; fastest: 0.07ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Power up WiFi flash size 4194304, free heap 24952 WiFi IP address 10.57.183.107 WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 07/5/2022, 8:24:36 PM: M122: === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 77920 of which 12 recycled Never used RAM 7432, free system stack 190 words Tasks: NETWORK(ready,337.3%,217) HEAT(notifyWait,0.9%,333) Move(notifyWait,0.1%,363) DUEX(notifyWait,0.0%,24) MAIN(running,2417.5%,462) IDLE(ready,0.1%,30), total 2755.8% Owned mutexes: === Platform === Last reset 05:28:57 ago, cause: software Last software reset at 2022-07-04 23:32, reason: User, GCodes spinning, available RAM 7412, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 33.0, current 33.6, max 34.2 Supply voltage: min 1.2, current 1.3, max 1.4, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/456/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min n/a Driver 1: ok, SG min n/a Driver 2: ok, SG min n/a Driver 3: ok, SG min n/a Driver 4: ok, SG min n/a Driver 5: ok, SG min n/a Driver 6: ok, SG min n/a Driver 7: ok, SG min n/a Driver 8: ok, SG min n/a Driver 9: ok, SG min n/a Driver 10: Driver 11: Date/time: 2022-07-05 20:24:34 Cache data hit count 4294967295 Slowest loop: 7.37ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, 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, 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 201.77ms; fastest: 0.07ms Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFSocket states: 4 2 0 0 0 0 0 0@dc42 do these percentages look ok?
Tasks: NETWORK(ready,149.2%,217) HEAT(notifyWait,0.4%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,329.6%,462) IDLE(ready,0.1%,30), total 479.2%Tasks: NETWORK(ready,337.3%,217) HEAT(notifyWait,0.9%,333) Move(notifyWait,0.1%,363) DUEX(notifyWait,0.0%,24) MAIN(running,2417.5%,462) IDLE(ready,0.1%,30), total 2755.8%Looks like those report matches the issues seen in the stacktrace
-
So I tried grounding my hotend as @dc42 suggested.
It is an E3D V6 Gold edition with a titanium heatbreak and the nozzleX.
Last night I've seen this https://forum.duet3d.com/topic/28399/1lc-board-stopped-working-but-still-responsive-to-m122/12 and now I give it a try but turns out that the heatsink is electrically isolated. Only the heatblock is conductive. Now what ?!
And as a thought - how this board was very stable before RRF3, with a configuration with two extruders and two bowden tubes about 700mm long and can print that took days to complete without any problems ? -
Sorry for leaving you hanging. I'll mention it to DC42 again.
Just to confirm, you're still getting software reset 0x4083?
-
Hello @Phaedrux and welcome back
Please hold on until tomorrow..
I'll start another test with the new released 3.4.2rc1 and I'll post an updateThankyou very much for your time and patience
-
Correction - worked only for 3 hours and failed with the same reason.. 4083
RRF crashed 2 minutes ago with this report=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2rc1 (2022-07-06 16:21:02) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917NK-F2MS4-7JKDG-3S06M-9ZSWD Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 77968 of which 0 recycled Never used RAM 7324, free system stack 148 words Tasks: NETWORK(ready,12.4%,254) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,304) DUEX(notifyWait,0.0%,24) MAIN(running,86.7%,456) IDLE(ready,0.8%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:33 ago, cause: software Last software reset at 2022-07-08 00:43, reason: StuckInSpinLoop, GCodes spinning, available RAM 5820, slot 2 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200016bc Task IDLE Freestk 44 ok Stack: 0045cdcd 0045d77a 61000000 a5a5a5a5 0045cdcd a5a5a5a5 2000232c 00c47889 20002c00 20005c40 200016d4 20005c38 00000004 20001428 20001428 200016d4 00000000 00000001 20001730 4e49414d 00000000 00000000 00000001 00000001 809f72da 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 28.5, current 29.7, max 30.1 Supply voltage: min 0.6, current 12.3, max 13.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/22, heap memory allocated/used/recyclable 2048/456/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-07-08 00:45:05 Cache data hit count 3472812724 Slowest loop: 10.69ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.8ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 53873ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 4, 2.56 reads/min === Network === Slowest loop: 15.52ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address b4:e6:2d:52:f5:47 WiFi Vcc 3.40, reset reason Power up WiFi flash size 4194304, free heap 26928 WiFi IP address 10.57.183.107 WiFi signal strength -37dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0And by the way, my only chance to ground the nozzle (for the E3D V6 Gold at least) is to ground the heaterblock directly..
-
Can you ground the stepper at least? If the source of the ESD is from the filament then the contact with the drive gear and motor shaft may mean grounding the stepper is enough.
-
Actually the extruder motor is already grounded
But the funny thing is that the filament don't even touch the extruder when the board restarts
Last 4 or 5 attempts to print the same model the crash happening always before the tip of the filament reaching the extruder so the second endstop. Never happend during printing, seems to be always during execution of "loadToBondtech.g" right above the extruder gears...
-
Ah, and as a side note:
As I seen this idea also somewhere here on the forum, I tried to simulate that gcode and the simulation completed without warnings or errors
