Docs · post processors

Homag / Weeke woodWOP

A 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

Built, simulated and verified against its own re-read — but no machine has cut one of these yet. Run it on scrap first.

File
.mpr
Controls
woodWOP
Machines
Weeke BHX · Weeke Vantage · Homag Centateq · Homag Venture · any Homag Group machine programmed through woodWOP

What the post writes

Conventions chosen, and why

Where the public description of this format left a token ambiguous, the conservative reading was taken — the one a mistake cannot bury a bit under. Each is written into the program's own header too, so it can be read on the machine before a scrap cut. Check these against your own setup sheet.

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

Which Homag and Weeke machines read this?
Every Homag Group machine programmed through woodWOP eats the same .mpr — Weeke BHX and Vantage, Homag Centateq and Venture among them. The file is line-oriented ASCII in millimetres, so it is also readable and editable by a person, which matters the first time you check one.
How are bores handled on a machine with a drilling head?
They are left to the machine. A bore becomes one vertical-drill macro carrying its position, depth and diameter, and the control picks the drill from its own bank — the same way the machine’s native programming does it. No pecking, no helix and no tool-library lookup on our side. If the bank does not hold that diameter the program stops in woodWOP, where you can see it, rather than in the spoilboard.
Why are arcs written as many short lines instead of arc elements?
Because the public description of the arc element leaves the sign of its direction token ambiguous, and an arc that curves the wrong way is scrap. Every arc is therefore tessellated to straight chords within 0.01 mm of the true curve — invisible in the part, slightly longer in the file. The day a shop confirms the direction and centre keys from a real woodWOP, this becomes one arc element per arc; the verifier already accepts that form.
Where do feeds and speeds come from?
From your woodWOP tool database, not from us. Tool numbers arrive as the job’s own for you to map, and the values the job intended are written into each macro’s comment line so you can see what was assumed — but they are never forced as keys over the database your machine already trusts.

Other controllers: Layered DXF · Generic ISO G-code · ShopBot OpenSBP · Biesse CIX · SCM Xilog