Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Printing stops

    General Discussion
    4
    18
    187
    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.
    • Weevil
      Weevil last edited by

      I ran across this issue 3 times now. I have a print job that is about 85% done and then it stops as if the job is completed It stops with the nozzle still in contact of the print. Please note, this print job has completed before. I was just printing a copy. Please advise.

      Here's my M122 report:
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.01-RC1 running on Duet 3 MB6HC
      Board ID: 08DJM-956L2-G43S4-6J9D6-3SJ6T-KA62H
      Used output buffers: 1 of 40 (6 max)
      === RTOS ===
      Static ram: 153800
      Dynamic ram: 160608 of which 32 recycled
      Exception stack ram used: 520
      Never used ram: 78256
      Tasks: NETWORK(ready,440) ETHERNET(blocked,456) HEAT(blocked,1200) CanReceiv(suspended,3820) CanSender(suspended,1436) CanClock(blocked,1436) TMC(blocked,76) MAIN(running,4376) IDLE(ready,76)
      Owned mutexes:
      === Platform ===
      Last reset 00:04:53 ago, cause: software
      Last software reset time unknown, reason: User, spinning module GCodes, available RAM 78264 bytes (slot 1)
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
      Error status: 0
      Free file entries: 10
      SD card 0 detected, interface speed: 25.0MBytes/sec
      SD card longest block write time: 0.0ms, max retries 0
      MCU temperature: min 43.2, current 43.7, max 43.8
      Supply voltage: min 23.7, current 23.7, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
      Driver 0: standstill, reads 58454, writes 19 timeouts 0, SG min/max 0/192
      Driver 1: standstill, reads 58454, writes 19 timeouts 0, SG min/max 0/373
      Driver 2: standstill, reads 58455, writes 19 timeouts 0, SG min/max 0/623
      Driver 3: standstill, reads 58456, writes 19 timeouts 0, SG min/max 0/839
      Driver 4: standstill, reads 58456, writes 19 timeouts 0, SG min/max 0/690
      Driver 5: standstill, reads 58462, writes 14 timeouts 0, SG min/max 0/0
      Date/time: 1970-01-01 00:00:00
      Slowest loop: 9.67ms; fastest: 0.07ms
      === Move ===
      Hiccups: 0(0), FreeDm: 375, MinFreeDm: 371, MaxWait: 68027ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 23, completed moves: 23, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
      === Heat ===
      Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      Heater 1 is on, I-accum = 0.8
      === 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
      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
      lcd is idle in state(s) 0
      spi is idle in state(s) 0
      autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 9.54ms; fastest: 0.03ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 1 of 8

      • Ethernet -
        State: 5
        Error counts: 0 0 0 0 0
        Socket states: 2 2 2 2 2 2 0 2
        === CAN ===
        Messages sent 1179, longest wait 0ms for type 0
        === Linux interface ===
        State: 0, failed transfers: 0
        Last transfer: 293463ms ago
        RX/TX seq numbers: 0/1
        SPI underruns 0, overruns 0
        Number of disconnects: 0
        Buffer RX/TX: 0/0-0
      dc42 1 Reply Last reply Reply Quote 0
      • Weevil
        Weevil last edited by

        The only error code I see is: "Exception stack ram used: 520" but I am not sure what it means.

        1 Reply Last reply Reply Quote 0
        • dc42
          dc42 administrators @Weevil last edited by

          @Weevil said in Printing stops:

          Last reset 00:04:53 ago, cause: software
          Last software reset time unknown, reason: User, spinning module GCodes, available RAM 78264 bytes (slot 1)
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d

          Did you run this M122 after the print stopped and without resetting the Duet ? It indicates that the printer reset less than 5 minutes ago due to a "normal" software reset, i.e. Emergency Stop or M999 command.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          Weevil 1 Reply Last reply Reply Quote 0
          • Weevil
            Weevil @dc42 last edited by

            @dc42 I just realized. When I tried to move the head it was stuck to the print. I hit emergency stop then. I will have to run the job again and see what happens.

            1 Reply Last reply Reply Quote 0
            • dc42
              dc42 administrators last edited by

              Also, I suggest you upgrade to RRF 3.01-RC4.

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              Weevil 2 Replies Last reply Reply Quote 0
              • Weevil
                Weevil @dc42 last edited by Weevil

                @dc42 The job is currently going and it has surpassed the point of the stoppage yesterday. Hopefully, it will complete. I will upgrade after this print.

                1 Reply Last reply Reply Quote 0
                • Weevil
                  Weevil @dc42 last edited by

                  @dc42 I was looking at the notes for RRF 3.01-RC4:

                  Recommended compatible firmware:

                  DuetWebControl 2.1.0 when available, 2.0.7 until then
                  DuetWiFiServer 1.23
                  Duet Software Framework version 1.2.5 (for Duet 3/Raspberry Pi users)
                  Duet 3 expansion board and tool board firmware 3.01-RC4

                  It looks like this update is geared for those using an expansion board or SBC. I am just using the main board.

                  dc42 1 Reply Last reply Reply Quote 0
                  • Phaedrux
                    Phaedrux Moderator last edited by

                    It's still applicable.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • dc42
                      dc42 administrators @Weevil last edited by

                      @Weevil said in Printing stops:

                      @dc42 I was looking at the notes for RRF 3.01-RC4:

                      Recommended compatible firmware:

                      DuetWebControl 2.1.0 when available, 2.0.7 until then
                      DuetWiFiServer 1.23
                      Duet Software Framework version 1.2.5 (for Duet 3/Raspberry Pi users)
                      Duet 3 expansion board and tool board firmware 3.01-RC4

                      It looks like this update is geared for those using an expansion board or SBC. I am just using the main board.

                      No, the recommended compatible firmware is what you should be using if you have expansion boards or SBC.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      Weevil 2 Replies Last reply Reply Quote 1
                      • Weevil
                        Weevil @dc42 last edited by Weevil

                        @dc42 So I downloaded Duet3Firmware_MB6HC.bin and uploaded it unto System Files via the Web Control. It's there now but I was not prompted to install. The files just sits there. Per the Dozuki, it should prompt. Clearly, I am missing something here. c3985bd2-4380-48b8-b172-10f1d2f0c463-image.png

                        1 Reply Last reply Reply Quote 0
                        • Weevil
                          Weevil @dc42 last edited by

                          @dc42 My printer stopped printing again. The first print was successful. The second copy stopped midway. This time, I did not reset. Here's my M122 code:

                          === Diagnostics ===
                          RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.01-RC1 running on Duet 3 MB6HC
                          Board ID: 08DJM-956L2-G43S4-6J9D6-3SJ6T-KA62H
                          Used output buffers: 1 of 40 (8 max)
                          === RTOS ===
                          Static ram: 153800
                          Dynamic ram: 160816 of which 32 recycled
                          Exception stack ram used: 552
                          Never used ram: 78016
                          Tasks: NETWORK(ready,440) ETHERNET(blocked,448) HEAT(blocked,1104) CanReceiv(suspended,3820) CanSender(suspended,1436) CanClock(blocked,1432) TMC(blocked,68) MAIN(running,4328) IDLE(ready,76)
                          Owned mutexes:
                          === Platform ===
                          Last reset 13:22:38 ago, cause: power up
                          Last software reset at 2020-03-23 06:06, reason: User, spinning module GCodes, available RAM 78004 bytes (slot 2)
                          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
                          Error status: 0
                          Free file entries: 10
                          SD card 0 detected, interface speed: 25.0MBytes/sec
                          SD card longest block write time: 5.2ms, max retries 0
                          MCU temperature: min 29.4, current 35.4, max 42.4
                          Supply voltage: min 23.7, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
                          12V rail voltage: min 12.1, current 12.1, max 12.3, under voltage events: 0
                          Driver 0: standstill, reads 31070, writes 38 timeouts 0, SG min/max 0/1023
                          Driver 1: standstill, reads 31070, writes 38 timeouts 0, SG min/max 0/1023
                          Driver 2: standstill, reads 31059, writes 50 timeouts 0, SG min/max 0/1023
                          Driver 3: standstill, reads 31059, writes 50 timeouts 0, SG min/max 0/1023
                          Driver 4: standstill, reads 31060, writes 50 timeouts 0, SG min/max 0/1023
                          Driver 5: standstill, reads 31085, writes 26 timeouts 0, SG min/max 0/1023
                          Date/time: 2020-03-26 07:25:57
                          Slowest loop: 217.99ms; fastest: 0.07ms
                          === Move ===
                          Hiccups: 0(0), FreeDm: 375, MinFreeDm: 315, MaxWait: 10482521ms
                          Bed compensation in use: mesh, comp offset 0.000
                          === MainDDARing ===
                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                          === AuxDDARing ===
                          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
                          === Heat ===
                          Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                          Heater 1 is on, I-accum = 0.7
                          === 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
                          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
                          lcd is idle in state(s) 0
                          spi is idle in state(s) 0
                          autopause is idle in state(s) 0
                          Code queue is empty.
                          === Network ===
                          Slowest loop: 205.73ms; fastest: 0.03ms
                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                          HTTP sessions: 1 of 8

                          • Ethernet -
                            State: 5
                            Error counts: 0 0 0 0 0
                            Socket states: 2 2 2 2 2 2 0 2
                            === CAN ===
                            Messages sent 192750, longest wait 0ms for type 0
                            === Linux interface ===
                            State: 0, failed transfers: 0
                            Last transfer: 48158945ms ago
                            RX/TX seq numbers: 0/1
                            SPI underruns 0, overruns 0
                            Number of disconnects: 0
                            Buffer RX/TX: 0/0-0
                          1 Reply Last reply Reply Quote 0
                          • Danal
                            Danal last edited by

                            It should prompt... but if it doesn't, you can enter M997 on the console and it will upgrade.

                            If you have ONLY the one board (main with no expansion, tool, etc) , M997 is all that is required. If you have other boards, run M997 once for each board, with a B parameter, like M997 B1 where '1' is the CAN address of each board. Do wait for each to finish before starting another.

                            Verify with M115. Which also takes a B parameter, check each board. M115 is equivalent to M115 B0 and will check your main board. M115 B1 your first expansion, etc.

                            Delta / Kossel printer fanatic

                            Weevil 1 Reply Last reply Reply Quote 1
                            • Danal
                              Danal last edited by Danal

                              Also, and this is a long shot, I was having some hangs about an hour to 1.5 into prints. Cured those by re-seating the ribbon cable Pi<>Duet, reseating at both ends.

                              Again, a long shot... but easy to try (power off, of course).

                              Delta / Kossel printer fanatic

                              Weevil 1 Reply Last reply Reply Quote 0
                              • Weevil
                                Weevil @Danal last edited by

                                @Danal Thanks but my setup is a standalone.

                                1 Reply Last reply Reply Quote 0
                                • Danal
                                  Danal last edited by

                                  Well, then, it certainly isn't that cable!!

                                  Let us know if the code helps...

                                  Delta / Kossel printer fanatic

                                  1 Reply Last reply Reply Quote 0
                                  • Weevil
                                    Weevil @Danal last edited by

                                    @Danal Using code M997 returns this error: "Error: In-application programming binary "Duet3_SDiap_MB6HC.bin" not found"

                                    I cannot find that file in Github anywhere.

                                    1 Reply Last reply Reply Quote 0
                                    • Danal
                                      Danal last edited by

                                      It is in R3.0, because it hasn't changed since then... not ideal, makes it hard to find, but it is the way the build process and/or github work.

                                      Anyway, Here's a direct link: https://github.com/dc42/RepRapFirmware/releases/download/3.0/Duet3_SDiap_MB6HC.bin

                                      Delta / Kossel printer fanatic

                                      Weevil 1 Reply Last reply Reply Quote 2
                                      • Weevil
                                        Weevil @Danal last edited by

                                        @Danal Thanks, M997 worked this time. I really appreciate the support I get from you guys. I hope this solves my printer stopping issue.

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post
                                        Unless otherwise noted, all forum content is licensed under CC-BY-SA