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

    Firmware ruins vase prints

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    4
    7
    669
    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.
    • gnydickundefined
      gnydick
      last edited by

      When prints finish the g-code that executes at the end doesn't kick in immediately. The print head sits there for a couple seconds first and keeps melting the wall.

      0_1548526371165_IMG_20190126_101123.jpg

      fcwiltundefined 1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @gnydick
        last edited by

        @gnydick We need more information.

        What version of the firmware are you running?

        What does your "print finish" g-code look like?

        Frederick

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        gnydickundefined 1 Reply Last reply Reply Quote 0
        • gnydickundefined
          gnydick @fcwilt
          last edited by gnydick

          @fcwilt latest firmware, and my end gcode from my slicer disables stuff, afaik, there are no G4 commands. No matter what is in there, it should all be executed near instantaneously because there are no moves or waits.

          Phaedruxundefined richardmckennaundefined 2 Replies Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator @gnydick
            last edited by

            @gnydick If you don't post what you have in there we can't see what might be causing the problem.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 1
            • richardmckennaundefined
              richardmckenna @gnydick
              last edited by

              @gnydick

              because there are no moves or waits

              Surely if there are no moves in your end gcode the nozzle will just stay where it ends? Like others have said we canโ€™t help if we canโ€™t see the code ๐Ÿค”

              gnydickundefined 1 Reply Last reply Reply Quote 0
              • gnydickundefined
                gnydick @richardmckenna
                last edited by

                @richardmckenna No moves other than moving away ๐Ÿ˜‰ I see what is happening. I had a slow retract in there that shouldn't have been slow.

                richardmckennaundefined 1 Reply Last reply Reply Quote 0
                • richardmckennaundefined
                  richardmckenna @gnydick
                  last edited by

                  @gnydick cool glad you figured it out ๐Ÿ‘

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