
AN-X-TI-MAS Page
25
When you create a mapping for a module, all the input or output data for
the module is mapped; you cannot map individual registers.
AN-X can automatically create a default mapping file when you
autoconfigure I/O. See page 19 for details.
ClxName
This line in the file identifies the AN-X module. AN-X uses this name in
the address portion of the ControlLogix tags it creates for the data. The
ClxName definition consists of a line with the keyword ClxName,
followed by a comma and the name you give the emulated ENBT (see
page 33) when you configure the AN-X in RSLogix 5000.
Example:
ClxName, TIMaster
When AN-X creates a configuration file automatically, it uses the
Ethernet host name (see page 11) as the default ClxName.
ClxPrefix
The ClxPrefix is used in the name portion of the tagnames AN-X creates
for import into RSLogix 5000. AN-X prefixes each tagname with the
ClxPrefix. The ClxPrefix can be used to distinguish tags for the same
address when the ControlLogix processor has connections to more than
one AN-X-TI-MAS.
For example, if the ControlLogix has connections to two AN-X-TI-MAS
modules, each controlling a different TI remote I/O network, each
network could have a module with the same base and slot address. Using
a different ClxPrefix in the configuration file for each AN-X-TI-MAS,
for example TI1_ and TI2, ensures the tagnames for the two modules are
distinct.
The ClxPrefix consists of a line with the keyword ClxPrefix, followed by
a comma and the prefix text. The default is TI_
Example:
ClxPrefix,TI_
Scheduled Connection Data
Each scheduled connection to the AN-X begins with a line that consists
of the keyword ClxSlot followed by a comma and then a number from 0
to 15