Rockwell Automation 1756-SPESMNRMXT GuardLogix Controllers User Manual - Manuel (Page 20)

20 Rockwell Automation Publication 1756-UM020I-EN-P - August 2012
Chapter 1 System Overview
Selecting Safety I/O Modules Safety input and output devices can be connected to CIP Safety I/O on
DeviceNet or EtherNet/IP networks, allowing output devices to be controlled by
a GuardLogix controller system via DeviceNet or EtherNet/IP communication.
For the most up-to-date information on available CIP Safety I/O catalog
numbers, certified series, and firmware revisions, see
http://www.ab.com/certification/safety .
Selecting Communication
Networks The GuardLogix controller supports communication that lets it do the
following:
• Distribute and control Safety I/O on DeviceNet or EtherNet/IP
networks.
• Distribute and control remote Safety I/O on DeviceNet, EtherNet/IP, or
ControlNet networks.
• Produce and consume safety tag data between 1756 and 1768 GuardLogix
controllers across EtherNet/IP or ControlNet networks or within the
same ControlLogix chassis.
• Distribute and control standard I/O on EtherNet, ControlNet, or
DeviceNet networks.
Use these communication modules to provide an interface between GuardLogix
controllers and network devices.
The GuardLogix controller can connect to RSLogix 5000 programming software
via a serial or USB connection, an EtherNet module, or a ControlNet module.
1756-L6 xS controllers have a serial port. 1756-L7xS controllers have a USB port.
See the Additional Resources on page 13 for more information on using network
communication modules.
Table 6 - Communication Modules
To interface between Use this module Refer to these
Installation
Instructions
The GuardLogix controller and DeviceNet devices 1756-DNB DNET-IN001
The GuardLogix controller and EtherNet/IP devices
1756-ENBT
1756-EN2T
1756-EN2F
1756-EN2TR, 1756-EN3TR
1756-EN2TXT ENET-IN002
Controllers on the ControlNet network
1756-CN2, 1756-CN2R
1756-CN2RXT CNET-IN005