Duet 2 wifi - software reset 0x4083

dc42

@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.

Leonard03

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

Leonard03

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"...

Phaedrux

That's too bad. Did you also have the hot end metal grounded? Is the frame itself grounded?

Leonard03

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

Leonard03

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 0

But 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 0

Please have a look at tasks percentages

Leonard03

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 0

7/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

Leonard03

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 ?

Phaedrux

Sorry for leaving you hanging. I'll mention it to DC42 again.

Just to confirm, you're still getting software reset 0x4083?

Leonard03

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 update

Thankyou very much for your time and patience

Leonard03

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 0

And by the way, my only chance to ground the nozzle (for the E3D V6 Gold at least) is to ground the heaterblock directly..

Phaedrux

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.

Leonard03

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...

Leonard03

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