Skip to content

Next Gen STEP AP242 Native-ish BREP Geometric Modeling Kernel

9.8 KB
Raw Blame

Formed Wire

Use WireForm when the design intent is a formed length of constant-section wire or rod. Authors specify the forming sequence; Aetheris derives the exact tangent centerline and materializes it with the circular Sweep kernel.

WireForm BentWire {
    Diameter: 1mm
    Material: Standard.Materials.StainlessSteel.304_Annealed
    StartFrame { Origin: [0mm, 0mm, 0mm]; Tangent: [1, 0, 0]; Up: [0, 0, 1] }
    Straight Lead { Length: 20mm }
    Bend Corner { Radius: 5mm; Angle: 90deg; Plane: Up }
    Straight Tail { Length: 30mm }
}

Fields accept the canonical camelCase spelling (diameter, material, radius, turns, pitch) and their established PascalCase aliases. Names and domain symbols retain their authored case.

Diameter and Material define the stock. Direct WireForm authoring uses the catalog identity; a typed product policy may carry that identity through a String field. StartFrame supplies an origin, initial tangent, and perpendicular Up reference. A Straight advances along the current tangent and preserves the frame. A signed Bend rotates the tangent by Angle around either the current local Up or Right axis. Here Plane names the current local plane normal/rotation axis: Plane: Up bends in the tangent/right plane, while Plane: Right bends in the tangent/up plane. The frame is transported by the same rigid rotation, avoiding arbitrary spin. Start-frame transformations therefore carry the forming program without global-coordinate bend hacks.

Radius is always the centerline bend radius. Wire forming applies a geometric-only minimum-radius rule: Radius > Diameter / 2. It does not invent material forming tables. Positive angles follow the right-hand rule about the selected local plane normal; negative angles reverse that normal. X0 admits nonzero angles through ±180°.

Each operation consumes a WireState (position, tangent, local frame, and accumulated length) and produces the next state. Changing an operation intentionally moves every downstream operation. The compiler retains operation identity and exposes the operation-to-line/arc-to-cylinder/torus correspondence through structured inspection.

The ideal cut-stock length is derived exactly:

  • Straight: Length
  • Bend: Radius × abs(AngleRadians)
  • Total: the sum of all operation lengths

Circular area times total length gives volume; density from the Material DB gives mass. These are idealized centerline quantities. It does not model springback, plastic stretch, forming allowance corrections, or manufacturing process simulation.

The centerline lowers to explicit line and circular-arc AIR, then to exact circular Sweep geometry. Straights become cylinders, bends become toroidal patches, and open terminals become planar caps. Canonical WireForms have no rational B-spline surfaces and no faceted fallback. Both terminals retain position, tangent/frame, and section diameter.

STEP export retains these analytic surfaces and circular edge bases. Face boundaries follow their outward normals, so a downstream CAD reader receives the intended bend side without needing to repair the wire's winding. When STEP edges lack surface-parameter trims, import derives exact linear trims for cylinder generators and rings, and torus major and minor circles. Straight/Bend wire forms do not need fitted B-spline trim curves; seam boundaries retain their full angular spans. Existing source trim curves are preserved rather than rewritten.

Winding generators extend wire forming without weakening the exact Straight/Bend route. Helix authors a cylindrical helix from Radius, Turns, either Pitch or Height, explicit Handedness, and an optional stable StartPhase. If both Pitch and Height are supplied they must agree with Height = Turns × Pitch. The compiler derives the missing value, exact helix length, terminal position/tangent/transported frame, turn clearance, volume, and mass. AxisCoil remains accepted as a compatibility spelling and lowers to the same semantic operation. The axis is derived from the current wire state rather than specified as an independent field.

Helix Winding {
    Radius: 12mm
    Turns: 8
    Pitch: 5mm
    Handedness: RightHanded
    StartPhase: 0deg
}

SurfaceCoil has an evaluable centerline law for analytic Cylinder, Frustum/Cone, and Sphere supports. This is currently internal centerline qualification, not an admitted multi-body Model recipe. Declaring support solids alongside a WireForm fails normal validate/build admission; the compiler does not silently discard those solids. An explicit nonmaterial support binding is still needed. The preserved regression witnesses record the boundary. Cylinder/frustum winding uses AxialPitch. Sphere winding uses linear-latitude progression between StartLatitude and EndLatitude, without equal-geodesic-spacing claims and excluding the exact poles.

Internal centerline fragment — this is not a complete buildable Model:

Frustum CupInnerFrustum { BottomRadius: 18mm; TopRadius: 30mm; Height: 60mm }
SurfaceCoil Winding {
    Surface: CupInnerFrustum
    Side: Inside
    Clearance: 1mm
    Turns: 6
    AxialPitch: 8mm
    Handedness: RightHanded
}

Clearance is support-to-wire clearance; the compiler uses Diameter / 2 + Clearance as centerline offset. CenterlineOffset is the mutually exclusive mathematical alternative. Collapsing inward offsets, pole singularities, turn overlap, and unsupported surfaces fail with typed diagnostics. CLI inspection reports the winding kind/law, handedness, resolved pitch/height, exact or deterministically integrated stock length, start/end terminals, self/support clearance, and polynomial realization evidence.

The semantic/evaluable winding law remains authoritative. Coil-containing forms lower through deterministic rotation-minimal frame transport to cubic non-rational B-spline tube patches and planar caps; STEP uses no rational product surfaces and no faceted fallback. Coil-free forms still use exact cylinders and tori. The current approximation uses 32 longitudinal cubic spans per turn and four cubic polynomial quarter patches around the circular section; the compiler measures maximum/RMS centerline error against the winding law and fails if its 0.01 mm bound is exceeded.

Coils remain continuous, unbranched, open paths. A distinct closed Knot operation for named mathematical knot families; it does not turn coils into closed paths or force Straight/Bend through spline approximation. See Mathematical Knots. Arbitrary/freeform supports, variable pitch or section, intentional contact, spring mechanics, contact dynamics, and branching remain unsupported. Surface support identity is authored rather than imported-face-ID based. Direct Concept Path plus Sweep remains the lower-level choice for explicitly authored line/arc trajectories.

See the canonical Helix, AxisCoil compatibility fixture, composed Straight/Coil/Straight, 90-degree bend, and Paperclip.

aetheris inspect source.firmament --json reports the semantic wireForm object, including operations, totalStraightLength, totalBendLength, and compiler-derived totalWireLength. A materializing build --json adds volume, mass, surface inventory, manifold/reimport status, rational/faceted counts, and the STEP hash.

The single-cut guitar witness reuses this exact Straight/Bend route for six thin strings. Each speaking length and tuner lead meets through a 3 mm centerline-radius bend at the nut. This is geometric routing, without string tension, vibration, wound-wire microgeometry, or tuner mechanics. Adjacent-operation clearance samples straight and curved operations on the same arclength interval count before excluding the intended tangent-join neighborhood.

Mating a coil to a rod

A Helix starts at the current wire point and preserves its tangent. Its winding axis is generally offset from that point and tilted from StartFrame.Up: pitch contributes an axial component to the tangent. Do not mate the part origin or assume local Z is the spring axis.

Executable Assembly template occurrences expose each Helix operation by its authored name. For Helix Winding, the public semantic members are Winding.Axis, Winding.Frame and Winding.ClearDiameter. They come from the same compiler-derived axis origin, direction, start radial and wire radius that build the coil. The frame's Z axis is the winding axis, X is its start radial, and its origin is the winding-axis base. Clear diameter is twice the coil centerline radius minus wire diameter. The build report retains these values as wireForm.operations[].axisDatum.

A bounded spring-to-rod interface can combine axial alignment with a seating frame:

Interface SpringOnRod {
    Role Spring requires AxisCapable, DatumFrameCapable, DimensionalCapable;
    Role Rod requires AxisCapable, DatumFrameCapable, DimensionalCapable;
    Lower AxisCoincident Spring.Axis Rod.Axis;
    Lower FrameCoincident Spring.Frame Rod.Frame SameDirection;
    Fit Rod.Diameter inside Spring.ClearDiameter;
}

The datum frame fixes axial seat position and roll; the explicit axis constraint independently validates coaxiality after materialization. Fit analysis classifies diameter compatibility. See the executable coil-on-stem fixture. This automatic datum exposure covers Helix and its AxisCoil compatibility spelling; it does not infer an axis for knots or arbitrary SurfaceCoil supports.