This webinar brought to you by the Relion® product family

Advanced protection and control IEDs from ABB

Relion. Thinking beyond the box.

Designed to seamlessly consolidate functions, Relion relays are
smarter, more flexible and more adaptable. Easy to integrate and
with an extensive function library, the Relion family of protection
and control delivers advanced functionality and improved
performance.
ABB Protective Relay School Webinar Series
Disclaimer
ABB is pleased to provide you with technical information regarding
protective relays. The material included is not intended to be a complete
presentation of all potential problems and solutions related to this topic.
The content is generic and may not be applicable for circumstances or
equipment at any specific facility. By participating in ABB's web-based
Protective Relay School, you agree that ABB is providing this information
to you on an informational basis only and makes no warranties,
representations or guarantees as to the efficacy or commercial utility of
the information for any specific application or purpose, and ABB is not
responsible for any action taken in reliance on the information contained
herein. ABB consultants and service representatives are available to
study specific operations and make recommendations on improving
safety, efficiency and profitability. Contact an ABB sales representative
for further information.

l Slide 2
September 17,
2015
ABB Protective Relay School Webinar Series

Intro to communication architectures

in a substation environment
Galina Antonova
September 17, 2015
Presenter

Galina Antonova is with ABB Substation Automation and

Communication group, North America. She has over 15
years of experience in the area of electrical engineering,
data communications and time synchronization, which she
mainly applied to the power industry. In her current role
Galina Antonova with ABB, Galina is applying her expertise to substation
automation and protective relaying applications. Galina
received her M. Sc. degree (1993) and a Ph.D. (1997) in
Electrical Engineering and Data Communications from the
State University of Telecommunications, St. Petersburg,
Russia, and spent one year at University of British
Columbia (UBC) on a scholarship from the Russian
President. She is actively involved with IEEE PSRC and is
a Canadian member of the IEC TC57 WG10.

© ABB Inc.
September 17, 2015 | Slide 4
Learning objectives

 Communication interfaces
 Serial: RS-232, RS-485
 Ethernet/IP
 Communication media
 Copper
 Fiber
 Wireless
 Application protocols / communication rules
 Modbus
 DNP
 IEC 61850

© ABB Group
September 17, | Slide 5
2015
What is RS-232?
Definition

NODE

 Found in many format, mainly 9/25 pin, but RJ-45 has been used.
 RS-232 is a point to point connection network.
 It is voltage based (referenced to a single common return [ground]).
 Relays may have multiple RS-232 ports.
 Usually one reserve for local programming (front port).
 It is the most commonly used electrical interface.
 It is a TIA (Telecommunications Industry Association) standard.
 It was originally developed on EIA subcommittee TR30.2 on interface.
 Latest revision as of July 2009 is TIA-RS232-F

© ABB Group
September 17, | Slide 6
2015
Typical RS-232 devices

POINT TO POINT

B A A A
VALUE

RADIO FREQUENCY MODEMS

RS-232

EC

RS-232
The Cloud.
RING WITH FIBER OPTIC MODEMS EC
B A A A
VALUE
EC

RS-232 RS-232

RS-232 B A
A VALUE
A

© ABB Group
September 17, 2015 | Slide 7
RS-232 ANSI Specification

 2 Emulations
 DTE- Date Terminal Equipment
 Example: personal computer

 DCE- Data Communication Equipment

 Example: modem (automatic calling equipment)

© ABB Group
September 17, | Slide 8
2015
Electrical levels

 Voltage is Negative
 Binary State = 1 +15 VDC
 Signal Condition -3V to -15V
 Mark. +3 VDC
 Voltage is Positive
 Binary State = 0
0VDC Intermediate Region
-3 VDC
 Signal Condition +3 to + 15 V
 Space. - 15 VDC

 Transition/Intermediate Region -3V to + 3V

© ABB Group
September 17, 2015 | Slide 9
Speed RS-232

 Modern speeds are from:

 110 baud (not really used).
 115.2 K baud.

 A baud is a bit representation.

 One baud does not necessarily mean 1 bit.
 One baud means one change of state of the line.
 Baud rate = 9600 = 1 changes of every state 100 micro
seconds.

© ABB Group
September 17, | Slide 10
2015
RS-232 Connector

 Connector style is not specified

 Originally specified for 25 pins.
 IBM developed de-facto standard of 9 pins.

 Physical Interface Connector

 DB-25
 DB-9
 Screw terminals
 RJ-11 telephone connectors
 RJ-45 Ethernet connectors

© ABB Group
September 17, | Slide 11
2015
RS-232 DB-25 wiring diagram

DTE DCE
1 - Protective Ground 1 - Protective Ground
2 - Transmitted Data 2 - Transmitted Data
3 - Received Data 3 - Received Data
4 - Request To Send 4 - Request To Send
5 -Clear To Send 5 -Clear To Send
6 - Data Set Ready 6 - Data Set Ready
7 - Signal Ground -Common Return 7 - Signal Ground -Common Return
8 - Data Carrier Detect 8 - Data Carrier Detect
20 - Data Terminal Ready 20 - Data Terminal Ready
22 - Ring Indicator 22 - Ring Indicator

RTS - Space = Transmit mode Mark = Receive Mode

CTS - Space = Send Data Mark = Do Not Send Data
DSR - Space = Device Off Hook Mark = Device ON Hook
DTR - Space = Device On Line Mark = Device Off Line
DCD - Space = Good Data Mark = Error In Data
RI - Mark = Phone Ringing Space = Not Ringing

NOTE: both RTS/CTS and DTR/DSR are rarely used

© ABB Group
September 17, 2015 | Slide 12
RS-232 Physical Interface

 Signal
 Transmit (TX)
 Receive (RX)
 Ground (GND)

 Control
 Clear To Send (CTS)
 Request To Send (RTS)
 Data Set Ready (DSR)
 Data Terminal Ready (DTR)
 Carrier Detect (CD)

© ABB Group
September 17, | Slide 13
2015
RS-232 (DB-9)

DTE ( )
9 Pin DCE
DTE DCE
2 - TX RX - 2
3 - RX TX - 3
4 - DTR DTR - 4
Note: If both devices are 5- GND GND - 5
DTE’s or DCE’s 6 - DSR DSR - 6
re-pin the cable as 7 - RTS RTS - 7
necessary! 8 - CTS CTS - 8
50 feet cable length maximum

© ABB Group
September 17, 2015 | Slide 14
 WHAT HAPPENS IF I NEED
TO CONNECT DTE/DTE
OR DCE/DCE RELAYING?
NULL MODEM

© ABB Group
September 17, | Slide 15
2015
What is a Null Modem?

NODE A NODE B
2 TD 2 TD
3 RD 3 RD
5 GND 5 GND
7 RTS 7 RTS
8 CTS 8 CTS
4 DTR 4 DTR
6 DSR 6 DSR

There are times when handshaking is required by the software and not by
the hardware.

© ABB Group
September 17, 2015 | Slide 16
RS-232
Advantages/Disadvantages

 Advantages
 Easy to implement
 Easy to troubleshoot
 Designed for “long-range” communication equipment

 Disadvantages
 Susceptible to noise
 Relativity short distances
 Designed for single devices

© ABB Group
September 17, | Slide 17
2015
RS-485

In Contrast to RS-232, RS-485 allows interconnection of multiple devices.

NODE NODE NODE NODE NODE NODE

 Advantages
 Easy to implement
 High expandability
 Less Susceptible to noise
 Disadvantages
 Higher wiring costs
 More difficult to troubleshoot

© ABB Group
September 17, 2015 | Slide 18
An IBM PC has an RS-232 Port

RS-485

NODE NODE NODE NODE NODE NODE

RS-232
CONVERTER

 A converter may be needed to transform the RS-232 Interface to an

RS-485 Interface
 Many manufacturers of interfaces are available.

© ABB Group
September 17, 2015 | Slide 19
RS-485
 2 Variants of RS-485
 2 Wire (Half Duplex)
TX = TX +
TX – TX-

RX + RX +
RX – RX –
REF REF

 4 Wire ( Full Duplex)

TX = RX +
TX – RX-

RX + TX +
RX – TX –
REF REF

 Simplex- data transmission in one direction only (not used very often).
 Half Duplex- data that can be transmitted in both directions, but not at the
same time.
 Full Duplex- data that can be transmitted in both directions (TX/RX) at the
same time.
© ABB Group
September 17, 2015 | Slide 20
RS-485 Loading

 Balanced communication
 Sensed between + and -
 A, B
 +,-

 Able to connect up to 32 loads.

 A terminal negative with respect to B terminal
 1 or Mark

 A terminal positive with respect to B terminal

 0 or Space

© ABB Group
September 17, | Slide 21
2015
RS-485 Loading

 A device must be able to drive:

 Impedance of 60 ohms (54 ohms worst case).

 Check manufacturer recommendations (depending on

cable) 1,000 ft. – 4,000 ft. max

© ABB Group
September 17, | Slide 22
2015
RS-485 Isolation
Internal External
to IED to IED

Internal External
IED World
circuitry Current/
Internal and references Voltage
External Reference diode Isolated via
same ground Opto- Electronics

 Electronic Isolation
 Internal Components sharing same ground. Noise isolation limited to that of
the integrated circuit. (Isolation = several volts)
 Opto-Isolation
 Internal Optical Isolation Circuitry. Isolates grounds from components
(isolation = several KV)

© ABB Group
September 17, 2015 | Slide 23
RS-485
What about grounding?

 It is recommended that a shield is terminated at one point.

 Some relays have isolate ports. This may require a
separate GROUND conductor interconnecting each node
on the cable.
 RS-485 EIA Spec states: “The circuit reference may be
established by a third connector connecting the common
leads of the equipment OR it may be provided by
connections in each using equipment to an earth
reference.”

© ABB Group
September 17, | Slide 24
2015
Topology Diagram RS-485 Multi-drop Architecture

+5V

Jumper J8 “IN 470 Ohms

TX/RX +
Jumper J6 “IN” 120 Ohms
TX/RX - Cable “A”

Jumper J 7 “IN” 470 Ohms

BANK SW 2
Dipswitch 1 = IN (Term Resitor IN)
Three-wire cable with

RS232/ RS422/485
Converter
E
C
shield. Cable “B”
* See Note A.

E
C E
C E
C

Unit 1 Unit 2 Unit 30 Unit 31

End Unit Inline Unit Jumpers Inline Unit End Unit
J6, J7, J8
“OUT”
32 Devices and 3,000 Feet Maximum loading and distance.
Ethernet

 IEEE 802.3
 Ethernet nodes found in substations are usually connected via
Fiber Optics.
 Ethernet nodes may be connected via copper (CAT 5 Cable).
 Copper: 10Base-T, 100Base-TX
 RJ-45 Connector
 Fiber: 100Base-FX
 SC Connector (push/pull)
 ST Connector (screw in)
 Others
Ethernet
Cable Connection

 There are two types of copper Ethernet ports:

 MDIX: typically what a hub or switch uses
 MDI: typically what a NIC card uses

 A typical Ethernet hub emulates the MDI interface.

 This means for interconnection one must know what type
of CAT 5 cable is required:
 Straight through pin-out
 Cross pinned

 Most modern Ethernet adapters have auto sense capability

eliminated the need for cross-over cables.

© ABB Group
September 17, | Slide 27
2015
Ethernet Copper Connectivity
Ethernet Straight Through Cable

Ethernet Hub Ethernet Hub Ethernet Straight Through Cable

Ethernet Cross Pinned

Cable *

* Unless Hub has an Uplink Switch

IED’s With Ethernet Cards Installed

IED
With Ethernet Card

Ethernet Straight
Ethernet Cross Through Cable
Pinned Cable Ethernet
Hub

PC PC With NIC Ethernet Straight

With NIC Card Card Through Cable
© ABB Group
September 17, 2015 | Slide 28
Ethernet CAT-5 cable pin-outs
Category 5 wiring standards:
EIA/TIA 568A/568B and AT&T 258A define the wiring standards and allow for two different wiring color codes.

Crossover Cable Straight Through Cable

RJ-45 PIN RJ-45 PIN RJ-45 PIN RJ-45 PIN

1 Rx+ 3 Tx+ 1 Tx+ 1 Rc+

2 Rc- 6 Tx- 2 Tx- 2 Rc-

3 Tx+ 1 Rc+ 3 Rc+ 3 Tx+

6 Tx- 2 Rc- 6 Rc- 6 Tx-

•Pairs may be solid colors and not have the stripe.

•Category 5 cable must use Category 5 rated connectors.

Pin # EIA/TIA 568A AT&T 258A, or Ethernet Token Ring FDDI, ATM, and
EIA/TIA 568B 10BASE-T TP-PMD
1 White/Green White/Orange X X

2 Green/White Orange/White X X

3 White/Orange White/Green X X

4 Blue/White Blue/White X
5 White/Blue White/Blue X

6 Orange/White Green/White X X

7 White/Brown White/Brown X

8 Brown/White Brown/White X

3- 17-26
© ABB Group
September 17, 2015 | Slide 29
Courtesy of Enterasys Knowledge @ http://knowledgebase.enterasys.com/esupport/esupport
Ethernet
Fiber Connection

 There are two types of fiber connections:

 Single mode
 Multi mode

 There are two types of fiber:

 Glass
 Plastic

 There are different diameters:

 50 µm
 62.5 µm

 Fiber cannot be intermixed without converters.

 Make sure you know what is being used.

© ABB Group
September 17, | Slide 30
2015
Ethernet
Fiber Connection

 Single-mode
 Single wavelength of light
 Used for long distances
 High bandwidth
 More expensive
 Multi-mode
 Multiple wavelengths
 Allows more “channels”
 Less expensive

© ABB Group
September 17, | Slide 31
2015
Ethernet
Fiber Connection

 Glass  Diameters
 Most common  62.5 µm
 Longer distances  Most common

 More expensive  50 µm
 Plastic  Higher bandwidths

 Cheaper
 Very short distances
 Low speeds

© ABB Group
September 17, | Slide 32
2015
Ethernet fundamentals
Media interfaces

 Most common connector used today is electrical RJ-45 for

 2 pairs (TX and RX) or 4 pairs for GigE => wire replacement
 Unshielded (UTP) or Shielded (STP)
 Straight or Crossover (TX and RX pairs swapped)

© ABB Inc.
September 17, 2015 | Slide 33
Ethernet fundamentals
Media interfaces

 Common fiber connections are ST, LC and SC for

 Multimode (Orange) cable with 810nm wavelength
 Singlemode (Yellow) cable with 1310nm or 1510nm wavelength
 Can have TX on one and RX on another wavelength (1 fiber)

© ABB Inc.
September 17, 2015 | Slide 34
Ethernet fundamentals
Media interfaces

 Small Form Factor Pluggable (SFP) provide a universal way

to connect over ANY connector (appropriate transceiver is
needed)

© ABB Inc.
September 17, 2015 | Slide 35
Ethernet fundamentals
Data frame structure

 Data (commands/status/control) is packed into “envelopes”

called Ethernet frames
 Ethernet frames, contain info about
 sender (Source MAC address)
 receiver (Destination MAC address)
 upper layer protocol, e.g. IEC 61850 GOOSE
 data integrity (special check for data validity)

 Ethernet frames are 64 – 1518 bytes or 68-1522 bytes (if

VLAN tag is used)

© ABB Inc.
September 17, 2015 | Slide 36
Ethernet fundamentals
MAC addresses

 MAC addresses are unique globally and consist of 6

bytes (there is a 8-byte extension)
 3 first bytes are Organization Unique Identifier (OUI)
 3 last bytes uniquely assigned by the Vendor

 Type of traffic corresponds to type of MAC address

© ABB Inc.
September 17, 2015 | Slide 37
Ethernet fundamentals
Traffic types and special MAC addresses

 Local Area Networks (LAN) typically have 3 types of traffic:

 broadcast (one to all others)
 multicast (one to many others)
 unicast (one to one other)

© ABB Inc.
September 17, 2015 | Slide 38
Ethernet fundamentals
Traffic types and special MAC addresses

 Special MAC addressed are used for broadcast (all 1s) and
multicast (first byte of MAC address least significant bit is 1 )

 Broadcast is normally used for MAC address learning to fill

MAC address table, and other functions, it covers whole LAN

© ABB Inc.
September 17, 2015 | Slide 39
Ethernet fundamentals
Network topologies

 Ethernet network topologies evolved from

 a bus to
 a star
 hieratical, mesh and ring topologies are also used

© ABB Inc.
September 17, 2015 | Slide 40
Ethernet fundamentals
Hubs and collisions

 Ethernet bus topology requires that all devices always

“hear” each other, so devices called Repeaters or Hubs
were used

© ABB Inc.
September 17, 2015 | Slide 41
Ethernet fundamentals
Hubs and collisions

 Ethernet hubs send all data received on 1 port to all other

ports and can not transmit and receive data at the same
time (this is called half-duplex mode)
 If 2 or more devices transmit at the same time a data
collision can occur. Data needs to be re-transmitted, and
can be lost

© ABB Inc.
September 17, 2015 | Slide 42
Ethernet fundamentals
Hubs and collisions

 Collision Detection Multiple Access (CDMA) is at the core

of the original Ethernet

 To address collision challenge, devices that can transmit

and receive at the same time were introduced – these are
called Ethernet switches (or Bridges)

© ABB Inc.
September 17, 2015 | Slide 43
Ethernet switch functionality
Full-duplex mode

 Ethernet switches can transmit and receive data at the

same time, this is called full-duplex mode

 Data collisions are NOT possible in full-duplex mode

© ABB Inc.
September 17, 2015 | Slide 44
Ethernet switch functionality
Dedicated, not shared

 Ethernet switches send data only to where its destination

resides (rather than sending data to all ports, as hubs do)

 Ethernet switches are typically used in star and mesh and

ring topologies

© ABB Inc.
September 17, 2015 | Slide 45
Ethernet switch functionality
MAC address table

 To be able to send data only to where its destination

resides, Ethernet switches need to know which port is
connected to which device(s)

 This information is learned and recorded in MAC address

table

© ABB Inc.
September 17, 2015 | Slide 46
Ethernet switch functionality
MAC address table

 Type and quality of MAC table defines the performance of

an Ethernet switch, e.g. with lousy table switch becomes a
hub sending frames to all ports, flooding the network

© ABB Inc.
September 17, 2015 | Slide 47
Ethernet switch advanced functionality
Priorities

 Although data collisions are not present in full-duplex

networks, data can still be lost due to limited buffering

 To make sure critical data is delivered reliably priorities

were introduced

 8 priority levels exist, while typically 4 or even 2 are used

© ABB Inc.
September 17, 2015 | Slide 48
Ethernet switch advanced functionality
Priorities

 Number of priorities corresponds to the number of regions

or queues in internal buffers, so that high priority buffers
are kept available for high priority data, even if low priority
buffers are full and low priority data could be discarded

 Priorities are used for critical applications

 Priorities are configured in Ethernet switches and end

devices. Priority is a part of Ethernet frame (3 bits)

© ABB Inc.
September 17, 2015 | Slide 49
Ethernet switch advanced functionality
VLANs

 In a LAN some devices can be used for one application, others

for another, and there is no need to share the data. It is in fact
preferable to separate data used for these applications

© ABB Inc.
September 17, 2015 | Slide 50
Ethernet switch advanced functionality
VLANs

 Virtual LANs (VLANs) allow traffic separation within the same

physical network

© ABB Inc.
September 17, 2015 | Slide 51
Ethernet switch advanced functionality
VLANs

 Up to 4094 separate VLANs are possible. All traffic, including

broadcast is contained within a given VLAN

 VLANs are configured in Ethernet switches and end devices.

VLAN identifier is a part of Ethernet frame (12 bits)

© ABB Inc.
September 17, 2015 | Slide 52
Ethernet switch advanced functionality
Multicasting

 Multicasting is an additional way to bound data traffic among

required devices

 In a given VLAN it is possible to create multiple multicast

groups, so that only devices that are members of that group will
be able to participate in data exchange

 Multicast membership is configured in Ethernet switches and

end devices. Multicast reservation protocols also can be used.

© ABB Inc.
September 17, 2015 | Slide 53
Ethernet switch advanced functionality
Example of Ethernet network

© ABB Inc.
September 17, 2015 | Slide 54
General Communication Architecture

LAN
Local
Area
Network

HUB/SWITCH

Ethernet Application Ethernet

IP TCP
Start Header Header End Flag Local SERVER
Flag

BROWSER -> Sends User Data ----DATAGRAM The

WAN
Network Wide
Area
Network

The Internet uses TCP/IP protocol stack. Data is mapped into multiple
layers, e.g. (TCP/IP over Ethernet)
Understanding the TCP/IP Model

 There are 4 interconnected layers:

 Application (Modbus, DNP)
 Transport (TCP, UDP)
 Internet (IP address)
 Network Access (media, MAC)

IP address: 192.168.1.5
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1

192.168.2.5 192.168.3.5
IP Addressing

 Network Address
 Identifies the network

 Host Address
 Identifies a device inside a network

IP address: 192.168.1.5
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1

© ABB Group
September 17, 2015 | Slide 57 192.168.2.5 192.168.3.5
Modbus

 Modbus was invented by Modicon Inc. in 1978

 As a method to connect PLC’s to a host (Master/Slave or
Parent/Child)
 Easy to implement with two emulations:
 RTU (Remote Terminal Unit) Emulation
 ASCII Emulation

 Modbus is available through several physical interfaces

(RS-232/RS-485/Ethernet, etc.)

© ABB Group
September 17, | Slide 58
2015
What makes Modbus a non-utility protocol?

 It has no Time Synch imbedded in the

protocol.
 It has no concept of frozen points.
 It has no concept of select before
operate.
 The manufacturer or implementer of the
protocol must engineer these features
into the protocol/device
Modbus
Protocol

Point to Point
Address 1
Confirm
E
SCADA C

Send Address X Address 2

Master
E
Multi-Drop E
C C
Network
Protective Relay
Slave Device E
C

Address 247

 Multi-Industry Open De-facto Standard.

 Master-Slave Protocol.
 Two Emulations
 Modbus ASCII ( Master/Slave Mode) - 10 bit Asynchronous
 Modbus RTU (Master/Slave Mode) - 11 bit Synchronous
Modbus
Example

The Master node (Circle) contains

a polling list. The master transmits
its request to a specific node and
waits for a response. All nodes hear
the transmitted request.

1 2 3 4 5

The addressed Slave responds with the

information. If the slave data cannot
be transmitted immediately, a not ready
response is generated and the master
must poll the slave again with the same
request.
1 2 3 4 5

© ABB Group
September 17, 2015 | Slide 61
Modbus
Emulation

 ASCII Mode
 Asynchronous communication
 Hexadecimal ASCII characters 0-9, A-F ( 30 - 39, 41,46)
 10 bit protocol
 1 start bit
 7 data bits
 1 parity (if enabled)
 1 stop bit (it parity) or 2 stop bits (if no parity enabled)
 Longitudinal redundancy check

© ABB Group
September 17, | Slide 62
2015
Modbus
Emulation

 RTU Mode
 Synchronous communication
 Data 8 bit binary, hexadecimal 0-9, A-F
 11 bit protocol
 1 start bit
 8 data bits, LBS sent first
 1 bit parity (if selected)
 1 stop bit (it parity) or 2 stop bits (if no parity selected)
 CRC-16 error check
 Most common

© ABB Group
September 17, | Slide 63
2015
Modbus
0 XXXX Memory (coils)

000512 1
TRIP C 1
000513 0 27-1P 0
000514 1 46 0
50P-1 0
001024 0 50N-1 0

PLC C
E
00008 Physical Output 8

 PLC 0 XXXX memory has duality (status and control) :

 Internal Memory bit-wide
 Output memory
 Many protective relays have similar capability
 Internal memory is analogous to ULO [User Logical Inputs/Outputs]
 Output memory is analogous to the physical outputs on the relay
Modbus
1 XXXX Memory (status)

+V
C
E
Physical Input 1
Permanently assigned
PLC as TRIP
100001

 PLC 1 XXXX memory is analogous to the physical inputs on a

protective relay.
 1 XXXX memory is a discrete bit.
 PLC’s may have XXXX = 16 to 65535 discrete inputs per device (1 X
memory).

© ABB Group
September 17, 2015 | Slide 65
Modbus
3 XXXX Memory

30001 65535
30002 -32123 CT
30003 100
EC
30004 0

0- 20 mA = PLC # 0 - 4095
I an
Transducer PLC

 A relay may have physical inputs matching the 3XXXX register

definition.
 3 XXXX data is defined as a word wide physical input from the field
mapped to memory.
 Can be analogs or status
Modbus
4XXXX Memory
400512 1 Fault Number 1
400513 98 Year 98
400514 12 Month 12
Day 11
401024 0 Hours 23
- + 10 V dc = 0 to 4095
PLC C
E
V

 PLC 4 XXXX memory has duality (status and control):

 Internal memory word wide.
 Output memory.
 Many protective relays have similar capability.
 Internal memory is analogous to metering and fault capabilities of the relay.
 4X physical output mapping is not applicable for the protective device
Modbus
6 XXXX Memory
File 0
File 1 60001 Execute Register
60001 1
60002 Password char 1
60002 98 1 File 2
60003 Password char 2
60003 1298 1 File 9
1298 60004 Password char 3
60005 Password char 4
69999 0 12 1
0 98
0 12 C
E

PLC 0

 6XXX memory is defined as extended memory. Some PLC’s have this

memory. It is able to be paged in to 4 XXXX memory.
 A few protective relay store configuration parameters in this memory
area for network access.

© ABB Group
September 17, 2015 | Slide 68
Modbus
Function 01- Read Coil Statues

 Reads 0X (Coil) references from the slave.

 All bytes are in hex (coding is dependent on RTU or ASCII
emulation).
 Memory Start Address is offset by one.
 If amount of data is not a multiple of 8, most significant bits
are padded with 0’s.

© ABB Group
September 17, | Slide 69
2015
Modbus
What happens if….?

 The issue with static data is

 What happens between access reads of the IED?
 If something changes?
 If something doesn’t change?

 If two changes occur during read, the event is lost using

static data
 Breaker trips – Pickup Alarm (PUA) energizes and de-
energizes briefly

© ABB Group
September 17, | Slide 70
2015
Modbus
How is this anomaly resolved?

 Latched Bits (which can be reset via a control write).

 Momentary Change Detect Bits (which change status is
reset on a read of the element).
 This is a manufacturer’s function and not one of the
protocol.
 NOT ALL MODBUS IMPLEMENTATIONS ARE ALIKE!

© ABB Group
September 17, | Slide 71
2015
Modbus
Function 01 – Read Coil Status
Example - Read Output 1-6, with two bit status

Modbus Slave Addr =1

C
E

Read from
0X Mapping
Obtain Output 8 Through Output 3 Status Indication (01037 to 01048 per the memory map).
Host Sends : 01 01 04 0C 00 00 14 - - = LRC or CRC Code
Addr = 01
Function = 01
Address = 1037 ( which is 1036 in hex = 040C)
Amount of Data Requested = 12 Coils
Relay Responds: 01 01 02 A1 02 -
Addr = 01
Function = 01
Data Bytes Received = 2
Data Received = A1 02
Modbus
Function 02- Read Input Status

 Reads 1X ( Input) references from the slave.

 All bytes are in hex ( coding is dependent on RTU or ASCII
emulation).
 Memory Start Address is offset by one.
 If amount of data is not a multiple of 8, most significant bits
are padded with 0’s.

© ABB Group
September 17, | Slide 73
2015
Modbus
Function 02 – Read Input Status
Example - Read User Logical Input 1-6, with two bit status

Modbus Slave Addr =1

C
E

Read from
1X Mapping
Obtain ULI1 Through ULI 6 Status Indication (10559 per the memory map).
Host Sends : 01 02 01 2E 00 14 - - = LRC or CRC Code
Addr = 01
Function = 02
Address = 559 ( which is 558 in hex = 012E)
Amount of Data Requested = 12 Inputs
Relay Responds: 01 02 02 A1 02 -
Addr = 01
Function = 01
Data Bytes Received = 2
Data Received = A1 02
Modbus
Function 03- Read Holding Registers

 Reads 4X holding registers from the slave.

 All bytes are in hex (coding is dependent on RTU or ASCII
emulation).
 Memory Start Address is offset by one.
 Data is returned in register format (16 bits/2 bytes per
register)
 Maximum registers read are 125 per query.
 Registers are sent Hi byte- Lo byte per register.

© ABB Group
September 17, | Slide 75
2015
DNP
Protocol History

 Distributed Network Protocol (DNP).

 Created by Westronics (Now GE ) in 1990.
 Released into Public Domain in 1993.
 Users Group created in 1993.
 DNP Technical Committee Created in 1995.
 Published subset documentation.
 Established parameters for future protocol
conformance committee.

© ABB Group
September 17, | Slide 76
2015
DNP 3.0

 Dependent on the implementation DNP 3.0 can:

 Request and respond with Multiple Data Messages in
a single message.
 Segment messages into multiple frames.
 Respond with changed data.
 Request data based on data priority.
 Support time synchronization.
 Allow multiple masters and peer to peer operation.
 Allow user defined objects and file transfer.

© ABB Group
September 17, | Slide 77
2015
DNP 3.0

 DNP 3.0 Supports the International Organization for

Standardization (ISO) and OSI model. Layers fully
supported are:
 Physical (Layer 1)
 Data Link (Layer 2)
 Application (Layer 7)

 Pseudo-supported and defined layers are:

 Transport (Layer 4)

© ABB Group
September 17, | Slide 78
2015
DNP
Definition of terms

 Object Categories - data which conforms to different data

types:
 Static: current value of field or software point.
 Event: historical data.
 Frozen Static: a field or software value which is not actively
updated due to a data freeze request.
 Frozen Event: data generated as a result of a data freeze
event but historically archived upon a change.

© ABB Group
September 17, | Slide 79
2015
DNP
Object types per object category

DATA TYPE OBJECT VARIANTS

Binary Input 1,2, |1,2 | |1,2,3|

Binary Output 10,12 |1,2 | |1,2,3|

Counter 20,21,22,23 |1 - 8| |1 – 12 | |1 – 8 |
|1–8|
Analog Input 30,31,32,33 |1 – 4| |1 – 6 | |1 – 4|
|1 – 4|
Analog Output 40,41 | 1, 2 | | 1, 2|

Time (relative or absolute) 50,51,52 | 1,2 | | 1,2 | | 1,2|

© ABB Group
September 17, 2015 | Slide 80
DNP
Object types per object category

DATA TYPE OBJECT VARIANT

Class 60 | 1 – 4|
Files 70 |1|
Devices 80,81,82,83 |1 | | 1| | 1 | | 1, 2 |
Applications 90 |1|
Alternate Numeric 100, 101 | 1,2,3 | |1,2,3|
Future Use [ 110 – 254] -

© ABB Group
September 17, 2015 | Slide 81
DNP 3.0
Level 1

Master

Slave
SEND
RESPOND
Data Concentrator Meter
SCADA Host Relay
 Master Requests - Slave Responds
Cap Bank Controller
Auto-Recloser
 Slave MUST Accept Requests for:
 Data Object Reads
 Binary/Analog Output Object Reads *
 Control Operations for Binary/Analog Outputs
 Cold and Internal Indication Restarts
 Delay Measurements
 Writes to Date and Time

© ABB Group
September 17, 2015 | Slide 82
DNP 3.0
Level 1

 Master Must accept (with multiple object variations)

 Binary/Analog Input and Events.
 Counter and Counter Events.
 Binary/Analog Output Status.

 Master device Must be able to break the message into

component pieces (parse).

© ABB Group
September 17, | Slide 83
2015
DNP 3.0
Level 1

 OPTIONAL FEATURE Implementation.

 Slave OPTIONALLY MAY send unsolicited responses.
 Slave OPTIONALLY MAY NOT generate parsed data objects
if master requests such information.
 Slave OPTIONALLY MAY respond without time object
attachment.
 Slave OPTIONALLY MAY send unsolicited responses AND
the capability MUST be configurable.

© ABB Group
September 17, | Slide 84
2015
DNP 3.0
Level 2

Data Concentrator Relay

Host Device
SEND Large IED or Small RTU
REQUIRED
RESPOND
Node A Node B
Master RESPOND SEND Slave
OPTIONAL

 Node A Requests - Node B Responds (Standard) Node B Requests -

Node B Responds (Optional)
 Slave MUST Accepts Requests for:
 FREEZE on Binary Counter Options
 Parse of Read Requests of various objects and OPTIONALLY MAY report
Frozen Counter objects.
 Master and Slave MUST incorporate Level 1 DNP features.

© ABB Group
September 17, 2015 | Slide 85
DNP 3.0
What does the data link layer do?

 DNP can allow a host and IED (Unsolicited Request) to act

as a master.
 The data link layer:
 Synchronizes data exchanges.
 Controls message retries.
 Connects and disconnects dial up sessions.
 Controls the physical layer.
 Provides message services (priority, error notification).
 Establishes and disconnects a DIAL UP connection
 Sets the frame construction in a DNP 3.0 session.
 Performs collision avoidance of messages (in an
unsolicited response node).

© ABB Group
September 17, | Slide 86
2015
DNP 3.0
Transport layer

 The transport layer indicates the length of a communication

session
 Why is this needed?
 Long messages exceeding 255 bytes are segmented in
multiple messages.
 The length of DLC data is 5 bytes.
 The length of the TL is 1 byte.
 The remaining data length is 255 - 5 -1 = 249 bytes.
 In case any data frames are corrupted, a retransmission of
the corrupted frame may occur.
 Allows assembly of large messages by a host device.

© ABB Group
September 17, | Slide 87
2015
DNP 3.0
Class data reporting

 Data may be obtained in a variety of methods:

 Ask for each point by object and variant.
 Allows for reporting only changed data.
 Allows for priority reporting of data.
 Allows for multiple polling times.
 Have the host report the data in classes.
 Class 0
 Class 1
 Class 2
 Class 3

© ABB Group
September 17, | Slide 88
2015
DNP 3.0
Unsolicited reporting

 Slave device sends data to master without a master

request:
 Reports critical data when change occurs.
 Able to reduce polling times.

© ABB Group
September 17, | Slide 89
2015
IEC 61850

 It is a standard – not just a protocol.

 Integration of status monitoring, protection, automation, and
control into IEDs.
 Digitization of copper wires
 IEC 61850-8-1  Manufacturing Message Specification (MMS)
and Generic Object Oriented Substation Events (GOOSE).
 IEC 61850-9-2  Sample Measurement Values (SMV)

 Modeling of the substation, equipment, and functions.

 Protocol stack.
 Interoperability by standardization and verification.

© ABB Group
September 17, | Slide 90
2015
IEC 61850
Goal of the standard

 Interoperability
 Exchange information between Intelligent Electronic Devices
(IED’s) from several manufacturers.
 IEDs use this information for their own function.

 Free Configuration.
 Free allocation of functions to devices.
 Support any philosophy of customer – centralized or
decentralized systems.

 Long Term Stability

 Future proof.
 Follow progress in mainstream communication technology.
 Follow evolving system requirements needed by customers.

© ABB Group
September 17, | Slide 91
2015
IEC 61850
Data Model

 Thanks to such representation, functions can then be allocated to objects within the
substation.
 Addressing scheme takes this into consideration tying the data with the application,
object, and location within the substation.

Bradley.J1.Q08.A01.LD0.MMXU1.A.phsA
Bradley.J1.Q08.A01.LD0.MMXU1.A.phsB
Bradley.J1.Q08.A01.LD0.PTOC.Op.general
Bradley.J1.Q08.A01.LD0.XCBR1.Pos.stVal
© ABB Group
September 17, 2015 | Slide 92
IEC 61850
Data model – logical node

“UCA & 61850 for Dummies.” – Douglas Proudfoot

IEC 61850
Different kinds of logical nodes
 LLN0, LPHD: IED and function management
 Pxxx: protection (PTOC, PIOC, PDIS, PDIF,….) (28)
 Rxxx: protection related (RREC, RSYN, RDRx, ….) (10)
 Cxxx: control related (CSWI, CILO, CALH, CCGR, CPOW)
 Mxxx: measurements (MMXU, MMXN, MMTR, MHAI, MDIF,
MSTA)
 Axxx: automatic functions (ATCC, ANCR, ARCO, AVCO)
 Gxxx: generic functions (GGIO, GAPC, GSAL)
 Sxxx: sensor/monitoring interface (SIMG, SIML, SARC, SPDC)
 Txxx: instrument transformer (TCTR, TVTR)
 Xxxx: switchgear process interface (XCBR, XSWI)
 Yxxx: transformer process if (YPTR, YLTC, YEFN, YPSH)
 Zxxx: further power related equipment (ZBAT, ZGEN, ZMOT,…)
 Ixxx: interfacing and archiving (IHMI, ITCI, IARC, ITMI)

© ABB Group
September 17, | Slide 94
2015
IEC 61850 Substation Modeling
The Substation Structure
Orlando Substation
Orlando Substation
Line 1 Line 2

D1 D2 230kV Voltage Level

CB1 Bay D1 Bay

230kV CB2
IED D1.1 IED
CB3
IED D.1.2

T1 Line 3 Bay D2

115kV CB10 115 kV

CB11 CB12 CB13

Line X..Y

Line X Line Y Line Z

© ABB Group
September 17, 2015 | Slide
95
IEC 61850
Engineering with SCL

System tool approach.

 Thanks to common file format engineering of the SAS
system can be performed under a single tool.
 This provides a single point of interaction with the
configuration files of all devices regardless of
manufacturer.
 End result (SCD file) must be part of the final system
documentation just like DC and AC elementary are.

© ABB Group
September 17, | Slide 96
2015
IEC 61850
Communication methods

 Client Server
 Similar to Master-Slave.
 Data is published by the IED (Server).
 IED’s subscribe to data (Client).

 Peer to Peer
 Data is published by the IED (Server).
 IED’s subscribe to data (Client).
 High speed.

© ABB Group
September 17, | Slide 97
2015
IEC 61850
Client - Server

 Get information from relays and meters.

 Higher resolution of information.
 Lower integration costs.
 Drag and drop process thanks to SCL file.
 All manufacturers with same naming convention.
 Less chances for mistakes.

© ABB Group
September 17, | Slide 98
2015
IEC 61850
Digitize copper

Digitize copper (GOOSE + SMV).

 Thanks to Ethernet technology and previously mentioned
data model we are able to digitize copper:
 Binary signals (GOOSE)
 Analog signals (GOOSE)
 Analog signals as input to protection and metering functions
(SMV in the Process Bus).

© ABB Group
September 17, | Slide 99
2015
IEC 61850
What is a GOOSE message?

 Generic Object Oriented Substation Event.

 Fast and reliable distribution of information.
 Status (breaker position, trip, pickup, alarms, etc.)
 Analog (counter values, etc.)

 Performance
 Fast messages Type 1A (Class P2/P3) received within 3ms.
 This includes transmission time into the other IEDs (similar to an
output to input connection between 2 relays).

© ABB Group
September 17, | Slide 100
2015
IEC 61850
What is a GOOSE message?

 GOOSE messages are based on change event.

 GOOSE messages include diagnostic functions (a “heart
beat” to all devices subscribed is sent periodically).
 GOOSE messages are managed by GCBs (GOOSE
control block) inside IEDs.
 GOOSE messages send “Data Sets” upon changes of
state.

© ABB Group
September 17, | Slide 101
2015
Summary
ModBus, DNP 3.0, and IEC 61850
Year RS-232 RS-485 Ethernet Description Data
of SS Description
ModBus 1978 YES YES YES NO NO
DNP 1990 YES YES YES NO NO
IEC 61850 2003 NO NO YES YES YES

© ABB Group
September 17, | Slide 102
2015
Conclusions

 Various communication interfaces have been discussed

 Protocols and communication architectures were covered
 Sufficient knowledge about communication interfaces,
protocols and equipment used is required by protection and
control engineers to ensure reliability of protection and
control schemes

© ABB Group
September 17, | Slide 103
2015
This webinar brought to you by:
ABB Power Systems Automation and Communication

• Relion Series Relays – Advanced flexible platform for protection and control
• RTU 500 Series – Proven, powerful and open architecture
• MicroSCADA - Advanced control and applications
• Tropos – Secure, robust, high speed wireless solutions

We combine innovative, flexible and open products with

engineering and project services to help our customers
address their challenges.
 Thank you for your participation
Shortly, you will receive a link to an archive of this presentation.
To view a schedule of remaining webinars in this series, or for more
information on ABB’s protection and control solutions, visit:
www.abb.com/relion

© ABB Group
September 17, | Slide 105
2015