Devicenet connections for cip safety i/o modules, Standard devicenet connections – Rockwell Automation 1756-SPESMNRMXT GuardLogix Controllers User Manual Manuel d'utilisation
Page 66
66
Rockwell Automation Publication 1756-UM020I-EN-P - August 2012
Chapter 4
Communicate over Networks
These software products are used with the DeviceNet networks and 1756-DNB
module.
DeviceNet Connections for CIP Safety I/O Modules
To access CIP Safety devices on DeviceNet networks, add a 1756-DNB to the
I/O Configuration tree of the GuardLogix controller project.
CIP Safety I/O modules on DeviceNet networks are added to the project under
the 1756-DNB module, as described in
. When you add a CIP Safety I/O module, RSLogix
5000 software automatically creates controller-scoped safety data tags for that
module.
Figure 16 - DeviceNet Module in Controller in the I/O Configuration Tree
Standard DeviceNet Connections
If you use standard DeviceNet I/O with your GuardLogix controller, you need to
allocate two connections for each 1756-DNB module. One connection is for
module status and configuration. The other connection is a rack-optimized
connection for the DeviceNet I/O data.
Table 17 - Software for Use with DeviceNet Networks
Software
Is used to
Required/Optional
RSLogix 5000
• Configure ControlLogix projects.
• Define DeviceNet communication.
Required
RSNetWorx™ for DeviceNet
• Configure DeviceNet devices.
• Define the scan list for those devices.
RSLinx Classic or RSLinx
Enterprise
• Configure communication devices.
• Provide diagnostics.
• Establish communication between devices.