670 Series Version 2.2 IEC: Engineering Manual
670 Series Version 2.2 IEC: Engineering Manual
670 series
Version 2.2 IEC
Engineering manual
Document ID: 1MRK511398-UEN
Issued: March 2024
Revision: N
Product version: 2.2
The software and hardware described in this document is furnished under a license and may be used or
disclosed only in accordance with the terms of such license.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(https://www.openssl.org/). This product includes cryptographic software written/developed by: Eric
Young (eay@cryptsoft.com) and Tim Hudson (tjh@cryptsoft.com).
Trademarks
ABB is a registered trademark of ABB Asea Brown Boveri Ltd. Manufactured by/for a Hitachi Energy
company. All other brand or product names mentioned in this document may be trademarks or
registered trademarks of their respective holders.
Warranty
Please inquire about the terms of warranty from your nearest Hitachi Energy representative.
Disclaimer
When the products and services provided by Hitachi Energy are designed to be connected to and
to communicate information and data via a network interface with Customer’s network or system
(Customer System), it is the sole responsibility of the Customer to provide and continuously ensure
a secure connection between the Customer’s System and Customer's network and any other network.
It is the sole responsibility of the Customer to establish and maintain any appropriate measures (e.g.,
the installation of firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc.) to protect the Customer’s System including its network and external interfaces
against any kind of security breaches, unauthorized access, interference, intrusion, leakage and/or theft
or losses of data or information. As necessary for the provision of work, the Customer will permit Hitachi
Energy’s employees, agents, consultants and/or subcontractors to remotely access certain systems
owned, controlled or operated by or on behalf of Customer.
Not withstanding any other provision to the contrary and regardless whether the contract is terminated or
not, Hitachi Energy, its subcontractors, its and their affiliates and its and their employees are under no
circumstances liable for and the Customer shall defend and indemnify said parties from and against any
claim for damages and/or losses related to any security breaches, unauthorized access, interference,
intrusion, leakage and/or theft or loss of data or information resulting from Customer’s failure to secure
Customer’s System. In the event a Security Incident on Customer’s System results in Hitachi Energy
Information being disclosed such that notification is required to be made under any applicable laws, or
pursuant to a request or directive from a governmental authority, Customer will coordinate with Hitachi
Energy prior to the disclosure as mutually agreed, except as required by applicable law.
The data, examples and diagrams in this manual are included solely for the concept or product
description and are not to be deemed as a statement of guaranteed properties. All persons responsible
for applying the equipment addressed in this manual must satisfy themselves that each intended
application is suitable and acceptable, including that any applicable safety or other operational
requirements are complied with. In particular, any risks in applications where a system failure and/or
product failure would create a risk for harm to property or persons (including but not limited to personal
injuries or death) shall be the sole responsibility of the person or entity applying the equipment, and
those so responsible are hereby requested to ensure that all measures are taken to exclude or mitigate
such risks.
This document has been carefully checked by Hitachi Energy, but deviations cannot be completely ruled
out. In case any errors are detected, the reader is kindly requested to notify the manufacturer. Other
than under explicit contractual commitments, in no event shall Hitachi Energy be responsible or liable for
any loss or damage resulting from the use of this manual or the application of the equipment.
Conformity
This product complies with the directive of the Council of the European Communities on the
approximation of the laws of the Member States relating to electromagnetic compatibility (EMC Directive
2004/108/EC) and concerning electrical equipment for use within specified voltage limits (Low-voltage
directive 2006/95/EC). This conformity is the result of tests conducted by Hitachi Energy in accordance
with the product standard EN 60255-26 for the EMC directive, and with the product standards EN
60255-1 and EN 60255-27 for the low voltage directive. The product is designed in accordance with the
international standards of the IEC 60255 series.
1MRK511398-UEN Rev. N Table of contents
Table of contents
Section 1 Introduction........................................................................................................ 5
1.1 This manual................................................................................................................................5
1.2 Intended audience......................................................................................................................5
1.3 Product documentation.............................................................................................................. 6
1.3.1 Product documentation set.......................................................................................................6
1.3.2 Document revision history........................................................................................................ 7
1.3.3 Related documents.................................................................................................................. 8
1.4 Document symbols and conventions........................................................................................10
1.4.1 Symbols..................................................................................................................................10
1.4.2 Document conventions...........................................................................................................10
1.5 IEC 61850 Edition 1, Edition 2, and Edition 2.1 mapping......................................................... 11
670 series 1
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Table of contents 1MRK511398-UEN Rev. N
2 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Table of contents
Section 12 Glossary..........................................................................................................145
12.1 Glossary................................................................................................................................. 145
670 series 3
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
4
1MRK511398-UEN Rev. N Section 1
Introduction
Section 1 Introduction
1.1 This manual GUID-AB423A30-13C2-46AF-B7FE-A73BB425EB5F v21
The engineering manual contains instructions on how to engineer the IEDs using the various tools
available within the PCM600 software. The manual provides instructions on how to set up a PCM600
project and insert IEDs to the project structure. The manual also recommends a sequence for the
engineering of protection and control functions, as well as communication engineering for IEC 61850.
This manual addresses system and project engineers involved in the engineering process of a project,
and installation and commissioning personnel, who use technical data during engineering, installation
and commissioning, and in normal service.
The system engineer must have a thorough knowledge of protection and/or control systems, protection
and/or control equipment, protection and/or control functions and the configured functional logics in the
IEDs. The installation and commissioning personnel must have a basic knowledge of handling electronic
equipment.
670 series 5
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Decommissioning
Commissioning
Maintenance
Engineering
Operation
Installing
Engineering manual
Installation manual
Commissioning manual
Operation manual
Application manual
Technical manual
Communication
protocol manual
Cyber security
deployment guideline
IEC07000220-4-en.vsd
IEC07000220 V4 EN-US
The engineering manual contains instructions on how to engineer the IEDs using the various tools
available within the PCM600 software. The manual provides instructions on how to set up a PCM600
project and insert IEDs to the project structure. The manual also recommends a sequence for the
engineering of protection and control functions, as well as communication engineering for IEC 61850.
The installation manual contains instructions on how to install the IED. The manual provides procedures
for mechanical and electrical installation. The chapters are organized in the chronological order in which
the IED should be installed.
The commissioning manual contains instructions on how to commission the IED. The manual can also
be used by system engineers and maintenance personnel for assistance during the testing phase. The
manual provides procedures for the checking of external circuitry and energizing the IED, parameter
setting and configuration as well as verifying settings by secondary injection. The manual describes the
process of testing an IED in a substation which is not in service. The chapters are organized in the
chronological order in which the IED should be commissioned. The relevant procedures may be followed
also during the service and maintenance activities.
6 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
The operation manual contains instructions on how to operate the IED once it has been commissioned.
The manual provides instructions for the monitoring, controlling and setting of the IED. The manual also
describes how to identify disturbances and how to view calculated and measured power grid data to
determine the cause of a fault.
The application manual contains application descriptions and setting guidelines sorted per function. The
manual can be used to find out when and for what purpose a typical protection function can be used.
The manual can also provide assistance for calculating settings.
The technical manual contains operation principle descriptions, and lists function blocks, logic diagrams,
input and output signals, setting parameters and technical data, sorted per function. The manual can be
used as a technical reference during the engineering phase, installation and commissioning phase, and
during normal service.
The communication protocol manual describes the communication protocols supported by the IED. The
manual concentrates on the vendor-specific implementations.
The point list manual describes the outlook and properties of the data points specific to the IED. The
manual should be used in conjunction with the corresponding communication protocol manual.
The cyber security deployment guideline describes the process for handling cyber security when
communicating with the IED. Certification, Authorization with role based access control, and product
engineering for cyber security related events are described and sorted by function. The guideline can be
used as a technical reference during the engineering phase, installation and commissioning phase, and
during normal service.
670 series 7
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
8 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
670 series 9
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
The electrical warning icon indicates the presence of a hazard which could result in electrical
shock.
The warning icon indicates the presence of a hazard which could result in personal injury.
The caution hot surface icon indicates important information or warning about the
temperature of product surfaces.
The caution icon indicates important information or warning related to the concept discussed
in the text. It might indicate the presence of a hazard which could result in corruption of
software or damage to equipment or property.
The information icon alerts the reader of important facts and conditions.
The tip icon indicates advice on, for example, how to design your project or how to use a
certain function.
Although warning hazards are related to personal injury, it is necessary to understand that under certain
operational conditions, operation of damaged equipment may result in degraded process performance
leading to personal injury or death. It is important that the user fully complies with all warning and
cautionary notices.
• Abbreviations and acronyms in this manual are spelled out in the glossary. The glossary also contains
definitions of important terms.
• Push button navigation in the LHMI menu structure is presented by using the push button icons.
For example, to navigate between the options, use and .
• HMI menu paths are presented in bold.
For example, select Main menu/Settings.
• LHMI messages are shown in Courier font.
For example, to save the changes in non-volatile memory, select Yes and press .
• Parameter names are shown in italics.
For example, the function can be enabled and disabled with the Operation setting.
• Each function block symbol shows the available input/output signal.
10 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
• the character ^ in front of an input/output signal name indicates that the signal name may be
customized using the PCM600 software.
• the character * after an input signal name indicates that the signal must be connected to another
function block in the application configuration to achieve a valid application configuration.
• Dimensions are provided both in inches and millimeters. If it is not specifically mentioned then the
dimension is in millimeters.
1.5 IEC 61850 Edition 1, Edition 2, and Edition 2.1 mapping GUID-C5133366-7260-4C47-A975-7DBAB3A33A96 v10
Function block names are used in ACT and PST to identify functions. Respective function block names
of Edition 1, Edition 2, and Edition 2.1 logical nodes are shown in the table below.
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
- - ALGOS
- - ALSVS
AEGPVOC AEGGAPC AEGPVOC
AGSAL AGSAL AGSAL
SECLLN0
ALMCALH ALMCALH ALMCALH
ALTIM - ALTIM
ALTMS - ALTMS
ALTRK - ALTRK
APPTEF
BCZPDIF BCZPDIF BCZPDIF
BCZSPDIF BCZSPDIF BCZSPDIF
BCZTPDIF BCZTPDIF BCZTPDIF
BDCGAPC SWSGGIO BBCSWI
BDCGAPC
BDZS4GAPC BBT4LLN0 LLN0
BDZSGAPC BDZSGAPC
BDZSGAPC BBS6LLN0 LLN0
BDZSGAPC BDZSGAPC
BFPTRC_F01 BFPTRC BFPTRC
BFPTRC_F02 BFPTRC BFPTRC
BFPTRC_F03 BFPTRC BFPTRC
BFPTRC_F04 BFPTRC BFPTRC
BFPTRC_F05 BFPTRC BFPTRC
BFPTRC_F06 BFPTRC BFPTRC
BFPTRC_F07 BFPTRC BFPTRC
BFPTRC_F08 BFPTRC BFPTRC
BFPTRC_F09 BFPTRC BFPTRC
BFPTRC_F10 BFPTRC BFPTRC
BFPTRC_F11 BFPTRC BFPTRC
BFPTRC_F12 BFPTRC BFPTRC
BFPTRC_F13 BFPTRC BFPTRC
BFPTRC_F14 BFPTRC BFPTRC
BFPTRC_F15 BFPTRC BFPTRC
BFPTRC_F16 BFPTRC BFPTRC
Table continues on next page
670 series 11
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
BFPTRC_F17 BFPTRC BFPTRC
BFPTRC_F18 BFPTRC BFPTRC
BFPTRC_F19 BFPTRC BFPTRC
BFPTRC_F20 BFPTRC BFPTRC
BFPTRC_F21 BFPTRC BFPTRC
BFPTRC_F22 BFPTRC BFPTRC
BFPTRC_F23 BFPTRC BFPTRC
BFPTRC_F24 BFPTRC BFPTRC
BICPTRC_01 BICPTRC BICPTRC
BICPTRC_02 BICPTRC BICPTRC
BICPTRC_03 BICPTRC BICPTRC
BICPTRC_04 BICPTRC BICPTRC
BICPTRC_05 BICPTRC BICPTRC
BICTPTRC_BIC01 BICTPTRC BICTPTRC
BICTPTRC_BIC02 BICTPTRC BICTPTRC
BICTPTRC_BIC03 BICTPTRC BICTPTRC
BICTPTRC_BIC04 BICTPTRC BICTPTRC
BRCPTOC BRCPTOC BRCPTOC
BRPTOC BRPTOC BRPTOC
BTCZPDIF BTCZPDIF BTCZPDIF
BTFPTRC_F01 BTFPTRC BTFPTRC
BTFPTRC_F02 BTFPTRC BTFPTRC
BTFPTRC_F03 BTFPTRC BTFPTRC
BTFPTRC_F04 BTFPTRC BTFPTRC
BTFPTRC_F05 BTFPTRC BTFPTRC
BTFPTRC_F06 BTFPTRC BTFPTRC
BTFPTRC_F07 BTFPTRC BTFPTRC
BTFPTRC_F08 BTFPTRC BTFPTRC
BTFPTRC_F09 BTFPTRC BTFPTRC
BTFPTRC_F10 BTFPTRC BTFPTRC
BTFPTRC_F11 BTFPTRC BTFPTRC
BTFPTRC_F12 BTFPTRC BTFPTRC
BTIGAPC B16IFCVI BTIGAPC
BTZNPDIF_Z1 BTZNPDIF BTZNPDIF
BTZNPDIF_Z2 BTZNPDIF BTZNPDIF
BTZNPDIF_Z3 BTZNPDIF BTZNPDIF
BTZNPDIF_Z4 BTZNPDIF BTZNPDIF
BUSPTRC_B1 BUSPTRC BUSPTRC
BBSPLLN0
BUSPTRC_B2 BUSPTRC BUSPTRC
BUSPTRC_B3 BUSPTRC BUSPTRC
BUSPTRC_B4 BUSPTRC BUSPTRC
BUSPTRC_B5 BUSPTRC BUSPTRC
BUSPTRC_B6 BUSPTRC BUSPTRC
BUSPTRC_B7 BUSPTRC BUSPTRC
BUSPTRC_B8 BUSPTRC BUSPTRC
BUSPTRC_B9 BUSPTRC BUSPTRC
Table continues on next page
12 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
BUSPTRC_B10 BUSPTRC BUSPTRC
BUSPTRC_B11 BUSPTRC BUSPTRC
BUSPTRC_B12 BUSPTRC BUSPTRC
BUSPTRC_B13 BUSPTRC BUSPTRC
BUSPTRC_B14 BUSPTRC BUSPTRC
BUSPTRC_B15 BUSPTRC BUSPTRC
BUSPTRC_B16 BUSPTRC BUSPTRC
BUSPTRC_B17 BUSPTRC BUSPTRC
BUSPTRC_B18 BUSPTRC BUSPTRC
BUSPTRC_B19 BUSPTRC BUSPTRC
BUSPTRC_B20 BUSPTRC BUSPTRC
BUSPTRC_B21 BUSPTRC BUSPTRC
BUSPTRC_B22 BUSPTRC BUSPTRC
BUSPTRC_B23 BUSPTRC BUSPTRC
BUSPTRC_B24 BUSPTRC BUSPTRC
BUTPTRC_B1 BUTPTRC BUTPTRC
BBTPLLN0
BUTPTRC_B2 BUTPTRC BUTPTRC
BUTPTRC_B3 BUTPTRC BUTPTRC
BUTPTRC_B4 BUTPTRC BUTPTRC
BUTPTRC_B5 BUTPTRC BUTPTRC
BUTPTRC_B6 BUTPTRC BUTPTRC
BUTPTRC_B7 BUTPTRC BUTPTRC
BUTPTRC_B8 BUTPTRC BUTPTRC
BZISGGIO BZISGGIO -
BZNPDIF_Z1 BZNPDIF BZNPDIF
BZNPDIF_Z2 BZNPDIF BZNPDIF
BZNPDIF_Z3 BZNPDIF BZNPDIF
BZNPDIF_Z4 BZNPDIF BZNPDIF
BZNPDIF_Z5 BZNPDIF BZNPDIF
BZNPDIF_Z6 BZNPDIF BZNPDIF
BZNSPDIF_A BZNSPDIF BZASGAPC
BZASPDIF
BZNSGAPC
BZNSPDIF
BZNSPDIF_B BZNSPDIF BZBSGAPC
BZBSPDIF
BZNSGAPC
BZNSPDIF
BZNTPDIF_A BZNTPDIF BZATGAPC
BZATPDIF
BZNTGAPC
BZNTPDIF
BZNTPDIF_B BZNTPDIF BZBTGAPC
BZBTPDIF
BZNTGAPC
BZNTPDIF
Table continues on next page
670 series 13
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
CBPGAPC CBPLLN0 CBPMMXU
CBPMMXU CBPPTRC
CBPPTRC HOLPTOV
HOLPTOV HPH1PTOV
HPH1PTOV PH3PTOC
PH3PTUC PH3PTUC
PH3PTOC RP3PDOP
RP3PDOP
CCPDSC CCRPLD CCPDSC
CCRBRF CCRBRF CCRBRF
CCSRBRF CCSRBRF CCSRBRF
CCSSPVC CCSRDIF CCSSPVC
CHMMHAI CHMMHAI CHMMHAI
CMMXU CMMXU CMMXU
CMSQI CMSQI CMSQI
COUVGAPC COUVLLN0 COUVPTOV
COUVPTOV COUVPTUV
COUVPTUV
CVGAPC GF2LLN0 GF2MMXN
GF2MMXN GF2PHAR
GF2PHAR GF2PTOV
GF2PTOV GF2PTUC
GF2PTUC GF2PTUV
GF2PTUV GF2PVOC
GF2PVOC PH1PTRC
PH1PTRC
CVMMXN CVMMXN CVMMXN
DELISPVC DELISPVC DELISPVC
DELSPVC DELSPVC DELSPVC
DELVSPVC DELVSPVC DELVSPVC
DPGAPC DPGGIO DPGAPC
DRPRDRE DRPRDRE DRPRDRE
ECPSCH ECPSCH ECPSCH
ECRWPSCH ECRWPSCH ECRWPSCH
EF4PTOC EF4LLN0 EF4PTRC
EF4PTRC EF4RDIR
EF4RDIR GEN4PHAR
GEN4PHAR PH1PTOC
PH1PTOC
EFPIOC EFPIOC EFPIOC
ETPMMTR ETPMMTR ETPMMTR
FDPSPDIS FDPSPDIS FDPSPDIS
FLTMMXU FLTMMXU FLTMMXU
FMPSPDIS FMPSPDIS FMPSPDIS
FRPSPDIS FPSRPDIS FPSRPDIS
FTAQFVR FTAQFVR FTAQFVR
FUFSPVC SDDRFUF FUFSPVC
SDDSPVC
GENPDIF GENPDIF GENGAPC
GENPDIF
GENPHAR
GENPTRC
GOPPDOP GOPPDOP GOPPDOP
PH1PTRC
GRPTTR GRPTTR GRPTTR
Table continues on next page
14 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
GSPTTR GSPTTR GSPTTR
GUPPDUP GUPPDUP GUPPDUP
PH1PTRC
HZPDIF HZPDIF HZPDIF
INDCALH INDCALH INDCALH
ITBGAPC IB16FCVB ITBGAPC
L3CPDIF L3CPDIF L3CGAPC
L3CPDIF
L3CPHAR
L3CPTRC
L4CPDIF L4CLLN0 LLN0
L4CPDIF L4CGAPC
L4CPTRC L4CPDIF
L4CPSCH
L4CPTRC
L4UFCNT L4UFCNT L4UFCNT
L6CPDIF L6CPDIF L6CGAPC
L6CPDIF
L6CPHAR
L6CPTRC
LAPPGAPC LAPPLLN0 LAPPPDUP
LAPPPDUP LAPPPUPF
LAPPPUPF
LCCRPTRC LCCRPTRC LCCRPTRC
LCNSPTOC LCNSPTOC LCNSPTOC
LCNSPTOV LCNSPTOV LCNSPTOV
LCP3PTOC LCP3PTOC LCP3PTOC
LCP3PTUC LCP3PTUC LCP3PTUC
LCPTTR LCPTTR LCPTTR
LCZSPTOC LCZSPTOC LCZSPTOC
LCZSPTOV LCZSPTOV LCZSPTOV
LD0LLN0 LLN0 -
LDLPSCH LDLPDIF LDLPSCH
LDRGFC STSGGIO LDRGFC
LLDLPTRC
PHPTUC
PHPTUV
SVABPTOC
SVBCPTOC
SVCAPTOC
ZSPTOC
LEXPDIS LEXPDIS LEXPDIS
LEXPTRC
LFPTTR LFPTTR LFPTTR
LMBRFLO LMBRFLO LMBRFLO
LOLSPTR LOLSPTR LOLSPTR
LOVPTUV LOVPTUV LOVPTUV
LPHD LPHD
LT3CPDIF LT3CPDIF LT3CGAPC
LT3CPDIF
LT3CPHAR
LT3CPTRC
LT6CPDIF LT6CPDIF LT6CGAPC
LT6CPDIF
LT6CPHAR
LT6CPTRC
Table continues on next page
670 series 15
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
MVGAPC MVGGIO MVGAPC
NS2PTOC NS2LLN0 NS2PTOC
NS2PTOC NS2PTRC
NS2PTRC
NS4PTOC EF4LLN0 EF4PTRC
EF4PTRC EF4RDIR
EF4RDIR PH1PTOC
GEN4PHAR
PH1PTOC
OC4PTOC OC4LLN0 GEN4PHAR
GEN4PHAR PH3PTOC
PH3PTOC PH3PTRC
PH3PTRC
OEXPVPH OEXPVPH OEXPVPH
OOSPPAM OOSPPAM OOSPPAM
OOSPTRC
OV2PTOV GEN2LLN0 OV2PTOV
OV2PTOV PH1PTRC
PH1PTRC
PAPGAPC PAPGAPC PAPGAPC
PCFCNT PCGGIO PCFCNT
PH4SPTOC GEN4PHAR GEN4PHAR
OCNDLLN0 PH1BPTOC
PH1BPTOC PH1PTRC
PH1PTRC
PHPIOC PHPIOC PHPIOC
PSLPSCH ZMRPSL PSLPSCH
PSPPPAM PSPPPAM PSPPPAM
PSPPTRC
PSTPDIF PSTPDIF PSTPDIF
PSTPHAR
PSTPTRC
PTRSTHR PTRSTHR PTRSTHR
QCBAY QCBAY BAY/LLN0
QCRSV QCRSV QCRSV
RCHLCCH RCHLCCH RCHLCCH
REFPDIF REFPDIF REFPDIF
ROTIPHIZ ROTIPHIZ ROTIPHIZ
ROTIPTRC
ROV2PTOV GEN2LLN0 PH1PTRC
PH1PTRC ROV2PTOV
ROV2PTOV
SAPFRC SAPFRC SAPFRC
SAPTOF SAPTOF SAPTOF
SAPTUF SAPTUF SAPTUF
SCCFPVOC SCCFPTRC SCCFPTRC
SCCFPVOC SCCFPVOC
SCCVPTOC SCCVPTOC SCCVPTOC
SCHLCCH SCHLCCH SCHLCCH
SCILO SCILO SCILO
SCPDPTDV SCPDLLN0 SCPDLLN0
SCPDGAPC SCPDGAPC
SCPDMMXU SCPDMMXU
SCPDPTOV SCPDPTOV
Table continues on next page
16 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
SCUCPTOC SCUCLLN0 SCUCLLN0
RUBCMMXU RUBCMMXU
SCUCGAPC SCUCGAPC
SCUCPTOC SCUCPTOC
UBCMMXU UBCMMXU
SCUVPTOV SCUVLLN0 SCUVLLN0
SCUVGAPC SCUVGAPC
SCUVMMXN SCUVMMXN
SCUVPTOV SCUVPTOV
SCSWI SCSWI SCSWI
SDEPSDE SDEPSDE SDEPSDE
SDEPTOC
SDEPTOV
SDEPTRC
SESRSYN RSY1LLN0 AUT1RSYN
AUT1RSYN MAN1RSYN
MAN1RSYN SYNRSYN
SYNRSYN
SLGAPC SLGGIO SLGAPC
SMBRREC SMBRREC SMBRREC
SMPPTRC SMPPTRC SMPPTRC
SMTRFLO SMTRFLO SMTRFLO
SP16GAPC SP16GGIO SP16GAPC
SPC8GAPC SPC8GGIO SPC8GAPC
SPGAPC SPGGIO SPGAPC
SSCBR SSCBR SSCBR
SSIMG SSIMG SSIMG
SSIML SSIML SSIML
STBPTOC STBPTOC BBPMSS
STBPTOC
STEFPHIZ STEFPHIZ STEFPHIZ
STTIPHIZ STTIPHIZ STTIPHIZ
SXCBR SXCBR SXCBR
SXSWI SXSWI SXSWI
T2WPDIF T2WPDIF T2WGAPC
T2WPDIF
T2WPHAR
T2WPTRC
T3WPDIF T3WPDIF T3WGAPC
T3WPDIF
T3WPHAR
T3WPTRC
TCLYLTC TCLYLTC TCLYLTC
TCSLTC
TCMYLTC TCMYLTC TCMYLTC
TEIGAPC TEIGGIO TEIGAPC
TEIGGIO
TEILGAPC TEILGGIO TEILGAPC
TMAGAPC TMAGGIO TMAGAPC
TR1ATCC TR1ATCC TR1ATCC
TR8ATCC TR8ATCC TR8ATCC
TRPTTR TRPTTR TRPTTR
UV2PTUV GEN2LLN0 PH1PTRC
PH1PTRC UV2PTUV
UV2PTUV
Table continues on next page
670 series 17
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical nodes
VDCPTDV VDCPTOV VDCPTOV
VDSPVC VDRFUF VDSPVC
VHMMHAI VHMMHAI VHMMHAI
VHMQVHA VHMQVHA
VMMXU VMMXU VMMXU
VMSQI VMSQI VMSQI
VNMMXU VNMMXU VNMMXU
VRPVOC VRLLN0 PH1PTRC
PH1PTRC PH1PTUV
PH1PTUV VRPVOC
VRPVOC
VSGAPC VSGGIO VSGAPC
WRNCALH WRNCALH WRNCALH
ZCLCPSCH ZCLCPLAL ZCLCPSCH
ZCPSCH ZCPSCH ZCPSCH
ZCRWPSCH ZCRWPSCH ZCRWPSCH
ZCVPSOF ZCVPSOF ZCVPSOF
ZGVPDIS ZGVLLN0 PH1PTRC
PH1PTRC ZGVPDIS
ZGVPDIS ZGVPTUV
ZGVPTUV
ZMCAPDIS ZMCAPDIS ZMCAPDIS
ZMCPDIS ZMCPDIS ZMCPDIS
ZMFCPDIS ZMFCLLN0 PSFPDIS
PSFPDIS ZMFPDIS
ZMFPDIS ZMFPTRC
ZMFPTRC ZMMMXU
ZMMMXU
ZMFPDIS ZMFLLN0 PSFPDIS
PSFPDIS PSFPDIS
ZMFPDIS ZMFPDIS
ZMFPTRC ZMFPTRC
ZMMMXU ZMMMXU
ZMHPDIS ZMHPDIS ZMHPDIS
ZMMAPDIS ZMMAPDIS ZMMAPDIS
ZMMPDIS ZMMPDIS ZMMPDIS
ZMQAPDIS ZMQAPDIS ZMQAPDIS
ZMQPDIS ZMQPDIS ZMQPDIS
ZMRAPDIS ZMRAPDIS ZMRAPDIS
ZMRPDIS ZMRPDIS ZMRPDIS
ZMBURPSB ZMBURPSB ZMBURPSB
ZPCPSCH ZPCPSCH ZPCPSCH
ZPCWPSCH ZPCWPSCH ZPCWPSCH
ZSMGAPC ZSMGAPC ZSMGAPC
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical
nodes
- - ALGOS
- - ALSVS
AGSAL AGSAL AGSAL
SECLLN0
ALMCALH ALMCALH ALMCALH
Table continues on next page
18 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical
nodes
ALTIM - ALTIM
ALTMS - ALTMS
ALTRK - ALTRK
BRPTOC BRPTOC BRPTOC
BTIGAPC B16IFCVI BTIGAPC
CCRWRBRF CCRWRBRF CCRWRBRF
CCSSPVC CCSRDIF CCSSPVC
CHMMHAN - LLN0
CHMMHAN
CHMQVHA
CMMXU CMMXU CMMXU
CMSQI CMSQI CMSQI
CVMMXN CVMMXN CVMMXN
D2PTOC D2LLN0 D2PTOC
D2PTOC PH1PTRC
PH1PTRC
DELISPVC DELISPVC DELISPVC
DELSPVC DELSPVC DELSPVC
DELVSPVC DELVSPVC DELVSPVC
DPGAPC DPGGIO DPGAPC
DRPRDRE DRPRDRE DRPRDRE
ECPSCH ECPSCH ECPSCH
ECRWPSCH ECRWPSCH ECRWPSCH
EF2PTOC EF2LLN0 EF2PTRC
EF2PTRC EF2RDIR
EF2RDIR GEN2PHAR
GEN2PHAR PH1PTOC
PH1PTOC
EFRWPIOC EFRWPIOC EFRWPIOC
ETPMMTR ETPMMTR ETPMMTR
FLTMMXU FLTMMXU FLTMMXU
FRWSPVC FRWSPVC FRWSPVC
INDCALH INDCALH INDCALH
ITBGAPC IB16FCVB ITBGAPC
L4UFCNT L4UFCNT L4UFCNT
LPHD LPHD -
LPTTR LPTTR LPTTR
MVGAPC MVGGIO MVGAPC
O2RWPTOV GEN2LLN0 O2RWPTOV
O2RWPTOV PH1PTRC
PH1PTRC
PCFCNT PCFCNT PCFCNT
PHPIOC PHPIOC PHPIOC
QCBAY QCBAY BAY/LLN0
QCRSV QCRSV QCRSV
RCHLCCH RCHLCCH RCHLCCH
REFPDIF REFPDIF REFPDIF
ROV2PTOV GEN2LLN0 PH1PTRC
PH1PTRC ROV2PTOV
ROV2PTOV
Table continues on next page
670 series 19
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 1 1MRK511398-UEN Rev. N
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical
nodes
RWRFLO - RWRFLO
SAPTUF SAPTUF SAPTUF
SCHLCCH SCHLCCH SCHLCCH
SCILO SCILO SCILO
SCSWI SCSWI SCSWI
SDEPSDE SDEPSDE SDEPSDE
SDEPTOC
SDEPTOV
SDEPTRC
SESRSYN RSY1LLN0 AUT1RSYN
AUT1RSYN MAN1RSYN
MAN1RSYN SYNRSYN
SYNRSYN
SLGAPC SLGGIO SLGAPC
SMBRREC SMBRREC SMBRREC
SMPPTRC SMPPTRC SMPPTRC
SP16GAPC SP16GGIO SP16GAPC
SPC8GAPC SPC8GGIO SPC8GAPC
SPGAPC SPGGIO SPGAPC
SSCBR SSCBR SSCBR
SSIMG SSIMG SSIMG
SSIML SSIML SSIML
SXCBR SXCBR SXCBR
SXSWI SXSWI SXSWI
T1PPDIF - T1PPDIF
T1PPHAR
T1PPTRC
TCLYLTC TCLYLTC TCLYLTC
TCSLTC
TCMYLTC TCMYLTC TCMYLTC
TEIGAPC TEIGGIO TEIGAPC
TEIGGIO
TEILGAPC TEILGGIO TEILGAPC
TMAGAPC TMAGGIO TMAGAPC
TPPIOC TPPIOC TPPIOC
U2RWPTUV GEN2LLN0 PH1PTRC
PH1PTRC U2RWPTUV
U2RWPTUV
VHMMHAN - LLN0
VHMMHAN
VHMQVHA
VMMXU VMMXU VMMXU
VMSQI VMSQI VMSQI
VNMMXU VNMMXU VNMMXU
VRPVOC LLN0 LLN0
PH1PTRC PH1PTRC
PH1PTUV PH1PTUV
VRPVOC VRPVOC
VSGAPC VSGGIO VSGAPC
WRNCALH WRNCALH WRNCALH
XENCPOW - XENCPOW
ZCPSCH ZCPSCH ZCPSCH
Table continues on next page
20 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 1
Introduction
Function block name Edition 1 logical nodes Edition 2 and Edition 2.1 logical
nodes
ZCRWPSCH ZCRWPSCH ZCRWPSCH
ZGTPDIS ZGTLLN0 ZGPDIS
ZGPDIS ZGPTRC
ZGPTRC
ZCVPSOF - LLN0
ZRCPDIS
ZRCPTRC
ZRWPDIS - PSRWPDIS
ZRWPDIS
ZRWPTRC
1.
670 series 21
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
22
1MRK511398-UEN Rev. N Section 2
Engineering tool set
The structure of a monitoring and control system for electrical substations has a principle structure as
shown in Figure 2. It contains a number of IEDs for the various purposes.
Station bus
Station
Communication
Process bus
level
Process Process Process
IED 1 IED 2 IED m
IEC08000101 V3 EN-US
All three parts require specific engineering and configuration. PCM600 is used to do the complete
engineering and configuration activities needed for bay level IEDs.
Each IED type and version has its own connectivity package module used in PCM600.
PCM600 communicates with the bay IEDs via an Ethernet connection. The connection allows to
reading and writing all configuration data needed for proper operation from or to the IED. The IEDs
have communication interfaces for protocols and media used for station communication. IEC 61850
communication files for a bay IED or a complete station can be exported from PCM600 to station
engineering tools for engineering of station communication between bay IEDs and station IEDs.
A PC with PCM600 can be connected to any IED on the station bus using the Ethernet connection.
The Ethernet connection can then later also be used for service and maintenance purposes. The
connection is also used to handle disturbance records in COMTRADE format from IEDs using the IEC
61850 file transfer or FTP.
The IEDs of today are designed on the concept of the IEC 61850 standard. This is mainly given for
the organization of functions represented by an equivalent logical node in the IEC 61850 standard. The
670 series 23
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 2 1MRK511398-UEN Rev. N
Engineering tool set
mapping between the logical node data model in the IED, following the structure and rules in part 7
of the IEC 61850 standard, and the function blocks in an IED configuration is given in the IEC 61850
communication protocol manual.
The same IEC 61850–based concept is also used for the DNP3 protocol. The signals used or delivered
by a function block are automatically generated and available for station communication. This concept
allows a very efficient time saving signal engineering.
The engineering of the used communication protocols is a separate task and an addition to the
engineering of control functions.
PCM600 can be used for different purposes throughout the IED life cycle. A set of special tools is
available for different applications.
This manual is valid for PCM600 supporting the Relion 670/650 series product ver.2.2.
PCM600 is used for various tasks in the IED engineering process. See Figure 3:
• Communication engineering
• IEC 61850 station communication engineering can be done in two ways, with a separate tool,
IET600 or with the PCM600 built in IEC 61850 configuration tool. PCM600 interacts with IET600 by
importing and exporting SCL files. The built in tool can be used for small projects including Hitachi
Energy IEDs only. To engineer communication between Hitachi Energy IED's and third party devices
it's recommended to use IET600.
• Organizing GOOSE messages received is done by using the Signal Matrix tool.
• Communication engineering for the DNP3 protocol by using the Communication Management tool.
24 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 2
Engineering tool set
• Generating overviews about the available (disturbance) recordings in all connected protection IEDs
by using the Disturbance Handling tool.
• Manually reading the recording files (in COMTRADE format) from the IEDs by using the Disturbance
Handling tool or automatically by using the PCM600 scheduler.
• Managing recording files with the assistance of the Disturbance Handling tool.
• Creating overview reports of recording file content for fast evaluation with assistance of the
Disturbance Handling tool.
• Service management
• Monitoring selected signals of an IED for commissioning or service purposes by using the Signal
Monitoring tool.
• Listing all actual existing IED internal events by using the Event Viewer tool.
• Listing all actual pending process events as they are stored in the IED internal disturbance report
event list by using the Event Viewer tool.
Communication Management
DRH
Service Management
MON EVT
PCM600
IEC08000100-3-en.vsd
IEC08000100 V3 EN-US
Additional functionality to manage the project and to organize the user rights:
670 series 25
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 2 1MRK511398-UEN Rev. N
Engineering tool set
• Organizing users with their rights, profile and password to read and write files of the IED. See the
Cyber security deployment guideline for more information.
• Defining allowed activities for the user profiles to use the read and write function.
Once the engineering of the IED is done, the results must be written to the IED. Conversely some parts
of the engineering information can be uploaded from the IED for various purposes.
The connection between the IED and PCM600 is established via an Ethernet link on the front or rear
port on the IED.
The IP addresses of the different ports on the IED are not allowed to belong to the same
subnet.
26 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 3
Engineering process
Start
Parametrization
PST
Easy GOOSE
Make GOOSE connections
engineering ACT SMT
Write configuration
to IED IED IED Write configuration
to IED
WRITE WRITE
End End
IEC08000122-6-en.vsd
IEC08000122 V6 EN-US
The described sequence in Figure 4 is a proposal based on practical experience and dependencies of
the steps. It is possible to do a different sequence based on the available information at the time the
project is started. This means that several iterations may be needed to finish the project.
670 series 27
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 3 1MRK511398-UEN Rev. N
Engineering process
For performance reasons, do not insert more than 40 IEDs in one PCM600 project. Larger
projects can be divided into several PCM600 projects.
• Insert an IED in plant structure which can be done in many ways. By inserting the IED in online
mode where the configuration is read from the physical IED, by inserting an IED in offline mode, by
importing a *.pcmi file or by selecting an IED template from the template library (*.pcmt).
• Rename the IED objects in PCM600 to the projects definitions.
• Set the IEC 61850 technical key (or use the default one from PCM600).
• Check and adjust if needed the setting values for example for:
• Operation of the access points
• Redundant communication on the access points
• Route for communication of devices in different subnetworks
• Operation of merging unit receivers.
28 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 3
Engineering process
670 series 29
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
30
1MRK511398-UEN Rev. N Section 4
Setting up a project
A typical project in PCM600 contains a plant structure including one or several IED objects, where each
IED object contains the engineering data created or modified using the different PCM600 tools.
Several projects can be created and managed by PCM600, but only one project can be active at a time.
A Connectivity package contains the complete description of the IED data signals, parameters and
protocol addresses for a certain IED type and version. Several types of IEDs can be managed in
one PCM600 project, thus the corresponding Connectivity package has to be installed on the PC.
Connectivity Packages and Connectivity Package Updates are managed in the Update Manager.
PCM600 version 2.10 or newer must be used with the 2.2 version of the IED. The
Connectivity package used with PCM600 2.10 and the 2.2 version of the IED must be of
version 3.4.0.0.
A Connectivity package for a specific IED type and version is divided in two parts. The IED Connectivity
package base module is common for all IEDs. The IED specific module is separate for each type of IED.
Procedure
Installing 670 2.1.5 (or lower) version of the Connectivity package on top of the 670 3.4.0.0
Connectivity package will corrupt the Connectivity package installation. To work around this,
uninstall all the Connectivity packages (starting from the lowest version first), and then
install the 670 3.4.0.0 Connectivity package freshly again. Because of parallel Connectivity
package support, 670 3.4.0.0 Connectivity package will background install 670 3.3.0.0, 670
3.2.6.0, 670 3.1.2.0, 670 3.0.2.0, 670 2.1.6 and 670 2.1.5 Connectivity packages.
Both IED and an IED object in PCM600 have a technical key. The purpose of the technical key is to
prevent writing a configuration to wrong IED. The technical key in the IED and PCM600 must be the
same, otherwise it is not possible to write a configuration. Each IED in a PCM600 project must have a
670 series 31
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
unique technical key. It is therefore not possible to set the same technical key for several IEDs in the
same PCM600 project.
For details on technical key settings, see Naming conventions for IEC 61850
The technical key property in PCM600 corresponds to the IED name attribute in SCL files.
Avoid changing the IED name attribute outside PCM600, because data in PCM600 might be
lost when importing SCL files.
When using PCM600 for writing to the IED, it is important that the LHMI is not in a position
where settings can be made. Only one active transaction, from LHMI or PCM600, is allowed
at any one time.
When writing a configuration to the IED, PCM600 checks if the technical key matches between the
IED object in PCM600 and the physical IED. For communication between the IED and PCM600, the
technical key must be the same. Users have the option to read the technical key from the IED and
update it to PCM600 or write the PCM600 technical key to the IED. The user can also define an own
technical key. The error message displayed due to mismatch between PCM600 and IED technical key is
shown in Figure 5.
IEC09000378-2-en.vsd
IEC09000378 V2 EN-US
Figure 5: Error message due to mismatch between PCM600 and IED technical key
Be sure that the IED object in PCM600 has the same IP address as the physical IED, which
is intended to be connected.
The technical key for an IED object in PCM600 can also be changed in the Object properties
window.
32 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC09000667-5-en.vsd
IEC09000667 V5 EN-US
IEC09000380-2-en.vsd
IEC09000380 V2 EN-US
Using the Technical Key Editor the following selections are possible.
670 series 33
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
The maximum technical key length is 25 characters for IEC 61850 Edition 1 and 55
characters for IEC 61850 Edition 2.
4.4 Setting up communication between PCM600 and the IED SEMOD58570-5 v16
The communication between the IED and PCM600 is independent of the communication protocol used
within the substation or to the NCC.
IED with blank front panel will not have front port. Instead in the IED's AP1 will be turned on which will
have the default IP address 192.168.1.10 and subnet mask 255.255.255.0. If the user wants to change
the default IP address, use RIA600 or PCM600.
The communication media is always Ethernet and the used transport layer is TCP/IP.
Each IED has an RJ-45 Ethernet interface connector on the front. The front Ethernet connector is
recommended to be used for communication with PCM600.
When an Ethernet-based station protocol is used, PCM600 communication can use the same Ethernet
port and IP address.
• Direct point-to-point link between PCM600 and the IED front port. The front port can be seen as a
service port.
• A link via a station LAN or from remote via a network.
The physical connection and the IP address must be configured in both cases to enable communication.
34 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
Setting up IP addresses
Communication between the IED and PCM600 is enabled from the LHMI. The IP address and the
corresponding communication subnetwork mask must be set via the Ethernet configuration tool (ECT)
for each available Ethernet interface in the IED. Each Ethernet interface has a default factory IP address
when the IED is delivered. The IP adress and the subnetwork mask might have to be reset when an
additional Ethernet interface is installed or an interface is replaced.
DHCP is available for the front port, and a device connected to it can thereby obtain an automatically
assigned IP address via the local HMI path Main menu/ Configuration/ Communication/ Ethernet
configuration/ Front port/ DHCP.
Alternatively the default IP address for the IED front port is 10.1.150.3 and the corresponding
subnetwork mask is 255.255.255.0, which can be set via the local HMI path Main menu/ Configuration/
Communication/ TCP-IP configuration/ ETHFRNT:1Main menu/ Configuration/ Communication/
Ethernet configuration/ AP_FRONT.
If an IED is equipped with optical LC interface, a converter between RJ-45 and LC is needed.
670 series 35
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC13000057 V2 EN-US
2. Type View network connections and click on the View network connections icon.
36 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC13000058 V2 EN-US
IEC13000059 V2 EN-US
4. Select the TCP/IPv4 protocol from the list of configured components using this connection and click
Properties.
670 series 37
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC13000060 V2 EN-US
5. Select Use the following IP address and define IP address and Subnet mask if the front port is
used and if the IP address is not set to be obtained automatically by the IED,see Figure 12. The IP
address must be different from the IP address chosen for the IED.
IEC13000062 V2 EN-US
The PC and IED must belong to the same subnetwork for this set-up to work.
38 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
The PC and IED must belong to the same subnetwork for this set-up to work.
It is possible to:
It is possible to open projects created in previous versions of PCM600 to the current version,
but the opposite is not possible.
Extension of the exported project file is *.pcmp and those files are only used for exporting and importing
the projects between different installations of PCM600.
1. Select File and Open/Manage Project ... to see the projects that are currently available in the
PCMDataBases.
2. Open Projects on my computer.
3. Click the icon New Project. To create new project currently open projects and object tools shall be
closed.
4. The New Project window opens, see Figure 13.
670 series 39
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC05000609‐3‐en.vsdx
IEC05000609 V3 EN-US
5. Name the project and include a description (optional) and click Create.
6. PCM600 sets up a new project that will be listed under Projects on my computer.
The plant structure is used to identify each IED in its location within the substation organization. It is
a geographical image of the substation and the bays within the substation. The organization structure
for the IEDs may differ from the structure of the primary equipment in the substation. In PCM600 it is
possible to set up a hierarchical structure of five levels for the IED identification.
Build up the plant structure according to the project requirements. PCM600 offers several levels to build
the hierarchical order from Center down to the IEDs in a bay.
40 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC09000710-4-en.vsdx
IEC09000710 V4 EN-US
Once a plant structure is built, the name of each level in the structure should be renamed by the names/
identifications used in the grid. Use the right mouse button to build the plant structure by selecting the
elements from the context menu. Rename the level after insertion using the Rename possibility or the
Object Properties. Figure14 shows the start of a project with two IEDs placed but still not renamed.
The plant structure corresponds to the complete grid including the needed IEDs.
• Right-click on the plant structure, select New and Create from Template ..., or
• Right-click on the plant structure, select New, General and select either IED Group or Substation.
• Click View in the menu bar and select Object Types. Select the needed elements and drag and drop
them into the plant structure. Close the window if it does not close automatically.
This section is only valid when the IEC 61850 standard is used for station bus communication.
According to the IEC 61850–6 clause 8.4, the SCL model allows two kinds of project designation in
the object properties.
• A technical key is used on engineering drawings and for signal identifications. The technical key is
used within SCL for referencing other objects. Observe that name is a relative identification within a
hierarchy of objects. The maximum number of characters allowed for a technical key is 25 for Edition 1
and 55 for Edition 2.
• A user-oriented textual designation is contained in the attribute desc. Attributes cannot contain
carriage return, line feed or tab characters. The semantics of desc must also be relative within an
object hierarchy.
PCM600 takes care of these two possibilities. The two possible signal designations are available per
object in the object properties for all hierarchical levels beginning with the station as the 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 Technical Key or Technical Key.
670 series 41
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
The predefined full path name of the technical key for the IED would be AA1J1Q01A1.
For all practical engineering purposes (both towards the IED and towards the 61850 engineering
process), the user should keep the default SCL technical key. However, it is possible, for example
due to company naming policies, to rename the SCL technical key for the station level, voltage level, bay
level and IED level using the Object properties window as shown in Figure 15.
The renamed full path name of the technical key for the IED would be DMSTATC1Q1SB1.
42 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
GUID-BDE605BB-5ACA-456A-9334-65B3CE3C46F5 V2 EN-US
You can change the SCL version of an IED in PCM600 from Edition 1 of IEC 61850 to Edition 2 or the
other way around. You can also convert a .pcmi file from Edition 1 to Edition 2 or the other way around.
670 series 43
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC17000133-1-en.vsdx
2. In a project that has no IEDs, right-click the bay and select Import... to insert the IED from a .pcmi
file.
3. Right-click the IED and select Change SCL Version and IEC 61850 Edition 1 or IEC 61850 Edition
2.
The Change SCL Version dialog opens.
4. Click Yes to confirm the edition change.
Changing SCL Version dialog opens and shows the conversion progress. When the conversion is
complete, the Change SCL Version dialog opens.
5. Close the dialog by clicking OK.
6. Right-click the IED and select Export... to save the converted IED in a .pcmi file.
The context menu or the Object Types view shows the available IEDs possible to insert on the bay level
in the plant structure according to the installed connectivity package.
44 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
accessed by PCM600. The housing type, the used overlay version for local HMI and the IO boards
included in the IED will be read from the IED directly.
• Offline mode: when the physical IED is not available or not connected to PCM600, the engineering
steps are done without any synchronization with the IED. The offline configuration in PCM600 can
be synchronized with the physical IED at a later state by connecting the IED to PCM600.
The green check mark (as shown in Figure 16) indicates that communication between the IED
object in PCM600 and the physical IED is established.
IEC09000361 V3 EN-US
• Import a template IED from a *.pcmt files available in the template library.
• Import a pre-configured IED available as a *.pcmt file.
Procedure:
670 series 45
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC15000329-1-en.vsdx
IEC15000329 V2 EN-US
1. Right-click the Bay and select New and application type of IED.
2. Select the IED type to insert.
It is also possible to drag an IED from the Object Types window to the Bay level.
IEC09000711-2-en.vsd
IEC09000711 V2 EN-US
46 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC15000332-1-en.vsdx
IEC15000332 V1 EN-US
5. Select the port and insert the IP address of the physical IED to configure, see Figure 20.
IEC09000713-2-en.vsd
IEC09000713 V2 EN-US
6. Cross-check that the IED whose IP address has been inserted, has been detected online by
PCM600, see Figure 16.
The user cannot scan data from the IED or proceed further if the IED is not online or if the IP
address is not correct.
7. Click the Scan option to scan/read the IED Type and IED Version for the IED that is online, see
Figure 21.
670 series 47
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC09000714-4-en.vsd
IEC09000714 V4 EN-US
The IEC 61850 protocol edition can be changed later in the Plant Structure view by right-clicking on
the IED and selecting Change SCL Version.
SCL versions can be changed only if option 'Allow changing SCL version of an IED configuration' is
selected from options in Tools menu.
8. Click Next to open the Housing Selection Page. The IED housing type and display type are detected
and displayed as shown in Figure 22.
IEC09000742-3-en.vsd
IEC09000742 V3 EN-US
9. The Setup Complete Page dialog shows the summary of the IED Type, IED Version, IP Address
of IED and Order Option, see Figure 23. It is possible to Cancel the insertion or confirm the
configuration and do the insertion with Finish.
48 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC09000715-5-en.vdsx
IEC09000715 V5 EN-US
It is not possible to go back and do any modifications in the setup complete page. If an error
is detected, the insertion has to be canceled and the IED has to be inserted again.
When the online configuration is completed, it is advised to read the configuration from
the IED to ensure that the IED object in PCM600 has the same configuration data as the
physical IED.
A template IED can only be inserted when the bay is selected in the plant structure.
670 series 49
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC17000043-1-en.vsdx
IEC17000043 V1 EN-US
2. Select New and Create from Template ... to open the Create New Object from Template window, see
Figure 25.
50 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
IEC15000268-3-en.vsdx
IEC15000268 V3 EN-US
670 series 51
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC09000718 V3 EN-US
5. Click Delete Template to delete the template, click Import Template to import a template from the
selection window or click Create to insert the selected IED to the bay, see Figure 25.
It is possible to insert more than one IED from the Create New Object from Template window
and the selection window remains open until the user clicks Close.
• Use the pre-configuration that has been shipped together with the IED.
• Install the pre-configuration from the Connpack media.
• Download and install pre-configuration from Update Manager.
52 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
To insert a pre-configuration in to plant structure, see section Inserting an IED from the template library.
Because IEC 61850 edition 1 and IEC 61850 edition 2 templates are incompatible, convert
an IEC 61850 edition 1 template to IEC 61850 edition 2 before you insert it.
Ordered pre-configurations are not locked. The user can use any of the available pre-
configurations for a particular product type as a base to create an own configuration. The
only requirement is that all needed hardware and software options are available.
It is possible to give the inserted IED in the plant structure a user-defined name. Be sure to
only user characters a-z, A-Z, 0-9 and _. Do not use space character in IED names.
To insert the template configuration in to a plant structure, see section Inserting an IED from the
template library.
Because IEC 61850 edition 1 and IEC 61850 edition 2 templates are incompatible, convert
an IEC 61850 edition 1 template to IEC 61850 edition 2 before you insert it.
It is possible to give the inserted IED in the plant structure a user-defined name. Be sure to
only user characters a-z, A-Z, 0-9 and _. Do not use space character in IED names.
There are two alternatives to set the IP address of the IED object in PCM600. The IED object in
PCM600 must have the same IP address and subnetwork mask as the front or rear port on the physical
IED to which the PC is connected.
• Via the first window of the wizard when including a new IED in a project, see Figure 27.
670 series 53
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 4 1MRK511398-UEN Rev. N
Setting up a project
IEC09000713-2-en.vsd
IEC09000713 V2 EN-US
• Via the IP address property of the IED in the Object Properties window, see Figure 28.
IEC08000121-4-en.vsdx
IEC08000121 V4 EN-US
Figure 28: Alternative 2: IP address via the IED Object Properties window
Procedure
54 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 4
Setting up a project
The used alternative depends on the time at which the IP address is available.
670 series 55
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
56
1MRK511398-UEN Rev. N Section 5
Ethernet configuration tool
The Ethernet configuration tool (ECT) is a configuration tool that provides the possibility to configure
Access points, Merging units and Routes in a single place. The tool increases security and easy of
use as it offers an overview of all configurations related to Ethernet communication, such as operation,
IP addresses, redundant communications and which protocols allowed to run on the individual access
points.
ECT validates the values entered for the IP-adress and the default gateway in the Access point-tab as
well as the settings in the Merging unit-tab. For more information refer to the Application manual.
Access points
The Ethernet configuration tool consists of one tab for access point, one for merging unit and one for
routing. The changes done during the session will be bolded until the tool is closed.
The protocols cannot be activated or deactivated from ECT, the tool only controls which
protocols are allowed to run on the access point. For information on how to activate or
deactivate the communication protocols, see the communication protocol manuals or cyber
security deployment guideline.
To configure the access points and merging units in offline mode, first hardware configuration should be
selected in Hardware Configuration Tool (HWT). In online mode all available access points and merging
units will appear in ECT.
IEC16000089-1-en.vsdx
IEC16000089 V1 EN-US
This tab allows configuration of the access points, model access points in SCL, filter the protocols to be
sent over each access point, and configure time synchronization for each access points. Each row in this
tab corresponds to an access point. Access point 1 is the default access point and will be included in the
SCL model by default. Changing settings in this tab will have impact on the SCL model.
The PTP VLAN tag is only valid for PTP time synchronization and it must have the same value in station
clock and in the IED. The default value is set to 0.
Columns in this tab will vary based on IED capability and order-specification.
670 series 57
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 5 1MRK511398-UEN Rev. N
Ethernet configuration tool
Physical port A Shows the physical port associated with the access point. Yes
Physical port B Shows the redundant physical port associated with the access point when PRP or Yes
HSR is activated.
Subnetwork Shows the SCL subnetwork to which the access point is connected, can be changed. No
This column shows the SCL subnetworks available in the PCM600 project. SCL
subnetworks can be created/deleted in Subnetworks tab of IEC 61850 Configuration
tool in PCM600.
58 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 5
Ethernet configuration tool
The columns that are updated during a partial write are highlighted when holding the pointer
over the partial write button. The highlighted columns will be written to the IED but not
synchronized towards SCL.
Changing an IED’s IEC 61850 configuration from IEC 61850 edition 2 to IEC 61850 edition 1
will remove the Access points that are modelled in SCL except the default Access point and
also if the redundancy is modelled then it will also be removed.
Merging units
IEC16000090-1-en.vsdx
IEC16000090 V1 EN-US
Access points should be configured before configuring merging units. This tab allows configuring of the
reception of data from merging units. Each row in this tab corresponds to a merging unit. Changing
settings in this tab will not have any impact on the SCL model. The IED can be configured to receive IEC
61850–9–2E sample value streams from merging units.
Migration of merging unit configuration from 670 2.0/2.1 to 2.2 series is not supported. From
670 2.2 series onwards, merging unit modules can be created/deleted from the merging unit
tab of ECT, not from HWT.
670 series 59
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 5 1MRK511398-UEN Rev. N
Ethernet configuration tool
The combination of associating merging units to access points mentioned below is invalid.
For Merging units 9201 to 9208, if any five of the merging units are associated to one access
point and the remaining merging units are assigned to different access points it will become
an invalid configuration.
IEC16000191-1-en.vsdx
IEC16000191 V1 EN-US
There should be one instance of LSVS in an IED for each sampled value data stream that the IED
receives. Each LSVS reports the status of one receiving sampled value data stream.
60 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 5
Ethernet configuration tool
The attributes St and SimSt are supported as well as the setting SvCBRef, according to IEC 61850-7-4
Ed. 2.0.
LSVS is not defined in IEC 61850 Ed. 1 and is only supported in Ed. 2 mode.
The configuration of LSVS is done automatically when the receiving of sampled data is defined in the
IED.
This configuration is done in ECT and there it is a column to fill in the SvCBRef. This field is used
to identify the sampled value stream that is supervised and should, according to IEC 61850, be set
to the IED and control block name of the sending IED. However, this is not used to configure the
communication and can be set to any string. The string is limited to 39 characters and to a character
string without tabs, line feeds and carriage return, restricted to 8-bit characters (UTF-8 single byte
coding,ISO/IEC 8859-1).
The identification of LSVS supervised sampled value data stream is done with the SvCBRef setting and not the instance
number of the LSVS instances.
Routes
IEC16000091-1-en.vsdx
IEC16000091 V1 EN-US
This tab allows configuration of the routing of data packets. Each row in this tab corresponds to a Route.
Changing settings in this tab will not have any impact on the SCL model.
670 series 61
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 5 1MRK511398-UEN Rev. N
Ethernet configuration tool
The tool can be started the from the IED level in the Plant Structure window in PCM600.
IEC16000094-1-en.vsdx
IEC16000094 V1 EN-US
62 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
ACT is used to create the application configuration for an IED. The application configuration is built up
with function blocks.
For detailed information about function blocks see the technical manual and the application
manual.
Some function blocks are mapped as logical nodes according to the IEC 61850 standard. Other function
blocks are not mapped as logical nodes, for example:
• Logical gates
• Timers
670 series 63
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
1
Application
function
2
Application
function
LN
Application
function
LN
GUID-CF053FE9-0BA6-448A-A1D9-9697027ECCBC V2 EN-US
Figure 33: Examples of function blocks with and without monitoring and commands
SMT is not supporting signals of integer type or group signals. So, even if these types of
signals are set as visible for SMT, they will not be shown in SMT.
64 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
For instructions on how to perform the different tasks in PCM600, see PCM600 online help.
• Function blocks are the main elements of an application configuration. They are designed for a various
number of functions and organized in type groups. The different function block types are shown in the
Object Types View. Figure 34 presents an overview of the main parts that are relevant for function
blocks.
• Set user defined names for function blocks and signals marked with blue text.
Signals that have a user defined name created in ACT, will only be visible in PST if the IED
configuration is written to the IED and read back to PCM600. Otherwise the default signal name
is shown in PST.
Do not use other characters than a-z, A-Z, 0-9 and _ when setting user defined names for
signals and function blocks, since other characters might not display properly in local HMI. Also
avoid using space character.
The maximum user defined name length or size is 16 characters or 39 bytes and the user
defined name will be truncated to the corresponding limit if any of the limit gets exceeded.
In all other 670 products, LDCM is preferably intended to be used in binary mode. However,
in case the LDCM module is used in the analog mode, then the only available pre-processing
SMAI blocks will be either in 3ms or 8ms cycle. Connecting the remote currents to either
of these two types of SMAI blocks might impact the performance of protection functions.
Namely, all functions that are running in the same cycle as the used processing SMAI block
for the remote currents may experience extra time delays in the operation due to the impact
of LDCM buffering and transmission delays. Thus, the application of LDCM in analog mode
in other products than RED670 shall be used with caution.
670 series 65
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
1 2 3 4 5 6 7 8 9
13 14 15 16 17
10 11 12 IEC08000258.vsd
IEC08000258 V1 EN-US
1 Connection(s)
2 User defined function block name
3 Function block, selected (red)
4 Mandatory signal (indicated by a red triangle if not connected)
5 Function block name
6 Function block, locked (red)
7 ANSI symbol
8 Inverted output
9 Hardware, binary output channel
10 Hardware, analog input channel
11 User defined signal name
12 Hardware, binary input channel
13 Execution order
14 Cycle time
15 Instance number
16 Inverted input
17 Signal description note
A function block can contain more signals than needed in that application part. A signal that is not used
in a particular application is possible to hide in the function block view in ACT. It is not necessary to
connect all inputs and outputs at a function block. If not connected, the signals always have a default
value. The default value can be seen when hove over the signal with the mouse.
Signals are located on both sides of the middle position up and down. When there is space left, move
some signals up or down for a better visibility and connection routing.
66 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
Boolean input and output signals may need to be inverted to fulfill the logic. ACT supports to add the
inversion logic to a binary signal.
The input signal on glue logic function blocks can only be inverted if a glue logic function
block with lower execution order in the same cycle time is available. Similar, the output signal
can only be inverted if a glue logic function block with higher execution order in the same
cycle time is available. Up to two input signals and two output signals can be inverted for
glue logic blocks in the same cycle time.
Even though current is injected to the IED and the IED is connected to PCM600 in online
mode, the signal value in ACT is shown as zero.
All non-mandatory input signals have a default value that will be used when not connected.
Functions can be blocked by loss of analog data, for example if a IEC/UCA 61850-9-2LE source
malfunctions. Figure 35 shows an example where MU1 malfunctions, and all function blocks connected
to that 3-phase group get blocked as a result, this is also known as conditional blocking functionality.
F1
MU1 SMAI1
F2
MU2 SMAI2
F3
TRM SMAI3 F4
Lost data
Blocked function
IEC16000049-2-en.vsdx
IEC16000049 V2 EN-US
Three function block execution parameters have influence on the runtime execution of the function block
within the application configuration.
670 series 67
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
• Execution Order
• Cycle Time
• Instance Number
Each time a new function block is selected, one or more of these parameters become available for
selection from the drop down lists in ACT depending on the function block type. The Cycle Time may be
predefined to one value with certain functions. The Instance Number is a counter for the total possible
number of function blocks of that type used within an application configuration.
Execution Order and Instance Number are given in the list as a selectable pair predefined within a
product.Figure 36 shows an example how the drop down list could look like.
IEC09000720 V3 EN-US
A minus sign in front of the cycle time, for example -200ms, indicates that the application is
time driven, otherwise the application is analog data driven. Analog data driven applications
require sample values from Analog input modules - in case the physical module is broken,
applications are not executed. Time driven applications are executed periodically regardless
of the status of the analog signal processing.
The Cycle Time can be selected to different values for certain functions. Depending on the function
block and IED type, one or more possibilities may be available.
The combination Execution Order, Instance Number is predefined by Hitachi Energy. Mainly for basic
logic function blocks like for example AND, OR, a set of combinations spread over the full range of
execution orders is available. This gives the possibility to select a combination which fits to the execution
order range needed in that application part.
68 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
IEC09000737 V1 EN-US
For the same time point, faster cycle times are executed first.
A function block that is placed after a function block in the execution flow must have the
same or a higher cycle time and/or execution order. See Figure 38.
IEC09000615-2-en.vsd
IEC09000615 V2 EN-US
A function block type can be defined to be a member of one or several cycle times. A function block
instance can be set only to one cycle time.
670 series 69
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
Execution Flow
In the conceptual MainApplication example in Figure 39, the execution order of the main function block
in the execution order group 2 defines the execution orders needed in group 1 and 3. The preceding
logic done with function blocks in group 1 must have a lower execution order than the ones in group 2.
The following function blocks in group 3 must have a higher execution order than the main function block
in group 2.
A connection is the link or "wire" between function block outputs and inputs.
Connection validation
A connection is only useful and possible between two signals of the same data type, see Figure 40.
70 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
IEC08000304-2-en.vsd
IEC08000304 V2 EN-US
Hardware channels can only be connected to a function block input or output. A hardware connection
can be established in ACT or SMT. When a hardware channel is connected a graphical symbol appears
in ACT, see Figure 41. The connection is also represented in SMT with a cross mark. Hardware
channels are always visible in SMT.
A hardware input channel can be used as often as it is needed. A hardware binary output channel is
taken from the list of available channels when a new channel is requested. That prevents for using a
hardware binary output channel twice. As an example, see Figure 41.
670 series 71
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
IEC09000723 V4 EN-US
Validation checks the application configuration on errors about the rules and restrictions defined for
doing a MainApplication on three levels.
• During creating the logic while doing a connection or placing a function block.
• On demand by starting the validation.
• When writing the application configuration into the IED.
72 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
• A connection between two input signals or two output signals is not possible.
• A connection between two different data types is not possible, for example a binary output to an
analog input.
Validation on demand
To check the validity of an application configuration, click the 'Validate Configuration' icon in the toolbar.
ACT will check the application configuration for formal correctness. Found problems are qualified in:
These warnings can be accepted to avoid checking the warnings every time the application
is validated.
Warnings will not prevent writing to the IED. Errors have to be corrected before writing the application
configuration to the IED. An application configuration can be saved and ACT can be closed with open
errors, but not written to the IED, see Figure 42.
These problems are listed in the Output View under the Tab Application Configuration. A double-click
in the error or warning row will navigate to the MainApplication>Page>Area where the problems are
identified.
IEC09000614-3-en.vsd
IEC09000614 V3 EN-US
670 series 73
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
Configuration parameters and settings parameters are changeable either from LHMI or from PST in
PCM600.
Note that the some parameters are only visible in PST and some are only visible on LHMI.
A write from PCM600 to the IED, where parameters are changed in PST, will overwrite any
parameter changes made locally from LHMI unless a read from the IED was performed prior
to changing any parameters in PCM600.
To export parameters from PST, both XRIO and CSV formats are supported.
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.
Setting parameter
A setting parameter (short form only “setting”) is a parameter that take immediate effect when changed.
Setting group
Up to six setting groups can be configured with different values. The IED supports the selection of a
setting group at runtime.
During a write both the basic and advanced settings are written to the IED.
The Graphical Parameter Setting tool (GPST) is a tool in PCM600 that is used to present parameter
settings in a graphical user interface. GPST is a part of the Parameter Setting tool (PST), the settings
are done in PST and can be presented in GPST.
74 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
For more information on GPST, see the online help for PCM600.
670 series 75
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
Binary
BIM
Input
IOM BI FBs
HMI
LEDs
LEDs
FBs
BOM
Binary
Output IOM BO
Analog
TRM SMAI
Input
A binary input channel can be connected to one or several function block inputs, see Figure 44. If
several binary inputs are connected to the same function block in SMT, the connection will appear as
glue logic in SMT and ACT, see Figure 45.
76 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 6
Protection and control engineering
IEC09000721-2-en.vsdx
IEC09000721 V2 EN-US
Figure 44: SMT Connection between binary input channels to binary input signals
IEC17000045-1-en.vsdx
IEC17000045 V1 EN-US
A function block output can be connected to one or several binary output channels, see Figure 46. A
binary output channel can only be activated from one function block output, if it should be activated from
more than one function block output, glue logic has to be used. Glue logic means inserting a logical
gate (OR and AND blocks) between the function blocks and the binary output channel. This can be
engineered in SMT.
670 series 77
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 6 1MRK511398-UEN Rev. N
Protection and control engineering
IEC17000046-1-en.vsdx
IEC17000046 V1 EN-US
Connections made in SMT are automatically shown in ACT and vice versa.
It is possible to group and collapse hardware channels in SMT to get a better overview.
Depending on the IED capability, SMT has a separate sheet for each possible combination.
• Binary Inputs
• Binary Outputs
• Analog Inputs
• GOOSE Receive
78 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
Figure 47 shows the different steps of the engineering process of the local HMI (LHMI) and their relative
order.
Local HMI
ACT / SMT
Select and configure
HMI function blocks
SAVE
PST
Set function
keys and LEDs
SAVE
GDE / ACT
Create the
single line diagram
SAVE
END
IEC09000622_1_en.vsd
IEC09000622 V1 EN-US
670 series 79
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
• The operation mode of the function keys and LEDs is defined in the Parameter Setting tool.
• The presented text labels on the LCD for LHMI keys and LEDs.
• Graphical Display Editor with assistance of the Application Configuration tool, for example
• to make the single line diagram of the primary process part.
• to make the dynamic links for the apparatus.
• to make the dynamic links for measurements.
The LHMI provides a set of special function blocks to be utilized in the Application Configuration tool:
• LHMICTRL
• FNKEYMD1 to FNKEYMD5
• LEDGEN
• GRP1_LED1 to GRP1_LED15
• GRP2_LED1 to GRP2_LED15
• GRP3_LED1 to GRP3_LED15
The function blocks for the LEDs are organized in function blocks per LED. They can be placed close to
the logic where the information per LED is built in the Application Configuration tool.
Figure 48 describes the basic LHMI and the operation element groups. These are the 15 LEDs and their
belonging text elements on the LCD [A]. They are operated by keys [a] and [b].
The other group is the five function keys with their LEDs and the corresponding text elements on the
LCD [B].
80 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
GUID-A374CBAE-CFB8-47CE-A2AD-514F8B6F20CA V3 EN-US
• The 15 LEDs on the right side of the LCD can indicate in total 45 alarms, warnings or other signals to
the operator. They are organized in three groups 1 to 3.
• Each signal group belongs to one function block.
• Each LED illuminates in one of the three colors: RED, YELLOW or GREEN.
• The organization of flashing, acknowledgment and group selection is done directly between the
function blocks and the basic LHMI keys, the 'Multifunction' key [a] to toggle between the three groups
or the 'Clear' key [b] to acknowledge or reset the LEDs.
• Only the programming of the signals is needed for the LEDs.
• The operation mode of the LEDs is defined in the Parameter Setting tool.
670 series 81
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
• Pulsed signal
• Each push forces a pulse of a configured time.
• The pulse time can be set in the Parameter Setting tool.
• The default pulse time is 200 ms.
• Toggle signal
• Each push changes the state of the signal: OFF-ON-OFF-ON-OFF...
• The default position after power up or reset is OFF.
• Menu shortcut
• When pressing a key configured for that purpose, the function key panel is hidden and the LHMI
opens directly in the configured menu.
IEC09000656 V2 EN-US
The LEDs have a number of different operation modes, see Figure 50:
• General definitions
82 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
• Each LED can illuminate in one of three colors: RED, YELLOW, GREEN.
• Only one color is illuminated at a time.
• The priority for illumination and the color is linked.
• Prio 1 = RED
• Prio 2 = YELLOW
• Prio 3 = GREEN
• When RED and YELLOW are ON at the same time, the LED will illuminate in RED.
• The operator's acknowledgement for the LED signals is done for all three signals (RED, YELLOW,
GREEN) of the LED.
• A reset of the LEDs operates also on all three signals of the LEDs.
• Follow-S
• The LED illumination follows the status of the signal. The LED illuminates steady (S).
• Follow-F
• The LED illumination follows the status of the signal. The LED illuminates flashing (F).
• LatchedAck-F-S
• The LED latches the signal change OFF-ON and flashes (F) until it is acknowledged.
• When the signal is still ON at the time the signal is acknowledged, the LED changes to steady (S)
mode.
• When the signal has already changed to OFF before the time it is acknowledged, the LED turns to
OFF.
• LatchedAck-S-F
• The same as LatchedAck-F-S but the LED starts with steady state and flashes after
acknowledgment.
• LatchedColl-S
• The LED illuminates in all cases in steady mode only
• The LED latches a signal change from OFF-ON until it is acknowledged by the operator.
• The LED stays in steady mode when it is reset and the signal is still in ON state.
• The LED is OFF only after the signal has changed to OFF state AND it is reset by the operator via
'Clear' operation.
• LatchedReset-S
• This mode is used for all LEDs that are used to indicate a disturbance. The LEDs will stay in the last
state after the disturbance run time until they are reset after a defined time.
• The timers are set in the Parameter Setting tool in the function block LEDGEN.
670 series 83
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
IEC09000657 V2 EN-US
The SequenceType parameter enables each LED to operate in one out of six different modes.
• Follow-S
• Follow-F
• LatchedAck-F-S
• LatchedAck-S-F
• LatchedColl-S
• LatchedReset-S
IEC08000395 V2 EN-US
In the Follow-S mode, the LED adopts a steady behavior. It is lit on a binary On signal and switched off
on a binary Off signal. See Figure 51 for details.
84 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
IEC08000396 V2 EN-US
In the Follow-F mode, the LED starts flashing when receiving a steady binary On signal. At other times it
is unlit. See Figure 52. This mode may be used to indicate that a tap changer or Petersen coil is moving.
IEC08000397 V2 EN-US
The LatchedAck-F-S mode is used to indicate unconfirmed alarms or warnings. On a binary On signal
(steady or pulse), the LED enters a flashing state. If acknowledged and if the signal is still On, the LED
transitions into a steady state. If the signal at this point is Off, the LED is switched off (for this color). See
Figure 53 for details.
670 series 85
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
IEC08000398 V2 EN-US
Each LED has one binary input for each of the colors: red, yellow and green representing high, medium
and low priority respectively. Each priority also applies to the presentation of the state (acknowledged
or unacknowledged) of each color. Excluding Off signals, the presentation of a state of higher priority
always overrides the presentation of any state of lower priority.
IEC08000399 V2 EN-US
86 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
IEC08000402 V2 EN-US
A LED operating in the LatchedColl-S mode enters a steady lit state on receiving a binary On signal. The
LED remains lit even if the signal immediately transitions to Off (pulse). When acknowledged, the LED is
switched off, unless the attached signal remains On. See Figure 56 for details.
IEC08000400 V2 EN-US
The LatchedReset-S mode is designed for multi-signal disturbance monitoring. For this reason, the
General LED indication function block (LEDGEN) has two parameters: tRestart and tMax. Both are
timers used to determine the end of a disturbance window.
670 series 87
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
A disturbance window starts when a LED receives a binary On signal. The LED then enters a steady
lit state. At the point where all signals, related to the LEDs in this particular mode, are Off, the timer
tRestart is triggered. This timer is common for all LEDs and when it elapses, the disturbance window
ends.
The second timer, tMax, starts whenever a LED is lit. If there are no activities until tMax elapses,
tRestart is triggered. This means that the disturbance window eventually ends even if a signal remains
On for a long time. See Figure 57.
IEC08000401 V2 EN-US
Phase angles are shown in radians in the single line diagram view, but in degrees in other
views on the LHMI.
88 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
IEC08000123-3-en.vsd
IEC08000123 V3 EN-US
Procedure
It is important to link correctly between the HMI display page and the corresponding bay that
is presented as a single line diagram on this HMI page.
Object types
The Graphical Display Editor window contains some panes that include drawing symbols or elements to
create a single line diagram, measurements and texts on a page. Click on the name bar of the selected
element to open the pane.
670 series 89
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
The object types shows the symbols either in ANSI standard or in IEC standard. The standard is
selected by the drop down list box located on top of the display window.
When changing to the other symbol standard, GDE closes the object type window, changes the symbols
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 that explains itself when selected. Select the
format and drop it in the drawing area. Use the object properties to make adaptations.
• Dynamic Text or Indication button is used when a position shall be monitored on single line diagram,
Figure 60
• Select Button is used when the functions shall be manoeuvred from a single line diagram.
IEC08000127-2-en.vsdx
IEC08000127 V2 EN-US
The standard (IEC or ANSI) for the symbols and the selection of the font size for the text elements can
be changed using the icons and drop down on top of the page window.
The total size of the presented white area (page) represents the visible part of the local HMI display
without header and foot-line.
The visible display for a single line diagram is organized in a raster of 13 x 8 (columns x rows). Each
symbol presented by 24 x 24 pixels included by the drag and drop method must be dropped in a raster
box. The apparatus object name can be placed in all four directions around the symbol. The name is
part of the apparatus object.
90 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
Handling text
The raster switches when text is selected in a raster of 45 x 15 (columns x rows). One raster box is the
placeholder for one character. A text element must be placed in the position of the raster. The signal
name can changed either by double click or via the property window. Unit and scaling of the signal can
only be changed via the property window.
Select and toggle Show Texts using the IED Fonts to get a view how it will look like later on the real HMI
display.
For the procedure to draw lines when the apparatus symbols are placed, see Figure 61.
1. Place the apparatus or transformer symbols by drag and drop in a raster box.
2. Place the connections symbols by drag and drop in a raster box.
3. Center the mouse pointer on the center of a connection point; visible in two triangles if not
connetions are made, otherwise two circles at the endpoints of a line, to draw a line.
4. Click to start and move the mouse pointer to the destination connection point. Center once again the
mouse pointer and click to drop the line.
5. Draw all line elements that are necessary.
IEC05000598-4-en.vsdx
IEC05000598 V4 EN-US
670 series 91
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
Category IEC Symbol Name IEC Symbol ANSI Y32.2/IEEE Function Block
Definitions 315 Symbol Type
Definitions
Connections Junction
Connections Earth
92 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
Category IEC Symbol Name IEC Symbol ANSI Y32.2/IEEE Function Block
Definitions 315 Symbol Type
Definitions
Others Reactor
Others Motor
Others Generator
Others Coil
Others Fuse
Others Resistor
Others Fieldwinding
Others Rectifier
Power Autotransformer
transformers
Isolator, 10 = Closed
Isolator, 11 = Undefined
670 series 93
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
Category IEC Symbol Name IEC Symbol ANSI Y32.2/IEEE Function Block
Definitions 315 Symbol Type
Definitions
Switchgear Isolator motor-operated, 00 = Middle SCSWI,
position VSGAPC
Isolator motor-operated, 01 = Open
Breaker, 10 = Closed
Breaker, 11 = Undefined
Isolator2, 10 = Closed
Isolator2, 11 = Undefined
94 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
Category IEC Symbol Name IEC Symbol ANSI Y32.2/IEEE Function Block
Definitions 315 Symbol Type
Definitions
Switchgear Isolator2 indication only, 00 = Middle SCSWI, SXSWI,
position DPGAPC,
VSGAPC
Breaker2, 10 = Closed
Breaker2, 11 = Undefined
670 series 95
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
Category IEC Symbol Name IEC Symbol ANSI Y32.2/IEEE Function Block
Definitions 315 Symbol Type
Definitions
Texts Select button, 00 = Middle position VSGAPC
A page with a single line diagram and measurements contains active living objects. The object values
are updated by the IED periodically (measurement) or in case of an event. Once the symbols are placed
on the HMI page they must be linked to the corresponding function block in the application configuration,
which protects or controls the object that the symbol on the HMI page represents.
96 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
IEC09000666-3-en.vsd
IEC09000666 V3 EN-US
• ACT to program the application function block for apparatus and/or measurements.
• PST to adapt the settings and/or configuration parameter of the application function 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:
Procedure
1. Right-click the apparatus symbol and select Select Input Signal. A list of engineered switch control
application function blocks opens, see Figure 63.
2. Select the switch control application function block that corresponds to the selected apparatus.
3. Right-click the measurement symbol and select Select Input Signal. A list of the engineered
measurement application function blocks opens.
4. Select the measurement application function block that corresponds to the selected symbol.
670 series 97
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
Section 7 1MRK511398-UEN Rev. N
Local HMI engineering
IEC08000125-2-en.vsd
IEC08000125 V2 EN-US
The number of order in the selection window of the process objects corresponds to the number given in
the PST tree and to the application function block in ACT.
Only those apparatus and measurements are shown that are configured in the application configuration
program.
98 670 series
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
1MRK511398-UEN Rev. N Section 7
Local HMI engineering
IEC05000611-2-en.vsdx
IEC05000611 V2 EN-US
The single line diagram screen can display different values, with the help of the dynamic text
fields. Please remember that these values are displayed by default in SI units (for example -
active power is displayed in W). Modify the Scale Factor in the object properties (see Figure
65) to display values in more readable units (for example MW). Be sure to write the proper
unit under the Unit Text field.
As the function delivers angles in radians, a scale factor of 180/pi = 57.3 shall be used to
display the angle in degrees
IEC10000174.vsd
IEC10000174 V1 EN-US
To get IED events to the LHMI event list and indications for Ready, Start and Trip indication LEDs,
disturbance report needs to be engineered.
Detailed information about disturbance report subfunctions is found in the technical manual.
670 series 99
Engineering manual
© 2017 - 2024 Hitachi Energy. All rights reserved
100
1MRK511398-UEN Rev. N Section 8
IEC 61850 communication engineering
For more information on the implementation of IEC 61850 standards in IEDs, see the IEC
61850 communication protocol manual.
The IED function blocks have a design based on the demands and advantages of the IEC 61850
standard. This means that there is a strict relation between the function blocks and the logical node
types. This relation is automatically handled by the PCM600 tools.
The concept in IED is such that the 61850 data for each function instantiated in ACT will be
automatically created. This means that the user does not need to handle any instance information for the
functions regarding IEC 61850.
An access point is an Ethernet communication interface for single or redundant station communication.
Each access point is allocated with one physical Ethernet port, two physical Ethernet ports (marked A
and B) are allocated if redundant communication is activated for the access point.
Device 1 Device 1
IEC16000092-2-en.vsdx
IEC16000092 V2 EN-US
Figure 66: Access points, non redundant (left) and redundant communication (right)
GUID-E630C16F-EDB8-40AE-A8A2-94189982D15F v1
The IEC/UCA 61850-9-2LE process bus communication protocol enables an IED to communicate with
devices providing measured values in digital format, commonly known as Merging Units (MU). The rear
access points are used for the communication.
The merging units (MU) are called so because they can gather analog values from one or more
measuring transformers, sample the data and send the data over process bus to other clients (or
subscribers) in the system. Some merging units are able to get data from classical measuring
transformers, others from non-conventional measuring transducers and yet others can pick up data
from both types.
When configuring RER670 for 9-2LE streams in a 16.7Hz system, the IED shall be set to
16.7Hz and the MU to 50Hz (4kHz sampling).
See Figure 67 for a principle view of the IEC 61850 logical node concept in the IED.
FBs
FBs
GOOSE interf.
GOOSE GOOSE
GOOSE
Receive Receive
LN Receive
LN
GOOSE
GOOSE
Send GOOSE
Send Send
FB
FBs application
with function
monitoring
Communication handler
Command / IN / OUT interface AF part
only LN
FB
application
function
FBs
LN
with Event
part
monitoring
handler
and
commands
FB
application
function Event
queue
LN
part
IEC08000364-2-en.vsd
IEC08000364 V2 EN-US
IEC 61850 has as a concept for the identification of all signals for communication that belong to a
function by a logical node as a placeholder. All signal information in command and monitoring direction,
which belongs to a function, is available within the logical node.
Whenever a function block is instantiated in ACT, PCM600 automatically generates the corresponding
logical node data. In Figure 67 this is shown by two parts per function block. The upper part is the visible
function block in ACTApplication Configuration tool and the lower part is the logical node data for the
function block.
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
The IEC 61850 protocol supports a method to directly exchange data between two or more IEDs. This
method is described in the IEC 61850–7–2 clause 15. The concept is based on sending a multicast 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 multicast sent and not acknowledged by the receiver.
Receive
Receive
Receive
Receive
Receive
Send
Send
Send
LN LN LN
LN LN
LN
LN LN LN
LN
LN LN LN LN LN
Figure 69 shows an example with three IEDs where each one communicates with all the others.
When a GOOSE message is to be sent is defined by configuring the data set with the defined trigger
option and the GOOSE control block (GoCB). This engineering process is done in the IET600 station
configuration tool. The task involves configuring lists with the signal, value and quality (data attributes)
that 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 must be defined in the IED application configuration. The SCD file
generated by the IET600 (or any other station configuration tool) contains these GOOSE data sets as
input data. The input data must be connected to a GOOSE receive function block (GOOSEBINRCV) in
SMT.
If the quality and time of the value is needed in the receiver IED, the quality and time must be included in
the GOOSE data set. The receiver side will connect this automatically and if the quality and time is not in
the data set, a warning message will occur in PCM.
The IEC 61850 standard defines SCL-file types in the sequence of engineering. These files have
a different definition, which is explained in IEC 61850–6. Three of these file types are used in the
engineering process for an IED.
To engineer the IEC 61850 protocol interface for the IED, the following additional manuals or knowledge
of their contents is required.
• Knowledge of the IEC 61850 engineering process as described in the IEC 61850 standard.
• The IEC 61850 conformance documents for the IED to be engineered.
• The Technical reference manual describes function blocks defined as logical nodes.
• IEC 61850 Data objects list for the IED.
The IEC 61850 standard defines the complete part needed for information communication in a
substation. This can be split into the following parts:
For more details please refer to the IEC 61850 standards. In the following description it is assumed that
PCM600 together with Integrated Engineering Tool (IET600) is used as system configuration tool.
A short form of a typical sequence is shown in Figure 70 when a complete station is exported as a SCD
file.
1. Export SCL files from PCM600. In the scenario in Figure 70 it is a SCD file. Other SCL file types are
possible to export.
2. Configure horizontal and vertical communication in the IET600 station configuration tool.
3. Import SCL files to PCM600 project. In the scenario in Figure 70 it is the updated SCD file.
IET600 2
create project
import SCD file
SCD file configure data sets SCD file
configure Report CBs
configure GOOSE CBs
export SCD file
PCM600 1 PCM600 3
IEC11000264-3-en.vsdx
IEC11000264 V3 EN-US
The pre-condition for exporting SCL files from PCM600 is that all IEDs included in the project are
configured. The hardware interface, for example the IP address, must be selected and configured.
Station communication has to be activated in the IED, that is, the IEC 61850-8-1 setting Operation must
be set to On.
IEC08000415 V3 EN-US
IEC09000627 V3 EN-US
5. Select the data to be exported and the version of the IEC 61850 standard.
Procedure for selecting the export type when an IED is selected in the plant structure:
1. Right-click on the IED in the plant structure and select Export to open the Export window.
2. Select the type of file to export from the Save as type drop down list (see Figure 73):
• Configured IED Description (*.cid) for the IEC 61850 structure as needed for the IED at runtime.
• IED Capability Description (*.icd) for the IEC 61850 structure.
IEC08000416-3-en.vsdx
IEC08000416 V3 EN-US
IEC08000418 V3 EN-US
Easy GOOSE engineering enables configuration of GOOSE communication between two or more IEDs
in a single tool, the application configuration tool (ACT). GOOSE datasets and GOOSE control blocks
are created automatically when the configuration is done in ACT. Easy GOOSE engineering does not
replace GOOSE engineering in the Signal Matrix Tool (SMT) or the IEC 61850 Engineering tool.
Easy GOOSE Engineering is supported for both IEC 61850 Edition 1 and IEC 61850 Edition 2
configured IEDs.
2 3
4
1
IEC16000171-1-en.vsd
IEC16000171 V1 EN-US
The Select sender IEDs list displays all IEDs in the PCM600 plant structure. The following IEDs will be
grayed out in the list:
The Recently Used IEDs list displays the last three GOOSE subscribed IEDs in the PCM600 plant
structure.
Sender IEDs
The Sender IEDs list displays all selected sender IEDs compatible data attributes that can be received
for the selected receiving signal.
• Application Configuration: Application configuration tab displays all selected sender IEDs data
attributes for signals that are visible in Application Configuration.
IEC16000172-1-en.vsd
IEC16000172 V1 EN-US
• SCL Configuration: SCL Configuration tab displays all selected sender IEDs IEC 61850 data
attributes for signals that are not visible in Application Configuration.
IEC16000173-1-en.vsd
IEC16000173 V1 EN-US
Figure 77: ACT: SCL Configuration tab in Connect to GOOSE dialog window
Search
In the Application Configuration tab, the Main Application, function block, signal, data attribute and IED
name is considered in the filtering.
In the SCL Configuration tab, the logical device, logical node, data object and data attribute is
considered in the filtering.
Extended Mode
Extended Mode is used to create multiple GOOSE connections without selecting an input signal in
Application Configuration. For detailed information about Extended Mode functionality, see Section
"Connect to GOOSE dialog window user interface – Extended Mode".
IEC16000168-1-en.vsdx
IEC16000168 V1 EN-US
The GOOSE Receive Blocks In Configuration displays list of compatible GOOSE Receive function
blocks which are already in the configuration.
The New GOOSE Receive Blocks displays list of compatible GOOSE Receive function blocks and
corresponding GOOSE input signals which can be added to the configuration.
Search
Extended mode
In the “Connect to GOOSE” dialog window, Extended Mode is selected to create multiple GOOSE
connections directly without selecting an input signal in the Application Configuration.
3
1 2
IEC16000190 V2 EN-US
Figure 79: ACT: Connect to GOOSE dialog window with Extended Mode
Receiver IED
Receiver IED list displays the Receiver IED Main Application, function block and signal data. Connection
can be made at signal level and one connection per signal.
Search
Main Application name, function block name and signal name are considered as filtering.
IEC16000099-1-en.vsdx
IEC16000099 V1 EN-US
The “IEC 61850 configuration engineering mode enabled” option under Tools /Options /
IEC 61850 Configuration /Enginneering tab has to be checked to get the option above
enabled.
1. Select and right click on the input signal of the GOOSE Receive function, point to “Connect” and
select the “GOOSE” option.
IEC16000170-1-en.vsd
IEC16000170 V1 EN-US
The “Connect to GOOSE dialog” window opens, for detailed information on the “Connect to GOOSE
dialog” window refer to Section "User interface".
2. Under Select sender IEDs section, check sender IEDs that can be received on receiver signal.
3. Under Sender IEDs section, select needed data attribute in Application configuration tab (see Figure
76) and click on the “Connect” button.
GOOSE connection will be added as shown in the Figure 82 below.
IEC16000174-1-en.vsd
IEC16000174 V1 EN-US
Figure 82: ACT: GOOSE configuration on Receiver IED (left) and Sender IED (right) side
4. If SCL configuration data attributes needs to be connected , the needed data attribute shall be
selected in the SCL configuration tab (see Figure 77). Click on the “Connect” button.
For more information on SCL configuration data attributes, see Section "User interface".
In this case, the GOOSE connection will be added as shown in Figure 83 below.
IEC16000175-1-en.vsdx
IEC16000175 V1 EN-US
Figure 83: ACT: GOOSE configuration on Receiver IED side (left) and Sender IED (right) side
1. Select and right click on the input signal of a normal function block, point to “Connect” and select the
“GOOSE” option.
IEC16000176-1-en.vsd
IEC16000176 V1 EN-US
The “Connect to GOOSE” dialog window opens. For detailed information about the “Connect to
GOOSE” dialog window refer to Section "User interface".
2. Under Sender IEDs section, select needed data attribute in the Application configuration tab
3. Click on the “Connect” button.
The “Select GOOSE Block and Signal” dialog window opens. For detailed information about the
“Select GOOSE Block and Signal” dialog refer to Section "User interface".
4. In the “Select GOOSE Block and Signal” dialog window, select needed GOOSE Input signal from
either “GOOSE Receive Blocks In Configuration” or “New GOOSE Receive Blocks” section.
For more information on the GOOSE Receive blocks, see Section "User interface"
5. Click on the “Connect” button, the GOOSE connection will be added to the configuration as shown in
Figure 85 below.
IEC16000177-1-en.vsd
IEC16000177 V1 EN-US
Figure 85: ACT: GOOSE configuration on Receiver IED (left) and Sender IED (right) side
6. If SCL configuration data attributes needs to be connected the needed data attributes needs to be
selected in the SCL configuration tab (See Figure 77).
6.1. Click on the “Connect” button.
6.2. Select the needed GOOSE input signal in the “Select GOOSE Block and Signal” dialog
window.
6.3. Click on the Connect button.
IEC16000178-1-en.vsd
IEC16000178 V1 EN-US
Figure 86: ACT: GOOSE configuration on Receiver IED (left) and Sender IED (right) side
Creation of GOOSE connections via normal function blocks is not supported for the
GOOSEINTLKRCV function.
8.4.3.3 Connect to GOOSE dialog window user interface – Extended Mode GUID-908FBED9-8F16-425E-8546-1969596C45CD v1
In the “Connect to GOOSE” dialog window, “Extended Mode” is selected to create multiple GOOSE
connections directly without selecting an input signal in the Application Configuration.
1. Under “Receiver IED” section, select GOOSE Receive or normal function input signal.
2. Under “Sender IEDs” section, select and right click on data attribute in either Application
Configuration or SCL Configuration tab
3. Click on Connect option.
The GOOSE connections will be added to the configuration. Refer to Figure 76, 77, 83 and 84 for
GOOSE connections appearance in ACT.
8.4.3.4 Connecting to a IEC 61850 SCL data attribute from sending IED GUID-2B09E287-61BF-456F-A35D-3B876064B86C v2
When a GOOSE connection is created by selecting data attribute under "SCL Configuration" tab in the
Connect to GOOSE dialog window (see Figure 77), a seperate MainApp called GOOSESenderApp is
created automatically and added to application configuration in the sender IED side. GOOSESenderApp
contains the graphical representation of the IEC 61850 SCL data attributes for signals that are not visible
in Application Configuration.
IEC16000169-1-en.vsdx
IEC16000169 V1 EN-US
GOOSE datasets and GOOSE control blocks are created automatically when the GOOSE
configuration is done in ACT.
If the sender IED and receiver IEDs do not belong to same subnetworks, GOOSE receiving
is not possible.
8.4.3.5 Easy GOOSE engineering when GOOSE is configured via IEC 61850
configuration protocol GUID-0D498334-DB06-4038-9FAB-D9ADE2585D51 v1
After enabling Easy GOOSE Engineering in PCM600 (see section "Enable Easy GOOSE Engineering in
PCM600"), GOOSE can be configured either via the IEC 61850 configuration tool and the Signal matrix
tool or via Easy GOOSE. When GOOSE is configured via the IEC 61850 configuration tool and Signal
matrix tool, the GOOSE configuration is also added to the application configuration in the sender IED
and the receiver IED as shown in Figure 82, 83, 85, and 86.
When Easy GOOSE engineering is enabled in PCM600, GOOSE can be still be configured
via IEC 61850 configuration tool and Signal Matrix Tool as well.
The GOOSE variables alone cannot be pasted. They can be cut or pasted only with the connected
block.
Copying and pasting of GOOSE variables within the same IED is not allowed. If the GOOSE variable is
copied along with the connected block, only the block is copied provided that the instance is available.
GOOSE variables and worksheets can be copied and pasted into other IEDs. However, the GOOSE
sending variables are not copied. The receiving GOOSE variables are copied unless they are already
present in the other IED.
Click Work online on the toolbar in ACT for Online Monitoring for the GOOSE sending signals and
receiving signals. The sending or receiving GOOSE variable shows the value being sent or received
over GOOSE.
For IEC 61850 engineering, a separate system configuration tool may be needed with PCM600 (for
example, when using other than Hitachi Energy IEDs).
All data sets, report control blocks and GOOSE control blocks must be located at LD0/LLN0.
There are limitations regarding the maximum number of data sets, number of entries in a data
set and the number of report control blocks that can be used.
3. Add and/or reconfigure data sets. The configured IED includes a number of predefined data sets,
but it is possible to add additional data sets and/or reconfigure default data sets according to the
requirements.
Reporting data sets only contain data intended to be used by vertical clients, for example
MicroSCADA or RTU560.
4. Configure report control blocks for each data set used in vertical communication. Pre-configured
IEDs include predefined report control blocks which can be reconfigured. If additional control blocks
are needed, it is possible to add them according to requirements.
The vertical client must belong to the same sub-network as the IEDs.
Please see the IET600 user manual for additional information about vertical and horizontal
station communication engineering.
All data sets, report control blocks and GOOSE control blocks must be located at LD0/LLN0.
There are limitations regarding the maximum number of data sets, number of entries in a data
set and the number of report control blocks that can be used.
3. Create a GOOSE data set for the sending IED. Define the content of the data set according to the
requirements.
The data set for GOOSE contains signals on the data attribute or FCDA levels. The latter is
also known as structured GOOSE.
Data for one signal can only be included in one GOOSE data set. The data set for GOOSE
cannot be empty.
4. Create a GOOSE control block and connect it to the GOOSE data set. Check parameters for
GOOSE control block, for eaxample MinTime and MaxTime, and update as required.
5. Connect the GOOSE control block to receiving IEDs that subscribe GOOSE data.
6. Export the SCD file.
IEC09000631 V4 EN-US
Figure 88: IEC 61850: SCL import options for SCD file
4.1. Select Ignore Substation Section to ignore the sub-station section in the SCD file during
import.
4.2. Select Don't import IEDs ... to disable the import of unknown IED types (for example third-
party IEDs).
4.3. Select Replace unknown ... to replace unknown IED types with IED type “Generic IEC 61850
IED”. Use this option if you need to import third-party IEDs into PCM600.
4.4. Select Ignore PCM Object Type if the IED type is modified outside PCM600.
4.5. Click Import.
5.1. In SMT, configure connections between signals the server is sending and the GOOSE receive
function blocks.
If a client is defined for GOOSE receive, at least one cross in SMT is required to write the
configuration to the IED.
It is important to set Operation to On for all configured GOOSE receiving function blocks.
IEC09000631 V4 EN-US
Figure 89: IEC 61850: SCL Import options for ICD or CID file
After changing any aspect of IEC 61850 communication in PCM600 the updated configuration needs to
be written to the IED. This is done through a full Write to IED... from the context menu or the Tools
menu.
The Application Configuration tool (ACT) and the Parameter Setting tool (PST) in PCM600 are used to
configure the communication for IEC 60870-5-103 protocol.
1. Add the desired IEC 60870-5-103 function blocks to the application configuration in the Application
Configuration tool.
2. Connect the outputs of desired protection and monitoring function in the application configuration to
the inputs of the corresponding IEC 60870-5-103 function block.
3. Set the function type and desired information number, where an information number must be
supplied, for each IEC 60870-5-103 function block instance in the Parameter Setting tool.
4. Set the general communication settings for IEC 60870-5-103 and time synchronization parameters
in the Parameter Setting tool.
See the Communication protocol manual for IEC 60870-5-103 for more information about the IEC
60870-5-103 implementation in the IED series.
9.1.1 Settings for RS485 and optical serial communication M17109-118 v13
General settings
SPA, DNP and IEC 60870-5-103 can be configured to operate on the SLM optical serial port while DNP
and IEC 60870-5-103 additionally can utilize the RS485 port. A single protocol can be active on a given
physical port at any time.
Two different areas in the HMI are used to configure the IEC 60870-5-103 protocol.
1. The port specific IEC 60870-5-103 protocol parameters are configured under:
Main menu /Configuration /Communication /Station Communication /IEC60870-5-103 /
• <config-selector>
• SlaveAddress
• BaudRate
• RevPolarity (optical channel only)
• CycMeasRepTime
• MasterTimeDomain
• TimeSyncMode
• EvalTimeAccuracy
• EventRepMode
• CmdMode
• RepIntermediatePos
<config-selector> is:
GUID-CD4EB23C-65E7-4ED5-AFB1-A9D5E9EE7CA8 V3 EN
GUID-CD4EB23C-65E7-4ED5-AFB1-A9D5E9EE7CA8 V3 EN-US
The general settings for IEC 60870-5-103 communication are the following:
• SlaveAddress and BaudRate: Settings for slave number and communication speed (baud rate).
The slave number can be set to any value between 1 and 254. The communication speed, can be set
either to 9600 bits/s or 19200 bits/s.
• RevPolarity: Setting for inverting the light (or not). Standard IEC 60870-5-103 setting is On.
• CycMeasRepTime: See I103MEAS function block for more information.
• EventRepMode: Defines the mode for how events are reported. The event buffer size is 5000 events.
If EventRepMode = HiPriSpont, spontaneous events will be delivered prior to GI event. To prevent old GI
data from being delivered after a new spontaneous event, the pending GI event is modified to contain
the same value as the spontaneous event. As a result, the GI dataset is not time-correlated.
Basic knowledge about DNP3 and the used definitions are required to use CMT. See the
DNP3 communication protocol manual for information on the DNP3 implementation in the
IED.
CMT is a part of PCM600 and allows to configure the signals that are used to communicate with clients
or master units for DNP3 protocols.
On the left window CMT organizes all available signals from the application configuration in containers
that are preselected as signal types.
On the right window CMT provides containers that are selected by tabs. Each container represents one
communication channel. The number of possible communication channels is IED type dependent. The
IED uses TCP/IP as communication channel. DNP3 can be tunneled over TCP/IP. Serial communication
over RS485 or optical is supported. .
Use direction icons that are located between the windows to move all signals or a set of individual
signals between the windows.
DNP3 signal types, index and default setting for classes are predefined in CMT. Adapt the signal
configuration to project definitions. The signal type can not be modified due to the fact that the internal
signal set up is fixed.
When the default configuration values are sufficient, the task is finished when all signal are moved
according to the project requirements.
With the Save option, the signals are stored for the communication part of the IED according to the
default selections.
Only for analog measurements additional configuration parameters are shown to do signal scaling to
DNP3 protocol presentation. This can be done when the Configuration Table View is selected.
Finally, the signal configuration to the different DNP3 channels can be listed in a report on demand and
per signal type.
In order to show for a DNP master which setting group is used, the procedure outlines here can be
performed.
In this example, only setting groups one and two are used. The DNP master will get two binary inputs:
the first is set if setting group one is used, the second is set if setting group two is used.
1. Configure ACTVGRP (Basic IED functions) and SP16GAPC (Monitoring) with the Application
Configuration Tool (ACT).
IEC11000423 V4 EN-US
To make it easier to recognize the signals for the active setting group, user-defined names are
used.
2. Open the Communication Management Tool (CMT). Set the Signal Type to Binary Input Object, and
choose the connection of the master for which the values should be presented.
IEC11000424-2-en.vsd
IEC11000424 V2 EN-US
3. Select the signals and move them into the DNP signal list of the master. DNP point zero and one of
the Binary Input Objects are used for indicating the active setting group in this case.
IEC11000425-2-en.vsd
IEC11000425 V2 EN-US
Figure 93: Selecting the signals into the DNP signal list
1. Save the actual project configuration in PCM600 to make all signals visible for CMT.
IEC10000172.vsd
IEC10000172 V1 EN-US
IEC10000173.vsd
IEC10000173 V1 EN-US
Figure 95: CMT: Hardware channels appearing in the Communication Management Tool
2. Right-click the IED in the plant structure and select Communication Management to start the
Communication management tool.
3. Select the DNP3 protocol from the new window and click OK. Figure 96 presents the design of the
two container windows, which open after the selection of DNP3.
• The right window shows tabs for possible communication channels.
• The left window has a drop down menu for signal selection and buttons for signal movement, see
Figure 96.
IEC09000722-2-en.vsd
IEC09000722 V2 EN-US
Figure 96: CMT: Container window design when selecting DNP3 protocol
2. Press the blue arrow button to insert the selected signals into the configuration.
3. Press the green double arrow button to insert all signals into the configuration, see Figure 97.
IEC08000361.vsd
IEC08000361 V1 EN-US
4. Click the drop down list Signal Type: to select the other signal types for this channel.
5. Repeat to move signals for all signal types and save the selection.
Content changes in the DNP3 container are marked with a star at the end of the name, see
Figure 98. The star indicates that changes in the container have to be saved before leaving
CMT.
IEC08000339-2-en.vsd
IEC08000339 V2 EN-US
Two parameters per signal can be set for all signal types:
1. Click the two inner arrows to sort signals to another index sequence, or select Set Index ... from the
context menu to move one or a set of signals to another array, see Figure 99.
IEC08000336-2-en.vsd
IEC08000336 V2 EN-US
2. The selection window shows the number of signals selected, see Figure 100.
IEC08000363-2-en.vsd
IEC08000363 V2 EN-US
3. Define the Starting index for this group and click OK.
1. Click in the class field of the signal to change the class configuration.
2. The Select Class window opens.
3. Make the selection according to the definitions in the project and click OK to close the window and
get the new configuration, see Figure 101.
IEC08000338-2-en.vsd
IEC08000338 V2 EN-US
In DNP3 the user classifies the signals and defines those signals that are not member of any class. CMT
has a default predefined organization of classes per signal type. In the master station the classes can be
polled in sequences according to the demands in the project. Unsolicited reporting is possible as well.
Procedure
1. Click in the Class field of the signal. A new window Select Class opens where the user classifies the
signal.
2. Select the signal classes and choose between None and 0 to 3 according to the project demands.
3. Click OK to set the signal classification.
4. Write to IED.
IEC 61850 Structure Mapping Tool is used to manage the data model of IED, where one can change the
IEDs IEC 61850 data model as per the requirement. This can be done by mapping the data model with
customer specific data model. The IEC 61850 structure mapping tool is available only in FPN projects in
PCM600. A PCM600 project can be converted into an FPN project by importing an FPN SCD file into it.
FPN is supported for both IEC 61850 Edition 1 and IEC 61850 Edition 2.
FPN allows the use of standardized, predefined and IED-vendor independent templates for building and
maintaining substations. Refer to the PCM600 online help for more detailed information about FPN.
1 2 3
IEC15000082-2-en.vsdx
IEC15000082 V2 EN-US
1. Plant Structure
2. IEC 61850 Structure Mapping
3. Object Properties
Plant Structure
The data tree displays the Flexible Product Naming (FPN) IEDs, non-FPN IEDs and mapped IEDs under
substation; internal IEDs under unassigned IEDs.
The IEC 61850 structure mapping list displays the FPN objects based on the current selection in the
plant structure. The list may display either IEDs or data attributes. The FPN object’s name is displayed in
the column on the left and the mapped PCM600 internal object name is displayed in the column on the
right. The IEC 61850 structure mapping displays customer data structure and customer data attribute on
the left; internal data structure and internal data attribute on the right.
Object Properties
Object properties window displays properties of objects currently selected in the FPN Mappings and
Internal Data Attribute lists. The properties are read-only and cannot be modified by user.
The names used for the internal objects can be defined to be either the names used in PCM600 or
the names defined in the internal IEC 61850 model. To change the naming convention, select PCM600
naming style in use from options.
The fundamental idea of FPN is to extend LN classes and adapt the name and assignments
of DOs/DAs to LNs, without "impersonating" or reusing standard LN classes for other uses.
There are certain restrictions when using the LN classes LTRK, GSAL, and LGOS in the customer
model because they are maintained directly by the communications stack.
LTRK and GSAL are completely managed by the stack; therefore, they can be included in the customer
model as long as they adhere to the internal LN modeling (or a subset of the internal model). The model
can be reduced but not extended in the FPN mapping.
LGOS can be reduced and extended, but in the FPN mapping, the stack will take on control of some
specified DOs (GoCBRef, NdsCom, St, SimSt, LastStNum, ConfRevNum, and RxConfRevNum) and
cannot be remapped to a different source.
LGOS also needs the GoCBRef with a setSrcRef referring to an authorized GOOSE Control Block to
function under GOOSE supervision.
Before starting the IEC 61850 Structure Mapping Tool, enable the option Import as Flexible Product
Naming SCD.
IEC17000021-1-en.vsdx
IEC17000021 V1 EN-US
System Configuration Description (SCD) file can only be imported only at the substation level.
IEC17000022-1-en.vsdx
IEC17000022 V1 EN-US
IEC17000023-1-en.vsdx
IEC17000023 V1 EN-US
Importing the FPN SCD file will convert the project into a FPN project and the conversion is
irreversible.
The tool can be started from any node from Substation to IED level.
IEC17000024-1-en.vsdx
IEC17000024 V1 EN-US
The first step in the IEC 61850 structure mapping is to map the real IEDs to the customer specific IEDs.
IED mapping means that each server IED in the FPN model is mapped with a corresponding IED in
the internal PCM600 model, that is, the real device in the substation. A server IED is an IED that has
an access point containing a server. IED mapping does not map the data attributes between the IEDs
unless the data attribute mapping is complete. IED mapping can be done in the PCM600 plant structure
and in the IEC 61850 structure mapping tool.
IED mapping
IED mapping is done in plant structure by dragging and dropping a PCM600 IED from the Unassigned
IEDs group on an FPN IED in the Substation. IED mapping status is indicated visually in the plant
structure.
11.4.1.2 IED mapping in the IEC 61850 Structure Mapping Tool GUID-07F9D393-FE3C-4392-8943-202D7ECB1587 v2
IED mapping
The tool will display all FPN IEDs and all PCM600 IEDs in separate lists. Mapping will be done by
dragging and dropping the PCM600 IED on the right hand side to FPN IED on the left hand side. The
tool indicates the mapping status visually.
Click save button of the IEC 61850 structure mapping tool to apply the mapping.
IEC15000090-2-en.vsdx
IEC15000090 V2 EN-US
IEC15000091-2-en.vsdx
IEC15000091 V2 EN-US
Click save button of the IEC 61850 structure mapping tool to remove the mapping.
IEC17000025-1-en.vsdx
IEC17000025 V1 EN-US
IEC17000026-1-en.vsdx
IEC17000026 V1 EN-US
Filters
Displayed objects can be filtered using the filtering options in the quick access Toolbar.
IEC17000027-1-en.vsdx
IEC17000027 V1 EN-US
The objects are filtered by free text, showing all the objects with a certain name in both Data Structure
level and Data Attribute level.
The objects are filtered by status, showing only selected objects in Data Structure level and Data
Attribute level.
Objects in the FPN can be filtered using additional filtering options available in the quick access menu.
Data attribute mapping means that each FPN data attribute in the FPN model is mapped with a
corresponding data attribute in the internal PCM600 model, that is, the real device in the substation.
The mapping status is indicated visually. It can be seen what FPN data attribute is mapped to what
PCM600 internal data attribute and how many FPN data attributes are mapped to a PCM600 internal
data attribute.
Data attribute mapping is complete when all data attributes of the FPN IED, which are not excluded from
the mappings, are mapped with a PCM600 internal data attribute. The data attribute mapping must be
complete in order to be able to write to IED.
Data attribute mapping is broken if any of the data attributes - FPN or PCM600 internal - that are
mapped, does not exist in the SCL database.
When performing data attribute mapping, understand the following visual signs:
Completely mapped
Not mapped
Broken mapping
Partially mapped
All data attributes in the FPN model must be mapped or excluded, otherwise write to IED
fails.
The IEC 61850 Structure Mapping Tool displays the FPN data attributes and PCM600 internal data
attributes in separate lists. The mapping is done by dragging and dropping the FPN data attribute onto a
PCM600 internal data attribute.
The mapping is removed by right clicking and selecting remove from the context menu or by clicking the
Delete key while the mapping is selected.
IEC17000030-1-en.vsdx
IEC17000030 V1 EN-US
Data attribute mapping can be created on the data object level in one of the alternative ways.
• Drag a data object from the customer data structure onto a data object in the internal data structure
• Drag a data object from the internal data structure onto a data object in the customer data structure.
IEC17000031-1-en.vsdx
IEC17000031 V1 EN-US
Data attribute mapping can be created on the logical node level in one of the alternative ways.
• Drag a logical node from the customer data structure on a logical node in the internal data structure.
• Drag a logical node from the internal data structure on a logical node in the customer data structure.
IEC17000032-1-en.vsdx
IEC17000032 V1 EN-US
Data attributes can be excluded by selecting the data attributes to exclude, right-clicking and selecting
the exclude option from the context menu. It is possible to exclude all unmapped data attributes from the
mapping at once by right-clicking and selecting the exclude all option.
IEC17000033-1-en.vsdx
IEC17000033 V1 EN-US
The data attributes that are excluded from the mapping will not be excluded from the model. Excluded
mappings will be ignored when determining if an IED mapping is complete.
It is crucial to set a value to the excluded data attributes before initiating the mapping.
The data attribute value can be set by editing the Value field in the Object Properties window. For enum
type of data attributes there is a list of available values to select. For numeric and string type data
attributes the value can be entered directly in the Value field.
IEC15000132 V2 EN-US
Value cannot be set for all types of data attributes, for example, quality and timestamp values
cannot be edited.
Once the FPN mapping is complete, all mapping can be validated in three ways using the validate option
available in quick access menu
1. Validate All
2. Validate Current
3. Validate Selected
IEC17000029-1-en.vsdx
IEC17000029 V1 EN-US
It is possible to create a template of an IED’s data attribute mapping and store it for reuse. The template
contains description of the data attribute mapping between two IED SCL models.
All mapping templates created in PCM600 are stored in a template library. The template library is not
specific to certain PCM600 project, but it is common for all projects. Templates in the library can be
managed in the following ways.
• Import templates
• A single or multiple template files can be imported.
• If a template being imported already exists in the library, user will be prompted whether to override
the existing one.
The mapping templates are also used by IET600 to translate the internal data references in the signal
library to the FPN references, because IET600 needs to know what template to use to resolve the
internal data references.
Data attribute mapping templates can be created from mapped IEDs. If the template is created from an
incompletely mapped IED, an information dialog will be shown. User can select an option to not show
the dialog again. The dialog can be resumed afterwards from the PCM600 Options menu.
The template can be created either from the IEC 61850 structure mapping tool or from the PCM600
plant structure. The required template information has to be filled in before it can be created.
The template can be selected from a list consisting of all available templates. The FPN IED must be
mapped with a PCM600 internal IED before the template can be applied.
The template can be applied either in the IEC 61850 structure mapping tool or in the PCM600 plant
structure. In the IEC 61850 structure mapping tool, the template can be applied to one or several IEDs at
once. In the plant structure the template can be applied on one IED at a time by right clicking on an IED
or on all IEDs under a bay by right clicking on the bay.
IEC15000501-2-en.vsdx
IEC15000501 V2 EN-US
4. Select the folder where to export the templates and click OK.
The report consist of a cross-reference list of the IED and data attribute mappings. I.e. a table of all FPN
objects together with the PCM600 internal objects they are mapped with.
Section 12 Glossary
12.1 Glossary M14893-1 v20
AC Alternating current
ACC Actual channel
ACT Application configuration tool within PCM600
A/D converter Analog-to-digital converter
ADBS Amplitude deadband supervision
ADM Analog digital conversion module, with time synchronization
AI Analog input
ANSI American National Standards Institute
AP Access Point
AR Autoreclosing
ASCT Auxiliary summation current transformer
ASD Adaptive signal detection
ASDU Application service data unit
AWG American Wire Gauge standard
BBP Busbar protection
BFOC/2,5 Bayonet fiber optic connector
BFP Breaker failure protection
BI Binary input
BIM Binary input module
BOM Binary output module
BOS Binary outputs status
BR External bistable relay
BS British Standards
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
CAM Central Account Management
CAN Controller Area Network. ISO standard (ISO 11898) for serial communication
CB Circuit breaker
CBM Combined backplane module
CCITT Consultative Committee for International Telegraph and Telephony. A United
Nations-sponsored standards body within the International Telecommunications
Union.
CCM CAN carrier module
CCVT Capacitive Coupled Voltage Transformer
Class C Protection Current Transformer class as per IEEE/ ANSI
CMPPS Combined megapulses per second
TRM Transformer Module. This module transforms currents and voltages taken from
the process into levels suitable for further signal processing.
TYP Type identification
UMT User management tool
Underreach A term used to describe how the relay behaves during a fault condition. For
example, a distance relay is underreaching when the impedance presented to
it is greater than the apparent impedance to the fault applied to the balance
point, that is, the set reach. The relay does not “see” the fault but perhaps it
should have seen it. See also Overreach.
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 addition 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 is
also sometimes known by the military name, "Zulu time." "Zulu" in the phonetic
alphabet stands for "Z", which stands for longitude zero.
UV Undervoltage
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