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

Architecture: The ApplicationTemplate PackML in detail
Triggering alarms
78
Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.9 Triggering alarms
Example: Triggering / forwarding alarms - within a machine module
Program line for triggering an alarm within the machine application:
[9-29] Example: Trigger Alarm1 of FB AlarmsA
There is a predefined coupling between the alarm handling and the state machine for the alarm
reactions "Stop" and "Abort".
• The alarm reactions trigger a PackML command "STOP" or "ABORT" in the module in which the
error occurred.
• These alarm types automatically deactivate the module which has no direct impact on the
master module.
• The alarm reaction types of the slaves and the own module can be defined individually so that
the desired state change in the state machine is possible.
Example: Triggered alarm with "Abort" reaction type in case of module 1
The following example shows what happens if an alarm of the "Abort" reaction type is triggered at
a slave module. The example contains two lower-level slave modules.
scMAL.AlarmsA.xAlarm1Trigger:=True;
• The state machine is located in the "Execute".
• The current state of the state machine is
highlighted in red.
• An alarm of the "Abort" reaction type is
triggered in the Module_1 slave module. The
Al. 1. input is highlighted in red.