Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 66)

5Ć10 AutoMax Programming Executive Version 3.x
5.1.8.3 Accessibility of Variables Added by Import
Although the Remote I/O hardware which was configured in the
configuration task does not get added to the rack, all variables
defined for it are added to the rack's database. In the local (master)
rack, the variables defined for the corresponding slot will be mapped
to a generic module. 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 and 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.
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 registers/ points 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.1.8.4 Register Assignments on Modules Added by Import
Registers defined for some modules in AutoMax V2 cannot be
configured in AutoMax Executive V3.x and will cause an error
message to be displayed (invalid/incompatible data type) when you
try to configure the module if you import the system or rack without
first checking your AutoMax V2 configuration. Refer to Appendix K for
examples.
Also, you can not define single and double integers in the same
addresses (except for generic cards in both local and remote racks,
where you have both an integer view and a double integer view). In
version 2.0, defining an address as both integer and double integer
was sometimes done in BLOCK_MOVE (BASIC) commands. When
you try to configure a module (created through the Import
procedure) that has integers and double integers defined in the
same register address, a warning will appear in a dialog box that tells
you that duplicate addresses were found. Double integer variables
will be loaded into the database for the module first, so the duplicate
address will always refer to the single integer variable. The dialog box
will display the name of the integer variable and the register number