Enum RadiusOffsetBasis

Namespace

Hi.NcParsers.Dependencys.Generic

Assembly

HiMech.dll

Which cutter-radius compensation strategy the NC program was posted for — decides what a tool-house refresh writes into the radius (D) column of a tool offset table. The height (H) column is refreshed the same way under both strategies. This is an output-affecting, project-level choice: the user or agent picks it after confirming how the NC program was posted, because a refresh under the wrong basis silently offsets the tool by a full cutter radius.

public enum RadiusOffsetBasis

Extension Methods

InvokeUtil.SelfInvoke<TSrc>(TSrc, Action<TSrc>)

InvokeUtil.SelfInvoke<TSrc, TDst>(TSrc, Func<TSrc, TDst>)

MaskUtil.GetMaskedValue<T>(T, T, bool)

MaskUtil.SetMask<T>(ref T, T, bool)

ColorUtil.GetGloomyColor(object, double, double)

NameUtil.GetSelectionName(object)

StringUtil.GetPropertyStringIfToStringNotOverloaded(object, bool, bool)

LockUtil.Lock(object)

Fields

CutterRadius = 0

Cutter-radius: the NC contour is the part contour, and the controller offsets it by the D row at run time. The D row holds the cutter's geometry radius plus wear, so a tool-house refresh writes the cutter profile's max radius into the ideal radius and leaves the radial wear untouched. This is the default and the only behaviour before the basis existed.

ZeroBased = 1

Zero-based: the NC path is already the tool-centre path (CAM applied the offset), while G41/G42 D.. stays in the program so the operator can dial in wear. The D row therefore holds the wear only, and a tool-house refresh writes 0 into the ideal radius and leaves the radial wear untouched. Refreshing such a program under CutterRadius would push the tool a full cutter radius into the wall.