
Acyclic Triggers
These consist of a specified date and time. The action specified by such a trigger is performed
once at the date and time specified.
Cyclic Triggers
These consist of a specified time interval and starting point. The following types of cyclic
triggers are available:
● Default cycle. The start of the first time interval coincides with the start of Runtime. The
length of the interval is determined by the cycle.
● Hourly. The start of the interval is specified as minutes and seconds. The length of the
interval is an hour.
● Daily. The start of the interval is specified by the time (hours, minutes and seconds). The
length of the interval is a day.
● Weekly. The start of the interval is specified by the day of the week (Monday, Tuesday,
etc.) and the time. The length of the interval is a week.
● Monthly. The start of the interval is specified by the day and time. The length of the interval
is a month.
● Annually. The start of the interval is specified by the day, month and time. The length of
the interval is a year.
Tag Triggers
These consist of the specification of one or more tags. The action associated with such a trigger
is performed each time a change in the value of one of these tags is detected.
How the tag values are queried may be customized for each tag. Either cyclic polling with a
specified period or a reaction as soon as the system detects a change in the tag value may
be selected.
Depending on the choice of query method, it is possible that the tag changes but the system
does not detect this. In this case the action is not performed.
Effect of Triggers on an Action
If the action is associated with only one trigger, then the action is performed as soon as the
triggering event occurs.
However, an action may be associated with multiple triggers, such as a cyclic trigger and a
tag trigger. In this case, the action is performed whenever one of the two triggering events
occurs. If two events occur simultaneously, the action is executed twice in sequence. If two
tag triggers fire at the same time, the action is performed only once.
The processing of an action should be completed before another call of the action occurs, as
there might otherwise be an overflow of the queue.
Tip:If the action is not to be carried out with each event occurrence, then a condition can be
specified
for the action that controls its further course dependent on the event. If the action is
not to be executed any more, it can be terminated with a <value> return.
ANSI-C for Creating Functions and Actions
2.13 Creating and Editing Actions
MDM - WinCC: Scripting (VBS, ANSI-C, VBA)
812
System Manual, 11/2008,