beautypg.com

Rockwell Automation 47C626 AutoMax Programming Executive V4.2 User Manual

Page 70

background image

5Ć36

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.12.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)

5.3.12.2

Generic Modules
Note that a generic" module is added to the appropriate slot in the

local rack when IODEF statements are 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.

5.3.12.3

Accessibility of Variables Added by Import
Although the Remote I/O hardware which was configured in the

AutoMax V2 configuration task does not get added to the rack, all

variables defined for it are added to the rack database. In the local

(master) rack, a generic module will have the variables defined for

the corresponding slot mapped to it. Remote I/O variables are not

accessible to the user until the correct module or rail is actually

added to the Remote rack or Head through the Rack Configurator.
Variables that exist in the rack database, but are not attached to any

module at all, are called floating variables. These variables must be

either deleted from the databases or the correct modules added to

account for them to properly document your application. Note

carefully that when you configure the remote I/O network hardware in

the Rack Configurator after the import procedure, you must be

careful to add the correct hardware (proper size rack or Remote

Head) the first time. This is important because if you make a mistake

and add the wrong hardware, the only method of modifying the

configuration is to remove the rack or Head and add the correct rack

or Head. However, removing the rack or Head will also delete all of

the floating variables that are mapped to the remote I/O system.