Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Solved M572 D1 S0.1

    Documentation
    5
    9
    110
    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.
    • paolozampini1973
      paolozampini1973 last edited by

      M572 D1 S0.1 someone can tell me where to put this command what I mean anywhere in the config.G ?

      bot 1 Reply Last reply Reply Quote 0
      • bot
        bot @paolozampini1973 last edited by

        Different filaments, or print setting combinations, could require different values of M572 pressure advance. For this reason, it's better to put the g-code in any filament-related macros, or even start g-code in the slicer on a per-print basis.

        *not actually a robot

        paolozampini1973 1 Reply Last reply Reply Quote 0
        • paolozampini1973
          paolozampini1973 @bot last edited by

          @bot so I have to install macros?

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

            @paolozampini1973 if you always print with the same sort of filament, then you can put it in config.g.

            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

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

              @dc42 Yes for now 99% I will always print with the same filament but if I have to install macros I install them and where I can download the macros and then I can put the command on any point of the config file Thanks in advance

              1 Reply Last reply Reply Quote 0
              • Phaedrux
                Phaedrux Moderator last edited by

                Macros are just text files that have gcode commands in them. You can create them in the Duet Web Interface itself, or in a text editor and upload them.

                https://docs.duet3d.com/en/User_manual/Tuning/Macros_tasks

                Z-Bot CoreXY Build | Thingiverse Profile

                paolozampini1973 1 Reply Last reply Reply Quote 0
                • paolozampini1973
                  paolozampini1973 @Phaedrux last edited by

                  @phaedrux Thanks for the information. I'm trying to solve a problem with the vertical line

                  deckingman 1 Reply Last reply Reply Quote 0
                  • deckingman
                    deckingman @paolozampini1973 last edited by

                    @paolozampini1973 For info, gcodes are acted on as soon as they are encountered and the latest values will override any previous values. So you could have M572 in your config.g as a default value. This will get acted on whenever the board boots up. Then if you want to change it for a particular print, you could have another M572 in the slicer start code, or send it manually through the web interface, or put it inside a macro and run that macro. There are numerous options - pick whichever one works best for you.

                    Ian
                    https://somei3deas.wordpress.com/
                    https://www.youtube.com/@deckingman

                    paolozampini1973 1 Reply Last reply Reply Quote 1
                    • paolozampini1973
                      paolozampini1973 @deckingman last edited by

                      @deckingman Thank you

                      1 Reply Last reply Reply Quote 0
                      • Topic has been marked as a question  droftarts droftarts 
                      • Topic has been marked as solved  droftarts droftarts 
                      • First post
                        Last post
                      Unless otherwise noted, all forum content is licensed under CC-BY-SA