• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Printers reset upon finishing prints in 3.5.1 and 3.5.2

Scheduled Pinned Locked Moved Solved
Firmware installation
3
6
190
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Andrew2087
    last edited by 14 Aug 2024, 14:59

    I could not find any reference to this issue so I figured I would post something (sorry if this is already a known issue). So this didn't happen in 3.4.5 or before, but when a print finishes, rather than going to idle status the printer(s) reset. This is at the end of every print. It also does not occur on machines running just a MB6HC. Including M122 responses for the machines that have the issue. So across three machines:
    Printer 1: 3.5.2 - CoreXY - Standalone Mode - No Issue
    9e6e9f56-fe44-421f-bb6f-39e6b4d35987-image.png
    Printer 2: 3.5.2 - Cartesian - Standalone25aa847f-1342-4096-a146-15bb93297cc8-image.png
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.5.2 (2024-06-11 17:13:58) running on Duet 3 MB6HC v1.01 (standalone mode)
    Board ID: 08DJM-9P63L-DJMSS-6JTD8-3S46M-9VFV8
    Used output buffers: 1 of 40 (40 max)
    === RTOS ===
    Static ram: 155360
    Dynamic ram: 122324 of which 0 recycled
    Never used RAM 68308, free system stack 192 words
    Tasks: NETWORK(1,ready,37.2%,153) ETHERNET(5,nWait 7,0.0%,400) HEAT(3,nWait 6,0.0%,321) Move(4,nWait 6,0.0%,323) CanReceiv(6,nWait 1,0.0%,771) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,9.5%,53) MAIN(1,running,53.1%,444) IDLE(0,ready,0.0%,29), total 100.0%
    Owned mutexes:
    === Platform ===
    Last reset 13:59:38 ago, cause: software
    Last software reset at 2024-08-13 20:19, reason: User, Gcodes spinning, available RAM 63316, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    MCU temperature: min 38.1, current 39.8, max 42.2
    Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
    Events: 0 queued, 0 completed
    Driver 0: standstill, SG min n/a, mspos 296, reads 10356, writes 14 timeouts 0
    Driver 1: standstill, SG min n/a, mspos 296, reads 10357, writes 14 timeouts 0
    Driver 2: standstill, SG min n/a, mspos 8, reads 10357, writes 14 timeouts 0
    Driver 3: standstill, SG min n/a, mspos 8, reads 10357, writes 14 timeouts 0
    Driver 4: standstill, SG min n/a, mspos 8, reads 10360, writes 11 timeouts 0
    Driver 5: standstill, SG min n/a, mspos 8, reads 10360, writes 11 timeouts 0
    Date/time: 2024-08-14 10:18:51
    Slowest loop: 16.08ms; fastest: 0.08ms
    === Storage ===
    Free file entries: 19
    SD card 0 detected, interface speed: 25.0MBytes/sec
    SD card longest read time 4.2ms, write time 30.8ms, max retries 0
    === Move ===
    DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
    no step interrupt scheduled
    Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
    === DDARing 0 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === DDARing 1 ===
    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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Movement locks held by null, 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
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    File2 is idle in state(s) 0
    Queue2 is idle in state(s) 0
    Q0 segments left 0, axes/extruders owned 0xc0000003
    Code queue 0 is empty
    Q1 segments left 0, axes/extruders owned 0x0000000
    Code queue 1 is empty
    === Filament sensors ===
    check 0 clear 276563284
    Extruder 0 sensor: ok
    === CAN ===
    Messages queued 453434, received 2015164, lost 0, errs 1, boc 0
    Longest wait 1ms for reply type 6041, peak Tx sync delay 386, free buffers 50 (min 49), ts 251892/251891/0
    Tx timeouts 0,0,0,0,0,0
    === Network ===
    Slowest loop: 34.03ms; fastest: 0.03ms
    Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 2 of 8
    = Ethernet =
    Interface state: active
    Error counts: 0 0 2 1 1783 0
    Socket states: 5 2 2 2 2 0 0 0
    === Multicast handler ===
    Responder is inactive, messages received 0, responses 0

    Printer 3: Cartesian - Standalone
    b4cfd6a6-4727-4a39-a034-dff6804d2bfb-image.png
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.5.1 (2024-04-19 14:30:55) running on Duet 3 MB6HC v1.01 (standalone mode)
    Board ID: 08DJM-9P63L-DJ3T0-6JTDJ-3SJ6P-T83MA
    Used output buffers: 3 of 40 (31 max)
    === RTOS ===
    Static ram: 155208
    Dynamic ram: 123244 of which 0 recycled
    Never used RAM 67540, free system stack 202 words
    Tasks: NETWORK(1,ready,25.7%,176) ETHERNET(5,nWait 7,0.2%,392) HEAT(3,nWait 6,0.3%,321) Move(4,nWait 6,0.0%,324) CanReceiv(6,nWait 1,0.9%,772) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,346) TMC(4,nWait 6,79.0%,54) MAIN(1,running,142.8%,444) IDLE(0,ready,0.0%,30), total 249.0%
    Owned mutexes:
    === Platform ===
    Last reset 09:01:17 ago, cause: software
    Last software reset at 2024-08-14 01:17, reason: User, Gcodes spinning, available RAM 64052, slot 2
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    MCU temperature: min 49.3, current 50.8, max 52.3
    Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.2, current 12.3, max 12.3, under voltage events: 0
    Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
    Events: 0 queued, 0 completed
    Driver 0: standstill, SG min n/a, mspos 8, reads 30627, writes 11 timeouts 0
    Driver 1: standstill, SG min n/a, mspos 880, reads 30619, writes 19 timeouts 0
    Driver 2: standstill, SG min n/a, mspos 16, reads 30620, writes 19 timeouts 0
    Driver 3: standstill, SG min n/a, mspos 784, reads 30620, writes 19 timeouts 0
    Driver 4: standstill, SG min n/a, mspos 176, reads 30620, writes 19 timeouts 0
    Driver 5: standstill, SG min n/a, mspos 8, reads 30628, writes 11 timeouts 0
    Date/time: 2024-08-14 10:18:34
    Slowest loop: 8.74ms; fastest: 0.08ms
    === Storage ===
    Free file entries: 19
    SD card 0 detected, interface speed: 25.0MBytes/sec
    SD card longest read time 3.2ms, write time 3.8ms, max retries 0
    === Move ===
    DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
    no step interrupt scheduled
    Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
    === DDARing 0 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === DDARing 1 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters -1 1 2 3 4 5 6 7 8 9 -1 -1, chamber heaters -1 10 11 -1, ordering errs 0
    Heater 12 is on, I-accum = 0.0
    === GCodes ===
    Movement locks held by null, 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
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    File2 is idle in state(s) 0
    Queue2 is idle in state(s) 0
    Q0 segments left 0, axes/extruders owned 0x80000003
    Code queue 0 is empty
    Q1 segments left 0, axes/extruders owned 0x0000000
    Code queue 1 is empty
    === CAN ===
    Messages queued 292381, received 2468336, lost 0, errs 1, boc 0
    Longest wait 2ms for reply type 6053, peak Tx sync delay 388, free buffers 50 (min 49), ts 162389/162388/0
    Tx timeouts 0,0,0,0,0,0
    === Network ===
    Slowest loop: 13.09ms; fastest: 0.03ms
    Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    = Ethernet =
    Interface state: active
    Error counts: 0 0 0 1 0 0
    Socket states: 5 2 2 2 2 0 0 0
    === Multicast handler ===
    Responder is inactive, messages received 0, responses 0

    undefined 1 Reply Last reply 14 Aug 2024, 15:02 Reply Quote 0
    • undefined
      jay_s_uk @Andrew2087
      last edited by 14 Aug 2024, 15:02

      @Andrew2087 how do you know they reset? neither of the M122 show a reset

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      undefined 1 Reply Last reply 14 Aug 2024, 16:26 Reply Quote 1
      • undefined
        Andrew2087 @jay_s_uk
        last edited by 14 Aug 2024, 16:26

        @jay_s_uk Print again does not appear, all motors are no longer homed, and babystepping is cleared

        This would be the time at which the print finished on Printer 2:
        Last software reset at 2024-08-13 20:19, reason: User, Gcodes spinning, available RAM 63316, slot 0
        This was not from user interaction with the printer

        undefined 1 Reply Last reply 14 Aug 2024, 19:51 Reply Quote 0
        • undefined
          Andrew2087 @Andrew2087
          last edited by 14 Aug 2024, 19:51

          I'm also including the printers' ending gcode for reference (I can also share configs if that might be helpful):
          Printer 1: CoreXY, single tool, running MB6HC, DOES NOT RESET Upon print completion
          ; layer end
          M106 S0 ; turn off cooling fan
          M104 S0 ; turn off extruder
          M140 S0 ; turn off bed
          G1 X0 Y270; part removal
          ; Build Summary

          Printer 2: Cartesian, IDEX, P3 and P4 are for Mimic/Mirroring and are only created on the printer if using Mimic/Mirror Mode. P1 and P2 are the left and right head respectively
          ; layer end
          T0
          G28 XUY
          M568 P1 R0 S0
          M568 P2 R0 S0
          M568 P3 R0:0 S0:0
          M568 P4 R0:0 S0:0
          M104 S0 ; turn off extruder
          M190 S0; Turn off bed
          M141 S0 ; turn off chamber
          G0 Z785;

          Printer 3: This printer is made up of 9 small bed heaters + a pellet extruder (hence the Nozzle heater, Middle, and Upper heaters), (the middle and upper heaters are configured as chamber heaters) - I am aware that this printer does disable the X and Y motors during the ending gcode, as stated above, Z is also disabled and babystepping is cleared.

          ; layer end
          T0
          G28 XY
          M106 P0 S0 ; shut off part cooling vent
          G10 P0 S0 R0; Set Active and standby temps for Nozzle heater
          M141 P1 S0 R0; Set Active and standby temps for Upper Heater
          M141 P2 S0 R0; Set Active and standby temps for Middle heater
          M104 S0 ; turn off extruder
          M141 S0 ; turn off chamber
          M84XY ; disable motors
          M144 P1
          M144 P2
          M144 P3
          M144 P4
          M144 P5
          M144 P6
          M144 P7
          M144 P8
          M144 P9

          undefined 1 Reply Last reply 14 Aug 2024, 20:06 Reply Quote 0
          • undefined
            gloomyandy @Andrew2087
            last edited by 14 Aug 2024, 20:06

            @Andrew2087 Do you have a stop.g file? If so what is in it?

            undefined 1 Reply Last reply 15 Aug 2024, 18:47 Reply Quote 1
            • undefined
              Andrew2087 @gloomyandy
              last edited by 15 Aug 2024, 18:47

              @gloomyandy That was it. Didn't see that stop.g now runs at the end of all prints since 3.5b1 regardless of M0 being present and stop.g was set with an M999 (I assume when it was set up on printers 2 and 3 it was thought that it was for an emergency stop situation not the end of a print). Thank you for your help!

              1 Reply Last reply Reply Quote 1
              • undefined dc42 marked this topic as a question 15 Aug 2024, 19:16
              • undefined dc42 has marked this topic as solved 15 Aug 2024, 19:16
              2 out of 6
              • First post
                2/6
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA