Homag machines run on woodWOP, the company’s workshop programming system, and the files it produces are MPRs: parametric descriptions of a panel and the operations on it. People search woodWOP to G-code for one of two reasons, moving a job to a non-Homag machine, or understanding what the format relationship even is, and both answers start from the same fact: an MPR is not G-code wearing a different extension.
What is an MPR file, and why is it not G-code?
woodWOP stores jobs the way a craftsman thinks about panels: a workpiece with dimensions, then operations, drill patterns, grooves, routed contours, placed on it, with variables tying everything together so a width change reflows the whole job. That is a part description. A G-code program is a motion description: this axis, this far, this fast, in the standard vocabulary. The Homag control bridges the two at runtime, planning motion from the description for its own machine, which is precisely the work a converter would have to replicate for somebody else’s machine.
So what actually works for moving a job?
The CAM route, in three honest steps:
| Step | What happens | Why it is needed |
|---|---|---|
| 1. Extract geometry | Part outline and features out of the design | The transferable core is the geometry |
| 2. CAM toolpaths | Operations rebuilt for the target machine | Tooling and capabilities differ |
| 3. Post for target | G-code in the target’s dialect | Every control has its accent |
Third-party utilities float around the wood industry claiming pieces of this chain, and the reliable pattern stays the same: geometry travels, toolpaths get rebuilt, and the posted code is target-specific. Budgeting an hour of CAM work per traveling job beats budgeting a week for a converter that almost works.
Why does this mirror every vendor ecosystem?
Because the trade-off is structural, not a Homag quirk. Parametric workshop systems buy enormous daily speed inside their ecosystem, and the price is that nothing they store runs anywhere else, the same shape as Biesse’s bSolid world next door and the conversational controls of the metal side. Mixed floors feel it most: a shop with a Homag cell, a standard router with an automatic tool changer, and an aging machining center is running three program worlds, and the people who move jobs between them are the ones fluent in the one layer all three share.
A concrete version: a panel shop won a contract requiring overflow production at a partner with non-Homag equipment. The MPRs stayed home; an afternoon in CAM rebuilt the six traveling jobs from exported geometry, and the shop’s woodWOP specialist, who had drilled standard code on the side, did the posting and prove-out herself. The contract renewed; the converter search did not.
What should a woodWOP operator actually learn?
The everyday universal layer, not a programmer’s depth: motion codes, units and positioning, offsets, and the machine-function families, including the wood-flavored ones where the coolant outputs run dust extraction, the list in the wood router M-codes. That is enough to read what a non-Homag machine is doing, follow a diagnostic conversation, and prove out a posted job, the three situations where the ecosystem boundary actually bites. It is recall-sized, and it stacks on top of machining judgment woodWOP already built.
Bottom line
woodWOP MPRs describe parts; G-code describes motion; nothing converts one to the other cleanly because the conversion is CAM’s whole job. Move jobs by exporting geometry, rebuilding toolpaths, and posting per target, and build the universal code layer alongside the parametric skill, a spare-minutes habit on the G-code practice hub. The ecosystem speed stays; the portability gets added.
Sources
Frequently asked questions
Can you convert woodWOP MPR files to G-code?
Not cleanly: MPRs are parametric part descriptions while G-code states motion, and bridging them is CAM’s job. Export the geometry, rebuild toolpaths, and post for the target machine.
What is woodWOP, exactly?
Homag’s workshop programming system: workpieces and operations defined parametrically, stored as MPR files the Homag control executes, with variables reflowing the job when dimensions change.
Why would a woodWOP shop need G-code at all?
Mixed floors, diagnostics below the graphical layer, and jobs that travel outside the ecosystem. The parametric skill stays home; the standard layer travels.
What is the best way to learn G-code coming from woodWOP?
As vocabulary on top of existing machining judgment. A free app like G-Code Sprint drills the everyday codes and repeats whichever ones you miss, in spare minutes alongside production.
G-Code Sprint is a study and practice tool only. Always follow your instructor, employer, machine manual, and shop safety procedures.