IEC 61850

e-terracontrol | Module 8

GRID
Topics

IEC61850 Overview
Data Model Hirarchy
IEC 61850 Config
IEC 61850 Client

e-terracontrol | IEC 61850 | P2

IEC 61850 Overview

IEC 61850 means an Communication for all functions

both between Station/Bay Level and Bay/Process Level

IEC 61850

e-terracontrol | IEC 61850 | P3

IEC 61850 Data Model Hirarchy

ClientDS

DeviceDS

Logical Device DS

BrickDS

ControlDS

IEC61850 ClientDS This SCADA dataset type will be assigned to the IEC61850
Client Dataset.
IEC61850DeviceDS This SCADA dataset type will be assigned to the IEC61850
device datasets.
IEC61850LogicalDeviceDS This SCADA dataset type will be assigned to the
IEC61850 logical device datasets.
IEC61850BrickDS This SCADA dataset type will be assigned to the IEC61850
brick datasets.
IEC61850ControlDS This SCADA dataset type will be assigned to the
IEC61850 brick control datasets. This is used to model setpoints, Raise/Lower

and control data items.
e-terracontrol | IEC 61850 | P4
Data Model Hirarchy Example

e-terracontrol | IEC 61850 | P5

IEC 61850 Client Data Set

IEC61850 Client dataset

Similar to how the Cfereader DataSet is modeled,

this dataset models the IEC61850 Client
application. It can be used for managing the
IEC61850 Client application and for redundancy.
The type will be IEC61850ClientDS and there will
be no data items in the dataset.

e-terracontrol | IEC 61850 | P6

IEC 61850 Client Data Set

There are several parameters used to

configure the connection to the
PACiS Agency application:

AgencyHeartbeat
NumMissedHeartbeats
HeartbeatMonitor_Freq
ScanRate

e-terracontrol | IEC 61850 | P7

IEC 61850 Device Data Set

IEC61850 device datasets

Each IEC61850 device to communicate with will

have a IEC61850DeviceDS dataset modeled for it.
This dataset will define the following mapping and
communication parameters for the device:

ARName This must match a Remote entry

(CommonName) in the Lean.cfg file.

IpAddress This must match an ipaddress

entry (ip_address) in the Lean.cfg file. This
field correspond to the ip address of the
server.

e-terracontrol | IEC 61850 | P8

IEC 61850 Device Data Set Example

e-terracontrol | IEC 61850 | P9

IEC 61850 Logical Device Data Set

IEC61850 Logical Device datasets

Under each IEC61850 device dataset, IEC61850 Logical

Device datasets will be modeled for each logical device in
the IEC61850 device that is to be mapped to SCADA.

Logical Device Object Models are specialized groupings of

associated Bricks that represent devices, functions, or
applications of a specific function or application in the
problem domain, i.e., protection, control, and data
acquisition.

The name of the dataset is case-sensitive and it must match

exactly the name of the logical device in the IEC61850 model.
There are no parameters for these datasets.

e-terracontrol | IEC 61850 | P10

IEC 61850 Brick Data Set

IEc61850 Brick datasets

Brick datasets are used to select the measurements in the

IEC61850 device that are to be mapped to the SCADA
database. A brick dataset will be modeled for each brick in
the IEC61850 device that is to be mapped to the SCADA
database.

The name of the dataset is case-sensitive and it must match

exactly the name of the brick in the IEC61850 model.

Individual components of a brick will be modeled by adding

dataitems to the dataset. These dataitems will have linkages
to measurements. This will be the mechanism for mapping
IEC61850 measurements to the e-terracontrol
measurements.

e-terracontrol | IEC 61850 | P11

IEC 61850 Brick Data Set Example

e-terracontrol | IEC 61850 | P12

IEC 61850 Control Data Set

IEC61850 Control datasets

Control datasets are used to model the controls to be issued

to the IEC61850 device. This is mostly a SCADA model
requirement. The IEC61850 Client will not process these
datasets but will receive the modeled names in the control
commands from SCADA. There should be one control dataset
for each brick that contains controls that will be sent to the
IEC61850 Client application. Data items should be modeled for
each control or setpoint record.

e-terracontrol | IEC 61850 | P13

IEC 61850 Control Data Set Example

e-terracontrol | IEC 61850 | P14

IEC 61850 Control Data Set Example

e-terracontrol | IEC 61850 | P15

 IEC 61850 Config

Before using the IEC61850 Client to communicate with a new device, the devices model must be obtained using the
IEC61850Config application.

IEC61850 Server(s) Tab

All servers connected to the IEC61850 Client must be defined on the IEC61850 Server tab. For each server, you must
define the name and the IP address of the server. All information entered is automatically updated in the Lean.cfg
and Agency.cfg files. The Server name is equal to the ARName defined in the IEC61850Device Data set in the
configuration of the Scada device.

e-terracontrol | IEC 61850 | P16

 IEC 61850 Config

Model Download Tab

By default, the obtained XML file will go into a new IEC61850WORK subfolder of the e-terracontrol installation
location. The integrator will not be able to override this location if desired.

e-terracontrol | IEC 61850 | P17

 IEC 61850 Client

The IEC61850 Client application user interface can be used for diagnostic purposes. This section
describes the interface.

e-terracontrol | IEC 61850 | P18

 End of training

Thank you for your time and

attention

e-terracontrol | IEC 61850 | P19