AN-X2-MOD-MON Page
39
Tag Format
AN-X builds the tags from the ControlLogix configuration. Each tag is a ControlLogix
alias. For example,
ALIAS,"","MOD_d01s5_Inp","B805","","AnxModMon:0:I.Data[2]"
In this example, the tag name is MOD_d01s5_Inp. The name is made up of the ClxPrefix
(MOD_) and the tagname (d01s5_Inp) from the ControlLogix configuration file.
If there is more than one word of data for the module, AN-X appends an underscore and a
number to the tagname, for example
ALIAS,"","MOD_d02s3_Inp_0","DDI_353_00","","AnxModMon:0:I.Data[7]"
ALIAS,"","MOD_d02s3_Inp_1","DDI_353_00","","AnxModMon:0:I.Data[8]"
For monitored outputs, AN-X generates two sets of tags, one for the actual output data,
and another that points to an internal ControlLogix array. For example,
ALIAS,"","MOD_MONOUT_d01s4_Out","B804","","AnxModMon:0:I.Data[18]"
ALIAS,"","MOD_d01s4_Out","16-OUT B804","","AnxModMonTempOut[0,18]"
The tagname for the I/O data is MOD_MONOUT_d01s4_Out, which is made up of the
ClxPrefixOut (MOD_MONOUT_) and the tagname (d01s4_Out) from the ControlLogix
configuration file.
The internal array tagname is made up of the ClxPrefix (MOD_) and the tagname
(d01s5_Inp) from the ControlLogix configuration file.
The internal array name is made up of the ClxName (AnxModMon) from the
ControlLogix configuration file appended with TempOut. This array is used in
applications where you are using monitor mode on the AN-X to monitor and convert an
existing Modicon control system.
Using the Ethernet/IP Log
If there are problems with scheduled connections to the AN-X, use the Ethernet/IP log to
identify the cause.
From the web interface, select
Log Files/Ethernet/IP Log
to display the log. Look for
error messages that describe in detail the cause of any problem with the current
configuration.
