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

    Filament config

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    5
    10
    2.0k
    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.
    • Iamturbo1978undefined
      Iamturbo1978
      last edited by

      Hello everyone,

      I'm just starting with the filament feature. I have a working load, unload, and config macros. I noticed that after a power down and restart, the filament is loaded under the tool 0, like is should, but the config does not load. with in my filament config macro, I have it set up to clear any baby stepping, then do -0.10mm baby stepping. If I unload and load the filament, the config macro runs like it should, but after power down, the config macro doesn't load. Is there something I am missing, or is there something I should be doing to make the filament config macro run after power up?

      Thanks

      1 Reply Last reply Reply Quote 0
      • CaiJonasundefined
        CaiJonas
        last edited by

        Hi,

        I just join this because I have similiar problems. In my case the filament config does not work. First it worked perfect and I used the filaments config to set up diffrent pressure advance settings but now it doesn' work any more. I don't know what changed 😞

        Best Regards
        Cai

        1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators
          last edited by

          This is behaviour is intentional because the tool of the corresponding filament has to be selected in order for the config macro to work. See M703 for more information about how to run filament configs manually (https://reprap.org/wiki/G-code#M703:Get_Board_Type.2F_Configure_Filament).

          Duet software engineer

          CaiJonasundefined Iamturbo1978undefined 2 Replies Last reply Reply Quote 0
          • CaiJonasundefined
            CaiJonas @chrishamm
            last edited by

            @chrishamm

            I did add M703 in the tpost*.g file but that didn't change anything. Or do I have to put it somewhere else?

            timcurtis67undefined 1 Reply Last reply Reply Quote 0
            • Iamturbo1978undefined
              Iamturbo1978 @chrishamm
              last edited by

              @chrishamm thank you so much for the reply. It makes total sense why not to load the config automatically. I now understand what I need to do. Thank you.

              1 Reply Last reply Reply Quote 1
              • timcurtis67undefined
                timcurtis67 @CaiJonas
                last edited by

                @caijonas said in Filament config:

                @chrishamm

                I did add M703 in the tpost*.g file but that didn't change anything. Or do I have to put it somewhere else?

                What firmware version are you using? You must use 2.02 or newer to use the M703 feature.

                See https://duet3d.dozuki.com/Wiki/GCode#Section_M703_Configure_filament

                CaiJonasundefined 1 Reply Last reply Reply Quote 0
                • CaiJonasundefined
                  CaiJonas @timcurtis67
                  last edited by

                  @timcurtis67

                  I am using the latest one --> 2.02RC4

                  chrishammundefined 1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @CaiJonas
                    last edited by

                    @caijonas Be aware that no tool change macros are run if you select the tool in config.g or if you don't have the axes homed at the time the T-code is processed.

                    Duet software engineer

                    1 Reply Last reply Reply Quote 1
                    • genghisnico13undefined
                      genghisnico13
                      last edited by

                      I added M703 to the start macro that is called in the start gcode.
                      I believe there is room for improvement by loading the config automatically but this works.

                      1 Reply Last reply Reply Quote 0
                      • CaiJonasundefined
                        CaiJonas
                        last edited by

                        I Just added M703 into the start gcode of my slicer. Now it works. Thank you.

                        Best richtige
                        Cai

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