Virtual Training Courses

(1)

Virtual Training Courses

(2)

Before We Begin

• Introductions

• All attendees are automatically muted with no video connection as a default.

• Please use the Q&A to ask questions, not the chat. We will address questions as they come in.

• At the end if there is time, we will take questions verbally from

the attendees. We will advise if and when there is time for you

to “raise your hand” if you have a question.

(3)

Technical Overview of CIP

The Common Industrial Protocol

Vivek Hajarnavis

Rockwell Automation

(4)

What is CIP?

• Complete suite of services for industrial automation

– Control

– Network management – Information

– Safety – Energy

– Synchronization and motion

• Object-based approach to designing control devices

– Consistent

– Interoperable

(5)

7

6

5

4

3

2

1 OSI Model

(Open Systems Interconnection)

APPLICATION

PRESENTATION

SESSION

TRANSPORT

NETWORK

DATA LINK

PHYSICAL

(6)

CIP

APPLICATION LAYER

OBJECT LIBRARY (Communications, Applications, Time Synchronization) DATA MANAGEMENT SERVICES (Explicit and I/O Messages)

Transport Network Data Link

CONNECTION MANAGEMENT, ROUTING

(7)

The EtherNet/IP Adaptation of CIP

OBJECT LIBRARY (Communications, Applications, Time Synchronization) DATA MANAGEMENT SERVICES (Explicit and I/O Messages)

TCP

Network (Internet Protocol) Data Link (CSMA/CD)

Physical Layer

UDP CONNECTION MANAGEMENT, ROUTING

FTP SMTP HTTP DNS APPLICATION LAYER OPC SNMP CIP

(8)

CIP Features

• Object-oriented

• Standardization through device profiles

• Seamless integration of networked devices

• Network independence

• Open

• Greater efficiency / flexibility

• Vendor-independent

(9)

CIP Device Profiles

Object Model

I/O Data Format

Configuration Data Format

Device

Profile

(10)

Device Profiles

• Define:

– Type of product

– Type of data available – Structure of data, etc.

• Enables device standardization

• Mechanism for

interoperability and interchangeability

• Ensures consistent behavior

– Among different vendors

– Among different networks

(11)

CIP Device Profiles (partial list)

✓ AC Drive

✓ CIP-Modbus Translator Device

✓ CIP Motion Device

✓ Communications Adapter

✓ Contactor

✓ DC Drive

✓ DC Power Generator

✓ Fluid Flow Controller

✓ General Purpose Discrete I/O

✓ Generic Device

✓ Human Machine Interface

✓ Inductive Proximity Switch

✓ Limit Switch

✓ Mass Flow Controller

✓ Motor Overload

✓ Motor Starter

✓ Photoelectric Sensor

✓ Pneumatic Valve

✓ Position Controller

✓ Process Control Valve

✓ Residual Gas Analyzer

✓ RF Power Generator

✓ Resolver

✓ Safety Discrete I/O Device

✓ Softstart Motor Starter

✓ Turbomolecular Vacuum Pump

✓ Vacuum Pressure Gauge

✓ System Architecture

45

Profiles

Defined and Maintained by

SIGs

(12)

CIP Device Profile Extensions

• Vendor-specific attributes

• Vendor-specific objects

• Profiles for:

– Vendor-specific

– Generic

(13)

Object Model

(14)

Traditional vs. Object Modeling

Traditional Software Design Object-Based Programing

Data Structures Functions

Processes

Attribute

Services

Behaviors

(15)

CIP Uses Object-Based Programming

• Defines the product from the network perspective

• Common object library provides consistency among devices

• Device is a collection of Objects

– Each object: a subset of overall device functionality

• Logically related attributes, services, and behaviors

• Each type of object belongs to a specific Class

– Classes: identified by a Class ID

(16)

General Format of a CIP Object Class

Reset( );

Create ( );

Services Attributes

CLASS

INSTANCES

Behavior

Idle Run Fault

GetAttr(inp) SetAttr(outp) Services

Attributes Behavior

Idle Fault

#1 int ClassRevision;

#4 int NumberOfInst;

#1 int status;

#2 sint value;

(17)

Attributes

Reset( );

Create ( );

Services Attributes

CLASS

INSTANCES

Behavior

GetAttr(inp) SetAttr(outp) Services

Attributes Behavior

#1 int ClassRevision;

#4 int NumberOfInst;

#1 int status;

#2 sint value;

(18)

Services

Reset( );

Create ( );

Services Attributes

CLASS

INSTANCES

Behavior

GetAttr(inp) SetAttr(outp) Services

Attributes Behavior

Idle Fault

#1 int status;

#2 sint value;

#1 int ClassRevision;

#4 int NumberOfInst;

(19)

Common CIP Services

✓ Get_Attributes_All

✓ Set_Attributes_All

✓ Get_Attribute_List

✓ Set_Attribute_List

✓ Reset

✓ Start

✓ Stop

✓ Create

✓ Delete

✓ Multiple Service Packet

✓ Apply_Attributes

✓ Get_Attribute_Single

✓ Set_Attribute_Single

✓ Find_Next_Object_Instance

✓ Restore

✓ Save

✓ No Operation (NOP)

✓ Get Member

✓ Set Member

✓ Insert Member

✓ Remove Member

The CIP See

Specification

for a complete list

of services

(20)

Behaviors

Reset( );

Create ( );

Services Attributes

CLASS

INSTANCES

Behavior

GetAttr(inp) SetAttr(outp) Services

Attributes Behavior

Idle Fault

#1 int ClassRevision;

#4 int NumberOfInst;

#1 int status;

#2 sint value;

(21)

Instances

Reset( );

Create ( );

Services Attributes

CLASS

INSTANCES

Behavior

GetAttr(inp) SetAttr(outp) Services

Attributes Behavior

#1 int ClassRevision;

#4 int NumberOfInst;

#1 int status;

#2 sint value;

(22)

Example of an Object Model

Object Class: Discrete Input Point

Value:

Status:

1 0 0

1 • • • • • • • • •

I/O Device Channel 1 Channel 8

Instances

Attributes

(23)

CIP Object Library

Communication Network Application

Identity

Message Router etc.

TCP/IP Interface Ethernet Link

Port etc.

Safety Motion Energy

I/O

etc.

(24)

Inside the

Object Model

Application object Application

object Application

object

Application Objects Identity

Object

Message Router

Assembly Object

Device

Network- specific Link object(s)

UCMM

Explicit

msg I/O

Connections

(25)

I/O

(26)

Producer / Consumer Model

Transmits data packets plus unique identifier that indicates packet content

Receives data by filtering the identifier to determine which packets to accept

PRODUCER CONSUMER

P1 P2

P3

P4

(27)

Message Types: Typical Uses

Explicit (TCP) Implicit (UDP)

Real-time I/O data

Functional safety data Motion control data Producer/Consumer Model

Configuration Diagnostics

Data collection

Connection establishment

(28)

Implicit Messaging Example

Client

I

O

I = Input Data O = Output Data

Independently

triggered based

on time

(29)

Explicit Messaging Example

Client

Server

M

(30)

Configuration

(31)

CIP Device Configuration

NETWORK

• Configure devices without switches

• Access all nodes from one tool

• Access and adjust parameters online PARAMETER EDS

Object ASSEMBLY

Object

(32)

Parameter Object: Resides in the Device

• Designed to drive user interface in tools

• One instance per configurable attribute

• Ranges, default values, and scaling

• Query with tools

• Doesn’t help with assembly structure or I/O connection configuration

• Becoming more widely used in CIP devices & provides

additional flexibility

(33)

Electronic Data

Sheets

EDS

I/O Data Structures

I/O Transfer Types

Configuration

Modular Constructs Network

Capacity Optional

Attributes

Parameters

(34)

CIP Technology Recap

(35)

Put It All Together

Object Model

I/O Data Format

Configuration Data Format

Device

Profile

(36)

Device Built on CIP

OBJECT LIBRARY (Communications, Applications, Time Synchronization) DATA MANAGEMENT SERVICES (Explicit and I/O Messages)

TCP

Network (Internet Protocol) Data Link (CSMA/CD)

UDP CONNECTION MANAGEMENT, ROUTING

FTP SMTP HTTP DNS APPLICATION LAYER OPC SNMP CIP

(37)

Benefits of CIP Application Layer

• Common and consistent

• Easier setup and

operation of multiple network

implementations

• Familiarity across all four networks and distinctive CIP

Services

(38)

Technical Overview of EtherNet/IP™

EtherNet/IP: CIP on Ethernet

Chatrapathi GV

Utthunga

(39)

Motor Control Profiles

Transducer

Profiles I/O Profiles Other Profiles Semiconductor Proflies

CIP Safety

^TM

Profiles

CIP Safety Object Library OBJECT LIBRARY

(Communications, Applications, Time Synchronization)

DATA MANAGEMENT SERVICES (Explicit and I/O Messages)

CONNECTION MANAGEMENT, ROUTING

TCP/UDP Internet Protocol EtherNet CSMA/CD EtherNet Physical Layer

C om m on In du str ia l P ro to co l (C IP

TM

) N etw ork A da pta tio n o f C IP CIP Motion

^TM

Profiles

CIP Safety Services &

Messages CIP Security

^TM

Profiles

CIP Sync

^TM

Object Library

CIP Security

^TM

Object Library CIP Energy

Object Library

CIP Security

^TM

Transports

(TLS, DTLS)

(40)

What is EtherNet/IP?

• Complete industrial Ethernet network solution for manufacturing automation

• Implementation of CIP over standard Ethernet

• Open network specified and maintained by ODVA

• Adheres to international standards (e.g., IEEE 802.3, ISO/IEC

8802-3, IEC 61784-5-2, and more)

(41)

Advantages of EtherNet/IP

• True, standard protocol

• Easy integration with existing Ethernet networks

• Easy on technology staff (IT/OT)

• COTS components

• Current with continuously evolving technology

(42)

EtherNet/IP Encapsulation:

TCP/IP Packet Structure

IP Data

IETF Scope

O SI M od el

APPLICATION PRESENTATION

SESSION

TRANSPORT NETWORK

TCP/UDP Header IP

Header IEEE 802

Scope TCP/UDP Data

Application App. Data

Header

Application Layer

Protocols CIP EtherNet/IP

Protocol EtherNet/IP

Encapsulation

(43)

Inside EtherNet/IP’s Encapsulation Layer

• The CIP data!

• EtherNet/IP defines a method of formatting the TCP payload to

transition from CIP to TCP

(44)

Encapsulation Session

Sets up TCP resources

• Opens a

socket using TCP/UDP Port 44818

Establish Session

• Creates linkage to part of product that handles CIP,

incoming

EtherNet/IP traffic

Uses Little- • Caution:

(45)

Explicit Messaging on EtherNet/IP

APPLICATION TRANSPORT

NETWORK

DATA LINK PHYSICAL

ICMP IGMP

RARP OSPF

ARP

IGRP

CIP Explicit Messaging

IP

HTTP OPC CIP

FTP SNMP ^BOOTP _DHCP

UDP TCP

IEEE 802.3 Ethernet

(46)

Connected vs. Unconnected Explicit Messages

Connected Explicit Unconnected Explicit

Message Sent Via Encapsulation session Encapsulation session Message Protocol TCP port 44818

TLS with TCP port 2221 for CIP Security

TCP port 44818

TLS with TCP port 2221 for CIP Security

Timeout Defined by CIP at connection establishment

Only depends on TCP timeouts (tens of seconds)

Allows for fault status? Yes, on connection timeout No Typical uses • Regular, periodic requests

• HMI parameter monitoring

• Occasional requests

• Connection establishment

(47)

Implicit Messaging on EtherNet/IP

APPLICATION TRANSPORT

NETWORK

DATA LINK PHYSICAL

ICMP IGMP

RARP OSPF

ARP

IGRP

CIP Implicit Messaging

IP

HTTP OPC CIP

FTP SNMP ^BOOTP _DHCP

UDP TCP

IEEE 802.3 Ethernet

(48)

Implicit Messages

Message Sent Via CIP implicit message connection

Message Protocol UDP, unicast / multicast with destination port 2222 DTLS, UDP, port 2221 for CIP Security

Timeout Defined during establishment

Allows for fault status? On connection timeout

• I/O Adapters: user-configured output states based on fault

• I/O Scanners: re-establish connections automatically

I/O Update Rate Cyclic, defined as requested packet interval (RPI)

Typical uses • Real-time I/O data (connection ID, run/idle header, sequence count and number)

• Functional safety data

(49)

EtherNet/IP Device Classes

Explicit Message Server

Explicit Message Client

I/O Adapter

(aka: Connection Target)

I/O Scanner (aka:

Connection Originator) Responds to

request/response oriented

communications initiated by explicit message clients The most basic EtherNet/IP

functionality that ALL devices must support

Initiates

request/response oriented

communications with other devices

Message rates and latency requirements are typically NOT demanding

Receives implicit

communication requests from I/O Scanner; then produces I/O data at requested rate

Supports Explicit Message Server functionality

Initiates implicit

communications with I/O Adapter devices Typically the most complex type of

EtherNet/IP device (deals with connections and I/O Adapter device

configurations)

Typically supports Explicit

Message Client

(50)

Key Terms and Relationships

• Connection Originator:

– Node responsible for opening a connection with other nodes

– Often called I/O Scanner

– Also acts as Explicit Client &

Explicit Server

• Connection Points:

– End points of a connection inside a device, typically an Assembly Object instance

• Connection Target:

– Node that receives connection request from Originator

– Often called I/O Adapter

– Also acts as Explicit Server

(51)

Key Terms: I/O Connection Types

• Point-to-Point (Unicast):

– I/O data transmitted to a single consuming device’s IP address; contains a Connection ID

• Multicast:

– I/O data transmitted to an IP multicast address; contains a Connection ID – IP multicast address exchanged between connection target and originator

during the connection establishment process

– Successive connection requests from other devices will receive the same multicast address

– I/O Adapters (producers) need to send I/O using multicast IP packets if user configures it

– I/O Scanners (consumers) need to receive multicast IP packets

– I/O Scanners must support IGMP to join IP Multicast Group (controls

propagation of multicast traffic)

(52)

Key Terms: I/O Connection Types – Exclusive Owner

– Connection to an Output connection point

• Only one I/O Scanner can control an I/O Adapter’s outputs

– May have a connection to an Input point

• If no Input, the I/O Adapter’s producing point is the Heartbeat connection point

I/O Scanner #1 I/O Adapter #1

C

P Point-to-Point

Outputs

Inputs or

(53)

Key Terms: I/O Connection Types – Input Only

– Connection to an Input connection point and a Heartbeat connection point

• No output data

– This connection type can stand alone

– The Heartbeat allows the I/O Adapter to timeout when communications is lost

I/O Scanner #1 I/O Adapter #1

C

C P

P Point-to-Point

Point-to-Point (can be Multicast)

Heartbeat

Inputs

(54)

Key Terms: I/O Connection Types – Input Only with Exclusive Owner

– Both are independent connections that share the input data from the I/O Adapter

• Input data sent using Multicast

– Heartbeat allows I/O Adapter to detect communications loss with Scanner #2

P C

C P

I/O Adapter #1

C

Point-to-Point

Multicast

Heartbeat Inputs Outputs

I/O Scanner #1

I/O Scanner #2

Exclusive Owner

(55)

Key Terms: I/O Connection Types – Listen Only

– Works like an Input Only connection except it depends on another connection (Exclusive Owner or Input Only)

• Other connection must be established first

– When other connection closes or times out, the Listen Only connection will time out and close

P C

C P

I/O Adapter #1

C C

P

Point-to-Point

Multicast

Heartbeat Inputs Outputs

I/O Scanner #1

I/O Scanner #2

Exclusive Owner

(56)

Connection Target Connection

Originator

Opening an I/O Connection on EtherNet/IP

Server Client

EtherNet/IP Network

Forward_Open Request/Response

Multicast and/or

(57)

Session and Connection Relationships

Relationship of TCP/IP, Encapsulation and CIP

I/O Adapter

TCP Connection Encapsulation Session

CIP Connected Explicit Messages

CIP Unconnected Explicit Messages

CIP Implicit (UDP) Data – I/O Connection

I/O Scanner

(58)

Thank you! Next sessions:

• CIP Safety Session 2: CIP Safety Overview: Today at 10:00 am – 11:30 am US Eastern

• EtherNet/IP Quick Start Session 2: Getting Started: Tomorrow at 8:00 am – 10:00 am US Eastern