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

    Duet "freezes" mid print?

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    7
    297
    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.
    • zockerleinundefined
      zockerlein
      last edited by zockerlein

      Hi,
      I got a big issue with my Duet Wifi Board.
      Sometimes (mostly during long prints, after a few hours or so) my printer simply freezes.
      The tool-fan is still running, temperature is being hold, but the printing-head doesnt move at all and the duet doesnt react to any commands.

      The problem occurred "out of the blue". I didnt change a thing on my printer (worked fine for 2 years) and now it simply stopped working.

      I suspected a faulty SD-Card, so I canged it, but the problem remains...

      Do you have any suggestions? πŸ™‚

      Daniel

      1 Reply Last reply Reply Quote 0
      • Nuramoriundefined
        Nuramori
        last edited by

        I’ve had this problem with the last two RCs.

        Not sure what causes it. I have a duet3 and thought maybe the raspberry pi heating up caused a freeze. I know you have a duet WiFi, so maybe the issue is in the firmware. There isn’t any commonality with what caused my freezes.

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

          What firmware version exactly are you using?

          Do you happen to be using high microstepping? x256 for example?

          If you run M122 after a print has been running for a while do you see a hiccup count?

          The only reliable leads I've seen on lockups like these have been from using high microstepping values on all axis and high-ish print speeds which results in a high number of hiccups to the point where the entire system locks up. Reducing microstepping to x16 with interpolation to x256 solves it.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • zockerleinundefined
            zockerlein
            last edited by

            I attached a screenshot πŸ™‚
            Duet.png

            Im using x256 on X- and Y-axis (without interpolation), but that never caused any problems till two days ago.

            M350 X256 Y256 Z128 E32 I0 ; Configure microstepping with interpolation
            

            Print speed is (as allways) 80mm/s.

            Ill try running M122 when it occurs again πŸ™‚

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

              Yes I could see how those settings could trigger the issue.

              When the step generator runs out of headroom it will pause for a fe micro seconds and drop the currently requested steps and then move on to the next ones. When it's only an occasional hiccup it's not much of an issue, but if it's never able to catch up it can generate an enormous number of hiccups and at that point it's either stuck waiting or it just locks up. Not sure which, but either way it's a failed print.

              Please try using x16 microsteps with interpolation to x256 enabled on all axis. You'll likely notice quieter operation from the Z and E axis and it should not impact print quality in any way.

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • zockerleinundefined
                zockerlein
                last edited by

                allright, thank you very much!
                Ill try that, as soon as my print finishes πŸ™‚

                1 Reply Last reply Reply Quote 0
                • zockerleinundefined
                  zockerlein
                  last edited by

                  Thank you so much Phaedrux! It seems to have worked. I didnt have any issues since then!

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