This shows you the differences between two versions of the page.
rhino:mitch_notes_2dcutting [2015/09/14] |
rhino:mitch_notes_2dcutting [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Preparing Rhino Files for Laser/Knife Cutting ====== | ||
+ | |||
+ | This is a summary of how we run our [[http:// | ||
+ | |||
+ | - For the lasers, we run directly out of Rhino. | ||
+ | - Unfortunately for the Zünd, there is no printer driver available, so it needs to be run with other software. The software that we use is Type3. It’s powerful but pretty painful to use. It can act as a machine control for the Zünd, but its DXF import is glitchy with certain types of objects. | ||
+ | - We thus need to create a DXF export model that works both for Rhino and Type3. | ||
+ | - The other reason for needing to create a special export model is that Default DXF scheme explodes polylines/ | ||
+ | - Exploded curves will be cut as separate entities, which can substantially lengthen cutting times and even lock the machines up if there are many, many small segments. | ||
+ | - So, we create an export scheme where polylines/ | ||
+ | - Since the files are set up for 2-D cutting, in principle there shouldn’t be any surfaces in them. But if there are accidentally, | ||
+ | - In addition to the export scheme, we have a set of rules for setting up cutting files. The rules include how to lay out the geometry on the page, colors to use, size and spacing constraints, | ||
+ | |||
+ | Mitch Heynick | ||
+ | |||
+ | > **Author:** //Mitch Heynick email: < | ||