Lenze ApplicationTemplate PackML (PLC Designer R3-x) - Manual (Page 77)

Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
77
Architecture: The ApplicationTemplate PackML in detail
Alarm handling (error handling)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.8.2 Acknowledging alarms
Acknowledging alarms deletes all messages/causes defined as subject to acknowledgement from
the Alarm List. The acknowledgement of alarms can be activated by means of the following
procedures:
1. Permanent activation: Within the module application via the following program command:
2. Activation for one cycle: Via the Command_AlarmQuit method, rising edge FALSE

TRUE. The
method sets the xQuitErrors input to TRUE for one cycle.
If multiple alarms occur, they cannot be acknowledged individually. Further information:
 L_EATP_ModuleErrorHandler_PackML ( 103)
9.8.3 Acknowledging alarms: Response in the machine module
The xErrorQuitActive output on the L_EATP_ModuleErrorHandler_PackML block can be used within
a module application to acknowledge alarms on an integrated function block.
Defining alarms - standard procedure
dwAlarmPriority Assign priority for alarms of the same error reaction type.
xAlarmAckNeeded Acknowledgement behaviour:
Information (yes/no) stating
whether the alarm tripped is to be
acknowledged.
The acknowledgement behaviour cannot
be changed for all alarm reaction types.
Characteristic Description Further information
ErrorHandler.xQuitErrors := TRUE; //error acknowledgement active as long as value =
TRUE
• The SetAlarms is to be extended
by one function block.
• The MAP_EmptyModul_App1 FB
has to be extended by the
corresponding declaration.
• The xAlarmTrigger[1...4] method
has to be connected to the module
application.
• Assign the corresponding
parameter to the respective alarm
input:
• Number,
• text,
• priority,
• category,
• Acknowledgement response
• More information:
 L_EATP_Alarm_PackML ( 98)