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

5Ć9 Using the System Configurator
example, A00) indicates which network is primary (in this example,
A). The description, engineer, and customer data for the system and
each rack are transferred from the ASD file. Import adds racks using
the same process as for importing an AutoMax Version 2 rack.
The Import procedure will add as many modules to the rack as
possible based on the definition type found for a given slot (see
section 5.1.8.1 for information regarding module types). Import will
add the variables and their descriptions defined in the configuration
task. The networkĆwide variable names will be added using the .NET
files, if any. .NET files define network addresses for GBLDEF
variables in configuration tasks.
The tasks (name, type, priority, critical flag, and Processor slot)
defined in the configuration task will also be added. Task source files
will be copied into the AutoMax Executive system. Note that tasks
must successfully compile in ASD in order to import properly. Since
BASIC include files (.INC) are treated as tasks in the AutoMax
Executive software, a task is added for each include file found. Import
will also copy and rename any system, rack, or task documentation
files from the ASD system into the AutoMax Executive system. The
CPU documentation files in the ASD system will be copied into
AutoMax Executive system, but they can be accessed by the
AutoMax Executive software only by using Edit File from the
Commands menu. You may want to copy pertinent information into
the documentation files for the appropriate racks.
5.1.8.1 Module Types Recognized by the 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)
5.1.8.2 Generic Modules
A generic" module, identified by the prefix GEN", is added to the
appropriate slot in the local rack when IODEF statements are the only
statements found for the slot in the configuration task. The generic
module is used because the IODEF statement does not provide
enough information to determine the specific type of module used.
Note also that for a remote I/O network, no hardware is added to the
rack database for the same reason.