Nesting and quoting software for CypCut

What Zorocut does before the file reaches CypCut

• Cleans the customer's DXF: closes small gaps, removes duplicate lines, reads the units or detects them when the file does not say, and keeps text and dimensions off the cut. Every repair is reported.
• Nests true-shape on the sheet formats you stock, with part-in-part, a rotation rule per part and mirrored copies for left and right pairs.
• Prices every part and the order before a sheet is loaded: machine time from cut length, pierces and corners, or per metre plus per pierce.
• Writes the parts in cut order — holes before the outline, part by part — so the file CypCut imports already has a sensible sequence. CypCut can still sort it again.

CypCut's own nesting, and when a separate nester pays

CypCut has a built-in nest. Its v6.5 manual caps it at 50 part types and 20 sheets, with array as the only strategy, and it runs on the machine's PC. It has co-edge, bridges, micro-joints and remnants, but no quote. A separate nester earns its place when the jobs have many different parts, when the nest and the price should be done in the office while the machine cuts, or when the customer wants the price first. The full comparison is on Zorocut vs CypCut nesting.

The CypCut family

All three read DXF and tidy it on import: they remove tiny shapes and duplicate lines, join unclosed shapes, smooth, and detect inner and outer contours. CypCut's layer 0 is the background layer, which is never cut; in CypCut layer 15 is processed first and layer 16 last. Which controller runs which version is on the FSCUT page.

Settings in Zorocut

1. Machine tab: kind Fiber laser, your power in W, Controller CypCut.
2. Export profile DXF R2000. Choose R12 only if your CypCut refuses the file: the entities are the same, only the header is older.
3. Part labels (layer ZC_LABEL): keep them on if you want part names on screen, and map that layer to CypCut layer 0 so they are not cut.
4. Sheet outline (layer ZC_SHEET) is written on a layer that is switched off; map it to layer 0 as well.
5. Output folder: a USB stick or the controller PC's network share. Export DXF writes one file per sheet there.

The layer-by-layer mapping dialog, step by step, is in the guide Export DXF for CypCut and FSCUT.

What Zorocut does not do for CypCut

• It writes DXF only — no LXD, lxds or CypNest .nrp2 task files.
• No lead-ins, kerf compensation, micro-joints, bridges or co-edge: CypCut adds them with its own tools.
• No G-code and no connection to the machine. The operator in front of CypCut stays in charge of every cut.
• No shared edges between parts: CypCut removes duplicate lines on import, so two parts on one line could lose an edge. Zorocut keeps the part spacing above zero and leaves common-line cutting to CypCut's co-edge.

Not verified yet

The CypCut manuals we read do not state the newest DXF version CypCut accepts, how it treats blocks, splines and DXF text, whether it reads the $INSUNITS unit from the header, or whether a layer mapping is remembered from one import to the next. Zorocut's file sidesteps the first three — no blocks, no splines, labels only on their own layer, mm in the header — but until we have imported it on a real CypCut controller, cut one scrap sheet before the first real job.

Les noms de produits servent uniquement à décrire la compatibilité. Zorocut n'est pas affilié à leurs fabricants.