Network Protocol PLCs

Field Bus Field Bus-Integrator

System Monitoring Sending local Information Monitor Critical Real Time Information Support power trading Reliable and Fast Communication Perform effective co-ordination through Communication Safe, secured and reliable transmission of information Protect information from Hacking or misuse

What is Protocol ?
When Intelligent Devices communicate with each other, there needs to be a common set of rules and instructions that each device follows.

A specific set of communication rules is called a protocol.

Address mapping

Routing

Loss of Information

Data Exchange

Basic Requirements Of Protocol

Flow Control

Detection of Transmission Error

Acknowle -dgement

Sequence Control

Protocols used in Electrical utilities

Modbus / Profibus

IEC 60870 series

UCA ( Utlity Communication Architecture ) IEC 61850 series DNP ( Distributed Network Protocol )

OSI Model

Functionality
7 LAYER System X
Application 7 6 5 4 3 2 1 System Y 7 6 5 4 3 2 1 Peer communication Protocols
Intermediate System A Intermediate System B

Presentation Session
Transport Network Data Link Physical

3 2

2
1

2
1

2
1

Physical Media

Physical Media

Physical Media

 Provides encapsulation of data Isolation from system and media

Due to many layers bandwidth goes higher Not suitable for SCADA

Proprietary
Protocol, used by the vendor, the utility is restricted to one supplier for support and purchase of future devices. This presents a serious problem. Examples of Proprietary Protocols are SPA, K-Bus etc.

Open
With the arrival of open systems concept, it is desired that devices from one vendor be able to communicate with those of other vendors i.e. devices should inter-operate. To achieve interoperability one has to use industry standard open protocols. Ex: IEC60870 -5-103,101,104, IEC61850,DNP,Modbus etc

Maximized flexibility Vendor independence Reliable product at optimized cost Easily available knowledge and specifications Lower costs of installation and maintenance A large market and thus opportunity to compete on price performance instead of technical details only. Cost effective project implementation Inter -operability Inter- changebility

Distributed Network Protocol 3.0

Based on earlier work of IEC TC57 Developed by GE Westronic, Inc. (now GE Harris) in 1990.

DNP 3.0 is an open protocol that was developed to establish interoperability between RTUs, IEDs (Intelligent Electronic Devices) and master stations. DNP was largely influenced by North and South America, together with the African and Asian regions as IEC 101 was from the European community.

The DNP 3.0 Basic 4 protocol specification document set was released into the public domain in 1993, and ownership of the protocol was given to the newly formed DNP Users Group in October 1993. DNP was specifically developed for use in Electrical Utility SCADA Applications. It is now the dominant protocol in electrical utility SCADA systems, and is gaining popularity in other industries, including Oil & Gas, Water, and Waste Water. DNP is based on the earlier work of IEC TC 57 DNP is byte-oriented protocols. DNP contains Application and Data Link Layers, with a pseudo-transport layer. DNP protocol is widely used over a variety of physical layers, including RS-232, RS-422, RS-485, and TCP/IP. With DNP, the protocol is simply encapsulated within TCP/IP. It is based on Enhanced Performance architecture ( EPA) model

Three Layered Protocol (EPA)

Application (Layer 7) Data Link Physical (Layer 2) (Layer 1)

This structure is similar to IEC. However, DNP3 enhances EPA by

adding a fourth layer, a pseudo transport layer that allows for message segmentation.

PROTOCOL

STRUCTURE
7-Layer 3-Layer
Application

Application Presentation Session Transport Network Data Link Physical

Data Link Physical

OSI

EPA

In addition Pseudo Transport Layer (Layer 4) DNP introduces a pseudo-transport layer(OSI Layer 4) to build application data messages larger than a single data link frame. In case of IEC, each 101 message should be contained in a single data link frame.

SUPPORT ADVANCE RTU FUNCTION

PROTOCOL STRUCTURE for IP based Open Protocols

IEC, DNP, UCA (and even MODBUS) standards are successfully able to adopt TCP/IP based Ethernet based technology for substation automation.

IEC 61850 (UCA2) DNP3/TCP IEC 104 Application Presentation Session TCP/UDP IP IEEE 802.1 IEEE 802.3

}TCP/IP }Ethernet

Transport Network Data Link

Physical

Why 3-Layered Structure of EPA?

1) Short Reaction Time 2) Reduced Transmission Bandwidth
BW: Measure of capacity of a transmission system. Measured in Hertz. How fast data can flow on a given transmission path. In Digital data transmission, BW is expressed

as data speed in bits per second. Thus, higher

the BW, more data can be transmitted.

In 1994, the IEEE Power Engineering Societys Data Acquisition, Monitoring and Control Subcommittee formed a Task Force to review the communication protocols being used between Intelligent Electronic Devices (IEDs) and Remote Terminal Units (RTUs) in substations The IEEE Task Force found a very confusing, constantly changing environment that was increasing the cost and time to completion of substation SCADA systems. The IEEE Task Force collected information on approximately 140 protocols and compared them to a list of communication protocol requirements. This comparison resulted in a short list of protocols that met most of the requirements. This short list was balloted and two serial SCADA protocols tied for being the most acceptable: IEC 60870-5-101 and DNP3.

 DNP3 is an open, intelligent, robust, and efficient modern SCADA protocol. It can request and respond with multiple data types in single messages, segment messages into multiple frames to ensure excellent error detection and recovery, include only changed data in response messages, assign priorities to data items and request data items periodically based on their priority, respond without request (unsolicited), support time synchronization and a standard time format, allow multiple masters and peer-to-peer operations,and allow user definable objects including file transfer. Details of Communication Interface supported. DNP Levels Supported. Data Scaling Range if any? Data Retrieval Method supported (unsolicited/polled static/exception). Object Type & variations supported. Data Map (Index number ) of each parameter.

 Waste water management

Oil and gas industries

Traffic management Power system automation Other industries