In this post I will give a brief overview of how Slice-Up works.
By the time you are done reading, you will have a clear idea of how to navigate through different Slice-Up modules. Also, how the interface works within each module.
Two important things about Slice-Up
The first thing to know is that Slice-Up works with lines, not solids. Each line is the path that your extruder will take. It is your responsibility to design clever paths. It is also your responsibility to create enough space for your extrusion.
In other words - you can define the spatial configuration (i.e. layer height, XY position, direction) during design, while you can compute the flow when you finalise the gcode.
The second important thing is that Slice-Up is composed of several modules. Each module performs a specific operation. You can define how that operation is performed by changing the parameters in each module. You can perform any number of operations, in (almost) any order you like.
In other words - you design on two different levels. On the lower level, you shape your design by changing the parameters within each module. On the higher level, you design by arranging different modules together. You can use as many -or as little- modules as you like. Sometimes less is more, sometimes less is just less.
How to navigate through different modules
You move from a module to the next one by means of downloading outputs and uploading inputs. The output of one module becomes the input of the next one, and so on. The last output before printing is a gcode file.
Modules are currently organized in 3 main blocks: define, modify, finalize.
Generally speaking, the flow should be downstream, from one block to the next.
In the define block, you can define your primary toolpath.
Your primary toolpath is the starting block -or skeleton- of your design.
The modify block is where the magic happens: each module gives you a different way to create and/or organize complexity starting from your primary toolpath. Here any module can be both the precursor or the successor of any other module, even of himself. The only exception to the rule is the baseFill module: baseFill output should always go to a gcode module.
Modules in the finalize block transform your design -or linework- to gCode.
Currently are available 4 different logic for generating gCode in total (open or closed curves, retraction or single extrusion).
Modelling interface
At the top of the page you will find a few basic info describing what the module does, what type of input requires, and what output produces, and a tip.
The interface is similar for all modules, and it is as follow:
Will send you back to the gCode Flow Map
Access info and hints regarding model parameters
Links to the dedicated support area
Control the model viewport (e.g. go full-screen, access camera views, etc.)
Import your input at the top of the parameters list
All the model parameters you can access and interact with
Export your output at the end of the list
Let you choose a finalize module to continue
Let you choose a modify module to continue
And this is pretty much all you need to get started!
Go on and have fun, if you have any doubt or question, or need specific informations feel free to ask in our support area.
Comments