Rockwell Automation 57C620 AutoMax Programming Executive Version 3.8 - Manual (Page 241)

DĆ1 Limitations on Object File Size
Appendix D
Limitations on Object File Size
This appendix explains application and configuration object file limits for AutoMax
Processor modules. Note that there are limits both on the size of tasks that can be
compiled and on the size of tasks that can be loaded onto the rack.
When BASIC, Control Block, and Configuration files are compiled, the object,
symbol, and data size are printed to the screen and totaled. For Control Block
tasks, estimated execution time is also printed to the screen. Note that for BASIC
and Control Block tasks, the data required for arrays is included in the total
displayed but does not actually affect the maximum allowable task size.
Task Size Limitations
Object Symbol Data
Configuration file * ** **
BASIC task *** 64K ***
AutoMax Control Block
task
32K <ĆĆĆĆĆĆĆĆ 32K ĆĆĆĆĆĆĆĆ>
UDC Control Block
task
20K <ĆĆĆĆĆĆĆĆ 20KĆ ĆĆĆĆĆĆĆĆ>
# of Symbols
PC/Ladder Logic task 2047
* The configuration file has an object size of 0 unless the reconstructible option
is used.
** The size limit for the configuration file is determined by the amount of
memory available on the Common Memory module (M/N 57C413B or M/N
57C423), or if a Common Memory module is not being used, the AutoMax
Processor that will store the configuration file.
*** The size limit for the object and data is determined by the amount of memory
available for application tasks on the AutoMax Processor that will run the task.
Refer to the AutoMax Processor Module instruction manual (JĆ3650) for this
information.
Determining the Size of Individual Tasks
For Control Block, BASIC, and Configuration files, after the task is compiled, the
pertinent information is printed to the screen both in terms of object, symbol, and
data, and in total. To the total figure add approximately 1K for system overhead.
This figure will tell you how much memory on the Processor or UDC each task
requires. You can also choose to create log files when you compile or verify
application tasks. The log file will contain the same statistics printed to the screen.
For PC tasks, the command F3 I in the PC editor is used to determine both the
number of symbols and the approximate amount of memory the task will require
on the Processor (this includes system overhead).