Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

IEC 61850 Protocol

Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

IEC61850 PROTOCOL

Prepared by
Eng: Ahmed Mamdouh
State before IEC61850
• There were different protocols used before IEC61850 such as MODBUS,
DNP, IEC101, PROFINET and PROFIBUS, and these protocols have limited
interoperability between devices from different vendors
• Devices from different vendors cannot be combined in a system because of
a missing standard (only with an uneconomic effort)
• There was point to point hardwired connections between devices, and as
there are more than 200 device in substations, there are a complex in wiring
schemes
• Maintenance and troubleshooting is very difficult due to complex of wiring
• The cost was very high so the market request a global standard for
competitive performance cost reduction
• The ability to add extension bays is too difficult.
State before IEC61850
Examples for different protocols used
Market Requirements
• Cost reduction for investments, operation and maintenance
• The global market needs a standard supported by all major vendors
• Mixing of all devices with FO cables in the same network to can
exchange information
• Open, future-proof standard for safe-guarding of investments and
improving technology and for future extensions by bays or functions
What is IEC 61850?
It is an international standard for substation automation systems, the
IEC 61850 standard defines the communication between devices in the
substation and related system, designed as open standard that provide
design flexibility and future proof, IEC 61850 enables the integration of
all protection, control, measurement, and monitoring function within a
power network at the field or process and station control levels.
BENEFITS
Lower installation and maintenance cost

Reduce Manual Effort & Errors

Reduced Setup and Configuration

Standard Configuration Language

Modern Network Technology

Standardized Device & Object Models IEC61850

Replacing hardware wiring with software telegrams


IEC 61850 Data Model
Data Hierarchy For Data Model
IEC 61850 Data Model
Physical Device (IED)
▪ Each physical device (IED) in substation must have unique Technical
Key and unique Ip address within the range of network.
▪ Examples of the Technical Keys:
oFor example, the Technical Key for BCU in level 220KV in bay No: 1 the
Technical Key will be (AA1D1Q01KF1), for first protection relay will be
(AA1D1Q01FN1).

oFor example, the Technical Key for FM in level 22KV in bay No: 1 the
Technical Key will be (AA1J1Q01KF1).
Standard for logical node
Example for logical node, data object
Data set
❖Data set: is container for data and defines which data to be sent.
➢For MMS: signals on data object level (Vertical Communication).
[BETWEEN BAY LEVEL AND STATION LEVEL]
➢For GOOSE: signals on data attribute level (Horizontal
Communication). [IN BAY LEVEL]
Reports and Types of reports from IEDs
❖Reports: Container of the dataset.
❖Types of reports:
➢RCB: Report Control Block is container of the dataset which receive
requests from SAS client (Server, gateway) and responds with updated
values of dataset contents.[For MMS]
There are two types of RCP:
1- BRCB: Buffered Report Control Block.
2- URCB: Unbuffered Report Control Block.
➢GCB: Goose Control Block is Container of the dataset which will
publish the dataset to the other IEDs selected.
MMS

MMS: is a Manufacturing
Message Specifications
It is support client-server
communication and it is
designed to facilitate
interoperability among
different vendor’s
devices and server.
▪ Examples for MMS name which have the data model of IEC61850:
oLD0/SCSWI1.Pos.stVal
GOOSE
GOOSE: Is a Generic Object-Oriented Substation Event and it is a
multicast message - One-to-many, and it is a fast message between IEDs
in the bay level, the same IED can work as publisher and as subscriber,
and GOOSE message have high availability and reliability.

• In Interlock
Usage: • In Blockings
• In AR Start
Signals Route from IED to SAS
• Data of the substation which is required to be transmitted from the IED
Logical Node to SAS.

• Container of different LNs from different signals in the same IED to be


Data Set sent as one time to SAS.

• Container of the dataset which receive requests from SAS client (Server,
Report gateway) and responds with updated values of dataset contents.
Control Block
Signals Route from IED to IED
• Data of the substation which is required to be
Data
Attribute
transmitted from the IED to another IED

• Container of different LNs from different signals in the


Data Set same IED to be sent updated signals to another IED

• Container of the dataset which will publish updated


Goose
Control Block
values of dataset contents to the other IEDs selected.
Time Synchronization Protocol SNTP

SNTP: is Simple Network


Time Protocol
It is a Protocol for Time
Synchronization defined in
IEC 61850 and Time Synch
error after 3 request from
time client without any
answer and this mean that
the connection fail to the
SNTP server.
Substation Configuration Language File (SCL)
• SCL: Description language for communication in electrical substations
related to IEDs
• Important types of SCL File
➢CID: Configured IED Description.
➢ICD: IED Capability Description.
➢SCD: Substation Configuration Description.
Tools for IEC61850 Engineering
IEDs: Basic IEC
61850
Engineering

Engineering Tool:
CID Advanced IEC
61850 Engineering

SAS System
SCD
Thank You

You might also like