OpenNest

aj/OpenNest

0 Fork 0

mirror of https://github.com/ajisaacs/OpenNest.git synced 2026-10-27 16:11:07 -04:00

Files

T

History

ajandClaude Opus 5.5 993555dba6 feat(cutoffs): head-locked overcut at the far edge, reversible by Plan Cutting

Stock can arrive up to 1.5 in wider than nominal, so only the origin-side
edge is certain. A cut-off with a head-locked overcut cuts past the nominal
far edge with the head height locked, covering the oversize. With that lock,
Plan Cutting may start the far-edge segment at the far edge: overcut outward,
rapid back still locked, unlock, cut toward the origin. Without it the
direction stays fixed, as decided in Project Memory a20ea455.

- CutOff.HeadLockOvercut / FarEdgeFirst, persisted in .nest; HEAD HEIGHT
  LOCK/UNLOCK comment markers; far edge is quadrant-aware.
- Planner offers the reversed far-edge segment in the joint search, the
  safest route and segment insertion; Apply records the direction.
- Cincinnati CL and CI Fiber posts gain lock/unlock code settings and refuse
  head-locked cut-offs while either is empty.
- Automatic cut-off dialog setting (off by default, 1.5 in), kept between
  sessions and used for new cut-offs.

Lock codes and machine behaviour with the head locked are unconfirmed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-23 09:51:59 -04:00

CincinnatiFeatureWriter.cs

feat(cutoffs): head-locked overcut at the far edge, reversible by Plan Cutting

2026-10-23 09:51:59 -04:00

CincinnatiHeadRaise.cs

feat(posts): trigger the Cincinnati safety head raise by rapid length

2026-10-20 07:08:10 -04:00

CincinnatiHoleCallWriter.cs

feat(posts): trigger the Cincinnati safety head raise by rapid length

2026-10-20 07:08:10 -04:00

CincinnatiPartSubprogramWriter.cs

fix(posts): never post a display perimeter