![]() (which is on GSAPP computers), see this tutorial instead. _Note that this tutorial works in ArcGIS version 10. They could extrude almost completely independently, but the slicer would have to have smart enough algorithms to keep them from crashing into each other.Exporting 3D Data and Importing in Rhino and 3DS Max The most capable way that I can imaging of doing it would be to mount each extruder on a separate robotic arm. Simultaneous extrusion would still be limited to printing parallel lines, but at least it could do so at any angle and at any distance (in the range (0-nozzle separation distance], at least). The simplest way I can think of to do that would be to add an axis to the typical cartesian machine that would rotate the extruder nozzles about the Z axis (or equivalently, rotate the print bed). On the other hand, if you had a way to vary the geometry between the extruder nozzles, then simultaneous extrusion might become useful in enough generalizable cases to be worth implementing. Therefore, IMO it's unlikely to be supported either now or in the foreseeable future. That seems limited to some pretty niche situations, and therefore strikes me as not worth the effort to develop toolpath-generation code for. Now, here's the real problem: since the current typical dual-extrusion printer design has a fixed geometric relationship between the two nozzles, this sort of simultaneous extrusion would only be useful in cases where the slicer actually wants to extrude the two filaments along paths that are (a) parallel and (b) the correct (angle-dependent) distance apart.īy "angle-dependent," what I mean is that if you have two nozzles aligned along the X axis 20mm apart, then you could simultaneously extrude parallel lines 20mm apart at 90° from the X axis, or parallel lines 7.07mm apart at 45° from the X axis, or adjacent parallel lines at ~0.01° from the X axis, etc. but that depends on both your slicing software and your machine's firmware supporting such a thing. G1 X90.6 Y13.8 E22.4:11.2 Move to 90.6mm on the X axis and 13.8mm on the Y axis while extruding 22.4mm of material from extruder 0 and 11.2mm of material from extruder 1 It seems like in principle you could have a command sequence that looked like this: T0:1 Set extruders 0 and 1 active at the same time If only one value is provided where a value is needed for each extruder, then that value is applied to all extruders. Typically this is used to specify extruder parameters, with one value provided per extruder. ![]() ![]() In RepRapFirmware, some parameters can be followed by more than one number, with colon used to separate them. However, looking at, I found this statement: So even if you tried to make it as close to simultaneous as possible by only running one G1 command between extruder change commands, it's still serialized and only using one at a time. do a bunch of move and extrude commands for extruder 1 do a bunch of move and extrude commands for extruder 0 I'm generating a dual-color octopus in Slic3r to see how it looks, but it's taking forever): T0 Set extruder 0 active The extrusion parameter of that command operates on whichever extruder is currently "active." Apparently, setting the active extruder is a separate command, so the usual way it works is like this (not sure about the extruder change syntax. For example, a typical move and print command might look like this: G1 X90.6 Y13.8 E22.4 Move to 90.6mm on the X axis and 13.8mm on the Y axis while extruding 22.4mm of material That means only one command can be executing at a time. Non-reddit communities are listed in our getting started guideĪs far as I can tell, G-code is fundamentally serial. ![]() We welcome community contributions to this wiki! Related Communities Hit the report button or message the mods NEED HELP? WE HAVE A WIKI!
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |