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

5Ć27 Using the System Configurator
5.3.9 Importing a Rack from
AutoMax Version 1 or Version 2
You can import the configuration information and application tasks
for an AutoMax Version 1 or AutoMax Version 2 rack and any Remote
I/O racks into AutoMax Executive V3.x. The rack name must not
already exist in the selected system. If you want to use tasks
created with earlier versions of the AutoMax V3 Executive in a
V3.5 environment, see Appendix Q.
Before importing an AutoMax V1 rack, you must edit any Control
Block tasks as follows: decimal points must be added to any real
literal values that do not already have them. Blocks that allow real
literal values include the following: DIFF_LAG, INTEGRATE, LAG,
LEAD_LAG, PROP_INT, and PID. After adding the decimal points
where appropriate, the task must be reĆcompiled. No changes are
required for tasks in AutoMax V2 racks.
It is helpful to try to create a test rack in V3.x first to understand the
structure by which the configuration task and application tasks will be
organized when they are imported into V3.x. The Import command
will not delete the original files or alter them in any way.
If your system has .NET files, you must run NETIN to compile the
.NET files and generate a networkĆwide database prior to importing
AutoMax V2 racks. Refer to Appendix G for the NETIN procedure.
The Import procedure will add the variables and their descriptions
from the AutoMax configuration task to the rack's variable database.
The task names, types, priorities, critical flags, and Processor slots
from the configuration task TASK statements are added to the task
database.
The Import procedure will copy in the task source files for the rack.
Note that tasks must be compilable in AutoMax V2 in order to import
properly. Since BASIC include (.INC) files are treated as tasks in the
current Executive software, a task is added for each include file
found.
5.3.9.1 Module Types Recognized by the Rack Import Procedure
Import will add as many modules as possible from the variable
definition statements in the configuration task. The following list
shows the modules added for the type of definition found.
Definition Found Type of Module Added
NETDEF or GBLDEF 57C404 Network
Communications
MODDEF 57C414 Modbus interface
RIODEF 57C416 Remote I/O
Communications
(in the master rack)
RNETDEF 57C417 AutoMate interface
ABDEF 57C418 AB interface
TASK 57C430 AutoMax Processor
IODEF Generic module (unless
one of the other
definitions is found for
the slot)