75275

Access Diagnostics > Axis > Position in SINUMERIK HMI to verify current axis positions and compare against MD32100/MD32101 limit values for the affected axis in channel %1.

Do not bypass limits without engineering review; limits protect machine mechanics and tooling.

Review the NC block %2 geometry in the part program. Calculate expected end position and verify it falls within MD32100 (upper) and MD32101 (lower) bounds.

If limits are incorrect, modify MD32100/MD32101 in NCK > Parameters > Machine Data menu. If part program coordinates are wrong, correct the G-code block geometry.

Recompile and download machine data after parameter changes; power cycle may be required.

Verify hard limit switches (if equipped) are mechanically within the software limit range. Check IO signals for limit switch activation in Diagnostics > Inputs/Outputs.

Verify machine kinematics configuration in NCK > Parameters > Machine Data. Check MD20050 (kinematic model type), MD20060 (DH parameters), and axis-specific geometry parameters (MD32010-MD32015).

Incorrect kinematic parameters cause systematic reachability failures across multiple blocks.

Simulate the NC program offline using SINUMERIK Operate or NCSimul to identify which block(s) and axis combinations trigger the alarm. Review tool offset (MD30140) and workpiece offset to confirm they do not push the path outside workspace.

For 5-axis machines, check MD34100 (axis coupling type) and MD34110 (coupling offset); verify orientation angles in block %2 do not force gimbal lock or singular configuration.

Some tool orientations near singularities may require path smoothing or orientation interpolation mode change (G16.1 vs. G16.2).

Consult machine builder's workspace diagram and confirm target coordinates in block %2 lie within documented reachable region, accounting for tool length and spindle geometry.

Review feed rate in block %2 and compare against MD32130 (max. feedrate) and MD32140 (max. acceleration) for affected axes. Reduce block feedrate or increase acceleration limit if within machine capability.

Increasing acceleration limits without servo tuning can cause oscillation or following error alarms.

Check interpolation mode: verify G-code block uses appropriate interpolation (G01 linear, G02/G03 circular, NURBS). For coupled axes, ensure MD34100 coupling mode is compatible with commanded path geometry.

Access Diagnostics > Servo > Axis tuning to confirm servo loop bandwidth (closed-loop gain MD36010, time constants MD36020) are tuned for the load and axis mass. Verify no servo error flags precede this alarm.

If alarm persists, reduce feedrate by 50% in the NC program or increase MD32110 (jerk limit) and MD32140 (acceleration). Re-run the block and monitor Trace data to confirm smooth interpolation.