Rockwell Automation 47C626 AutoMax Programming Executive V4.2 - Manual (Page 71)

5Ć37
When you configure the remote I/O system, you will be prompted
that variables have already been configured for the hardware.
If floating variables exist in a remote I/O network when the
configuration object file is generated in the Task Manager, they will be
included in the configuration object code even though they are not
accessible in the Variable Configurator. Floating variables in the
master rack are flagged as errors. You can compile tasks when there
are floating variables in a remote I/O network. You cannot, however,
compile tasks when there are floating variables in a master rack.
Local network variables will be linked to networkĆwide names
whenever possible. If there is a networkĆwide name for the network
point used by a variable, the networkĆwide variable is linked to that
variable. Any network or remote I/O variables configured as both
single and double integers will not import correctly. The procedure
will result in prompts that indicate duplicate Multibus addresses"
and will require you to delete the offending variables.
5.3.12.4 Register Assignments on Modules Added by Import
Registers defined for some modules in AutoMax V2 cannot be
configured in the current Executive software and will cause an error
message to be displayed (invalid/incompatible data type) when you
try to configure the module if you import the rack without first
checking your AutoMax V2 configuration. See section 5.1.9.4 for
more information. Refer to Appendix K for examples.
5.3.12.5 Source Drive and Subdirectory for Import
It is important that the files to be imported be stored in a specific
manner as follows. The only configuration task in the subdirectory
should be the configuration task for the rack you want to import. The
configuration task does not need to be compiled because the import
procedure will compile it. If there is more than one configuration task
in the subdirectory, the import procedure will use the first one found,
which may not necessarily be the configuration you want to import.
The Import procedure will copy in all the application tasks (.BAS,
.BLK, .PC. and .INC) found in the subdirectory. However, only those
tasks with corresponding TASK statements in the configuration task
will be added to the tasks database. If no application task exists for a
TASK statement, you will be prompted to delete the task when you
enter the Task Manager. Utility tasks (those without TASK statements)
can subsequently be added in the Task Manager, which can use the
imported source file of the same name.
5.3.12.6 Procedure for Importing a Rack
Use the following procedure to import a rack.
Step 1.
Select Import from the Rack menu. Note that this assumes
you have selected a system and section first. The Import
V2 Rack dialog box will be displayed.
Step 2. Enter information for the following fields, then select OK.
Some fields may contain default entries. If you do not
change these fields, the default will be used.
Rack name Ć The name you want to use for the rack in the
currently selected; an alphanumeric string (unique within
the system) of up to 8 characters (no spaces, hyphens, or
underlines). The name of the rack in the new system may