ControlEdge EtherNetIP User Guide RTDOC-X548-en-151A · 2018. 12. 6. · ControlEdgePLC...

ControlEdge PLC

EtherNet/IP User's Guide

RTDOC-X548-en-151A

November 2018

Release 151

ControlEdge PLC

DISCLAIMERThis document contains Honeywell proprietary information.Information contained herein is to be used solely for the purposesubmitted, and no part of this document or its contents shall bereproduced, published, or disclosed to a third party without theexpress permission of Honeywell International Sàrl.

While this information is presented in good faith and believed to beaccurate, Honeywell disclaims the implied warranties ofmerchantability and fitness for a purpose and makes no expresswarranties except as may be stated in its written agreement with andfor its customer.

In no event is Honeywell liable to anyone for any direct, special, orconsequential damages. The information and specifications in thisdocument are subject to change without notice.

Copyright 2018 - Honeywell International Sàrl

2

3

CONTENTSContents 3About this guide 5Chapter 2 - Overview 9Chapter 3 - Planning and Designing EtherNet/IP 11

Tested EtherNet/IP devices 11

EtherNet/IP implementation architecture and topology 12

Device Level Ring (DLR) by ETAP 13

STAR with Stratix switch or MOXA switch 14

Liner (Broken Ring) on Non-redundant CPM 17

Common network for multiple CPM 17

Network usage guidelines and recommendations 19

Chapter 4 - Configuration 21Configuring EtherNet/IP Client 22

Binding EtherNet/IP Client to an Ethernet port 23

Registering Electronic Data Sheets (EDS) files 24

Configuring EtherNet/IP devices using EDS files 27

Configuring generic EtherNet/IP devices 33

Scaling support for generic device 35

Configuring communication with third-party controllers 36

Configuring communication with C300/UOC 36

Configuring communication with ControlLogix controllers 37

Configuring EtherNet/IP Server 38

Binding EtherNet/IP Server to an Ethernet port 38

Selecting EtherNet/IP for variables 38

Chapter 5 - EtherNet/IP I/O Behavior during switchover 41Chapter 6 - Diagnostic 43

Viewing EtherNet/IP device diagnostics 43

EtherNet/IP device error codes 45

Contents

Appendix A - Status codes 49Notices 50

4

Contents

CHAPTER

1 ABOUT THIS GUIDEThis document provides an overview of the use of EtherNet/IP™communication with ControlEdge™ 900 Controller and offerspractical guidance to perform a successful integration of EtherNet/IPwith ControlEdge 900 Controller.

Revision history

Revision Date Description

A November 2018 Initial release of this document

Intended audience

This documentation is intended for the following audience: Users whoplan, install, configure, operate, or maintain ControlEdge™ 900controllers running the eCLR (IEC 61131-3) execution environment.

Prerequisite skills

Knowledge of SCADA systems and experience of working in aMicrosoft Windows environment are required.

Introduction to ControlEdge Technology

Item Description

ControlEdge PLC ControlEdge 900 controllers running the eCLR (IEC 61131-3) execution environment with PLC software optionsconfigured with ControlEdge Builder.

ControlEdge RTU ControlEdge 2020 controllers running the eCLR (IEC 61131-3) execution environment with RTU software optionsconfigured with ControlEdge Builder.

ControlEdge UOC ControlEdge 900 controllers running the Honeywell controlexecution environment (CEE) configured with ExperionControl Builder.

5

Special terms

The following table describes some commonly used industry-wideand Honeywell-specific terminology:

Terminology Description

Adapter A communication device which connects to the EtherNet/IPnetwork to serve data from a set of devices or modulesunderneath it. Adapter typically supports I/O connectivity fromScanners via implicit EtherNet/IP connections.

Assembly A set of data passed between a Originator and a Target after animplicit I/O connection has been established on an EtherNet/IPnetwork.

CIP Common Industrial Protocol

EDS Electronic Data Sheet. A text file which specifies all the propertiesof an EtherNet/IP device necessary for a Scanner module tocommunicate with it. EDS files my be used in the first step ofcreating an I/O module or device type for interfacing to anEtherNet/IP device.

IP Internet Protocol

Originator Originator is the controller that initiate any data exchange withEtherNet/IP devices on the EtherNet/IP network.

RPI Requested Packet Interval. The repetitive interval by whichassemblies are periodically transported over EtherNet/IP I/Oconnections between Producer and Consumer.

Scanner A device which connects to the EtherNet/IP network to act as aclient of other EtherNet/IP connected devices. ControlEdge 900Controller acts as EtherNet/IP Scanner. It connects to andexchanges data with Adapters of Modular IO stations, directlyconnected devices and Rockwell AB ControLogix controllers.

Target Target is the EtherNet/IP device that address any data requestsgenerated by the controller.

TCP Transport Control Protocol

UDP User Datagram Protocol

ODVA Open DeviceNet Vendors Association

6

About this guide

7

Related documents

The following list identifies publications that may contain informationrelevant to the information in this document.

n ControlEdge Builder Software Installation User’s Guide

n ControlEdge Builder Software Change Notice

n ControlEdge PLC and ControlEdge RTU Getting started

n ControlEdge Builder User’s Guide

n ControlEdge 900 Platform Hardware Planning and InstallationGuide

n ControlEdge Builder Function and Function Block ConfigurationReference Guide

n ControlEdge Builder Protocol Configuration Reference Guide

n ControlEdge PLC and ControlEdge RTU Network and SecurityPlanning Guide

About this guide

8

About this guide

CHAPTER

2 OVERVIEWEtherNet/IP™ (Ethernet industrial protocol) is an application layerprotocol for industrial automation applications. It uses all thetransport and control protocols used in traditional Ethernet includingthe Transport Control Protocol (TCP), the User Datagram Protocol(UDP), the Internet Protocol (IP) and the media access and signalingtechnologies found in off-the-shelf Ethernet interfaces and devices. Itallows the user to address a broad spectrum of process control needsusing a single technology.

EtherNet/IP is currently managed by the Open DeviceNet VendorsAssociation (ODVA). EtherNet/IP is the name given to the CommonIndustrial Protocol (CIP™), as implemented over standard Ethernet(IEEE 802.3 and the TCP/IP UDP protocol suite). CIP encompasses acomprehensive suite of messages and services for a variety ofmanufacturing automation applications, including control, safety,synchronization, motion, configuration and information.

ControlEdge PLC supports comprehensive integration betweenControlEdge 900 controllers and compatible devices installed on anEtherNet/IP network. An EtherNet/IP enabled ControlEdge 900controller can communicate with EtherNet/IP compliant devicesconnected on EtherNet/IP networks. Data accessed from EtherNet/IPdevices (reads and writes) can be used for control and indication.

ControlEdge Builder provides options to create new device types forthe supported EtherNet/IP compatible devices. To enable easyintegration between ControlEdge 900 Controller and third-partycontrollers, ControlEdge Builder also provides a set of function blocksfor the communication between controllers.

9

10

Chapter 2 - Overview

CHAPTER

3 PLANNING AND DESIGNING ETHERNET/IPThe following sections provide more information to help you plan anddesign an EtherNet/IP interface for the integration betweenControlEdge 900 Controller and the EtherNet/IP compatible devices:

n EtherNet/IP implementation architecture and topology

n Network usage guidelines and recommendations

Tested EtherNet/IP devices The following table lists the tested EtherNet/IP compliant devices:

Device category Device name Vendor Revision

Adapter + I/O module Turck BL20-E-GW-EN, adaptor Turck 2.7

BL20-E-4IOL Turck 2.7

BL20-2RFID-S Turck 2.7

BL20-S4T-SBBS Turck 2.7

BL20-PF-24VDC-D Turck 2.7

BL20-P3T-SBB Turck 2.7

BL20-BR-24VDC-D Turck 2.7

BL20-4DO-24VDC-0.5A-P Turck 2.7

BL20-S4T-SBCS Turck 2.7

BL20-4DI-24VDC-P Turck 2.7

BL20-2AIH-I Turck 2.7

BL20-2AOH-I Turck 2.7

BL20-4DI-NAMUR Turck 2.7

BL20-2DO-R-CO Turck 2.7

BL20-E-2CNT-2PWM Turck 2.7

Drive Rockwell PowerFlex 525 RockwellAutomation

N/A

11

Device category Device name Vendor Revision

Rockwell PowerFlex 753 RockwellAutomation

N/A

YASKAWA V1000 YASKAWA N/A

Remote I/O FEN20-16DXP Turck 2.7

FEN20-4DI-4DXP Turck 2.7

1732E-OF4 RockwellAutomation

1.006

Rockwell ArmorBlock 1732E-16CFGM12P5QCR

RockwellAutomation

1.14

Turck BLCEN-4M12MT-4AI4AO-VI

Turck 2.5

TBEN-L5-16DIP Turck 2.7

Turck TBEN-L5-16DOP Turck 2.7

Turck PBEN-L4-8DIDO Turck 2.7

ATTENTION: You can also add and configure other EtherNet/IPcompliant devices and modules, but these devices and modulesmust be qualified and validated by yourself. After that, youshould test functions for devices. If any questions, you cancontact Honeywell representatives.

EtherNet/IP implementation architecture andtopology

EtherNet/IP can be used to communicate between ControlEdge 900controller and the EtherNet/IP compatible third-party devices, suchas I/Os, drives, and relays.

Supported EtherNet/IP topologies

The EtherNet/IP-I/O devices, drives, and relays can be set up in one ofthe following network topologies:

n Device Level Ring (DLR) topology - The nodes of the network areconnected in a circular mode, forming a ring.

n Linear bus topology - Nodes are connected in a linear array, with a

12

Chapter 3 - Planning and Designing EtherNet/IP

13

single cable hop from one device to the next.

n Star topology - The nodes of the network are connected to acentral hub.

The topology can also be a hybrid setup with a combination of star,linear bus, and ring topologies.

A Device-level ring topology is recommended because it provides anetwork that is single-fault tolerant.

In an EtherNet/IP implementation setup, the ring network includesthe following components:

n EtherNet/IP compatible I/O devices, drives, and relays

n Ring supervisor

n ETAP modules for single port devices

n MOXA, Stratix 5700 or Stratix 8000 switches

The Ring supervisor is an important component on the ring networkbecause it is used as the connection media between the EtherNet/IP-compatible devices and the stratix switch. Only one node (ETAP orstratix switch) in the Device Level Ring topology can be configured asan active ring supervisor.

The stratix 5700/8000 switch is capable of playing Ring Supervisorrole and can be a node on the ring.

The 1783-ETAP modules are also used to connect single-port deviceson the ring and linear bus network.

Device Level Ring (DLR) by ETAP

NOTE: ETAP is required for the Device Level Ring topology. It canbe configured using Rockwell RSLogix software, refer to thevendor's document for more information.

NOTE: Stratix switches which support the Device Level Ringtopology should be configured. Refer to the vendor's documentfor how to configure the switch.

You must follow the rule below for Device Level Ring topology:

n Configure CPM downlink network topology as “STAR” (and Rotaryswitch on EPM is setting as 4).


n Do not connect non-DLR devices directly to the network. Non-DLRdevices must be connected to the network through 1783-ETAP.

STAR with Stratix switch or MOXA switchYou must follow the rule below for Star topology:

n Only use ETH3 to connect to Stratix or MOXA switch withEtherNet/IP devices.

n Tested switches include MOXA, Stratix 5700 and Stratix 8000.

n Inter-connection with more switches for port expanding isallowed.

n Single EPM or EtherNet/IP device failed won’t impact otherdevices operation.

n Maximum two network devices are allowed to be connectedbetween CPM and EPM including switch and Fiber opticalconvertor.

14


15

Figure 3-1: Star with Moxa switch


Figure 3-2: Star with Stratix 5700

16


17

Liner (Broken Ring) on Non-redundant CPM

n This topology applies to small projects and simple connection.

n It supports single port EtherNet/IP devices by ETAP and dual portdevices.

Common network for multiple CPM

n All EtherNet/IP devices connected with different CPMs can beconnected under the same network.

n Each device (EPM or EtherNet/IP device) only can be owned by aunique host (CPM). Not support owned by multiple controllers(except redundant controller).

n You must avoid IP conflict on each devices.

n Common network topology support both Device Level Ring andSTAR.


Figure 3-3: Downlink as Client through MOXA dual STAR

18


19

Figure 3-4: Downlink as Client through STRATIX for Device Level Ring

Network usage guidelines andrecommendations

Consider the guidelines and recommendations in the following table.

Guideline/Recommendation Explanation

Do not configure a supervisor (ETAP orstratix switch) on a linear network.

If your linear network includes non-DLRnodes and has a supervisor-enabled nodeon the network, it will impactcommunication to non-DLR devicesconnected to the linear network.

Connect switches to a DLR network via1783-ETAP.

If switches are connected to the DLRnetwork without a 1783-ETAP, thenetwork will experience unpredictablebehavior.

Run all nodes on the DLR network at 100 These configuration values provide the


Guideline/Recommendation Explanation

Mbps and in Full-duplex mode. best performance for your network.

Additionally, we recommend the following:

l Use auto-negotiate for all nodes on theDLR network.

l Do not use auto-negotiate on onenode and then force speed on the nextnode linked to it.

Do not physically close a DLR networkwithout a supervisor configured on thenetwork.

A DLR network without a supervisor noderesults in a network storm.

If you do close the DLR network without asupervisor configured, break the ring andconfigure at least one supervisor beforephysically reconnecting the network.

20


CHAPTER

4 CONFIGURATIONThe following table lists workflows for different scenarios.Task Go to

Configure EtherNet/IP Client Configure EtherNet/IP devices with EDS file:

1. See "Binding EtherNet/IP Client to anEthernet port" on page 23 for moreinformation.

2. See "Registering Electronic Data Sheets(EDS) files" on page 24 for moreinformation.

3. See "Configuring EtherNet/IP devicesusing EDS files" on page 27 for moreinformation.

If you do not have the EDS file, you canconfigure generic EtherNet/IP devices:

1. See "Binding EtherNet/IP Client to anEthernet port" on page 23 for moreinformation.

2. See "Configuring generic EtherNet/IPdevices" on page 33 for more information.

Configure EtherNet/IP Server 1. See "Binding EtherNet/IP Server to anEthernet port" on page 38 for moreinformation.

2. See "Selecting EtherNet/IP for variables"on page 38 for more information.

Configure communication withC300/UOC

When ControlEdge 900 controllercommunicates with C300/UOC, it acts as anEtherNet/IP Server. Only User-defined datatype STRUCT is supported for communicatingwith C300/UOC.

1. See "Binding EtherNet/IP Server to anEthernet port" on page 38 for moreinformation.

21

Task Go to

2. Declare a STRUCT data type. See"Configuring communication withC300/UOC" on page 36 for moreinformation.

3. Configure the target variable data type asthe STRUCT data type.


Configure communication withControlLogix controllers

If ControlEdge 900 controller acts as anEtherNet/IP client:

ControlEdge Builder provides function blocksto enable the communication, see"EtherNetIP" in the ControlEdge BuilderFunction and Function Block ConfigurationReference.

If ControlEdge 900 controller acts as anEtherNet/IP server, user-defined data typesare not supported. See "Configuringcommunication with ControlLogixcontrollers" on page 37 for more information.

1. See "Binding EtherNet/IP Server to anEthernet port" on page 38 for moreinformation.


Configuring EtherNet/IP ClientThe ControlEdge 900 controller supports communication withEtherNet/IP compliant third-party devices, such as I/O modules,drives, and relays. To facilitate the integration of PLC with theEtherNet/IP compliant devices, you must add and configureequivalent devices by using ControlEdge Builder. Each configureddevice represents an equivalent physical EtherNet/IP compliant-device, which is installed on the EtherNet/IP network.

To enable communication between I/O modules and the EtherNet/IPnetwork, an adapter is needed. The adapter provides the Assembly

22

Chapter 4 - Configuration

23

connection feature, which helps you in consolidating connectionsfrom a group of I/O modules.

You can create EtherNet/IP device, drive, and I/O module types byusing Electronic Data Sheets (EDS) files. Or if you do not have theEDS file, you can create a generic EtherNet/IP device.

Binding EtherNet/IP Client to an Ethernet portThis section introduces how to bind EtherNet/IP Client protocol toETH3.

ETH4 has the same configuration as ETH3, so only ETH3 should beconfigured manually.

Star topology is required if you bind EtherNet/IP Client.

To bind EtherNet/IP Client

1. From Home Page, click Configure Ethernet Ports and select ETH3.

2. Under Network Setting, configure the IP address and the subnetmask.

l The default IP address is 172.168.0.101.

l The range of the IP address is from 101 to 254.

l The IP address cannot be in the same network subnet as ETH1and ETH2.

l The IP address must be in the same network subnet as theEtherNet/IP device.

l The IP address cannot be conflict with the IP address ofEtherNet/IP device.

l The IP address cannot be conflict with the EPM IP address.

3. Under Protocol Binding, select EtherNet/IP Client.

4. Under I/O Network Topology, Star Topology is selected automatically.This configuration should match the position of 100X switch onthe EPM hardware. For more information about the switch, see“Assembling I/O racks” in the ControlEdge 900 ControllerHardware Planning and Installation Guide.

5. Click Save to complete the Ethernet port configuration.

6. Click Back to return to the Home Page.


Registering Electronic Data Sheets (EDS) filesEDS files are used to create EtherNet/IP device types or I/O moduletypes for communication with EtherNet/IP devices or I/O modules. Toenable the communication between I/O modules and the EtherNet/IPnetwork, you should register EDS files of I/O modules.

You can download EDS files from the third party vendor and registerthem into the Device Type list. The registered information will bestored under the location: C:\ProgramData\Honeywell\ControlEdgeBuilder\EDSFiles. The registered information cannot be saved alongwith project backups, you must back up them manually.

If you want to modify EDS files, you can access EZ EDS tool fromODVA official website: https://www.odva.org/software/EZ-EDS-Download. For how to modify EDS file, check the online helpembedded in the EZ EDS tool.

Prerequisites

n If you want to create the EtherNet/IP device types, or I/O moduletypes by using the EDS, ensure that you have the appropriate EDSfile.

n Ensure that you have all the required device-related specifications,which are available with the device, before you create the device,or I/O module type.

To register EDS files

1. From the Home Page, click Configure EtherNet/IP Devices > RegisterEDS Files, and click Register EDS File.

2. Enter a Device Type Name. The device type name cannot begin withnumbers and cannot contain any spaces and special characters.

3. Select Device Type according the type of the physical EtherNet/IPdevice.If a device supports both Input and Output channels, then selectOutput here. For example, a device has analog input and analogoutput, then select Analog Output.If a device supports neither Input nor Output channels, then selectGeneric Device here.

4. When you register an EDS file for an I/O module, indicate whetherthe I/O module requires an associated adapter or not. If the I/Omodule requires an adapter, select the Needs Adapter box.

24


25

NOTE: In a scenario where multiple I/O modules share asingle communication adapter to communicate with anEtherNet/IP protocol, the Needs Adapter must be selected.When you select Needs Adapter, the device type is onlyavailable on the I/O Configuration tab when you create orcustomize a generic EtherNet/IP Adapter.

NOTE: You cannot change this setting after compiling theproject. You must remove the device type from bothControlEdge Configuration Workspace and IECProgramming Workspace, and re-add a device type.

5. Click Select File, browse to the location stored the target EDS file,select the EDS file and click Open.

6. You can view the basic information of the EDS file at the bottompanel. You can also click View EDS to open the EDS file to viewmore details.

NOTE: The EDS file is read-only and not allowed to modify.

7. Select the boxes for the following Assembly types accordingdevices types:


l InputAn assembly transfers data from an EtherNet/IP device asProducer device to a controller as Consumer.

l OutputAn assembly transfers data from a controller as Producerdevice to an EtherNet/IP device as Consumer.

l ConfigurationAn assembly which transports configuration data from theEtherNet/IP device originating the connection to theEtherNet/IP device or IO module which is the target of theconnection.

NOTE: There might be more than one Input, Output andConfiguration assembly types. However, ensure that youselect one instance of Input, one instance of Output, andone instance of Configuration assembly type per yourrequirement.

8. Click OK to import the EDS file to ControlEdge Builder. Devicetypes are created and grouped by different vendors automaticallybased on the "vendor" information in the EDS file.

9. Click the vendor name to expand the group, and select the targetdevice type, you can view General, Configuration Assembly, InputAssembly and Output Assembly information.

10. You can click the Delete icon to remove the device type. You can

26


27

also click the View EDS File icon to view more information of theEDS file.

11. Click Save to complete the configuration.After saving, the new device type will be populated in the Data Typelibrary with an input and and output channel in IEC ProgrammingWorkspace. You can use the created device type from the library toconfigure new devices.

Configuring EtherNet/IP devices using EDS filesPrerequisites

n Ensure you have imported the EDS file of the EtherNet/IP deviceinto ControlEdge Builder. See "Registering Electronic Data Sheets(EDS) files" on page 24 for more information.

n The following information in the EDS file are critical for devicetype creation. Ensure that these details are available before usingthe EDS file.

l Device and Vendor information

l Parameter information

l Assembly information

l Connection information

n Bind EtherNet/IP Client to an Ethernet port. See "BindingEtherNet/IP Client to an Ethernet port" on page 23 for moreinformation.

To configure a device using an EDS file, without an adapter

1. From the Home Page, click Configure EtherNet/IP Devices >Configure Devices, and click Add Device.

2. Click Select Device Type, all available device types are displayed.


You can enter keywords to search EDS files, and also can filterthem by selecting from the various filters for the Vendor andCategory fields.

3. Select the target device type, and enter the Device Name andDescription. The device name cannot begin with numbers andcannot contain any spaces and special characters.

4. Click OK to add the device.

5. In the General tab, configure the following parameters.

Parameter Description

IP Address The IP address of the EtherNet/IPdevice which is provided by thevendor.

Originator to Target RPI(ms)

Requested Packet Interval (RPI)specifies the rate at which data isupdated during a connection.

Set the rate for initiating the dateexchange with the EtherNet/IP device.

Target to Originator RPI(ms)

Set the rate for reading data from theEtherNet/IP device.

Electronic Keying It is used to control if accept theconnection when the identityinformation of EDS file does notmatch the EtherNet/IP device.

28


29


l Disable Keying: Allow theconnection with EtherNet/IP deviceeven the identity information ofEDS file and the EtherNet/IP deviceare not match.

l Exact Match: The identityinformation of EDS file must matchthe EtherNet/IP device, and thenthe connection will be allowed.

6. Click Configuration tab to configure parameters which are definedby the corresponding EDS file. Configure them according vendor'sdocuments.

7. In the Configuration tab, you can also do the following options ifrequired:

l Click Change Device Type to re-select a device type.

l Click Clear Device Type to remove the device type.

8. You can click to edit the device name and description. You can

also click to remove the device if required.

9. Click Save to complete the configuration.


To configure a device using an EDS file, associated with an adapter


2. Select Create or Customize EtherNet/IP Device, and select GenericEtherNet/IP Adapter.

3. Enter the Number of Slots ranging from 1 to 64.

ATTENTION: An attempt to communicate with the I/Omodule fails if the number of slots entered does not matchthe physical configuration. Therefore, ensure that thenumber of slots matches the number of the physicallyinstalled I/O modules and the adapter (number of slots =number of I/O modules + one for the adapter). For example,if the number of I/O modules is 7, the number of slotsshould be 8.

4. Enter the Device Name and Description. The device name cannotbegin with numbers and cannot contain any spaces and specialcharacters.




IP Address The IP address of theEtherNet/IP device.

30


31


Apply RPI settings on all associatedI/O modules

Select the checkbox, theRPI specified is applicablefor all the I/O modulesassociated to the adapter.

If you do not select thisoption, you shouldconfigure the RPI for everyI/O modules separately inthe I/O Configuration tab.

Originator to Target RPI (ms) RPI specifies the rate atwhich data is updatedduring a connection.

Set the rate for initiatingthe date exchange with theEtherNet/IP device.

It is applicable for all theI/O modules associated tothe adapter if the Apply RPIsettings on all associated I/Omodules option is selected.

It is un-configurable if theApply RPI settings on allassociated I/O modulesoption is not selected.

Target to Originator RPI (ms) Set the rate for reading datafrom the EtherNet/IPdevice.

It is applicable for all theI/O modules associated tothe adapter if the Apply RPIsettings on all associated I/Omodules option is selected.

It is un-configurable if theApply RPI settings on allassociated I/O modulesoption is not selected.


7. In the I/O Configuration tab, perform the following steps toconfigure parameters.

a. You can click or to add or remove I/O modules.

b. Select the Enable box for an I/O module, configure thefollowing parameters.If you do not select the Enable box, you cannot downloadconfigurations to the controller.


I/O ModuleName

Define a name for the I/O module. It cannotbegin with numbers and cannot contain anyspaces and special characters.

Description (Optional) The description for the I/Omodule.

Target toOriginator RPI(ms)

Set the rate for reading data from theEtherNet/IP device.

It is un-configurable if the Apply RPI settingson all associated I/O modules option isselected in the General tab.

Originator toTarget RPI (ms)

Set the rate for initiating the date exchangewith the EtherNet/IP device.

It is un-configurable if the Apply RPI settingson all associated I/O modules option isselected in the General tab.

ElectronicKeying

It is used to control if accept theconnection when the identity information ofEDS file does not match the EtherNet/IPdevice.

l Disable Keying: Allow the connectionwith EtherNet/IP device even the identityinformation of EDS file and theEtherNet/IP device are not match.

l Exact Match: The identity information ofEDS file must match the EtherNet/IPdevice, and then the connection will beallowed.

32


33

c. Click Select Device Type to choose a device type. The SelectDevice Type dialog appears.The available device types are displayed. You can enterkeywords to search device types, and also can filter them byselecting from the various filters for the Vendor and Categoryfields.

d. Select the target device type, and click Next to configure moreparameters which are defined in the corresponding EDS file.Configure them according vendor's documents.

e. Click OK to add the device type.

f. You can select Edit Device Type to re-configure the device type.The Edit Configuration Assembly dialog appears.

l Click Change Device Type to re-select a device type.

l Click Clear Device Type to remove the device type.

g. If you complete all the configurations, the Status will change

from to .

8. From the left panel, you can click to edit the device name and

description. You can also click to remove the device if required.


Configuring generic EtherNet/IP devicesIf you do not have the EDS file, you can create and configure ageneric EtherNet/IP device.

Prerequisites

n Ensure that the following details are available before creating andconfiguring the device:

l Device and Vendor information

l Parameter information

l Assembly information

l Connection information

n Bind EtherNet/IP Client to an Ethernet port. See "BindingEtherNet/IP Client to an Ethernet port" on page 23 for moreinformation.

To configure a generic EtherNet/IP device



2. Select Create or Customize EtherNet/IP Device, and select GenericEtherNet/IP Device.

3. Enter the Device Name and Description. The device name cannotbegin with numbers and cannot contain any spaces and specialcharacters.




IP Address The IP address of theEtherNet/IP device

Originator to Target RPI (ms) Set the rate for initiatingthe date exchange with theEtherNet/IP device.

Target to Originator RPI (ms) Set the rate for readingdata from the EtherNet/IPdevice.

6. In the Connection tab, configure the following parameters.


Comm Format The data type of the update data readingfrom EtherNet/IP devices.

34


35


There are four options: DINT, INT, REAL,and SINT

Input Input assembly: An assembly transfers datafrom an EtherNet/IP device as Producerdevice to a controller as Consumer.

Output Output assembly: An assembly transfersdata from a controller as Producer deviceto an EtherNet/IP device as Consumer.

Configuration Configuration assembly: An assembly whichtransports configuration data from theEtherNet/IP device originating theconnection to the EtherNet/IP device or IOmodule which is the target of theconnection.

Assembly Instance The assembly instance number provided bythe vendor. For more information, see thevendor's specification.

Assembly Size(Bytes)

The data length of the assembly providedby the vendor. For more information, seethe vendor's specification.

7. You can click to edit the device name and description. You can

also click to remove the device if required.


Scaling support for generic deviceScaling support covers custom parameters as well as PV and OPparameters on generic devices.

Formulae used by the controller to perform scaling:

1. FLOATVALUE for Custom Input parameters is calculated as:

2. For the Output direction, use this formula to calculate RAWVALUEfrom the FLOATVALUE (which is typically written through the


strategy):

The formula is the same as with Input scaling solved for 'Raw value'.

The process value that is received from field is converted to digitalform by the A/D converter. LOWRANGE and HIGHRANGE valuesdefine the normal operating range of the RAW value.

RAW value in the output direction is the final output value sent to thedevice in the output assembly. This is the linearly scaled value (withsome scale factor multiplied and bias added) of the OP (which is inpercentage) within the LOWRANGE and HIGHRANGE operating rangeof the RAW value.

Configuring communication with third-partycontrollers

Configuring communication with C300/UOCWhen ControlEdge 900 controller communicates with C300/UOC, itacts as an EtherNet/IP Server. Only User-defined data type STRUCT issupported for communicating with C300/UOC, which can include thefollowing elementary data types:

n DATATYPE_BOOL (0x01)

n DATATYPE_SINT (0x02)

n DATATYPE_INT (0x03)

n DATATYPE_DINT (0x04)

n DATATYPE_USINT (0x05)

n DATATYPE_UINT (0x06)

n DATATYPE_UDINT (0x07)

n DATATYPE_REAL (0x08)

1. Bind EtherNet/IP Server to an Ethernet port. See "BindingEtherNet/IP Server to an Ethernet port" on page 1 for more

36


37

information.

2. Declare a STRUCT data type.

a. From IEC Programming Workspace, right-click Data Types, selectInsert > Datatypes.

b. Enter a name for the data type, and click OK.

c. Double click the new data type, and from Edit Wizard, doubleclick STRUCT.

d. Enter the target elementary data types, and click Save.

3. Configure target variables data type as the STRUCT data type.

4. Select EtherNet/IP for target variables. See "Selecting EtherNet/IPfor variables" on page 1 for more information.

Configuring communication with ControlLogixcontrollersWhen ControlEdge 900 controller communicates with Rockwell ABControlLogix controllers, it can act as an EtherNet/IP Client orEtherNet/IP Server.

n If ControlEdge 900 controller acts as an EtherNet/IP Client,ControlEdge Builder provides function blocks to enablecommunication between 900 controller and third-partycontrollers. For how to configure function blocks, see"EtherNet/IP" in the ControlEdge Builder Function and FunctionBlock Configuration Reference.

n If ControlEdge 900 controller acts as an EtherNet/IP Server, See"Configuring EtherNet/IP Server" on page 1 for more information.User-defined data types are not supported. Rockwell ABControlLogix can read and write variables of ControlEdge 900controller with the following data types:

l DATATYPE_SINT (0x02)

l DATATYPE_INT (0x03)


l DATATYPE_DINT (0x04)

l DATATYPE_USINT (0x05)

l DATATYPE_UINT (0x06)

l DATATYPE_UDINT (0x07)

l DATATYPE_REAL (0x08)

Configuring EtherNet/IP ServerThis section introduces how to configure ControlEdge 900 controlleras an EtherNet/IP Server. EtherNet/IP Client can read, write andmonitor global variable, program local variable of the EtherNet/IPServer through the Tag name configured in EtherNet/IP Client.

Global variable's tag name is@GV. . If some controllers donot support special characters such as @, the tag name should beGV.GV..

Program Local variable's tag name is ..

Binding EtherNet/IP Server to an Ethernet portThis section introduces how to bind EtherNet/IP Server to ETH1 orETH2. Only one Ethernet port can be bound at a time.

To bind EtherNet/IP Server

1. From Home Page, click Configure Ethernet Ports and select ETH1 orETH2.

2. Under Network Setting, configure the IP addresses, subnet maskand gateway.

3. Under Protocol Binding, select EtherNet/IP Server.

4. Click Save to complete the Ethernet port configuration.

5. Click Back to return to the Home Page.

Selecting EtherNet/IP for variablesEtherNet/IP must be selected for global variables or program localvariables of EtherNet/IP Server, so that EtherNet/IP Client can read,write and monitor these variables through the Tag name configuredin EtherNet/IP Client.

38


39

Global variable's tag name is@GV. . If some controllers donot support special characters such as @, the tag name should beGV.GV..

Program Local variable's tag name is ..

1. Click IEC Programming Workspace on the toolbar, or from HomePage, click Program with IEC61131-3.

2. Perform either of the following methods to select EIP for localvariables or global variables.

l From the variable sheets, select EIP.

l From the variable properties dialog, select EIP.

3. Compile the configuration to the controller. See "Compiling aproject" on page 1 for more information.


40


CHAPTER

5 ETHERNET/IP I/O BEHAVIOR DURINGSWITCHOVEROn controllers switchover there will be a control freeze for 200 ms toa maximum of 2 seconds.

The control freeze time is due to controllers reforming theEtherNet/IP I/O connections from the new primary and getting thelatest publication from the I/O.

NOTE: This time is dependent on the number of EtherNet/IP I/OModules configured.

During this time the IOM and channel blocks in the controllers willhold and work on with the last I/O data received before switchover.

41

42

Chapter 5 - EtherNet/IP I/O Behavior during switchover

CHAPTER

6 DIAGNOSTICViewing EtherNet/IP device diagnostics

You can log in as the Administrator, Engineer or Operator to connectthe target controller and view EtherNet/IP device diagnostics.

1. From the Home Page, click View Diagnostics under Diagnostics. Thediagnostics page appears.

2. Click the down arrow on the right of the EtherNet/IP Device tab toexpand the group. The overview of the EtherNet/IP devices whichare connected with the controller appears at the rightmost page.See the following table for the configuration parameters:


CIP ConnectionUsed

The number of the used CIP connections.

CIP ConnectionRemaining

The number of the unused CIPconnections.

CIP ConnectionActive

The number of the active CIP connections.

Device Name EtherNet/IP device name

Device Type EtherNet/IP device type

Status Status of EtherNet/IP device:

l OK: All the devices are runningwithout error.

l Error: Error exists for theconnection.

Total Packets Sent The number of packets sent by the client

Total PacketsReceived

The number of received packets from theserver

Packets ReceivedPer Second

The number of received packets from theserver per second

43


Packets Sent PerSecond

The number of packets sent by the clientper second

IP Address IP Address of the EtherNet/IP device

Connection Timeout The number of connection timeout

Auto-refresh is selected by default, you can set a refresh rate toupdate diagnostics regularly. You can also click Auto-refresh toclose it, and click Refresh to update diagnostics manually.

You can click Reset Statistics to reset statistic values to the defaultvalues.

3. Click an EtherNet/IP device name view its diagnostics displayed atthe rightmost page.


Module Status The status of EtherNet/IP device

See "EtherNet/IP device error codes" on thefacing page for more information.

IP Address The IP Address of EtherNet/IP device

Device Type The EtherNet/IP device type

Vendor Vendor of EtherNet/IP device

Product Code EtherNet/IP device code

Revision EtherNet/IP device revision

Total PacketsSent

The number of packets sent by the client




The number of packets sent by the client persecond



CommunicationErrors

The number of communication error

44

Chapter 6 - Diagnostic

45


CommunicationTimeout

The number of device offline

4. For the EtherNet/IP device with an adapter, click the down arrowat the right of the device to view I/O module list. Click an I/Omodule to view its diagnostics.


Module Status The status of I/O module

IP Address The IP Address of I/O module

Device Type The I/O module type

Vendor Vendor of EtherNet/IP device

Product Code EtherNet/IP device code

Revision EtherNet/IP device revision

Total Packets Sent The number of packets sent by the client




The number of packets sent by the clientper second



CommunicationErrors

The number of communication error

CommunicationTimeout

The number of device offline

EtherNet/IP device error codesEtherNet/IP device diagnostics are also displayed in IEC ProgrammingWorkspace. Click IEC Programming Workspace, and double-click Global_Variables, check the EtherNetIP Diagnostics group.

Error code Status Description

0x0000 EIP_IO_STATE_STANDBY Device is standby.



0x1000 EIP_IO_STATE_FAULTED Connecting failed

0x1100 EIP_IO_STATE_FAULTED_WAITING_TO_CONNECT

Connecting failed, waiting to re-connect

0x1200 EIP_IO_STATE_FAULTED_CONNECTING

Connecting failed, re-connecting

0x1300 EIP_IO_STATE_FAULTED_BAD_IP_ADDR

Invalid IP address specified

0x1400 EIP_IO_STATE_FAULTED_SERVER_ALLOC_FAILED

I/O server allocation failed

0x1500 EIP_IO_STATE_FAULTED_IO_ALLOC_FAILED

I/O allocation failed

0x1600 EIP_IO_STATE_FAULTED_BAD_T2O_DATAPTR

Invalid Target to Originator data sizeand/or pointer

0x1700 EIP_IO_STATE_FAULTED_BAD_O2T_DATAPTR

Invalid Originator to Target data sizeand/or pointer

0x1800 EIP_IO_STATE_FAULTED_BAD_T2O_RPI

Invalid Target to Originator RPI

0x1900 EIP_IO_STATE_FAULTED_BAD_O2T_RPI

Invalid Originator to Target RPI

0x1a00 EIP_IO_STATE_FAULTED_BAD_CONFIGPTR

Invalid configuration size and/orpointer

0x3000 EIP_IO_STATE_CONNECTING Connecting

0x4000 EIP_IO_STATE_RUNNING Running

0x5000 EIP_IO_STATE_SHUTTING_DOWN Shutting down

0x7100 EIP_IO_STATE_WAITING_TO_CONNECT

Waiting to connect

0x7200 EIP_IO_STATE_WAITING_TO_SHUTDOWN

Waiting to shut down

0x7300 EIP_IO_STATE_WAITING_TO_RECONNECT

Re-connect after forward close,instead of freeing I/O

0x9000 EIP_IO_STATE_CNTRLR_ Forward closing of I/O modules with

46


47


SWITCHOVER input channels after the controllerswitch over


48


APPENDIX

AThe error codes are returned with the response to a Connection Manager ServiceRequest that resulted in an error. These error codes shall be used to help diagnosethe problem with a Service Request. The error code shall be split into an 8 bitgeneral status and one or more 16- bit words of extended status. Unless specifiedotherwise, only the first word of extended status shall be required. Additional wordsof extended status may be used to specify additional device specific information. Alldevices that originate messages shall be able to handle multiple words of extendedstatus.

See "Connection Manager Object Instance Error codes" in the Common IndustrialProtocol Specification for definitions of status codes. If any questions, you cancontact Honeywell representatives.

STATUS CODES

49

Notices

NOTICES

Trademarks

Experion® is a registered trademark of Honeywell International, Inc.

ControlEdge™ is a trademark of Honeywell International, Inc.

Other trademarks

Microsoft and SQL Server are either registered trademarks or trademarks ofMicrosoft Corporation in the United States and/or other countries.

Trademarks that appear in this document are used only to the benefit of thetrademark owner, with no intention of trademark infringement.

Third-party licenses

This product may contain or be derived from materials, including software, ofthird parties. The third party materials may be subject to licenses, notices,restrictions and obligations imposed by the licensor. The licenses, notices,restrictions and obligations, if any, may be found in the materials accompanyingthe product, in the documents or files accompanying such third party materials, ina file named third_party_licenses on the media containing the product, or athttp://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedback

You can find the most up-to-date documents on the Honeywell Process Solutionssupport website at:

http://www.honeywellprocess.com/support

If you have comments about Honeywell Process Solutions documentation, sendyour feedback to:

[email protected]

Use this email address to provide feedback, or to report errors and omissions inthe documentation. For immediate help with a technical problem, contact yourlocal Honeywell Technical Assistance Center (TAC).

50

http://www.honeywell.com/ps/thirdpartylicenseshttp://www.honeywellprocess.com/supportmailto:[email protected]

Notices

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a softwaredefect or weakness that can be exploited to reduce the operational or securitycapabilities of the software.

Honeywell investigates all reports of security vulnerabilities affecting Honeywellproducts and services.

To report a potential security vulnerability against any Honeywell product, pleasefollow the instructions at:

https://honeywell.com/pages/vulnerabilityreporting.aspx

Submit the requested information to Honeywell using one of the followingmethods:

n Send an email to [email protected]

n Contact your local Honeywell Technical Assistance Center (TAC) listed in the“Support” section of this document.

Support

For support, contact your local Honeywell Process Solutions Customer ContactCenter (CCC). To find your local CCC visit the website,https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx.

Training classes

Honeywell holds technical training classes that are taught by process controlsystems experts. For more information about these classes, contact yourHoneywell representative, or see http://www.automationcollege.com.

51

https://honeywell.com/Pages/vulnerabilityreporting.aspxmailto:[email protected]://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspxhttps://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspxhttp://www.automationcollege.com/

Notices

52

ContentsAbout this guideChapter 2 - OverviewChapter 3 - Planning and Designing EtherNet/IPTested EtherNet/IP devicesEtherNet/IP implementation architecture and topologyDevice Level Ring (DLR) by ETAPSTAR with Stratix switch or MOXA switchLiner (Broken Ring) on Non-redundant CPMCommon network for multiple CPM

Network usage guidelines and recommendations

Chapter 4 - ConfigurationConfiguring EtherNet/IP ClientBinding EtherNet/IP Client to an Ethernet portRegistering Electronic Data Sheets (EDS) filesConfiguring EtherNet/IP devices using EDS filesConfiguring generic EtherNet/IP devicesScaling support for generic device

Configuring communication with third-party controllersConfiguring communication with C300/UOCConfiguring communication with ControlLogix controllers

Configuring EtherNet/IP ServerBinding EtherNet/IP Server to an Ethernet portSelecting EtherNet/IP for variables

Chapter 5 - EtherNet/IP I/O Behavior during switchoverChapter 6 - DiagnosticViewing EtherNet/IP device diagnosticsEtherNet/IP device error codes

Appendix A - Status codesNotices

ControlEdge EtherNetIP User Guide RTDOC-X548-en-151A · 2018. 12. 6. · ControlEdgePLC...

Documents

Transcript of ControlEdge EtherNetIP User Guide RTDOC-X548-en-151A · 2018. 12. 6. · ControlEdgePLC...