Lenze PLC Designer PLC Designer (R2-x) - Manual (Page 415)

L-force | PLC Designer
The Resources

DMS 3.2 EN 02/2011 TD29 413
Insert the desired attributes:
Name: a name for the task; with this name the task is represented in the
configuration tree; the name can be edited there after a mouseclick on the entry or
after pressing the <Space> key when the entry is selected.
Priority (0-31): (a number between 0 and 31; 0 is the highest priority, 31 is the lowest),
Type:
cyclic ( ) : The task will be processed cyclic according to the time definition given in
the field 'Interval' (see below).
freewheeling ( ) : The task will be processed as soon as the program is started and at
the end of one run will be automatically restarted in a continuous loop. There is no
cycle time defined.
triggered by event ( ): The task will be started as soon as the variable, which is
defined in the Event field gets a rising edge.
triggered by external event ( ): The task will be started as soon as the system event,
which is defined in the Event field, occurs. It depends on the target, which events will
be supported and offered in the selection list. (Not to be mixed up with system events
Properties for event triggered tasks:
Interval (for Type 'cyclic' resp. 'triggered by external event' if the event requires a
time entry): the period of time, after which the task should be restarted. If you
enter a number, then you can choose the desired unit in the selection box behind
the edit field: milliseconds [ms] or microseconds [μs]. Inputs in [ms]-format will be
shown in the TIME format (e.g. "t#200ms") as soon as the window gets repainted;
but you also can directly enter the value in TIME format. Inputs in [ms] will always
be displayed as a pure number (e.g. "300").
Event (for Type 'triggered by event' or 'triggered by external event'): a global
variable which will trigger the start of the task as soon as a rising edge is detected.
Use button ... or the input assistant <F2> to get a list of all available global
variables.
Possibly the target system defines Singleton Events. These are events, which only
allow to start one single task. Whether such an event starts several tasks will be
checked during compilation of the project. The check regards the data address of
the event variable, not on the name.