Cabinet·CNC exports seven documents from a single model: a CSV cut list, an SVG sheet layout, DXF R12 whose layer names carry the cut depth, GRBL and Mach3 G-code per tool and per sheet, a table-saw cut sequence, labels and assembly instructions, and a hardware schedule with a costed quote. Everything comes from the same model, so nothing is re-keyed.
A DXF cannot say that a recess is 6 mm deep: it holds flat outlines only. The convention VCarve and Aspire read is therefore to write the depth into the layer name, and Cabinet·CNC follows it: through profiles go on a cut layer, each pocket on a layer whose name carries its depth, each drill diameter on its own.
The file is R12, the version everything still reads. Polylines are closed, which avoids cleaning up open contours on import — the first half hour lost to a badly formed DXF.
Operations come out in the order they must be done: drilling first, pockets and dados next, the profile last. Cutting the profile first would free the part, which would then move under the cutter during everything that follows.
One file per tool rather than a single file with tool changes: on a machine with no automatic changer that is safer — you cannot start a program that assumes a cutter already fitted. Holding tabs keep the parts in the sheet at the end of the profile, and entry is a ramp rather than a vertical plunge.
A test suite replays every program produced and checks that no rapid move enters the material, that no point is cut deeper than one pass at a time, and that the spindle starts before the first move. That is not validation on your machine: air-cut or simulate every program before you cut.
A shaker front is pocketed on the face and bored on the back; a panel machined on both faces therefore passes under the spindle twice. Programs are split per face, face B is mirrored about the sheet width, and a header announces the flip.
A single file assuming the flip had happened would drill the hinge cups straight through the front. That is the mistake that costs a sheet, and it only shows afterwards.
Any CAM or drawing package that reads DXF R12: VCarve, Aspire, Fusion 360, LibreCAD, Inkscape, AutoCAD. The layer convention with the depth in the name is the one VCarve and Aspire use to assign machining operations automatically.
It is produced for GRBL and Mach3, which cover the large majority of shop and hobby CNCs. The dialect is standard G-code — G0, G1, G2/G3, M3/M5 — so most controllers read it. Always simulate before you cut: it is your machine, not ours.
Yes. The table-saw cut sequence is made for that: it gives the order of cuts and the fence setting at each step, from the same raw sheets as the nesting plan. A shop without a CNC uses the cut list, the cut sequence and the labels.
No. All computation happens in the browser, on your machine. No drawing, no dimension and no file leaves your computer, and the app keeps working offline once the page has loaded.
Free · no account · nothing is sent to a server