Devicenet connections for cip safety i/o modules, Standard devicenet connections – Rockwell Automation 1756-L7x GuardLogix 5570 Controllers User Manual

Page 56

Advertising
background image

56

Rockwell Automation Publication 1756-UM022A-EN-P - November 2012

Chapter 4

Communicate over Networks

These 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

Chapter 5

,

Add, Configure, Monitor,

and Replace CIP Safety I/O

. When you add a CIP Safety I/O module, the Logix

Designer application automatically creates controller-scoped safety data tags for
that module.

Figure 15 - 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 - Product for Use with DeviceNet Networks

Product

Is used to

Required

Studio 5000 environment

Configure ControlLogix projects.
Define DeviceNet communication.

Yes

RSNetWorx for DeviceNet software

Configure DeviceNet devices.
Define the scan list for those devices.

Yes

RSLinx Classic or
RSLinx Enterprise software

Configure communication devices.
Provide diagnostics.
Establish communication between devices.

Yes

Advertising