Rockwell Automation 1336T Function Block Prog. Manual, Series A/B - Manual (Page 38)

2–4 System Component Detail
1336 FORCE — 5.9 August 1995
Creating an Execution List
The steps needed to create an execution list vary depending on the
type of terminal you are using. You should refer to the appropriate
documentation for information specific to your terminal. However,
general steps for creating an execution list are included here.
❒ If you are using the DriveTools software, you can create an
execution list offline by selecting the New option from the
DriveBlockEditor’s pull–down File menu.
❒
If you are using a PLC terminal, you can create an execution list
by developing a block transfer routine. Chapter 5 provides
information about block transfer routines.
Adding Events to the Execution List
Once you have created your execution list, you can add events to it.
When adding events to your execution list, keep the following
information in mind:
❒
Events are executed in the order in which they appear in the list.
Therefore, you need to add an event at the point in the list where
you want the function block to be executed.
❒
Each event that you add requires a unique block ID.
In DriveTools, you can add multiple events or a single event to an
execution list by selecting the name(s) to add from the Function
Block Library window.
NO–OP Events
You can specify that an event in your execution list have both an ID
number and a type number of zero. This is called a NO-OP event, or
no-operation event. NO-OPs are typically used as placed markers
that place a NULL event within the executed application.
If you assign a non–zero value to either the ID number or the type
number, you must also assign a non–zero value to the other number.
For example, if you assign an ID number of 25 to a function block,
you cannot assign it a type number of 0. Likewise, if you assign a
valid type number to a function block, you cannot assign the function
block an ID number of 0.