Namespace Hi.MachiningSteps
Classes
- MachineMotionStep
MachiningStep has spindle information. Note that the spindle information is only for milling behavior.
- MachiningStep
Represents a machining step enriched with physics, mapping and source metadata. The duration-based step property is based on the duration from previous-step to current-step.
- MachiningStep.CollidedKeyPair
A pair of collided keys that indicates two entities are in collision.
- MachiningStepUtil
Utility class for milling step related constants and helper methods.
- PresentAccess
Provides a value accessor bound with its PresentAttribute metadata.
- PresentAttribute
Attribute for presenting property information with localization support.
- PropertyAccess<TData>
Provides access to properties of a milling step with presentation information.
- StepActualTime
Wall-clock stamp of a machining step end — the controller-recorded timeline, as opposed to the simulated machine timeline (EndTimecode). Grouped into one optional sub-object so scenes that never map measured data (pure NC simulation, collision check, optimization) carry a single null reference per step. A CSV play stamps only the first step built after each row/idle boundary with the controller instant; the steps in between receive values extrapolated from the latest stamp along the machine timeline and are marked IsInterpolated.
Interfaces
- IFlagText
temperary design for showing flag text.
- IMachiningService
Represents a host interface for milling steps that provides access to milling equipment and related resources.
- IMotionStepIndex
Abstraction for an object that carries a StepIndex — the 0-based ordinal of a machining motion step in execution order. Used as a cross-object alignment key so a step (MachiningStep), its cutter-location position (
ClStripPos), and the messages anchored to it (StepDiagnostic,StepScopedProgress) can be matched by the same ordinal without depending on a concrete type.Distinct from ISentenceIndexed: that ordinal counts NC source blocks, whereas this one counts produced motion steps — a single source block (e.g. a canned cycle) can fan out into several steps.
- IStepPropertyAccessHost
Narrow host contract for accessing the step-variable registry and registering new step variables. Exposed as a dedicated surface so pipelines that only need step-variable wiring (e.g. CsvRowSyntax) do not have to depend on the broader IMachiningService.