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

Page 22 AN-X-DCSNet2 November 2011
Scheduled Data with a ControlLogix
AN-X-DCSNet2 exchanges scheduled data with a ControlLogix
processor.
It supports:
• up to 16 scheduled connections
• up to 248 registers of ControlLogix output data per connection
• up to 250 registers of ControlLogix input data per connection
The ControlLogix processor sends its output data to the AN-X-DCSNet2
and the AN-X sends it out on the DCS network. You create a
configuration file to define how the ControlLogix data is mapped to
DCSNet registers.
If the AN-X is a DCS master, allowed output data includes registers 32
to 39 on drop 0 (broadcast data) and registers 32 to 63 on drops 1 to 55.
If the AN-X is a DCS slave, allowed output data includes registers 0 to
31 on any drops (1 to 55) that are included in the AN-X drop number
and drop depth.
The AN-X sends input data to the ControlLogix. The configuration file
defines how DCSnet data is mapped to ControlLogix input data. There
are no restrictions on which DCS registers can be mapped to
ControlLogix input data.
In addition, you can also map connection statistics to ControlLogix
inputs.
You define data mappings in a comma-separated text file and use the
AN-X web interface to send the mapping file to the AN-X.
Connections
There are two possible types of scheduled connections from the
ControlLogix processor to the AN-X-DCSNet:
• Exclusive owner connection, which contains input and output data
• Input-only connection, which contains input data
Only the exclusive owner connection can write data to AN-X and to
DCSNet.
There can be only one exclusive owner connection to an AN-X module.
In general, you should try to keep the number of connections small.
There is significant overhead in opening and maintaining each
connection.
Configuration
To configure the scheduled data exchange:
1. Configure AN-X in RSLogix 5000