Rockwell Automation 1732E-IB16M12SOEDR User Manual

1732E EtherNet/IP ArmorBlock Supporting Sequence of Events

Catalog Number 1732E-IB16M12SOEDR User Manual

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at

http://literature.rockwellautomation.com

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.

) describes some important differences between solid state equipment and hard-wired electromechanical

IMPORTANT

ATTENTION

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

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

SHOCK HAZARD

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

BURN HAZARD

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

Rockwell Automation, Allen-Bradley, RSLogix, RSLinx, RSLogix 5000 and TechConnect are trademarks of Rockwell Automation, Inc.

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

About 1732E ArmorBlock Modules

Module Overview

Preface

Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Common Techniques Used in this Manual. . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Module Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Hardware/Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Use of the Common Industrial Protocol (CIP) . . . . . . . . . . . . . . . . . . . 2

Understand the Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . 2

Specify the Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . 3

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

EtherNet/IP Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Introduction to CIP Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

What is IEEE 1588 PTP (Precision Time Protocol)? . . . . . . . . . . . 6

CIP Sync Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

What is CIP Sync? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

What is Time Stamping? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Introduction to Sequence of Events modules . . . . . . . . . . . . . . . . . . . . 8

High Performance Sequence of Events Applications in the Logix

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

First Fault Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

High Speed Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Motion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Global Position Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Use the Module in an ArmorBlock System

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Differences Between Module and Standard I/O . . . . . . . . . . . . . . . . . 11

Similar Functionality to Standard ArmorBlock. . . . . . . . . . . . . . . . . . . 11

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 4 Install Your Module

i Publication 1732E-UM002A-EN-P - March 2010

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Mount the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Wire the Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Auxiliary Power Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table of Contents ii

Configure the Module for Your EtherNet/IP Network

Configure the Module Using RSLogix 5000

Chapter 5

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Gateway Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Subnet Mask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Set the Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Use the Rockwell BootP/DHCP Utility . . . . . . . . . . . . . . . . . . . . . . . . 21

Save the Relation List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Use DHCP Software to Configure Your Module . . . . . . . . . . . . . . . . 24

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 6

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Create the Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure Your I/O Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

RSLogix 5000 Configuration Software . . . . . . . . . . . . . . . . . . . . . . 30

Overview of the Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . 30

Add a New Bridge and Module to Your RSLogix 5000 Project . . . . . 30

Add the Local EtherNet/IP Bridge to the I/O Configuration. . . 31

Add the 1732E-IB16M12SOEDR as a child of the

1756-EN2T module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Use the Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Change the Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Download Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Edit Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Access Module Data in RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configure RSLogix 5000 and the 1756-EN2T Communication

Module for CIP Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Module Features

Chapter 7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Determine Module Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Module Features That Can Be Configured . . . . . . . . . . . . . . . . . . . . . . 42

Timestamp Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Timestamp Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Input Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Software Configurable Input Filters . . . . . . . . . . . . . . . . . . . . . . . . 46

Communications Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Electronic Keying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Module Inhibiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Module Fault Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Fully Software Configurable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Using the Module

Table of Contents iii

Producer/Consumer Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Status Indicator Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Agency Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 8

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

How Does the Module Store Timestamp Data? . . . . . . . . . . . . . . . . . 56

Using Timestamp Latching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Using Timestamp Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Manage the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Module Sends Data to the Controller. . . . . . . . . . . . . . . . . . . . . . . 60

Copy Relevant Input Data to a Separate Data Structure . . . . . . . . 63

Acknowledge Timestamp Latching Timestamp Data . . . . . . . . . . 64

Sort the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Clear All Data From the Module’s Buffer At Once . . . . . . . . . . . . . . . 67

Propagate a Signal From Input Pin to EtherNet . . . . . . . . . . . . . . . . . 67

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Interpret Status Indicators

Troubleshoot the Module

ArmorBlock 2 Port Ethernet Module Specifications

Module Tags

1732E EtherNet/IP ArmorBlock Supporting Sequence of Events Data Tables Connect to Networks via Ethernet Interface

Chapter 9

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

Chapter Summary and What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 10

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Troubleshoot the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Determining Fault Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Appendix A

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Appendix B

Fault and Status Reporting Between the Module and Controllers . . . 77

Module Tag Names and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Appendix C

Communicate with Your Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix D

ArmorBlock Module and Ethernet Communication . . . . . . . . . . . . . . 89

ArmorBlock module and PC Connections to the

Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Ethernet Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Publication 1732E-UM002A-EN-P - March 2010

Table of Contents iv

1732E ArmorBlock I/O Embedded Web Server

Index

Connecting to an Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . 90

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Ethernet Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Duplicate IP address Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Configure Ethernet Communications on the ArmorBlock module . . 91

Configure Using RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . . 92

Configure Using Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix E

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Typical Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Browser Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Access the Home Page of the Web Server . . . . . . . . . . . . . . . . . . . . . . 96

Log Into the Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Navigate the 1732E ArmorBlock I/O . . . . . . . . . . . . . . . . . . . . . . . . . 97

Access Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Glossary

Publication 1732E-UM002A-EN-P - March 2010

Preface

Read this preface to familiarize yourself with the rest of the manual. It provides information concerning:

• who should use this manual

• the purpose of this manual

• related documentation

• conventions used in this manual

Who Should Use this Manual

Purpose of this Manual

Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use 1732 ArmorBlock EtherNet/IP with Diagnostics and CIPSync modules.

You should have a basic understanding of electrical circuitry and familiarity with relay logic. If you do not, obtain the proper training before using this product.

This manual is a reference guide for the 1732E-IB16M12SOEDR module. It describes the procedures you use to install, wire, and troubleshoot your module. This manual:

• explains how to install and wire your module

• gives you an overview of the ArmorBlock EtherNet/IP system

v Publication 1732E-UM002A-EN-P - March 2010

vi Preface

Common Techniques Used in this Manual

Publication 1732E-UM002A-EN-P - March 2010

The following conventions are used throughout this manual:

• Bulleted lists such as this one provide information, not procedural steps.

• Numbered lists provide sequential steps or hierarchical information.

Italic

•

type is used for emphasis.

About 1732E ArmorBlock Modules

Chapter

Overview

Module Features

This chapter is an overview of the 1732E ArmorBlock family of modules. You will need to understand the concepts discussed in this chapter to configure your module and use it in an EtherNet/IP control system. The following table lists where to find specific information in this chapter.

Topic Page

Module Features 1 Hardware/Software Compatibility 1 Use of the Common Industrial Protocol (CIP) 2 Understand the Producer/Consumer Model 2 Specify the Requested Packet Interval (RPI) 3

The module features include:

• use of EtherNet/IP messages encapsulated within standard

TCP/UDP/IP protocol

• common application layer with ControlNet and DeviceNet

• interfacing via Category 5 rated twisted pair cable

• half/full duplex 10 Mbit or 100 Mbit operation

• mounting on a wall or panel

• communication supported by RSLinx software

• IP address assigned via standard DHCP tools

• I/O configuration via RSLogix 5000 software

• no network scheduling required

• no routing tables required

• supports connections from multiple controllers simultaneously

Hardware/Software

The module and the applications described in this manual are compatible with the following firmware versions and software releases.

Compatibility

1 Publication 1732E-UM002A-EN-P - March 2010

2 About 1732E ArmorBlock Modules

Contact Rockwell Automation if you need software or firmware upgrades to use this equipment.

Product Firmware Version / Software Release

1732E-IB16M12SOEDR Firmware rev. 1.6 or later 1756-EN2T or 1756-EN2TR module 2.3 (or later version of major revision 2) when

using RSLogix 5000 v17

3.x version when using RSLogix 5000 v18 or later RSLogix 5000 software 17 or later RSLinx software 2.56 or later

Use of the Common Industrial Protocol (CIP)

For a complete ControlLogix compatibility matrix, see publication IA-AT003

The 1732E-IB16M12SOEDR uses the Common Industrial Protocol (CIP). CIP is the application layer protocol specified for EtherNet/IP, the Ethernet Industrial Protocol, as well as for ControlNet and DeviceNet. It is a message-based protocol that implements a relative path to send a message from the “producing” device in a system to the “consuming” devices.

The producing device contains the path information that steers the message along the proper route to reach its consumers. Because the producing device holds this information, other devices along the path simply pass this information; they do not need to store it.

This has two significant benefits:

• You do not need to configure routing tables in the bridging modules,

which greatly simplifies maintenance and module replacement.

• You maintain full control over the route taken by each message, which

enables you to select alternative paths for the same end device.

Understand the Producer/Consumer Model

Publication 1732E-UM002A-EN-P - March 2010

The CIP “producer/consumer” networking model replaces the old source/destination (“master/slave”) model. The producer/consumer model reduces network traffic and increases speed of transmission. In traditional I/O systems, controllers poll input modules to obtain their input status. In the CIP system, input modules are not polled by a controller. Instead, they produce their data either upon a change of state (COS) or periodically. The frequency of update depends upon the options chosen during configuration and where on the network the input module resides. The input module, therefore, is a producer of input data and the controller is a consumer of the data.

The controller can also produce data for other controllers to consume. The produced and consumed data is accessible by multiple controllers and other devices over the EtherNet/IP network. This data exchange conforms to the producer/consumer model.

About 1732E ArmorBlock Modules 3

Specify the Requested Packet Interval (RPI)

Chapter Summary and What’s Next

The Requested Packet Interval (RPI) is the update rate specified for a particular piece of data on the network. This value specifies how often to produce the data for that device. For example, if you specify an RPI of 50 ms, it means that every 50 ms the device sends its data to the controller or the controller sends its data to the device.

RPIs are only used for devices that exchange data. For example, a ControlLogix EtherNet/IP bridge module in the same chassis as the controller does not require an RPI because it is not a data-producing member of the system; it is used only as a bridge to remote modules.

In this chapter you were given an overview of the 1732E ArmorBlock family of modules. The next chapter is an overview of the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module.

Publication 1732E-UM002A-EN-P - March 2010

4 About 1732E ArmorBlock Modules

Notes:

Publication 1732E-UM002A-EN-P - March 2010

Module Overview

Overview

EtherNet/IP Network Overview

This chapter provides an overview of the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module. The module uses CIP Sync functionality to provide time stamping when an input event occurs.

Status Indicators Functional Earth

EtherNet/IP D-Code M12 connector

M12 I/O connectors/ Status indicators

LINK 1 LINK 2

EtherNet/IP D-Code M12 connector

M12 I/O connectors/ Status indicators

Auxiliary power

Protective Earth

Auxiliary power status indicator

Node address switches

44945

The module incorporates embedded switch technology. The module supports Star, Tree, Daisy Chain or Linear, and Ring network topologies.

• Star or Tree topologies can connect to either Port 1 or Port 2.

• Daisy Chain/Linear topologies will pass communications from Port 1 to

2, or Port 2 to 1.

• Ring topology will pass communications from Port 1 to 2, or Port 2

to 1.

The 1732E-IB16M12SOEDR supports the management of network traffic to ensure timely delivery of critical data, Quality of Service (QoS) and Internet Group Management Protocol (IGMP) protocols are supported.

5 Publication 1732E-UM002A-EN-P - March 2010

6 Module Overview

Introduction to CIP Sync

If the ring topology is used, the ArmorBlock Supporting Sequence of Events) must be designated in the system, and it will determine the beacon rate and the timeout period. For more information on topologies, refer to publication ENET-AP005 1732E-IB16M12SOEDR module is a CIP Sync slave only device. There must be another module on the network that will function as a master clock.

Each input connector's Sensor Source Voltage (SSV) is protected from short circuits to ground as well as open wire conditions due to missing sensor or cable disconnection. These conditions are indicated in the modules input tags and by its input LEDs flashing red for open wire or being solid red for short circuit.

CIP is the Common Industrial Protocol that we use to let all Rockwell products communicate with each other whether it be on a DeviceNet, ControlNet, and/or an EtherNet network. Since it is an ODVA standard, other industrial product manufactures develop products to communicate via the CIP protocol.

CIP Sync is a CIP implementation of the IEEE 1588 PTP (Precision Time Protocol) in which devices can bridge the PTP time across backplanes and on to other networks via EtherNet/IP ports.

Ring Master

(not the 1732E EtherNet/IP

. The

What is IEEE 1588 PTP (Precision Time Protocol)?

The IEEE 1588 standard specifies a protocol to synchronize independent clocks running on separate nodes of a distributed measurement and control system to a high degree of accuracy and precision. The clocks communicate with each other over a communication network. In its basic form, the protocol is intended to be administration free. The protocol generates a master slave relationship among the clocks in the system. Within a given subnet of a network there will be a single master clock. All clocks ultimately derive their time from a clock known as the grandmaster clock. This is called Precision Time Protocol (PTP).

The PTP is a time-transfer protocol defined in the IEEE 1588-2008 standard that allows precise synchronization of networks, for example, Ethernet. Accuracy within the nanosecond range can be achieved with this protocol when using hardware generated synchronization.

IEEE 1588 is designed for local systems requiring very high accuracies beyond those attainable using Network Time Protocol (NTP). NTP is used to synchronize the time of a computer client or server to another server or reference time source, such as a GPS.

Publication 1732E-UM002A-EN-P - March 2010

Module Overview 7

CIP Sync Support

CIP Sync supports the IEEE 1588-2008 synchronization standard. In this architecture, a grandmaster clock provides a master time reference for the system time. The 1732E-IB16M12SOEDR module is a CIP Sync slave only device. There must be another module on the network that will function as a master clock. The grandmaster could be:

• a 1756 ControlLogix L6 or L7controller when using RSLogix 5000

software V18 or later.

• an Ethernet switch that supports IEEE 1588 V2, or

• a Symmetricom Grand Master GPS or equivalent.

What is CIP Sync?

CIP Sync is a CIP implementation of the IEE 1588 PTP (Precision Time Protocol). CIP Sync provides accurate real-time (Real-World Time) or Universal Coordinated Time (UTC) synchronization of controllers and devices connected over CIP networks. This technology supports highly distributed applications that require time stamping, sequence of events recording, distributed motion control, and increased control coordination.

What is Time Stamping?

Each input has its own individual timestamp recorded for both ON and OFF transitions. The offset from the timestamp to the local clock is also recorded so that steps in time can be detected and resolved. Diagnostic events such as short circuit, open wire and open load are not time stamped.

Time stamping uses the 64-bit System Time whose time base is determined by the modules master clock resolved in microseconds. Each timestamp is updated as soon as an input transition is detected, before input filtering occurs. When filtering is enabled, the transition is only recorded if the transition passes the filter.

The module starts time stamping as soon as it powers up, even if it is not synchronized to a master clock. If it is synchronized to a master clock and then becomes unsynchronized it will continue to time stamp. All time stamps and offsets have a value of zero at power-up.

For more information on how to use CIP Sync technology, see the Integrated Architecture and CIP Sync Configuration Application Technique publication

A-AT003.

Publication 1732E-UM002A-EN-P - March 2010

8 Module Overview

Introduction to Sequence of Events modules

The 1732E-IB16M12SOEDR is an input module that offers sub-millisecond timestamping on a per point basis in addition to providing the basic ON/OFF detection.

All input point event times are recorded and returned in a single buffer. The module returns two 64-bit timestamps for each input point, thus allowing:

Filtering allows all inputs on the module to be filtered for both ON to OFF and OFF to ON transitions. The timestamp for a filtered input will be the time of the initial transition to the new state and not the time that the filter validates the event as real.

Selective Event Capturing allows particular events to be disabled per input and per transition, ON to OFF or OFF to ON.

• ON and OFF events for each point to be displayed simultaneously in

the input data.

• ladder logic not being explicitly required to see events, although needed

to archive events.

• events to be kept in the controller memory during remote power loss

thus eliminating data loss.

Event latching ensures that events are not overwritten. A single transition in each direction is recorded per point. Any new event, which occurs after the point has captured a time stamp, is dropped until the stored events have been acknowledged.

If latching is not enabled, new events overwrite old events immediately. Thus, if inputs are changing rapidly it may be possible that events will be lost either in the module or the controller prior to an event being operated on by ladder logic.

When events are lost, either old ones being overwritten or new ones being ignored due to latching, an EventOverflow bit will be set for each point that loses an event. The EventOverflow bit will clear when the blocking events for that point are acknowledged.

Timestamping is a feature that registers a time reference to a change in input data. For the 1732E-IB16M12SOEDR, the time mechanism used for timestamping is (PTP) system time. The 1732E-IB16M12SOEDR module is a PTP slave only device. There must be another module module on the network that will function as a master clock.

Publication 1732E-UM002A-EN-P - March 2010

Module Overview 9

High Performance Sequence of Events Applications in the Logix Architecture

Sequence of Events (SOE) applications span a wide range of industry applications. Typically any event that needs to be compared against a second event can be classified as SOE.

• Used on discrete machines to identify failure points

• Used in Power Substations or power plants to indicate first fault

conditions

• Used in SCADA applications to indicate pump failures or other discrete

events

• Used in motion control applications to increase control coordination.

• Used in high speed applications

• Used in Global Position Registration

In today's environment, specifications for SOE applications typically require 1 ms or better resolution on time stamps. There are two types of SOE applications.

First Fault

First Fault measures the time between events with no correlation to events outside of that system.

Real Time

Real Time captures the time of an event occurrence as it relates to some master clock. Typically this is a GPS, NTP server or some other very accurate clock source. This method allows distributed systems to capture events and build a history of these events. These events are almost always digital, however some are analog for which lower performance requirements can be configured.

First Fault Detection

An example of first fault detection would be intermittent failure from a sensor on a safety system faults a machine and halts production cascading a flood of other interrelated machine faults. Traditional fault detection or alarms may not appear in the correct timed order of actual failure making root cause of the down time difficult or impossible.

Time Stamped I/O

High precision time stamps on I/O allows very accurate first fault detection making it easy to identify the initial fault that caused machine down time.

Publication 1732E-UM002A-EN-P - March 2010

10 Module Overview

Common Time base for Alarming System logs user interaction as well as alarm events using common time reference.

The power industry requires sub 1 ms accuracy on first fault across geographically dispersed architecture.

High Speed Applications

Packaging machines or sorters that have fast part cycles are often bottlenecked by controller scan times. By switching to a time based solution, you can remove many scan time critical components of the system. This programming technique allows you to do predictive events and schedule outputs to run things like diverters without having a scan time to match the part cycle time.

Motion Control

CIP Sync also provides a common time reference for distributed VFD drives, servo’s, and controllers throughout the system. This allows controllers to request axes reach a pre-defined position at a known time reference or run at a set speed using the same reference. Since all drives and controllers in the system have the same reference to time, the controller can issue simple requests for axes to reach target positions in a synchronized fashion.

Global Position Registration

Registration refers to a function usually performed by the drive where a physical input is triggered causing the drive to precisely capture the actual axis position when the input event occurred. Rather than wiring inputs to the registration input on all of the drives, this time based system lets you wire an input to only one time based SOE input module. The time stamp returned for that input, can be used by the motion planner to calculate the actual axis position at the time the input triggered. This simplifies system installation, reduces wiring costs, and provides a global machine registration for all the axes in the system thru one SOE input.

Chapter Summary and What’s Next

Publication 1732E-UM002A-EN-P - March 2010

In this chapter, you were given an overview of the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module. The next chapter describes how the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module operates in an ArmorBlock system.

Use the Module in an ArmorBlock System

Introduction

Differences Between Module and Standard I/O

Difference Description

Additional data produced for controller The module produces significantly more data for its owner-controller than standard

CIP Sync This module has an internal clock that is synchronized with a master clock using CIP Sync.

Only one owner-controller per module While multiple controllers can simultaneously own other digital input modules, the module

This chapter describes how the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events module operates in an ArmorBlock system.

Topic Page

Differences Between Module and Standard I/O 11 Similar Functionality to Standard ArmorBlock 11

In many aspects, the module behaves the same as other ArmorBlock digital input modules. However, the module offers several significant differences from other EtherNet/IP ArmorBlock digital input modules, including those described in the following table.

ArmorBlock digital input modules. While other input modules only produce ON/OFF and fault status, the module produces data such as ON/OFF and fault status, timestamp data, indication of whether new data was produced for specific input points or if transitions were not timestamped.

This clock is used for time stamping inputs.

only supports a single owner-controller.

No listen-only connections Controllers cannot make listen-only connections to the module. All connections between

the module and its owner-controller are direct connections.

Similar Functionality to Standard ArmorBlock

11 Publication 1732E-UM002A-EN-P - March 2010

With respect to general module operation in an ArmorBlock I/O system, the module operates similarly to other ArmorBlock, single and dual port EtherNet/IP I/O modules in many ways. This chapter focuses on how the module’s behavior differs from that of other ArmorBlock I/O modules. However, you should be aware of aspects in which the module is similar to

12 Use the Module in an ArmorBlock System

standard EtherNet/IP ArmorBlock I/O modules. In addition to the common features described in Chapter 1

Concept Description

Ownership Every module in the ArmorBlock system must be owned by a Logix5000 controller. This

owner-controller:

, the following table describes the similarities.

• stores configuration data for every module that it owns.

• sends the module configuration data to define the module’s behavior and

begin operation with the control system.

This module does not support multiple owner-controllers.

Using RSLogix 5000 software The I/O configuration portion of RSLogix 5000 software, v17 or greater, generates the

configuration data for each module.

Configuration data is transferred to the controller during the program download and subsequently transferred to the appropriate modules.

Modules are ready to run as soon as the configuration data has been downloaded.

Chapter Summary and What’s Next

Configure all modules for a given controller using RSLogix 5000 software and download that information to the controller.

In this chapter, you learned about the differences between this module and other EtherNet/IP ArmorBlock modules. The next chapter describes how to install and wire your module.

Publication 1732E-UM002A-EN-P - March 2010

Install Your Module

Chapter

Overview

Mount the Module

This chapter shows you how to install and wire the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events. The only tools you require are a flat or Phillips head screwdriver and drill.

To mount the module on a wall or panel, use the screw holes provided in the module.

Refer to the drilling dimensions illustration to guide you in mounting the module.

43.25 mm (1.70 in.)

26.5 mm (1.04 in.)

179 mm (7.05 in.)

65 mm (2.56 in.)

32.5 mm (1.28 in.)

169 mm (6.64 in.)

44946

Front view

Install the mounting base as follows:

1. Lay out the required points as shown above in the drilling dimension drawing.

2. Drill the necessary holes for #8 (M4) pan head screws.

3. Mount the module using #8 (M4) screws.

13 Publication 1732E-UM002A-EN-P - March 2010

Side view

14 Install Your Module

Wire the Module

The ArmorBlock EtherNet/IP family has 5-pin micro-style I/O connectors.

We provide caps to cover the unused connectors on your module. Connect the quick-disconnect cord sets you selected for your module to the appropriate ports.

I/O Connectors

Refer to the pinout diagrams for the I/O connectors.

Micro-style

1 2

5-Pin Input Female

(View into connector) Pin 1 Sensor Source Voltage Pin 2 Input B Pin 3 Return

44807

Pin 4 Input A Pin 5 PE

Connector

Ethernet/IP Connectors

Refer to the pinout diagrams for the network connectors.

D-Code M12 Network Female Connector

(View into connector) Pin 1 M12_Tx+ Pin 2 M12_Rx+ Pin 3 M12_TxPin 4 M12_Rx-

Pin 5 Connector shell shield FE

44808

Publication 1732E-UM002A-EN-P - March 2010

IMPORTANT

ATTENTION

Use the 1585D–M4DC–H: Polyamide small body unshielded or the 1585D–M4DC–SH: Zinc die-cast large body shielded mating connectors for the D-Code M12 female network connector.

Use two twisted pair CAT5E UTP or STP cable.

D-Code

M12 Pin

1 White-Orange TX+ 1 2 White-Green RX+ 3 3 Orange TX- 2 4 Green RX- 6

Wire Color Signal 8-way Modular

RJ45 Pin

Make sure all connectors and caps are securely tightened to properly seal the connections against leaks and maintain IP enclosure type requirements.

Install Your Module 15

Auxiliary Power Cable

Attach the mini-style 4-pin connector to the mini-style 4-pin receptacle as shown below.

Mini-style 4-Pin Male Receptacle

(View into receptacle)

4 2

3 1

Auxiliary Power is based on a 4-pin connector system and is used to provide 24V DC power to I/O modules and other devices. Pins 3 and 4 are connected inside the module.

Pin 1 NC Pin 2 Sensor/MDL power+ Pin 3 Sensor/MDL powerPin 4 NC

44809

Chapter Summary and What’s Next

ATTENTION

To comply with the CE Low Voltage Directive (LVD), this equipment and all connected I/O must be powered from a source compliant with the following:

Safety Extra Low Voltage (SELV) or Protected Extra Low Voltage (PELV).

In this chapter, you learned how to install and wire your module. The following chapter describes how to configure your module to communicate on the EtherNet/IP network by providing an IP address, gateway address, and Subnet mask.

Publication 1732E-UM002A-EN-P - March 2010

16 Install Your Module

Notes:

Publication 1732E-UM002A-EN-P - March 2010

Configure the Module for Your EtherNet/IP Network

Introduction

Before using the 1732E EtherNet/IP ArmorBlock Supporting Sequence of Events in an EtherNet/IP network, configure it with an IP address, subnet mask, and optional Gateway address. This chapter describes these configuration requirements and the procedures for providing them. Here are the ways you can do this:

• Use the Rockwell BootP/DHCP utility, version 2.3 or greater, that ships

with RSLogix 5000 or RSLinx software. You can also use this utility to reconfigure a device whose IP address must be changed.

• Use a third party DHCP (Dynamic Host Configuration Protocol) server.

• Use the Network Address switches.

• Have your network administrator configure the module via the network

server.

See the table for a list of where to find specific information in this chapter.

Topic Page

Configuration Requirements 17 IP Address 18 Gateway Address 19 Subnet Mask 20 Use the Rockwell BootP/DHCP Utility 21 Save the Relation List 24 Use DHCP Software to Configure Your Module 24

Configuration Requirements

17 Publication 1732E-UM002A-EN-P - March 2010

Before you can use your module, you must configure its IP address, its subnet mask, and optionally, gateway address. You have the option to use the Rockwell BootP/DHCP utility, version 2.3 or greater, to perform the configuration. You also have the option to use a DHCP server or the network address switches to configure these parameters.

18 Configure the Module for Your EtherNet/IP Network

If the module needs to be reset to factory defaults, set the switches on the module to the value 888 and then cycle power to the module.

IMPORTANT

If using the BootP/DHCP utility, you will need to know the Ethernet hardware address of your module. Rockwell assigns each module a unique 48-bit hardware address at the factory. The address is printed on a label on the side of your module. It consists of six hexadecimal digits separated by colons. This address is fixed by the hardware and cannot be changed.

If you change or replace the module, you must enter the new Ethernet hardware address of the module when you configure the new module.

IP Address

The IP address identifies each node on the IP network (or system of connected networks). Each TCP/IP node on a network (including your module) must have a unique IP address.

The IP address is 32 bits long and has a net ID part and a Host ID part. Networks are classified A, B, C, (or other). The class of the network determines how an IP address is formatted.

Class A

Class B

Class C

Net ID

Host ID

15 16

Host ID

233124

Host ID

0 0

1 0 0 1 1 0

Net ID

You can distinguish the class of the IP address from the first integer in its dotted-decimal IP address as follows:

Classes of IP Addresses

Range of first integer Class Range of first integer Class

0…127 A 192…223 C

128...191 B 224…255 other

Each node on the same logical network must have an IP address of the same class and must have the same net ID. Each node on the same network must have a different Host ID thus giving it a unique IP address.

Publication 1732E-UM002A-EN-P - March 2010

Configure the Module for Your EtherNet/IP Network 19

IP addresses are written as four decimal integers (0...255) separated by periods where each integer gives the value of one byte of the IP address.

EXAMPLE

For example, the 32-bit IP address:

10000000 00000001 00000000 00000001 is written as

128.1.0.1.

Gateway Address

This section applies to multi-network systems. If you have a single network system, skip to the next section.

The gateway address is the default address of a network. It provides a single domain name and point of entry to the site. Gateways connect individual 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. The following figure shows gateway G connecting Network 1 with Network 2.

128.1.0.1

128.2.0.1

Network 1

128.2.0.2

Network 2

128.1.0.2

128.2.0.3

When host B with IP address 128.2.0.1 communicates with host C, it knows from C’s IP address that C is on the same network. In an Ethernet environment, B then resolves C’s IP address into a hardware address (MAC address) and communicates with C directly.

When host B communicates with host A, it knows from A’s IP address that A is on another network (the net IDs are different). In order to send data to A, B must have the IP address of the gateway connecting the two networks. In this example, the gateway’s IP address on Network 2 is 128.2.0.3.

The gateway has two IP addresses (128.1.0.2 and 128.2.0.3). The first must be used by hosts on Network 1 and the second must be used by hosts on Network 2. To be usable, a host’s gateway must be addressed using a net ID matching its own.

Publication 1732E-UM002A-EN-P - March 2010

20 Configure the Module for Your EtherNet/IP Network

Subnet Mask

The subnet mask is used for splitting IP networks into a series of subgroups, or subnets. The mask is a binary pattern that is matched up with the IP address to turn part of the Host ID address field into a field for subnets.

EXAMPLE

Take Network 2 (a Class B network) in the previous example and add another network. Selecting the following subnet mask would add two additional net ID bits, allowing for four logical networks:

11111111 11111111 11000000 00000001 = 255.255.192.0

These two bits of the host ID used to extend the net ID

Two bits of the Class B host ID have been used to extend the net ID. Each unique combination of bits in the part of the Host ID where subnet mask bits are 1 specifies a different logical network.

The new configuration is:

128.1.0.1

Network 1

128.1.0.2

Publication 1732E-UM002A-EN-P - March 2010

128.2.64.1

128.2.128.1

Network 2.1

128.2.128.2

Network 2.2

128.2.64.3

128.2.128.3

A second network with Hosts D and E was added. Gateway G2 connects Network 2.1 with Network 2.2. Hosts D and E use Gateway G2 to communicate with hosts not on Network 2.2. Hosts B and C use Gateway G to communicate with hosts not on Network 2.1. When B is communicating with D, G (the configured gateway for B) routes the data from B to D through G2.

Configure the Module for Your EtherNet/IP Network 21

Set the Network Address

The I/O block ships with the rotary switches set to 999 and DHCP enabled. To change the network address, you can do one of the following:

1. Adjust the switches on the front of the module.

2. Use a Dynamic Host Configuration Protocol (DHCP) server, such as

Rockwell Automation BootP/DHCP.

3. Retrieve the IP address from nonvolatile memory.

The I/O block reads the switches first to determine if the switches are set to a valid number. Set the network address by adjusting the 3 switches on the front of the module. Use a small blade screwdriver to rotate the switches. Line up the small notch on the switch with the number setting you wish to use. Valid settings range from 001…254.

Network Address Example

This example shows the network address set at 163

Use the Rockwell BootP/DHCP Utility

44233

When the switches are set to a valid number, the I/O block’s IP address is

192.168.1.xxx (where xxx represents the number set on the switches). The I/O block’s subnet mask is 255.255.255.0 and the gateway address is set to 0.0.0.0. When the I/O block uses the network address set on the switches, the I/O block does not have a host name assigned to it or use any Domain Name Server.

If the switches are set to an invalid number (for example, 000 or a value greater than 254, excluding 888), the I/O block checks to see if DHCP is enabled. If DHCP is enabled, the I/O block asks for an address from a DHCP server. The DHCP server also assigns other Transport Control Protocol (TCP) parameters.

If DHCP is not enabled, and the switches are set to an invalid number, the I/O block uses the IP address (along with other TCP configurable parameters) stored in nonvolatile memory.

The Rockwell BootP/DHCP utility is a stand alone program that incorporates the functionality of standard BootP/DHCP software with a user-friendly graphical interface. It is located in the Utils directory on the RSLogix 5000

Publication 1732E-UM002A-EN-P - March 2010

22 Configure the Module for Your EtherNet/IP Network

installation CD. The module must have DHCP enabled (factory default and the network address switches set to an illegal value) to use the utility.

To configure your module using the BootP/DHCP utility, perform the following steps:

1. Run the BootP/DHCP software.

The BOOTP/DHCP Request History dialog appears showing the hardware addresses of devices issuing BootP/DHCP requests.

2. Double-click the hardware address of the device you want to configure.

The New Entry dialog appears showing the device’s Ethernet Address (MAC).

3. Enter the IP Address you want to assign to the device and click OK.

Publication 1732E-UM002A-EN-P - March 2010

+ 102 hidden pages