Reducing The Number Of Alarms - Siemens Sinumerik 840D sl Function Manual

Diagnostics

10.5 Reducing the number of alarms

Note
The alarm reduction is only made in the SPL commissioning mode (MD
$MN_PREVENT_SYNACT_LOCK[0,1] = 0). Outside this mode, when changing
the parameter assignment, the corresponding individual axis--specific alarms
27032, 27035 and 27060 are always output.
Acceptance test alarms of the drive are not included in the alarm reduction. The
reason for this is that a parameterization change, which results in acceptance test
alarms, can be performed independently of one another in the two monitoring
channels.
It does not make sense to reduce the global acceptance test alarms
(27070--27073). The reason for this is that these alarms, which refer to a
checksum error in the SPL parameterization, PROFIsafe configuration or I/O
coupling (peripherals), is only output if the axis--specific monitoring functions have
been enabled.
Boundary condition
The MD is not incorporated in the axis--specific safety MD checksum. This means
that the function can be enabled/disabled at any time by changing the MD. In the
acceptance test, the alarm suppression should be internally deactivated so that the
two--channel fault/error detection can be checked. It can then be subsequently
activated in order to reduce the number of alarms that end users have to cope
with.
10.5.2 Assigning priorities to alarms
Especially for machines with an extremely high number of axes, the previously
described alarm suppression function is not adequate in order to obtain a display of
the real fault/error codes.
Just one single defective input signal can cause alarm 27001 (or 27101 to 27107)
to occur for many axes if this input signal has been configured as SGE on several
axes. The cause of the fault/error can be hidden as a result of the large alarm list.
This is the reason that priorities are assigned to Alarms 27090, 27004, 27001 and
27101 to 27107. For these alarms
S a subsequent (follow--on) alarm that occurs afterwards is no longer displayed.
This alarm is also not visible in the alarm log.
S a subsequent (follow--on) alarm that already occurred beforehand is cleared
again. This alarm is then visible in the alarm log.
Assigning priorities to Alarm 27090 only becomes effective if it occurs due to differ-
ences in the $A_INSE system variables. Only then will this alarm be initiated as a
result of different input signals. For Alarms 27004, 27001 and 27101 to 27107, no
additional condition is required, as
10-798
SINUMERIK 840D sl/SINAMICS S120 SINUMERIK Safety Integrated (FBSI sl) - - 10.2015 Edition
© Siemens AG 2015 All Rights Reserved
10/15