Duet freezing



  • Sometimes my delta with a build size of 1m x 1,5m freeze without any logical reason, at least for me 🙂

    Maybe this is the reason, but what does this mean ??

    Last software reset at 2020-06-04 16:50, reason: User, spinning
    module GCodes, available RAM 11400 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR
    0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    

    Below the full diagnostic after reboot:

    24/9/2020, 14:14:23: Connected to 192.168.1.206
    24/9/2020, 14:15:38: M122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet
    WiFi 1.02 or later
    Board ID: 08DDM-9FAM2-LW4S4-6J9DG-3SD6N-13SRX
    Used output buffers: 3 of 24 (6 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 92700 of which 300 recycled
    Exception stack ram used: 440
    Never used ram: 11920
    Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3640)
    IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:05:22 ago, cause: power up
    Last software reset at 2020-06-04 16:50, reason: User, spinning
    module GCodes, available RAM 11400 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR
    0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 30.9, current 33.9, max 35.5
    Supply voltage: min 24.0, current 24.2, max 24.5, under voltage
    events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 359/699
    Driver 1: standstill, SG min/max 408/712
    Driver 2: standstill, SG min/max 41/179
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-09-24 14:15:37
    Cache data hit count 902642629
    Slowest loop: 26.07ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0,
    finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 154, MaxWait: 14074ms
    Bed compensation in use: mesh, comp offset 0.000
    === DDARing ===
    Scheduled moves: 5, completed moves: 5, StepErrors: 0, LaErrors: 0,
    Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 15.47ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    Telnet(0)
    HTTP sessions: 1 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.23
    WiFi MAC address 60:01:94:73:5b:3c
    WiFi Vcc 3.39, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 24952
    WiFi IP address 192.168.1.206
    WiFi signal strength -65dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: no data received
    24/9/2020, 14:15:58: M122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet
    WiFi 1.02 or later
    Board ID: 08DDM-9FAM2-LW4S4-6J9DG-3SD6N-13SRX
    Used output buffers: 3 of 24 (12 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 92744 of which 256 recycled
    Exception stack ram used: 440
    Never used ram: 11920
    Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3640)
    IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:05:41 ago, cause: power up
    Last software reset at 2020-06-04 16:50, reason: User, spinning
    module GCodes, available RAM 11400 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR
    0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 146.5ms, max retries 0
    MCU temperature: min 33.8, current 34.1, max 34.4
    Supply voltage: min 24.2, current 24.4, max 24.4, under voltage
    events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-09-24 14:15:57Cache data hit count 960253407
    Slowest loop: 80.23ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0,
    finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
    Bed compensation in use: mesh, comp offset 0.000
    === DDARing ===
    Scheduled moves: 5, completed moves: 5, StepErrors: 0, LaErrors: 0,
    Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 364.48ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    Telnet(0)
    HTTP sessions: 1 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 1
    WiFi firmware version 1.23
    WiFi MAC address 60:01:94:73:5b:3c
    WiFi Vcc 3.39, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 25064
    WiFi IP address 192.168.1.206
    WiFi signal strength -65dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: no data received
    24/9/2020, 14:17:51: M122: === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet
    WiFi 1.02 or later
    Board ID: 08DDM-9FAM2-LW4S4-6J9DG-3SD6N-13SRX
    Used output buffers: 1 of 24 (15 max)
    === RTOS ===
    Static ram: 25712
    Dynamic ram: 92744 of which 256 recycled
    Exception stack ram used: 440
    Never used ram: 11920
    Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3640)IDLE(ready,160)
    Owned mutexes:
    === Platform ===
    Last reset 00:07:35 ago, cause: power up
    Last software reset at 2020-06-04 16:50, reason: User, spinning
    module GCodes, available RAM 11400 bytes (slot 2)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR
    0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 33.7, current 33.9, max 34.2
    Supply voltage: min 24.1, current 24.2, max 24.5, under voltage
    events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-09-24 14:17:50
    Cache data hit count 1294237665
    Slowest loop: 4.94ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0,
    finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
    Bed compensation in use: mesh, comp offset 0.000
    === DDARing ===
    Scheduled moves: 5, completed moves: 5, StepErrors: 0, LaErrors: 0,
    Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 203.13ms; fastest: 0.08ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    Telnet(0)
    HTTP sessions: 1 of 8
    - WiFi -
    Network state is running
    WiFi module is connected to access pointFailed messages: pending 0, notready 0, noresp 3
    WiFi firmware version 1.23
    WiFi MAC address 60:01:94:73:5b:3c
    WiFi Vcc 3.39, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 25064
    WiFi IP address 192.168.1.206
    WiFi signal strength -64dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Filament sensors ===
    Extruder 0 sensor: no data received
    

    thank you



  • please can you provide your config 😁


  • Moderator

    @paboman I can't see anything obvious in your M122 report. It says that the board was reset, that's about it.

    Try updating your firmware to 2.05.1. This fixed a problem in 2.05:

    Fixed a 1-character buffer overflow in class OutputBuffer. The effects of this overflow were unknown but potentially severe.

    From https://github.com/Duet3D/RepRapFirmware/blob/dev/WHATS_NEW.md

    Ian



  • @droftarts
    I run M122 after reboot because the duet was not responding at all

    Thanks I will try to update the firmware


Log in to reply