NC Optimization

How HiNC rewrites feed rates against the physical limits of a cut, and how to read a result that looks wrong. The optimizer is conservative by construction: it lowers feed until every tracked ratio sits under its ceiling, so an unexpectedly low value is usually a report of a real limit rather than a fault.

Ordered from the general rule to the case that most often prompts the question.

• NC Optimization Principles — The optimization objective, what limits each step, velocity smoothing, and the per-metric utilization factors that decide which peaks may be tolerated
• Corner Feedrate Behavior — Why the optimized feed at a corner falls below the empirically feasible value, and why that is the controller's own deceleration being reported back
• Machining Time Estimation — What the quoted cycle times are computed from, why they agree with controller simulators, and why the ratio is sounder than the absolute

See Also

• Milling Physics — the per-step criteria the optimizer holds under 100%
• Machine Capability — the spindle, controller and workstation ceilings the optimizer works against
• Scripting — the Opt* settings a script uses to drive the optimizer
• NC Dialects — the engine that reads the program before it is rewritten