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

3–8 System Interactions
1336 FORCE — 5.9 August 1995
The following example is not valid because block ID 23 was re–used
for a new event when it was already assigned to a BIN2DEC function
block.
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 23 Integral
4 24 COMPHY
5 25 DEC2BIN
6 26 DELAY
Existing, valid application New (subsequent) event list
In this last example, the second execution list is invalid only in the
subsequent compile mode. If the first application was cleared with a
function block Init, the second (new) execution list would be valid
during an initial mode compile. This is a major difference between
using the DriveBlockEditor and a GPT to compile your execution
list. The following sections contain additional information about the
different terminals.
You can do either an initial compile mode or a subsequent compile
mode when you use the PLC block transfer mechanism.
Because a PC running DriveTools has significantly more available
RAM than a hand-held GPT, the PC running DriveTools can store
more information. Besides maintaining its own copy of an execution
list (when in ONLINE mode), a PC running DriveTools also holds a
one word value for every node to be created and a one word link
reference for every linkable input node.
The DriveTools’ DriveBlockEditor uses the Data Highway Plus
protocol to perform emulated block transfer commands. It uses the
same block transfer services available to a PLC from one of the
adapter’s RIO ports.
DriveTools’ DriveBlockEditor
Download and Compile
Operation