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

5Ć28 AutoMax Programming Executive Version 3.x
5.3.9.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.9.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.
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.9.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.8.4 for
more information. Refer to Appendix K for examples.