75070

Navigate to Siemens HMI > Diagnosis > Machine Data > search for MD 36010 and MD 36020 for the affected axis %2. Verify min limit < max limit with realistic physical boundaries.

Do not set soft limits beyond actual machine travel without geometry verification

If MDs are empty or zero, enter physically measured axis travel limits. Example: X-axis with 500mm travel should have MD 36010 = 0 and MD 36020 = 500 (in mm or inches per MD 20050).

Cross-reference with MD 32000 (axis type) to confirm the axis is defined as linear (1) or rotary (0) - collision protection requires correct axis classification.

Access Siemens HMI > Diagnosis > Machine Data > MD 37000 (Coll. protect. monitoring active). Verify it is set to 1 (enabled) for axis %2. If 0, change to 1 and reload machine data via Startup > Initialize.

Enabling collision protection without proper soft limits (MD 36010/36020) will cause immediate 75070 recurrence

Check MD 37010 (warning distance). Value must be positive and less than the distance between soft limit and current position. Typical range: 10-50mm for linear axes.

Verify MD 37020 (monitoring window for protective stop) is set appropriately - should match or exceed the warning distance to allow controlled deceleration.

Navigate to Siemens HMI > Diagnosis > Machine Data > Axis > select axis %2 > verify MD 20050 matches the channel %1 unit system (0=metric, 1=inch). Inconsistency causes parameter interpretation errors.

Confirm axis %2 is explicitly assigned to channel %1 in the NCK channel configuration (typically MD 10000-10100 range). Verify the axis appears in the active axis list for the channel.

Some axes may be defined in machine data but not linked to any channel - this will trigger 75070

After correcting channel-axis assignment or unit inconsistencies, perform a full machine data reload: Startup > Initialize > select 'Reload all machine data' and confirm NCK restart completes without errors.