1C7-0206

Access safety parameters

Enter machine parameter mode: Switch key to position 1, press MOD key, enter password if required. Navigate to safety parameters: enter MP7686 in the search field to access SS2_MAX_STOPPING_DIST for each axis

Modifying safety parameters requires proper authorization and may invalidate safety certification. Document all changes and coordinate with safety engineer.

Review safety event log

Press MOD key, select 'Functional Safety', then 'Safety Event Log'. Identify which axis (X, Y, Z, etc.) triggered alarm 1C7-0206 and note the actual stopping distance recorded

The event log shows timestamp, axis, and actual distance traveled during SS2. Compare this to MP7686.x to see the margin of violation.

Measure actual stopping distance

Use Test Run mode with reduced override. Trigger SS2 manually via safety input while monitoring with DataPilot (record axis actual position values). Repeat 3 times to establish consistent stopping distance with normal loads

Ensure safe machine environment with no workpiece or tooling that could be damaged during emergency stop testing.

Adjust MP7686.x if necessary

If measured stopping distances are consistently below the safety-required limit but exceed current MP7686.x setting, increase the parameter value appropriately. Add 20% safety margin to measured maximum distance. Requires safety validation and risk assessment documentation

Typical stopping distances: lightweight axes 10-50mm, heavy gantry axes 100-300mm. Consult machine safety documentation for validated values.

Check current SS2 deceleration setting

Access machine parameter MP7685.x (SS2_DECEL) for the affected axis. Value is in m/s² or mm/s². Compare to axis maximum deceleration capability shown in MP1410.x (MAX_DECEL)

SS2_DECEL should typically be 60-80% of MAX_DECEL to ensure reliable stopping while avoiding mechanical shock.

Verify drive deceleration capability

Check axis drive parameters in MOD > Drive Configuration. Verify current limit, motor thermal capacity, and brake resistor sizing support the required deceleration rate without drive faults

Increasing deceleration rate may expose mechanical weaknesses or cause drive overload. Test incrementally.

Increase SS2_DECEL incrementally

If current MP7685.x is significantly lower than MP1410.x MAX_DECEL, increase SS2_DECEL in 10% increments. Perform test stops after each change. Monitor for mechanical resonance or drive current limits

Use the Scope function (MOD > Scope) to monitor actual deceleration profile and verify it matches commanded SS2_DECEL value.

Validate stopping distance improvement

Repeat controlled SS2 tests and verify actual stopping distance now remains within MP7686.x limit with adequate margin. Update safety documentation with new validated parameters

Analyze SS2 trigger conditions

Review Safety Event Log (MOD > Functional Safety > Safety Event Log) to determine axis velocity at moment of SS2 activation. Check if alarm occurred during rapid traverse (G00) vs. feedrate moves

Event log shows commanded feedrate and actual velocity at SS2 trigger. Stopping distance scales with v².

Inspect safety input signals

Use PLC Diagnostics (MOD > PLC > Status > Inputs) to monitor safety-related inputs (door switches, light curtains, etc.). Check for intermittent signals or noise causing premature SS2 activation

Never bypass safety inputs. Only diagnose and repair faulty safety devices per safety regulations.