Engineering Guide IED670 Products

Engineering guide
IED 670 products
Innovation from ABB

Engineering guide
IED 670 products
About this Manual

Document No: 1MRK 511 179UEN
Issued: March 2006
Revision: -
Copyright 2006 ABB. All rights reserved.

COPYRIGHT
WE RESERVE ALL RIGHTS TO THIS DOCUMENT, EVEN IN THE EVENT THAT A PATENT IS
ISSUED AND A DIFFERENT COMMERCIAL PROPRIETARY RIGHT IS REGISTERED. IMPROPER
USE, IN PARTICULAR REPRODUCTION AND DISSEMINATION TO THIRD PARTIES, IS NOT
PERMITTED.
THIS DOCUMENT HAS BEEN CAREFULLY CHECKED. HOWEVER, IN CASE ANY ERRORS ARE
DETECTED, THE READER IS KINDLY REQUESTED TO NOTIFY THE MANUFACTURER AT THE
ADDRESS BELOW.
THE DATA CONTAINED IN THIS MANUAL IS INTENDED SOLELY FOR THE CONCEPT OR
PRODUCT DESCRIPTION AND IS NOT TO BE DEEMED TO BE A STATEMENT OF GUARAN-
TEED PROPERTIES. IN THE INTERESTS OF OUR CUSTOMERS, WE CONSTANTLY SEEK TO
ENSURE THAT OUR PRODUCTS ARE DEVELOPED TO THE LATEST TECHNOLOGICAL STAN-
DARDS. AS A RESULT, IT IS POSSIBLE THAT THERE MAY BE SOME DIFFERENCES BETWEEN
THE HW/SW PRODUCT AND THIS INFORMATION PRODUCT.
Manufacturer:
ABB Power Technologies AB
Substation Automation Products
SE-721 59 Vsters
Sweden
Telephone: +46 (0) 21 34 20 00
Facsimile: +46 (0) 21 14 69 18
www.abb.com/substationautomation
Contents
Chapter Page
Chapter 1 Introduction ..................................................................... 1
Introduction to the IED 670 engineering guide .................................... 2

About the complete set of manuals for an IED ............................... 2
About the IED 670 engineering guide............................................. 2
Intended audience .......................................................................... 3
Related documents......................................................................... 4
Revision notes ................................................................................ 6
Chapter 2 IED 670 engineering tool set introduction .................... 7
IED 670 engineering tool set introduction............................................ 8

IED engineering process ..................................................................... 9
IED signal engineering per protocol................................................... 12
IED monitoring process ..................................................................... 13
IED diagnostic capabilities................................................................. 14
Chapter 3 PCM 600 Tool set .......................................................... 15
PCM 600 Tool set .............................................................................. 16

PCM 600 views and windows ............................................................ 19
The toolbar and the mouse........................................................... 23
PCM 600 options for operation .......................................................... 26
Log configuration .......................................................................... 26
PCM 600 access .......................................................................... 27
Connectivity package version ............................................................ 33
Set up PCM 600 communication link per IED.................................... 35
Set up communication link per Generic IEC 61850 IED ............... 41
Chapter 4 Set up a project ............................................................. 43
Set up a project.................................................................................. 44
Set up a plant structure...................................................................... 45
Naming conventions for IEC 61850 .............................................. 46
Selection of an IED ........................................................................... 49
Order specific IED ........................................................................ 49
Pre-configured IED ....................................................................... 50
Base IED ...................................................................................... 51
Generic IEC 61850 IED ................................................................ 51
Managing projects ............................................................................. 54
Chapter 5 IED 670 Engineering process....................................... 59

Contents
IED Engineering process ................................................................... 60

Configuration and Programming tool CAP 531.................................. 62
Engineering the IO interfaces ....................................................... 65
Customized application configuration templates .......................... 67
Signal matrix tool SMT....................................................................... 68
Parameter and setting tool PST......................................................... 74
Configuration parameters and settings......................................... 79
Graphical display editor GDE............................................................. 81
Engineering of a bay configuration ............................................... 85
HMI engineering ................................................................................ 89
Chapter 6 IED 670 signal engineering per protocol..................... 91
Introduction ........................................................................................ 92
Additional procedures for signal engineering................................ 93
IEC 61850 protocol ............................................................................ 94
Sequence for signal engineering of IEC 61850 protocol .............. 94
IEC 61850 interface in IED 670 .................................................... 98
Export/import of SCD files in PCM 600......................................... 99
GOOSE signal engineering and download of ied.CID file .......... 102
SPA protocol .................................................................................... 105
SPA interface in IED 670 ............................................................ 105
LON protocol.................................................................................... 110
LON interface in IED 670............................................................ 110
Engineering LON horizontal communication .............................. 114
IEC 608705103 protocol .............................................................. 117
IEC 608705103 interface in IED 670 ...................................... 117
Chapter 7 IED monitoring process .............................................. 121
Disturbance record handler DRH..................................................... 122

Use of Comtrade header file in IED 670 relays .......................... 125
Operating the DRH ..................................................................... 128
IED Recording ....................................................................... 131
DR Recording ........................................................................ 131
Reports ....................................................................................... 133
Configuration capability of a report ........................................ 135
Task scheduler to monitor new disturbance reports ................... 137
Set up tasks and jobs within a task ....................................... 139
IED 670 signal monitoring ISM ........................................................ 143
ISM operation ............................................................................. 143
Chapter 8 IED 670 diagnostic capabilities .................................. 147
IED 670 event viewer IEV ................................................................ 148

IEV operation .............................................................................. 148
OPC online diagnostic OOD ............................................................ 152
OOD operation............................................................................ 153
Contents
Chapter 9 Glossary....................................................................... 159
Glossary........................................................................................... 160
Contents
About this chapter Chapter 1
Introduction
Chapter 1 Introduction
About this chapter

This chapter explains concepts and conventions used in this manual and provides information
necessary to understand the contents of the manual.
1
Introduction to the IED 670 engineering guide Chapter 1
Introduction
1 Introduction to the IED 670 engineering guide
1.1 About the complete set of manuals for an IED

The users manual (UM) is a complete set of five different manuals:
Application Technical Installation and Operators Engineering

manual reference commissioning manual guide
manual manual
en06000097.vsd
The Application Manual (AM) contains application descriptions, setting guidelines and setting
parameters sorted per function. The application manual should be used to find out when and for
what purpose a typical protection function could be used. The manual should also be used when
calculating settings.
The Technical Reference Manual (TRM) contains application and functionality descriptions
and it lists function blocks, logic diagrams, input and output signals, setting parameters and tech-
nical data sorted per function. The technical reference manual should be used as a technical ref-
erence during the engineering phase, installation and commissioning phase, and during normal
service.
The Installation and Commissioning Manual (ICM) contains instructions on how to install
and commission the protection IED. The manual can also be used as a reference during periodic
testing. The manual covers procedures for mechanical and electrical installation, energizing and
checking of external circuitry, setting and configuration as well as verifying settings and per-
forming directional tests. The chapters are organized in the chronological order (indicated by
chapter/section numbers) in which the protection IED should be installed and commissioned.
The Operators Manual (OM) contains instructions on how to operate the protection IED dur-
ing normal service once it has been commissioned. The operators manual can be used to find
out how to handle disturbances or how to view calculated and measured network data in order
to determine the cause of a fault.
The IED 670 engineering guide (EG) contains instructions on how to engineer the IED 670
products. The manual guides to use the different tool components for IED 670 engineering. It
also guides how to handle the tool component available to read disturbance files from the IEDs
on the basis of the IEC 61850 definitions. The third part is an introduction about the diagnostic
tool components available for IED 670 products and the PCM 600 tool.
1.2 About the IED 670 engineering guide

The Engineering guide for IED 670 products contains the following chapters:
2
Introduction
IED 670 engineering tool set introduction

- An overview about the engineering tasks for the different parts of an IED 670
is given. The capability and tools used for system monitoring and diagnostic
is listed and their general task described.
PCM 600 Tool set
- The handling of the PCM 600 tool and its tool components in the MicroSoft
windows environment is described. The configuration options of PCM 600
are listed and their task explained. The connectivity package concept as it is
needed for IED 670 products is included.
Set up a project
- PCM 600 operates with projects and the handling and set up of a project is
described with its different steps and project management.
IED 670 Engineering process
- The engineering process for the IED 670 product itself is described. The task
of the different tool components anf the handling of the tool components is
explained.
IED 670 signal engineering
- IED 670 products can handle different communication protocols. The engi-
neering process for each protocol is different and described in this chapter.
IED monitoring process
- The task, way of operation and handling of the disturbance record handler is
described herein. The second tool for IED 670 signal monitoring is explained
here.
IED 670 diagnostic capabilities
- The two diagnostic tools for IED 670 are described. This is the event viewer
for IED 670 system events and for process evnets and the OPC online diag-
nostic tool to check the communication link between the IED and the PCM
600.
Glossary
- Contains a list of terms, acronyms and abbreviations used in ABB technical
documentation.
1.3 Intended audience

General
This manual addresses system engineers, project engineers involved n the engineering process
for a project, installation and commissioning personnel, who use technical data during engineer-
ing, installation and commissioning, and in normal service.
Requirements
The system engineer must have a thorough knowledge of protection and/or control systems, pro-
tection/control equipment, protection/control functions and the configured functional logics in
the IED 670 devices. The installation and commissioning personnel must have a basic knowl-
edge in the handling electronic equipment.
3
Introduction
1.4 Related documents
Documents related to RED 670 Identity number

Operators manual 1MRK 505 133-UEN
Installation and commissioning manual 1MRK 505 134-UEN
Technical reference manual 1MRK 505 132-UEN
Application manual 1MRK 505 135-UEN
Buyers guide 1MRK 505 164-BEN
Connection diagram, Single breaker arr. Three phase tripping arr. 1MRK 002 801-BA
Connection diagram, Single breaker arr. Single phase tripping arr. 1MRK 002 801-CA
Connection diagram, Multi breaker arr. Three phase tripping arr. 1MRK 002 801-DA
Connection diagram, Multi breaker arr. Single phase tripping arr. 1MRK 002 801-EA
Configuration diagram A, Single breaker with single or double busbars 1MRK 004 500-82
Configuration diagram B, Single breakers with single or double busbars 1MRK 004 500-83
Configuration diagram C, Multi breakers such as 1 1/2 or ring busbar arr. 1MRK 004 500-84
Configuration diagram D, Multi breakers such as 1 1/2 or ring busbar arr. 1MRK 004 500-85
Setting example 1, 230 kV Short cable line with 1 1/2 CB arr. 1MRK 505 175-WEN
Documents related to REL 670 Identity number

Connection diagram, Single breaker arr. Three phase tripping arr. 1MRK 002 801-BA
Connection diagram, Single breaker arr. Single phase tripping arr. 1MRK 002 801-CA
Connection diagram, Multi breaker arr. Three phase tripping arr. 1MRK 002 801-DA
Connection diagram, Multi breaker arr. Single phase tripping arr. 1MRK 002 801-EA
Configuration diagram A, Single breaker with single or double busbar 1MRK 004 500-86
Configuration diagram B, Single breaker with single or double busbar 1MRK 004 500-87
Configuration diagram C, Multi breaker such as 1 1/2 or ring busbar arr. 1MRK 004 500-88
Configuration diagram D, Multi breaker such as 1 1/2 or ring busbar arr. 1MRK 004 500-89
Setting example 1, 400 kV Long overhead power line with 1 1/2 CB arr. 1MRK 506 267-WEN
Setting example 2, 230 kV Extremely long overhead power line, double bus, 1MRK 506 268-WEN
single CB arr.
Setting example 3, 132 kV Short overhead power line, double bus, single CB 1MRK 506 269-WEN
arr.
4
Introduction
Documents related to REC 670 Identity number

Connection diagram, Single breaker 1MRK 002 801-FA
Connection diagram, Double breaker 1MRK 002 801-MA
Connection diagram, 1 1/2 CB 1MRK 002 801-NA
Configuration diagram A, Single breaker arr. with single or double busbar 1MRK 004 500-90
Configuration diagram B, Double breaker arrangements 1MRK 004 500-91
Configuration diagram C, 1 1/2 breaker arr. for a full bay 1MRK 004 500-92
Documents related to RET 670 Identity number

Connection diagram, Two winding transf. Single breaker arrangements 1MRK 002 801-LA
Connection diagram, Two winding transf. Multi breaker arrangements 1MRK 002 801-HA
Connection diagram, Three winding transf. Single breaker arrangements 1MRK 002 801-KA
Connection diagram, Three winding transf. Multi breaker arrangements 1MRK 002 801-GA
Configuration diagram A, Two winding transf. with single or double busbar but 1MRK 004 500-93
with a single breaker arr. on both sides
Configuration diagram B, Two winding transf. in multi breaker arr. on one or 1MRK 004 500-94
both sides
Configuration diagram C, Three winding transf. with single or double busbar 1MRK 004 500-95
but with a single breaker arr. on both sides
Configuration diagram D, Two winding transf. in multi breaker arr. on one or 1MRK 004 500-96
both sides
Setting example 1, 400/230 kV 500 MVA Transformer, YNyn connected 1MRK 504 083-WEN
Setting example 2, 132/230 kV 40 MVA Transformer, YNd1 connected 1MRK 504 084-WEN
5
Introduction
Documents related to REB 670 Identity number

Operator's manual 1MRK 505 168-UEN
Buyer's guide 1MRK 505 172-BEN
Connection and Installation components 1MRK 013 003-BEN

Test system, COMBITEST 1MRK 512 001-BEN
Accessories for IED 670 1MRK 514 012-BEN
Getting started guide IED 670 1MRK 500 065-UEN
SPA and LON signal list for IED 670 1MRK 500 075-WEN
IEC 61850 Data objects list for IED 670 1MRK 500 077-WEN
Generic IEC 61850 IED Connectivity package 1KHA001027UEN
Protection and Control IED Manager PCM 600 Installation sheet 1MRS755552
Engineering guide IED 670 products 1MRK 511 179UEN
Latest versions of the described documentation can be found on www.abb.com/substationautomation
1.5 Revision notes
Revision Description
- First release
6
IED 670 engineering tool set
introduction
Chapter 2 IED 670

engineering tool
set introduction
About this chapter

Shows the general activities to engineer an IED 670 product. Introduces the tasks that can be
performed with the PCM 600 tool set.
7
IED 670 engineering tool set introduction Chapter 2
introduction
1 IED 670 engineering tool set introduction

The product family IED 670 is designed on the basis of the IEC 61850 standard. Beside others
the following IEC 61850 standards are relevant for the functional scope and for the engineering
process of the IED.
IEC 618505 for the functional scope of the Logical Nodes (LN)
IEC 618506 for the engineering process and the interchange of IED descriptive
information
IEC 618507 for the content description of the Logical Nodes and services
IEC 618507 and 81 for the communication protocol, when used
The reference to IEC 61850 for the application functions is indicated for each application func-
tion block in the technical reference manual (TRM) of the corresponding product. When a Log-
ical Node (LN) is specified in the standard for this function it is shown in the header in the TRM.
The description of each of these LN for engineering purposes follows the structure and rules as
specified in part 7 of the standard.
The IED 670 product family supports actually the following protocol standards:
IEC 6185081
SPA
LON
IEC 608705103
Using the engineering concept as defined by IEC 61850 for all supported protocols keeps the
advantages of the IEC 61850 standard for engineering. The IED needs only one protocol inde-
pendent way of engineering. The engineering of the communication protocol used is a separate
task and is an addition to the IED engineering.
The PCM 600 tool set which is used for the engineering of IED 670 products from ABB follows
this concept. The PCM 600 tool is a frame which allows the integration of additional tool sets
for the various ABB substation automation product families. Following the layout of substations
where several product families may be used for transmission and distribution arrays, the PCM
600 frame will have the tool sets for all IED products used in transmission and/or distribution
stations. The integration of these tools, IED products and protocols is done by so called con-
nectivity packages per product family and product or per protocol.
The PCM 600 tool set can be used for different purposes regarding the IED 670 products. A set
of special tools is available for the different applications. The applications can be organized in:
IED 670 product engineering

IED 670 signal engineering per protocol
IED 670 system monitoring
IED 670 product diagnostic
This manual is valid for the PCM 600 tool set supporting the IED 670 product family
8
IED engineering process Chapter 2
introduction
2 IED engineering process

Figure 1 shows the areas of engineering in IED 670 products. From one view the parts within
the IED which need to be engineered, from a second view the tools used to do the engineering
for that subpart and in a third view the boundaries of the IED itself. The additional elements used
to describe the substation plant structure are only informative and not used/needed by the IED.
They help to locate the IED in the organization of the substation and to operate with the object
structure as specified in the IEC 61346 standard part 1 and part 2.
Plant structure [PCM 600]
HSI NCC-GW PCM 600
Station bus
IED 1 (REx 670) [PCM 600]

IED n-1 IED n
Vertical communication Horizontal communication
[protocol dependent] [protocol dependent]
IED HMI
Application Functions (AF)
Signal text
AF-parameters [PST / CAP 531]
[PST]
------------------------
LEDs and Display

AF-settings [PST / SMT]
[PST]
------------------------
Single line diagram

AF-program [GDE]
[CAP 531]
I / O Boards and I / O Signals

[CAP 531 / SMT]
en05000590.vsd
Figure 1: Parts to engineer in an IED 670 product
9
introduction
The PCM 600 itself may be part of the substation automation structure. It might be connected to
the station bus on demand only or it may also be integrated in the substation control system
(SCS).
The PCM 600 tool is always connected to the IED 670 via Ethernet. This is independent of the
used communication protocol. When the communication protocol is based on Ethernet only one
interface is needed, and PCM 600 may use the same IP address. Communication with the
IED670 via LAN/WAN Network is dependent on customer's demands.
The engineering categories within the IED 670 can be split as shown in the figure 1 into:
the IED application functions (AF)

- the AF program [CAP 531]
- the AF configuration parameters [PST]
- the AF settings [PST]
the IO boards and IO signals [CAP 531 / SMT]
- the IO board organization within a case including the line differential com-
munication modules (when available) [CAP 531]
- the IO signals interface towards the application configuration [CAP 531 /
SMT]
the HMI [CAP 531 / SMT / PST / GDE]
- the different text strings used in the presentation on the HMI [CAP 531 /
PST]
- the operation of the LEDs [PST] and [SMT]
- the operation configuration for the LCD display [PST]
- the single line diagram used to control the bay; when a LHMI is used [GDE]
the IED communication [protocol dependent]
- the vertical communication to station level units
- the horizontal communication between units connected to the station bus
(when supported; protocol dependent)
As shown in figure 1 the following tool components are used for the engineering of the IED
product family IED 670:
PCM 600 Protection and Control IED Manager

CAP 531 Configuration and Programming tool
PST Parameter and Setting Tool
SMT Signal Matrix Tool
GDE Graphical Display Editor
Once the engineering for the different parts is done the results shall be downloaded to the IED.
Conversely some parts of the engineering information can be uploaded from the IED for various
purposes. Access to the PCM 600 is either
via the RJ 45 connector on the front panel (Ethernet)

via one of the possible Ethernet interfaces available on the rear.
10
introduction
PCM
600
Network
IED670
PCM
600
en05000591.vsd
Figure 2: Connecting PCM 600 to an IED 670
The connection between the IED and the PCM 600 is always via an Ethernet link, either on the
front or on the rear.
11
IED signal engineering per protocol Chapter 2
introduction
3 IED signal engineering per protocol

ABB supports various communication protocols between the IED and station level IEDs like the
network control center gateway (NCC-GW) and/or station human system interface (HSI):
IEC 6185081
SPA
LON
IEC 60870-5-103
Engineering of the communication is an additional second step in the complete engineering pro-
cess for an IED.
The engineering for each available protocol is different and is described in chapter 6 "IED 670
signal engineering per protocol".
12
IED monitoring process Chapter 2
introduction
4 IED monitoring process

Apart from the IED engineering process the PCM 600 can be used by a system operator to mon-
itor the primary process information available in an IED 670 parallel to the online runtime com-
munication to the NCC.
PCM 600 delivers two tools with different tasks for that reason:
a Disturbance recording handler tool (DRH)

an IED signal monitoring tool (ISM)
The DRH tool can be used to monitor all IED 670 products and other IEDs which can generate
a disturbance record (DR) and using the IEC 61850 protocol for DR file transfer. The IEC 61850
file transfer is defined in the standard in IEC 6185072 and its use on Ethernet is defined in
IEC 6185081. It can be used to read the DRs from the IEDs and to manage them. Together
with a task scheduler it is possible to monitor the IEDs permanently without operator interac-
tions.
The ISM may be used to read the actual process values out of the IED 670 for any purpose. The
ISM delivers a snap shot of the values on demand or periodically.
The PCM 600 operates independently and without influencing the ongoing runtime communi-
cation to the NCC.
The system monitoring tools are described in more detail in chapter 7 "IED monitoring process".
13
IED diagnostic capabilities Chapter 2
introduction
5 IED diagnostic capabilities

An additional set of tools enables a diagnostic of the IED 670, or the communication between
the IED 670 and the PCM 600 itself.
The two tools are:
the IED event viewer (IEV)

the OPC online diagnostic (OOD)
The IEV tool can be used to read all IED 670 internal system events and the process events
stored by the disturbance recorder. This information is also available on the IED 670 local HMI.
The OOD may be used to check the communication link between the IED 670 and the PCM 600
itself. It delivers a statistic on the different communication packages etc.
The diagnostic tools are described in more detail in chapter 8 "IED 670 diagnostic capabilities".
14
PCM 600 Tool set
Chapter 3 PCM 600 Tool set
About this chapter

This chapter explains the presentation of the PCM 600 tool and its tool components in the Mi-
crosoft Windows environment. The common data base concept and the possible options which
may be used to organize the different types of user and their capabilities.
The general description is valid for all tools. The description covers the main task of PCM 600
which is the engineering of IED 670 as start point.
15
1
16
Figure 3:
PCM 600 Tool Set
Function Compile
Block
Library
PCM 600 Tool set
Structure HW AF
builder Parameter Signal
Configuration Programm- LHMI
- Plant Settings Marshalling
IO signals ing Display Editor
- Communication Functionblocks IN and OUT
PCM 600 Tool set
PCM 600 CAP 531 PST SMT GDE
Project Data Base
AFC Settings
Download
IO Cnfg HMI Download
by
by PST
CAP531
PCM 600 Tool set for IED engineering overview

Download Download
by SMT by GDE
The PCM 600 is a state of the art tool set based on Microsoft.net technology.
Data transfer in
IED 670 SPA formats
en05000592.vsd
PCM 600 Tool set
Chapter 3
PCM 600 Tool set Chapter 3
PCM 600 Tool set
PCM 600 is a tool which allows to integrate a number of tool components for the different pur-
poses. In this document the tool components are called tools to simplify the understanding.
The above figure shows the organization and interaction principle of the PCM 600 and the cor-
responding tools for the IED 670 product family. This figure shows only the tools needed to do
the IED engineering. The other tools used for signal engineering, monitoring or diagnostic are
single tools without dependencies on other tools. The presentation and organization in PCM 600
is the same for all tools and described in this chapter.
General items:
all tools operate on a common project data base per project

all tools are independent of each other
all tools are responsible for download and/or upload to/from the IED
all tools operate with the data needed for their task
an engineering workflow is given in order to generate information needed by oth-
er tools
an application function block library (AFL library) is used per IED
an IED Capability Description file (ied.ICD) is used per IED to describe the ca-
pability of the used Logical nodes for the IEC 61850 signal engineering
PCM 600 uses the concept of projects. The content of a project depends on the customer's orga-
nization concept and task. The view of the IED engineering process for a substation and the op-
eration process for monitoring the grid might be different.
A meaningful engineering project may include a substation with all IEDs used. The dependen-
cies between the IEDs can be handled within the project.
In a monitoring project, a project might be a region with all its substations and their IEDs which
can communicate via IEC 61850 protocol for disturbance recording.
A PCM 600 project contains all files etc. which are used in a project for engineering or monitor-
ing.
The common project data base is handled per project by PCM 600 . It contains all files which
are needed, created and uploaded while running the project.
The engineering parts for an IED are different and so each tool is tailored to meet specific needs.
Splitting the information needed by the IED into different files gives the capability to only mod-
ify information for the specific part. It is then only necessary to download the changed informa-
tion.
In the workflow of the engineering process the CAP 531 tool has a central role. It generates the
basic information for the other tools. For more information see chapter 5 "IED 670 Engineering
process".
The content of the application function block library (AFL) per IED is determined by the ordered
IED configuration. Only those application functions ordered are available.
17
PCM 600 Tool set Chapter 3
PCM 600 Tool set
The IED Capability Description file (ied.ICD) is needed internally for the other tools as well as
to support a System Configurator tool (SC) when the complete station is engineered according
to the IEC 61850 standard.
The PCM 600 supports the inclusion of non ABB IEDs which run on IEC 61850 protocol as a
Generic IEC 61850 IED.
The PCM 600 tool set is installed / located in two areas of the PC or workstation:
the program part (normally on drive C:\)

the data part (directory PCMDataBase) with all files needed, created or uploaded
including the SQL data base (located on the drive with the largest free disk
space!).
An exported PCM 600 project is identified by its suffix: project.PCMP. Export and Import of a
complete project might be used to archive projects and reuse them in the event of modifications
or extensions. See chapter 4 section 4 "Managing projects" for more details.
When the DRH tool is used, all uploaded disturbance record file sets are stored within the PC-
MDataBase under the directory DR in a specific directory structure.
18
PCM 600 views and windows Chapter 3
PCM 600 Tool set
2 PCM 600 views and windows

The PCM 600 tool set runs under the operating system Windows 2000 or Windows XP. It is ex-
pected that the user is familiar with the handling and use of the Windows platform. In this chap-
ter only those items are explained and shown which are specific to PCM 600 but still based on
Microsoft windows methods.
When you start PCM 600 and no project is already selected you will get an empty window with
the base menubar and toolbar only. Once you have selected a project, you will be given the pos-
sibility to select different views. The start menu of a project may look like the menu shown in
the figure below.
Menubar & Toolbar
Project
Explorer Object
Place for
& Properties
selected tool
Object
Types
Output & Logging
en06000028.vsd
Figure 4: PCM 600: base screen example
19
PCM 600 Tool set
en05000580.vsd
Figure 5: PCM 600: base menubar
Possible views:
Project Explorer
Object Properties
Output
Object Type
Project Explorer
The Project Explorer window is the skeleton of the project organization. It is used to show the
project in two different structures:
the plant structure

the communication structure
The plant structure is the most commenly used view and shows the organization of the stations
in the geographical order top down from a defined highest level (e.g. the network control center
(NCC)) down to each IED logically connected to a bay in the station. The plant structure is used
to select the tools per IED.
The communication structure is not needed for normal operation. It is used to view the commu-
nication network and links from the PCM 600 to each IED. Only the private communication
from the PCM 600 to each IED is managed and handled by the PCM 600.
To select the communication structure do a right mouse click on the area next to the Plant Struc-
ture tab. Select communication and an additional page will be included which shows the com-
munication structure of the PCM 600
20
PCM 600 Tool set
en05000562.vsd
Figure 6: Plant structure: select communication structure
Object Properties
The Object Properties window is a standard Microsoft window which allows the user to view
and when needed to modify properties of the selected object. In the PCM 600 frame this window
is used by some tools like GDE to insert the IP address of the IED selected and some other prop-
erties like object naming in the HMI picture and so on. It might be necessary to check some prop-
erties for communication to adapt and synchronize the communication network . The shown
properties in the object properties window follow the selected object in the Project Explorer or
in a tool.
en05000559.vsd
Figure 7: PCM 600: Object properties window
Modifications are only possible in cells with their content shown in bold. Renaming of objects
can be done more easily by using the Rename capability in the plant structure, which is made
available by pressing the right mouse button.
21
PCM 600 Tool set
Output
The Output window is shown on the bottom array of the PCM 600 screen when selected. It is a
log script which is used by PCM 600 to list all activities, warnings, error messages etc. which
come up during operation of the PCM 600. It might be needed and used when a task does not
operate as expected. The information in the output list may provide a clue as to why it does not
operate etc. The Output view is not needed for normal operation and can be closed.
en05000558.vsd
Figure 8: PCM 600: Output window
Object Type
The window Object Type can be used to build up a plant structure using drag and drop and se-
lecting the object type from the list of possible objects. It is opened in the same place and then
the Plant Structure is presented. It is selected by clicking on the Object Types tab at the bottom
of the window.
22
PCM 600 Tool set
en05000556.vsd
Figure 9: PCM 600: Object Type window
The Object Type window contains some different panes depending on selected structure. For the
plant structure view the two panes are selectable by clicking the menubar General or Transmis-
sion IED.
More details to different views etc. are given in chapter 4 "Set up a project".
IED 670 tools

Each started IED tool will be visible in the residual screen area surrounded by the three windows
Plant Structure, Object Properties and Output. For normal operation only the Plant Structure is
needed and it is recommended to close the other two windows. More then one tool can be open
at the same time for one IED or for some IEDs in parallel. But only one tool at a time is active.
The tool is selected either by its tool tab or by selecting the IED.
One tool session operates only with the IED which was selected when the tool was started. To
use the same tool for different IEDs at the same time, additional tool sessions are started by se-
lecting the IED and the tool.
An exception to the parallel operation of several sessions of a tool is the CAP 531 tool. This tool
can only be started once for one IED and must be closed before it can be used on another IED.
In addition CAP 531 as the central tool to generate the basic information used by the other tools
can only run when all other tools are closed. This should be taken into account when CAP 531
is started.
2.1 The toolbar and the mouse

For each IED 670 tool the PCM 600 basic menubar and toolbar is expanded by additional
menu-lists and tool-icons. The different menu- and tool-bars are shown in chapter 5 "IED 670
Engineering process" when the use of the tool is described. Nearly all actions needed are already
presented as icons in the toolbar. This helps in routine jobs.
23
PCM 600 Tool set
The right button of the mouse is supported. Clicking the right mouse button opens a context sen-
sitive menu. This menu presents all possible actions and selections corresponding to the selected
object.
en05000555.vsd
Figure 10: PCM 600: Conditional selection by the right mouse button
Depending on selection as given in this example the alternative choice could be to select New....
In this case a new window will pop up and it shows the same selection possibilities.
en05000554.vsd
Figure 11: PCM 600: New object selection window
24
PCM 600 Tool set
Save tool engineering results

The PCM 600 stores all changes for which it is responsible directly in the database. This is useful
because these changes are only of type organization and have no influence on IED data. Chang-
es, additions etc. done within a tool are only moved to the project database when they are saved.
This possibility is context sensitive and will be displayed in the PCM 600 base menu bar under
File when a tool has the ability to save.
Save tool result
en05000574.vsd
Figure 12: PCM 600: Save tool result window
Cut, copy, paste, drag and drop

PCM 600 supports these functions where possible and useful. Depending on what it is and where
it is inserted as a copy a request to rename the object may appear. It is indicated as copy of ....
until it is given a unique name..
All other possibilities are self explanatory or Microsoft Windows standard.
25
PCM 600 options for operation Chapter 3
PCM 600 Tool set
3 PCM 600 options for operation

The options can be selected from the menulist Tools>Options. A pop up window will be dis-
played showing the entry point for the four different options. The four option windows are:
1. Log Configuration
to organize the log file which is produced during the sessions and shown in
the Output view of PCM 600
2. Category Manager
allows the definition of user groups with different rights to work with PCM
600 according to their need and task.
3. System Settings
specifies the basic decision about access rights for PCM 600 by the authen-
tication method
4. User Manager
is used to edit the list of persons or users which can use PCM 600 when an
authentication method is selected
3.1 Log configuration

As described in chapter 3 section 2 "PCM 600 views and windows" PCM 600 writes a log about
all activities. This log is made visible by selecting the view output. In normal operation and with
skilled knowledge about the way it operates the list will include only the history of your actions.
The output view may be used when a problem occurs and it is not apparent why. It is also used
when a failure occurs or when any other abnormal sequence which may be clarified by ABB.
The log file is requested by ABB when you communicate a failure or any other item. It is there-
fore requested to keep the log file history for this purpose. You may clear your hard disc from
the burden of the PCM 600 history from time to time.
Ways to configure the log:
Log File Base Name

- The default file name is extended by PCM 600 with the start date
(_yyyymmdd). This allows an easy identification in checking history.
Max. Log File Size
- This is the size per file! A daily file of 2 MB is hard to achieve . Be aware of
the volume when you select a daily file. Clear the history from time to time!
Log Filter
- The log filter allows the way to select the type of messages which should be
kept in the log file. The concept is that all types of messages above this filter
are stored. ABB recommend putting the filter on Error to be able to analyze
a sequence of actions in case a failure has occurred.
Log File Location
- You may select a separate directory outside the PCMDataBase where the file
will be stored.
Daily Log File
26
PCM 600 Tool set
- We recommend enabling this function. A daily file makes it easier for search
in a list as well to check other dates etc.
en05000616.vsd
Figure 13: PCM 600: Log configuration window
3.2 PCM 600 access

The set up and the possibilities to organize PCM 600 access can be seen as a branch with three
basic alternatives . For each of the three alternatives you have to set up information in the user
manager and select a user category out of the list described by the category manager.
Changes in the System Settings, Category Manager and User Manager can only be done by a
user of the category type System Engineer.
The used alternative is selected in the Authentication. Select the System Settings window to
choose the authentication.
27
PCM 600 Tool set
en05000614.vsd
Figure 14: PCM 600: Set authentication window
Set Data Access Password

This password is used to control access to the MSSQL$PCMSERVER. It is recommended not
to enter a password when several users have access to PCM 600. Only a single user with his own
PC may use this.
PCM 600 must be reinstalled and all projects will be lost if this password is not available!
User authentication
The tasks and action in each branch can be sorted like this:
1. Use Authentication
NO = no selection. Everybody can use the PC where this PCM 600 is in-
stalled.
YES = Authentication is used. Select the method with one of the two choices:
2. PCM Authentication or
3. Windows Authentication
Select the User manager.
28
PCM 600 Tool set
en05000613.vsd
Figure 15: PCM 600: User profile window
The User Manager window has four input fields. Three of them are used to define the access for
a user for either PCM or Windows authentication. The field Real Name might be used to identify
the user, when the user name is a short version of his name.
The PCM authentication uses the following inputs to identify a user:
User Name
Set Password (optional)
User Category. The user category is defined in the category manager. It belongs
to the user name and is not part of the authentication check.
The Windows authentication uses the following inputs to identify a user:
User Name
Windows Account.
User Category. The user category is defined in the category manager. It belongs
to the user name and is not part of the authentication check.
Set Password is not used!
PCM authentication
When the PCM authentication method is used a Login window pops up after start of PCM 600.
The user has to identify himself with his user name and the password when it is used for access
control.
29
PCM 600 Tool set
en05000610.vsd
Figure 16: PCM 600: Login window
Rules to set a password:
can not be empty

is at least 8 characters long
contains at least one special character (like ! , \, &, etc.)
starts and ends with an alphabetic character
contains at least one number
contains at least one uppercase character
contains at least one lowercase character
Windows authentication
In the Windows authentication method each user must have a different account on this PC. Only
in this case a selective input is possible. In this case the user has already identified himself to the
PC, when he started Windows. So a separate access control is not needed.
A user can change his password, by entering his old password once, and then the new password
twice. The system engineer can change passwords without knowledge of the old passwords.
30
PCM 600 Tool set
en05000617.vsd
Figure 17: PCM 600: User window with password setting
Category Manager
Different categories of default user are defined for PCM 600:
System Engineer
- has access to all tools and functions
- is the only one who can edit user management
Application Engineer
- has access to all tools for engineering the IEDs
- has access to the system monitoring tools to check during commissioning
phase the correct operation of the IED
- has no user management rights
System Monitoring User
- has access to the system monitoring tools to monitor the IEDs during opera-
tion
- has no access to the engineering tools
- has no user management rights
31
PCM 600 Tool set
en05000615.vsd
Figure 18: PCM 600: Category manager window
32
Connectivity package version Chapter 3
PCM 600 Tool set
4 Connectivity package version

As described in the beginning PCM 600 is a tool which allows the user to include the engineer-
ing tool components for product families of ABB products for transmission and distribution. In
the way you are using ABB products it might be that you will have several sets installed using
the concept of connectivity packages.
How to install a new product package or to add an additional communication protocol is de-
scribed in the PCM 600 Installation and Commissioning Manual.
To engineer the ABB IED 670 product family you must have enabled the use of these tools and
protocols in the connectivity package manager . Please check that before you may start the PCM
600.
en05000561.vsd
Figure 19: Connectivity manager: version selection window
Always use the latest version of a tool package or protocol. This can be easily done in the
menubar Set Latest.
In the above Connectivity Package Manager window the following packages are available
33
Connectivity package version Chapter 3
PCM 600 Tool set
Generic IEC 61850 IED connectivity Package

- This package is only needed when the station communication is using IEC
61850 protocol.
- It has to be used, when the DRH tool is used to read the DR files from all
IEDs running the IEC 61850 protocol. The Generic IEC 61850 IED allows
the integration of any IEC 61850 IED in the plant structure.
- It can also be used to include the ied.ICD file of any IED in the station.SCD
file. This might be helpful when the station configurator tool requests a com-
plete SCD file of all IEDs in a station.
IEC 61850 Connectivity Package
- This package is needed for IED 670 products, which communicate with
PCM 600 on Ethernet, TCP/IP and using elements of the IEC 61850 proto-
col.
LON Connectivity Package
- This package is not needed for IED 670 products. It is used for products us-
ing LON to communicate with PCM 600.
IED 670 Connectivity Package
- This package is needed in the latest revision to engineer IED 670 products.
It contains the description of the IED 670 products.
SPA Connectivity Package
- This package is not needed for IED 670 products. It is used for products us-
ing SPA to communicate with PCM 600.
34
Set up PCM 600 communication link per IED Chapter 3
PCM 600 Tool set
5 Set up PCM 600 communication link per IED

The communication between the IED and the PCM 600 is independent of the used communica-
tion protocol within the substation or to the NCC. It can be seen as a second channel for com-
munication.
The communication media is always Ethernet and the used protocol is TCP/IP.
Each IED 670 product has an Ethernet front connector for PCM 600 access. Depending very
much on the station concept and the used station protocol additional Ethernet interfaces may be
available on the rear side of the IED 670. All Ethernet interfaces can be used to connect PCM
600.
When an Ethernet based station protocol is used the PCM 600 communication can use the same
Ethernet port and IP address. The IED 670 is able to separate the information belonging to the
PCM 600 dialog.
For the connection of the PCM 600 to the IED two basic variants have to be considered.
direct point to point link between PCM 600 and the IED 670
indirect link via a station LAN or from remote via a network
The communication procedures are in both cases the same.
The physical connection and the IP-addresses must be configured in both cases before a dialog
can start. The steps to do this are:
Set up or get the IP-addresses of the IED 670s

Set up the PC or workstation for a direct link or
- in this case get a special null-modem cable (Rx, Tx cross-wired) for the di-
rect link between PCM 600 and IED 670
Connect the PC or workstation to the network
Configure the IED 670 IP-addresses in the PCM 600 project for each IED these
are used by the OPC interface of PCM 600 for communication
IP addresses of IED 670 products

The IP address and the corresponding mask can be set only via the local HMI for each available
Ethernet interface in the IED 670. Each Ethernet interface has a default address ex factory when
the complete IED 670 is delivered. This is not given when an additional Ethernet interface is in-
stalled or an interface is replaced.
The rules etc. for the configured IP addresses are part of the project.
Point to point link

A special cable is requested to connect two physical Ethernet interfaces together without a HUB,
router, bridge, switch etc. between. The Tx and Rx signal wires must be crossed in the cable to
connect Tx with Rx on the other side and vice versa. These cables are known as null-modem
cable or cross-wired cable. The minimum length should be about 2 m. The connector type is
RJ45.
35
PCM 600 Tool set
IED670
RJ45
PCM600
Tx Tx
Rx Rx
en05000810.vsd
Figure 20: Point to point link between IED 670 and PCM 600 using a null-modem cable
Set up a PC for a direct link

The following description is an example valid for standard PCs using Microsoft Windows oper-
ating system . The example is taken from a Laptop with one Ethernet interface.
The procedure is as follows:
1. select the Local Area Connection

2. select Properties in the shown status window
3. select the TCP/IP protocol from the list of configured components using this con-
nection and open Properties
4. choose Use the following IP address and type in an IP address and Subnet mask
which you can define. Make sure that you are outside the range of addresses used
by the IED 670s.
5. close all open windows and start PCM 600
Remark
Administrator rights are requested to change the configuration as described above.
36
PCM 600 Tool set
en05000812.vsd
Figure 21: Step 1: select the Local Area Connection
en05000813.vsd
Figure 22: Step 2: select Properties in the status window
37
PCM 600 Tool set
en05000814.vsd
Figure 23: Step 3: select the TCP/IP protocol and open Properties
38
PCM 600 Tool set
en05000815.vsd
Figure 24: Step 4: specify a TCP/IP address and Subnet mask for the PC
Set up the PC to access the IED 670 via a network

This task is very much dependent on the used LAN/WAN network. A description of how this is
done is beyond the scope of this manual..
Enter IED 670 IP-address in the project

There are two ways of entering the given IP-address of an IED 670 in a project which is used by
PCM 600 to communicate with the IED 670.
1. via the first window of the wizard by including a new IED 670 in a project
2. by entering the IP-address of the IED 670 in the Object Properties window
select the IED to enter the IP-address
open the Object Properties window
place the cursor in the IP Address row and enter the IP-address.
39
PCM 600 Tool set
en05000643.vsd
Figure 25: Possibility 1: IP-address via first Wizard window
en05000811.vsd
Figure 26: Possibility 2: IP-address via IED Object Properties window
The used alternative depends very much on the time at which the IP-address is available. Alter-
native 2 allows a change of the IP-address at any time.
The OPC Online diagnostic tool (OOD) can be used to test the communication between the PCM
600 and the IED 670. See chapter 8 "IED 670 diagnostic capabilities".
40
PCM 600 Tool set
5.1 Set up communication link per Generic IEC 61850 IED

A Generic IEC 61850 IED (Gen-IED) can only communicate with the PCM 600 in the same way
as the IED 670 products are when using the IEC 61850 protocol. That is only given for the dis-
turbance file reading from the relays. The DRH tool is responsible for that task. For more details
about the DRH tool see chapter 7 section 1 "Disturbance record handler DRH".
In this way the PCM 600 needs for a Gen-IED the IP-address only. For a Gen-IED only one pos-
sibility is given.
enter the IP-address of the Generic IEC 61850 IED in the Object Properties win-
dow
- select the Gen-IED to enter the IP-address
- open the Object Properties window
- set cursor in the row IP Address and enter the IP-address of the Gen-IED (see
figure 26).
Remark
PCM 600 needs to know the basic configuration of the Gen-IED to be able to read the DR files
etc. This is a IEC 61850 description file defined as gen-ied.ICD or also possible as gen-ied.SCL
file. The file has to be delivered by the supplier of the Gen-IED. This file has to be loaded for
the Gen-IED after it is selected and installed in the plant structure. See chapter 4 section 3.4 "Ge-
neric IEC 61850 IED" for more details.
41
PCM 600 Tool set
42
Set up a project
Chapter 4 Set up a project
About this chapter

This chapter describes how a project is defined and activated by PCM 600. It explains the dif-
ferent steps required to integrate the needed IEDs into a project and how PCM 600 manages the
projects.
43
Set up a project Chapter 4
Set up a project
1 Set up a project
PCM 600 operates on projects.
A project contains all information about the IEDs, the engineering of the IEDs,
the uploaded and downloaded files and internal files produced by PCM 600 and
the tools used to run the project.
A project is stored under the directory of PCMDataBase on the PC or workstation
on which PCM 600 is installed. PCM 600 runs various projects under the control
of PCM 600. But only one project can be active at a time. These imported projects
are handled by the MSSQL$SERVER which is part of PCMDataBase.
Projects may be grouped into two categories:
- Engineering projects. Engineering projects are focused on the complete en-
gineering of an IED, a substation with its IEDs or at least of several substa-
tions and their IEDs. The most practical size for a project might be a
substation.
- System monitoring projects. System monitoring projects are focused on the
monitoring information from the operating IEDs located in several substa-
tions. The most practical size for a project depends on the structure of the
grid and customer's responsibility.
Tasks in an engineering project:
build up a plant structure for the substation

engineer the IEDs
engineer the IED communication to the station level IEDs and between the IEDs
for operation
set up / check the communication access of the PCM 600 to all IEDs to upload
and download files
load all IEDs with their configuration files
commission the IED and substation
archive the project
Tasks in a system monitoring project:
build up a plant structure which includes all IED 670 products and Generic IEC
61850 IEDs within the grid section which should be monitored
set up / check the communication access of the PCM 600 to all IEDs
use and configure the DRH tool
- configure the task scheduler to periodically monitor IEDs for new reports
- read disturbance files and analyze them on demand
- archive the disturbance record files from time to time
use ISM tool
- read IED process signals on demand
44
Set up a plant structure Chapter 4
Set up a project
2 Set up a plant structure

The plant structure is used to identify each IED in its location within the electrical grid. It is a
geographical image of the substation and the bays within the substation.
You may build up the plant structure according to your project requirements. To do this PCM
600 offers some elements which build the hierarchical order from Center down to the IEDs in a
bay. In a system monitoring project the plant structure is an easy way to find the path to the pro-
tection IED. The following levels are available:
1. Project = Center
2. Region = when your grid might be subdivided into regions this level should be
used in addition (optional)
3. Substation = Name of the substation
4. Voltage Level = identifies to which grid type or part in the substation the IED be-
longs to
5. Bay = Bay within the voltage level
6. IED = selection of the IED which is used in the bay. Several IEDs are possible
within a bay (e.g. one control IED and two protection IEDs)
Level (2.) is optional all other level are a must to identify an IED.
Once a plant structure is built the identification should be renamed by the names/identifications
used in your grid. Use the right mouse button to build the plant structure and to rename the ele-
ments.
en05000565.vsd
Figure 27: PCM 600: Set up a plant structure
Building a plant structure using the Object Types view

This is useful when a complete grid with a large number of IEDs have to be built.
Steps to build a plant structure:
select the Object Types view
45
Set up a project
place the Object Types window beside the Project Explorer window by selecting
the Object Types tab and move it outside the Project Explorer window.
select the General pane
select the elements you need and place them in the plant structure by drag and
drop
to select an IED open the Transmission IED pane and follow the procedure de-
scribed in the next chapter
close the Object Types window
select IED
en05000557.vsd
Figure 28: PCM 600: Set up a plant structure by using Object Type window
2.1 Naming conventions for IEC 61850

This section is only valid when the IEC 61850 protocol is used. The following definition is taken
from IEC 618506 clause 8.4:
The SCL model allows two kinds of object designation:
1. A technical key, which is used on engineering drawings and for signal identifica-
tions. This is contained in the attribute name as identification of each object. If
this value is used as reference to an object, it is contained in an attribute name
46
Set up a project
starting with a string denoting the reference target object type, and ending with
the string Name. The technical key is used within SCL for referencing other ob-
jects. Observe that name is a relative identification within a hierarchy of objects.
2. A user oriented textual designation. This is contained in attribute desc. Attributes
are not allowed to contain carriage return, line feed or tab characters. The seman-
tics of desc shall also be relative within an object hierarchy.
End of reference to the standard.
PCM 600 takes care for these two possibilities. The two possible signal designations are avail-
able per object in the object properties for all hierarchical levels beginning with the station as
highest level.
The technical key is automatically generated based on the rules and type specifications of IEC
61346 and the extended definitions done for substations by a technical committee. The technical
key is shown in the Object Properties under SCL TechnicalKey.
the start point is the station which is predefined by AA1 where 1 is the index.
the second hierarchical level is the voltage level. The voltage level can be select-
ed in the Object Properties from a drop list. The corresponding character is auto-
matically included in all objects.
the bay and the IED is appended with the coding defined in the IEC 61346 stan-
dard and the substation definition lists.
The user oriented textual designation is visible in the plant structure for each object. It is the
name given by default or changed via the Rename possibility. It is shown in the Object Proper-
ties in the row Caption.
en06000029.vsd
Figure 29: PCM 600: IEC 61850 signal designation concept
In the above figure the bay named in the example B_TR42 is visible in the object properties
with the two designations. The technical key AA1C1Q1 can be read like this:
47
Set up a project
AA1 = station 1 in the project

C1 = voltage level from 380 to 420 kV
Q1 = the first bay in the voltage level
48
Selection of an IED Chapter 4
Set up a project
3 Selection of an IED
A control or protection IED 670 can be delivered in three general versions:
order specific IEDs

pre-configured IEDs
base IEDs
When selecting an IED 670 a wizard is displayed which helps you make the correct selection.
Apart from the IED 670 it is possible to select a Generic IEC 61850 IED. This is only needed
and useful, when the IEC 61850 protocol is used.
3.1 Order specific IED

An order specific IED is described by:
the delivered hardware

the delivered lists of selected functions
It includes:
a set of ordered functions available for engineering the logic and operation of the
functions
It does not include:
any configuration of the application configuration program

any engineering preparation for the IO hardware and IO signals
no defined settings other then the default values
It is important to understand, that the list of delivered functions correspond to the list of available
function blocks in the IED itself. You can not use more function blocks than ordered.
An IED is selected by:
selecting the correct IED version 1.0 onwards

type in the IP address for the IED to communicate with PCM 600. This IP address
may be the same then used for the communication protocol (e.g. IEC 61850 or
DNP 3.0 on Ethernet) but it must not be the same. This IP address is the link to
the PCM 600 tool set.
Browse to the folder where your order specific zip-file is stored.
When you do not use an order specific configuration indicate that in the selection
box.
49
Set up a project
en05000643.vsd
Figure 30: Order specific IED selection
3.2 Pre-configured IED

A pre-configured IED is described by:
the delivered hardware loaded with the basic functions and logic, ready for use
after some project specific engineering additions like IO signal marshalling etc.
the delivered engineering configuration
- configured logic with basic functions active for direct use
- predefined signals for IO which needs only to be routed to physical IO boards
the optional functions are available in the engineering tool fully configured and
presented in a template
It does not include:
adaptations to the project specific settings

IO signal routing for application specific IOs
A pre-configured IED is ready to use after some minor engineering additions, which are in any
way project specific. Similar to the order specific version it includes only those functions and
options which are ordered and available in the IED itself.
50
Set up a project
en05000644.vsd
Figure 31: Pre-configured IED selection
When the pre-configured IED versions are not delivered in a zip file. Skip this window by se-
lecting No PreConfig File. Check the availability of pre-configured IED versions in the CAP
531 template folder as described in chapter 5 section 2.2 "Customized application configuration
templates".
3.3 Base IED

A base IED is described by:
possibility to set up and engineer an IED for special use which is not possible by
a predefined IED version for your customer project
possibility to select all options and base functions as specified for the IED type
to be used to develop customer specific IED configurations which can be used
after coordination with ABB to be loaded in order specific IEDs after delivery of
the hardware.
This type of IED is selected, when one of the two earlier alternatives has not been chosen.
3.4 Generic IEC 61850 IED

This section is only valid, when the IEC 61850 protocol is used.
The Generic IEC 61850 IED (Gen-IED) may be installed when:
51
Set up a project
a project will be configured for disturbance recording handling and protection re-
lays from other vendors using IEC 61850 for communication shall be monitored
also.
- apart from the IP-address for the Gen-IED a basic ied.ICD file is needed to
establish access to DR files in the IED.
- for more details see chapter 7 section 1 "Disturbance record handler DRH".
a station.SCD file that contains all bay level IEDs (IED 670 devices and IEDs
from other vendors) with their ied..ICD files shall be exported.
- import the ied.ICD file per Gen-IED
- export the updated Gen-IED ied.SCD file for further use in the Gen-IED
- for more details see chapter 6 section 2 "IEC 61850 protocol".
en06000031.vsd
Figure 32: Generic IEC 61850 IED selection
When a Gen-IED is selected and placed in the station configuration it is necessary to define the
IP-address of the Gen-IED (see chapter 6 section 5.1 "Set up communication link per Generic
IEC 61850 IED") and to install the basic configuration to be able to read disturbance files out of
the relay. The supplier must supply an ied.ICD or ied.SCD file for each IED.
Import of an ied.ICD file for a Gen-IED

After a Gen-IED is installed it is useful to load the corresponding ied.ICD file also.
select the Gen-IED

select Import IED SCL ...with the right mouse button out of the menu
a standard Microsoft windows for file selection pops up. Navigate to the directo-
ry where the ied.ICD or .SCD file is located and open the file for import
a selection window SCL Import Options pops up
leave the Import Type as set to Update PCM Structure from SCL. For more de-
tails about this item see chapter 4 section 2 "Set up a plant structure".
open the Advanced Options
because it is a Gen-IED it must be possible to replace the IED object types with
the known Generic IEC 61850 IED object types. Select the Replace ... alterna-
tive
52
Set up a project
the Gen-IED is a not known IED until now for the PCM 600. It must be possible
to overwrite the default IED type with the type defined in the vendors IED. Select
Allow overwriting ...
en06000032.vsd
Figure 33: Generic IEC 61850 IED import of ied.ICD file
The SCL file import starts and a progress window shows the status. A message will indicate the
conclusion of a successful import. The IED name will not change by loading the file. Adapt the
IED name to reflect the nature of the project with the Rename selection in the right mouse button
menu.
53
Managing projects Chapter 4
Set up a project
4 Managing projects
The PCM 600 manages the project in its own PCMDataBase which is placed on the PC or work-
station running the PCM 600 tool set. The projects imported to PCMDataBase or set up in PC-
MDataBase are the actual available projects for PCM 600. They can be selected via the menu
bar File. But once again only one project at a time can be open.
These projects are handled by the MSSQLPCMSERVER which is included in the PCMData-
Base.
It is possible
to import projects
to create new projects
to export projects
to delete projects out of the PCMDataBase
A PCM 600 project is identified by its suffix "project.PCMP"
To open a project select File>Open/Manage Projects. The Open/Manage Project window will
pop up.
New Import
en05000552.vsd
Figure 34: PCM 600: Open / Manage Project window
Choose an existing project

open the tree Projects on my computer. Projects available in the PCMDataBase
are listed.
54
Set up a project
select a project from the list and click Open Project.

you may also select the project in the traditional way from the list shown in the
menubar File>list of last used projects.
Import a project
open the tree Projects on my computer.
select the icon Import Project.
a standard Windows file selection window will pop up
navigate to the directory where you have stored exported projects
select your project to import (suffix = PCMP)
PCM 600 will import the project. The contents will be reorganized according to
the PCM 600 internal needs. Depending on project size this can take some time.
the imported project will be listed under the tree Projects on my computer.
select the imported project and open it.
en05000608.vsd
Figure 35: PCM 600: Import a project window
Create a new project

open the tree Projects on my computer
select the icon New Project
a New Project window will pop up
give the new project a name and include a description (optional)
PCM 600 will set up a new project
the new project will be listed under the tree Projects on my computer
55
Set up a project
select the new project and open it
en05000609.vsd
Figure 36: PCM 600: Create a new project window
export a project
select the project you want to export
select the icon Export Project
a standard Windows file selection window will pop up
navigate to the directory where you want to store the project
the file name may be adapted to your needs
PCM 600 prepares the contents of the project for import. The procedure is oppo-
site to the task listed under import a project
the project still exists in PCM 600 and can be continued to be used
delete a project
select the project you want to delete
select the icon Delete Project
a warning window will pop up
be sure you have exported the project first before using it later
confirm that you want to delete the project
PCM 600 will delete all files etc. about this project from its PCMDataBase
56
Set up a project
rename a project
this is only possible when the project is not active in PCM 600
close the project when active
select File>Open/Manage Projects. The Open/Manage Project window will pop
up.
select the project which should be renamed
click Rename using the right mouse button
rename the project and close the naming field
PCM 600 will rename the project
57
Set up a project
58
Chapter 5 IED 670

Engineering
process
About this chapter

This chapter describes the operation of each tool needed to engineer an IED 670. It explains the
different steps for each tool.
59
IED Engineering process Chapter 5
1 IED Engineering process

It is expected that the contents of the previous chapters are known.
IED library
order specific volume
Application IO
CAP 531
function hardware
build
logic organisation
CAP 531
compile
Workflow
Application IED description files

program(s) (includes ied.ICD file)
IO
Settings HMI
Config.
CAP531 SMT PST GDE

load build/load build/load build/load
IED
en05000593.vsd
Figure 37: IED 670 engineering workflow
The following points describe the engineering sequence in a summary form. See figure 37 for
reference.
60
IED Engineering process Chapter 5
1. the selected IED 670 contains an application function library. The volume is de-
pendent on selected IED template
order specific IED
pre-configured IED
product base IED
2. in Cap 531 you have to define the used IO boards and LDCM modules and place
them in their physical position in the case
3. in CAP 531 the application function logic has to be programmed
modified and adopted on the basis of the pre-configured IED
build up on the basis of a selected template from the template library or in
worst case start from scratch
select and configure all IO signals which have a physical presentation to the
corresponding signal matrix function blocks (SM-function block). Either on
the IO boards or on the LDCM signal set.
4. after step 2 and/or step 3 the application configuration program must be com-
piled. This results in some files which include the main files
ied.ICD file
the downloadable application configuration program file
when the CAP 531 is closed the PCM 600 takes over the results which may
take some time. The plant structure presentation of the IED will be extended
by the structure of the settings organization.
5. when step 2 and step 3 are completed, the SMTsupports you when configuring
signal marshalling between the physical IO signals on the IO boards etc. and the
logical signals defined in step 2.
6. the configuration and the settings for the IED and for the included application
function groups have to be completed and adapted to project needs using the PST
tool
7. when a large HMI is available the GDE has to be used to draw the single line
schematic of the bay
8. when all steps are completed the files must be downloaded to the IED. This may
also be done directly per tool after successful engineering.
Points 5 to 8 can be done in any order.
61
Configuration and Programming tool CAP 531 Chapter 5
2 Configuration and Programming tool CAP 531

The CAP 531 is selected either from the menulist in the menubar or with the right mouse button.
The IED must be selected as object.
When CAP 531 is selected all other tools that are actual running will be closed (after confirma-
tion) and CAP 531 starts in a new separate screen.
The CAP 531 is an approved tool and is also used by the former REX 500 product line. CAP
531 is a application configuration program development tool. The operation of the CAP 531 is
explained in the separate CAP 531 user's manual. It is included on the PCM 600 Installation CD.
The CAP 531 is password protected. The default password is: ABB (capital letters) or abb (small
letters). You may change it when necessary. See the instruction within the CAP 531 user's man-
ual.
en05000575.vsd
Figure 38: CAP 531: tool menubar
To use CAP 531 a sufficient knowledge of application configuration programming is recom-

mended. A complete programmed IED with its worksheets may look like the presentation in fig-
ure 39.
62
en05000567.vsd
Figure 39: CAP 531: IED 670 worksheet tree window
When you have finalized your work in CAP 531 you will have a usable application function con-
figuration. You have to compile the complete IED to generate the files which will be imported
by PCM 600.
Remark
PCM 600 will only import the files when the compilation has indicated no errors! Warnings are
ignored.
Import of the compiled application configuration program

When you close the CAP 531 tool, PCM 600 starts transfer the results to its project data base. It
imports the IED Capability Description file (ied.ICD). The set of parameters and settings is eval-
uated. The plant structure below the IED is extended by the structure of the settings. A successful
integration is indicated by a final message window.
63
en05000569.vsd
Figure 40: CAP 531: Import of the compiled IED to PCM 600
en05000570.vsd
Figure 41: CAP 531: Extension of the plant structure per IED with the settings tree
Download or Upload of the application configuration program

A final application configuration program has to be downloaded by the CAP 531 tool. In the
same manner it is possible to upload the application configuration program from the IED. The
upload and download are only possible directly under CAP 531.
64
2.1 Engineering the IO interfaces

The task described in this chapter is a precondition for the use of the Signal matrix tool (SMT).
To do the signal marshalling as described in chapter 5 section 3 "Signal matrix tool SMT". It is
necessary to prepare the first two steps by using CAP 531. It might be useful to read the SMT
section first.
The two steps are:
engineer the IO boards to the correct slots in the IED 670 case. Engineer the po-
sition of the Line Differential Communication Module (LDCM) mezzanine
boards when available.
program the input/output signals which have a physical channel as source or des-
tination to the signal matrix function blocks for each signal type.
IO board configuration
Steps to do the IO board configuration:
start the CAP 531

select the IED 670 icon
select via the menubar: Edit>Function Selector
the Function Selector Tool window will pop up
the next steps have to be repeated for each IO module which must be located
- select the Function Group which is the indirect selection of the physical po-
sition. This is shown by the corresponding Selector identification.
- select the board type out of the conditional presented Value list. The Descrip-
tion field contains an explanation about the selected board type.
- press Set to confirm the configuration of that board
- the result is shown in the lower half of the window (Selected Values)
- repeat until all IO modules, transformer modules (TRM) and when applica-
ble the LDCMs are placed in a position
press Save to store the configuration
exit the Function Selector Tool
CAP 531 updates its configuration after the Function Selector tool is closed.
65
en05000566.vsd
Figure 42: CAP 531: Function selector tool window
Remark
The IO board configuration is transferred to PCM 600 for further use when CAP 531 is closed.
IO signal matrix function block programming

Special interface function blocks are available to route the IO signals to the physical channels.
The function blocks are described in the TRM. The following types are used:
SMAI = AC analog input signals (from Transformer Modules)

SMBI = binary input signals (from BIM or IOM-BI part)
SMBO = binary output signals (from BOM or IOM-BO part)
SMMI = mA analog input signals (from MIM)
Only those function block types are identified by the SMT for the IO signal interface. The first
two characters identify them as Signal Matrix function blocks (SM-function block).
Steps to do the SM-function block programming:
start the CAP 531

open or create the appropriate worksheets
the next steps have to be repeated for each SM-function block until all IO signals
are routed to one of the SM-function blocks
- select an IO SM-function block from the list of available SM-function blocks
- connect the IO signals to the signal inputs of the SM-function blocks.
- give the signals and the SM-function block a name. These names are used by
the SMT tool to present the signals for marshalling in the matrix (Y-direc-
tion)
66
- repeat until all IO signals are connected to a SM-function block

close the worksheets
compile the whole Terminal or the associated worksheets
only those SM-function blocks which have at least one signal connected are
shown in the SMT matrix!
en05000568.vsd
Figure 43: CAP 531: Worksheet with SM-function block block
Remark
The configuration is taken to PCM 600 only after compilation and CAP 531 is closed. SM-func-
tion blocks have to have at least one signal linked to an input to be taken by the SMT and shown
in the signal list.
2.2 Customized application configuration templates

Control and protection IEDs are most likely very similar for a specific bay type or protection
variant. To build up an IED configuration library which may contain master configurations and
project specific variants should be possible.
CAP 531 supports this by maintaining a template library. It is possible to generate a template as
well as to insert a template to or from the library. For more details see CAP 531 user's manual.
The template library is part of the CAP 531 tool and therefore project independent.
Access to the library is available in CAP 531 under Edit >Insert Template or Edit>Generate
Template.
67
Signal matrix tool SMT Chapter 5
3 Signal matrix tool SMT

The SMT is selected either from the menulist in the menubar or with the right mouse button. The
IED must be selected as object.
en05000581.vsd
Figure 44: SMT: tool menubar
Extension to the menubar
IED
- Write configuration to IED
Extension to the toolbar (from left to right) not fully included in the menubar selections:
write signal matrix configuration to IED

collapse/expand all IO signals (Y-direction)
collapse/expand all IO boards (X-direction)
Print matrix window for selected signal type
Preview pages for printing
The task of the Signal matrix tool (SMT) is to marshal the IO signals between the FBs in the
application function program and the physical channels given by the IO boards and LDCMs. The
task can be subdivided into three steps.
step one: engineer the IO boards to the correct slots in the IED 670 housing. En-
gineer the position of the LDCM mezzanine boards.
step two: program the input/output signals which belong to a physical channel to
the function blocks for each type.
step three: link the signal on both interfaces by doing crosses in the matrix pre-
sented by the SMT
Step one and two have to be done in CAP 531 and are described in chapter 5 section 2.1 "Engi-
neering the IO interfaces".
Principle of operation
Figure 45 explains the principle operation and task of the SMT. The task of the SMT is to do the
link between the IO hardware interfaces on one side and the signal interfaces given by the signal
matrix function blocks (SM-FB) on the other side.
68
BIM
Binary IOM-BI SMBI
Input
LDCM Receive
HMI
LEDs LEDs
SMBO
BOM
Binary
IOM-BO
Output
LDCM Transm
SMMI
MIM
Analog TRM
Input SMAI
LDCM Receive
Analog LDCM Transm LDCM Transm

Output
GOOSE GOOSE Inputs

IEC 61850 ONLY !!! Goose_Bin
Input blocks Intl_AP
Hardware Signal Matrix

IO interfaces IO FBs
(X-direction) (Y-direction)
en05000620.vsd
Figure 45: SMT: Operation principles
A cross in the SMT matrix establishes a wired link between the IO channel (Y-direction) and
the IO signal (X-direction).
As shown in the drawing:
69
a physical input signal can be routed to several SM-FBs and/or to a LED on the
HMI
a SM-FB output signal can be routed to several physical output channels and/or
to a LED on the HMI
LDCM handling
The LDCM is a special module. The data interchange with other LDCMs contains all four types
of signal:
AC signals receive = analog input

AC signals transmit = analog output
binary signals receive = binary input
binary signals transmit = binary output
The block AC signals transmit is not represented by a SM-FB. The SMT includes a special
signal block in the IO signal list (Y-direction). Following the principles of line differential pro-
tection the direct AC signals coming from the TRM will be routed to the LDCM Transmit signal
block.
GOOSE Input blocks

This signal type is only valid when the IEC 61850 protocol is used.
GOOSE messages are sent in horizontal communication between the IEDs. To engineer the re-
ceived signals from a GOOSE message it is necessary to marshal these signals to specific receive
function blocks.
For more details see chapter 6 section 2 "IEC 61850 protocol" .
70
en05000618.vsd
Figure 46: SMT: Data synchronization report window
Step three
The sequence in step three to generate the complete IO signal routing is as follows:
select the IED and start the SMT

- the SMT compares its most recently saved signal configuration with the ac-
tual IO signal configuration in PCM 600 when started. Differences will be
listed and shown in a window. This might be printed and shall be confirmed
by closing the window.
perform step three and make the crosses for all signals
- the SMT contains three (four) different matrix windows.
- Binary Input, Binary Output, Analog Input
- and GOOSE Input when IEC 61850 protocol is used and horizontal com-
munication needed.
- open, not marshalled signals are allowed and not checked for completeness.
- It is the responsibility of the user to verify the completeness of the IO signals
and the links
save the IO signal marshalling configuration
download the configuration to the IED
71
en05000572.vsd
Figure 47: SMT: Matrix window example binary input signals
en05000573.vsd
Figure 48: SMT: Matrix window example binary output signals
72
en05000571.vsd
Figure 49: SMT: Matrix window example analog input signals and LDCM
Remark
Binary input signals: A physical input signal from an IO board can be routed to several logical
signals
Binary output signals: A logical output signal can be routed to several physical output channels
(relays)
73
Parameter and setting tool PST Chapter 5
4 Parameter and setting tool PST

The PST is selected either from the menulist in the menubar or with the right mouse button. The
en05000586.vsd
Figure 50: PST: tool menubar
Customize
- allows modification of the colors used in the parameter list. Please leave the
colors untouched.
IED
- Read parameters from IED
- Write parameters to IED
View extensions
- Parameter layer
- Parameter filter
- Group options
- Browse options
- Parameter warnings
All functions extended in the menubar are also available in the toolbar with their icon.
In this chapter the variables are identified by the word parameter. Parameters in this sense are
setting parameters and configuration parameters. In the other chapters the definition parameter
and setting are used according to their real definition.
To use the PST some additional points about the presentation concept need to be explained first.
These points are:
the parameter list and the definition of the different columns

selection of different views for the parameter list
input field and possible entry types
74
Structure of the parameter list

Each parameter is presented in the parameter list in a row with six columns:
1. Group / Parameter Name

The organization of the parameters follows the structure also visible in the
plant structure, starting with settings. The parameters are organized in a log-
ical structure. This column identifies either the hierarchical level or it identi-
fies a parameter by its name.
The used parameter names are identical with the name used in the parameter
and setting lists in the TRM. This gives a direct reference between the PST
list and the description in the TRM.
2. IED Value
Contains the parameter value which is uploaded from the IED. That means
the actual value used in the IED 670.
3. PC Value
Contains the parameter value currently available in the PCM 600.
This is the input field where a parameter can be changed manually. Input is
only possible in fields which have a white background color.
Only two versions of input fields are given. Version one is just a value which
is checked against the limits. Version two is a drop down listbox. One choice
has to be selected.
4. Unit
5. Min
The last two columns inform about the allowed range for the parameter,
when available. An input value is checked against these limits and ignored
when it is outside this range.
6. Max
en05000576.vsd
Figure 51: PST: Parameter list window
75
View option
The different view options may be used to facilitate the search for special parameters.
Parameter layer
Mainly on protection application functions you can have a long list of parameters which are
needed to set up the function to the primary process etc. Not all of them are needed when it
comes to the configuration of the parameters for the configuration e.g. of timers and settings for
grid protection, which is mainly done in a second step. Skilled experts from ABB have analyzed
the parameters and marked those as basic parametes which are used for configuration of the grid
protection etc.. All other parameters belong together with the Basic parameter to the group of
Advanced (or all) parameters. When you select Basic parameters, all other parameters are hid-
den until you select Advanced parameters again.
Select a protection function and examine the Basic and the Advanced parameter to see the con-
cept. Select either:
Basic parameters or
Advanced (All) parameters (Default)
The possibility to select either Basic or Advanced parameters is part of the authorization config-
uration and user rights and included in the Category manager. See chapter 3 section 3.2 "PCM
600 access".
Parameter filter
There are four different filters available:
Visible parameters
- Is the summary of all available parameters without the hidden parameters.
See figure 51 as example
Changed parameters
- A parameter is marked changed when the actual PCM 600 value is modi-
fied by a manual input. It is marked changed, when you leave the input
field.
- A parameter is also marked changed when the IED value is different to the
PC value. The PC values are shown in bold.
- By selecting this filter only parameters which have been changed will be list-
ed. This allows a fast and easy check where the differences between the IED
parameters and the PCM 600 parameters are or more general which values
have been modified.
Invalid parameters
- When a parameter value is outside the allowed limits this value is marked as
invalid by a special symbol.
- By selecting this filter only invlaid parameters will be listed. An example can
not be shown, because all input entries are checked against the limits.
Hidden parameters
- When the Basic parameter layer is selected, the Advanced parameters are not
listed. To view advanced parameters only, select the view Hidden parame-
ters.
76
Group option
Expands and collapses the parameter list
Browse option
There are two possibilities:
Display selected node and child nodes

Display only selected node
Each IED contains a large number of parameters organized in General settings and up to six set-
ting groups. The description and the values for all parameters is included in the ied.ICD file
which is a XML file following the IEC 61850 standard. Building the parameter list from this file
takes time. Therefore it is recommended to use the Display only selected node mode as stan-
dard.
Read, write parameter from/to IED

Once the PCM 600 is connected with the IED the parameters can be uploaded or downloaded.
It is possible:
to load the whole set of parameters

to load a group of parameter or
to load only one selected parameter
When you write parameters to the IED you can choose as option:
all parameters or
only changed parameters
For both cases it can be selected to read back the values and compare them to the values send.
During up- and download a progress window is shown.
77
en05000579.vsd
Figure 52: PST: Write/download parameters to IED 670
en05000589.vsd
Figure 53: PST: Read/upload parameters from IED 670
78
4.1 Configuration parameters and settings

All variables listed and shown in the parameter list can be sorted into two groups:
configuration parameter or
setting parameter
Configuration parameter
A configuration parameter specifies an operation mode of an application function or of the IED.
These are basic configurations which are normally configured only once and then settled. The
IED configures itself at start up according to the given configuration parameter values.
This implies that an IED has to restart and do a re-configuration when such a value is changed.
This has to be considered when such a parameter is changed and downloaded to a running IED.
The IED will stop and do a restart with the new configuration parameter.
Setting parameter
A setting parameter (short form only setting) is a parameter which can be changed in the IED
at runtime.
Setting group
Nearly all settings used by the IED for the protection application functions are organized in a
group of settings. Up to six setting groups can be configured with different values. The IED 670
supports the selection of a setting group at runtime. The new setting group is taken on the fly
and will then be in use from the next cycle..
Copy, paste of a Setting group Nx

Because it is most likely that only some parameters in the available setting groups will be dif-
ferent it is useful to set up the first group with all parameters and copy these base settings to all
possible setting groups. So only these settings specific for that group need to be modified.
Copy and Paste of a setting group is only possible in the Parameter list.
select the top line of the setting group which will be the base group
copy the complete setting group with a right mouse click and select Copy
select the setting group which shall be overwritten with the settings of the base
group
paste the complete copied setting group with a right mouse click and select Paste
Remark
The active setting group can not be used for the copy function, neither as source nor as destina-
tion.
Organization of the parameters for an IED 670

The organization of the parameters in a tree structure is visible in the plant structure by expand-
ing the setting tree.
79
en05000588.vsd
Figure 54: PST: Example of tree plant structure down to function group
All configuration parameters are included in the General settings group. But not all parameters
in this group are of type configuration parameter. Single settings which are not part of the setting
group are listed here. This is mainly given for the protection application functions.
All settings belonging to the setting group are included in the available setting groups.
80
Graphical display editor GDE Chapter 5
5 Graphical display editor GDE

The GDE is selected either from the menulist in the menubar or with the right mouse button. The
en05000583.vsd
Figure 55: GDE: tool menubar
Extension to the menubar:
IED
- Write Display configuration to IED
Graphical Display Editor
- Display Page
- Display Container
Extension to the toolbar (from left to right) not included in the menubar selections:
normal pointer (arrow)

panning pointer (hand)
show grid
snap to grid; when placing a symbol or a measurement or a text element.
zoom factor; 100% or 200%
direct line; to draw lines between connection points
rotate a symbol left
rotate a symbol right
print the display page
print preview
To use the GDE some additional points about the presentation and generating a diagram concept
of the GDE have to be explained first. These points are:
the different windows of the GDE, including display container and display pages,
symbol library and font library
the HMI display raster layouts
drawing lines
81
Page types
Symbol library Container Display window

window en05000595.vsd
Figure 56: GDE: Screen image with active GDE tool
When you start the GDE you will get a screen similar to the screen in figure 56. The Object prop-
erties window will not be shown from the beginning. It will be used when text needs to be filled
in.
82
GDE windows
When you start the GDE the first time for a bay only the symbol library window will appear.
The display window exists but is not defined.
The first action therefore is to create a page type Single_Line or Measurement.
Display window
The display window contains a different container per page type and may be needed in the IED.
The visible area in the LHMI display is represented by a white drawing area. A container repre-
sents the visible display window of the LHMI.
Symbol library
The symbol library window contains some panes which include drawing symbols or elements
to create a single line diagram page and/or a measurement page. Click on the name bar of the
elements you are looking for to open the pane.
The library shows the symbols either in ANSI standard or in IEC standard. This is selected by
the drop down list box located on top of the display window.
When changing to the other library standard, GDE closes the library windows, changes the sym-
bols according to the selected new standard and redraws the single line diagram in the display
window.
Select the different panes and their symbols to become familiar with the available symbols.
Measurements (Measurands) are presented in one format. The format explains itself when you
select one and drop it in the drawing area.
Additional text strings are possible (Caption) . The maximum length is 12 characters.
The organization of the different display windows per IED LHMI is done in containers per page
type. A page type can contain several containers. For example, the number of different single
line diagrams of all bays which may be controlled by one IED. The selected container is shown
in the tab at the bottom of the display window. The selected page type is shown on the tab at the
top of the display window.
The standard for the symbols and the selection of the fonts for the text elements can be changed
using the two selector boxes on top of the page window. .
83
en05000596.vsd
Figure 57: GDE: Page type selection window
HMI display raster layout

When selecting a page type, two types are available:
Single_Line
Measurements
The total size of the drawing area represents the visible part of the LHMI display without head-
line and foot-line.
The visible display for a single line diagram is organized in a raster of 8 x 10 (columns x rows).
Each symbol included by the drag and drop method must be dropped in a raster box. The icon
snap to grid must be enabled to place a symbol. The description text for an apparatus object
can be placed in all four directions around the symbol. The description is part of the apparatus
object. See next section for details.
The visible display for a measurement page is organized in a raster of 37 x 23 (columns x rows).
One raster box is the placeholder for one character. A measurement must be placed in the posi-
tion of the raster. The name and the unit of a measurement can be changed. The description is
part of the measurement object. See next section for details.
Drawing lines
When the apparatus symbols are placed the lines can be drawn:
place the connection symbols by drag and drop in a raster box.

a junction point, included in the line element or only a junction point have to be
placed where necessary
enable direct line drawing by clicking the Direct Line icon in the toolbar
to draw a line center the mouse pointer on the center of a connection point; visible
in two circles at the endpoints of a line
click to start and move the mouse pointer to the destination connection point;
click again to drop the line
draw all line elements necessary
to finish the line drawing click the right mouse button
84
Line draw icon
start point end point

en05000598.vsd
Figure 58: GDE: Drawing a line
5.1 Engineering of a bay configuration

A page with a single line diagram as well as a page with measurements contains active living
objects which need to be updated by the IED when their values change (event driven) or period-
ically (measurements). Once the symbols are placed they need to be linked to their correspond-
ing process objects in the IED. The information is taken from the application function block
which operates this project object.
The object is used when a function block is selected in the application configuration. The corre-
sponding setting are done in the parameter setting tool and the link to the presentation in the HMI
is done by the graphical display editor.
Three tools work with that object:
CAP 531 to program the application function block for apparatus and/or mea-
surements
PST to adapt the settings and/or configuration parameter of the application func-
tion block
GDE to establish the link for updating the selected data attribute in the HMI of
the application function block
The following application function blocks are used to deliver the needed information:
for an apparatus
- SwitchController (SCSWI)
for the measurements
- all configured function blocks with measurements e.g. ServiceValues
(CVMMXU)
85
To choose the right object select the apparatus symbol and do a right mouse click. A list of en-
gineered application function blocks of type SCSWI pops up. Choose the SCSWI that belongs
to the selected apparatus.
To choose the right object select the measurement symbol and do a right mouse click. A list of
the engineered application function blocks of type ServiceValues (CVMMXU) with their avail-
able measurements pop up. Choose the measurement which belongs to the selected one.
The ordering number in the selection window corresponds to the number given in the PST set-
tings tree and to the application function block in CAP 531.
Only those apparatus and measurements are shown which are configured in the application con-
figuration program.
en05000600.vsd
Figure 59: GDE: Establish a dynamic object link
86
en05000611.vsd
Figure 60: GDE: Object properties windows for text insertion
Add and change text elements

To adopt or to add text elements it is necessary to open the object properties window.
Apparatus object
- select the apparatus object
- add the text of the apparatus in the object properties field
- choose the position for the text (north, south, east, west or center)
Measurement
- select the measurement object
- change the text element for measurement type in the object properties field
- change the unit caption
87
en05000599.vsd
Figure 61: GDE: Example pictures for single line diagram and measurements
Figure 61 shows two example pages.
The single line diagram also includes measurements. When you select a measurement in a single
line page GDE switches the raster to the grid for text elements.
The measurements are taken from the ServiceValues (CVMMXU1) and in this example partly
sorted to another view for process monitoring.
Do not forget to save your engineered pages.
88
HMI engineering Chapter 5
6 HMI engineering
The Human Machine Interface (HMI) is part of the IED. It displays various information about
the controlled and monitored process status and about the IED itself. The information which
should be displayed is either fixed or given by the engineered application functions. But there is
still engineering work needed to adapt the signals and or the description texts to the project
needs.
The IED 670 products can be delivered either with:
a small HMI (SHMI)

a large HMI (LHMI)
The LHMI is used to allow apparatus control directly from the IED by selecting and switching
the apparatus from a displayed single line diagram of the bay configuration. How to build the
single line diagram using the GDE tool is described in chapter 5 section 5.1 "Engineering of a
bay configuration".
Elements and signals used by the HMI which need project specific engineering work are:
the 15 LEDs; done in PST and SMT

- marshalling of the process signals selected to indicate their status on a LED
[SMT]
- type of flash mode, color etc. [PST]
the LCD operation mode [PST]
the display method of events [PST]
adaptation of text elements [PST]:
- analog input signals from the transformer modules (TRM)
- binary input signals from the BIM
- binary output signals from the BOM
- mA input signals from the MIM
- binary input and output signals from the IOM
adaptation of text elements [CAP 531]:

- binary process events linked to disturbance report function blocks
- analog process events linked to disturbance report function blocks
- pulse counter input signals
The text elements are used to display a message in the HMI display for the operator's use. Use
your project wording.
89
HMI engineering Chapter 5
Text/setting input in PST

Text input in CAP 531
en05000621.vsd
Figure 62: HMI: Where to engineer HMI elements
Figure 62 shows the tree structure for General Settings and those tree elements which are listed
above to be used for HMI engineering. It has to be taken into consideration that only the text
elements used to identify the object have to be entered in CAP 531. The other configuration pa-
rameters are entered in PST. The different configuration parameters and settings per object are
explained in the TRM.
90
IED 670 signal engineering per
protocol
Chapter 6 IED 670 signal

engineering per
protocol
About this chapter

This chapter describes the engineering procedure used to configure the signals which will be
communicated between the IED and station level IEDs or direct to the NCC. As well as between
the bay level IEDs, described as horizontal communication. The engineering procedure differs
depending on the protocol used.
The signal engineering is mainly done by selecting function blocks prepared to do the protocol
specific information presentation in command and monitoring direction. This is valid for the
SPA, LON and IEC 608705103 protocols. A new and very different type of signal communi-
cation is defined for the IEC 61850 protocol.
91
Introduction Chapter 6
protocol
1 Introduction
Looking to the complete chain for an information flow in monitoring or command direction the
signal interface between the application function program for the application functions and the
communication handler has to be specific for the different protocols. These protocol interfaces
have to be programed in the application function part specific for each protocol.
Communication handler
actor / sensor interface
I/O Function blocks
Protocol interface
Primary process
HSI / NNC-GW
Application
I/O interface
Station level
Functions
Disturbance
Recording
IED670
en06000021.vsd
Figure 63: IED 670: Protocol interface as part of the information chain
As shown in the figure above the protocol interface is part of the overall application function
program within the IED 670. Special function blocks are available to support the information
presentation and addressing model, specific to the protocol used.
The following sections describe the engineering process for each supported protocol in the IED
670 products mainly done in the CAP531 tool and assisted by some additions in the PST.
Double commands for apparatus control

The IED 670 product has a revised and new concept for the handling of commands used in ap-
paratus control. Until now the preparation, check for preconditions, correct selection and allow-
ance etc. was done using standard application function control logic. ABB has analyzed the
sequence etc. and developed a specific module located in the base software. This has the advan-
tage of being faster, secure and requiring no engineering work to adapt it to station needs.
More details can be found in the Technical Reference Manual (TRM).
Hidden protocol interface parts

The IED 670 products have an updated design based on the demands and advantages of the new
IEC 61850 standard. The Logical node is a container to deal with signal information of a func-
tion in IEC 61850 specification. The content of information per Logical node is predefined and
92
Introduction Chapter 6
protocol
fixed in the IED 670. There is no engineering work or configuration possibility given for Logical
nodes. To minimize the complexity in engineering the Logical node part of a function block is
not visible in any form.
More details will be given in the protocols where this is valid.
1.1 Additional procedures for signal engineering

The engineering process for the complete IED 670 product is described in chapter 5 "IED 670
Engineering process". The tasks to do signal engineering for vertical and horizontal communi-
cation can be seen as additional parts of the different activities already needed for the IED 670
itself.
CAP 531
- program the additional signal interface function blocks per protocol. This is
mainly described in the following sections per protocol.
- download the application function program, now extended with the tasks for
the protocol interface to the IED 670 via CAP 531
PST
- select and configure the hardware interface of the used protocol
- set the used interface addresses according to protocol and project definitions
- configure the selected signal interface function blocks to the signal type and
project demands, when applicable and foreseen
SMT
- the SMT tool has some additional tasks used especially for the IEC 61850
protocol.
- when GOOSE messages are used you have to configure the links between the
received GOOSE message blocks and the programed GOOSE signal inter-
face FBs (GooseBinRev; IntlReceive).
- download the IED 670 specific ied.CID file via SMT tool to the IED. This
file is available/generated after receiving the updated station.SCD file from
a station configurator (SC) tool, e.g. the CCT tool.
93
IEC 61850 protocol Chapter 6
protocol
2 IEC 61850 protocol

References and preconditions:
To be able to do the engineering of the IEC 61850 protocol interface for the IED 670 , the fol-
lowing additional manuals or knowledge of their contents is required.
Knowledge of the IEC 61850 protocol as described in the IEC 61850 standard
part 7
Knowledge of the IEC 61850 engineering process as described in the IEC 61850
standard part 6
Technical Reference Manual (TRM)
TRM, presents the function blocks which are defined as Logical Nodes (LN)
IEC 61850 data objects for IED 670
Communication Configuration Tool (CCT) user's guide
The communication principle and the need for data sets and communication control blocks as
described in IEC 618507 should be known.
The main part of the signal engineering is done in a Station Configurator tool (SC) as described
in IEC 618506. The PCM 600 tool set for IED 670 products is defined in the IEC 61850 stan-
dard and described in this manual as an IED Configurator tool. PCM 600 is also able to do the
station configuration part in cooperation with the CCT. This is described in the Station engineer-
ing guide for IEC 61850.
2.1 Sequence for signal engineering of IEC 61850 protocol

The IEC 61850 standard defines the complete part needed for information communication in a
substation. This can be split into the following parts:
the definition of data objects and their common data classes with their data at-
tributes
the definition of Logical nodes (LN) as the communication interface for a substa-
tion function (e.g. a protection function)
the definition of a protocol based on Ethernet and TCP/IP
the definition of the engineering process for a substation control system including
the signal engineering between all IEDs identified in the station
For more details please refer to the IEC 61850 standards. In the following description it is as-
sumed that the PCM 600 together with the CCT is used as system configurator tool in the defi-
nition of IEC 618506.
A short form of the complete sequence can be described as shown in the following figure.
94
protocol
CCT (2)
create project
station.SCD import station.SCD file station.SCD
file configure Data sets file
configure Report CBs
configure GOOSE CBs
export station.SCD file
PCM600 (1) PCM600 (3)
do IED 670 engineering import station.SCD file

import all IEDs of the station link GOOSE input data
export station.SCD file download ied.CID files
IED670 IED670 IED670 IED670
en06000022.vsd
Figure 64: IEC 61850: Signal engineering procedure flow
The procedure can be split into three main parts
1. the IED engineering as described in chapter 5 "IED 670 Engineering process"

IED engineering as described and additional station configuration
repeat IED engineering for all IED 670s used in the station project
each compilation with CAP 531 will generate an ied.ICD file
include all other IEDs used in the station via the Generic IEC 61850 IED.
export all ied.ICD files collected to one station.SCD file
2. the signal engineering for the station by using the CCT tool
create a project in CCT, when not already exist for the station
import the station.SCD file created by PCM 600
check the Datasets generated by the IED configurator tools for each IED.
Generate additional Datasets when requested
generate Datasets for GOOSE communication based on the engineered hor-
izontal function.
create and configure Report Control Blocks (RCB) for each data set used for
vertical communication.
link each Dataset for vertical communication to a RCB
link the IED clients to the RCBs
95
protocol
create and configure GOOSE Control Blocks (GoCB) for each Dataset con-
figured for GOOSE messages
link the GOOSE Datasets to a GoCB
link the IEDs to the GoCB which shall receive the GoCB
update data flow (CCT specific function)
export the updated station.SCD file for further use by the IEDs
3. the additional GOOSE engineering (when applicable) and download of the result
as ied.CID file to the IED 670.
import the updated station.SCD file to the project in PCM 600
do signal marshalling in all IED 670s which are involved to receive GOOSE
messages with the SMT tool
download the updated ied.CID file to the IED 670 with the SMT tool
This is a short form of the complete procedure for IEC 61850. Most of the tasks are done in a
system configurator tool like PCM 600 together with CCT.
The additional tasks for signal engineering for IEC 61850 in an IED 670 can be seen in the fol-
lowing figure, which is an extension to the figure 3 in chapter 3 section 1 "PCM 600 Tool set".
The additional tasks are shown in bold and with rectangular lines.
96
Figure 65:
PCM 600 Tool Set
Function Compile
Block
Library
IEC 61850 protocol
Structure AF GOOSE
Generate Parameter
builder GOOSE-FB marshalling LHMI
ICD file Settings
- Plant additions Generate Display Editor
- Communication Functionblocks
CID file
PCM 600 CAP 531 PST SMT GDE
CID file
Project Data Base
AFC Settings
IO Cnfg HMI
SCD file SCD file
IEC 61850: Additional tasks for signal engineering

CCT
(Communication REX 670
Configuration)
en06000023.vsd
97
protocol
Chapter 6
protocol
2.2 IEC 61850 interface in IED 670

The following figure tries to give a principle view of the IEC 61850 Logical node concept in the
IED 670.
FB GOOSE
GOOSE
Receive Receive
GOOSE
FBs Send
FB
with AF part
monitoring
IN / OUT interface AF part

only LN
part
Single commands
IEC 61850 protocol

FBs FB
with AF part
monitoring
and LN
commands part
Event
handler
CSWI XCSWI; XCBR
FB FB
AF part AF part Event
queue
LN LN
part part
Command handler Double

Apparatus control
Release command commands
en06000020.vsd
Figure 66: IEC 61850: Communication interface principle
IEC 61850 has as a concept for the identification of all signals for communication which belong
to a function by a logical node as a placeholder. The Logical node (LN) has the name of the func-
tion. All information in command and monitoring direction which belongs to this function is or-
ganized below the LN. So a function which is identified in the application function part as a
function block has a corresponding LN. This solution concept is ABB IED 670 specific and is
not requested by the IEC 61850 standard.
The design in IED 670 takes care of this idea. The signals generated by the function are follow
the standard and need no special engineering therefore. This requires another way of thinking,
because the signals are not shown in the application function presentation of the function block!
98
protocol
Whenever a function block is selected from the library and placed, the CAP 531 will automati-
cally generate the corresponding Logical node with its data . In the above figure this is shown
by two blocks per function block. The upper one is the visible block in application function and
the lower one is the LN which belongs to this function.
Double commands are checked against the state of the IED 670 and the rules before the com-
mand are given to the function block dealing with commands, which is the SCSWI function
block.
CAP 531 generates the complete set of LNs per IED as an ied.ICD file when the compilation of
the application function was without errors and CAP 531 is closed. This ICD file contains all
LN, their data type definitions and the two standard Logical nodes LLN0 and LPHD. See chapter
5 section 2 "Configuration and Programming tool CAP 531" for more details.
2.3 Export/import of SCD files in PCM 600

The IEC 61850 standard defines four file types in the sequence of engineering. These files have
a different definition which is explained in IEC 618506 clause 7. Three of this file type are used
in the engineering process for an IED 670.
ied.ICD = IED Capability Description

- describes the capability of the IED in Logical nodes and their data. No infor-
mation about communication configuration etc. is included.
- an IED 670 is already extended by default data sets. They are defined by ex-
perts from ABB for standard functionality. Additional data sets etc. have to
be done with the CCT tool.
station.SCD = Station Configuration Description
- describes the complete configuration of all IEDs in a station and the full en-
gineering of process signals and communication structure is included. This
includes all needed data sets and all control blocks. This describes the end
version.
ied.CID = Configured IED Description
- The CID file structure and contents is not defined by the standard. It is sup-
plier specific. The SMT tool is extended with the capability to read the SCD
file and build the ied.CID file from it.
Export a station.SCD file

Assuming that more than one IED 670 is used in a station project it is useful to export all ied.ICD
files as one file which is then the station.SCD file. The procedure is a follows:
select the station in the plant structure. See figure: 67.

select Export System SCL... with the right mouse button
a standard Windows menu pops up to select a location. Choose a destination
where the file should be stored and give it a name
PCM 600 starts the process and will generate a new selection window. See figure
68.
select SCL Object Naming variant for your project. IEC 618506 defines in
clause 8.4 two types of object designation.
99
protocol
- A technical key: Predefined by PCM 600 and can be checked in the object
properties for each level. Beginning with the station itself = AA1 down to
the IED 670. The technical key is based on the IEC 61346 standard and the
definitions written for substations by a technical committee.
- A user oriented textual designation: which is the name provided in the plant
structure and visible in the object properties under Caption.
check that the selection box Export Private Section is blank (not set). IEC
618506 defines in clause 8.2.6 the possibility to include a private structure of
presentation in the SCL file for later reuse etc. This is actually not supported and
not needed.
start export. A progress window will show the export procedure which will take
some time depending on the number of IEDs.
Station
en06000025.vsd
Figure 67: IEC 61850: Export station.SCD step 1
en06000026.vsd
Figure 68: IEC 61850: Export station.SCD step 2
100
protocol
Import a station.SCD file

When an exported station.SCD file is handled by the CCT tool or another SC tool it is necessary
to import the extended station.SCD file back and update the IED 670 with the additional config-
uration.
The procedure is as follows:
select the station in the plant structure.

select Import System SCL... with the right mouse button
a standard Windows menu pops up to select the file to be imported. Browse to the
destination the file is stored and start the reading.
a selection menu pops up which queries how the file should be handled during
import. See figure 69.
1. the standard is the basic window as shown in the right screen-shot in figure
69.
2. Update PCM Structure from SCL expects that the file is the one which was
exported but now extended by configuration actions done in CCT. This is the
normal case and set by default.
3. Append SCL to PCM Structure will append the information for each IED
to the existing ICD part in the IED. This is useful, when the station configu-
ration part is done on a basis ied.ICD file with no specific engineering or the
ICD file does not exist for the IED 670 until now.
4. Advanced Options expand the window as shown in the left screen-shot. of
figure 69 "IEC 61850: Import station.SCD file".
5. Don't import ... protects the existing IEDs in case the station.SCD file does
not match the original configuration in PCM 600.
6. Replace unknown ... can be used when it is known, that the file includes
additional IEDs which are needed. The IED of type Generic IEC 61850
IED is used to integrate these kinds of IEDs in the plant structure etc.
7. Allow overwriting ... should only be done when it is clear what happens
and justified with the complete project.
start Import when you have completed your definitions. A progress window
will show the import procedure which will take some time depending on the num-
ber of IEDs.
101
protocol
en06000027.vsd
Figure 69: IEC 61850: Import station.SCD file
2.4 GOOSE signal engineering and download of ied.CID file

The SMT tool is used to do this tasks. For the general operation of the SMT see chapter 5 section
3 "Signal matrix tool SMT".
GOOSE signal marshalling

The 61850 protocol supports a method to exchange data between two or more IEDs directly.
This method is described in IEC 6185072 clause 15. The concept is based on sending a data
set broadcast over the Ethernet. Whoever needs the information detects the telegram by its
source address and will read the telegram and deals with it. The telegrams are broadcast sent and
not acknowledged by the receiver. This implies that the confirmation is part of the application
dialog between the sender and the receiver(s). So a message sent by an IED requests an answer
from the receiver. It is of course also possible that the receiver do not need to respond. In all
cases it is a matter of the application to decide.
102
protocol
IEC 61850 Subnetwork
Receive
Receive
Receive
Receive
Receive
Receive
Send
Send
Send
Data-set Data-set Data-set
LN LN LN
LN LN
LN
LN LN LN
LN
LN LN LN LN LN
IED 1 IED 2 IED 3

en05000830.vsd
Figure 70: IEC 61850: Horizontal communication principle
The above figure shows an example with three IEDs where each communicates with all the oth-
ers. So IED 1 sends a GOOSE message and receives a response in form of a GOOSE message
from IED 2 and IED 3. The response includes the requested information and the information to
check the correct receive message and acknowledgement.
To send a GOOSE message is defined by the configured data set with the defined trigger option
and the GOOSE control block (GoCB). There is no specific function block requested to define
the signals which are sent. This engineering process is done in the station configurator tool
(CCT) by defining the GOOSE data set. So it is useful to prepare lists with the signals (data at-
tributes) which belong to the GOOSE message dataset.
In the opposite direction the standard only defines the IED as a receiver of the GOOSE message.
How the GOOSE input signals are handled is a matter for the IED. The station.SCD file gener-
ated by the CCT (or any other station configurator tool) contains these GOOSE data sets as In-
put data. They have to be linked to a receive function block. This is done by the IED 670 with
two special function blocks for GOOSE receive signals.
function block = GooseBinRev with the capacity to handle 16 binary signals

function block = IntlReceive with the capability to handle 16 signals used for
interlocking information
The GOOSE receive function block has to be engineered before the link can be made using the
SMT tool.
103
protocol
GOOSE signal marshalling with SMT

When the SMT detects GOOSE input signal blocks and engineered GOOSE function blocks it
is able to present the two partners in an additional matrix window (GOOSE RECEIVE). The
GOOSE input blocks are presented in x-direction and the GOOSE receive function blocks in
y-direction. The signal routing is done in the way described earlier in the IED 670 engineering
description. Each X identifies a link.
en06000024.vsd
Figure 71: IEC 61850: GOOSE signal marshalling by SMT
Save your links in the SMT.
Download the complete configuration for signal engineering into the IED 670 by using the SMT
download function. The IED 670 will read the file and establish the configuration based on the
ied.CID file at start up.
104
SPA protocol Chapter 6
protocol
3 SPA protocol
To be able to do the engineering of the SPA protocol interface using the application function,
the following manuals or a knowledge of their contents is required.

SPA-Bus communication protocol V2.5
SPA signal lists for IED 670 (SAT)
The communication principles and the methods used to access data from the IED 670s based on
the SPA protocol should be known.
The engineering of the SPA interface function blocks is part of the application function pro-
gramming and done in CAP 531. Open CAP 531 to proceed.
3.1 SPA interface in IED 670

The following figure shows the possible data types and their access methods for the SPA proto-
col.
The SPA protocol in the IED 670 products supports the following communication access meth-
ods:
Monitoring direction
- Event driven information via the protocol specific event function block
(function block = Event; see TRM). Only binary signals are transmitted as
events.
- Information transmitted on an explicit read request from the SPA master.
These values are read from the application function data part when a read re-
quest for that signal is sent by the SPA master. Typical signals are measured
values and pulse counter values.
Command direction
- Single commands via a special single command function block (SingleCmd;
see TRM)
- Double commands for apparatus control are sent to the command handler as
part of the base system. The extension to the corresponding function block
(SCSWI, SXCBR, SXCWI) is hidden and needs no engineering in the appli-
cation function part. The correct routing of the command to the function
block is given by the predefined SPA address for each function block. (see
TRM and SAT).
105
protocol
Control Single Single commands

logic Cmnd
Prot.-FB
Counter PCGGIO
logic Prot.-FB
IN / OUT interface PLC part

Get values
SMMI
direct
Read request SPA
MMXU
Event
Range-XP
SPA protocol
Protocol
Boolean FB Event
signals (SI) for handler
some
event
SMBI
types Event
direct
queue
SXCBR
SCSWI
SXSWI
Cmnd
Control

Command Substitute
Apparatus control
handling handling
en05000821.vsd
Figure 72: SPA-Bus: Communication interface principle
Event function block

The Event function block is used for the SPA protocol or the LON protocol. For the SPA proto-
col the connected signals are converted to the demands of the SPA protocol. The Event function
block detects the type of connected signal by the structure of the link. For SPA it supports the
following types:
Simple binary signals. Normally coming from application function logic directly.
Binary signals represented by value and event time. The binary information
linked to a SMBI-function block represents this type of signal.
Double point signals represented by value and time. For each possible position
value an event is generated. The apparatus control function blocks (SCSWI, SX-
CBR, SXCWI) generates this kind of signal.
Binary status information about the limits of a measurement supported by the
Range-XP function block.
106
protocol
The event detection is initiated has to be configured using the PST parameter block per Event
function block. For more details see TRM.
Remark
The function block Event is able to detect the type of signal by its description. The following
rules have to be regarded:
Double indications are only possible on the inputs, Input1 to Input8. This is given
due to the addressing capability of SPA events for DI blocks.
All other signals can be connected through Input1 to Input16 in any order and in
any combination with DI signals.
SPA
en05000817.vsd
Figure 73: SPA-Bus: Example for event signal configuration
Single commands function block

A single command in SPA is represented by its SPA address and its value. The value is handled
as a static value or as a pulse value with a fixed pulse time of 200 ms. For more details see TRM.
Double commands
The apparatus control is a combination of two function blocks.
107
protocol
for a circuit breaker: the function block SCSWI and SXCBR

for any kind of isolator: the function block SCSWI and SXCWI
The SCSWI function block is needed to organize all items around the switch command like in-
terlocking, operation capability of the apparatus and so on. The SXCBR or SXSWI function
block is used to switch the apparatus ON or OFF. The IED 670 allows substitution of the position
of an apparatus. This feature is handled by the function blocks SXCBR or SXSWI.
The commands dealing with the apparatus are handled by the Command handler included in the
base software.
SPA or
LON
en05000818.vsd
Figure 74: SPA-Bus: Example for single commands
Read request SPA

Following the principle of the SPA-Bus protocol all other kinds of values are transmitted only
on request from the SPA master unit. The SPA master is responsible for organizing the data poll-
ing and the polling for events to fulfill the performance demands. The communication handler
in the IED 670 for the SPA protocol has a fast direct access to all values represented by a SPA
address. So it is therefore not necessary to program a special interface block for this kind of pro-
cess information.
The use of the information is possible when the signal is listed in the used SPA addresses for the
IED 670. See SAT tables for more details.
Configuration of protocol related function blocks in PST

After successful compilation of the application function program in CAP 531, the project data-
base is updated with the additional information and the new protocol function blocks are visible
in the setting structure.
You have to configure the Event function blocks according to the correct event detection method
for each signal.
108
protocol
Documentation of used SPA addresses and signal types

Each piece of process information used to communicate with a station level IED has a pre-
defined SPA address and due to signal type a fixed definition of value presentation in a SPA tele-
gram. All possible process signals are listed with their SPA address in the SAT document. This
is provided for all signal types and for all instances of a function block type.
Once you have finalized the application function programming and all signals have been defined
you may produce a list of used signals by listing all used function blocks and the connected sig-
nal types. The corresponding SPA address is found in the SAT document.
109
LON protocol Chapter 6
protocol
4 LON protocol
To be able to do the engineering of the LON protocol interface within the application function,
the following manuals or a knowledge of their contents is required.

LON Application Guideline (LAG) V1.2
SPA signal list for IED 670
The communication principles and the methods used to access data from the IED 670s based on
the LON protocol should be known.
The engineering of the LON interface function blocks is part of the application function pro-
gramming and done in CAP 531. Open CAP 531 to proceed.
4.1 LON interface in IED 670

The following figure shows the possible data types and how to access them for the LON proto-
col.
The LON protocol in the IED 670 product supports the following communication access meth-
ods:
- Event driven information via the protocol specific event function block
(function block = Event; see TRM). Information presentation is based on the
IEC 608705101 definitions.
- via Event function block: Simple binary signals
- via Event function block: Single indication as event including time and qual-
ity information
- via Event function block: Double indication as event including time and
quality information
- via Event function block: Measured values from MMXU function block in-
cluding limit supervision. The values are transmitted periodically
Command direction
- Single commands via a special single command function block (SingleCmd;
see TRM). Information presentation in SPA protocol formats.
- Double commands for apparatus control are send to the command handler as
part of the base system. The extension to the corresponding function block
(SCSWI, SXCBR, SXCWI) is hidden and needs no engineering in the appli-
cation function part. The correct routing of the command to the function
block is given by the predefined SPA address for each function block (see
TRM and SAT). Information presentation in SPA protocol formats.
Horizontal communication
110
protocol
- Horizontal communication between IED 670 units connected to the same

LON Bus is used to exchange information about station wide interlocking or
other station wide control or protection functions handled by more than one
IED.
Multi- LON SNVTs

Cmnd
e.g.
Prot.-FB
station wide
interlocking
logic Multi- LON SNVTs
Transm.
Prot.-FB
Control Single Single commands

logic Cmnd
Prot.-FB
Event
MMXU
values +
ranges Protocol
LON protocol
FB
SMMI
for
direct
various Event
event handler
Boolean types
signals (SI)
SMBI Event
direct queue
SXCBR
SCSWI
SXSWI
Cmnd
Control

Command Substitute
Apparatus control
handling handling
en05000822.vsd
Figure 75: LON-BUs: Communication interface principle
LON Protocol
The LON protocol as it is used by ABB for substation communication applications is specified
in the LON Application Guideline (LAG). The LAG specifies three basic communication parts.
111
protocol
1. communication on the basis of Echelon's defined Standard Network Variables

types (SNVTs). This method is used for the horizontal data exchange between
IEDs.
2. transmission of SPA messages in the same presentation then provided by the
original SPA telegrams. Echelon allows the transmission of messages in trans-
parent mode with support of the full basic communication features of the LON
protocol. This method is used for commands of all kinds. So the contents of these
telegrams is the same as that provided for the SPA protocol.
3. transmission of process information based on the IEC 608705101 telegrams
for events. Also using the transparent mode of Echelon's LON protocol. This
method is used for all information in the monitoring direction from IED 670 to
station level devices.
LON
en05000824.vsd
LON: Example for event signal configuration
Event function block

The Event function block is used for the SPA protocol or the LON protocol. For the LON pro-
tocol the connected signals are converted to the demands of the LON protocol using IEC
608705101 based telegrams. The Event function block detects the type of connected signal by
the structure of the link.
Simple binary signals. Transmitted as single indication with time stamp. The
time is taken by the event function block, when it detects the change.
112
protocol
Single indication as event including time and quality information. Transmitted as

single indication with time stamp. The time is given by the source of the tele-
gram. When this signal comes from an SMBI interface function block, it is the
time included by the BIM input board.
Double indication as event including time and quality information. Transmitted
as double indication with time stamp. These events come from the apparatus con-
trol function blocks. The time is in normal cases the time included by the BIM
input board, because the position is connected to the apparatus function block via
the SMBI interface function block.
Measured values from MMXU function blocks including limit supervision. The
values are transmitted periodically as measured values in real format with time
stamp. In the LON presentation this telegram type is extended with limit super-
vision quality bits (from LL to HH). The structure of a measured value includes
this information in the value. The additional signal x_Range must therefore not
also be connected to the event block.
Single commands function block

A single command in the LON protocol is transmitted as a SPA command represented by its
SPA address and its SPA value. The value is handled as a static value or as a pulse value with a
fixed pulse time of 200 ms. For more details see TRM.
SPA or
LON
en05000818.vsd
Figure 76: LON-Bus: Example for single commands
Double commands
The apparatus control is a combination of two function blocks.
for a circuit breaker: the function block SCSWI and SXCBR

for any kind of isolator: the function block SCSWI and SXCWI
113
protocol
The SCSWI function block is needed to organize all items around the switch command like in-
terlocking, operation capability of the apparatus and so on. The SXCBR or SXSWI function
block is used to switch the apparatus ON or OFF. The IED 670 allows substitution of apparatus
poistion. This feature is handled by the function blocks SXCBR or SXSWI.
The commands dealing with the apparatus are handled by the Command handler included in the
base software.
Configuration of protocol related function blocks in PST

After successful compilation of the application function program in CAP 531, the project data-
base is updated with the additional information and the new protocol function blocks are visible
in the setting structure.
You have to configure the Event function blocks to the correct event detection method for each
signal. For the measured values the update period must be defined.
Documentation of used LON and SPA addresses and signal types

Each piece of process information used to communicate with a station level IED has a pre-
defined LON object address or SPA address (in command direction). The LON object address
is given by the predefined base address of the used event block plus the input number. The tele-
gram type which belongs to this input is given by the connected signal type. For more details see
TRM.
Once you have finalized the application function programming and all signals have been defined
you may produce a list of used signals by listing all used function blocks and the connected sig-
nal types. The corresponding LON object addresses and telegram types in the monitoring direc-
tion and the SPA addresses for commands have to be taken from the SAT document
4.2 Engineering LON horizontal communication

The LON protocol supports a method used to exchange data between two or more IED 670 de-
vices directly. This is done by the standard procedure for communication in the LON protocol,
using the distribution of Standard Network Variables (SNVTs).
The base concept of LON protocol is to send telegrams with the source address as identification
and everyone who needs this information detects the telegram by its source address and will read
the telegram and deal with it. Several methods of confirmation are defined in the LON protocol
standard. For horizontal communication between IED 670 the UNACK (unacknowledged)
method is used. This implies that the confirmation is part of the application dialog. So a message
sent by an IED requests an answer from the receiver(s).
114
protocol
LON Bus
LON Interface LON Interface LON Interface
1 2 3 2 1 3 3 1 2
MT CM CM MT CM CM MT CM CM
Interlocking logic Interlocking logic Interlocking logic
IED670 Bay1 IED670 Bay1 IED670 Bay1
en05000820.vsd
Figure 77: LON: Horizontal communication principle
The above figure shows an example with three IEDs where each communicates with all the oth-
ers. So IED 1 sends a message (MT) and receives a response (CM) from IED 2 and IED 3. The
response includes the requested information and the information used to check the correct re-
ceive message and acknowledgement. The IED 670 has special function blocks to receive and
send LON telegrams horizontal.
The SNVT concept requests the engineering of sender and receiver for each telegram. This is
needed to configure the LON Bus Neuron chips with address tables of telegrams which shall be
received by this node. The Lon Network tool (LNT 505) is used to do LON configuration which
includes the address engineering.
Engineering horizontal communication in the application function

Two function blocks are used to handle horizontal communication:
to send a data block: function block = MultiTransmit

to receive a data block: function block = MultiCommand
The input and output signals of the two blocks represent the contents of the SNV type = 83 of
Echelon's SNVT list. This is a 16 bit status block, where all sixteen inputs are user defined.
The logic to handle the station wide function, for example, interlocking, deals with the input and
output signals.
115
protocol
LON Bus
e.g. Interlocking logic

en05000819.vsd
Figure 78: LON: Example of interlocking with horizontal communication
The needed function blocks for LON communication can be engineered completely before the
LON address links have to be done.
It is necessary to fill a list with all senders and all receivers of a telegram before the LNT 505
can be used to do the links.
Engineering of SNVT telegrams with LNT 505

It is expected that the use of the LNT 505 is known.
The LNT 505 must be updated with the configuration capability of the IED 670 for LON. This
is done by including the corresponding SLDT file for IED 670 devices in the LNT 505. This file
is included on the engineering CD for IED 670. The file includes the type and number of instanc-
es per function block used for LON communication.
Creating of connections for SNVTs is described in chapter 3.5 of the LNT 505 as NV connec-
tions. For each known transmitter (as Output selection) function block the receiver (as Input
selection) has to be linked to. Take your list of used senders and receivers to complete the links.
Once all links are engineered the address lists have to be downloaded to the LON Neuron inter-
face chip. The general configuration of the LON network has to be engineered first, to be able
to do this. See LNT 505 for more details.
116
protocol
5 IEC 608705103 protocol

To be able to do the engineering of the IEC 608705103 protocol (herein now 103 protocol)
interface within the application function part, the following additional manuals or a knowledge
of their contents is required..

The IEC standard paper for the IEC 608705103 protocol in its latest version
The communication principle and the methods used to access data from the IED 670s based on
the 103 protocol should be known.
The engineering of the 103 interface function blocks is part of the application function program-
ming and done in CAP 531. Open CAP 531 therefore.
5.1 IEC 608705103 interface in IED 670

The following figure shows the possible data types and their access methods for the 103 proto-
col.
The 103 protocol in the IED 670 product is aware of the following communication access meth-
ods:
- According to the protocol standard all signals are transmitted as events. They
are transmitted when they occur and the 103 master polls the IED for
changed data.
- changes of binary signals are detected by the I103 interface function block.
- measured values are transmitted periodically when requested by he IED 670.
The period has to be configured in the parameter block of the I103 function
block in the PST tool.
Command direction
- IEC 608705103 is only aware of some special commands which are direct
coded like all the other. The corresponding function blocks handle these
commands.
117
protocol
I103IEDCmd
103 commands
I103Cmd
I103IED

I103UserCMD
I103Superv
IEC 60870-5-103 protocol

Event
IED670 handler
I103EF
Protection
I103UserDef Event
Logic queue
I103FltDis
I103FltStd
I103MeasUsr
I103AR
I103MEAS
DR transfer
handler
IED670 Disturbance handler
DR file recording and storage
en05000823.vsd
Figure 79: IEC 608705103: Communication interface principle
103 compatible function blocks

The IEC 608705103 protocol is a protocol which allows the connection of protection relays
from different suppliers to a master. All signals are fully defined with their function type and
their information number and therefore compatible with the different relays and suppliers. The
IED 670 supports this with a set of function blocks for the different groups of information num-
bers. For more details see TRM. It is the responsibility of the user to connect the correct signal
to each predefined input, identified by its information number.
Additional user defined signals, measurements and commands

The IED 670 allows the user to add additional signals, measurements and commands. This is
made possible by the I103 function blocks with the coding USER in their name. For these ad-
ditional function blocks the configuration of signals has also to be done in the PST for each used
user function block.
118
protocol
103
103
en05000816.vsd
Figure 80: IEC 608705103: Example for event signal configuration and 103 commands
Documentation of used 103 addresses and signal types

The IEC 608705103 defines in clause 8 a compatibility list for the 103 interface configuration.
For each configured IED 670 protection relay a compatibility list is requested. When additional
I103 user function blocks are used they have to be included as well.
Remark
Disturbance records are transmitted via IEC 608705103 to the 103master as specified in the
standard. A parallel transmission of the disturbance record is possible by the PCM 600 as de-
scribed in chapter 7 section 1 "Disturbance record handler DRH".
119
protocol
120
Chapter 7 IED monitoring

process
About this chapter

This chapter describes the tools available to monitor the IED 670s with their process information
apart of the online runtime communication to the NCC or HSI. These tool components are part
of the PCM 600 tool.
121
Disturbance record handler DRH Chapter 7
1 Disturbance record handler DRH

The DRH is integrated in the PCM 600 tool set and used to support the handling of disturbance
records (DR) by
reading DRs out of the IEDs

managing them in the PCMDataBase
starting a disturbance recording analysis tool with the selected DR as input
exporting and importing DRs to/from other user or archive
creating reports out of the DR information to give an overview about the distur-
bance
monitoring the IEDs for new DRs under assistance of a task scheduler
A precondition is that the communication with the IEDs is established and running.
The DRH installed in PCM 600 is designed to read DRs from all kinds of relays which use the
IEC 61850 protocol and support reading DR files in Comtrade format and use file transfer as it
is specified in the IEC 61850 standard.
This section will describe the operation of the DRH with less reference to the tool itself. This
allows us to focus on the conceptual operation in a general way and to have a reference when
the DRH tool is described in the next sections.
DRH is able to read the DRs from all ABB IED 670 products and from all other IED relays using
IEC 61850. For these IEDs a Generic IEC 61850 IED (here called Gen-IED) has to be config-
ured in the project. See chapter 4 section 3.4 "Generic IEC 61850 IED" and chapter 3 section 5.1
"Set up communication link per Generic IEC 61850 IED" how to integrate a Gen-IED in the
plant structure and how to set up the communication.
The abbreviation DR is used to identify a disturbance record created by the protection IED. A
DR consists of three files according to the IEEE COMTRADE standard (see below).
Remark for IEC 608705103 protocol used

When the IED communicates via the IEC 608705103 protocol to a master the disturbance
records are transmitted to the 103master as specified in the standard. A parallel transmission of
the disturbance record is possible by the PCM 600 as described in this chapter. The functionality
as described herein is valid also when IEC 608705103 is used.
Operation concept
The IED 670 product family supports a set of functions for disturbance recording. See the TRM
for more details about the disturbance record functions. From the viewpoint of a user who needs
as much information as possible about a disturbance it would be useful to have the other infor-
mation about the disturbance available beside the pure recording of the AC-signals over time.
The IED 670 generates the disturbance record files according to the standard IEEE C37.111
(COMTRADE) in the current revision. This standard defines four different files, where two of
them are mandatory and two optional. The IED 670 delivers the two mandatory and the optional
header files:
xxxxxxxx.HDR = Header file (optional; supported by IED 670)
122
xxxxxxxx.CFG = Configuration file (mandatory)

xxxxxxxx.DAT = Data file (mandatory)
xxxxxxxx.INF = Information file (optional; not supported by IED 670)
The header file in the IED 670 contains additional information about the disturbance which pro-
vides a more complete picture. This additional information is generated and prepared by the dis-
turbance report functions of IED 670. The information included in the header file is:
general information about the disturbance, the disturbance recording configura-

tion and the IED
the configured analog channels and their actual values at pre-fault time (start re-
cording) and at fault time (trigger time)
the configured binary channels and their state during the disturbance
actual information from the DR fault locator function when available/configured
list of configured binary signals with their event information when available/con-
figured (DR Event list function)
This useful information in the header file is IED 670 specific and can only be read and presented
by the DRH tool.
A Gen-IED may do something similar but because it is supplier specific it can not be handled
by the DRH. In this case the information about the DR is limited to the contents of the
xxxxxxxx.CFG file. This has to be considered when it comes to the presentation of the DRs in
the DR windows.
By starting the report function of the DRH, the complete information of the header file is made
visible in a report.
123
Remote
User
Network
PCM600
DR with
Report
Recording DRH
PCMDataBase
IED
Recording
IEC 61850 Network
Generic Generic
IED670 IED670 IED670 IED670
IED IED
en05000622.vsd
Figure 81: DRH: Operation principles
The above figure shows the operating principle of the DRH tool. The task can be split into three
main parts:
communication with the IED

- getting a list of all actual available DRs in the IED
- uploading the DRs selected
- deleting DRs in the IED which may not needed or have been uploaded
- forcing a manual trigger (IED 670 relays only)
- clearing/acknowledging the LEDs in the IED (IED 670 relays only)
managing the uploaded DRs
- creating a report (useful for IED 670 relays only)
- start a DR analysis tool with the selected DR
- export the DRs to another user or to an external archive
- import a DR when needed for any purpose
124
- delete DRs out of the PCMDataBase

monitor IEDs for new DRs at runtime
- use the task scheduler to start the monitoring periodically
- upload the DRs when available
- generate a report and save it as PDF file
- send the report to a user defined in an E-mail set up
1.1 Use of Comtrade header file in IED 670 relays

The header file is defined in the IEEE C37.111 COMTRADE standard as: The header file is an
optional ASCII text file created by the originator of the COMTRADE data. The creator of the
header file can include any information in any order desired.
ABB has taken this opportunity to include additional information which helps to identify the dis-
turbance by selecting it from the list. In addition it includes summary information which is sup-
plied in case of a disturbance by the IED 670. In a report the additional information which is
contained in the header file can be included. The report may be used parallel to the information
presented by the DR analysis tool or to get a quick overview to make decisions on the further
usage of the DR.
The general information as part in the header file is used to show the DRs in the lists of the IED
recordings window and with some modifications also in the DR recording window. Which of
these information elements may be used in the lists and in which order can be configured accord-
ing to your needs.
For the Gen-IEDs the information elements contained in the xxxxxx.cfg file is used for presen-
tation. These elements are listed in the tables below and marked in italic.
The available elements in the general part in the header file are as shown in the table:
Table 1: Possible elements of type general for the IED Recording list presentation
Possible elements of type general for the IED Recording list presentation
Name Information/Value Description
DRP Id 1 Instance number of the disturbance recorder within the IED.
Actually only one is available
Trig Date Time date and time Date and time of the DR trigger event
Also for Gen-IED
Trig Ch channel name Name of the channel which forces the trigger. Is the first
channel in case more then one channel have triggered
Test Trig YES/NO Trigger occurred while IED in test mode
Seq No 0...255 Sequence number of DR per day. Seq No is reset to 0 at
midnight
Sync NONR/BIN/GPS/SN Method of time synchronization within the IED.
TP/GPS+BIN/GPS+
SNTP/SPA/LON/103
DR Installed Not Is always Installed.
installed/Installed
125
Possible elements of type general for the IED Recording list presentation
ER Installed Not When installed an event list is available in the header file
installed/Installed and will be listed in the report
FL Installed Not When installed the Fault locator information is available in
installed/Installed the header file and will be listed in the report
Line Length 0...10000 km Line length in km
3ph IED NOT 3phase Type of primary installation
IED/3phase IED
Freq 50Hz/60Hz Line frequency
Also for Gen-IED
MAX Rec Time Set <= 6300 ms Maximum total recording time of the active DR
PreTrig Time <=300 ms Pre-fault time of recording
PostFault Time <= 5000 ms Post-fault time of recording
Recording Time <= 6000 ms Maximum Post-fault time of recording
Pretrig Set <= 300 ms Configured Pre-fault time of recording
Postfault Set <= 6000 ms Configured Post-fault time of recording
Sampling f 1.0 kHz / 1.2 kHz Sampling frequency at 50/60 Hz
Also for Gen-IED
IED Type REx 670 10 Type of the IED
SW Ver 1.nnn Software version of the IED
Stn Name station name Station name
Also for Gen-IED
Obj Name object name Object name
IED Name IED name IED name
Stn No station number station number
Obj No object number object number
IED No IED number IED number
Also for Gen-IED
Act GRP 1 ... 6 Active setting group at trigger time
The contents of the column Information/Value contains at runtime the actual values config-
ured in the IED. The above listed contents is for information only and tries to give an impression
about the value.
Once the file is uploaded to the PCM 600 DRH, the information presented in the DR recording
list is reorganized and some information from the xxxxxxxx.cfg file is included.
126
Table 2: Possible elements for the PCM Recording list

Possible elements for the PCM Recording list
DRP Id 1 Instance number of the disturbance recorder within the IED.
Actually only one is available
Trig Date Time date and time Date and time of the DR trigger event
Also for Gen-IED
Trig Date date Date part of the element Trig Date Time
Also for Gen-IED
Trig Time time Time part of the element Trig Date Time
Also for Gen-IED
Trig Ch channel name Name of the channel which forces the trigger. Is the first
channel in case more then one channel have triggered
Seq No 0...255 Sequence number of DR per day. Seq No is reset to 0 at
midnight
Sync NONR/BIN/GPS/SN Method of time synchronization within the IED.
TP/GPS+BIN/GPS+
SNTP/SPA/LON/10
3
Line Length 0...10000 km Line length in km
Freq 50Hz/60Hz Line frequency
Also for Gen-IED
MAX Rec Time Set <= 6300 ms Maximum total recording time of the active DR
PreTig Time <=300 ms Pre-fault time of recording
PostFault Time <= 5000 ms Post-fault time of recording
Recording Time <= 6000 ms Maximum Post-fault time of recording
Sampling f 1.0 kHz / 1.2 kHz Sampling frequency at 50/60 Hz
Also for Gen-IED
Stn Name station name Station name
AC 1...n Number of recorded channels. Taken from xxxxxxxx.cfg file
Also for Gen-IED
127
Possible elements for the PCM Recording list

Fault Location nnn km Distance to fault in km
Fault Type Not Fault loop used for calculation
valid/L1N/L2N/L3
N/L12/L2L3/L3
L1
Fault Direction Not valid/For- Direction to fault position
ward/Forward
beyond range/Not
applicale
REV YEAR 2001 Year of the COMTRADE revision used. Taken from
xxxxxxxx.cfg file
Also for Gen-IED
File name of the DR file File name generated by PCM 600 to identify the file set.
set
The contents of the column Information/Value contains at runtime the actual values config-
ured in the IED. The above listed contents is for information only and tries to give an impression
about the value.
1.2 Operating the DRH

The DRH is selected either from the menulist in the menubar or with the right mouse button. The
IED must be selected as an object.
en05000623.vsd
Figure 82: DRH: Tool menubar
Extensions to the menubar
IED
- Recordings > Refresh list
- Available Recordings in IED > Get Record Information
Report
- Create Report
There are no tool icons included in the toolbar. But all DRH specific actions can be selected with
the right mouse button. The choice list varies between an empty list or a list of DRs.
128
en05000624.vsd
Figure 83: DRH: task selection windows
It is expected in this chapter that the communication to the IED is established and running.
DR recording windows
When the DRH is started the tool pops up with two windows split horizontally. The upper win-
dow (DRR window) is used to handle the DR recordings stored in the PCMDataBase. The lower
window (IEDR window) is used to handle the DR recordings available in the IED. DRs available
in the PCMDataBase for the selected IED will be shown in the DRR window at start up. In figure
84 the IEDR window is empty.
129
en05000625.vsd
Figure 84: DRH: Screen image with DR windows
Each row in a window describes a DR. The columns shown are the selection of information el-
ements which should be displayed . The identification of each column is explained by its name
in the content bar at the top of the window.
Methods of adjusting column width, sequence etc. are standard of MS windows. The other pos-
sibility is to open the configuration window Settings by selecting via right mouse button . A se-
lection window of the DRR or IEDR window will pop up. The content of the columns is listed
and explained in the previous chapter.
You may select the elements you need and by shifting them up and down (select the line and
move them while keeping the mouse pressed) you can organize the information presented ac-
cording your own preferences. To adjust the width of each column is possible in the window Set-
tings, but it seems easier to do it by visual control using standard MS windows methods
130
You may select a single DR line or select a range of DRs or some individual DRs by the Win-
dows standard methods (Shift or Ctrl button pressed) or with the right mouse button.
1.2.1 IED Recording

Communication between the DRH and the IED occurs only when requested by the DRH.
Get Recordings Information

The first step is to be informed by the IED about the available DRs. Click Get Recordings Infor-
mation to start the dialog with the IED. A list of all currently available DRs in the IED is dis-
played.
A DR is deleted in the IED only if requested by the PCM 600
When you have deleted files in the IED or new DRs may be available you should clear the list
and read the actual available DRs in the IED once again.
Upload and delete DRs

Select the files you want to see in PCM 600 and start Read. The files will be uploaded and stored
in the PCMDataBase. They will not automatically be visible in the DRR window. DRH checks
that all selected DRs are uploaded and will inform in case of a failure. See DR Recording below
for more information.
Once all files are uploaded you may delete them in the IED. Select the DRs you want to delete
or select all. Click the corresponding actions with the right mouse button to do so.
Commands to the IED

Two commands are needed/possible:
Execute Manual Trigger

- execute the manual trigger command to get a DR forced manually. You have
to read and upload the file to see the results as described above.
Clear LEDs
1.2.2 DR Recording
The following described functions are possible with DRs stored in the PCMDataBase.
Refresh List
As described above uploaded DRs from the IED are stored in the PCMDataBase but not auto-
matically listed in the DRR window. To import them to the DRR window it is necessary to do
Refresh List. The DRH will read all files stored under the directory of the selected IED and pre-
pares the presentation for the DRR window. The DRR window is cleared and the new actual list
is displayed.
131
en05000587.vsd
Figure 85: DRH: Generating list progress window
While doing the update a window shows the progress.
Start a DR analysis tool

Select the DR you want to analyze and open the DR analysis program. The path to the DR pro-
gram in the input field Target is requested the first time. In the input field Arguments the DRH
has already filled in the path to the selected DR The selected tool must be designed to read the
name and path of the DR file as an argument.
en05000619.vsd
Figure 86: DRH: Start a DR analysis tool window
Export, Import, Delete Recordings

To export DRs you have to select the DRs and start the export action. Select the location where
you want to store the DRs and store them. DRH will store all three files in the selected directory.
In the opposite way you may import an archived DR set for any purpose. The DRH selects the
xxxxxxxx.cfg file as master to identify a DR set. DRH stores all three files into the PCMData-
Base in the directory of the selected IED.
DR sets can be deleted from the PCMDataBase.
It is the responsibility of the user to be aware of the tasks involved when moving or deleting DR
file sets.
132
1.3 Reports
A report can be made per DR at any time, because the data in the DR is not manipulated by the
DRH. ABB has made a general layout of the report log, which can be partly adapted to your re-
quirements. This is possible by using the Template editor. The template editor allows you to
choose which parts of a complete report are to be included or not.
Remark
The report task takes the elements for presentation as they are filled in by the DRH when it reads
a DR file loaded from the IED 670 or from a Gen-IED. Information not available from a
Gen-IED is left out and so will not be presented in the report. This has to be considered when a
report for a Gen-IED is generated.
To generate a report click Create Record .... A selection window of available templates will pop
up.
en05000597.vsd
Figure 87: DRH: Select a report template window
Once you have selected a template the DRH starts to generate the report for the selected DR.
When it has finished the generation, a presentation tool will start and enables viewing of the re-
port on screen.
133
en05000585.vsd
Figure 88: DRH: Report Framework window
The Disturbance Report Framework is based on Windows standard tool components. The tool
allows:
printing of the report directly on a printer

export of the report in two formats
preview of the report in page layout on screen
the selection of another report template
The report can be exported as a dr.PDF file or in a picture file format dr.PNG with a file per page
to a directory of your choice.
Content of a report
The parts which can be reported and the presentation layout are predetermined.
The following parts are available for a report:
General data
134
- includes the up to 30 information items from the general part in the

xxxxxxxx.hdr file.
Fault location
- includes the four values calculated by the fault locator in the IED
Analog channels
- lists the recorded channels with their values at start of recording and at trig-
ger time.
Digital channels
- lists the recorded digital channels with their state (0/1) at trigger time
Total recording of analog channels
- is a time line diagram of all recorded analog channels over the recorded total
time. Can be used as a preview.
Total recording of digital channels
- is a time line diagram of all recorded digital channels over the recorded time.
The change of state is visible in form of a thin (=0) and bold (=1) line
Zooming window around the trigger time
- is a time line diagram of the trigger digital channels over a time window
around the trigger time to see more details when the trigger occurred.
Vector diagram of AC signals at trigger time
- shows the recorded analog channels in a vector diagram
Event list as generated in the IED during disturbance report
- lists all entries made in the disturbance report event list in the IED with their
state and absolute event time and date.
1.3.1 Configuration capability of a report
Set up E-mail configuration

When the PCM 600 is used to monitor the IEDs for new DRs by the task scheduler it is possible
to send an E-mail containing the report about the new DR to a user. This allows the user to check
the report and he can decide what to do. See chapter 7 section 1.4 "Task scheduler to monitor
new disturbance reports".
To do so, it is necessary to configure the addresses etc. for the E-mail body which is used to send
the report.
There is one E-mail body per IED requested.
The DRH will append the report to the E-mail body. This is activated by the task manager.
To configure the E-mail body select in the DRR window Settings. SelectCreate Report>E-mail.
135
en05000553.vsd
Figure 89: DRH: Configuration of the E-mail set up window
The E-mail configuration window has six input fields, which must/can be filled per IED:
SMTP Server
- SMTP = Simple Mail Transfer Protocol is a MS standard service. Fill in the
call for your installed SMTP service.
Sender
- E-mail address of the PCM 600 sending the E-mails. It is recommended to
create an E-mail address which allows identification of the sender in the list
of received E-mails when some PCM 600 units are sending E-mails.
To
- E-mail address of the receiver of the E-mail. PCM 600 checks the E-mail ad-
dress for formal correctness.
CC
- CC field is optional
136
Subject
- It is recommended that a unique identification of the IED is filled in, for a
single IED structure. This facilitates detection of the IED in the list of
E-mails
Text
- Optional free text
Apply the contents.
1.4 Task scheduler to monitor new disturbance reports

The task scheduler tool (TST) is selectable from the menubar only. No IED must be selected as
object in the beginning.
en05000564.vsd
Figure 90: TST: tool menubar
Task Manager
- Start Task Manager
- Stop Task Manager
- Filter (not supported)
Tasks/Jobs
- Add Task
- Add System Job
- Add Object Job
- Activate Task
- Interrupt Task
- Enable Task
- Disable Task
All functions extended in the menubar are also available in the toolbar via their icon or with the
right mouse button.
The Scheduler tool also named Task manager is a support tool which allows the starting of jobs
at predefined time points. The activities which should be executed at that execution time are de-
scribed in one or several job(s). A job is a sequence of predefined DRH tool actions
137
There is a hierarchical order of control.
1. Task Manager
The task manager enables or disables all tasks. Only when the task manager
is active can any task be executed.
2. Task
A task is configured in the way the task should be executed over the time.
There are some modes of time scheduling selectable. Following the config-
uration the task will be executed only once or periodically. When a job fails
during execution or does not end normally the whole task is stopped and
must be restarted manually.
3. Job
A task can manage one or several jobs. When a task is started according to a
time plan it will execute each job sequentially. The next job is started when
the predecessor has finished. When all configured jobs are executed once, the
task will terminate and wait for the next scheduled time.
User
Task PCM600
Task
Manager Manager
Network
Task Task DRH
Project 1 Project A
Job 1 Job A Network
Job 2 Job B
PCM
Job C DataBase REX REX
670 REX 670
670
en05000560.vsd
Figure 91: TST: Task scheduler operation principles
Definitions and rules to operate the task manager
the task scheduler is a tool which is independent of a PCM 600 project.

it can handle jobs for several projects.
138
the configuration of a task and of jobs must be done per project.

a job is limited to, can handle only one IED 670 or Gen-IED.
the IED is/must be selected in the plant structure before a job can be added to the
task.
there are two variants of a job available
- read new DRs from the IED and store them in the PCMDataBase or
- read new DRs from the IED and store them in the PCMDataBase AND in-
form the user by sending an E-mail which includes a report of the DR
the task manager keeps active when the PCM 600 is shut down and not running.
- the activated job will execute the DRH tool in a sequence as it would be done
by a user operating the DRH manually
the task manager has to be restarted after the PC was stopped/shut down
It is the responsibility of the user to check and manage the volume of stored DRs in the PCM-
DataBase. As described in the previous chapter about DRH, DRs will only be deleted on request
and selection by the user.
1.4.1 Set up tasks and jobs within a task

A sequence to create a list of jobs to monitor IEDs would be as follow:
start a project or it might be already started

start Scheduler tool
select the Task Manager icon and chooseAdd Task
- to add a task is always possible
perform the task configuration in the configuration window according to your re-
quirements
- see below how to configure a task scheduler
repeat the next three steps for all IEDs which should be included in the task
- select the IED you want to monitor in the plant structure
- select Task icon and choose Add Object Job
- do job configuration. Select job variant and tool for the job
choose Enable Task
139
en05000578.vsd
Figure 92: TST: Task manager menu tree example window
The above figure shows a task with two jobs.
1. waiting for the next start at 13:00 o'clock

2. running the task and the first job is active
The task manager, the tasks and their jobs are shown in a tree structure.
Configuration of a task scheduler

Seven modes for task execution are possible. For each mode you have to select the interval
(which is given by some of the modes as predefined), the start condition and the end condition.
Possible modes are:
None
- this mode allows you to start the sequence manually. The task is activated by
choosing Activate Task. It will execute all jobs once.
Fixed Interval
- this mode allows you to configure an interval to your needs. This is done by
the interval parameters days and time period (hh:mm:ss)
Once
- there is no interval but the start time decide when the task will be started
Once an Hour
- the interval is fix to one hour
Once a Day
- the interval is fix to 24 hours
Once a Week
- the interval is fix to seven days
Once a Month
- the interval is fix to one month
140
With the start condition and end condition you decide when it should start and how long or how
often the task should be executed in the interval.
en05000577.vsd
Figure 93: TST: Task configuration window
Remark
The start time must always be in the future. If you select a start time which has already passed,
the task will be started immediately after you enable the task and the start time for each interval
will be changed to the actual time it was started now the first time.
141
Configuration of a job
en05000563.vsd
Figure 94: TST: Job configuration window
Two input fields are provided:
Tool
- only the DRH tool can be/must be selected
Job
- select either Read new recordings or
- select Read Recordings and Send Report (per E-mail) to the user
To set up the E-mail sending see chapter 7 section 1.3.1 "Configuration capability of a report".
Activate Task or Interrupt Task

You can activate a task at any time by selecting Activate Task. This is needed for a task config-
ured to task scheduler mode None. But it can also be done for all other tasks. It has to be con-
sidered that the start time for the interval is changed to the time of the activation.
You may want to stop the running task. This is possible by selecting Interrupt Task. The running
job will be finalized but the other pending jobs will not be executed. The task is on hold and must
be started again by setting Enable Task. Check the start time and adjust the time to a start point
in the future.
142
IED 670 signal monitoring ISM Chapter 7
2 IED 670 signal monitoring ISM

The IED 670 signal monitoring tool enables reading of actual values of the binary physical
IO-signals from the BIM and BOM boards and the calculated analog values from all configured
function blocks which deliver analog values.
The values are transmitted to the PCM 600 independent of the ongoing runtime communication
to station level units. The values are transmitted at the request of the PCM 600. It is possible to
update the values manually or to start a periodical update controlled by the PCM 600.
All available values are presented in a list form to get the overall overview on one side and in
logical groups for the binary signals per physical IO board or the analog values per function
block on the other side.
A precondition to run the ISM tool is the existing and operational communication link between
the IED 670 and the PCM 600.
2.1 ISM operation

The ISM is selected either from the menulist in the menubar or with the right mouse button. The
IED 670 must be selected as object.
en05000797.vsd
Figure 95: ISM: Tool menubar
Extensions to the menubar
IED
- Online Monitoring
- Manual Refresh
Signal Monitoring
- Filter ON/OFF
Extension to the toolbar are (from left to right)
Print preview
Print
Online Monitoring
Manual Refresh
Filter ON/OFF
143
Once the ISM tool is started it starts the reading of all possible values from the IED 670. The
IED 670 informs about the available signals. During that task an information window informs
about the running signal collection.
The first reading is finished when a tool window as shown in figure 96 is presented.
en05000798.vsd
Figure 96: ISM: general tool window
The actual process information is shown in two possibilities:
in a List View
in an overview window per group. With the following possible groups:
- binary input signals organized per binary input module BIM
- binary output signals organized per binary output module BOM
- binary input/output signals organized per binary IO module IOM
- analog input signals organized per milliampere input module MIM
- calculated analog signals organized per function block with readable values
144
en05000799.vsd
en05000800.vsd
en05000801.vsd
Figure 97: ISM: Example of signal presentation windows
145
List View
The List View shows all available signals with an index from 1 to n. The different columns are
self-explaining.
Filter ON/OFF
This feature is only possible when the List View window is selected.
en05000802.vsd
Figure 98: ISM: List View with Filter selected
The operation of this function might be well known from Microsoft Excel. With Filter = ON an
additional row is blended in on top. For those columns where a selection is useful a choice list
can be listed and by selecting one of the possible choices only rows which belong to the selected
filter are listed.
Value update
When you start the tool the values are read once and then presented. You have two choices to
update the values.
once on your demand = Manual Refresh

periodical = Online Monitoring. In this mode the PCM 600 reads the values pe-
riodical from the IED 670 and updates the values.
146
Chapter 8 IED 670 diagnostic

capabilities
About this chapter

This chapter describes the tool components available to gain access to diagnostic information
from the IED 670 or to get diagnostic information about the Ethernet link between the IED and
the PCM 600 tool. These tool components are part of the PCM 600 tool.
147
IED 670 event viewer IEV Chapter 8
1 IED 670 event viewer IEV

The IED 670 event viewer tool allows you to read the events from the IED 670 and list them in
a table. Events in the definition for the IEV tool are:
S = IED 670 internal system events produced when an error or warning is detect-
ed in the operation of the IED 670 hardware or software.
P = process events stored in the IED 670 internal disturbance report event list
(DR event list).
The system events are transmitted to the PCM 600 only, so the IEV tool is the only way of listing
internal IED 670 messages. The process events from the DR event list are part of a disturbance
report, when configured. They are also presented in the HMI of the IED 670.
The event view list is only updated on demand. The received events are stored in an internal
PCM 600 datastore. They are available for history analysis when the period Unlimited is select-
ed.
1.1 IEV operation

The IEV is selected either from the menulist in the Menubar or with the right mouse button. The
IED 670 must be selected as object.
en05000803.vsd
Figure 99: IEV: Tool menubar
Event Viewer
- Read newest events from IED 670
- Show newest events on top / on bottom
- Filter On/off
- Select period type
- Go to first period
- Go to previous period
- Go to next period
- Go to last period
- Go to specific period
- Clear IED 670 event buffer(s)
148
- Delete events in datastore
Extension to the toolbar are (from left to right)
Print preview
Print
Read newest events from IED 670
Show newest events on top / on bottom
Filter On/off
Go to first period
Go to previous period
Go to next period
Go to last period
Go to specific period
Clear IED 670 event buffer(s)
Delete events in datastore
Once the IEV is started it starts reading the events from the IED 670. During that task an infor-
mation window informs about the running event collection.
The first reading is finished when the information window is closed. IEV starts with a period
type of Day and lists the events in chronological order with the latest event on top. The real pe-
riod which is selected is shown to the right of the period type selection box.
en05000804.vsd
Figure 100: IEV: Event list presentation
The internal events shown in the figure were forced for demonstration purposes here. The dif-
ferent columns in the event list are self-explanatory.
149
Filter ON/OFF
The operation of this function might be known from Microsoft Excel. With Filter = ON an ad-
ditional row is blended in on top. For all columns a choice list can be listed and by selecting one
of the possible choices only rows which belong to the selected file are listed.
en05000805.vsd
Figure 101: IEV: Event list with Filter list selection
The internal events shown in the figure were forced for demonstration purposes here.
Select Period type

Depending on available events it might be useful to concentrate the view for a shorter period
only. This is done by selecting a period type in the period type select box.
It has to be taken into consideration, that the IEV tool lists and has available the actual events
read from the IED 670 and the events of the IED 670 stored in the internal event datastore.
Available period types are:
1h
2h
6h
12h
Day
Week
Month
Unlimited
Unlimited means all available events from both sources (IED 670 and event datastore) in one
list.
150
When a period type is selected it is possible to scroll through the periods by using the icons avail-
able in the toolbar. The selected period is shown at the top of the list.
Go to specific period
Especially when a long list of events might be available in the IED 670 and in PCM 600 it might
be useful to go directly to a specific date and time period. A selection window is shown when
this feature is selected. This is only possible when a limited period type is selected.
en05000806.vsd
Figure 102: IEV: Go to specific period selection window
Clear IED 670 event buffer(s)

This function is actually not supported by the IED 670.
Delete events in datastore

This function deletes ALL events from the selected IED 670 stored in the PCM 600 internal
datastore. A confirmation window is shown and the task must be confirmed.
en05000807.vsd
Figure 103: IEV: Delete PCM 600 event datastore
151
OPC online diagnostic OOD Chapter 8
2 OPC online diagnostic OOD

The OPC online diagnostic tool monitors the communication between the PCM 600 and the con-
nected IEDs.
PCM 600 uses an OPC interface for each protocol interface it has to support. This is also pro-
vided for the Ethernet interface with IEC 61850 protocol which is used between PCM 600 and
the IED 670 devices.
The OPC (OLE for Process Control) interface is an industrial standard to allow client applica-
tions (here PCM 600) access to plant data (here IED 670 devices) in a consistent manner. The
OPC interface makes the application software independent from the used protocol because it
uses Microsoft OLE (Object Linking and Embedding) standard.
The IEC 61850 OPC server is used within the ABB product family for three different products:
the MicroSCADA pro product for the HSI

the COM 610 product for the NCC gateway
the PCM 600 product for the engineering of IED 670 products and other ABB
IED product families
HSI NCC GW PCM 600

(MicoSCADA) (COM 610)
OPC OPC OPC
Server Server Server
IEC 61850 NETWORK
IED IED IED IED IED

IED IED IED
670 670 670 670 670
en06000096.vsd
Figure 104: PCM 600: Use of OPC server
The HSI and the NCC GW are client IEDs in the term of IEC 61850 and using the OPC server
with all its functionality. The PCM 600 communicates with the IEDs for most of the transfers in
the ABB SPA protocol. The OPC server is only used in case of disturbance readings.
The OOD tool is available also for the PCM 600. The only relevant information taken from the
dialog between the OPC diagnostic tool and the IED is the successful connection between the
two partners.
The following section describes only these elements which are relevant for PCM 600.
152
2.1 OOD operation

To select the OOD tool it is necessary to open the Communication structure in the Project Ex-
plorer. The OOD tool can only be started in the communication view, because it is part of the
OPC interface. The OOD is selected either from the menulist in the menubar or with the right
mouse button.
There are no extensions to the menubar and toolbar provided by the OOP tool.
Position of the OOD tool in the network structure

The OOD tool can be started on different levels within the communication structure. It presents
different views and information in each level. The three levels are:
the OPC server itself

the IEC 61850 Network with all partners connected to it
a specific IED
To select one of the three views, select the element OPC server, network or IED and choose the
Online diagnostics.
en05000808.vsd
Figure 105: OOP: Select Online Diagnostic and start it
153
OPC server view
en06000093.vsd
Figure 106: OOP: OPC server view
Shows only information about the installed OPC server version etc. No actions etc. for PCM
600.
Tool connection => Follow selected
Allows to swap between the OPC server without new selection and start when more then one
OPC server is installed
154
IEC 61850 network view
en06000094.vsd
Figure 107: OOP: IEC 61850 network view
State => In use
It indicates that the network is connected and runs communication to the connected IEDs. Not
used for PCM 600.
Diagnostic counters
The OOD checks the link between the IEDs and the OPC server periodically. Each time it counts
the requests and the response. The number of requests and responses should be the same, when
no error like missing IED etc. is given. Definition of the relevant rows see below.
Allows to swap between the IEC 61850 networks without new selection and start when more
then one IEC 61850 network is installed
155
IED view
IP address
en06000095.vsd
Figure 108: OOP: IED view
State => In use
It indicates that the network is connected and runs communication to the connected IEDs. Not
used for PCM 600.
State => Diagnostic events enabled
Only relevant for the IEC 61850 client OPC server like HSI and NCC GW.
Status information
When a communication between the OPC server and the IED is possible, it is shown in this
sub-window. The IP address is taken from the IED configuration.
156
Diagnostic counters
The OOD checks the link between the IEDs and the OPC server periodically. Each time it counts
the requests and the response. The number of requests and responses should be the same, when
no error is given. Definition of the relevant rows see below.
Allows to swap between the IEDs without new selection and start when more then one IED is
installed
Diagnostic counters
Only those counters are listed which are used in the communication between PCM 600 and the
OPC server
Table 3: Diagnostic Counter description

Diagnostic counters Description see
figure:
Sent connection requests Request to connect the IED to the OPC server is sent to the IED 107, 108
Received connection Successful reply with connection from the IED received 107, 108
replies OK
Received connection The connection request was not answered or with failure 107
aborts
Sent requests A formal IEC 61850 sent request was transmitted to the IED 107, 108
Received replies OK The IED has answered with a successful response 107, 108
Received status requests Unsolicited status requests received from the IED. That means the 107, 108
IED has send a request to read status to the OPC server.
157
158
Glossary
Chapter 9 Glossary
About this chapter

This chapter contains a glossary with terms, acronyms and abbreviations used in ABB technical
documentation.
159
Glossary Chapter 9
Glossary
1 Glossary
AC Alternating current
A/D converter Analog to digital converter
ADBS Amplitude dead -band supervision
AIM Analog input module
ANSI American National Standards Institute
AR Autoreclosing
ArgNegRes Setting parameter/ZD/
ArgDir Setting parameter/ZD/
ASCT Auxiliary summation current transformer
ASD Adaptive signal detection
AWG American Wire Gauge standard
BBP Busbar protection
BFP Breaker failure protection
BIM Binary input module
BOM Binary output module
BR External bi-stable relay
BS British standard
BSR Binary signal transfer function, receiver blocks
BST Binary signal transfer function, transmit blocks
C37.94 IEEE/ANSI protocol used when sending binary signals between IEDs
CAN Controller Area Network. ISO standard (ISO 11898) for serial communi-
cation
CAP 531 Configuration and programming tool
CB Circuit breaker
CBM Combined backplane module
CCITT Consultative Committee for International Telegraph and Telephony. A
United Nations sponsored standards body within the International Tele-
communications Union.
CCM CAN carrier module
CEM Controller area network emulation module
CIM Communication interface module
CMPPS Combined mega pulses per second
CO cycle Close-open cycle
160
Glossary Chapter 9
Glossary
Co-directional Way of transmitting G.703 over a balanced line. Involves two twisted
pairs making it possible to transmit information in both directions
COMTRADE Standard format according to IEC 60255-24
Contra-directional Way of transmitting G.703 over a balanced line. Involves four twisted
pairs of with two are used for transmitting data in both directions, and
two pairs for transmitting clock signals
CPU Central processor unit
CR Carrier receive
CRC Cyclic redundancy check
CS Carrier send
CT Current transformer
CVT Capacitive voltage transformer
DAR Delayed auto-reclosing
DARPA Defense Advanced Research Projects Agency (The US developer of the
TCP/IP protocol etc.)
DBDL Dead bus dead line
DBLL Dead bus live line
DC Direct current
DFT Discrete Fourier transform
DIP-switch Small switch mounted on a printed circuit board
DLLB Dead line live bus
DR Disturbance recorder
DRH Disturbance report handler
DSP Digital signal processor
DTT Direct transfer trip scheme
EHV network Extra high voltage network
EIA Electronic Industries Association
EMC Electro magnetic compatibility
EMF Electro motive force
EMI Electro magnetic interference
EnFP End fault protection
ESD Electrostatic discharge
FOX 20 Modular 20 channel telecommunication system for speech, data and
protection signals
FOX 512/515 Access multiplexer
FOX 6Plus Compact, time-division multiplexer for the transmission of up to seven
duplex channels of digital data over optical fibers
FXM IEC 61850, Optical ethernet card
161
Glossary Chapter 9
Glossary
G.703 Electrical and functional description for digital lines used by local tele-
phone companies. Can be transported over balanced and unbalanced
lines
G.711 Standard for pulse code modulation of analog signals on digital lines
GCM Communication interface module with carrier of GPS receiver module
GI General interrogation command
GIS Gas insulated switchgear
GOOSE Generic object oriented substation event
GPS Global positioning system
GSM GPS time synchronization module
HDLC protocol High level data link control, protocol based on the HDLC standard
HFBR connector type Plastic fiber connector
HMI Human machine interface
HSAR High speed auto reclosing
HV High voltage
HVDC High voltage direct current
IDBS Integrating dead band supervision
IEC International Electrical Committee
IEC 60044-6 IEC Standard, Instrument transformers Part 6: Requirements for pro-
tective current transformers for transient performance
IEC 60870-5-103 Communication standard for protective equipment. A serial master/slave
protocol for point-to-point communication
IEC 61850 Substation Automation communication standard
IEEE Institute of Electrical and Electronics Engineers
IEEE 802.12 A network technology standard that provides 100 Mbits/s on twisted-pair
or optical fiber cable
IEEE P1386.1 PCI Mezzanine card (PMC) standard for local bus modules. References
the CMC (IEEE P1386, also known as Common mezzanine card) stan-
dard for the mechanics and the PCI specifications from the PCI SIG
(Special Interest Group) for the electrical EMF Electro Motive Force.
IED Intelligent electronic device
I-GIS Intelligent gas insulated switchgear
IOM Binary input/output module
Instance When several occurrences of the same function are available in the IED
they are referred to as instances of that function. One instance of a func-
tion is identical to another of the same kind but will have a different num-
ber in the IED user interfaces. The word instance is sometimes defined
as an item of information that is representative of a type. In the same
way an instance of a function in the IED is representative of a type of
function.
162
Glossary Chapter 9
Glossary
IP 1. Internet protocol. The network layer for the TCP/IP protocol suite
widely used on Ethernet networks. IP is a connectionless, best-effort
packet switching protocol. It provides packet routing, fragmentation and
re-assembly through the data link layer.
2. Ingression protection according to IEC standard
IP 20 Ingression protection, according to IEC standard, level 20
ITU International Telecommunications Union
LAN Local area network
LIB 520 High voltage software module
LCD Liquid crystal display
LDCM Line differential communication module
LDD Local detection device
LED Light emitting diode
LNT LON network tool
LON Local operating network
MCB Miniature circuit breaker
MCM Mezzanine carrier module
MIM Milli-ampere module
MPM Main processing module
MVB Multifunction vehicle bus. Standardized serial bus originally developed
for use in trains.
NCC National Control Centre
NUM Numerical module
OCO cycle Open-close-open cycle
OCP Overcurrent protection
OLTC On load tap changer
OV Over voltage
Overreach A term used to describe how the relay behaves during a fault condition.
For example a distance relay is over-reaching when the impedance pre-
sented to it is smaller than the apparent impedance to the fault applied
to the balance point, i.e. the set reach. The relay sees the fault but per-
haps it should not have seen it.
PCI Peripheral component interconnect, a local data bus
PCM Pulse code modulation
PCM 600 Protection and control IED manager
PISA Process interface for sensors & actuators
POTT Permissive overreach transfer trip
163
Glossary Chapter 9
Glossary
Process bus Bus or LAN used at the process level, that is, in near proximity to the
measured and/or controlled components
PSM Power supply module
PST Parameter setting tool
PT ratio Potential transformer or voltage transformer ratio
PUTT Permissive underreach transfer trip
RASC Synchrocheck relay, COMBIFLEX
RCA Relay characteristic angle
REVAL Evaluation software
RFPP Resistance for phase-to-phase faults
RFPE Resistance for phase-to-earth faults
RISC Reduced instruction set computer
RMS value Root mean square value
RS422 A balanced serial interface for the transmission of digital data in
point-to-point connections
RS485 Serial link according to EIA standard RS485
RS530 A generic connector specification that can be used to support RS422,
V.35 and X.21 and others.
RTC Real time clock
RTU Remote terminal unit
SA Substation Automation
SC Switch or push-button to close
SCS Station control system
SCT System configuration tool according to standard IEC 61850
SLM Serial communication module. Used for SPA/LON/IEC communication.
SMA connector Subminiature version A, A threaded connector with constant impedance.
SMS Station monitoring system
SNTP Simple network time protocol is used to synchronize computer clocks
on local area networks. This reduces the requirement to have accurate
hardware clocks in every embedded system in a network. Each embed-
ded node can instead synchronize with a remote clock, providing the
required accuracy.
SPA Strmberg protection acquisition, a serial master/slave protocol for
point-to-point communication
SRY Switch for CB ready condition
ST Switch or push-button to trip
Starpoint Neutral point of transformer of generator
SVC Static VAr compensation
TC Trip coil
164
Glossary Chapter 9
Glossary
TCS Trip circuit supervision

TCP Transmission control protocol. The most common transport layer proto-
col used on Ethernet and the Internet.
TCP/IP Transmission control protocol over Internet Protocol. The de facto stan-
dard Ethernet protocols incorporated into 4.2BSD Unix. TCP/IP was
developed by DARPA for internet working and encompasses both net-
work layer and transport layer protocols. While TCP and IP specify two
protocols at specific protocol layers, TCP/IP is often used to refer to the
entire US Department of Defense protocol suite based upon these,
including Telnet, FTP, UDP and RDP.
TEF Time delayed earth-fault protection function
TNC connector Threaded Neill Concelman, A threaded constant impedance version of a
BNC connector
TPZ, TPY, TPX, TPS Current transformer class according to IEC
Underreach A term used to describe how the relay behaves during a fault condition.
For example a distance relay is under-reaching when the impedance
presented to it is greater than the apparent impedance to the fault
applied to the balance point, i.e. the set reach. The relay does not see
the fault but perhaps it should have seen it. See also Overreach.
U/I-PISA Process interface components that deliver measured voltage and cur-
rent values
UTC Coordinated universal time. A coordinated time scale, maintained by the
Bureau International des Poids et Mesures (BIPM), which forms the
basis of a coordinated dissemination of standard frequencies and time
signals. UTC is derived from International Atomic Time (TAI) by the addi-
tion of a whole number of "leap seconds" to synchronize it with Universal
Time 1 (UT1), thus allowing for the eccentricity of the Earth's orbit, the
rotational axis tilt (23.5 degrees), but still showing the Earth's irregular
rotation, on which UT1 is based. The Coordinated Universal Time is
expressed using a 24-hour clock and uses the Gregorian calendar. It is
used for aeroplane and ship navigation, where it also sometimes known
by the military name, "Zulu time". "Zulu" in the phonetic alphabet stands
for "Z" which stands for longitude zero.
UV Undervoltage
V.36 CCITT interface for 4 wire data communication with a speed exceeding
48Kkbps.
WEI Weak end infeed logic
VT Voltage transformer
X.21 A digital signalling interface primarily used for telecom equipment
3IO Three times zero-sequence current. Often referred to as the residual or
the earth-fault current
3UO Three times the zero sequence voltage. Often referred to as the residual
voltage or the neutral point voltage
165
Glossary Chapter 9
Glossary
166
1MRK 511 179-UEN
ABB Automation Technology Products AB

Substation Automation
SE-721 59 Vsters
Sweden
Telephone: +46 (0) 21 34 20 00
Facsimile: +46 (0) 21 14 69 18
Internet: www.abb.com/substationautomation
Printed on recycled and ecolabelled paper at Elanders Novum

Engineering Guide IED670 Products

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Engineering Guide IED670 Products

Uploaded by

Copyright:

Available Formats

Engineering guide

IED 670 products

Innovation from ABB

About this Manual

Copyright 2006 ABB. All rights reserved.

Chapter 1 Introduction ..................................................................... 1

Introduction to the IED 670 engineering guide .................................... 2

Chapter 2 IED 670 engineering tool set introduction .................... 7

IED 670 engineering tool set introduction............................................ 8

Chapter 3 PCM 600 Tool set .......................................................... 15

PCM 600 Tool set .............................................................................. 16

Chapter 4 Set up a project ............................................................. 43

Chapter 5 IED 670 Engineering process....................................... 59

IED Engineering process ................................................................... 60

Chapter 6 IED 670 signal engineering per protocol..................... 91

Chapter 7 IED monitoring process .............................................. 121

Disturbance record handler DRH..................................................... 122

Chapter 8 IED 670 diagnostic capabilities .................................. 147

IED 670 event viewer IEV ................................................................ 148

Chapter 9 Glossary....................................................................... 159

About this chapter

1 Introduction to the IED 670 engineering guide

1.1 About the complete set of manuals for an IED

Application Technical Installation and Operators Engineering

1.2 About the IED 670 engineering guide

IED 670 engineering tool set introduction

1.3 Intended audience

1.4 Related documents

Documents related to RED 670 Identity number

Documents related to REL 670 Identity number

Documents related to REC 670 Identity number

Documents related to RET 670 Identity number

Documents related to REB 670 Identity number

Connection and Installation components 1MRK 013 003-BEN

Latest versions of the described documentation can be found on www.abb.com/substationautomation

1.5 Revision notes

Chapter 2 IED 670

About this chapter

1 IED 670 engineering tool set introduction

IED 670 product engineering

2 IED engineering process

Plant structure [PCM 600]

HSI NCC-GW PCM 600

IED 1 (REx 670) [PCM 600]

LEDs and Display

Single line diagram

I / O Boards and I / O Signals

Figure 1: Parts to engineer in an IED 670 product

the IED application functions (AF)

PCM 600 Protection and Control IED Manager

via the RJ 45 connector on the front panel (Ethernet)

Figure 2: Connecting PCM 600 to an IED 670

3 IED signal engineering per protocol

4 IED monitoring process

a Disturbance recording handler tool (DRH)

5 IED diagnostic capabilities

The two tools are:

the IED event viewer (IEV)

Chapter 3 PCM 600 Tool set

About this chapter

PCM 600 CAP 531 PST SMT GDE

Project Data Base

PCM 600 Tool set for IED engineering overview

all tools operate on a common project data base per project