Duet wifi print stalls



  • Hi Folks,
    It's been some time since I first equipped my detla printer with duet 3d WiFi board.
    I have run a number of successful prints however now I'm facing issues that I cannot resolve.

    Problem:
    With longer or prints my printer suddenly stalls.
    Previously I run prints overnight fine but now after 1h or 2h it stalls.
    By stall I mean printhead stops moving (randomly) but heaters keep heating (OMG!). Web GUI shows printer state as "paused" but nobody paused the print...
    When I hit Resume button only one axis moves. Sending G28 also fails as only one motor moves.

    Restarting via "emergency stop" or power cycle fix the problem.

    Today I run 3 times into this issue and couldn't finish prints.

    I have a M122 output from two last attempts:

    5:48:31M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3S8-6J9DG-3S46S-TVJ3F
    Used output buffers: 1 of 20 (14 max)
    === RTOS ===
    Static ram: 28476
    Dynamic ram: 96392 of which 16 recycled
    Exception stack ram used: 428
    Never used ram: 5760
    Tasks: NETWORK(ready,272) HEAT(blocked,1248) MAIN(running,3548)
    Owned mutexes:
    === Platform ===
    Last reset 03:00:42 ago, cause: power up
    Last software reset at 2019-10-22 10:50, reason: User, spinning module GCodes, available RAM 5840 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 2.7ms, max retries 0
    MCU temperature: min 35.1, current 45.0, max 45.4
    Supply voltage: min 11.4, current 12.6, max 12.7, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max 0/474
    Driver 1: standstill, SG min/max 0/467
    Driver 2: standstill, SG min/max 0/468
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2019-10-26 15:48:27
    Slowest loop: 251.58ms; fastest: 0.07ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 120, MaxWait: 3653980ms, Underruns: 18, 0
    Scheduled moves: 138950, completed moves: 138949
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    Heater 0 is on, I-accum = 0.2
    Heater 1 is on, I-accum = 0.3
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 doing "G1 X-53.272 Y19.900 E7.6444" 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: 182.45ms; 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 0
    WiFi firmware version 1.21
    WiFi MAC address 80:7d:3a:15:1e:1c
    WiFi Vcc 3.40, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 15880
    WiFi IP address 192.168.5.110
    WiFi signal strength -46dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Expansion ===
    

    And second

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-9T6BU-FG3S8-6J9DG-3S46S-TVJ3F
    Used output buffers: 3 of 20 (14 max)
    === RTOS ===
    Static ram: 28476
    Dynamic ram: 96392 of which 16 recycled
    Exception stack ram used: 436
    Never used ram: 5752
    Tasks: NETWORK(ready,328) HEAT(blocked,1248) MAIN(running,3540)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 02:07:55 ago, cause: power up
    Last software reset at 2019-10-26 15:49, reason: User, spinning module GCodes, available RAM 5760 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 9
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 50.4ms, max retries 0
    MCU temperature: min 26.4, current 43.4, max 45.7
    Supply voltage: min 11.4, current 12.6, max 12.7, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max 0/468
    Driver 1: standstill, SG min/max 0/459
    Driver 2: standstill, SG min/max 0/458
    Driver 3: standstill, SG min/max 0/1023
    Driver 4: standstill, SG min/max not available
    Date/time: 2019-10-26 19:05:23
    Slowest loop: 104.33ms; fastest: 0.07ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 120, MaxWait: 215158ms, Underruns: 20, 0
    Scheduled moves: 145400, completed moves: 145399
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 2 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 doing "G1 X47.940 Y-70.150 E3.9089" 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: 52.86ms; fastest: 0.01ms
    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.21
    WiFi MAC address 80:7d:3a:15:1e:1c
    WiFi Vcc 3.40, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 15960
    WiFi IP address 192.168.5.110
    WiFi signal strength -55dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0
    === Expansion ===
    
    

    My system

    Firmware Name:   RepRapFirmware for Duet 2 WiFi/Ethernet
    Firmware Electronics:   Duet WiFi 1.02 or later
    Firmware Version:   2.01(RTOS) (2018-07-26b2)
    WiFi Server Version:   1.21
    Web Interface Version:   1.22.3
    

    I thought it's an SD card issue and replaced it but again print failed.

    I don't know how to find the root cause as currently I'm really nervous of leaving printer alone as when stall occurs heaters keep heating and print could burn after a while...

    No additional errors occured.

    Thank you for help



  • please update to the latest duet firmware and try again (2.04RC version as 2.03 has a bug with deltas)



  • also. did you follow dc42 suggestion to decrease your microstepping to the recommended x16 with interpolation?



  • @Veti yes

    Ok I'll update to recommended firmware version and let You know.

    The only thing that bothers me is that printer generally was working fine until yesterday so I wouldn't blame firmware in the first place as it looks very similar to SD card issues (but I replaced it and then same problem was encountered).

    How about power supply? Undervoltage event should be visible in m122 command shouldn't it?

    Shall I enable some additional debug verbosity level? (And how?)



  • @morf said in Duet wifi print stalls:

    Shall I enable some additional debug verbosity level? (And how?)

    https://duet3d.dozuki.com/Wiki/Logging



  • Ok i upgraded firmware to 2.04RC4 but it didn't solve my problems directly 🙂 however with new firmware onboard when the "stall" occured in the Console window I got message saying that print was paused due to low voltage.
    I replaced my power supply and restart the print.
    So far it seems that this problem is gone and it was connected to faulty PS.


Log in to reply