02 Legacy Communication Protocols PDF
02 Legacy Communication Protocols PDF
02 Legacy Communication Protocols PDF
PTSS ENGINEERS
Legacy Protocols
ABB, Peenya in
15 June, 2005 Substation Automation
© ABB Ltd. PTUA-SA - 1
Rajiv Krishnan
ABB Limited, Bangalore
2005-06-10
ABB
Substation Automation Systems
Thus, the need arose for efficient communication among the IEDs using
appropriate protocols.
© ABB Ltd. PTUA-SA - 2
2005-06-10
ABB
Why Automation?
To manage
• Hazardous operation
• Repetitive operation
• Complex operation
To have
• Faster response
• Quicker decisions
• Faster restoration after breakdown
© ABB Ltd. PTUA-SA - 3
2005-06-10
ABB
Why Automation?
Benefits
ABB
Why Automation?
To supply the power meeting the power quality standards:
The electrical utility should meet the above with optimum economy
© ABB Ltd. PTUA-SA - 5
2005-06-10
ABB
Data Exchange in a Substation Automation System
Monitored Information:
ABB
Data Exchange in a Substation Automation System
Control Information:
ABB
What is a Protocol?
Protocol:
Set of rules that determines the behavior of functional units in achieving and
performing communication.
Open Protocol:
A communication protocol whose stack is either standardized or publicly
available.
ABB
OSI Layer Reference Model Protocol Stack
The OSI Model
OSI is a well-known hierarchical framework for
implementing communications protocols. It serves as
7 Application the worldwide foundation for interoperability between
networking products.
6 Presentation
5 Session The OSI architecture consists of seven functional
4 Transport sections known as layers. Each layer is cleverly
defined to hand off control over data to the layer
3 Network directly above and the layer directly below.
2 Data Link
1 Physical OSI is really a reference model that manufacturers
work from. Compliance is voluntary, but most
vendors’ products provide some subset of OSI
functionality.
© ABB Ltd. PTUA-SA - 9
2005-06-10
ABB
OSI Layer Reference Model Protocol Stack
APPLICATION LAYER:
This top layer, the easiest one to access in the OSI model,
defines the way in which applications, including e-mail,
7 Application file transfer and client/server software, communicate with
each other.
6 Presentation
PRESENTATION LAYER:
5 Session
This layer governs the way data is presented. Essentially,
4 Transport it translates messages between nodes (stations on the
3 Network network), using text compression, security encryption and
other forms of data conversion.
2 Data Link
1 Physical SESSION LAYER:
This layer coordinates communications by managing the
interaction between an end user and a resource on the
network. In other words, it keeps everything tidy and
© ABB Ltd. PTUA-SA - 10
ABB
OSI Layer Reference Model Protocol Stack
TRANSPORT LAYER:
This layer polices data integrity and validity across
the network. It breaks up large messages into
7 Application smaller packets (also known as frames) that can be
sent by the Data Link Layer below. It also detects
6 Presentation any lost packets and confirms the delivery of a
5 Session complete message at the receiving end.
4 Transport
NETWORK LAYER:
3 Network This layer controls the routing of messages across
2 Data Link different networks. Routable network protocols have
1 Physical a network address and a node address so packets can
be forwarded across the entire network. The
Network Layer also controls flow and traffic
management.
© ABB Ltd. PTUA-SA - 11
2005-06-10
ABB
OSI Layer Reference Model Protocol Stack
DATA LINK LAYER:
This layer is the mechanism used to synchronize and
control the exchange of data from node to node and
7 Application check errors in the information received. At this layer,
data transmits in topology-specific frames, such as
6 Presentation Ethernet or token ring frames.
5 Session
4 Transport PHYSICAL LAYER:
This lowest layer is charged with passing data to and
3 Network from the physical media that connect nodes. It deals
2 Data Link with the wire, the network adapter, the electrical
1 Physical signals, etc., and controls the flow of information
between devices.
© ABB Ltd. PTUA-SA - 12
2005-06-10
ABB
Steps of communication
“Switch CB in
bay 1 on "
© ABB Ltd. PTUA-SA - 13
2005-06-10
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
information
© ABB Ltd. PTUA-SA - 18
2005-06-10
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
ABB
Steps of communication
“Switch CB in
bay 1 on "
Electric signals
2005-06-10
ABB
Steps of communication
Application-program
Structure
Encoding
Communication-
control
Transport-control
additional
information Routing
Error-detection
Electric signals
2005-06-10
ABB
OSI-Layer-Model
7 Application Layer
Structure
Encoding 6 Presentation Layer
Communication- 5 Session Layer
control
Transport-control 4 Transport Layer
additional
information Routing 3 Network Layer
Error-detection 2b Logical Link Control Layer
Access to the bus 2a Medium Access Control Layer
© ABB Ltd. PTUA-SA - 24
ABB
IEC 60870-5 Protocols
IEC Technical Committee 57 (working group 03) has defined a standard for
relatively simple, bit serial communication: IEC 60870-5.
The standard is optimized for efficient and reliable transfer of process data
and commands to and from geographically widespread systems over low-
speed (up to 64 kbps) fixed and dial-up connections.
ABB
IEC 60870-5 Protocols
Protocol Standards and Companion Standards
ABB
IEC 60870-5 Protocols
Protocol Standards
IEC 60870-5-1 Transmission Frame Format
(Specifies standards for the Physical and Data Link Layers)
Data Integrity classes I1, I2 and I3 defined with Hamming distance of 2 for I1 and
Hamming distance of 4 for I2 and I3. The Hamming distance can be interpreted as the
number of bits which need to be changed (corrupted) to turn one string into the other.
With Bit Error Rate of 10-4 I1 I2 I3
Mean Time Between Undetected Errors 1 day 26 Years 260000 Years
Residual error rate 10-6 10-10 10-14
Baud rates : Up to 19200 bauds
Service classes: S1 – Send / No response; S2 – Send / Confirm; S3 – Request / Respond
Addresses: Single address, Group address, Global address
Frame Formats
FT1.1 : 8 bit data + parity + start and stop bits (HD of 2)
FT1.2 : FT1.1 frame with frame checksum (HD of 4)
© ABB Ltd. PTUA-SA - 27
ABB
IEC 60870-5 Protocols
ABB
Format Type FT1.2
Supports both Fixed length and variable length frames
0 0 0 0 0 1 0 0 0 1 1 Start Character
0 U S E R D A T A P 1 User Data
0 C H E C K S U M P 1 Frame Checksum
0 0 1 1 0 1 0 0 0 1 1 End Character
SB 0 1 2 3 4 5 6 7 EP Stop
Start Character
Variable length messages 0 0 0 0 1 0 1 1 0 1 1
0 - L E N G T H - P 1 Length
0 - L E N G T H - P 1 Length (repeated)
0 0 0 0 1 0 1 1 0 1 1 Start Character
0 U S E R D A T A P 1 User Data
- - - - - - - - - - -
- - - - - - - - - - -
0 U S E R D A T A P 1 User Data
© ABB Ltd. PTUA-SA - 29
0 C H E C K S U M P 1 Frame Checksum
0 0 1 1 0 1 0 0 0 1 1 End Character
2005-06-10
ABB
IEC 60870-5 Protocols
Protocol Standards
Length – one octet (repeated) [range from 0 to 255, length of user data]
User Data consists of Control, Address and Link User data
Control – one octet
Address - one or more octet (to be agreed by both sides)
© ABB Ltd. PTUA-SA - 30
2005-06-10
ABB
IEC 60870-5 Protocols
Protocol Standards
• IEC 60870-5-3 General Structure of Application Data
Specifies rules for structuring application data units in transmission frames
Compatibility between devices of different suppliers can only be reached by defining
the complete application profiles
• IEC 60870-5-4 Definition and Coding of Application Information Elements
Specifies rule for defining information elements and presents a set of information
elements that are frequently used in telecontrol applications
• IEC 60870-5-5 Basic Application Functions
It defines the basic application functions that perform standard procedures for
telecontrol applications. This serves as a basic standard for the different companion
standards.
Examples - Command transmission, event transmission, cyclic transmission, etc.,
Information Level 1:
Monitored information, Control information, Parameters, File transfer
© ABB Ltd. PTUA-SA - 31
Application functions not defined here are defined in the companion standards.
2005-06-10
ABB
IEC 60870-5 Protocols
Companion Standards
ABB
IEC 60870-5 Protocols
IEC 60870-5-101 for basic telecontrol tasks
ABB
IEC 60870-5 Protocols
IEC 60870-5-102 transmission of integrated totals in electric power systems
ABB
IEC 60870-5 Protocols
IEC 60870-5-103 for informative interface of protection equipment
ABB
IEC 60870-5 Protocols
IEC 60870-5-104, network access for IEC 60870-5-101
ABB
DNP 3.0 Protocol
Protocol for transmission of data from Point A to Point B using serial communication
Developed by Westronics Inc., Canada based on IEC 60870-5 standards.
Now available to anyone through the DNP Users Group
Initially developed for permanent directly connected data circuits and supports Point-
to-point, multidrop and hierarchical networks
Later a psuedo Transport Layer (incorporated in the Application Layer) was added to
make it compatible for use over a LAN
Spontaneous transmission of messages (for peer-to-peer communication) is
supported, but the implementation of the algorithm is left to the implementer
© ABB Ltd. PTUA-SA - 37
2005-06-10
ABB
DNP 3.0 Protocol
DNP 3 Frame
A DNP3 frame consists of a header and data section.
Header Data
Header
Sync Length Link Control Dest. Source CRC
Address Address
The header specifies the frame size, which DNP3 station should receive the frame,
which DNP3 device sent the frame and data link control information. The data
section is commonly called the payload and contains the data passed down from
the layers above.
Every frame begins with two sync bytes that help the receivers determine where
the frame begins. The length specifies the number of octets in the remainder of the
frame, not including CRC check octets. The link control octet is used between
© ABB Ltd. PTUA-SA - 38
ABB
DNP 3.0 Protocol
A destination address specifies which DNP3 device should process the data, and the
source address identifies which DNP3 device sent the message. Having both
destination and source addresses satisfies at least one requirement for peer-to-peer
communications because the receiver knows where to direct its responses.
65520 individual addresses are available. Every DNP3 device must have a unique
address within the collection of devices sending and receiving messages to and from
each other. Three destination addresses are reserved by DNP3 to denote an all-call
message; that is, the frame should be processed by all DNP3 devices. Thirteen
addresses are reserved for special needs in the future.
The data payload in the link frame contains a pair of CRC octets for every 16 data
octets (Frame Format FT3 as defined in IEC 60870-5). This provides a high degree
of assurance that communication errors can be detected (Integrity Class I3).
The maximum number of octets in the data payload is 250, not including CRC octets.
(The longest link layer frame is 292 octets if all the CRC and header octets are
© ABB Ltd. PTUA-SA - 39
counted.)
2005-06-10
ABB
DNP 3.0 Protocol
DNP3 over LAN:
It is possible to use TCP/IP to transport DNP3 messages in lieu serial lines. Link
layer frames are embedded into TCP/IP packets. This approach has enabled DNP3 to
take advantage of Internet technology and permitted economical data collection and
control between widely separated devices.
The link layer has the responsibility of making the physical link reliable. It does this
by providing error detection and duplicate frame detection. The link layer sends and
receives packets or frames. Sometimes transmission of more than one frame is
necessary to transport all of the information from one device to another.
A feature of DNP3's link layer is the ability for the transmitter of the frame to request
the receiver to confirm that the frame arrived. Using this feature is optional, and it is
often not employed.
© ABB Ltd. PTUA-SA - 40
2005-06-10
ABB
DNP 3.0 Protocol
DNP3 over LAN:
It is the responsibility of the transport layer to break long messages into smaller
frames sized for the link layer to transmit, or when receiving, to reassemble frames
into the longer messages.
In DNP3 the transport layer is incorporated into the application layer. The transport
layer requires only a single octet within the message to do its work. Therefore, since
the link layer can handle only 250 data octets, and one of those is used for the
transport function, then each link layer frame can hold as many as 249 application
layer octets.
Application layer messages are broken into fragments. Fragment size is determined
by the size of the receiving device’s buffer. It normally falls between 2048 and 4096
bytes. A message that is larger than a one fragment requires multiple fragments.
Fragmenting messages is the responsibility of the application layer.
© ABB Ltd. PTUA-SA - 41
2005-06-10
ABB
DNP 3.0 Protocol
DNP3 over LAN:
In DNP3, the term static is used with data and refers to the current value. Thus static
binary input data refers to the present on or off state of a bi-state device. Static
analog input data contains the value of an analog at the instant it is transmitted. One
possibility DNP3 allows is requesting some or all of the static data in a slave device.
DNP3 event occurs when a binary input changes from an on to an off state or when
an analog value changes by more than its configured deadband limit. DNP3 provides
the ability to report events with and without time stamps so that the client can
generate a time sequence report.
DNP3 classifies events into three classes. When DNP3 was conceived, class 1 events
were considered as having higher priority than class 2 events, and class 2 were higher
than class 3 events. The user layer can request the application layer to poll for class
1, 2 or 3 events or any combination of them.
© ABB Ltd. PTUA-SA - 42
2005-06-10
ABB
LON Protocol
A LON network uses the LONWORKS protocol, also known as the ANSI/EIA 709.1
Control Networking Standard.
In some ways the LON network resembles a computer data network (LAN) using
protocols like TCP/IP.
A control network allows a number of intelligent devices to communicate directly
with each other, without the need for a supervisory controller to poll each device and
retransmit the information to other devices. This is the difference between a peer-to-
peer communication and master slave communication.
Control networks have a number of unique requirements that make them different
from data networks. These include the following:
•Frequent, reliable, secure communication between devices
•Short message formats for information being passed
•Peer-to-peer functionality for every device
© ABB Ltd. PTUA-SA - 43
2005-06-10
ABB
LON Protocol
The LONWORKS protocol, also known as the LONTALK protocol, provides a set
of communication services that allow application programs in a device to send and
receive messages from other devices over the network without needing to know the
topology of the network or the names, addresses or functions of the other devices.
The LONWORKS protocol is a layered, packet based, peer-to-peer communication
protocol that adheres to the layered architectural guidelines of the ISO OSI reference
model.
By tailoring the protocol for control at each of the OSI layers, the LONWORKS
protocol provides a control specific solution that provides the reliability,
performance and robust communication required for control applications.
© ABB Ltd. PTUA-SA - 44
2005-06-10
ABB
LON Protocol
Summary of services provided by each layer:
1. The physical layer defines the transmission of raw bits over a communication
channel. The physical layer ensures that a 1 bit transmitted by a source device is
received as a 1 bit by all destination devices.
2. The link layer defines media access methods and encoding to ensure efficient
use of single communication channel. The raw bits of the physical layer are
broken up into data frames. The link layer defines when a source device can
transmit a data frame, defines how destination devices receive data frames and
detect transmission errors. A priority mechanism is also defined to ensure
delivery of important messages.
3. The network layer defines how message packets are routed from a source
device to one or more destination devices. This layer defines naming and
addressing of devices to ensure the correct delivery of packets. This layer also
defines how messages are routed between the source and destination devices
when these devices are on different communication channels.
© ABB Ltd. PTUA-SA - 45
2005-06-10
ABB
LON Protocol
Summary of services provided by each layer (contd.):
4. The transport layer ensures reliable delivery of message packets. Messages
can be exchanged using an acknowledged service, where the sending device
waits for an acknowledgement from the receiver and resends the message if the
acknowledgement is not received. The transport layer also defines how
duplicate messages are detected and rejected if a message is resent due to lost
acknowledgement.
5. The session layer adds control to the data exchanged by the lower layers. It
supports remote actions so that a client may make a request to a remote server
and receive a response to this request. It also defines an authentication protocol
that enables receivers of a message to determine if the sender is authorized to
send the message.
© ABB Ltd. PTUA-SA - 46
2005-06-10
ABB
LON Protocol
Summary of services provided by each layer (contd.):
6. The presentation layer adds structure to the data exchanged by the lower
layers by defining the encoding of message data. Messages may be encoded as
network variables, application messages, or foreign frames. Interoperable
encoding of network variables is provided with standard network variable types
(SNVTs).
7. The application layer adds application compatibility to the data exchanged by
the lower layers. Standard objects promote interoperability by ensuring that
applications use a common semantic interpretation of the data exchanged by
lower layers. The application layer also defines a file transfer protocol that is
used to transfer streams of data between applications.
© ABB Ltd. PTUA-SA - 47
2005-06-10
ABB
LON Protocol
MEDIA ACCESS
All network protocol use a media access control (MAC) algorithm to allow devices
to determine when they can safely send a packet of data. MAC algorithms are
designed either to eliminate or minimize collisions.
The LONWORKS protocol uses a unique MAC algorithm called the predictive p-
persistent CSMA protocol that has excellent performance characteristics even
during periods of network overload.
In LONWORKS protocol, devices randomize over a minimum of 16 different levels
of delay called Beta 2 slots. The number of available Beta 2 slots varies from 16 to
1008, depending on the network loading estimate.
This method allows LONWORKS protocol to minimize media access delays during
periods of light load, while minimizing collisions during periods of heavy load.
© ABB Ltd. PTUA-SA - 48
2005-06-10
ABB
LON Protocol
ADDRESSING
The addressing algorithm defines how packets are routed from a source device to one
or more destination devices. Packets can be addressed to single device, to any group
of devices, or to all devices.
Following are the LONWORKS address types:
Physical Address – Unique 48 bit identifier called Neuron ID
Device Address – Domain ID, Subnet ID and Node ID
Group Address – a logical collection of devices in a domain
Broadcast Address – all devices in a subnet or in a domain
Every LONWORKS packet transmitted over the network contains the device address
of the transmitting device (the source address) and the address of the receiving
device (the destination address) that can either be a physical address, a device
address, a group address, or a broadcast address.
© ABB Ltd. PTUA-SA - 49
2005-06-10
ABB
LON Protocol
MESSAGE SERVICES
• Acknowledged Messaging
• Repeated Messaging
• Unacknowledged Messaging
• Authenticated Messaging
NEURON CHIP
In order to achieve economical and standardized deployment, Echelon designed the
Neuron Chip. It includes three processors that provide both communication and
application processing capabilities.
It provides the first six layers of the ISO OSI reference model. Only the application
layer programming and configuration needs to be added.
© ABB Ltd. PTUA-SA - 50
2005-06-10
ABB
Development of Ethernet
X.25 – High Speed Communication, using Packet Switching, standardized
in 1976 was the first step towards development of LAN.
Xerox teamed up with Digital and Intel to publish the first public
specification for physical network communication in 1980.
The Ethernet specification (then called DIX – Digital, Intel, Xerox) defined
the cable, connectors and electrical characteristics used for communicating.
It specified a network speed of 10 megabits per second (10Mbps).
ABB
IEEE 802 Standards
The IEEE 802 set of standards govern networking and address the bottom
two layers of the OSI model – the Physical Layer and the Data Link Layer.
In an IEEE 802 protocol, the Data Link layer is broken down into two sub-
layers.
The Media Access Control (MAC) sub-layer arbitrates the access to physical
transmission media on a LAN (provided through the Physical layer). The
MAC is also responsible for identifying and using the physical node
addresses of each device on a network.
Logical Link Control (LLC) is the top sub-layer of the Data Link Layer.
LLC serves as the link between software entities known as service access
points, providing a common interface to the MAC sub-layer.
© ABB Ltd. PTUA-SA - 52
2005-06-10
ABB
IEEE 802 Standards
802.1
Specifies how internetworking is achieved; addresses network management.
802.2
Defines an interface between low-level hardware and high-level software,
such as device drivers and the network operating system.
802.3
Describes a physical bus using CSMA/CD as the access method; modeled
after and popularized by the Ethernet standard.
ABB
IEEE 802 Standards
802.4
Describes a physical bus using token passing as the access method.
802.5
Describes a physical ring using the token passing access method at 4 or
16Mbps; popularized by IBM Token Ring.
802.6
Specifies how metropolitan area networks (MANs) are implemented.
© ABB Ltd. PTUA-SA - 54
2005-06-10
ABB
TCP / IP
TCP/IP was developed by the US Department of Defence to connect a
number different networks designed by different vendors into a network of
networks (the "Internet").
ABB
TCP / IP
TCP
TCP is a connection-oriented transport protocol that sends data as an
unstructured stream of bytes.
By using sequence numbers and acknowledgment messages, TCP provides a
sending node with delivery information about packets transmitted to a
destination node. Where data has been lost in transit from source to
destination, TCP retransmits the data until either a timeout condition is
reached or until successful delivery has been achieved.
TCP adds support to detect errors or lost data and to trigger retransmission
until the data is correctly and completely received. TCP also recognizes
duplicate messages and will discard them appropriately.
If the sending computer is transmitting too fast for the receiving computer,
TCP employs flow control mechanisms to slow data transfer. TCP also
communicates delivery information to the upper-layer protocols and
© ABB Ltd. PTUA-SA - 56
applications it supports.
2005-06-10
ABB
TCP / IP
IP
IP is the primary layer 3 protocol in the Internet suite. In addition to
internetwork routing, IP provides error reporting and fragmentation and
reassembly of information units called datagrams for transmission over
networks with different maximum data unit sizes. IP represents the heart of
the Internet protocol suite.
ABB
TCP / IP
An IP address is divided into three parts. The first part designates the
network address, the second part designates the subnet address, and the third
part designates the host address. IP addressing supports three different
network classes.
Class A networks are intended mainly for use with a few very large
networks, because they provide only 8 bits for the network address field.
Class B networks allocate 16 bits, and Class C networks allocate 24 bits for
the network address field. Class C networks only provide 8 bits for the host
field, however, so the number of hosts per network may be a limiting factor.
In all three cases, the leftmost bit(s) indicate the network class.
IP network can be divided into smaller parts called subnets to provide
greater flexibility to the administrator. Messages to hosts in the same subnet
are sent directly, while messages to external hosts are sent through a router.
© ABB Ltd. PTUA-SA - 58
2005-06-10
ABB
© ABB Ltd. PTUA-SA - 59
2005-06-10
ABB