multi filament help
-
Hi, I'm trying to configure my printer for dual extrusion, I have the printer setup and it works however I'm having issues in regard to slicing/macros and the workflow, what I'm getting confused with is does the slicer select the tool or does it just reference the custom tool change gcode box? in which case how does it know to swap back to tool0 say when it`s required?
apologies if this is something obvious but I've been trying to learn meta commands this week it's taken me two days to make a macro that toggles between both tools, my head is currently on a swivel and spinning freely!
-
@jumpedwithbothfeet It's going to depend on what slicer you use. But essentially, the tool (change) commands have to be embedded in the gcode file. When you print a gcode file, the firmware will do whatever is necessary whenever it encounters a "Tn" command. That "whatever is necessary" is what you've "told" the firmware to do via you tool change macros.
I can tell you what to do if you use Prusa Slicer (Slic3R) or it's variants but it'll vary if you use different slicers. Essentially you load multiple stl files into the slicer and tell the slicer which tool to use for each part. Using Slic3R or one of it's variants, the process involves adding the first stl to the platter, then click "Object" or right click on the part (stl file), then go to "Settings" and you'll have an option "Load Part". Click on that and you'll be able to the next stl. Repeat as necessary for all the other "parts" (stl files). You should then see a tree structure with the "Object" and all the associated "parts". In that same window, highlight each part of the object and you'll be able to select which extruder to use for that part (note that Slic3R has no concept of tools and uses "Extruder" instead or tool). Then when you slice the object, Slic3R will insert "Tn" commands wherever a different tool is needed.
Does that help?
-
@deckingman thanks for the reply, yes I think it does help, assuming I read your post correctly! essentially if the slicer has multiple tools in my case T0 and T1 it automatically inserts these into the produced print gcode, after that the printer takes over, which is where tfree0 or tfree1 would automatically be invoked depending on what tool is selected by the gcode?
I'm hoping I've understood that correctly everything would start making sense!
-
@jumpedwithbothfeet said in multi filament help:
@deckingman thanks for the reply, yes I think it does help, assuming I read your post correctly! essentially if the slicer has multiple tools in my case T0 and T1 it automatically inserts these into the produced print gcode, after that the printer takes over, which is where tfree0 or tfree1 would automatically be invoked depending on what tool is selected by the gcode?
I'm hoping I've understood that correctly everything would start making sense!
Yes - looks like you've got it. To expand on that, if you have a 2 part object made of 2 stl files called say "part1.stl" and "part2.stl", when you slice it you assign tool 0 (extruder 0) to part1 and tool 1 (extruder 1) to part 2. Then when you slice it, the resultant gcode file will have T0 and T1 embedded in it whenever a tool change is necessary. If you were using tool 0 and the next tool is tool 1 the sequence of events that the firmware would instigate would be as follows:
Run macro tfree0.g
Deselect tool 0 and set it's temperature to the standby temperature that you have defined by the R parameter in M568 or G10
Run macro tpre1.g
Set tool 1 to it's active temperature as defined by the S parameter in M568 or G10
Run macro tpost1.g
Apply any XY or Z offsets to the toolYou might find this useful https://docs.duet3d.com/en/User_manual/Tuning/Tool_changing
and/or a recent post I did on tool chnage files using meta commands
https://forum.duet3d.com/topic/29646/universal-tool-change-files-on-steroids -
@deckingman Thanks for the confirmation hopefully I can start making some headway, I had already read through the tool changing manual but to be honest, as much as made sense, it also didn't, couple that with the meta guide which was even worse until I found the github reference page, and I was truly struggling! thankfully you have filled in the gaps enough to hopefully get me sorted.
