Sprecher+Schuh CEP7 DNENCAT, DNENCATR EtherNet/IP Communications Auxiliary User Manual

User Manual

CEP7 EtherNet/IP Communications Auxiliary

Catalog Number CEP7-DNENCAT, CEP7-DNENCATR

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://www.rockwellautomation.com/literature/ ) describes some important 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.

WARNING: 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.

ATTENTION: 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

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

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

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

Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

Table of Contents

Chapter 1

Installation & Wiring

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Network Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2

Configure the EtherNet/IP

Communications Auxiliary

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Determining Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting the IP Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

EtherNet/IP Node Address Selection Switches. . . . . . . . . . . . . . . . . . 16

Assign Network Parameters via the BOOTP/DHCP Utility. . . . . . . . . 17

Assign Network Parameters Via a Web Browser &

MAC Scanner Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Other Factors to Consider When Assigning Network Parameters 22

Duplicate IP Address Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Behavior of Modules With Duplicate IP Addresses . . . . . . . . . . . . . . 23

DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Electronic Data Sheet (EDS) File Installation. . . . . . . . . . . . . . . . . . . . . . . 23

Download the EDS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Register the EDS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3

Configure the DeviceNet

Network

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 4

Add Devices to the DeviceNet

Network

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

DeviceNet Node Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Node Address Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Set the Node Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Using the Hardware Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Using the DeviceNet Node Commissioning Tool . . . . . . . . . . . . . . . 37

Add DeviceNet Modules to the Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Simple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

User-Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 3

Table of Contents

4

Chapter 5

View & Configure Parameters

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

View & Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 6

Automatic Device Recovery or

Replace

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Setting ADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 7

Automation Controller

Communications

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Ethernet Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

I/O Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

ControlLogix Generic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 51

EtherNet/IP Generic Module Configuration . . . . . . . . . . . . . . . . . . . 53

Accessing Generic Module Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Logic Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 8

E-mail/Text

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

E-mail Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

E-mail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configure Device Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Text Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 9

Device Parameters

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Parameter Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Parameter Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 10

Troubleshooting

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

EtherNet/IP Modules of Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Power-Up Reset Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Specifications

EtherNet/IP & DeviceNet

Information

Table of Contents

Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Recoverable Error Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Unrecoverable Error Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Appendix A

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Appendix B

Electronic Data Sheet (EDS) Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Common Industrial Protocol (CIP) Objects. . . . . . . . . . . . . . . . . . . . . . . . 85

Identity Object — CLASS CODE 0x01. . . . . . . . . . . . . . . . . . . . . . . . 85

Message Router Object — CLASS CODE 0x02 . . . . . . . . . . . . . . . . 86

DeviceNet Object — CLASS CODE 0x03 . . . . . . . . . . . . . . . . . . . . . 87

Assembly Object — CLASS CODE 0x04 . . . . . . . . . . . . . . . . . . . . . . 87

Connection Manager Object — CLASS CODE 0x06 . . . . . . . . . . . 91

Parameter Object — CLASS CODE 0x0F . . . . . . . . . . . . . . . . . . . . . 92

Device Level Ring (DLR) Object — CLASS CODE 0x47 . . . . . . . 93

QoS Object — CLASS CODE 0x48 . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Non-Volatile Storage Object — CLASS CODE 0xA1. . . . . . . . . . . 94

Port Object — CLASS CODE 0x0F4. . . . . . . . . . . . . . . . . . . . . . . . . . 95

TCP/IP Interface Object — CLASS CODE 0xF5 . . . . . . . . . . . . . . 96

Ethernet Link Object — CLASS CODE 0xF6 . . . . . . . . . . . . . . . . . . 97

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 5

Table of Contents

6 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Introduction

Overview

Chapter

1

Installation & Wiring

The purpose of this chapter is to provide the necessary instructions to successfully install the CEP7 Ethernet™/IP Communications Auxiliary and properly connect it to an EtherNet/IP and DeviceNet™ network.

The CEP7 EtherNet/IP Communications Auxiliary is an EtherNet/IP to

DeviceNet linking device. It provides a means for devices that primarily communicate on a DeviceNet network (e.g., a CEP7 Overload Relay or a CET5

Electronic Overload Relay) to communicate to EtherNet/IP-based scanners. The

EtherNet/IP Communications Auxiliary allows up to six (6) DeviceNet-based devices to be scanned via Implicit Messaging and can bridge explicit messaging for all nodes on a DeviceNet network. The EtherNet/IP Communications

Auxiliary uses an internal web server to configure the module, the DeviceNet network, and DeviceNet-based devices that fully support the Parameter Object.

SHOCK HAZARD: To prevent electrical shock, disconnect the EtherNet/

IP Communications Auxiliary from its power source before installing or servicing. Install in suitable enclosure. Keep free from contaminants.

ATTENTION: The EtherNet/IP Communications Auxiliary contains ESD

(electrostatic discharge) sensitive parts and assemblies. Static control precautions are required when installing, testing, servicing, or repairing the EtherNet/IP Commuications Auxiliary. Component damage may result if ESD control procedures are not followed. If you are not familiar with static control procedures, refer to Rockwell Automation publication 8000-

4.5.2, “Guarding Against Electrostatic Damage”, or any other applicable

ESD protection handbook.

ATTENTION: The purpose of this document is to serve as a guide for proper installation. The National Electrical Code (NEC) and any other governing regional or local code will take precedence. Rockwell

Automation cannot assume responsibility for the compliance or proper installation of the EtherNet/IP Communications Auxiliary or associated equipment. A hazard of personal injury and/or equipment damage exists if codes are ignored during installation.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 7

Chapter 1

ATTENTION: An incorrectly applied or installed EtherNet/IP

Communications Auxiliary can result in damage to the components or reduction in product life. Wiring or application errors (e.g., supplying incorrect or inadequate supply voltage or operating/storing in excessive ambient temperatures) may result in malfunction of the product.

ATTENTION: Only personnel familiar with the EtherNet/IP

Communications Auxiliary and associated machinery should plan to install, set up, and maintain the system. Failure to comply may result in personal injury and/or equipment damage.

ATTENTION: This is a Class A product. In a domestic environment, this product may cause radio interference in which case the user may be required to take adequate measures.

ATTENTION: To remain compliant with UL/CSA Certifications, the

DeviceNet power supply must meet NEC Class 2 Requirements.

8 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Features

Installation

Chapter 1

Figure 1 - Features

Front View

Status

LEDs

Module

Ethernet/IP

Network

Activity

LEDs

Front Port Link

Rear Port Link

DeviceNet Network

Status LED

DeviceNet Connector

Side View

Top View

Ethernet Connectors

RJ-45

DIN

Rail Mounting

Rear View

Panel Mounting

Earth Ground Connector

The EtherNet/IP Communications Auxiliary may be DIN Rail or panel mounted. To avoid overheating, the unit must be mounted vertically and requires 37.4 mm (1-1/2 in.) of clearance at the top and bottom to allow proper air flow. The temperature ratings for the unit will be derated if not mounted in this manner.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 9

Chapter 1

Figure 2 - Installation

37.44 mm

(1-1/2 in.)

Front View

Wiring

37.44 mm

(1-1/2 in.)

The EtherNet/IP Communications Auxiliary can accept all forms of DeviceNet cable. However, DeviceNet shielded cable is recommended. The EtherNet/IP

Communications Auxiliary complies with the Open Device Vendors Association

(ODVA) DeviceNet compliance testing when the distance between end nodes is

100 m or less with 60 or fewer network drops.

Table 1 - Wire & Torque Specifications

Wire

1X

2X

Torque

24…12 AWG

24…16 AWG

5 lb.•in.

1X

2X

1X

2X

0.2…2.5 mm

2

0.25…1 mm

2

0.56 N•m

0.2…2.5 mm

2

0.2…1 mm 2

0.56 N•m

10 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 1

Figure 3 - Wiring Diagram

DNET (Black)

24V -

CAN L (Blue)

Shield

CAN H (White)

DNET (Red)

24V +

Dimensions

Earth Ground

ATTENTION: Use a shielded DeviceNet cable to comply with CISPR 22 and CISPR 24.

Figure 4 - Dimension Diagram

Dimensions are shown in millimeters (inches).

110.0

(4.33)

31.3

(1.23)

5.85

(0.23)

100.5

(3.95)

98.0

(3.86)

87.0

(3.43)

Ø 4.50

(0.16)

105.0

(4.13)

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 11

Chapter 1

Network Design

The EtherNet/IP Communications Auxiliary is available as a single Ethernet port

(Cat. No. CEP7-DNENCAT) and dual Ethernet port (Cat. No.

CEP7-DNENCATR) module that has RJ-45 ports to connect to Ethernet cable

CAT5 type or better . Both the CEP7-DNENCAT and CEP7-DNENCATR devices support a Star Ethernet topology in which all Ethernet nodes wire back to a central Ethernet switch, hub, or router as shown in Figure 5 on page 12 .

Figure 5 - Star Ethernet Topology

The Cat. No. CEP7-DNENCATR Module also supports a Ring Ethernet topology in which all Ethernet nodes are wired in series with one another until a

complete network ring is made as shown in Figure 6 on page 13

.

12 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Figure 6 - Ring Ethernet Topology

Chapter 1

The Cat. No. CEP7-DNENCATR Module supports Rockwell Automation’s

Device Level Ring (DLR) topology as a slave device in which the EtherNet/IP network will still continue to communicate in the event that one of the network chains is disrupted.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 13

Chapter 1

14 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter

2

Configure the EtherNet/IP Communications

Auxiliary

Introduction

Determining Network

Parameters

This chapter describes how to configure an EtherNet/IP Communications

Auxiliary to operate on an EtherNet/IP network.

When you first install an EtherNet/IP Communications Auxiliary, the module is

Dynamic Host Configuration Protocol (DHCP) enabled.

To operate an EtherNet/IP network, you must define these parameters.

Table 2 - EtherNet/IP Network Parameters

Network Parameter

IP Address

Subnet Mask

Gateway

Description

The IP address uniquely identifies the module. The IP address is in the form xxx.xxx.xxx.xxx where each xxx is a number from

0...255. Do not use the following IP addresses, as these are reserved values:

• 0.0.0.1...0.255.255.255

• 127.0.0.0...127.255.255.255

• 224.255.255.255...255.255.255.255

Subnet addressing is an extension of the IP address scheme that allows a site to use a single network ID for multiple physical networks. Routing outside of the site continues by dividing the IP address into a net ID and a host ID via the class. Inside a site, the subnet mask is used to redivide the IP address into a custom network ID portion and host ID portion.

NOTE: If you change the subnet mask of an alreadyconfigured module, you must cycle power to the module for the change to take effect.

A gateway connects individual physical networks into a system of networks. When a node needs to communicate with a node on another network, a gateway transfers the data between the two networks.

If DNS addressing is used or if the module is referenced via a host name in an

MSG instruction, the following parameters must be defined.

NOTE: Consult with your Ethernet network administrator to determine if these parameters need to be specified.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 15

Chapter 2

Table 3 - EtherNet/IP Network Parameters for DNS Addressing

Network Parameter

Host Name

Domain Name

Primary DNS Server Address

Secondary DNS Server Address

Description

A host name is part of a text address that identifies the module. The full text address of a module is:

host_name.domain_name.

A domain name is part of a text address that identifies the domain in which the module resides. The full text address of a module is: host_name.domain_name. The domain name has a

48-character limit.

This identifies any DNS servers used in the network. You must have a DNS server configured if you specify an SMTP server with a name. The DNS server converts the domain name or host name to an IP address that can be used by the network.

For more information on DNS addressing, refer to page 23

.

Setting the IP Network

Address

An EtherNet/IP Communications Auxiliary ships with DHCP enabled. You can set the network Internet Protocol (IP) address by using:

• the EtherNet/IP node address selection switches,

• a Bootstrap Protocol (BOOTP)/Dynamic Host Configuration Protocol

(DHCP) server (e.g., the Rockwell Automation BOOTP-DHCP Server

Utility, which is included with Rockwell Software’s RSLinx™ Classic software), OR

• a web browser and MAC scanner software.

EtherNet/IP Node Address Selection Switches

The EtherNet/IP Communications Auxiliary comes with three node address selection switches that allow the user to select the last octet for the IP address

192.168.1.xxx.

16 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 2

Figure 7 - Last Octet Selection x 100 Digit x 10 Digit x 1 Digit

EXAMPLE When the top dial is set to 1, the middle dial is set to 2, and the bottom dial is set to 3, the resulting IP address is: 192.168.1.123.

When the node address selection switches are set to a value greater than 255, the

IP address is set to DHCP Enabled or programmed for a static IP address.

Assign Network

Parameters via the BOOTP/

DHCP Utility

By default, the EtherNet/IP Communications Auxiliary is DHCP Enabled. The

BOOTP/DHCP utility is a standalone program that is located in the BOOTP-

DHCP Server folder accessed from the Start menu.

IMPORTANT Before starting the BOOTP/DHCP utility: Make sure you have the hardware MAC ID of the module, which is printed on the front of the

EtherNet/IP Communications Auxiliary. The MAC ID has a format similar to: 00-0b-db-14-55-35.

This utility recognizes DHCP-enabled devices and provides an interface to configure a static IP address for each device.

To assign network parameters via the BOOTP/DHCP utility, perform this procedure:

1.

Execute the BOOTP/DHCP software.

2.

Choose Tool

>Network Settings.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 17

Chapter 2

3.

If appropriate for the network, type the subnet mask, gateway address, primary/secondary server addresses, and domain name in their respective fields.

4.

Click OK.

The Request History panel displays the hardware addresses of modules issuing BOOTP or DHCP requests.

5.

Double-click the MAC address of the module to be configured.

NOTE: The MAC address is printed on the front of the EtherNet/IP Communications

Auxiliary. The format of the hardware address resembles:

00-0b-db-14-55-35

18 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 2

The New Entry window appears with the module’s Ethernet Address

(MAC).

6.

Type the IP address, host name, and a module description.

7.

Click OK.

8.

Cycle power to the module by removing and reapplying the DeviceNet connector.

9.

To permanently assign this configuration to the module: Select the module in the Relation List panel and click Disable BOOTP/DHCP.

When module power is cycled, it uses the assigned configuration and does not issue a DHCP request.

If you do not click Disable BOOTP/DHCP, on a power cycle, the module clears the current IP configuration and will again begin sending DHCP requests.

Assign Network

Parameters Via a Web

Browser & MAC Scanner

Software

In the event that a user does not have access to a DHCP software utility, a user can assign network parameters via a web browser (e.g., Microsoft® Internet

Explorer) and Media Access Control (MAC) scanner software (e.g., MAC

Scanner from Colasoft® - http://www.colasoft.com/ ). Follow these steps to configure the module using this method.

1.

Locate and identify the MAC ID printed on the label of the EtherNet/IP

Communications Auxiliary. This address has a format that is similar to:

00-0b-db-14-55-35

2.

Connect the EtherNet/IP Communications Auxiliary to the same wide area network (WAN) as your personal computer.

3.

Initiate the MAC scanner software.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 19

Chapter 2

4.

Select the appropriate subnet to scan for available MAC addresses.

5.

Scan the Subnet for all available MAC addresses.

6.

Identify the IP address assigned to the MAC ID of the EtherNet/IP

Communications Auxiliary. The IP address will have a format that is similar to 192.168.0.100.

7.

Open a web browser and type the IP address on the address line to view the internal web server of the EtherNet/IP Communications Auxiliary.

20

8.

Select Administration Settings>Network Configuration to change the IP address of the EtherNet/IP Communications Auxiliary to a static IP address.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 2

9.

The module will prompt the user for a User Name and Password. Type

“Administrator” as the user name, leave the password field blank, then click

OK.

10.

Assign the appropriate network settings per the recommendation of the network administrator for the network that this module will be communicating on and click Apply.

11.

Remove and reapply the DeviceNet connector to allow the communications changes to take affect.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 21

Chapter 2

Other Factors to Consider When Assigning Network Parameters

There are other factors to consider when assigning networks parameters, which include the:

• network isolation from or integration into the plant/enterprise network.

• network size.

For large networks, even isolated networks, it might be more convenient and safer to use a BOOTP/DHCP server rather than RSLinx software.

The BOOTP/DHCP server also limits the possibility of assigning duplicate IP addresses.

• company policies and procedures associated with plant floor network installation and maintenance.

• level of involvement by information technology personnel in plant floor network installation and maintenance.

• type of training offered to control engineers and maintenance personnel.

If the Rockwell Automation BOOTP or DHCP server is used in an uplinked subnet where an enterprise DHCP server exists, a module may get an address from the enterprise server before the Rockwell Automation utility even sees the module. In this case, disconnect the uplink to set the address and configure the module to retain its static address before reconnecting to the uplink. This is not a problem if you have node names configured in the module and leave DHCP enabled.

ATTENTION: The EtherNet/IP Communications Auxiliary must be assigned a fixed network address. The IP address of this module must not be dynamically provided. Failure to observe this precaution may result in unintended machine motion or loss of process control.

Duplicate IP Address

Detection

22

When you change the IP address or connect the module to an EtherNet/IP network, the module checks to make sure that the IP address assigned to this module does not match the address of any other network device. If the module determines that another device on the network with a matching IP address, the

EtherNet/IP port of the module goes into conflict mode where the Network

Status LED indicator is solid red.

To resolve this conflict, use the instructions below to change the IP address of the module. Then, cycle power to the module or reset the modules by disconnecting and then reconnecting the Ethernet cable.

Two modules could possibly detect a conflict simultaneously. If this occurs, perform this procedure.

1.

Remove the module with the incorrect IP address and correct its conflict.

2.

Cycle power or disconnect the Ethernet cable from the second module and reconnect it.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 2

Behavior of Modules With Duplicate IP Addresses

Devices in conflict over an IP address behave differently depending on whether connections have been established to either of the modules and whether both modules support duplicate IP address detection.

Table 4 - Device Conflict over Duplicate IP Addresses

If both modules support duplicate IP address detection, then the first started module uses and retains its IP address.

The other module will detect a conflict, give up the IP address and enter conflict mode.

both modules support duplicate IP address detection and are started at roughly the same time, one of the modules surrenders the IP address and enters conflict mode.

one module supports duplicate IP address detection and a second module does not, the second module generally keeps its IP address, regardless of which module first obtains the IP address.

The module that supports duplicate IP address detection will detect the conflict and give up the IP address.

DNS Addressing

To further qualify a module’s address, use DNS addressing to specify a host name for a module, which also includes specifying a domain name and DNS servers.

DNS addressing makes it possible to set up similar network structures and IP address sequences under different domains.

DNS addressing is only necessary if you refer to the module by host name, such as in path descriptions in MSG instructions.

To use DNS addressing, perform this procedure.

1.

Assign a host name to the module.

NOTE: Contact the network administrator ro have a host name assigned. Valid host names should be IEC-1131-3 compliant.

2.

Configure the module's parameters.

3.

In addition to the IP address, subnet mask, and gateway address, configure a host name for the module, domain name, and primary/secondary DNS server addresses.

Electronic Data Sheet (EDS)

File Installation

Before the EtherNet/IP Communications Auxiliary is configured to communicate on an EtherNet/IP network, it must be registered to the software that configures the network (e.g., Rockwell Automation RSLinx Classic and

RSNetWorx for EtherNet/IP software). A user registers the module by installing an EDS file. The EDS file for the EtherNet/IP Communications Auxiliary can be obtained from one of two locations:

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 23

Chapter 2

• embedded in the module OR

• the Sprecher+Schuh EDS file download website.

Download the EDS File

Embedded in the Module

The EDS file for the EtherNet/IP Communications Auxiliary is embedded within the module. After the IP address for the module has been configured, connect the module to same Ethernet network as a personal computer. Using a web browser on the personal computer, a user can download the EDS file using a web browser by following these steps:

1.

Type the IP address of the EtherNet/IP Communications Auxiliary on the address line of the web browser.

2.

Select EDS File link

3.

Click Save to save the EDS file to the personal computer.

24 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 2

From the EDS File Download Site

The EDS file for the EtherNet/IP Communications Auxiliary can also be downloaded from the Sprecher+Schuh EDS File download site. Using a web browser on the personal computer that is connected to the internet, a user can download the EDS file by following these steps:

1.

Type http://www.sprecherschuh.com/library/literature/ motorprotection/cep7gen2.html

on the address line of the web browser.

2.

Select “CEP7-DNENCATR and CEP7-DNENCAT Communication

EDS file” and download it according to the directions.

Register the EDS File

After the EDS file has been downloaded, a user will need to register the EDS file with the software that configures the EtherNet/IP network. The following example lists the steps needed to register an EDS file with Rockwell Automation’s

RSLinx Classic software.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 25

Chapter 2

1.

Start the EDS Hardware Installation Tool located at Start>Programs>

Rockwell Software>RSLinx Tools.

2.

Click Add to register a new device.

3.

Click the “Register a single file” radio button, then browse to the location where the EDS file is located. Click Next.

26 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

4.

Click Next to accept the installation test results.

Chapter 2

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 27

Chapter 2

5.

Click Next to accept the graphic image.

6.

Click Next to register the device.

28 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

7.

Click Finish to successfully register the module.

Chapter 2

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 29

Chapter 2

30 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Introduction

Configuration

Chapter

3

Configure the DeviceNet Network

The purpose of this chapter is to assist in configuring the DeviceNet Network with the EtherNet/IP Communications Auxiliary. A DeviceNet network can be configured using the internal web interface from the EtherNet/IP

Communications Auxiliary.

1.

From the web page, navigate to Scan List>Configuration>Advanced.

2.

If desired, change the baud rate using the DeviceNet Baud Rate pull-down menu. The default value of 125K for the DeviceNet network.

NOTE: Autobaud is not supported with this product.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 31

Chapter 3

3.

Type the size of the Scan List I/O Entry in the field.

The entry size determines the number of input and output bytes that the

EtherNet/IP Communications Auxiliary will scan from each of the scanned devices. The maximum Scan List I/O Entry Size supported is 50 bytes with the default value being 8 bytes.

NOTE: Auto Device Replacement (ADR) is discussed in Chapter 6 , Automatic Device

Recovery or Replace

.

4.

If necessary, adjust DNet IO Request Packet Interval (RPI) and DNet IO

Inhibit.

DNet IO RPI determines the time it takes for data to be requested; DNet

IO Inhibit is the time used on DeviceNet Change of State (COS) I/O.

Both of these parameters are measured in milliseconds.

NOTE: Electronic keying is implemented on all scan list entries. Electronic keys are captured when a scan list is configured form the EtherNet/IP Communications

Auxiliary webpage. The proper setting of the electronic keying becomes more important with ADR functions and replacing units in the network.

5.

Navigate to Scan List>Configuration>Scan List to change the DeviceNet node address of the EtherNet/IP Communcations Auxiliary.

32 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 3

6.

Change the DeviceNet network address to the appropriate node address, then click Save.

NOTE: Typically, DeviceNet scanners have the node address of 0.

7.

Click OK to finish changing the scanner DeviceNet network address.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 33

Chapter 3

34 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Introduction

DeviceNet Node

Addressing

Chapter

4

Add Devices to the DeviceNet Network

In this chapter, you will be able to assign an address to each DeviceNet module and configure the DeviceNet scanner to scan up to six modules.

Each module being added to the DeviceNet network must have a unique network mode address. A unique network node address can be created by using hardware devices (e.g., DIP and Selector Switches) or by the Node Commissioning tool from the internal web interface of the EtherNet/IP Communications Auxiliary.

The following chart shows the recommended node addresses.

Table 5 - Recommended Node Addresses

Assign this

Device:

Scanner

Any Device on the

Network

(except the scanner)

Computer Interface to the Network

New DeviceNet

Module

This

Node Address: Notes:

0 • For multiple scanners, assign the lowest addresses in sequence (0, 1...).

1...61

62

63

• Give the lower addresses to devices with 15 bytes or more of input or output data.

• Gaps between addresses are acceptable and have no effect on system performance. If the final layout of the system is not certain at this time, leave gaps between addresses to allow flexibility as the system is developed.

• If a computer is connected directly to the DeviceNet network, use address 62 for the computer. The reason for this is that many computer interface devices use 63 as the default address.

• The 1784-U2DN device can connect a computer directly to a DeviceNet network.

• To avoid conflict, always leave address 63 open. This is due to the following:

– most DeviceNet devices have a factory preset address of 63.

– leaving address 63 open allows for configuration of a new device.

– the auto-address recovery feature requires address

63 to be open.

• Some devices do not have switches or push buttons to set the address. Therefore, the device must first be connected to the network then software (e.g.,

RSNetworx for DeviceNet) must be used to change the address.

• If another device is already using address 63, an address conflict will occur and communication will not occur with the newly connected device.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 35

Chapter 4

Set the Node Address

Node Address Basics

• Verify the node address assigned to the new device.

• Prevent duplicate node address assignments.

– When connecting new DeviceNet modules with the Node

Commissioning tool from the EtherNet/IP Communications Auxiliary web interface, place one new DeviceNet module on the network at a time. Refer to “New DeviceNet Module” in

Table 5 on page 35

.

– If DIP or selector switches on hardware will be used, set the network node address for the device before connecting it to the network.

• Leave node address 63 open.

For more information about setting the node address for DeviceNet devices, refer to the Rockwell Automation Literature Library at: www.rockwellautomation.com/literature

Using the Hardware Mechanism

Many DeviceNet devices feature a hardware mechanism to set the network node address (e.g., a rotary switch or a push wheel switch). Use the following procedure to set the node address.

IMPORTANT Ensure each device’s node address set by the hardware mechanism matches the node address used in the DeviceNet network. Note that if the network node address is set higher than 63, the Ethernet /IP

Communications Auxiliary Node Commissioning tool can be used instead of the hardware mechanism.

IMPORTANT In order for the node address change to take effect, cycle the module’s power.

1.

Using Table 5 on page 35 as a guide, select a node address to apply to the

new device.

36 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 4

2.

Change the node address using the appropriate mechanism for the new device.

Mechanism

Rotary Switch

2

4

2

0

PGM

MSD

6

4

0

8

LSD

6

Push Wheel Switch

Procedure

Turn the rotary switch dials to the desired node address value.

Usually, a small, flathead screwdriver is needed to turn the dials.

Once the device is powered up, the rotary switch settings are recognized. If the set node address value needs to be changed, power down the device, turn the dials to the desired setting, then power up the device again.

Turn the push wheel to the desired node address value.

Using the DeviceNet Node Commissioning Tool

A device’s network node address can be set using the Node Commissioning Tool on the EtherNet/IP Communications Auxiliary web page. This tool uses the

Network Who to view the DeviceNet modules on the network.

Refer to the following guidelines when using the Network Commissioning tool.

• Only use this tool with an online DeviceNet network.

• Only use this tool when adding new devices to the network if :

– the new device does not feature a hardware mechanism to set the node address or

– the new device’s node address is set higher than 63.

NOTE: If the new device features a hardware mechanism and the node address is set at 63 or lower, the Network Commissioning tool does not change the device’s node address.

• Each time a new device is added to the DeviceNet network, the procedures beginning on

page 38 must

be performed.

• To avoid conflict with duplicate node addresses, due largely in part to modules having a factory node setting of 63, configure a module to the online DeviceNet network one a time.

• Record the node address for each device that is set by the Node

Commissioning Tool.

Complete the following steps to set a device’s node address using the Node

Commissioning Tool on the EtherNet/IP Communications Auxiliary web page.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 37

Chapter 4

1.

From the EtherNet/IP Communications Auxiliary web page, navigate to

Scan List>Configuration>Node Commissioning.

2.

Select the device where node address needs to be assigned. Once selected, the Current Settings aand New Settings areas are populated.

3.

Double-click the “Node address” field’s value. The value will be highlighted in blue.

38 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 4

4.

Using the keypad on the PC keyboard, change the network node address to the desired value. Ensure the desired value is not duplicating any other device’s node address, then click the Apply button.

5.

The following window will appear confirming a successful node address value change. Click OK.

6.

Verify the node address was changed to the desired value in the “New settings” section of the page. Note that the “Current settings” area will still display the old node address unitl the device is selected again from the

Network Who list.

7.

Repeat steps 1 through 6 until all new or additional devices are added to the DeviceNetwork.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 39

Chapter 4

Add DeviceNet Modules to the Scan List

After each DeviceNet device has been assigned a unique node address, up to six

DeviceNet devices can be added to the EtherNnet/IP Communications Auxiliary

DeviceNet scan list. The EtherNet/IP Communications Auxiliary provide two methods to configure the scan list, Simple and User-Defined.

Simple

1.

From the EtherNet/IP Communications Auxiliary web page, navigate to

Scan List>Configuration>Scan List. The EtherNet/IP Communications

Auxiliary will read the available DeviceNet modules on the DeviceNet network.

2.

Click Config. The lowest six DeviceNet node addresses will populate into the Scan List field on the right.

40 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 4

3.

Click OK to complete the configuration.

The DeviceNet scanner on the EtherNet/IP Communications Auxiliary will begin scanning the DeviceNet devices.

User-Defined

If there are more than six DeviceNet devices on the network, the user can select up to six DeviceNet devices to scan. Follow the steps below to select specific

DeviceNet devices for the scan list.

1.

From the EtherNet/IP Communications Auxiliary web page, navigate to

Scan List>Configuration>Scan List. The EtherNet/IP Communications

Auxiliary will read the available DeviceNet modules on the DeviceNet network.

2.

Select the DeviceNet device in the Network Who screen to be added to the Scan List. The >> button becomes highlighted.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 41

Chapter 4

3.

Click >> to move the selected device into the Scan List.

4.

Repeat steps 2 and 3 to add five additional DeviceNet devices.

5.

Click Save at the bottom right of the screen.

6.

Click OK to complete the scan list configuration.

42 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Introduction

View & Edit

Chapter

5

View & Configure Parameters

In this chapter, you will be able to view and configure parameters for a DeviceNet device that supports the full implementation of the Parameter Object.

The EtherNet/IP Commuications Auxiliary is able to view and configure parameters for a DeviceNet device that supports the full implementation of the

Parameter Object. Users can use the web interface to view and edit parameters for a DeviceNet Module in the scan list.

Follow the steps below to view and edit parameters using the web interface of the

EtherNet/IP Commuications Auxiliary.

1.

Navigate to Scan List>Configuration, then select the DeviceNet device folder to view or edit its parameters. The selected DeviceNet device folder will expand.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 43

Chapter 5

2.

Click on the Identity folder. The Identity tab will appear, providing information about the selected device.

3.

Click on the Parameter folder. Subfields for this folder will appear.

44 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 5

4.

Select a parameter group. A list of up to 15 parameters will be displayed. If more than 15 parameters are available, select the page number or use the navigation arrows to view the additional parameter screens.

TIP To increase the update rate of the data being displayed on the screen, lower the value in the “Seconds before refresh:” field.

5.

Select a parameter group that contains programmable parameters, then click the Edit button. The value options will appear.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 45

Chapter 5

6.

Click the down arrow on the pull-down boxes to adjust fixed values and/or enter numerical values in the fields without an arrow to adjust the values.

7.

Click Apply once all parameter edits have been completed. The EtherNet/

IP Communications Auxiliary will download the new parameter values to the device. A confirmation window will appear.

8.

Click OK.

9.

Continue editing the remaining parameters, if desired.

NOTE: If a DeviceNet module does not support the parameter object, the following window will appear:

46 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Introduction

Setting ADR

Chapter

6

Automatic Device Recovery or Replace

In this chapter, using the Automatic Device Recovery or Replace (ADR) will be explained. The use of this feature reduces downtime if a device needs to be replaced.

With ADR, there is no need for software tools to get a replacement device configured and online. The EtherNet/IP Communications Auxiliary automatically configures the replacement device if the device was listed in the scan list and the appropriate electronic keying was selected.

IMPORTANT Not all DeviceNet devices support ADR.

1.

Navigate to Scan List>Configuration>Advanced.

2.

Select the appropriate electronic keying for your DeviceNet network application.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 47

Chapter 6

By default, the Device Type, Vendor, and Product Code will be enabled.

Electronic keying will define how closely a replacement device must match a failed device before the EtherNet/IP Auxiliary reconfigures a module. If the new module does not match the criteria of one of the checked boxes, the ADR will not function and an ADR error will appear.

3.

Once the scan list and DeviceNet module programmable parameters have been configured, click Upload ADR Data.

The EtherNet/IP Communications Auxiliary will upload and store the configuration data from the modules in the scan list and a confirmation message will appear,

4.

Select Enable from the Auto Device Replace pull-down menu. This will enable the ADR.

48 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 6

5.

Click Save, then cycle power on the EtherNet/IP Communications

Auxiliary.

An ADR download is performed immediately before an I/O connection is allocated by the DeviceNet master.

If the download is unsuccessful, an “ADR Error” for the appropriate node will be reported in the corresponding “Scan List Entry Status Word”. If the electronic keys for the device at a given node address do not match the saved electronic keys, no ADR download will take place, an I/O connection will not be allocated, and a “Keying Mismatch” will be reported in the corresponding “Scan List Entry Status Word”.

A warning list will appear after enabling the ADR and a change has been made to the scan list.

AAR (Auto Address Recovery) is also supported by the EtherNet/IP

Communications Auxiliary. When the EtherNet/IP Communications Auxiliary

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 49

Chapter 6 detects a node is missing from the scan list and a module matching the electonic key is detected on node 63, the EtherNet/IP Communications Auxiliary will attempt to change the module’s network node address to that of the missing scan list node number. When successful, the EtherNet/IP Communications Auxiliary will download the ADR information to the module.

50 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter

7

Automation Controller Communications

Introduction

Ethernet Messaging

I/O Messaging

This chapter describes and gives examples of how each type of EtherNet/IP messaging, I/O messaging and Explicit messaging, is used.

The EtherNet/IP Communications Auxiliary supports two types of EtherNet/IP messaging.

• I/O Messaging — Used for deterministic EtherNet/IP communications with ControlLogix™, CompactLogix™, SoftLogix™, and EtherNet/IP scanners. Its primary use is to read and write I/O data for control purposes.

• Logic Explicit Messaging — Used for non-deterministic communications in which the data is not critical for control. Logic explicit messages have a lower priority compared to I/O messages and are used to read and write non-critical data.

RS Logix 5000™ software is used to configure I/O messaging between an automation controller and an EtherNet/IP Communications Auxiliary on an

EtherNet/IP network.

The following example provides the steps necessary to configure a Logix controller for I/O messaging.

ControlLogix Generic Configuration

An existing project can be used or a new project can be created to configure

EtherNet/IP I/O Messaging. To create a new project, perform the following steps.

1.

Select File>New from the RSLogix 5000.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 51

Chapter 7

2.

Select the controller type, chassis type, slot number, and project path.

Then, enter a name for the controller and click OK.

3.

Right-click the I/O Configuration folder, then select New Module. The

Select Module Type window will appear.

52 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 7

4.

Select the desired EtherNet/IP scanner module, then click OK.

5.

Enter the desired communication settings, then click Finish.

EtherNet/IP Generic Module Configuration

Once the Logix controller has been configured, the EtherNet/IP

Communications Auxiliary must be added to the I/O configuration.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 53

Chapter 7

1.

Place the program in offline mode.

2.

Right-click on the EtherNet/IP scanner within the I/O Configuration folder, then select New Module to open the Select Module Type window.

3.

Select Generic Ethernet Module, then click OK.

54 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 7

4.

Enter a name for the EtherNet/IP Communications Auxiliary. The name will create a tag in RSLogix 5000 that can be used to read and write data from the devices being scanned by the EtherNet/IP Communication

Auxiliary.

5.

Select Data-INT for the Comm Format. The Data-INT format wil l represent the data from the EtherNet/IP Communications Auxiliary as a field of 16-bit values.

6.

Set the Connection Parameters. I/O data is accessed using Input Instance

101 and Output Instance 100. The size of the input connection and the output connection shall correspond to the size of the chosen instance. The configuration assembly instance is 102.

NOTE: In this example, configuration data is not used. Thus, the data size is set to 0

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 55

Chapter 7

7.

Type the IP address of the EtherNet/IP Communications Auxiliary.

8.

Type the value for the time between each scan of the module. The recommended RPI time is 250 ms. Ensure that the Inhibit Module is not checked.

9.

Click OK to add the EtherNet/IP Communications Auxiliary to the I/O

Configuration in RSLogix 5000.

Accessing Generic Module Data

With both the ControlLogix controller and the EtherNet/IP network configured, the ControlLogix controller can exchange data with the EtherNet/IP

Communications Auxiliary.

1.

Go online, then switch the controller to Remote Run mode.

56 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 7

2.

Open the Controller Tags window.

3.

Select the Monitor Tags tab.

An array of input and output tags were generated for each of the six scanned devices. To control the output relays for the scanned device, use the output tags; to obtain diagnostic information from the scanned device, use the input tags.

The format of output data is shown in the table to follow.

Table 6 - Output Assembly — Instance 100

Byte Size Contents

Scan List I/O Size Data to be delivered to the first scan list entry.

Scan List I/O Size Data to be delivered to the second scan list entry.

Scan List I/O Size Data to be delivered to the third scan list entry.

Scan List I/O Size Data to be delivered to the fourth scan list entry.

Scan List I/O Size Data to be delivered to the fifthscan list entry.

Scan List I/O Size Data to be delivered to the sixth scan list entry.

The format of the input data is shown in the table to follow.

Table 7 - Input Assembly — Instance 101

Byte Size

4 bytes

2 bytes

2 bytes

2 bytes

2 bytes

2 bytes

2 bytes

Contents

Logix Status Word

DeviceNet Scanner Status (Parameter 1) See Table 9 on page 69

Scan List Entry 1 Status Word (Parameter 2) See

Scan List Entry 2 Status Word (Parameter 3) See

Scan List Entry 3 Status Word (Parameter 4) See

Scan List Entry 4 Status Word (Parameter 5) See

Scan List Entry 5 Status Word (Parameter 6) See

Table 10 on page 70

Table 11 on page 70

Table 12 on page 70

Table 13 on page 71

Table 14 on page 71

2 bytes

Scan List Entry 6 Status Word (Parameter 7) See Table 15 on page 71

Scan List I/O Size Produced I/O data from the first scan list entry.

Scan List I/O Size Produced I/O data from the second scan list entry.

Scan List I/O Size Produced I/O data from the third scan list entry.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 57

Chapter 7

Byte Size Contents

Scan List I/O Size Produced I/O data from the fourth scan list entry.

Scan List I/O Size Produced I/O data from the fifth scan list entry.

Scan List I/O Size Produced I/O data from the sixth scan list entry.

Scan List I/O Size Data Link 1 Data

2 bytes

2 bytes

: :

2 bytes

Data Link 2 Data

Data Link 3 Data

: :

Data Link 48 Data

Logic Explicit Messaging

CompactLogix, ControlLogix, and SoftLogix controllers can read and write specific information to and from DeviceNet modules on the same DeviceNet network through the EtherNet/IP Communications Auxiliary using Explicit

Messaging.

The following steps configure a ControlLogix explicit message using the MSG instruction to read diagnostic parameters from an CEP7 C5 Overload Relay.

1.

In an interger array named MSG_Read_Request, define the number of attributes to read and list the specific attribute numbers.

58

The MSG instruction will return in an integer array with the first integer representing the following information:

• number of attributes

• first attribute number being returned

• first attribute number data status

• first attribute data…

• last attribute number being returned

• last attribute number data status

• last attribute data

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 7

In the screen capture below, the user-defined structure listing the integers is being returned in this example.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 59

Chapter 7

2.

Set up the MSG instruction in the Configuration tab to read the list of attributes (Parameters Group) by configuring the following fields:

• Message Type: CIP Generic

• Service Type: Custom

• Service Code: 0x03 (hex)

• Class: 0x375 (hex)

• Instance: 1 (dec)

• Attribute: 0x00 (nex)

• Source Element: MSG_Read_Request [0]

• Source Length: 14 (bytes)

• Destination: MSG_Read_Data

3.

Set up the communications path in the Communications tab to read the data from the CEP7 Overload Relay located at Node 6 by configuring the communication path as “MotorStarter, 3, 6”.

NOTE: Motor Starter — the name of the EtherNet/IP Communications Auxiliary

3 — the port number of the DeviceNet Scanner of the EtherNet/IP

Communications Auxiliary.

6 — the node address of the CEP7 Overload Relay.

60 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 7

4.

Click OK. When finished, the MSG instruction will read the 25 parameters from the CEP7 Overload Relay and place the results into

MSG_Read_Data as shown below.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 61

Chapter 7

62 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter

8

E-mail/Text

Introduction

E-mail Notifications

This chapter describes e-mail notifications and how to configure an EtherNet/IP

Communications Auxiliary to send e-mail messages and text notifications for different communication events.

Events

Several communication events can trigger e-mail notifications. These events are fault conditions for the DeviceNet scan list and EtherNet/IP Communications

Auxiliary.

Fault Conditions for the DeviceNet Scan List

Minor Recoverable Major Unrecoverable Wrong Data Size Slave Init Error

Minor Unrecoverable Connection Timeout

Major Recoverable Keying Mismatch

No Such Device I/O Data Overflow

Frag/Idle Error Automatic Device

Replacement Error

Acknowledge Timeout

Fault Conditions for the EtherNet/IP Communications Auxiliary

On Line Global ADR Error In Idle Mode Duplicate Mac Error

Illegal Scan List Data No Scanner Messages Hardware Error Data Link Error

No Network Messages Transmit Failure Bus Off Error Non Volatile Storage Error

E-mail Contents

The subject and body contents in the e-mail message wil be created from the:

• type of trip or warning that is detected,

• device name,

• device description,

• device location, and

• contact information.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 63

Chapter 8

EXAMPLE E-mail Subject:

CEP7-DNENCATR Comms Aux has detected a fault

E-mail Body:

Fault Status:

Device Name: CEP7-DNENCATR Comms Aux

Device Description: Motor Starters

Device Location: Bay 6-U29

Contact Info: Contact Person [email protected]

The first word in the e-mail subject is the device name. If a device name is not configured, then the product name attribute from the identity object will be used.

E-mail Configuration

To be able to send an e-mail, the IP address ot the hostname of a Simple Mail

Transfer Protocol (SMTP) server must be configured and notifications must be selected. Follow these steps to configure an e-mail notification.

1.

In the web browser, type the IP address of the EtherNet/IP

Communications Auxiliary in the address bar, then press the enter key on the keyboard.

2.

Select Administrative Settings E-Mail Configuration. A login window will appear.

64 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 8

3.

Log in with the username “Administrator”, leave the password field blank, and click OK.

NOTE: If desired, a password can be set within the Administrative Settings tab.

4.

Type the information into the e-mail notification fields as stated below.

E-mail Recipient The e-mail address of the person who will receive the notifications.

E-Mail Sender The e-mail address from which the notification will be sent.

SMTP Server Consult with the network administrator for the SMTP server address.

SMTP Username Consult with the network administrator for the SMTP username.

SMTP Password Consult with the network administrator for the SMTP password.

SMTP Port Consult with the network administrator which SMTP port number to use. Port 25 is the most common SMTP port.

5.

Check the desired notification time, fault conditions, and local conditions to be included in notification e-mails to the recipient. These can be changed after the initial configurations.

6.

Click Apply Changes to save the configuration.

Configure Device Identity

The properties of the Device Identity populate the notification e-mail subject and e-mail body. To configure the Device Identity, perform the following steps.

1.

Select Administrative Settings>Device Identity.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 65

Chapter 8

2.

Type the Device Identity information into the fields as described below.

Device Name The name of the EtherNet/IP Communications Auxiliary.

Device Description The description of the EtherNet/IP Communications Auxiliary.

Device Location The location of the EtherNet/IP Communications Auxiliary.

Contact Information The contact information for the EtherNet/IP Communications

Auxiliary.

Device X Name The name of the DeviceNet device being scanned.

Device X Description The description of the DeviceNet device being scanned.

3.

Click Apply Changes to save the configuration.

Text Notifications

The EtherNet/IP Communications Auxiliary can send a text message to a wireless phone be e-mailing the wireless phone’s service provider. The format for the text message is provided by the service provider and looks similar to the example formats below.

AT&T™ 10-digit wireless phone [email protected]

Sprint® 10-digit wireless phone [email protected]

66 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 8

Multiple e-mail addresses can be entered into the E-mail Recipient field, separating each e-mail address with a semicolon (;). The E-mail Recipient field is limited to 255 characters.

EXAMPLE An EtherNet/IP Communications Auxiliary sending an e-mail and text message when a Communications Timeout event occurs:

Limitations

Based on the functionality of the EtherNet/IP Communications Auxiliary, there are some limitations on when the e-mails can be triggered.

• If two events occur at the same time, an e-mail will only be sent for the most significant error.

• If the device has been configured to send an e-mail for a lower prioritized event and this event occurs at the same time as a higher prioritized event for which the device has not been programmed to send an e-mail, an e-mail will not be sent for either event.

• The Clear e-mail will only be sent when all events have been cleared and an event e-mail has previously been sent.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 67

Chapter 8

68 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter

9

Device Parameters

Introduction

The EtherNet/IP Communications Auxiliary provides parameters to allow the user to view the status and configure the DeviceNet scanner with RSNetWorx for

DeviceNet if the user does not want to use the internal web server of the

EtherNet/IP Communications Auxiliary. The 14 available parameters are listed below.

Table 8 - Parameter List

1 Scanner Status

2 SL Entry 1 Status

3 SL Entry 2 Status

4 SL Entry 3 Status

5 SL Entry 4 Status

6 SL Entry 5 Status

7 SL Entry 6 Status

8 SL Entry Size

9 Device Keys

10 Scanlist Config

11 ADR Record

12 ADR Enable

13 DNet IO RPI

14 DNet IO Inhibit

Parameter Programming

IMPORTANT Parameter setting changes to the EtherNet/IP Communications Auxiliary take effect immediately even during a “running” status.

Parameter Listing

The details for each of the 14 available parameters are listed below.

Table 9 - Parameter 1 — Scanner Status

Description Access Rule Data Type Units

Value

Min.

Max. Default

Provides the status of the

Devicenet scanner.

Get WORD — 0 16383

0 On Line

1 Illegal Scan List

Bit

3 No Scanner Messages

4 Transmit Failure

2 No Network Messages 5 In Idle Mode

6 Initializing

7 Duplicate MAC Failure

8 Bus Off

0

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 69

Chapter 9

70

Table 10 - Parameter 2 — SL Entry 1 Status

Description

Provides the status of the first scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Table 11 - Parameter 3 — SL Entry 2 Status

Description

Provides the status of the second scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Table 12 - Parameter 4 — SL Entry 3 Status

Description

Provides the status of the third scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 9

Table 13 - Parameter 5 — SL Entry 4 Status

Description

Provides the status of the fourth scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Table 14 - Parameter 6 — SL Entry 5 Status

Description

Provides the status of the fifth scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Table 15 - Parameter 7 — SL Entry 6 Status

Description

Provides the status of the sixth scan list entry in the

DeviceNet scanner.

Access Rule Data Type Units

Get WORD —

0 On Line

1 Connection Timeout

2 Keying Mismatch

3 Wrong Data Size

Bit

4 No Such Device

5 Fragment Error

6 Slave Initialization Error

7 I/O Data Overflow

Min.

0

Value

Max. Default

2047

8 Device Went Idle

9

Automatic Device

Replacement Error

10 Acknoledgement Timeout

0

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 71

Chapter 9

72

Table 16 - Parameter 8 — SL Entry Size

Description

Defines the number of bytes to be scanned for I/O data from eacn DeviceNet Device.

Access Rule Data Type Units

Get/Set USIN T Bytes

Min.

Value

Max. Default

1 50 8

Table 17 - Parameter 9 — Device Keys

Description

Determines how electronic keying will be performed.

0 Device Type

1 Vendor

Access Rule Data Type

Get/Set USIN T

2 Product Code

Bit

3 Major Revision

Units

—

Min.

0

4 Minor Revision

5 Minor of Higher

Value

Max. Default

63 7

Table 18 - Parameter 10 — Scanlist Config

Description

Triggers the building of a new

DeviceNet scan list.

0 = Ready

1 = Build Scan List

Access Rule Data Type Units

Get/Set BOOL —

Table 19 - Parameter 11 — ADR Record

Min.

Value

Max. Default

0 1 0

Description

Triggers the recording of configuration parameters from devices in the DeviceNet scan list to be used for Automatic Device

Replacement.

0 = Ready

1 = Record Parameters

Access Rule Data Type Units

Value

Min. Max. Default

Get/Set BOOL — 0 1 0

Table 20 - Parameter 12 — ADR Enable

Access Rule Data Type Units

Value

Min. Max. Default Description

Enables Automatic Device

Replacement.

0 = Disable

1 = Enable

Get/Set BOOL — 0 1 0

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 9

Table 21 - Parameter 13 — DNet IO RPI

Description

Defines the requested packet interval rate in milliseconds used on DeviceNet Polled I/O messaging.

Access Rule Data Type Units

Value

Min. Max. Default

Get/Set WORD ms 2 1000 75

Table 22 - Parameter 14 — DNet IO Inhibit

Description

Defines the inhibit time in milliseconds used on DeviceNet

Change of State (COS) I/O messaging.

Access Rule Data Type Units

Value

Min. Max. Default

Get WORD ms 2 1000 1

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 73

Chapter 9

74 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter

10

Troubleshooting

Introduction

The purpose of this chapter is to assist in troubleshooting the EtherNet/IP

Communications Auxiliary.

SHOCK HAZARD: Servicing energized industrial control equipment can be hazardous. Electrical shock, burns, or unintential actuation of controlled industrial equipment may cause death or serious injury .For seafety of maintenance personnel as well as others who may be exposed to electrical hazards assicated with maintenance activities, follow local safety related work practices (e.g., the NFPS 70W; Part II, Electrical

Safety for Employee Workplaces, in the United States) when working on or near energized equipment. Maintenance personnel must be trained in the safety practices, procedures, and requirements that pertain to their respective job assignments. Do not work alone on energized equipment.

ATTENTION: Do not attempt to defat or override fault circuits. The cause of a fault indication must be determined and corrected before attempting operation. Failure to correct a control system or mechanical malfunction may result in personal injury and/or equipment damage due to uncontrolled machine system operation.

EtherNet/IP Modules of

Operation

The EtherNet/IP Communications Auxiliary has four EtherNet/IP modes of operation:

• Power-Up Reset Mode,

• Run Mode,

• Recoverable Error Mode, and

• Unrecoverable Error Mode.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 75

Chapter 10

76

Power-Up Reset Mode

Figure 8 - Status LEDs

Module Status (MS) LED

Ethernet/IP Network Status (NS) LED

Front Port Link Activity LED

Rear Port Link Activity LED

DeviceNet Network Status (NS) LED

During the Power-Up Reset Mode, the following procedure occurs.

1.

The various LEDs will cycle simultaneously.

• Module Status (MS) LED will flash green for approximately 0.25 seconds, flash red for another 0.25 seconds, then remain a solid green.

• EtherNet/IP Network Status (NS) LED will flash green for approximately 0.25 seconds, flash red for another 0.25 seconds, then not illuminate.

• Device Network Status (NS) LED will flash green for approximately

.25 seconds, flash red for another0 .25 seconds, then not illuminate.

The MS and both NS LEDs will then return to their standard illuminated state.

2.

The EtherNet/IP Communications Auxiliary will perform a duplicate IP address check to verify that another module is not assigned to the same IP address. If a duplicate IP address is detected on the network, the EtherNet/

IP NS LED illuminates to a solid red, the MS LED flashes red, and the

EtherNet/IP Communications Auxiliary enters the Recoverable Error

Mode.

3.

The EtherNet/IP Communications Auxiliary performs a duplicate MAC address check to verify that another module is not assigned to the same

MAC address. If a duplicate MAC address is detected on the DeviceNet network, the DeviceNet NS LED illuminates a solid red, the MS LED flashes red, and the EtherNet/IP Communications Auxiliary enters the

Recoverable Error Mode.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 10

4.

If the power-up or reset is successful, the overload relay will enter into Run

Mode.

Run Mode

In Run Mode, the EtherNet/IP Communications Auxiliary will:

• operate as a slave device to a master device on an EtherNet/IP network.

• operate as a master device and scan up to six slave devices on a DeviceNet network.

• accept messages from a master on the EtherNet/IP network.

• send response messages, COS messages, or CYCLIC messages to a master.

• support a Device Level Ring (DLR) for Catalog Number

CEP7-DNENCATR.

If a communication error is detected, the EtherNet/IP Communications

Auxiliary will either enter the Recoverable Error Mode or Unrecoverable Error

Mode.

Operating as a Slave Device to a Master Device

As stated, the EtherNet/IP Communications Auxiliary will operate as a slave device to a master device on an EtherNet/IP network in Run Mode. The

EtherNet/IP NS LED will flash green if there are no network connections established with an EtherNet/IP network master. When one or more connections are in the “established’ state, the EtherNet/IP NS LED will illuminate a solid green. When one or more connections are in the “timed out” state, the EtherNet/IP NS will flash red.

Operating as a Master Device

As also stated, the EtherNet/IP Communications Auxiliary will also operate as a master device and scan up to six slave devices on a DeviceNet network in Run

Mode. The DeviceNet NS LED will flash green if there are no connections established with a DeviceNet slave device. When one or more connections are in the “established” state, the DeviceNet NS LED will illumiate a solid green. When one or more connections are in the “timed out” state, the DeviceNet NS LED will flash red. If no slave devices are defined in the DeviceNet scan list, the MS LED will flash red.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 77

Chapter 10

Troubleshooting

Procedures

78

Recoverable Error Mode

In this mode, the EtherNet/IP Communications Auxiliary MS LED flashes red.

The device will respond to messages that are specified in offline mode recovery message protocol.

Error Type Description

Recoverable Duplicate IP address detected.

A device is not present on the DeviceNet scan list.

LED State

Flashing Red

Unrecoverable Error Mode

In this mode, the EtherNet/IP Communications Auxiliary MS LED illuminates a solid red. The device continues in this state as long as the device is powered.

Error Type Description

Unecoverable Power-up initialization failure.

Data communication error.

LED State

Solid Red

The following table identifies possible causes and corrective actions when troubleshooting EtherNet/IP related failures using the status LEDs.

Table 23 - Troubleshooting Procedures

Status LED

EtherNet/IP

Network Status

(NS)

Color

None

Green, Red,

Not Illuminated

Green

Green

Red

Red

State

—

Possible Cause

The EtherNet/IP

Communications Auxiliary is not receiving power.

Flashing

(once)

Normal

Flashing

Solid

Flashing

Solid

The EtherNet/IP

Communications Auxiliary is online, but with no connections established.

Normal operating state and the EtherNet/IP

Communications Auxiliary is allocated to a master.

One or more EtherNet/IP connections timed out.

Diagnostics test failed on power-up/reset. An internal fault exists.

Duplicate EtherNet/IP module address exists. Two modules cannot have the same address.

A fatal communication error occurred.

Corrective Action

Check the DeviceNet cable connections and verify that

24V DC exists between the red and black terminals.

This is a normal power-up sequence.

Check the EtherNet/IP master and its scan list for correct scanner configuraton.

No action is required.

Reset the EtherNet/IP master device.

Cycle power to the unit. If the fault still exists, replace the unit.

Change the IP address to a valid setting and reset the device.

Check Ethernet media for proper installation.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Chapter 10

Status LED

DeviceNet

Network Status

(NS)

Module Status

Link

Link (front)

Link (back)

Color

None

Green, Red,

Not Illuminated

Green

Green

Red

Red

None

Green, Red,

Not Illuminated

Green

Green

Red

Red

None

Green

Green

State

—

Possible Cause

The EtherNet/IP

Communications Auxiliary is not receiving power.

Flashing

(once)

Normal

Flashing

Solid

Flashing

Solid

—

The EtherNet/IP

Communications Auxiliary is not configured to scan any

DeviceNet slave devices.

Normal operating state and the EtherNet/IP

Communications Auxiliary is scanning DeviceNet slave devices.

One or more DeviceNet connections timed out.

Diagnostics test failed on power-up/reset. An internal fault exists.

Duplicate DeviceNet module address exists. Two modules cannot have the same address.

A fatal communication error occurred.

The EtherNet/IP

Communications Auxiliary is not receiving power.

Corrective Action

Check the DeviceNet cable connections and verify that

24V DC exists between the red and black terminals.

This is a normal power-up sequence.

Check the DeviceNet scan list for the correct scanner configuration.

No action is required.

Reset the EtherNet/IP

Communications Auxiliary.

Cycle power to the unit. If the fault still exists, replace the unit.

Change the MAC address to a valid setting and reset the device.

Check DeviceNet media for proper installation.

Check the DeviceNet cable connections and verify that

24V DC exists between the red and black terminals.

This is a normal power-up sequence.

Check the Ethernet scan list for the correct scanner configuration.

Flashing

(once)

Normal

Flashing

Solid

Flashing

Solid

The EtherNet/IP

Communications Auxiliary is proper;y scanning DeviceNet slave devices, but it is not being scanned by the

EtherNet/IP master.

Normal operating state, the

EtherNet/IP Communications

Auxiliary is scanning

DeviceNet slave devices, and is allocated to its master.

One or more DeviceNet or

EtherNet/IP connections timed out.

The EtherNet/IP

Communications Auxiliary is not configured to scan any

DeviceNet slave devices.

Diagnostics test failed on power-up/reset.

—

Flashing

Solid

No action is required.

Reset the EtherNet/IP

Communications Auxiliary.

Check the DeviceNet scan list for correct scanner configuration.

The EtherNet/IP

Communications Auxiliary is not properly connected to an

Ethernet network.

The Ethernet network is properly connected.

Communications are occurring on the Ethernet network.

Cycle power to the device. If the fault still exists, replace the device.

Check the Ethernet cabling to make sure it is properly installed.

No action is required.

No action is required.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 79

Chapter 10

80 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Specifications

Appendix

A

Specifications

Table 24 - Ratings

Terminal Ratings

Terminal Screw

Wire Cross Section

Torque

Degree of Protection

Power Supply Ratings

Rated Supply Voltage U s

Rated Operating Range U e

Rated Supply Current I e

Maximum Surge Current at Power-Up

Maximum Power Consumption

Environmental Ratings

Ambient Temperature T amb

Storage

Operating

(Open)

(Enclosed)

Humidity

Operating

Damp Heat - Steady State

Damp Heat - Cyclic

Cooling Method

Vibration (per IEC 68-2-6)

Shock (per IEC 68-2-27)

Maximum Altitude

Pollution Environment

Terminal Marking

Degree of Protection

M3

See wiring diagram section

0.56…0.79 N•m (5…7 lb.•in.)

IP20

24V DC

24V -15%, +10% DC

100 mA at 24V DC

6.4 A

2.1 W

-40…+85 °C (-40…+185 °F)

-20…+60 °C (-4…+140 °F)

-20…+40 °C (-4…+104 °F)

5…95% non-condensing per IEC 68-2-3 per IEC 68-2-30

Natural Convection

3 G

30 G

2000 m

Pollution Degree 2

EN 50012

IP20

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 81

Appendix A

82

Table 25 - Electromagnetic Compatibility

Electromagnetic Compatibility

Electrostatic Discharge Immunity

Test Level

Performance Criteria

RF Immunity

Test Level

8 kV Air Discharge

4 kV Contact Discharge

B ➊➋

10V/m — 80 MHz…1 GHz

3V/m — 1.4 GHz…2 GHz

1V/m — 2 GHz…2.7 GHz

B ➊➋ Performance Criteria

Electrical Fast Transient/Burst Immunity

Test Level

Performance Criteria

Surge Immunity

Test Level

2 kV (Power Protective Earth)

1 kV (control bus cable)

B ➊➋

1 kV L-L (bus cable)

Performance Criteria

Radiated Emissions

B ➊➋

Class A

Conducted Emissions Class A

➊ Performance Criteria B requires the DUT (device under test) not to experience degradation or loss of performance.

➋

Environment 2 - Heavy Industrial.

WARNING: This is a class A product. In domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures.

Table 26 - Ethernet IP Communcations

EtherNet/IP Communications

Total Connections Supported

TCP

CIP

Total CIP Unconnected Messages Supported

CIP Class 1 Connection Consumed

Packet Rates (packets/second)

I/O

HIM/MSG

Media Support

Twisted Pair

Fiber

Speed Duplex (Half/Full)

Duplicate IP Detection

150

47

128

1

500

500

Yes

No

10/100

Yes

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Table 27 - Standards & Certifications

Standards and Certifications

UL 508

CSA 22.2, No. 14

EN 60947-4-1

Appendix A

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 83

Appendix A

84 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix

B

EtherNet/IP & DeviceNet Information

Electronic Data Sheet (EDS)

Files

EDS files are specially formatted ASCII files that provide all of the information necessary for a configuration tool (e.g., RSNetWorx for EtherNet/IP) to access and alter the parameters of a device. The EDS file contains all the parameter information of a device: number of parameters, groupings, parameter name, min, max, and default values, units, data format and scaling. The EDS file for the

EtherNet/IP Communications Auxiliary is available from the Internet at http:// www.sprecherschuh.com/library/literature/motorprotection/cep7gen2.html

. It can also be obtained from the EtherNet/IP Communications Auxiliary’s internal web page.

Common Industrial Protocol

(CIP) Objects

The following CIP object classes are supported.

Table 28 - CIP Object Classes

Class Object

0x01

0x02

0x03

Identity

Message Router

DeviceNet

0x04 Assembly

0x05 Connection

0x06

0x0F

Connection Manager

Parameter

X

0x47 Device Level Ring Object

0x48 Q05 Object

0xA1 Non-Volatile Storage Object X

0xF4 Port Object X

X

X

X

X

EtherNet/IP DeviceNet

X X

X X

X

X

X

X

X

X

0xF5 TCP/IP Interface

0xF6 Ethernet Link

X

X

Identity Object — CLASS CODE 0x01

The following class attributes are supported for the Identity Object.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 85

Appendix B

86

Table 29 - Identity Object Class Attributes

Attribute ID

1

2

Access Rule

Get

Get

Name

Revision

Max. Instance

Data Type

UINT

UINT

Identity Object instances contain the following instance attributes.

Table 30 - Identity Object Instance Attributes

Value

0x0001

0x00011

Attribute ID Access Rule Name

4

5

6

7

8

1

2

3

Get

Get

Get

Get

Get

Get

Get

Get

Vendor ID

Device Type

Status

Data Type

UINT

UINT

Product Code UINT

Major Revision USINT

Minor Revision USINT

WORD

Value

12

220 for CEP7-DNENCAT

221 for CEP7-DNENCATR

1

1

Bit 0: Owned, shall be set when at least one connection i configured

Bit 2: Configured

Bit 8: Minor Recoverable fault

BIt 9: Minor Unrecoverable fault

Bit 10: Major Recoverable fault

Bit 11: Major Unrecoverable fault

Serial Number UDINT Unique number assigned for each device

Product Name SHORT_STRING Product name

State USINT 3=Operational

The following common services are implemented for the Identity Object.

Table 31 - Identity Object Common Services

Service Code

0x01

0x0E

0x05

Class

No

Yes

No

Implemented for:

Instance

Yes

Yes

Yes

Service Name

Get Attribute All

Get Attribute Single

Reset

Message Router Object — CLASS CODE 0x02

No class or instance attributes are supported. The message router object exists only to route explicit messages to other objects.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

DeviceNet Object — CLASS CODE 0x03

The following class attributes will be supported for the DeviceNet Object.

Table 32 - DeviceNet Object Class Attributes

Attribute ID

1

Access Rule

Get

Name

Revision

Data Type

UINT

Value

2

A single instance of the DeviceNet Object will be supported by the following attributes.

Table 33 - Single Instance of the DeviceNet Object

Attribute ID

1

2

13

Access Rule

Get/Set

Get/Set

Get

Name

Node Address

Baud Rate

Active Node

Table

Data Type

USINT

USINT

Array of BOOL

[64]

Value

0-63

0=125K

1=250K

2=500K

Identifies which nodes are online on the local network based on the node address.

The following services will be implemented for the DeviceNet Object.

Table 34 - DeviceNet Object Common Services

Service Code

0x0E

0x10

Class

Yes

No

Implemented for:

Instance

Yes

Yes

Service Name

Get Attribute Single

Set Attribute Single

Assembly Object — CLASS CODE 0x04

The following class attributes are supported for the Assembly Object.

Table 35 - Assembly Object Class Attributes

Attribute ID Access Rule Name

2 Get

Data Type Value

Max. Instance UINT 120

Instance Attributes

Instances/Connection points implements the following data attributes.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 87

Appendix B

88

Byte Size

4 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

2 Bytes

2 Bytes

2 Bytes

: : : :

2 Bytes

Table 36 - Instance Attributes

# Access Name Type Value Description

3 Get/Set Data Array of UINT — Data produced/consumed by the module

Output Assemblies

The following output assembly instances are implemented.

Table 37 - Instance 100

Byte Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Input Assemblies

Table 38 - Instance 101

Contents

Data to be delivered to the first scan list entry.

Data to be delivered to the second scan list entry.

Data to be delivered to the third scan list entry.

Data to be delivered to the fourth scan list entry.

Data to be delivered to the fifth scan list entry.

Data to be delivered to the sixth scan list entry.

Contents

Logix Status Word

DeviceNet Scanner Status (Parameter 1) See Table 9 on page 69

Scan List Entry 1 Status Word (Parameter 2) See Table 10 on page 70

Scan List Entry 2 Status Word (Parameter 3) See Table 11 on page 70

Scan List Entry 3 Status Word (Parameter 4) See Table 12 on page 70

Scan List Entry 4 Status Word (Parameter 5) See Table 13 on page 71

Scan List Entry 5 Status Word (Parameter 6) See Table 14 on page 71

Scan List Entry 6 Status Word (Parameter 7) See Table 15 on page 71

Data to be delivered to the first scan list entry.

Data to be delivered to the second scan list entry.

Data to be delivered to the third scan list entry.

Data to be delivered to the fourth scan list entry.

Data to be delivered to the fifth scan list entry.

Data to be delivered to the sixth scan list entry.

DataLink 1 Data

DataLink 2 Data

DataLink 3 Data

: : : :

Data Link 48 Data

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

Table 39 - Instance 103 ➊

Byte Size

4 Bytes

4 Bytes

4 Bytes

4 Bytes

4 Bytes

4 Bytes

4 Bytes

4 Bytes

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

Contents

Logix Status Word

DeviceNet Scanner Status (Parameter 1) See Table 9 on page 69

Scan List Entry 1 Status Word (Parameter 2) See Table 10 on page 70

Scan List Entry 2 Status Word (Parameter 3) See Table 11 on page 70

Scan List Entry 3 Status Word (Parameter 4) See Table 12 on page 70

Scan List Entry 4 Status Word (Parameter 5) See Table 13 on page 71

Scan List Entry 5 Status Word (Parameter 6) See Table 14 on page 71

Scan List Entry 6 Status Word (Parameter 7) See Table 15 on page 71

Data to be delivered to the first scan list entry.

Data to be delivered to the second scan list entry.

Data to be delivered to the third scan list entry.

Scan List I/O Size

Scan List I/O Size

Scan List I/O Size

2 Bytes

2 Bytes

2 Bytes

: : : :

Data to be delivered to the fourth scan list entry.

Data to be delivered to the fifth scan list entry.

Data to be delivered to the sixth scan list entry.

DataLink 1 Data

DataLink 2 Data

DataLink 3 Data

: : : :

2 Bytes Data Link 48 Data

➊ Available with firmware v 2.00 and higher.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 89

Appendix B

Configuration Assembly

Table 40 - Instance 102 (Revision 1)

Byte Size

2 Bytes

2 Bytes

2 Bytes

1 Byte

2 Bytes

1 Byte

2 Bytes

1 Byte

2 Bytes

1 Byte

2 Bytes

1 Byte

2 Bytes

1 Byte

2 Bytes

: : : :

1 Byte

2 Bytes

Contents

Revision = 1

ScanList I/O Size

Data Link Update Interval (ms)

Data Link 1 Node

Data Link 1 Parameter

Data Link 2 Node

Data Link 2 Parameter

Data Link 3 Node

Data Link 3 Parameter

Data Link 4 Node

Data Link 4 Parameter

Data Link 5 Node

Data Link 5 Parameter

Data Link 6 Node

Data Link 6 Parameter

: : : :

Data Link 48 Node

Data Link 48 Parameter

90 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

Table 41 - Instance 102 (Revision 2)➊

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

Byte Size

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

2 Bytes

: : : :

2 Bytes Data Link 48 Node

2 Bytes Data Link 48 Parameter

➊ Available with firmware v 2.00 and higher.

Contents

Revision = 2

ScanList I/O Size

Data Link Update Interval (ms)

Reserved

Data Link 1 Node

Data Link 1 Parameter

Data Link 2 Node

Data Link 2 Parameter

Data Link 3 Node

Data Link 3 Parameter

Data Link 4 Node

Data Link 4 Parameter

Data Link 5 Node

Data Link 5 Parameter

Data Link 6 Node

Data Link 6 Parameter

: : : :

2 Bytes

The following services are implemented for the Assembly Object.

Table 42 - Ethernet Object Common Services

Service Code

0x0E

0x10

Implemented for:

Class Instance Consuming Instance Producing

Yes

No

Yes

Yes

Yes

No

Service Name

Get Attribute Single

Set Attribute Single

Connection Manager Object — CLASS CODE 0x06

No class or instance attributes are supported.

The following common service are implemented for the Connection Manager

Object.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 91

Appendix B

92

Table 43 - Connection Manager Object Common Services

Implemented for:

Instance

Yes

Yes

Yes

Service Name

Forward Open

Forward Close

Unconnected Send

Parameter Object — CLASS CODE 0x0F

The following class attributes are supported for the Parameter Object.

Table 44 - Parameter Object Class Attributes

2

8

Attribute ID Access Rule Name

1 Get Revision

Get

Get

Max Instance

Data Type Value

UINT

UINT

Parameter Class Descriptor WORD

0x0001

0x0029

0x000B

The following instance attributes are implemented for all parameter attributes.

Table 45 - Parameter Object Instance Attributes

Attribute ID Access Rule Name

1

14

15

12

13

16

17

10

11

8

9

6

7

4

5

2

3

Get/Set

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Get

Value

Link Path Size

Link Path

Data Type

Specified in Descriptor

USINT

Packed EPATH:

Value

N/A

Path to specified object attribute

Descriptor

Data Type

Data Size

Parameter Name

String

WORD

EPATH

USINT

SHORT_STRING

Units String

Help String

SHORT_STRING

SHORT_STRING

Minimum Value Specified in Descriptor

Maximum Value Specified in Descriptor

Default Value Specified in Descriptor

Scaling Multiplier UINT

Scaling Divisor

Scaling Base

UINT

UINT

Scaling Offset

Multiplier Link

INT

UINT

Parameter

Dependent

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

Attribute ID Access Rule Name

18

19

Get

Get

Divisor Link

Base Link

20

21

Get

Get

Data Type

UINT

UINT

Offset Link UINT

Decimal Precision USINT

Value

Parameter Dependent

The following commons services are implemented for the Parameter Object.

Table 46 - Parameter Object Common Services

Service Code

0x01

0x0E

0x10

0x4B

Implemented for:

Class Instance

No

Yes

Yes

Yes

No

No

Yes

Yes

Service Name

Get Attribute All

Get Attribute Single

Set Attribute Single

Get Enum String

Device Level Ring (DLR) Object — CLASS CODE 0x47

No class attributes will be supported for the DLR object. A single instance

(Instance 1) will be supported.

Table 47 - DLR Object Single Instance

Attributes ID Access Rule Name

1

2

10

12

Get

Get

Get

Get

Network Topology USINT

Network Status

Data Type

USINT

Value

0=Linear

1=Ring

0=Normal

1=Ring Fault

2=Unexpected Loop Detect

3=Partial Network Fault

4=Rapid Fault/Restore Cycle

Active Supervisor

Address

Structure of UDINT; array of 6 USINT

Capability Flags DWORD

Ring Supervisor

0x00000002

The following common services will be implemented for the DLR object.

Table 48 - DLR Object Common Services

Service Code

0x01

0x0E

Implemented for:

Class Instance

No

No

Yes

Yes

Service Name

Get_Attributes_All

Get_Attribute_Single

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 93

Appendix B

94

QoS Object — CLASS CODE 0x48

The following class attributes will be supported for the QoS object.

Table 49 - QoS Object Class Attributes

Attribute ID Access Rule Name Data Type Value

1 Get Revision UINT 1

A single instance (Instance 1) will be supported.

Table 50 - QoS Object Instance

6

7

8

4

5

Attribute ID Access Rule Name

1 Set

Data Type Value

802: 1Q Tag Enable USINT 0=Disable (default)

1=Enable

Set

Set

DSCP Urgent

DSCP Schedule

USINT

USINT

Default=55

Default=47

Set

Set

Set

DSCP High

DSCP Low

DSCP Explicit

USINT

USINT

USINT

Default=43

Default=31

Default=27

The following common services will be implemented for the QoS object.

Table 51 - QoS Object Common Services

Service Code

0x0E

0x10

Implemented for:

Class Instance

Yes

No

Yes

Yes

Service Name

Get_Attribute_Single

Set_Attribute_Single

Non-Volatile Storage Object — CLASS CODE 0xA1

The following instances of the Non-Volatile Storage object will be supported.

Table 52 - Non-Volatile Storage Object Instances

2

3

NVS Object Instance Entity to be Updated

1 EtherNet/IP Module Application Code

EtherNet/IP Module Boot Code

EtherNet/IP Module FPGA Image

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

Port Object — CLASS CODE 0x0F4

The Port object supports the following class attributes.

Table 53 - Port Object Class Attributes

2

3

Attribute ID Access Rule Name

1 Get Revision

8

Get

Get

Get

Max. Instance

Num. Instances UINT

Entry Port

Data Type

UINT

UINT

UINT

Port Instance Info Array of

Structure of

Value

1

2

2

1

1

9 Get

Port Type

Port Number

UINT

UINT

Two instances of the Port object will be supported. Instance 1 will represent the

EtherNet/IP port and Instance 2 will represent the DeviceNet port.

Table 54 - Port Object Instances

Attribute ID Access Rule Name

1 Get Port Type

2 Get Port Number

Link Object

3

4

5

7

8

Get

Get

Get

Get

Get

Path Length

Link Path

Port Name

Port Type Name

Data Type

UINT

UINT

Struct of

Value

Inst 1=4; Inst 2=5

UINT

Padded EPATH

Short String Inst 1=”Port A”;

Inst 2=”Port B”

Short String Inst 1=”EtherNet/IP”;

Inst 2=”DeviceNet”

Node Address

Port Node Range

Padded EPATH

Struct of

Min. Node Number UINT

Max. Node Number UINT

This attribute is implemented for Inst 2 only.

The following services will be implemented.

Table 55 - Port Object Services

Service Code

0x01

0x0E

Implemented for:

Class Instance

Yes

Yes

Yes

Yes

Service Name

Get_Attributes_All

Get_Attribute_Single

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 95

Appendix B

96

TCP/IP Interface Object — CLASS CODE 0xF5

The TCP/IP object supports the following class.

Table 56 - TCP/IP Object Class

Attribute ID Access Rule Name Data Type Value

1 Get Revision UINT 3

For single port devices, one instance of the TCP/IP interface object is supported.

For dual port devices, two instances of the TCP/IP interface object are supported.

Table 57 - TCP/IP Object Class Instances

Value

6

8

Attribute ID Access Rule Name

1 Get Status

2 Get

3 Get/Set

Configuration

Capability

Configuration

Control

4 Get Physical

Link Object

Data Type

DWORD

DWORD

DWORD

5 Get/Set Interface

Configuration

Struct of:

UINT

Padded

EPATH

Struct of:

UDINT

UDINT

UDINT

UDINT

UDINT

STRING

Get/Set

Get/Set

Host Name

TTL Value

STRING

USINT

9 Get/Set Multicast

Config

Struct of:

USINT

USINT

UINT

UDINT

0x00000014

0=Configuration from NVS

2=Configuration from DHCP

For a single port device: 2 words

20 F6 24 01 (ENet Link Object Inst 1)

For dual port device: NULL

IP Address

Network Mask

Gateway Address

Primary DNS

Secondary DNS

Default domain name for not fully qualified host names

Time to live value for EtherNet/IP multicast packets

Allocation Control

Reserved

Number of multicast addresses to allocate (1-4)

Multicast starting address

The following common services are implemented for the TCP/IP interface object.

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Appendix B

Table 58 - TCP/IP Interface Object Common Services

Service Code

0x01

0x0E

0x10

Implemented for:

Class Instance

No

Yes

No

Yes

Yes

Yes

Service Name

Get_Attributes_All

Get_Attribute_Single

Set_Attribute_Single

Ethernet Link Object — CLASS CODE 0xF6

The following class attributes are supported for the Ethernet Link object.

Table 59 - Ethernet Link Object Class Attributes

Attribute ID Access Rule Name Data Type Value

1 Get Revision UINT 1

The following one instance of the Ethernet Link object is supported.

Table 60 - Ethernet Link Object Instance

2

3

Attribute ID Access Rule Name

1 Get Interface Speed

4

Get

Get

Get

Interface Flags

Data Type

UDINT

DWORD

Physical Address ARRAY of 6 USINTs

5 Get

Interface Counters Struct of:

In Octets

In Ucast Packets

In NUcast Packets

In Discards

In Errors

In Unknown Protos

Out Octects

Out Ucast Packets

Out NUcast Packets

Out Discards

Out Errors

Media Encounters Struct of:

Alignment Errors

FCS Errors

Single Collisions

SQE Test Errors

Deferred Transmits

Late Collisions

Excessive Collisions

MAC Transmit Errors

Carrier Sense Errors

Frame Too Long

MAC Receive Errors

Value

10 or 100 Mbit/sec

See ENet/IP Spec

MAC Address

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 97

Appendix B

7

8

10

Attribute ID Access Rule Name

6 Get/Set Interface Control

Data Type

Struct of:

Control Bits

Forced Interface Speed

Get

Get

Get

Interface Type

Interface State

Interface Label

USINT

USINT

SHORT_STRING

Value

Instance 1: Port 1

Instance 2: Port 2

The following common services are implemented for the Ethernet Link object.

Table 61 - Ethernet Link Object Common Services

Service Code

0x0E

0x10

Implemented for:

Class Instance

No

Yes

No

Yes

Yes

Yes

Service Name

Get_Attributes_All

Get_Attribute_Single

Set_Attribute_Single

98 Rockwell Automation Publication CEP7-UM014B-EN-P December 2011

Rockwell Automation Publication CEP7-UM014B-EN-P December 2011 100

Supercedes Publication CEP7-UM014A-EN-P - July 2011 Copyright © 2011 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.