Docs · post processors

Layered DXF

The nested sheet as a layered DXF that any CAM package can read — the one output here that is proven rather than pending.

Proven

Shops have used this output on real jobs.

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

What the post writes

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?
Yes, and it is the one output on this page that is proven rather than pending. Nest the sheet in WoodWright, export the layered DXF, and drive it with the CAM you already trust and already know. You keep your own tooling, your own feeds and your own post — WoodWright supplies the geometry and the nesting, nothing else.
Why is DXF marked stable when every G-code post is not?
Because DXF is geometry and G-code is machine motion. A DXF that opens in your CAM with the parts in the right place has done its whole job, and shops have opened these. 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