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

    wait for...

    Scheduled Pinned Locked Moved
    Gcode meta commands
    4
    12
    350
    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.
    • tecnoundefined
      tecno @MintyTrebor
      last edited by

      @MintyTrebor

      Thanks!

      I now have following in my start

      M104 S[first_layer_temperature] ; set extruder temp
      M140 S[first_layer_bed_temperature] ; set bed temp
      M190 S[first_layer_bed_temperature] ; wait for bed temp
      M109 S[first_layer_temperature] ; wait for extruder temp
      
      1 Reply Last reply Reply Quote 0
      • A Former User?
        A Former User @MintyTrebor
        last edited by A Former User

        This post is deleted!
        tecnoundefined MintyTreborundefined 2 Replies Last reply Reply Quote 0
        • tecnoundefined
          tecno @A Former User
          last edited by

          @Herve_Smith

          Yes

          A Former User? 1 Reply Last reply Reply Quote 0
          • MintyTreborundefined
            MintyTrebor @A Former User
            last edited by

            @Herve_Smith They are prusaslicer variables or as they call them placeholders.

            NodeDSF - Native Node-Red integration with Duet boards.
            BtnCmd - Customise DWC with user defined buttons/layouts/panels (DWC Plugin)
            ReleaseMgr - Duet update info inside DWC.
            Repo

            A Former User? 1 Reply Last reply Reply Quote 1
            • A Former User?
              A Former User @tecno
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • A Former User?
                A Former User @MintyTrebor
                last edited by

                This post is deleted!
                MintyTreborundefined 1 Reply Last reply Reply Quote 0
                • MintyTreborundefined
                  MintyTrebor @A Former User
                  last edited by

                  @Herve_Smith The syntax is described here

                  NodeDSF - Native Node-Red integration with Duet boards.
                  BtnCmd - Customise DWC with user defined buttons/layouts/panels (DWC Plugin)
                  ReleaseMgr - Duet update info inside DWC.
                  Repo

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

                    @tecno said in wait for...:

                    How do I setup following start gcode in slicer Prusa or Superslicer.

                    Have start to read temperature settings from gcodefile for bed and hotend and wait for temperatures to reach set values?

                    To wait for all temperatures to reach set values, use M116.

                    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

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

                      @dc42

                      So is this then correct?

                      M104 S[first_layer_temperature] ; set extruder temp
                      M140 S[first_layer_bed_temperature] ; set bed temp
                      M190 S[first_layer_bed_temperature] ; wait for bed temp
                      M109 S[first_layer_temperature] ; wait for extruder temp
                      M116
                      

                      How about chamber temp if I want it to reach xC before start print?

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

                        @tecno there are multiple ways of doing it. M104, M140 and M141 set the hot end, bed and chamber temperatures respectively without waiting for them to reach temperature before proceeding to the next command. So they will all heat concurrently. Then you can use M116 to wait for them all to be reached:

                        M104 S225 ; set extruder temp
                        M140 S70 ; set bed temp
                        M141 S60 ; set chamber temp
                        M116 ; wait for all temps to be reached
                        

                        Or if the hot end heats quickly but the bed and chamber heat slowly, you might want to do this instead:

                        M140 S70 ; set bed temp
                        M141 S60 ; set chamber temp
                        M116 ; wait for bed and chamber temperatures to be reached before heating the hot end
                        M104 S225 ; set extruder temp
                        M116 ; wait for all temps to be reached
                        

                        You can substitute variables in [ ] for the actual values if the slicer supports that.

                        Using M104 followed by M109, or M140 followed by M190 is the old (Marlin) way of doing things.

                        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 1
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA