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

    Gcode after print completes

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    6
    951
    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.
    • BlueDustundefined
      BlueDust
      last edited by

      I thought I saw someone mention this but wasn't able to find it...
      The nozzle doesn't move away after each print completes and is leaving large blobs. Can I put the Gcode to move the hotend to g28 x after each print? I have been putting this code in a few places, last one being stop.g (but I think this is only for cancelled prints) and its not working.
      Where do I put this code?
      If I have to add it to ending scripts in S3d, that easy to do, but would prefer to do this on the Duet.

      Thanks!

      Fun, that 3 letter word with "u" in the middle.

      wilrikerundefined 1 Reply Last reply Reply Quote 0
      • PlasticMetalundefined
        PlasticMetal
        last edited by

        Not your preferred choice, but I do it in S3D. My normal end script:

        M104 S0 ; turn off extruder
        M140 S0 ; turn off bed
        M106 S0 ; turn off part fans
        G28 ; home axes
        M84 ; disable motors

        1 Reply Last reply Reply Quote 1
        • wilrikerundefined
          wilriker @BlueDust
          last edited by wilriker

          @bluedust What I did is that I created print_start.g and print_end.g in Duet's sys folder that contain my start and end Gcodes. In my slicer I simply use

          M98 P/sys/print_start.g
          

          as start code (and if course respectively fit the end code). This way I can even still modify my start code after a print has started and while the printer is still heating up. Needed it rarely but comes in handy once you do need it.

          Of course the same goes for end code to be modifiable even after print started.

          Manuel
          Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
          with probably always latest firmware/DWC (incl. betas or self-compiled)
          My Tool Collection

          1 Reply Last reply Reply Quote 2
          • BlueDustundefined
            BlueDust
            last edited by

            @PlasticMetal @wilriker
            Thanks guys! all very helpful!

            Fun, that 3 letter word with "u" in the middle.

            1 Reply Last reply Reply Quote 0
            • token47undefined
              token47
              last edited by

              There is already stop.g that will be run at the end of the print if the sliced gcode sends an M0. I prefer to just put "M0" at the end script so I will keep the gcode at only one place, since stop.g will also be called in other circunstancies.

              1 Reply Last reply Reply Quote 1
              • BlueDustundefined
                BlueDust
                last edited by

                @token47
                Also very helpful! I will be combining all 3 of your suggestions in the near future.

                Thanks!

                Fun, that 3 letter word with "u" in the middle.

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