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
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.
-
@Danal wait are you referring to a t-1 in the start gcode of the slicer, or in the config file?
-
In the config file. Or just don't have a T0.
-
@Danal Gotchaaaaa. i assumed you meant the start gcode. Ill remove it and add a t-1
-
@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 -
@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.
-
@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.
