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

3–7 System Interactions
1336 FORCE — 5.9 August 1995
Subsequent Compile Mode
With the subsequent compile mode, a new execution list is compared
against the current application in the drive to selectively create and
delete function block objects. This compile mode is automatically
enabled when a previously valid application exists in the drive.
Common event blocks will retain previous node values and links.
Only the new event blocks need to be adjusted.
The GPT uses the subsequent compile mode for its download and
compile service.
The subsequent mode of operation is a bit more involved and
requires that you remove any links from blocks that receive input
from an object to be deleted before downloading and compiling the
new list. Processing links is the compiler’s last step. If you do not
remove links to objects that are to be deleted, you will get an error.
Examples of Subsequent Compile Mode Operations
Important: In the following examples, the block type name is used
in place of the block type number for clarity.
The following example shows a valid subsequent compile. In this
example, no new blocks were created and no existing block was
deleted; only the execution sequence was changed.
Exec# Block Block Type
ID
1 1 ABS
2 2 AND4
3 3 BIN2DEC
4 4 COMPHY
5 5 DEC2BIN
6 6 DELAY
Exec# Block Block Type
ID
1 6 DELAY
2 5 DEC2BIN
3 4 COMPHY
4 3 BIN2DEC
5 2 AND4
6 1 ABS
Existing, valid application New (subsequent) event list
The following example is also valid. Block ID’s 23 and 26 were
removed from the original program, and blocks 38 and 46 were
newly created and need to be set up. The blocks which are common
to both lists will retain all previous links and values.
Exec# Block Block Type
ID
1 21 ABS
2 22 AND4
3 23 BIN2DEC
4 24 COMPHY
5 25 DEC2BIN
6 26 DELAY
Exec# Block Block Type
ID
1 21 ABS
2 22 AND4
3 38 Integral
4 24 COMPHY
5 25 DEC2BIN
6 46 DELAY
Existing, valid application New (subsequent) event list