Biesse Rover post — bSolid and bWorks CIX

File: .cix
Controls: bSolid · bWorks
Machines: Biesse Rover · modern Biesse machining centres

What the post writes

A routed pass as ROUT with START_POINT, a run of LINE_EP elements, and ENDPATH.
A bore the tool library can drill as BG; a wider hole helix-routed; anything neither can make refuses rather than guessing.
MAINDATA kept to LPX, LPY, LPZ, ORLST and FCN, leaving the rest to the control’s own defaults.
Through paths carrying THR=1, with depth taken from the measured stock plus the breakthrough allowance.
Feeds carried on the ROUT itself — the run speed and the entry speed — because a LINE_EP has no feed word of its own.

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.

LINE_EP Z is read as INCREMENTAL from the previous point, negative going deeper, while X and Y stay absolute. This one is corroborated, and it is also the reading a mistake cannot bury a bit under: taken the other way, a tab lift would read as a lift above the panel — air, never the table.
Z zero is the top of the panel, because CIX is panel-relative and the panel thickness is the measured stock. There is no table-zero choice to make here.
ORLST="1" and CRN="1" are read as the front-left corner with the top face up. Confirm against your own setup sheet, which says which corner the sheet loads from.
Arcs are tessellated to LINE_EP chords within 0.025 mm of true, because the arc element’s direction word is not corroborated. That upgrades the day a Biesse shop sends one real .cix.

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 Biesse machines read a CIX file?

CIX is the ingest every modern Biesse speaks, through bSolid or bWorks, so a Rover is the machine most shops will be pointing this at. The program is written panel-relative, which is how CIX works natively — there is no table-zero decision to get wrong.

Which corner does the program assume the sheet loads from?

The front-left, top face up. That is the conservative reading of the origin and corner words, and it is the one thing on this page worth checking against your own setup sheet before the first program — your setup sheet states which corner the sheet loads from, and if it disagrees the whole program is mirrored.

Why are arcs broken into short straight moves?

Because the arc element’s direction word is not corroborated in the public format notes, and an arc that curves the wrong way is scrap. The chords stay within 0.025 mm of the true curve, which does not show in the part. The day a Biesse shop sends a real .cix that settles the direction, this becomes true arcs.

Has a Biesse actually run one of these?

No. It is planned, simulated, written, and then parsed back and compared to the source program move for move — but no Biesse has cut one. Verify on scrap first, and check the loading corner before you do.

Download Join the waitlist Measure a room All post processors

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