Just had a mid-print reset on 2.01b2

  • I was standing there watching the printer. None of the axes were even close to their endstops and I wasn't touching the printer.

    Last reset 00:08:56 ago, cause: reset button or watchdog

    doesn't say which it was though so it's not all that helpful. Can we get that message enhanced to say which button or which watchdog it was?

    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta2(RTOS) running on Duet Ethernet 1.02 or later + DueX5
    Board ID: 08DGM-95BNL-MGPSJ-6JTD8-3SS6K-11XHZ
    Used output buffers: 3 of 20 (7 max)
    === RTOS ===
    Static ram: 28484
    Dynamic ram: 95724 of which 0 recycled
    Exception stack ram used: 308
    Never used ram: 6556
    Tasks: NETWORK(ready,400) HEAT(blocked,1248) MAIN(running,3648)
    Owned mutexes:
    === Platform ===
    Last reset 00:08:56 ago, cause: reset button or watchdog
    Last software reset at 2018-07-20 19:27, reason: User, spinning module GCodes, available RAM 6408 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: 10

    I also had an issue earlier today where the thermostatically controlled heatsink fan just stopped but the print continued. A few minutes later the filament jammed in the hotend and I had to take everything apart to clear it.

  • administrators

    Thanks for your report. On the Duet rev 1.04 we should be able to tell the difference between a watchdog reset and the reset button, but on the older Duets we can't. Unless something is fouling the reset button on your Duet, it's probably a watchdog reset. What's odd is that there is a second watchdog that normally goes off before that one, and it hasn't in this case.

Log in to reply