Documentation

What actually lands on your machine.

One page per controller: the tokens the post emits, the conventions it chose where a public format description was ambiguous, and whether anyone has cut one yet. Written for the person setting the machine up.

Post processors

Six outputs, one toolpath

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.

.dxfLayered DXFThe nested sheet as a layered DXF that any CAM package can read — the one output here that is proven rather than pending.ProvenISO / RS-274Generic ISO G-codeThe generic ISO / RS-274 post for the routers most small shops actually own — Mach3 and Mach4, GRBL 1.1, LinuxCNC and Masso.Awaiting a first cut.sbpShopBot OpenSBPAn OpenSBP .sbp part file for every ShopBot — PRS, Buddy, Desktop, SB3 and FabMo all read the same flat subset.Awaiting a first cut.mprHomag / Weeke woodWOPA woodWOP .mpr program for the Homag Group machines — Weeke BHX and Vantage, Homag Centateq and Venture — with bores left to the machine’s own drilling head.Awaiting a first cut.cixBiesse CIXA CIX program for Biesse Rover machines through bSolid or bWorks — the one ingest every modern Biesse speaks.Awaiting a first cut.xxlSCM XilogThe Xilog .xxl program — and the native lane the other five posts are translated from, which is why this page is worth reading even if you do not own an SCM.Awaiting a first cut
How a program is checked

Every file is read back before it is offered

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.

That is a real gate and it is not the same thing as a first cut. Five of the six outputs below have never been run on a machine — they are marked awaiting a first cut here and at the top of their own pages. Run the first program on scrap and check it against the drawing.

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

Questions

Straight answers

What is in the WoodWright documentation?
One page per CNC post processor, covering what the post emits, which controls and machines read it, the conventions chosen where a public format description was ambiguous, and whether it has been cut on a real machine yet. It is reference material for the person setting the machine up, not a marketing overview.
Do I need a post processor to use WoodWright?
No. The design, cut lists, sheet nesting, labels and shop drawings all work with no machine attached, and the layered DXF export drives any CAM package you already own. The posts exist so that a shop with a supported control can go from the design to the machine without a CAM step in between.
Which outputs have actually been cut on a machine?
The layered DXF has — shops open it in their own CAM and run it. None of the five G-code posts has been cut on iron yet. Each one is planned, simulated, emitted and then parsed back and compared to the source program move for move, but that is verification, not a first cut, and every post page says so at the top rather than in a footnote.
Were any vendor post processors copied to build these?
No. Every post is written from public format documentation only — no vendor post file was copied, decompiled or referenced. Where the public description left a token ambiguous, the conservative reading was taken, and that reading is written on the page and into the program header so the shop can see the assumption before a scrap cut.
DownloadJoin the waitlistMeasure a roomThe CNC overview

Related: CNC output · the file format · post processor packs · sheet nesting · cut lists