Docs · post processors

Layered DXF

Every cut part of a material as a layered DXF that any CAM package can read — geometry for your CAM to nest and toolpath, not a machine program.

Geometry for your CAM

Not a machine program: your CAM nests and toolpaths it, and your post writes the code. It audits clean in an independent DXF library.

File
.dxf
Controls
Any CAM that reads DXF
Machines
Vectric VCarve / Aspire · Fusion 360 · RhinoCAM · EnRoute · any CAM package

What the post writes

  • One DXF per material, every cut part in its own frame, laid out in rows for your CAM to nest. It is the parts, not the nested sheet.
  • From 1.0.0, a second export when you nest in WoodWright: Sheets ▸ DXF of sheets writes one layered DXF per nested sheet, every part where the nest put it, labeled with its part number.
  • Geometry separated onto layers by kind, so your CAM can assign a tool per layer rather than per part.
  • Part outlines carry the same coordinates the cut list and the labels do — one job, one set of numbers.

Where this program comes from

WoodWright has one toolpath planner. The Xilog generator plans the program, the simulator clears it, and every post below translates that cleared program op for op — never a second planner with a second set of rules. Whatever your machine reads is the same toolpath every other machine reads.

Every file this post writes is read back by the post’s own parser and compared to the source program move for move — same XY, same depth, same order, every bore accounted for. A translation that does not survive its own re-read is not a program, and is not offered.

Written from public format documentation only. No vendor post-processor was copied, decompiled or referenced.

Questions

Straight answers

Is the DXF export the safe route if my machine is not listed?
It is the route that keeps your own CAM in charge. Export the layered DXF and nest and toolpath the parts in the CAM you already trust and already know. You keep your own tooling, your own feeds and your own post — WoodWright supplies the part geometry, nothing else. Check the first part on scrap as you would any new job.
Why is DXF marked differently from the G-code posts?
Because DXF is geometry and G-code is machine motion. A DXF has done its job when it opens in your CAM with the parts drawn right, and these audit clean in an independent DXF library (ezdxf: zero errors); your CAM writes the motion. A G-code program only proves itself when a spindle follows it, and none of ours has yet been followed by one.

Other controllers: Generic ISO G-code · ShopBot OpenSBP · Homag / Weeke woodWOP · Biesse CIX · SCM Xilog