ProSoft Technology AN-X-AMX - Manual (Page 34)

Page 30 AN-X-DCSNet2 November 2011
The ClxPrefix can be used to distinguish between AN-X modules when a
ControlLogix processor communicates with more than one AN-X. Use a
different prefix for each AN-X
Example:
ClxPrefix, ANX2
I/O 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
Example:
ClxSlot, 0
This is followed by mappings of input and output data for that
connection.
Scheduled outputs from the ControlLogix processor for the connection
begin with a line with just the keyword DataOutput.
Scheduled inputs to the ControlLogix processor for the connection begin
with a line with just the keyword DataInput.
Data definitions consist of lines that define the mapping between the
ControlLogix data table and the DCSNet data.
They are of the form
CLXoffset, drop, register, length
For example, the entry
200,4,0,10
maps 10 registers starting at drop 4, register 0 to offset 200 in the current
section.
If the offset is omitted, AN-X automatically assigns an offset based on
the previously mapped data.
For example, to automatically map the same data as the previous
example, use
,4,0,10
The maximum size for each section is 250 input registers and 248 output
registers.
Anything after a semicolon on a line is treated as a comment and is
ignored. You can use this to document the file by adding comments to
the ends of lines or as separate lines.
Output Data
If the AN-X-DCSNet is a DCS slave, the only valid entries are DCS
registers 0-31 on drops included in the AN-X drop number and drop