UNSOLVED Duet 2 Wifi rebooting/crashing during print



  • @Phaedrux was out of town for the holidays, just started a 4 hour print and the printer rebooted ~40mins in

    m122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta4 running on Duet WiFi 1.02 or later
    Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
    Used output buffers: 3 of 24 (12 max)
    === RTOS ===
    Static ram: 24108
    Dynamic ram: 99836 of which 60 recycled
    Never used RAM 6044, free system stack 106 words
    Tasks: NETWORK(ready,183) HEAT(blocked,308) MAIN(running,451) IDLE(ready,20)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:49 ago, cause: software
    Last software reset at 2021-01-07 01:30, reason: AssertionFailed, GCodes spinning, available RAM 5836, slot 1
    Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x200044ac Task MAIN
    Stack: 00000c55 00472af0 00452a9d 2000ae20 00000000 200094c8 00000000 00000000 00451edb 00000000 ffffffff 2000ae20 200034cc 200094c8 ffffffff 00000000 20004524 a5a5a5a5 00451f1b 20004514 200094b8 20008380 0044f543 20008380 0042ee47 2001e448 200094bc
    Error status: 0x00
    MCU temperature: min 25.0, current 25.2, max 26.1
    Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: position 63150, standstill, SG min/max 0/138
    Driver 1: position 63150, standstill, SG min/max 0/133
    Driver 2: position 63150, standstill, SG min/max 0/156
    Driver 3: position 0, standstill, SG min/max not available
    Driver 4: position 0, standstill, SG min/max not available
    Driver 5: position 0
    Driver 6: position 0
    Driver 7: position 0
    Driver 8: position 0
    Driver 9: position 0
    Driver 10: position 0
    Driver 11: position 0
    Date/time: 2021-01-07 01:32:29
    Cache data hit count 170332161
    Slowest loop: 3.51ms; fastest: 0.17ms
    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.1ms, write time 0.0ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 163, MaxWait: 22002ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 5, completed moves 5, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is 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.
    === Network ===
    Slowest loop: 15.70ms; 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.25beta0
    WiFi MAC address dc:4f:22:6e:6c:ca
    WiFi Vcc 3.43, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 19552
    WiFi IP address 192.168.86.34
    WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00002002
    Socket states: 0 0 0 0 0 0 0 0
    

    I see that 4.2 was just released so i'll update to that and try again.



  • @Phaedrux no dice, another crash. @dc42 any ideas?

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
    Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
    Used output buffers: 3 of 24 (12 max)
    === RTOS ===
    Static ram: 23460
    Dynamic ram: 72744 of which 60 recycled
    Never used RAM 15816, free system stack 99 words
    Tasks: NETWORK(ready,157) HEAT(blocked,307) MAIN(running,450) IDLE(ready,19)
    Owned mutexes:
    === Platform ===
    Last reset 00:01:12 ago, cause: software
    Last software reset at 2021-01-07 19:24, reason: HardFault invState, GCodes spinning, available RAM 15608, slot 1
    Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f003 BFAR 0xe000ed38 SP 0x2001fe90 Task MAIN Freestk 29308 ok
    Stack: 00000000 00000001 400e1400 00001000 3ed0bedf 0044adf3 2001ff28 400f0227 00000160 00000100 2001db10 fffffff1 000001ab 00000000 00a69e38 0000012b 2001c8b8 38000000 005a0073 00000001 28bb5437 fffffffb 29767437 2000770e 2001ff28 01000001 2001ff28
    Error status: 0x00
    Aux0 errors 0,0,0
    MCU temperature: min 24.9, current 25.4, max 26.0
    Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: position 63150, standstill, SG min/max 0/147
    Driver 1: position 63150, standstill, SG min/max 0/131
    Driver 2: position 63150, standstill, SG min/max 0/157
    Driver 3: position 0, standstill, SG min/max not available
    Driver 4: position 0, standstill, SG min/max not available
    Driver 5: position 0
    Driver 6: position 0
    Driver 7: position 0
    Driver 8: position 0
    Driver 9: position 0
    Driver 10: position 0
    Driver 11: position 0
    Date/time: 2021-01-07 19:25:21
    Cache data hit count 87576278
    Slowest loop: 4.81ms; fastest: 0.20ms
    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.9ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 83, maxWait 11729ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 5, completed moves 5, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is 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.
    === Network ===
    Slowest loop: 15.95ms; 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.25
    WiFi MAC address dc:4f:22:6e:6c:ca
    WiFi Vcc 3.43, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 19568
    WiFi IP address 192.168.86.34
    WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00002002
    Socket states: 0 0 0 0 0 0 0 0
    


  • can you post a picture of your wiring on the duet?


  • administrators

    @bwnance, your M122 software reset data doesn't make any sense, so I think it must have been caused by a transient or possible power brownout. Can you run a few more prints to see if any future crashes are similar? You can do air prints to avoid wasting filament.

    The assertion failure you had with 3.2beta4 is different, that's a known bug that was fixed in 3.2beta4.1.



  • @dc42 Will do dry-runs throughout today. It's weird, sometimes it completes a print just fine, sometimes it fails -- but all with the same file.

    @Veti
    szoter_annotated_image.jpeg



  • motors very close to the board .
    maybe try to add some shielding , or relocate the board just for a test .



  • @dc42 crash on a no-filament run:

    m122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
    Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
    Used output buffers: 3 of 24 (11 max)
    === RTOS ===
    Static ram: 23460
    Dynamic ram: 72744 of which 24 recycled
    Never used RAM 15852, free system stack 191 words
    Tasks: NETWORK(ready,182) HEAT(blocked,309) MAIN(running,452) IDLE(ready,19)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:26 ago, cause: software
    Last software reset at 2021-01-08 15:42, reason: HardFault imprec, GCodes spinning, available RAM 15608, slot 0
    Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00400003 BFAR 0xe000ed38 SP 0x2001ffa8 Task MAIN Freestk 29378 ok
    Stack: 20008e54 20008e50 1cc5b538 00000004 0000000a ffffffed 0040f1f8 010f001f 20008e54 20003440 20008110 20004494 a5a5a5a5 ffffffed 00000000 00f00000 e000ef34 c0000000 20004690 004548f5 0045465c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff
    Error status: 0x00
    Aux0 errors 0,0,0
    MCU temperature: min 24.0, current 24.4, max 25.2
    Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: position 62528, standstill, SG min/max not available
    Driver 1: position 62528, standstill, SG min/max not available
    Driver 2: position 62528, standstill, SG min/max not available
    Driver 3: position 0, standstill, SG min/max not available
    Driver 4: position 0, standstill, SG min/max not available
    Driver 5: position 0
    Driver 6: position 0
    Driver 7: position 0
    Driver 8: position 0
    Driver 9: position 0
    Driver 10: position 0
    Driver 11: position 0
    Date/time: 2021-01-08 15:43:37
    Cache data hit count 105466486
    Slowest loop: 4.99ms; fastest: 0.20ms
    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.1ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is 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.
    === Network ===
    Slowest loop: 16.01ms; 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.25
    WiFi MAC address dc:4f:22:6e:6c:ca
    WiFi Vcc 3.43, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 22320
    WiFi IP address 192.168.86.34
    WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00002002
    Socket states: 0 0 0 0 0 0 0 0
    


  • Anotha one.

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
    Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
    Used output buffers: 3 of 24 (11 max)
    === RTOS ===
    Static ram: 23460
    Dynamic ram: 72744 of which 24 recycled
    Never used RAM 15852, free system stack 193 words
    Tasks: NETWORK(ready,194) HEAT(blocked,307) MAIN(running,456) IDLE(ready,19)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:21 ago, cause: software
    Last software reset at 2021-01-08 16:41, reason: HardFault invState, GCodes spinning, available RAM 15608, slot 1
    Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f803 BFAR 0xe000ed38 SP 0x200043e0 Task MAIN Freestk 976 ok
    Stack: 00000002 200099c0 00000100 00000000 200178b8 0042d68f 00000000 600f0000 0042d75a 610f0000 ffffffff 0000000a 010095c8 20008e54 00000000 00000000 00000000 00454a15 20008e54 00000000 20008e54 00454daf 200099c4 00454f3b 00000000 ffffffff 200099c0
    Error status: 0x00
    Aux0 errors 0,0,0
    MCU temperature: min 24.0, current 24.6, max 25.0
    Supply voltage: min 24.0, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: position 62528, standstill, SG min/max not available
    Driver 1: position 62528, standstill, SG min/max not available
    Driver 2: position 62528, standstill, SG min/max not available
    Driver 3: position 0, standstill, SG min/max not available
    Driver 4: position 0, standstill, SG min/max not available
    Driver 5: position 0
    Driver 6: position 0
    Driver 7: position 0
    Driver 8: position 0
    Driver 9: position 0
    Driver 10: position 0
    Driver 11: position 0
    Date/time: 2021-01-08 16:42:20
    Cache data hit count 25138224
    Slowest loop: 4.94ms; fastest: 0.20ms
    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.1ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === AuxDDARing ===
    Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is 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.
    === Network ===
    Slowest loop: 15.68ms; 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.25
    WiFi MAC address dc:4f:22:6e:6c:ca
    WiFi Vcc 3.43, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 22400
    WiFi IP address 192.168.86.34
    WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00002002
    Socket states: 0 0 0 0 0 0 0 0
    


  • @hackinistrator Moved the board over and repositioned the berdair to be nowhere near the board... we shall see.



  • @bwnance
    so?



  • @hackinistrator haven't had a bunch of time, but i've run 3 dry runs so far with no issue - a pretty good sign.


  • administrators

    Is the Berdair driven directly from a Duet heater output? If so then I suggest twisted pair wires between the two. Hand twisted will do.

    Have you connected a fast recovery flyback diode in parallel with the Berdair? The best place for it is on the motor terminals. Make sure you connect it the right way round!



  • @dc42 the Berdair is connected directly to FAN0 -- i was under the impression that a flyback diode had been included on all the fan headers in recent board revisions - i might have misunderstood?