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

7Ć6 AutoMax Programming Executive Version 3.x
In order for application tasks in the rack to be able to access the
variable in this rack, the register/bit must have a local name in the
rack. The local name for a register/bit will be displayed (in the local
name" field) only when configuring the Network module that contains
the actual drop area where the register/bit is located. The local name
will not be displayed in this register/bit location when the Network
drop area is viewed through any other Network module on the
network. Note that the meaning of local" in terms of the Network
module configuration form is different from local" in the sense of
variable access in a single application task as described in
section 7.1.
To add a networkĆwide name to a rack configuration so that
application tasks within the rack can access it, the networkĆwide
name must be linked to a local name. This is done by checking the
Link networkĆwide and local variable names/descriptions" checkbox
when the desired networkĆwide name is selected. Note that whether
the local or networkĆwide names are linked or not, only the
networkĆwide description will be displayed on the form. The local
description will be displayed in the default fields at the bottom of the
screen when the register is selected.
If you link the networkĆwide and local variable names when the local
name field is empty, the networkĆwide name will be copied to the
local name field. Conversely, if the local name is specified and the
networkĆwide field is empty, checking the box will copy the local
name to the networkĆwide field. NetworkĆwide and local names doe
not have to be the same in order to be linked. When the names are
linked, the Linked" column on the screen will display a
doubleĆheaded arrow (<-->). If you delete a networkĆwide variable
name, any local variables linked to that name will also be deleted for
all racks in the system.
Because of the way in which linked networkĆwide names are stored
(in the network database as well as in individual rack configurations),
there is a great deal of flexibility in manipulating the configuration of
the network. You can edit or copy linked networkĆwide names from
any Network module on that network. Linking the local name to the
networkĆwide name is also helpful in case you need to reĆorganize
your use of network registers because all local names linked to a
networkĆwide name are copied when the networkĆwide name is
copied. Further, if you edit the networkĆwide name for a register, the
new name will replace the old networkĆwide name for all racks on the
network. It is important, however, to understand the results of editing
a linked networkĆwide name.
In order to successfully edit, i.e., change the name of a linked
networkĆwide variable, the rack configuration databases for all the
racks on the network must be present and accessible so that the
AutoMax software can change the name in each at the same time.
The reason for this is that when the configuration object code for a
rack is generated, the actual register/bit address of a linked local
name is determined using the networkĆwide name, which is also
stored in the rack's database, as a key into the network database. If a
register/bit has a local name which is NOT linked to a networkĆwide
name, the register/bit address is found in the rack database, not the
network database. If the change cannot be made in all of the racks'
databases at this time, the old networkĆwide name (in the unchanged
rack's database) will no longer have a corresponding entry in the
network database. This condition will be flagged as an unresolved
networkĆwide name" when the configuration for this rack is
generated.