Files
OpenNest/docs/cincinnati-ci-fiber-post-output.md
T
ajandClaude Opus 5.5 5a627e5cc3 Merge branch 'claude/shared-post-contours'
Master added head-raise markers, common-line shared cuts and remainders to
the CI Fiber's own contour extractor, which this branch replaced with Core's
shared PostContours. Those now live in the shared model: PostContour carries
Raised, IsCommonLine and RemainderWinding, and Classify gives remainders the
perimeter macro on their perimeter's side and shared cuts no kerf side.
ContourWinding uses PortableMath for trig, as master's Core guard requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 19:10:16 -05:00

11 KiB

Cincinnati CI Fiber Post Output Reference

Project-written summary of OpenNest.Posts.CincinnatiCIFiber, not a vendor manual or a machine-operation guide. For the separate CL-series post, see Cincinnati output.

Controller reference used during development: Beckhoff TF5200 | TwinCAT 3 CNC Programming manual, version 1.33, May 19, 2026 (TF5200_programming_manual_en.pdf), and Cincinnati's CNC Codes Handbook (Programming Manual, rev 1.0, January 12, 2023) with LaserNST CI FIBER 8K sample programs, supplied by Cincinnati on October 19, 2026. Obtain the applicable documentation from Beckhoff and Cincinnati. Vendor PDFs and full-text extracts stay outside source control; redistribution permission has not been established.

Output contract

The current writer uses the Cincinnati machine-sample convention, not a generic TF5200 laser API:

  • Header: nest/configuration/material comments; V.E.MATERIAL, V.E.THICKNESS, V.E.X_SIZE, V.E.Y_SIZE, and V.E.UNIT. Sheet weight is omitted by default.
  • Startup: G90, L PROGRAMSTART.NC, then P3=V.E.R3, $GOTO NP3:, and N0:.
  • Parts follow plate order. V.E.R4 identifies the part within its sheet; numbered contour labels and V.E.R3 count up through the program for restart lookup (they restart at 1 in each per-sheet program).
  • Each contour: /L "L0", restart number, rapid to pierce, then /L "L2" for a hole or /L "L4" for the perimeter, G41 or G42, linear lead-in, /L "L6", cutting moves, and /L "ZHSOFF".
  • The perimeter is the part's contour with the largest bounding box, as ShapeProfile picks it; the others are holes. Compensation follows the Cincinnati CNC Codes Handbook (rev 1.0, G-codes): G41 leaves the product right of travel and G42 leaves it left. The post picks whichever puts the kerf in the scrap for the way each contour runs: imported drawings (perimeter CW, holes CCW) get G41 throughout, and a contour wound the other way gets G42. Cincinnati's LaserNST samples cut both perimeter and holes CCW, so they use G42 on the perimeter and G41 on holes, the same kerf sides. Paths that enclose no area count as holes with G41.
  • Tail: /L "L0", L PROGRAMEND.NC, the pallet-change code (M50), M30, and %.
  • Motion endpoints are sheet-absolute XY. Arc I/J are offsets from the arc start, matching the G162 convention; the post does not explicitly emit G162.
  • Parts and sheet cut-offs post in the plate's cut sequence (Plate.Parts order, as set by Set Sequence or a sequencer). A cut-off is not moved after the parts. Each segment is an open line with no lead-in: rapid to its start, /L "L4", /L "L6", the G1, and /L "ZHSOFF". No G41/G42 is selected, because the line is the beam centerline and has no inside or outside. Whether the L4 macro runs correctly without a following lead-in move has not been confirmed on the machine.
  • A head-locked cut-off overcut (see automatic cutoffs) writes the Head height lock block before the overcut's G1 and the Head height unlock block where the program unlocks: after the overcut, or, for a segment started at the far edge, after the rapid back and before the G1 toward the origin. Both blocks are blank by default, and a nest with a head-locked cut-off is refused while either is blank. Whether ZHSOFF and the next contour's L0 keep a locked head down for the rapid back is unconfirmed.
  • A rapid Plan Cutting marked to pass over parts already cut (see the cutting planner) writes the Head raise block just before its G0; a marked hole call raises before its hole's first G0. The block is blank by default, and a nest with a marked rapid is refused while it is blank. Which block raises the head on the CI Fiber (whether L "L0" without block delete does) is unconfirmed; enter and verify it on the machine.
  • Common lines cut once: see common lines below.
  • Contour geometry comes from Core's shared PostContours (OpenNest.CNC.Posting): hole subprograms and incremental programs are flattened to sheet coordinates, and it picks the perimeter (never a scribe mark) and each contour's kerf side (common-line shared cuts and remainders as described below). Suppressed moves are omitted; a cut that resumes after them starts a new contour pierced where they end, which this post refuses without a lead-in rather than cutting a chord across the gap. By default, wholly scribe contours are omitted.
  • Files use UTF-8 without a BOM and CRLF lines. Default accuracy is three decimal places: coordinates trim trailing zeros; dimensional header values retain them.

Common lines

A common line cut once posts in plate order, member by member, each member's holes first:

  • Owner's outside: the part that cuts a common line starts its outside on it. With no span cut before it, it is a normal closed perimeter (G41/G42 from its travel), whose straight lead-in runs up the shared edge's axis, so the common line is its first cut.
  • Remainder (an open contour after a COMMON LINE REMAINDER comment): the normal contour form with the perimeter macro, /L "L4", G41 for a clockwise perimeter or G42 for a counterclockwise one (the side its whole perimeter would get), the straight lead-in, /L "L6", the open path and /L "ZHSOFF". A member's closed contours are then all holes; the post picks no perimeter among them. An owner whose outside stops in an earlier member's kerf writes each of its pieces this way.
  • Shared cut (CommonLine motions, programs planned before the owner cut its own edge): the cut-off form with a real lead-in, no G41/G42.

Unconfirmed on the machine (release gate, see common-line cutting):

  • compensation start-up on a remainder whose lead-in starts in void (the kerf the owner's cut opened) and runs along it, and on the owner's lead-in collinear with its shared edge;
  • compensation cancel where a remainder ends in that kerf, and that the next contour starts uncompensated, since the post writes no G40 (the macros cancel compensation);
  • whether L4 runs correctly before an older program's uncompensated shared cut, as for cut-offs.

Verify on a 3/16 stainless coupon pair on the CI FIBER 4020 and record the result here.

Configuration and boundaries

See CIFiberPostConfig for macro names, material mappings, unit codes, precision, and table limits. The post is named for the machine family; table size belongs in configuration. In the desktop app these settings open in a sectioned editor (Machine, Sheets, Material, Program output, Macros) with a material-code table; values are validated and saved only when OK is pressed.

Steel is "Carbon Steel" in OpenNest, as in the Cincinnati post's cut libraries. The material-code table maps both "Carbon Steel" and "Mild Steel" to MSN. A deployed config is copied from the shipped JSON only when a PC has none, so an existing PC needs the "Carbon Steel" row added in the material-code table. Until then such nests still post MSN through DefaultMaterialCode.

  • Assign linear lead-ins before posting, including circular holes. The writer rejects missing or arc-first lead-ins. Its conservative rule cites the G238 compensation-selection restriction in TF5200 §13.2.4.1; do not generalize it to every controller compensation mode.
  • /L calls are skippable; L PROGRAMSTART.NC and L PROGRAMEND.NC are not. Macro bodies, process settings, restart handling, and compensation cancellation belong to the machine configuration. The post does not emit an explicit G40.
  • InchUnitCode defaults to 1; MetricUnitCode defaults to 0 but remains unconfirmed. Table limits compare directly with nest dimensions, without unit conversion. Do not assume changing the unit code establishes metric support.
  • Plates without parts are not posted. With One program per sheet (the default) and more than one sheet, JOB.cnc is written as JOB-1.cnc, JOB-2.cnc, ..., each a complete program with its own sheet size and pallet change. This follows the CL-series batch rule (EM-423 §7.4: one sheet per program; the operator sets repeats). A single-sheet nest keeps the chosen name. Plate quantity is not written; repeat the program at the machine.
  • With the option off, every sheet goes into one program: /L "L0" and the pallet change separate sheets, and the header carries the first sheet's size. Sheets of different sizes are rejected in this mode. Posting to a stream always produces one program, so it rejects a multi-sheet nest in per-sheet mode.
  • PalletChangeCode defaults to M50, as in the machine sample, which ends L PROGRAMEND.NC, M50, M30. Cincinnati's CNC Codes Handbook calls M50 "Table In" and M51 "Table Out". On the CI Fiber the head stays at a fixed height and the pallets shuffle and lift to swap. Table In moves the waiting pallet into the laser, which sends the cut pallet out for unloading, so M50 is the swap (reading confirmed by the machine owner). It expects the waiting pallet to be loaded. Newer Cincinnati samples end with M30 and no pallet code; clear the setting to match.
  • Release blocker: the single-program sequence between sheets (/L "L0", then M50, then the next sheet with no new header or start macro) is inferred, not observed. Confirm it against a Cincinnati multi-sheet sample before release, or keep One program per sheet on, which matches the single-sheet sample.
  • All programs are generated and every sheet is validated before any file is written, so a failed file post writes nothing. A failed stream post may leave partial output; discard it. Successful generation and tests do not establish that a program is safe to run on a particular machine.

Verification

Output-contract tests cover a square with a hole, kerf side for either winding, coordinate transforms/formatting, lead-in rejection, cut-off sequencing and output, table bounds, suppression/scribe handling, and multi-sheet output in both modes. Common-line post tests hold a golden program for a planned two-part pair (the owner's perimeter starting on the common line, and the partner's remainder), the remainders' compensation side for either winding, and the refusals of posts without support. Sample regression tests post a nest rebuilt from a Cincinnati machine sample, whose parts carry the sample's own pierce, lead-in and cut moves. Posted unchanged, the program body must match the sample line for line (macro, G41/G42 side, lead-ins and cuts). The fixture stays outside the repository and the tests skip when test-config.json does not point at it. Run:

dotnet test OpenNest.Tests/OpenNest.Tests.csproj --filter FullyQualifiedName~CincinnatiCIFiber

Keep this summary aligned with the implementation and tests. Cite the relevant manual section for controller rules and distinguish those rules from Cincinnati-specific macros and behavior observed in a machine sample.