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

    Change print speed in gcode

    Scheduled Pinned Locked Moved
    Firmware wishlist
    4
    7
    3.4k
    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.
    • peirofundefined
      peirof
      last edited by

      Hi,

      I know this question it's not of this forum, but... I post for you can help me...

      I have to print a piece, the first 80% there is not problem but in last 20% are curved, vaults....
      I can generate the gcode, and in the layer when start vaults, reduce print speed... Maybe later height?

      I think that Slic3r PE, can do this...

      What line I have to insert in gcode for change print speed?

      Thanks

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @peirof
        last edited by

        @peirof If you want ot reduce the speed simply for the top 20% of layers then you can add the M220 command (or the speed slider on DWC) to a lower %:
        https://duet3d.dozuki.com/Wiki/Gcode#Section_M220_Set_speed_factor_override_percentage

        I assume though that that is not exactly what you are trying to do. Am I right in thingking you want only bridges to be printed slower? In that case it really is a slicer's job as it knows what parts of the print refer to bridges and what do not. the firmware does not know if a line it is laying down in over a gap or over a previous line.

        It is probably different in all firmware, but there should be a setting for bridge speed. Cura has just introduced these settings apparently (but I have not tried them):

        https://community.ultimaker.com/topic/22195-introducing-the-experimental-bridging-settings/

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • fmaundefined
          fma
          last edited by

          The other day, I had this idea: what about using a specific move G-code for each type of extruding move? This way, all speeds/accel/... could be changed dynamically by the firmware, while extruding.

          Frédéric

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

            @fma said in Change print speed in gcode:

            The other day, I had this idea: what about using a specific move G-code for each type of extruding move? This way, all speeds/accel/... could be changed dynamically by the firmware, while extruding.

            I proposed this at https://reprap.org/forum/read.php?1,803621 but I didn't get much support.

            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

            T3P3Tonyundefined 1 Reply Last reply Reply Quote 1
            • T3P3Tonyundefined
              T3P3Tony administrators @dc42
              last edited by T3P3Tony

              @dc42 said in Change print speed in gcode:

              @fma said in Change print speed in gcode:

              The other day, I had this idea: what about using a specific move G-code for each type of extruding move? This way, all speeds/accel/... could be changed dynamically by the firmware, while extruding.

              I proposed this at https://reprap.org/forum/read.php?1,803621 but I didn't get much support.

              Its another chicken and egg problem. The slicers would need to label G1 moves with the move type before the firmware could implement that...

              www.duet3d.com

              1 Reply Last reply Reply Quote 0
              • fmaundefined
                fma
                last edited by

                I think it should be first implemented by the firmware, as it is possible to generate test g-code files with scripts, or to modify real g-code files with post-processors, to have something working.

                Frédéric

                T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                • T3P3Tonyundefined
                  T3P3Tony administrators @fma
                  last edited by

                  @fma fair enough. I have moved the topic to the firmware wishlist section.

                  @peirof in summary - it cant be done by the firmware right now. it can be done by some/most slicers.

                  www.duet3d.com

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