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

2–5 System Component Detail
1336 FORCE — 5.9 August 1995
Important: If you insert a NO-OP event when using the
DriveTools’ DriveBlockEditor, the DriveBlockEditor
appears to assign an ID number to a NO-OP event block
when added to an off–line file. However, the ID number
is not sent to the drive during download for NO-OP
blocks. When an on–line file is uploaded, all NO–OP
blocks have an ID number of 0.
Example Execution Lists
Important: In the following examples, the block type text is used in
place of the block type number for clarity.
The following example shows a valid execution list, with each block
type having a unique block ID.
Exec# Block Block Type
ID
1 22 ABS
2 23 AND4
3 24 BIN2DEC
4 25 COMPHY
5 30 DEC2BIN
6 27 FILTER
The following example shows an invalid execution list. The
execution list is invalid because block ID 22 cannot be assigned to
both the ABS function and the DELAY function in the same execution
list. Keep in mind that you cannot assign the same block ID to more
than one block type or block name within any given execution list.
Exec# Block Block Type
ID
1 22 ABS
2 23 AND4
3 24 BIN2DEC
4 25 COMPHY
5 30 DEC2BIN
6 22 DELAY
Chapter 3 contains additional examples of execution lists.
Linking Events
To use the output of one function block as the input of another
function block, you can create a link between the two function
blocks. A link is a software connection between two data points.
You can also use links if you want to use the same input values for
two different function blocks, or if you want to link drive linear
parameters to function block nodes.