The cutter does not want “nesting software”. It wants the file it has eaten for years.
Summa, Graphtec, iEcho, Zünd and Kongsberg are not “generally compatible”. They are compatible with a container: spotted PDF, DXF, a native table job. Nesting software that cannot say what comes out is a slide.
Updated 28 August 2026. NestPrintCut editorial — the team that builds RolCut. Scores follow the public method. We do not run a 200-roll lab we have not run.
| Table / plotter | What it usually eats | Watch |
|---|---|---|
| Summa S / F + OPOS | PDF + spot, OPOS marks | Spot name and mark size |
| Graphtec CE / FC | PDF / HPGL / DXF | Old firmware likes DXF |
| iEcho | PDF + DXF, camera | Kiss/thru layers, not “a black stroke” |
| Zünd / Cut Center | Native job or Griffin PDF/DXF | Integration > generic PDF |
| Kongsberg | PDF / DXF + i-cut | Marks and tool layers |
Why “works with every plotter” is an empty sentence
It is easy to ship 800 small-vinyl drivers — EasyCut lives on that list. An iEcho shop does not need 800 drivers. It needs a spot, a layer and a mark inside camera tolerance. Software that emits cut.pdf + cut.dxf and lets you type the spot name closes 80% of tables without pretending to be a driver.
A recipe once, not on every job
Roll width, kerf, gutter, kiss/thru, mark size, piece code. That is a shop setting, not an “export option”. RolCut keeps it in a recipe. PrimeCenter and Griffin — in a workflow / preset. Shops that click this from zero on every wallpaper have people-waste, not algorithm-waste.
Questions
Does RolCut ship a Summa driver?
No. It emits files Summa (and the RIP) already understand. The driver sits on the table and the RIP, not in the nester.
iEcho without DXF?
Some tables will take a spotted PDF. Keep DXF as plan B. Software without both is a purchase risk.