Saved: 2014-06-18
Filename: Catalyst Ethernet Addendum 1 1 V1_5 released
RACO Manufacturing and
Engineering
Page 19 (21)
9.2.
Setting Catalyst Remote Channels
Setting up the remote channels in the Alarmware application is described clearly in the main Catalyst manual
(Ref: 1.1.2 Net Addresses). Setting up the communication nodes and channels in Ethernet is seamless. The
Catalyst Ethernet node once declared and identified in the ControlLogix controller will become an active
node in the network.
10.
Testing
When connected to ControlLogix controller, it is possible to access the data exchanged by the ControlLogix
5000 and the Catalyst module. By writing data to the tags the communication between the PLC and the Catalyst
it is possible to ensure that the corresponding data bytes have changed on the Modbus RTU side of the network.
10.1.
Monitoring the tags
First go online and switch to “Remote Run” on the PLC. To monitor the tags, open the “Controller Tags”
window
and go to monitor tags
. Three tags named “RACO_Ethernet:C”, “RACO_Ethernet:I” and”
RACO_Ethernet:O” should be visible, representing the three instances configuration, input and output. The
configuration instance is created even if we selected its size as zero. The RACO_Ethernet:I tag is data going
from the Catalyst and RACO_Ethernet:O tag holds data going to the Catalyst.
First enter 01 02 03 04 (for the sake of example) in the Output Tag, so there is some “data” to read. This can be
done just by entering values for the Output tags
. If the network is correctly configured the corresponding data
bytes will obtain the respective value if polled by the Catalyst.
Note on the Catalyst side you should be hearing alarms being announced when the alarm conditions are
triggered. Test all the conditions before you complete your deployment…
2
3
1
