Solved Issues with dual extrusion and Prusaslicer with Duet 2
-
Got it. I just missed it with my eye, somehow.
Hmmm.... Let me upgrade to the latest release, I'm on 2.0.0 right now. Be a min or two...
-
Okay so deleting The temps from the start gcode solved it I believe. I have a print running right now, but ill try it afterwards, but the gcode reflects the fix.
-
Good. I'm still going to install 2.2, just because
-
@Danal Okay so deleting it kinda fixed it but not really. It does auto add the code for the tool requested, but will try to print before the extruder is up to temp. I dont know why.
-
adding an M109 S[first_layer_temperature] cause it to heat up the wrong extruder
Cant stop tuning wont stop tuning.
Dbot, Custom i3, Voron 0&2 -
Adding an M116 seems to have done the trick, however, i get an error message saying that tool 0 didnt move because it never got up to temp, possibly because it is set as active by default (although im not using is to why even prompt me?), and the second extruder only gets set to active when the standalone T1 command is executed in gcode. I would leave it, but i dont want an error message every print, as it concerns me.
-
Waiting for the tool is not up to the slicer. Be sure you have a "M116 H2 " near the beginning of your
/sys/tpost1.g
file. Actually tpost0.g and tpost1.g
If you don't have those files, create them.
-
@Danal
M116 H1 in the tpost0 and H2 in tpost1 as they refer to heater number, or h2 in both? -
@Turbo said in Issues with dual extrusion and Prusaslicer with Duet 2:
@Danal
M116 H1 in the tpost0 and H2 in tpost1 as they refer to heater number, or h2 in both?Heater number. Which, in my config, is Tool Number + 1. Because H0 is bed.
-
@Danal After including that, nothing seems to have changed. when it goes to start the purge line i configured in the start gcode, it doesnt extrude because its not up to temp, defeating the purpose
Cant stop tuning wont stop tuning.
Dbot, Custom i3, Voron 0&2 -
@Turbo said in Issues with dual extrusion and Prusaslicer with Duet 2:
@Danal After including that, nothing seems to have changed. when it goes to start the purge line i configured in the start gcode, it doesnt extrude because its not up to temp, defeating the purpose
It should be waiting on that line in the toolchange macro. You may need a T-1 (unmount all tools) in the startup.
Delta / Kossel printer fanatic
-
@Turbo Use G10 S and R to set the active and standby temperatured. You need to put the commands in your slicer start gcode. I'm trying to remember how I had multiple tools set up years ago when I used a Mendel Tri- colour. I'm fairly sure that's all I had to do. When changing tools, the firmware waits (or it used to) for the new tool to reach the active temperature and (I think) the old tool to cool to the standby temperature. No need for any commands other than Tn. These days, I use up to 9 tools but they share a common heater so all I have to do is put G10 Pn Snn Rnn for each tool in the start gcode and use the same value for S and R.
-
@deckingman, the goal is to not change the default Slicer3pe start gcode.
Part of this is based on the fact that I am using a multi-tool printer, and my "custom start gcode" is blank, and it works (properly heats tools at the right time, etc)
So another phrasing could be: Why would @Turbo have to use custom start gcode when others don't?
-
@Danal Ahh OK. I hadn't read the entire thread - just the title ("Issues with dual extrusion and Prusaslicer with Duet 2") and one or two posts. Sorry for not realising that there were restrictions on what could, and could not, be done to help. I'll leave you guys to it then.
-
@deckingman said in Issues with dual extrusion and Prusaslicer with Duet 2:
@Danal Ahh OK. I hadn't read the entire thread - just the title ("Issues with dual extrusion and Prusaslicer with Duet 2") and one or two posts. Sorry for not realising that there were restrictions on what could, and could not, be done to help. I'll leave you guys to it then.
No prob, man, your insights are always welcome!
-
@Danal No worries. For info, the G10 S and R thing was used along with X and Y offsets on the original RepRap Pro Mendel Tri-Colour and running the original (Andrian Bowyer?) RepRap firmware on Duet 06 boards. It even pre-dates the use of tool change macros (I think). I guess it would still be valid for fixed multi-nozzle setups, but not for tool changers.
-
@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.
-
Yeah, sorry, I wasn't clear. May need a T-1 and a later T0...
-
@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
-
@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.
