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

    Issues with dual extrusion and Prusaslicer with Duet 2

    Scheduled Pinned Locked Moved Solved
    Tuning and tweaking
    4
    40
    2.1k
    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.
    • Turboundefined
      Turbo @Danal
      last edited by

      @Danal said in Issues with dual extrusion and Prusaslicer with Duet 2:

      It should be waiting on that line in the toolchange macro. You may need a T-1 (unmount all tools) in the startup.

      As i have it now, I deleted the temp gcode in the start gcode, and now it generates it for the proper tool automatically, however, it places it before the start gcode. Inputting a T-1 in the prusaslicer start .gcode prompts an error message saying something about trying to extrude with no tool selected.

      Cant stop tuning wont stop tuning.
      Dbot, Custom i3, Voron 0&2

      1 Reply Last reply Reply Quote 0
      • Danalundefined
        Danal
        last edited by

        Yeah, sorry, I wasn't clear. May need a T-1 and a later T0... 🙂

        Delta / Kossel printer fanatic

        Turboundefined 1 Reply Last reply Reply Quote 0
        • Turboundefined
          Turbo @Danal
          last edited by Turbo

          @Danal the problem with putting in any "T" command in the start gcode is i have to modify it every time i want to change which tool i want to use, which is what i'm trying to avoid

          Cant stop tuning wont stop tuning.
          Dbot, Custom i3, Voron 0&2

          Danalundefined 1 Reply Last reply Reply Quote 0
          • Danalundefined
            Danal @Turbo
            last edited by

            @Turbo said in Issues with dual extrusion and Prusaslicer with Duet 2:

            @Danal the problem with putting in any "T" command in the start gcode is i have to modify it every time i want to change which tool i want to use, which is what i'm trying to avoid

            The generated G-code from any slicer that is aware of two or more tools should contain a mount command for the tool it is going to use.

            The T0 at the end of config.g is really there for slicers that are not multi tool aware, and that therefore do not have any T commands (to your point about not changing things per job...)

            Hmmm... what is a "eat our cake and have it too" for this? Let me ponder a little.

            Delta / Kossel printer fanatic

            Turboundefined 1 Reply Last reply Reply Quote 0
            • Turboundefined
              Turbo @Danal
              last edited by

              @Danal wait are you referring to a t-1 in the start gcode of the slicer, or in the config file?

              Cant stop tuning wont stop tuning.
              Dbot, Custom i3, Voron 0&2

              1 Reply Last reply Reply Quote 0
              • Danalundefined
                Danal
                last edited by

                In the config file. Or just don't have a T0.

                Delta / Kossel printer fanatic

                Turboundefined 1 Reply Last reply Reply Quote 0
                • Turboundefined
                  Turbo @Danal
                  last edited by

                  @Danal Gotchaaaaa. i assumed you meant the start gcode. Ill remove it and add a t-1

                  Cant stop tuning wont stop tuning.
                  Dbot, Custom i3, Voron 0&2

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

                    @Turbo said in Issues with dual extrusion and Prusaslicer with Duet 2:

                    adding an M109 S[first_layer_temperature] cause it to heat up the wrong extruder

                    M109 can't work without a tool being selected, so if no tool is selected then it selects the first available tool. So if you want to apply it to tool 1 instead of tool 0, you need to add the T1 parameter to the M109 command, or put a T1 command before the M109 command, or select T1 manually before you print the file.

                    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

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

                      @dc42 I understand that, and its what im trying to avoid. I dont want to have to change my start file every time i want to change the extruder, but i think i got it thanks to Danal.

                      Cant stop tuning wont stop tuning.
                      Dbot, Custom i3, Voron 0&2

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

                        @Turbo said in Issues with dual extrusion and Prusaslicer with Duet 2:

                        @dc42 I understand that, and its what im trying to avoid. I dont want to have to change my start file every time i want to change the extruder, but i think i got it thanks to Danal.

                        In that case, make sure there are no T commands anywhere in the GCode file. If you send T1 before you print it, it will use tool 1. Otherwise it will select tool 0 when it reaches the M109 command.

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