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

    Print "stuck"

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    592
    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.
    • auserundefined
      auser
      last edited by

      Dear all
      I treid searching in the forum but could not really find anthing that seems to apply:
      I have a print that is "suck":
      –> Print head is stationary, Bed and Head temperature are ok (and getting updated).
      But I have no idea how I could get the print to continue (Heater shows "active" in DWC).
      Any Ideas?
      This is a Duet 0.6 Firmware 1.04f-dc42 DWC1.06 (yes I know I should update šŸ˜‰
      many thanks for all your help!

      PS: I think i have seen this before but it did recover itself, if I had a look at the layer times there have been layers (max 1 per print) that took a LOT longer than they should have...

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

        If it's a particular file, and it gets stuck at the same place each time, then it probably means the gcode file isn't complete. This happens quite easily with older versions of slic3r, because it's easy to upload the file via DWC before slic3r has finished writing it.

        However, that firmware is so old that I wouldn't rule out some feature of that version that I have forgotten about.

        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

        1 Reply Last reply Reply Quote 0
        • auserundefined
          auser
          last edited by

          No particular file, same print came out flawless just "before" the failed print. But there was one layer that took roughly 5-8 times as long as it should have, in the successful print. I'm hoping on bad weather this weekend to do the update šŸ˜‰

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