27010

Check current SLS velocity settings

Navigate to Diagnostics > Safety Integrated > SLS Monitor to view current velocity limits and actual axis speeds when alarm occurred.

Compare the logged velocity at alarm time with the SLS limit - often the difference is minimal indicating a borderline condition

Review machine data parameters

Check MD36600 (SLS_VEL_LIMIT) for each affected axis to verify the configured maximum velocity matches machine capabilities and program requirements.

Modifying safety parameters requires proper authorization and may need safety validation

Verify feedrate override settings

Ensure feedrate override is not set above 100% when SLS limits are active, as this can cause programmed speeds to exceed safety limits.

SLS monitoring is active even during override conditions, unlike some other safety functions

Test with reduced rapid traverse rate

Temporarily reduce G00 rapid traverse rate in machine data MD32000 (MAX_AX_VELO) to confirm if velocity limiting resolves the alarm.

This is a diagnostic step - don't leave production speeds permanently reduced

Check SLS position monitoring status

Access Diagnostics > Safety Integrated > Position Monitoring to view current axis positions relative to configured SLS monitoring windows.

Position violations often occur at the exact moment of coordinate system changes (G54, G55, etc.)

Verify work coordinate system setup

Review active work offset values in Settings > Work Offsets and ensure they don't place the workpiece outside SLS monitoring boundaries.

Incorrect work offsets can cause crashes - verify setup before running programs

Review SLS monitoring window parameters

Check MD36610 (SLS_POS_LIMIT_PLUS) and MD36620 (SLS_POS_LIMIT_MINUS) to ensure monitoring windows are appropriate for current job requirements.

SLS position limits are often set conservatively - verify they allow full range of intended machining operations

Test program simulation

Run the part program in simulation mode to identify exactly where position limits are exceeded before attempting actual machining.

Use the program path display to visualize tool movement relative to SLS boundaries

Review active safety functions

Navigate to Commissioning > Safety Integrated > Function Overview to see which SLS functions are currently active and their trigger conditions.

Multiple SLS functions can be active simultaneously - check all active functions, not just the first one listed

Verify SLS activation conditions

Check MD36630 (SLS_ACTIVATION_MODE) to ensure SLS is only active when required and not interfering with normal machining operations.

Changing safety activation modes requires proper safety assessment and documentation

Compare with machine manufacturer specifications

Cross-reference current SLS parameter settings with machine builder's original safety configuration documentation to identify deviations.

Keep a backup copy of original safety parameters - they're often needed for reference during troubleshooting

Test SLS function disable/enable

If operationally safe, temporarily disable the triggering SLS function to confirm it's the source of the alarm, then re-enable and adjust parameters accordingly.

Only disable safety functions if alternative safety measures are in place and proper authorization is obtained

Check encoder signal quality

Access Diagnostics > Drive > Encoder Signals to verify clean position feedback signals without noise or dropouts that could affect SLS calculations.

SLS monitoring is very sensitive to encoder signal quality - even minor signal issues can cause false alarms

Verify drive communication status

Check Diagnostics > Drive > Communication Status for any PROFIBUS/PROFINET communication errors between NCU and drive modules.

Communication issues can cause delayed or incorrect position reporting to safety functions

Review actual position vs. commanded position

Monitor the following error display in Diagnostics > Axis > Position Control to identify any excessive deviation that might trigger SLS monitoring.

Large following errors can cause SLS to trigger even when commanded positions are within limits