The DXF is not redrawn. It comes from the piece.
In Marmos, the file is not an illustrative outline created after quoting. It exports the stones frozen in the cut map: nominal millimeter dimensions, curves, cutouts and fabrication intent separated into CAM layers.
The geometry that formed the price
Top, aprons, backsplashes, build-ups and cutouts come from the parametric model used to quote. Measurements are not entered a second time between selling the piece and opening it in CAM.
Declared millimeters and origin
The DXF declares millimeters and uses the lower-left origin, X to the right and Y up. The transform is rigid: the piece is not rescaled or mirrored on export.
A curve stays a curve
Arcs travel as bulges, the native curved segment of a DXF polyline. Holes, cutouts and oval sinks use their own entities or a compatible approximation in R12.
One layer per intent
Outline, cutout, hole, polish, edge profile, miter, pocket and back kerf do not arrive mixed together. Layer names and colors help the operator map geometry to the right CAM operation.
Loose pieces or arranged slab
The pieces DXF serves shops that nest in CAM. The slab DXF preserves the cutting-plan arrangement for profiles that use it. They are separate artifacts because they support different shop workflows.
DXF carries facts; CAM chooses tools
The file carries nominal geometry and intent. Kerf compensation, tooling, depth, lead-in, final order and collision remain with the CAM and the machine manufacturer's approved postprocessor.
Files for the real shop workflow.
DXF R2000
Closed polylines, arcs, circles, ellipses, named layers, colors and declared units.
DXF R12
An alternative for older importers, without relying on entities those readers do not understand.
Slab package
A ZIP with DXF, versioned manifest and README explaining units, origin, layers and warnings.
Review file
A separate view overlays references for checking; the CAM-targeted file keeps only what belongs to that machine profile.
Questions about DXF and CNC
- Does the Marmos DXF go straight to the machine?
- No. DXF is the geometry file imported into CAM. CAM chooses tools, compensation, path and order, and the manufacturer's postprocessor generates the machine program. Keeping those responsibilities separate prevents a generic file from pretending to know every machine.
- Does it work with every CNC or bridge saw?
- Marmos generates R2000 and R12 DXF using common stone-CAM conventions, but every CAM, postprocessor and machine combination must be approved by the shop before its first production cut. Format compatibility does not replace a real machine test.
- Does the file include kerf and tool compensation?
- No. Geometry is nominal and CAM owns compensation. If Marmos offset the contour and CAM compensated again, the stone would be wrong. Slab planning accounts for kerf when arranging material, but the final toolpath belongs to CAM.
- What is the difference between a pieces DXF and a slab DXF?
- The pieces DXF delivers stones without claiming a slab position, so the operator can nest them in CAM over the real material. The slab DXF carries an existing plan arrangement plus references and the manifest for that slab.
- Do arcs, sinks and operations stay separate?
- Yes. Arcs remain curved geometry, cutouts and holes have their own boundaries, and polish, profile, miter, pocket and back-kerf operations sit on separate layers. R12 uses compatible alternatives where a modern entity is unavailable.
From drawing to CAM without entering the piece again
The model that forms the price delivers the real stones, the shop map and the nominal DXF geometry.