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

3–6 System Interactions
1336 FORCE — 5.9 August 1995
You can use any of the three supported terminal devices to create and
update your function block applications:
❒
DriveTools’ DriveBlockEditor
❒ Graphic Programming Terminal (or GPT)
❒
PLC block transfer
The three terminal devices use different compiler modes due to
differences in the amount of their available RAM. Depending on
how you change your execution list, you may receive an error when
using one terminal device, but not when you use another terminal
device. This section describes the compiler modes that are used and
information specific to the individual terminal devices to help you
use function blocks more effectively.
Regardless of which terminal device you are using, an application is
created when you compile your execution list. You should also note
the following information:
❒
The application executes partially out of RAM.
❒ The application executes within a 20 millisecond task interval and
is integral to the system operation.
❒
The compiler resides on the PLC Communication Adapter board
as part of its AP or Application Processor code PROM.
The two basic compiler modes used for function blocks are the initial
compile mode and the subsequent, or comparison, compile mode.
You do not select which mode to use; the compile mode is
automatically determined by the terminal device and whether or not
an application already exists in the RAM area of the drive.
Initial Compile Mode
With the initial compile mode, no events exist in the drive when the
execution list is downloaded, and all the objects are created from
scratch.
The DriveTools’ DriveBlockEditor always uses the initial compile
mode for its download and compile service. The DriveBlockEditor
forces an initial compile mode by initializing the function block’s
RAM before downloading the new execution list for compilation.
Compiler Modes and Terminal
Operation Differences
Compiler Modes