Rockwell Automation DeviceNet Communications for PanelView Plus and PanelView Plus CE User Manual

DeviceNet Communications

For PanelView Plus and
PanelPlus CE Terminals

2711P

User Manual

Important User Information

Solid state equipment has operational characteristics differing from those of
electromechanical equipment. Safety Guidelines for the Application,
Installation and Maintenance of Solid State Controls (publication SGI-1.1
available from your local Rockwell Automation sales office or online at
http://literature.rockwellautomation.com
differences between solid state equipment and hard-wired electromechanical
devices. Because of this difference, and also because of the wide variety of
uses for solid state equipment, all persons responsible for applying this
equipment must satisfy themselves that each intended application of this
equipment is acceptable.

In no event will Rockwell Automation, Inc. be responsible or liable for
indirect or consequential damages resulting from the use or application of
this equipment.

The examples and diagrams in this manual are included solely for illustrative
purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume
responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to
use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without
written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware
of safety considerations.

) describes some important

WARNING

IMPORTANT

ATTENTION

SHOCK HAZARD

BURN HAZARD

Identifies information about practices or circumstances that can cause
an explosion in a hazardous environment, which may lead to personal
injury or death, property damage, or economic loss.

Identifies information that is critical for successful application and
understanding of the product.

Identifies information about practices or circumstances that can lead
to personal injury or death, property damage, or economic loss.
Attentions help you identify a hazard, avoid a hazard, and recognize
the consequence

Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that dangerous voltage may be present.

Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that surfaces may reach dangerous
temperatures.

Table of Contents

Preface

DeviceNet Overview

Configure the Terminal as a Slave
Device

Configure the Terminal as a
Scanner

About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Topics Covered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . 5

Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

DeviceNet Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

DeviceNet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Module Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Sample Network Configuration . . . . . . . . . . . . . . . . . . . . . . 15

Configure Communications . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configure RSNetWorx for DeviceNet Software . . . . . . . . . . . 31

Use RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 3

Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configure Communications . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configure RSNetWorx for DeviceNet . . . . . . . . . . . . . . . . . . 60

Use RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . . . . 69

Restore Configuration to Local Tab

Index

Appendix A

Copy Configuration to Local Tab . . . . . . . . . . . . . . . . . . . . . 71

3 Publication 2711P-UM004B-EN-P - March 2007

4 Table of Contents

Publication 2711P-UM004B-EN-P - March 2007

Preface

About This Publication

Topics Covered

PanelView Plus and PanelView Plus CE terminals with a DeviceNet
communications module support DeviceNet scheduled I/O
communications. This guide will show you how to configure
DeviceNet communications between a PanelView Plus terminal and a
ControlLogix controller.

The PanelView Plus and PanelView Plus CE terminals can operate as a
slave or a scanner on the DeviceNet network. You will learn how to
configure a PanelView Plus terminal as a slave and a scanner using
RSView Studio Machine Edition, RSNetWorx for DeviceNet software,
and RSLogix 5000 programming software.

Chapter 1 Overview of DeviceNet module
Provides an overview of the DeviceNet communication module for
PanelView Plus and PanelView Plus CE devices including supported
controllers and DeviceNet I/O messaging.

Chapter 2 Configure Terminal as a Slave Device
Shows how to configure your PanelView Plus terminal to operate as a
slave device on a DeviceNet network using I/O messaging. The
procedures in this chapter build on the configurations defined in
Chapter 1.

Hardware and Software Requirements

Chapter 3 Configure Terminal as a Scanner
Shows how to configure your PanelView Plus terminal to operate as a
scanner on a DeviceNet network using I/O messaging.

Appendix A Restore Configuration to Local Tab
Shows how to copy the Target tab configuration to the Local tab.

To configure applications for DeviceNet communications, you must
install the appropriate communication module on your PanelView
Plus or PanelView Plus CE terminal. You must also verify that the
correct software and firmware is installed on the development
computer.

PanelView Plus 700 to1500

Hardware and Software

RSView Studio Version 4.0 or later Version 4.0 or later

RSView Machine Edition
Runtime

PanelView Plus CE 700 to
1500

Version 4.0 or later Version 4.0 or later

PanelView Plus
400/600

5 Publication 2711P-UM004B-EN-P - March 2007

6

Hardware and Software

PanelView Plus 700 to1500
PanelView Plus CE 700 to
1500

PanelView Plus
400/600

RSNetWorx for DeviceNet Version 6.0 or later V6.0 or later

RSLogix 5000 15.0 or later 15.0 or later

Terminal Communication
Module and Firmware

2711P-RN10H
firmware version 3.16 or later

2711P-RN10C
firmware version 3.16
or later

Publication 2711P-UM004B-EN-P - March 2007

7

Additional Resources

For more information on RSView Enterprise or RSView Studio
programming software, refer to the online help.

You can download electronic versions of these publications from the
Rockwell Automation website:

http://www.literature.rockwellautomation.com

Publication Publication Number

PanelView Plus User Manual 2711P-UM001

RSView Machine Edition User Manual ViewME-UM003

DeviceNet Selection Guide DNET-SG001

DeviceNet Media Design Installation Guide DNET-UM072

DeviceNet Tips & Tricks DNET-BR003

Communication Module Installation Instructions 2711P-IN003

Publication 2711P-UM004B-EN-P - March 2007

8

Publication 2711P-UM004B-EN-P - March 2007

DeviceNet Overview

Chapter

1

Chapter Objectives

DeviceNet Protocol

Supported Controllers

This chapter provides an overview of:

• DeviceNet protocol

• Controller support

• DeviceNet modules

• DeviceNet module indicators

The PanelView Plus or PanelView Plus CE terminals support
DeviceNet I/O only. DeviceNet allows direct connection of devices. It
also provides a control architecture that supports multiple processors.
DeviceNet is a trunk/drop or bus-based network that supports up to
64 nodes and operates at 125, 250, or 500 Kbps.

A PanelView Plus or PanelView Plus CE terminal with a DeviceNet
communication module can connect with other devices. Typical
controllers supported include:

• 1756-DNB module for the Control Logix network

• 1771-SDN module for the PLC-5 network

• 1747-SDN module for the SLC 5/03 to SLC 5/05 network

DeviceNet Module

9 Publication 2711P-UM004B-EN-P - March 2007

There are two DeviceNet communication modules:

• 2711P-RN10C for PanelView Plus 400 and 600 terminals

• 2711P-RN10H for PanelView Plus and PanelView Plus CE 700

to 1500 terminals

For details how to install the modules on the terminals, refer to the
2711P-IN003 installation instructions that ship with the module.

ATTENTION

The DeviceNet network is not supported on a personal
computer running RSView Machine Edition software.

10 DeviceNet Overview

2711P-RN10C DeviceNet Module for 400 and 600 Terminals

I/O Status Indicator

NET Status
Indicator

MOD Status Indicator

Red
White
Shield
Blue
Black

2711P-RN10H DeviceNet Module for 700 to 1500 Terminals

NET Status
Indicator

WARNING

MOD Status Indicator

I/O Status Indicator

Red
White
Shield
Blue
Black

Do not connect or disconnect any communication cable with
power applied to this device or any device on the network. An
electrical arc could cause an explosion in hazardous location
installations. Be sure that power is removed or the area is
nonhazardous before proceeding.

Publication 2711P-UM004B-EN-P - March 2007

DeviceNet Overview 11

Module Indicators

The DeviceNet communication modules have three indicators:
Network Status, I/O Status, Module Status.

DeviceNet I/O Status Indicator

This bi-color (green/red) LED provides information on the states of
inputs and outputs.

Condition Status Indication

Off Outputs active All outputs are active.

Inputs active All inputs are active.

Green Outputs active One or more outputs are active and

under control, and no outputs are
faulted.

Inputs active One or more inputs are active and

producing data, and no inputs are
faulted.

(1)

Flashing green

Flashing red

Outputs idle One or more outputs are idle, and no

outputs are active or faulted.

(1)

Outputs faulted One or more outputs are faulted, and

may be in the fault state.

Inputs faulted One or more inputs are faulted, and

may be in the fault state.

Red Outputs forced off One or more outputs are forced off

(may be an unrecoverable fault).

Input unrecoverable fault One or more inputs has an

unrecoverable fault.

(1)

The flash rate of the LED is approximately 1 flash per second. The LED should be on for approximately 0.5
seconds and off for approximately 0.5 seconds.

Publication 2711P-UM004B-EN-P - March 2007

12 DeviceNet Overview

DeviceNet Module (MOD) Status Indicator

This bi-color (green/red) LED provides device status. It indicates
whether or not the device has power and is operating properly.

Condition Status Indication

Off No power No power applied to device.

Green Device operational Device is operating in a normal

condition.

(1)

Flashing green

Device in standby
(device needs
commissioning)

(1)

Flashing red

Recoverable fault For example, the device’s scan list

Red Unrecoverable fault Device has an unrecoverable fault.

Device needs commissioning due to
configuration missing, incomplete, or
incorrect.

configuration does match the actual
network configuration.

Cycle power to your computer. If the
problem persists, the device may
need to be replaced.

Device self testing Device is in self test. Refer to the

DeviceNet Specification, Volume II,
Identity Object.

(1)

The flash rate of the LED is approximately 1 flash per second. The LED should be on for approximately 0.5
seconds and off for approximately 0.5 seconds.

Publication 2711P-UM004B-EN-P - March 2007

DeviceNet Overview 13

DeviceNet Network (NET) Status Indicator

This bi-color (green/red) LED indicates the status of the
communication link.

Condition Status Indication

Off Not powered Device is not online.

Not online The device has not completed the

Dup_MAC_ID test yet.

The device may not be powered; look
at the Module Status LED.

(1)

Flashing green

Green Link okay, online, connected The device is online and has

Flashing red

Red Critical link failure Failed communication device. The

Online Device is online, but has no

connections in the established state.

Not connected The device has passed the

Dup_MAC_ID test, is online, but has
no established connections to other
nodes.

connections in the established state.

(1)

Connection timeout One or more I/O connections are in

the timed-out state.

device has detected an error that has
rendered it incapable of
communicating on the network
(Duplicate MAC ID or Bus-off).

Check network integrity and
communication rate of all devices.
Then cycle power to the card by
shutting down and cycling power to
your computer.

(1)

The flash rate of the LED is approximately 1 flash per second. The LED should be on for approximately 0.5
seconds and off for approximately 0.5 seconds.

ATTENTION

Extensive use of change-of-state connections, particularly with
rapidly changing data, can adversely impact the available
DeviceNet network bandwidth. If the network bandwith
becomes consumed, some devices may only be able to
communicate intermittently. This can result in timeout errors
and possible loss of data. If timeouts occur, consider changing
the connection type for some of the change-of-state
connections to cyclic or polled.

Publication 2711P-UM004B-EN-P - March 2007

14 DeviceNet Overview

Publication 2711P-UM004B-EN-P - March 2007

Chapter

Configure the Terminal as a Slave Device

2

Chapter Objectives

Sample Network Configuration

The procedures in this chapter will show you how to configure a
PanelView Plus terminal to operate as a slave device on a DeviceNet
network. A ControlLogix processor with a 1756-DNB DeviceNet
module will scan inputs and outputs from the PanelView Plus
terminals.

You will learn how to:

• configure communications for the PanelView Plus terminal and
1756-DNB module using RSLinx Enterprise software in RSView
Studio software.

• create a DeviceNet configuration using RSNetWorx for
DeviceNet software.

• add the DeviceNet module I/O configuration to the ControlLogix
tag database using RSLogix 5000 software.

The example configures DeviceNet I/O messaging for a numeric input
and numeric output from a PanelView Plus terminal to a 1756-L63
ControlLogix processor, version 15.0.

• The PanelView Plus terminal has a network node address of 2.

• 1756-L63 ControlLogix processor, version 15.0, in slot 0

communicates via the 1756-DNB DeviceNet scanner module at
network node address 1 in slot 2.

1756-DNB Scanner

Node 2

L
6
3

PanelView Plus with
DeviceNet module

Ethernet
Network

RSLogix 5000 network
RSNetWorx network
RSView Studio network

15 Publication 2711P-UM004B-EN-P - March 2007

Node 1

E
N
B

T

D
N
B

DeviceNet
Cable

16 Configure the Terminal as a Slave Device

Configure Communications

After creating your Machine Edition application, you are ready to
configure communications using RSLinx Enterprise software.

1. Open RSView Studio software.

2. In the Application Explorer dialog, double-click RSLinx

Enterprise software to expand the tree.

3. Double-click Communication Setup.

4. If prompted, select Create a New Configuration and click Finish.

5. On the Local tab, right-click the 1789-A17 Backplane icon and

select Add Device.
This is the virtual backplane of the PanelView Plus or PanelView

Plus CE device.

Publication 2711P-UM004B-EN-P - March 2007

Configure the Terminal as a Slave Device 17

6. In the Add Device Selection dialog, select the communications

card appropriate for your terminal size and click OK.

• The correct card for the PanelView Plus 400 and 600 terminals
is 2711P-RN10C.

• The correct card for the PanelView Plus 700-1500 terminals is
2711P-RN10H.

7. Set the node address to 2, the communication rate to match the

1756-DNB DeviceNet module, and click OK.

The General tab of the DeviceNet Scanner Properties dialog
specifies the name, node address, virtual backplane slot, and
communication rate of the DeviceNet scanner. The virtual
backplane of the PanelView Plus has two slots. Because the
terminal resides in slot 0, the DeviceNet scanner is automatically
assigned to slot 1.

Publication 2711P-UM004B-EN-P - March 2007

18 Configure the Terminal as a Slave Device

Configure the Slave Inputs and Outputs

You are now ready to configure the slave inputs and outputs in the
PanelView Plus terminal. For the example used in this chapter, the
1756-DNB DeviceNet module will scan these inputs and outputs.

• One DINT or 4 bytes of input data

• One DINT or 4 bytes of output data

IMPORTANT

What differentiates the PanelView Plus terminal as a slave or a scanner
is the node you specify for each block of data. The device you
configure data for via the I/O Configuration tab is the slave on the
network. If the device node matches the node address for the
PanelView Plus terminal, then it will operate as a slave. In this
example, the node address is 2.

Typically these address blocks will be larger. Minimize the
number of address blocks going to a single device.

Definition of Inputs and Outputs

Inputs and outputs are in reference to the PanelView Plus DeviceNet
module and correspond to RSNetWorx terminology. In other words,
the output of a controller is an input to the PanelView Plus terminal.
RSView ME software can read inputs and outputs, but only write to
outputs configured in the PanelView Plus terminal.

Configure the Slave Input Data

Publication 2711P-UM004B-EN-P - March 2007

1. On the I/O Configuration tab, right-click the Input icon and

select Add Address Block.

Configure the Terminal as a Slave Device 19

2. In the Address Block Properties dialog, set the Start Byte to 0,

Length in Bytes to 4, and click OK.

The address block 0-3 Bytes is added under Inputs.

3. Right-click on the new address block 0-3 Bytes and select Add

Device to define the PanelView Plus terminal as the slave for the
input address block.

4. In the Device Properties dialog of the input address block, select

Node 2 and click OK.

Publication 2711P-UM004B-EN-P - March 2007

20 Configure the Terminal as a Slave Device

Because the device node is the same node as the PanelView
Plus terminal, Node 2 will operate as a slave for the input data.
The 1756-DNB scanner will scan this data.

A dimmed icon appears under the Input address block for
Device 02. This indicates the PanelView Plus terminal is the
slave.

Publication 2711P-UM004B-EN-P - March 2007

Configure the Terminal as a Slave Device 21

Create an Input Alias

To make connections to objects, aliases are required. You must create
an alias for the input address block. The aliases serve as the
connection reference you select in RSView Studio software.

1. Right-click the 0-3 Bytes icon and select Add Alias.

2. In the Alias Properties dialog, select these properties and click

OK to add the alias to the input address block:

• Alias Data Type = DINT

• Alias Name = Slave_Input

• Start Byte = 0

• Array Count = 1

Publication 2711P-UM004B-EN-P - March 2007

22 Configure the Terminal as a Slave Device

The Array Count lets you quickly configure multiple aliases with
the same prefix.

Swapping of bytes or words is necessary for some controllers
such as SLC controller. Refer to Help for more information.

The slave input is now configured with:

• Address length of 4 bytes, starting at byte 0

• Slave device at node 2, which is the PanelView Plus terminal

• Alias of Slave_Input for the input address block

Publication 2711P-UM004B-EN-P - March 2007

Configure the Terminal as a Slave Device 23

Configure the Slave Output Data

Follow the same procedure to add a slave output block to the I/O
configuration. The 1756-DNB DeviceNet scanner will scan this output.

1. On the I/O Configuration tab, right-click the Output icon and

select Add Address Block.

2. In the Address Block Properties dialog, set the Start Byte to 0,

Length in Bytes to 4, and click OK.

The address block 0-3 Bytes is added under Outputs.

Publication 2711P-UM004B-EN-P - March 2007