Bcid 1207 Av 01

ercid
IEC61850 Files Editing Program

Instructions Manual
© ZIV GRID AUTOMATION, S.L. 2012 BCID1207Av01

ZIV APLICACIONES Y TECNOLOGÍA, S.L.
End-User Software License Agreement
THIS IS A LEGAL AGREEMENT BETWEEN YOU (AS "LICENSEE") AND ZIV APLICACIONES Y
TECNOLOGIA, S.L. (AS "LICENSOR") FOR THE SOFTWARE PROGRAM YOU HAVE
PURCHASED. PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT
CAREFULLY BEFORE USING THE PROGRAM DISKETTES/CDs. THE PROGRAM IS
COPYRIGHTED AND LICENSED TO YOU (NOT SOLD).
IF YOU INSTALL, USE OR COPY THE SOFTWARE PROGRAM, YOU ARE ACCEPTING AND
AGREEING TO THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO
BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, YOU SHOULD PROMPTLY
RETURN THE ENTIRE CONTENTS OF THIS PACKAGE TO YOUR SELLER.
Terms and Conditions of License
1. License Grant. Licensor hereby grants to you, and you accept, a nonexclusive license to use the
Program Diskettes and the computer programs contained therein in machine-readable, object code form only,
and the accompanying documentation (collectively referred to as the "Software"), only as authorized in this
License Agreement. You may use the program(s) solely in your internal operations at all facility sites you own
but only with the type of machines and equipment specified in the printed material furnished by Licensor and
only in accordance with the instructions given in such material.
2. Restrictions. You may not: (a) use, copy, modify or transfer the Software except as expressly
provided in this or another Agreement with Licensor, (b) reverse engineer, decompile or disassemble or separate
the components of the Software, or (c) rent, sell or lease the Software or make the Software available to others to
do any of the foregoing.
3. Back-up. Upon loading the Software into your computer, you may retain the Program Diskette/CDs
for backup purposes. In the event the program diskettes are damaged, you may return them to Licensor, at your
expense, and obtain a new copy free of charge.
4. No Assignment. This License is intended for your exclusive use. You agree that you will not
assign, sublicense, transfer, pledge, lease, rent or share your rights under this License Agreement.
5. Licensor's Ríghts. You acknowledge and agree that the Software is the proprietary product of
Licensor protected under International laws and treaties. You further acknowledge and agree that all right, title
and interest in and to the Software, including associated intellectual property rights, are and shall remain with
Licensor. This License Agreement does not convey to you an interest in or to the Software, but only a limited
right of use revocable in accordance with the terms of this License Agreement.
6. Confidentiality. The Software is confidential and no details or information relating to the same
shall be disclosed to any third party without the prior written consent of Licensor.
7. Term. This License Agreement is effective upon your opening of this package and shall continue
until terminated. You may terminate this License Agreement at any time by returning the Software and all copies
thereof and extracts there from to Licensor, or by destroying all tangible copies of the Software. Licensor may
terminate this License Agreement upon your breach of any term hereof. Upon such termination by Licensor, you
agree to return to Licensor the Software and all copies and portions thereof, or destroy all tangible copies of the
Software, and to erase all copies of the Software held in computer memory or otherwise.
8. AS IS. THE SOFTWARE IS LICENSED "AS IS" AND WITHOUT A WARRANTY OF ANY
KIND. LICENSOR EXPRESSLY DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER
EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. LICENSOR DOES NOT
WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET
UNINTERRUPTED OR ERROR FREE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE
OF THE SOFTWARE IS WITH YOU.
9. Limitation of Liability. Licensors sole and entire liability, and your exclusive remedy, with respect
to any claims relating to the Software shall be to provide a new set of diskettes free of charge. In no event shall
Licensor be liable for any indirect, incidental, consequential, special, or exemplary damages or lost
profits, even if Licensor has been advised of the possibility of such damages.
10. Trademark. ZIVERCID is a common law trademark of Licensor. No right, license, or interest to
such trademark is granted hereunder, and you agree that no such right, license or interest shall be asserted by you
with respect to such trademark.
11. Licensee's indemnity. You shall defend, indemnify and hold Licensor harmless against any loss or
damage of any kind arising from a breach by you of this License Agreement, or any use or misuse of the
Software by you or your employees, agents, or representatives, and from any other of your conduct or from any
claim or action by any of your customers in connection with the Software or this License Agreement.
12. Governing Law. This License Agreement shall be construed and governed in accordance with the
internal laws of SPAIN.
13. No Waiver. The failure of either party to enforce any rights hereunder or to take action against the
other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent
enforcement of rights or subsequent actions in the event of future breaches..
14. Entire Agreement. This License Agreement is the entire agreement between you and Licensor
with respect to the use of the Software and supersedes all prior understandings or agreements between the
parties. This License Agreement may be amended only by a writing by an officer of Licensor.
ZIV Aplicaciones y Tecnología S.L.

Parque Tecnológico, 210
48170 Zamudio (Bizkaia)
Apartado 757
48080 Bilbao - Spain
Tel.- (34) 94 452.20.03
Table of Contents
Chapter 1. Description and Start
1.1 Introduction ................................................................................................ 1.1-1

1.1.1 Introducing to the ZIVerCid® File Editing Program ...................................... 1.1-2
1.1.2 Functions ..................................................................................................... 1.1-2
1.1.2.a ICD, CID and SCD File Validation ............................................................... 1.1-2
1.1.2.b DataSet Configuration ................................................................................. 1.1-2
1.1.2.c RCBs and GCBs Configuration ................................................................... 1.1-2
1.1.2.d Configuration of Goose Message Reception ............................................... 1.1-2
1.1.2.e Logic Configuration ...................................................................................... 1.1-2
1.1.2.f File Comparison........................................................................................... 1.1-3
1.1.2.g Configuring Communications Data .............................................................. 1.1-3
1.1.2.h Other functions ............................................................................................ 1.1-3
1.2 Installation and Start ................................................................................. 1.2-1

1.2.1 Minimum Computer Requirements .............................................................. 1.2-2
1.2.2 Preparation for Installation ........................................................................... 1.2-2
1.2.3 Program Installation ..................................................................................... 1.2-2
1.2.4 General Operation Mode ............................................................................. 1.2-2
1.2.4.a Organization of the information ................................................................... 1.2-2
1.2.4.b Operating Method ........................................................................................ 1.2-3
1.2.4.c Information Screens..................................................................................... 1.2-3
Chapter 2. Application Development
2.1 Application Management .......................................................................... 2.1-1

2.1.1 Edit Screen .................................................................................................. 2.1-2
2.1.2 Menu Options .............................................................................................. 2.1-3
2.1.3 Edit Data ...................................................................................................... 2.1-7
2.1.4 Data Validation ............................................................................................ 2.1-8
2.1.4.a File Validation .............................................................................................. 2.1-8
2.1.4.b Dynamic Data Validation ............................................................................. 2.1-8
2.1.4.c DataSets Validation ..................................................................................... 2.1-9
2.1.5 ConfigRev and ParamRev Parameter Index Update .................................. 2.1-9
2.2 DataSets...................................................................................................... 2.2-1

2.2.1 Introduction .................................................................................................. 2.2-2
2.2.2 DataSets Configuration................................................................................ 2.2-3
2.2.3 Import DataSets ........................................................................................... 2.2-5
2.2.4 Validate DataSets ........................................................................................ 2.2-6
2.3 RDBs and GCBs ......................................................................................... 2.3-1

2.3.1 Introduction .................................................................................................. 2.3-2
2.3.2 RCBs Configuration ..................................................................................... 2.3-3
2.3.3 GCBs Configuration ..................................................................................... 2.3-4
I
BCID1207A
ZIVerCid: IEC61850 Files Editing Program
 ZIV GRID AUTOMATION, S. L. Zamudio, 2012
Table of Contents
2.4 Gooses ........................................................................................................ 2.4-1

2.4.1 Receive Goose Messages ........................................................................... 2.4-2
2.4.2 Configure an incoming Goose ..................................................................... 2.4-2
2.4.2.a setRef Attribute Configuration ...................................................................... 2.4-3
2.4.2.b intAddr Attribute Configuration ..................................................................... 2.4-6
2.4.2.c Configuration through ZIVerlog® .................................................................. 2.4-6
2.5 Communications ........................................................................................ 2.5-1

2.5.1 Edit Communications ................................................................................... 2.5-2
2.5.1.a General Communications Data .................................................................... 2.5-2
2.5.1.b Goose Communications Settings................................................................. 2.5-3
2.6 CIDs ............................................................................................................. 2.6-1

2.6.1 Compare CIDs ............................................................................................. 2.6-2
2.6.1.a Functional Constraint (FC) Tree .................................................................. 2.6-3
2.6.1.b Copy Differences between Files .................................................................. 2.6-3
2.7 Display and Edit Data ................................................................................ 2.7-1

2.7.1 Arrangement of the Settings Tree ................................................................ 2.7-2
2.7.1.a Filters for FC mode ...................................................................................... 2.7-2
2.7.2 Search and Replace .................................................................................... 2.7-2
2.7.3 Expand and Collapse Nodes ....................................................................... 2.7-3
2.7.3.a Expand Tree Nodes ..................................................................................... 2.7-3
2.7.3.b Collapse Tree Nodes ................................................................................... 2.7-3
2.7.3.c Expand / Collapse in Edit Screen ................................................................ 2.7-3
2.8 Edit Logic .................................................................................................... 2.8-1

2.8.1 Introduction .................................................................................................. 2.8-2
Chapter 3. Managing Control Configurations
3.1 Introduction ................................................................................................ 3.1-1

3.1.1 Introduction .................................................................................................. 3.1-2
3.1.2 Functions...................................................................................................... 3.1-2
3.1.2.a Creating a Configuration .............................................................................. 3.1-2
3.1.2.b Editing a Selected Configuration ................................................................. 3.1-2
3.1.2.c Generating Files ........................................................................................... 3.1-3
3.1.2.d Controlling and Checking Configuration Data.............................................. 3.1-3
3.1.2.e Validating a Configuration ............................................................................ 3.1-3
3.1.2.f Importing Data from Other Logic Configurations ......................................... 3.1-3
3.1.2.g Controlling and Managing Configurations.................................................... 3.1-3
3.2 Getting Started ........................................................................................... 3.2-1

3.2.1 Loading and Validating the Profile ............................................................... 3.2-2
3.2.2 Start Menu.................................................................................................... 3.2-4
3.2.3 Operating Method (Mouse & Keyboard) ...................................................... 3.2-4
3.2.4 Information Displays .................................................................................... 3.2-5
3.2.5 Using the Controls ....................................................................................... 3.2-5
3.2.6 Selecting Signals ......................................................................................... 3.2-7
3.2.6.a Signal Selection Screen ............................................................................... 3.2-7
3.2.6.b Signal Types ................................................................................................ 3.2-8
3.2.6.c Signal Restrictions ....................................................................................... 3.2-8
II
BCID1207A
Table of Contents
3.3 File Menu .................................................................................................... 3.3-1

3.3.1 New Configuration ....................................................................................... 3.3-2
3.3.2 Configuration Information ............................................................................ 3.3-2
3.3.3 Load Configuration ...................................................................................... 3.3-2
3.3.4 Save Configuration ...................................................................................... 3.3-3
3.3.5 Compile Configuration ................................................................................. 3.3-3
3.3.6 Quit .............................................................................................................. 3.3-3
3.4 Input / Output Logic................................................................................... 3.4-1

3.4.1 Introduction .................................................................................................. 3.4-2
3.4.2 Input Logic ................................................................................................... 3.4-2
3.4.3 Output Logic ................................................................................................ 3.4-4
3.4.4 LEDs Logic .................................................................................................. 3.4-5
3.5 Configuration-Associated Logic .............................................................. 3.5-1

3.5.1 Introduction .................................................................................................. 3.5-2
3.5.2 Definition of Opcodes .................................................................................. 3.5-2
3.5.3 Records Associated with Logic .................................................................... 3.5-10
3.5.4 Managing Records....................................................................................... 3.5-10
3.5.4.a Opcodes....................................................................................................... 3.5-14
3.6 Defining Resources ................................................................................... 3.6-1

3.6.1 Introduction .................................................................................................. 3.6-2
3.6.1.a Digital Signals .............................................................................................. 3.6-2
3.6.2 Parameters .................................................................................................. 3.6-3
3.6.3 Settings ........................................................................................................ 3.6-4
3.6.3.a Settings Group ............................................................................................. 3.6-4
3.6.3.b Defining Settings.......................................................................................... 3.6-5
3.6.4 Constants ..................................................................................................... 3.6-6
3.6.5 Commands .................................................................................................. 3.6-7
3.6.5.a Command Element Description ................................................................... 3.6-7
3.6.5.b Configuring the Command ........................................................................... 3.6-8
3.6.6 Analog Commands ...................................................................................... 3.6-15
3.6.6.a Analog Command Actions ........................................................................... 3.6-15
3.6.6.b Command Blocks......................................................................................... 3.6-16
3.7 Communications........................................................................................ 3.7-1

3.7.1 Introduction .................................................................................................. 3.7-2
3.7.1.a General Format and Screen Handling ......................................................... 3.7-2
3.7.2 Procome....................................................................................................... 3.7-4
3.7.2.a Events .......................................................................................................... 3.7-4
3.7.2.b Control Changes .......................................................................................... 3.7-6
3.7.2.c Commands .................................................................................................. 3.7-9
3.7.2.d Metering Values ........................................................................................... 3.7-11
3.7.2.e Meters .......................................................................................................... 3.7-13
3.7.2.f Output Writings ............................................................................................ 3.7-14
3.7.3 DNP3 ........................................................................................................... 3.7-19
3.7.3.a Contacts ....................................................................................................... 3.7-19
3.7.3.b Commands .................................................................................................. 3.7-20
3.7.3.c Metering Values (Profile I) ........................................................................... 3.7-24
3.7.3.d Metering Values (Profile II) .......................................................................... 3.7-26
3.7.3.e Meters .......................................................................................................... 3.7-29
3.7.3.f Analog DNP3 Output Writings (Profile I) ..................................................... 3.7-31
3.7.3.g DNP3 Analog Output Writings (Profile II) .................................................... 3.7-34
III
BCID1207A
Table of Contents
3.7.4 MODBUS Protocol ....................................................................................... 3.7-37

3.7.4.a Inputs and Outputs ....................................................................................... 3.7-37
3.7.4.b Commands ................................................................................................... 3.7-39
3.7.4.c Metering Values ........................................................................................... 3.7-41
3.7.4.d Meters .......................................................................................................... 3.7-43
3.7.4.e Analog Output Writings ModBus .................................................................. 3.7-44
3.7.5 61850 Protocol ............................................................................................. 3.7-47
3.7.5.a Validity Configuration ................................................................................... 3.7-47
3.7.5.b CSWI Node .................................................................................................. 3.7-48
3.7.5.c XCBR Node.................................................................................................. 3.7-51
3.7.5.d XSWI Node .................................................................................................. 3.7-52
3.7.5.e MCXL Node.................................................................................................. 3.7-52
3.7.5.f RFTL Node................................................................................................... 3.7-53
3.7.5.g MMTR Node ................................................................................................. 3.7-56
3.7.5.h LPHD Node .................................................................................................. 3.7-57
3.7.5.i ATCC ........................................................................................................... 3.7-57
3.7.5.j IHMI.............................................................................................................. 3.7-59
3.7.5.k CALH............................................................................................................ 3.7-59
3.7.5.l SIMG ............................................................................................................ 3.7-60
3.7.5.m GENGGIO .................................................................................................... 3.7-60
3.7.5.n TGOGGIO and TGO2GGIO......................................................................... 3.7-62
3.7.5.o YLTC ............................................................................................................ 3.7-63
3.8 HMI............................................................................................................... 3.8-1

3.8.1 Introduction .................................................................................................. 3.8-2
3.8.2 Commands ................................................................................................... 3.8-2
3.8.3 Events .......................................................................................................... 3.8-3
3.8.4 User Defined HMI Screens .......................................................................... 3.8-4
3.8.5 HMI Cyclical Screens ................................................................................... 3.8-5
3.8.5.a HMI Available Screens ................................................................................. 3.8-6
3.9 Graphical HMI ............................................................................................. 3.9-1

3.9.1 Introduction .................................................................................................. 3.9-2
3.9.2 Graphic Screens to be Displayed ................................................................ 3.9-2
3.9.2.a Screens available for the Graphical HMI ..................................................... 3.9-3
3.9.3 Graphical User Screens ............................................................................... 3.9-3
3.9.3.a Single Line Diagram Data Configuration ..................................................... 3.9-3
3.9.3.b Single Line Diagram Design ........................................................................ 3.9-7
3.9.3.c Import Single Line Diagram and Import Single Line Diagram Graphic
Design .......................................................................................................... 3.9-8
3.10 Profile Descriptions ................................................................................... 3.10-1

3.10.1 Introduction .................................................................................................. 3.10-2
3.10.1.a Digital Signals .............................................................................................. 3.10-2
3.10.1.b Analog Signals ............................................................................................. 3.10-2
3.11 Documentation ........................................................................................... 3.11-1

3.11.1 Introduction .................................................................................................. 3.11-2
3.11.2 Reports......................................................................................................... 3.11-2
3.11.3 Report Output Types .................................................................................... 3.11-4
3.11.4 Report Parts ................................................................................................. 3.11-5
IV
BCID1207A
Chapter 1
Description and
Start
Content
1.1 Introduction
1.2 Installation and Start
1.1 Introduction

1.1.1 Introducing to the ZIVerCid® File Editing Program .................................................. 1.1-2
1.1.2 Functions ................................................................................................................. 1.1-2
1.1.2.a ICD, CID and SCD File Validation ...................................................................... 1.1-2
1.1.2.b DataSet Configuration ........................................................................................ 1.1-2
1.1.2.c RCBs and GCBs Configuration .......................................................................... 1.1-2
1.1.2.d Configuration of Goose Message Reception ...................................................... 1.1-2
1.1.2.e Logic Configuration ............................................................................................. 1.1-2
1.1.2.f File Comparison.................................................................................................. 1.1-3
1.1.2.g Configuring Communications Data ..................................................................... 1.1-3
1.1.2.h Other functions ................................................................................................... 1.1-3
This manual is intended to serve as help in using the ZIVerCid® file editing program, which
runs on WINDOWS© compatible PCs.
1.1.1 Introducing to the ZIVerCid® File Editing Program

The ZIVerCid® software program allows the user to edit ICD, CID and SCD files in an easy and
simple manner, as well as file data retrieval. ZIVerCid® simplifies the configuration of dataSets,
RCBs and Communications Data.
Also, this software allows editing the configuration logic of ZIV devices.
In order for this function to be used, the Zivercomplus® and the Zivercomplus® Equipments
Profile Database, from which the required data for using and validating the above logics can be
obtained, must be installed as they cannot be obtained from the ZIVerCid®.
1.1.2 Functions
1.1.2.a ICD, CID and SCD File Validation
Assists in file validation against SCL scheme and extra validation of types of data, dependency,
etc.
1.1.2.b DataSet Configuration

Allows importing, creating or deleting DataSets for correct configuration. It also allows arranging
DataSet elements.
1.1.2.c RCBs and GCBs Configuration

It allows linking the previously created DataSets to the different RCBs and GCBs, apart from
their parameterisation.
1.1.2.d Configuration of Goose Message Reception

It allows configuring Goose message parameters to be subscribed and applicable Goose
message information, to be used as desired.
1.1.2.e Logic Configuration

It allows configuring the IED programmable logic as well as other IED configurable features not
included for free in standard 61850. In order to configure IED logics, the Zivercomplus®
database must be installed.
1.1-2
BCID1207A
1.1 Introduction
1.1.2.f File Comparison

It allows comparing final attributes of two different CID files, as well as displaying and copying
the differences between both files.
1.1.2.g Configuring Communications Data

It allows for quick access to Communications configuration data and Goose data.
1.1.2.h Other functions

Language selection, printing documents and results, changing tree view mode (FC / CDC),
filtering, search/replace, etc.
1.1-3
BCID1207A
1.1-4
BCID1207A

1.2.1 Minimum Computer Requirements .......................................................................... 1.2-2
1.2.2 Preparation for Installation ....................................................................................... 1.2-2
1.2.3 Program Installation ................................................................................................. 1.2-2
1.2.4 General Operation Mode ......................................................................................... 1.2-2
1.2.4.a Organization of the information .......................................................................... 1.2-2
1.2.4.b Operating Method ............................................................................................... 1.2-3
1.2.4.c Information Screens............................................................................................ 1.2-3
1.2.1 Minimum Computer Requirements

The minimum requirements for the PC to be used with this application are:
- 1 GB of RAM.
- WINDOWS® XP or Vista OS.
- Hard drive with 200 MB of free space.
- VGAcard, minimum 1024x768.
- Color VGAmonitor.
- Mouse and Keypad.
1.2.2 Preparation for Installation

Before commencing to install the ZIVerCid®, you must first check the requirements specified in
the previous paragraph, and ensure your hard disc has enough free space to house the new
application, a minimum of 60 Mb.
1.2.3 Program Installation

The ZIVerCid® program is supplied in a CD-ROM to be subsequently installed in the PC.
Installation is made by inserting the CD-ROM and execute filesetup.exe.
During the installation process the program gives options to select the directory where the
program is to be installed, as well as the group to be generated in the program manager.
By default, the software will be installed in the directory \ZIV\ZIVerCID of the folder Program
Files (or equivalent). The directory will be created if it does not exist.
For computers with WINDOWS® 7, the installation directory must be isolated from the Program
Files area and located from C: (or D:, …), e.g. C:\ZIV\ZIVerCID.
1.2.4 General Operation Mode

1.2.4.a Organization of the Information
There are two information structure: trees and tables.
- The tree structures facilitate the navigation and the visualization of the files ICD, CID or
SCD with which one is working.
- The tables shows the information of a tidy and simple way for the edition of the
information that they contain.
1.2-2
BCID1207A
1.2.4.b Operating Method

The options desired can be selected from most of the screens from the ZIVerCid® in two
different ways: the mousse and the keyboard.
The keyboard is used to introduce the values of the modified information and to gain access to
some of the options of the menu making use of the brief methods Ctrl+O, Ctrl+S, Ctrl+V and
Ctrl+C or functions as the access to the help by means of the key F1.
The mouse allows to navegate trough the application and gain access to the contextual menus
of those who arrange both the tree and the table of the principal screen clicking in the right
button. From the contextual menus depending on the screen in which it is he will be able to gain
access to the options to expand / contract, search / replace and copy / paste.
1.2.4.c Information Screens

There consider information screens all those who inform the user of what happens in the
application. It can be a question so much of information about the errors that have arisen as of
information of general interest for the user.
The biggest information window is the sliding window of results, window that appears
automatically on having opened the application and that the user can open in any moment.
1.2-3
BCID1207A
This window can be on the principal screen and on the screen of forming dataSets, showing the
information of the validates of the document, of the validate of dataSets orinformation of
dataSets:
- Document Validation: it shows the route of the erroneous fact and indicates type of error
(incoherences of the types of information, erroneous references, etc.).
- dataSet Validation: it shows the information obtained on having validated the dataSet of
the current document, as well as a summary of the current configuration.
- dataSet Information: it shows the number of datasets existing and the FCDAs that these
contain.
The informative windows in other points of the application appear to give information to the user
on serious errors or to warn him of errors that have happened on having introduced new not
valid values for a data.
Also this type of windows is used to inform the user about actions taken the application or
events happened during the execution of an operation.
On having tried to form the logic, if it is detected that is not had installed the database of the
Zivercomplus® also will show a message warning the user that there is not the profile file of
which to obtain the datas for the configuration of the logic.
Another way of informing the user is by means of

the title of the window in which it finds, where there
appears information relative to the file that is edited
as it is the name of the file. In windows as that of
Importing DataSets, tags appear to indicate the
names of the files origin and destination with that
they are working.
In the status bar placed in the left low part of

the window, there appears a progress bar of
the status of the operation indicates in
execution together with an explanatory text
on the operation that is carried out in every
moment.
1.2-4
BCID1207A
Chapter 2
Application
Development
Content
2.1 Application Management

2.2 DataSets
2.3 RDBs and GCBs
2.4 Gooses
2.5 Communications
2.6 CIDs
2.7 Display and Edit Data
2.8 Edit Logic
2.1 Application
Management

2.1.1 Edit Screen .............................................................................................................. 2.1-2
2.1.2 Menu Options........................................................................................................... 2.1-3
2.1.3 Edit Data .................................................................................................................. 2.1-7
2.1.4 Data Validation......................................................................................................... 2.1-8
2.1.4.a File Validation ..................................................................................................... 2.1-8
2.1.4.b Dynamic Data Validation .................................................................................... 2.1-8
2.1.4.c DataSets Validation ............................................................................................ 2.1-9
2.1.5 ConfigRev and ParamRev Parameter Index Update............................................... 2.1-9
2.1.1 Edit Screen

It is the application main screen and is divided into two areas.
The area to the left shows a tree for easy file browsing. Clicking the mouse right button displays
a contextual menu. This menu allows access to Search and replace, Expand and Collapse tree
nodes.
The area to the right shows a four-column table with data relative to the selected tree node:
 Node Name. Description to identify the file node.

 Node Value. It shows the value of the data shown in the previous column. The data could
be edited if valkind is Set (green background).
 Associated list of values. In case the value shown has an associated list of values, it
will be in this column. The list value can only be edited if data valkind is Set.
 Node information. It shows information on the data shown in Node Value column, such
as: type of data, FC, valkind, etc.
Data shown in table are dynamically validated when edited (see par 2.1.4 Data validation).
Clicking the mouse right button displays a contextual menu. Use this menu to:
 Copy: to copy the text shown.

 Paste: this option is only active on Node Value column.
 Expand: this option is only active when the menu is accessed from Node Name column.
It expands table nodes, except nodes: SCL, IED, Server, LDevice and AcessPoint.
 Collapse: this option is only active when the menu is accessed from Node Name column.
It collapses table nodes.
2.1-2
BCID1207A
2.1.2 Menu Options

Available options from the application
main menu are as follows.
- Open a CID, SCD or ICD file:

select Open in the File menu or
use the Tool bar button .
- Save CID, SCD or ICD file: select
Save in the File menu or use the
Tool bar button .
Every time changes are introduced

into the open file, parameters
configRev or paramRev are
updated before saving the file. For
more information please refer to
section 2.1.5 ConfigRev and
paramRev parameter index
update.
- Save CID, SCD or ICD file as a

new document: select Save As in
the File menu to save the
document with a name in the
selected location.
2.1-3
BCID1207A
- Print the document: select Print in the File menu or use the Tool bar button At the
left of the screen, select the output option, namely, if data are to be printed (option=print)
or exported to a text file (option Save as text document).
At the left of the screen, select the output option, namely, if data are to be printed (option=print)
or exported to a text file (option Save as text document).
At the right of the screen, also select which data are to be printed: the entire tree, only the
nodes selected or the entire tree up to DOI or DAI data level. The contents of results panel in
the main screen can also be printed.
- Close the application: this option closes

the application. In case changes have been
introduced and not saved before, a dialogue
box will ask whether you want to save said
changes.
- Copy cell data: select Copy in the Edit menu or press keys Ctrl+C. This option allows
copying cell data of the table at the right. To do this, the cell must be selected but not in
edit mode.
- Paste data into cells: select Paste in the Edit menu or press keys Ctrl+V. This option
allows pasting copied data of the table to the right into cells. To do this, the cell must be
selected but not in edit mode. It is important to take into account that with this action the
previous data will be lost.
2.1-4
BCID1207A
- Validate current file: select Validate in the Tool menu or use the Tool bar button
.This option validates the document and shows Results window errors. For additional
information, refer to par 2.1.4 Data Validation.
- Change tree view from CDC mode to FC mode: select Base FC in the View menu or
use the Tool bar button . It allows changing the tree view mode, from CDC to FC
mode.
- Change tree view from FC to CDC mode: select Base CDC in the View menu or use
the Tool bar button . It allows changing the tree view mode, from FC to CDC mode.
This action may cause loss of information relative to colouring, and a screen similar to
that of the above action asks for confirmation.
2.1-5
BCID1207A
- Show the results: select

Results in the View menu, use
the tool bar button or the
button at the bottom left area of
the screen where "Results" is
written. It allows displaying the
messages and errors written in
the sliding window.
- Filter FCs: select Filter FCs in

the View menu. This option is
only active when the tree is
shown in FC mode. It allows
selecting the FCs to be shown
in the tree.
- Change SCD element: select Change SCD element in the View menu or use the tool bar
button . This option activates when detecting the file is of .scd type.
The user can at any time gain access to the IEDs screen to change data to be read or
edited. In order to select another element, the user will be asked to save the changes
made previously.
Both when selecting this option or when opening a file, a selection window is displayed
with the set of IEDs the CID of which are contained in the .scd, as well as an input of
“generic data” (Nodes Private, Header, Substation, Communication).
- Help: select Help in the Help menu or use key F1. This Help file can only be accessed in
case it exists, otherwise, nothing will be displayed by key F1 and the Help menu option
will be disabled.
2.1-6
BCID1207A
2.1.3 Edit Data

Data can be edited from various application screens.
Data with the attribute valkind equal to Set and specific attributes (cells with green background
in the table to the right or enabled lists of values) can be edited on the main screen. Click on the
cell to edit and enter the new values when the cell background colour changes. If data belongs
to a list of values, a new value of said list must be chosen without the possibility to enter any
value through the keypad.
In the case of the next screen, the setting attribute ‘set-Mag’ and descriptor ‘d’ could be
changed.
In the following case, descriptor ‘d’ could be changed and one of the possible values in the list
could be selected as attribute ‘set-Charact’.
2.1-7
BCID1207A
On the DataSets Configuration screen, data can be edited in three different manners:
 Dragging data from the tree on the left to the tree on the right.
 Dragging FCDA data between dataSets in the tree on the right.
 Adding/deleting elements through the contextual menu or applicable button.
On Import Datasets, by contrast, elements are added from the tree on the right to the tree on
the left using the button .
If two different files are being compared, current file data can be edited both clicking the symbol
whereupon the external value will be copied and clicking second column cells (Actual
Value) in rows where data can be copied.
Finally, on Configuring communications data all data can be edited by clicking the applicable
cell. Values such as IP or MAC values, must comply with a specific format; otherwise, the user
will be informed and changes will not be saved. To edit datSet data, the new value must be
selected from the drop down list displayed when clicking said data, no value can be entered
otherwise.
2.1.4 Data Validation

The validation process of all file data can be done from different application points:
- When opening a new file a first file validation can be done.

- When saving a file.
- When selecting the option validate on the main screen.
Also, specific file areas can be validated whenever editing data requiring it and when
configuring dataSet data on the applicable screen.
2.1.4.a File Validation

This process performs a first validation against the SCL scheme. After this, all links between
document nodes will be correct and all document data will be the correct type (special treatment
for Enum, Boolean, Check, Tcmd Dbpos, setMag, and setVal types of data). Then, LDevice
nodes with undefined attribute “inst” are detected and that no nodes are repeated at the same
level within the IED node. Finally, the existence and consistency of IED names is checked,
namely, that IED node attribute “name” have their reference in the “communication” area of the
current file.
2.1.4.b Dynamic Data Validation

After editing data requiring validation, an automatic validation process of the data entered takes
place.
2.1-8
BCID1207A
2.1.4.c DataSets Validation

For information on this validation, please refer to section 2.2.3 DataSets Validation.
2.1.5 ConfigRev and ParamRev Parameter Index Update

These parameters are updated just before saving the file. Parameter format is:
INDEX YEAR.MONTH.DAY.HOUR:MINUTE:SECOND [EDITOR DATA]
ParamRev: will be changed in every LD any time a real change is produced (in those “set” type
attributes, namely, those with fc: CF, SP, DC and SG). A real change is a change between the
data value of that node in the source file and in the file to save. Every attribute change is a new
change even in the same node. LLN0 node paramRev must be changed every time any node is
changed.
ConfigRev: will be changed every time the logic configuration, datasets, or any Report Control
Block or Goose Control Block parameter is changed.
The INDEX number increases by one unit every time either paramRev or configRev is updated.
This means that the index is used as a counter of the number of changes, whether configuration
or relay parameterisation changes.
When a node (the paramRev of which must be changed) attribute is edited, the actual index
number (common to Ldevice, that, at first, will be the maximum value between LLN0 node
paramRev and configRev) is increased by one unit. This new index is used to create the new
paramRev of the changed node and is also the index used for increments upon any other
change (whether in the same node or not) and update the applicable paramRev.
2.1-9
BCID1207A
In the end, the index value of LLN0 node paramRev or ConfigRev (depending on where the
changes occurred) will coincide with the maximum value of LDevice node paramRev or
configRev (as applicable).
As an example:
Starting situation:
LLN0- paramRev 960 2008.11.11..........
LLN0- configRev 55 2008.11.11.........
Changes in:
RCB
ATCC-namplt-d
GAPC-namplt-d
Result in paramRev and ConfigRev of every node and of LLN0

starting index = MAX(960.55) = 960
Change in RCB:
index = 960 +1 affects LLN0 configRev
Change in ATCC-namplt-d:
index = index +1 = 961 +1
ATCC.paramRev = 962 2008.11.12..................
Change in GAPC-namplt-d:
index = index + 1 = 962 + 1
GAPC.paramRev = 963 2008.11.12...................
Change in LLN0.configRev = 961 2008.11.12...................
LLN0.paramRev = 963 2008.11.12...................
2.1-10
BCID1207A
2.2 DataSets

2.2.1 Introduction .............................................................................................................. 2.2-2
2.2.2 DataSets Configuration ............................................................................................ 2.2-3
2.2.3 Import DataSets ....................................................................................................... 2.2-5
2.2.4 Validate DataSets .................................................................................................... 2.2-6
2.2.1 Introduction
In standard 61850, "dataSet" is a group of data. Other service control data (e.g. Goose Control
Block, Report Control Block...) make reference to said "group" through the dataSet name with
no need to specify individual dataSet data. As a general rule these groups are used in data
transmission communications. DataSet data also comprise references to IED data, attributes or
data model class.
Data configured in a dataSet are:
The maximum number of dataSets that can be configured depends on the model and will be
specified by the attribute "max" of the IED service "ConfDataSet".
Every dataSet must have a name (minimum 1 character, space characters are not valid) and
can have a description associated. The dataSet name will be used for the rest of the CID to
refer to that dataSet, namely, the association of a dataSet to a ReportControl Block will be done
through the dataSet name. When the data-Set name is changed, it is changed at all places
where reference to it is made.
DataSet data are references to model data. These references can be classes (LnClass), data
or attributes. Only data with functional constraints of the type status data (ST), measurements
or analog values (MX), settings (SP), substitution data (SV) and configuration data (CF) can be
grouped in a dataSet.
There is an attribute designated "fc" (functional constrain) that defines the attribute function.
Every attribute of data model 61850 has an associated functional constraint. Dataset data,
whether attributes, data or classes (Logical Nodes) must be linked to a specific fc. In case of
attributes, the fc is the attribute proper. In case of Logical Nodes (Logic node classes) the user
will be prompted on the type of fc associated to said dataSet attribute.
The number of valid attributes in the same dataSet is also limited by the device capabilities.
Said number can be read from attribute "maxAttributes" in the "ConfDataSet" node on the area
where IED services are defined.
2.2-2
BCID1207A
2.2 DataSets
2.2.2 DataSets Configuration
Select DataSet configuration in the Tools menu or use the tool bar button .
DataSets can
be configured
from a data
source tree to
the left of the
screen, created
from the
Logical Nodes
already
configured in
the file,
including all
node data and
all data
attributes.
This tree is arranged with data grouped as a function of its “fc”. DataSets and dataSet data
(designated FCDAs in the standard) can be configured from this screen. When a document with
various Ldevice is being configured, the combo at the top right of the screen must be enabled to
select the Logical Device to be configured.
The following options are available to configure DataSets:
- Create a new dataSet. This option is also available from the contextual menu of the tree
to the right.
- Rename dataSets. To rename a dataSet click the dataSet name in the tree on the right
after selection (the same as for Windows Explorer).
The name and the description can be

edited directly. The dataset name may
not contain blank spaces, therefore,
the text after the first blank space
character will be considered part of
the description. References to that
dataSet in the CID document will be
modified by the new value.
2.2-3
BCID1207A
- Add elements to a dataSet. To add new elements to the dataSet, select an element of
the tree on the left with the mouse and drag it on an element of the tree on the right.
There must be taken into account that by dragging on "dataSet" type node directly,
dragged elements will be added to the end of already existent dataSet elements, in the
same order than have been selected. On the contrary, by dragging on an element that
occupies any position within the dataSet, the dragged elements (in the same order as
they were selected) will be placed in that position, moving the element on which they are
dragged and the rest of the elements towards later positions in the list. If elements are
dragged from a dataSet to another, they will be added in the same way. In this case take
into account that dragged elements of the source dataSet are not deleted from the source
dataSet, but are “copied” to the new dataSet.
- Sort dataSet elements. DataSet elements can be sorted. Just drag the elements with
the mouse to the new position. Dragged elements will be placed in the new selected
position (in the same order as they were selected), moving the rest of the elements to
subsequent positions. In this case, elements are not “copied”, but moved. To move an
element to the end of the dataset, it must be dragged on the "dataSet" node.
- Delete an element. This option is also available from the contextual menu of the tree on
the right. DataSets must be deleted element by element, as there could be connections
with GooseControl, Report Control, etc., and the operations must be confirmed. In case
of the FCDAs the selection of several elements is allowed.
- Import DataSet. This option allows adding dataSets and FCDAs of other files to the file
being edited. See section 2.2.3 Import DataSets.
- Erase buggy FCDAs. If when opening the dataSets configuration window, a FCDA
validation error is produced (Some FCDA reference is not found in the configured part of
the file [there is no such IED’s LN] or references are not found in DataTypesTemplates)
this button will be enabled and options:’ Add a new data-Set’, ‘import dataSet’, ‘see
dataSet detail’ will be disabled. Clicking ‘Erase buggy FCDAs’ deletes all buggy FCDAs
and options: ’Add a new data-Set’, ‘import dataSet’, ‘see dataSet detail’ will be enabled.
- Enable Colour FCDAs refs. Colours FCDA referenced elements in the tree on the left.
- Disable Colour FCDAs refs. Removes the colour of FCDA referenced elements in the
tree on the left.
- See dataSet detail. Shows a summary of the actual configuration of all document
dataSets in the movable window on the lower part of the screen.
- Validate dataSet. Allows validate on request the configuration of document dataSets.
Clicking this option displays the results on the movable window at the lower part of the
screen. See section 2.2.4 Validate DataSets.
A valid configuration is required to carry out any operation to create/delete both dataSet and
FCDAs, as the application will not allow the execution until correct data of the present dataSet
configuration are available.
2.2-4
BCID1207A
2.2 DataSets
2.2.3 Import DataSets

First, the document from which dataSets are imported must be selected, whether SCD or CID.
DataSets of the selected document will be displayed, no matter the LDevice to which they
belong, in the tree on the right, which allows for multiple selection. DataSEts of the target file
are displayed on the left part of the window.
Data can be imported, using the button , provided they are valid, as when data are imported
they are validated to check the node exists at the target.
Clicking the button displays data to check the capacity and the present configuration of file
dataSets.
2.2-5
BCID1207A
2.2.4 Validate DataSets

Below are the operations carried out during dataSets validation:
1) Getting the parameters that define the maximum number of IED’s dataSet (parameter
‘max’ -> SCL/IED/Services/ConfDataSet/max), as well as the number of dataSet’s
Attributes (parameter ‘maxAttributes’ -> SCL/IED/ Services/ConfDataSet/
maxAttributes). If these parameters are not well defined in the file being edited,
dataSets cannot be configured.
2) Validate that the number of configured dataSets is lower than parameter ‘max’.
3) Validate that FCDA parameter ‘ldinst’ and parameter ‘inst’ of the Logical Device to
which they belong coincide.
4) To get the number of FCDA’s Attributes, call on DataTypeTemplates and add up all end
elements (DAIs) defined or, what is the same, the maximum capacity of that reference.
5) Prior to create and add a new FCDA validate that the parameter maxAttributes is not
exceeded and that the reference to the Logical Node exists in the configured part of the
file (an instance of the Logical Node within the IED), otherwise, the operation will be
cancelled.
2.2-6
BCID1207A
2.3 RDBs and GCBs

2.3.1 Introduction .............................................................................................................. 2.3-2
2.3.2 RCBs Configuration ................................................................................................. 2.3-3
2.3.3 GCBs Configuration ................................................................................................. 2.3-4
2.3.1 Introduction
Previously created dataSets (see section 2.2
DataSets), can be assigned to data transmission
services Report Control Block (RCB) and Goose
Control Block (GCB).
ZIV devices are provided with 7 Report Control

Block with buffer (BRCB), 7 Report Control Block
without buffer (URCB) and 3 Goose Control Block
(GCB).
RCB is a point-to-point service such that when a

client is subscribed to the same, only the client
receives the "reports" generated by the device.
This is the service normally used to ‘upload’ level 1
device data to level 2 devices.
GCB is a multicast service, in which data is

‘published’ in a MAC multicast address to which
anyone can access. This is both a horizontal
communications service (between level 1 devices)
and a vertical communications service (between
level 1 and 2 devices).
These services are represented in the IED’s zero

logic node LLN0.
2.3-2
BCID1207A
2.3 RDBs and GCBs
2.3.2 RCBs Configuration

The following Report C o n t r o l Block settings shown in a green background can be changed:
 bufTime: buffer size used to group changes in a single report in milliseconds.

 desc: RCB name.
 rptID: RCB identifier, by default, the IED’s RCB path.
 intgPd: cyclic report transmission period in milliseconds.
 confRev: revision nr. of RCB configuration.
 datSet: it can only be chosen from the values
displayed in the window to the right.
 TrgOps: parameters defining the reason for
sending a report.
o period: periodicity report.
o dchg: changed data report.
o qchg: changed data quality report.
o dupd: updated data report.
2.3-3
BCID1207A
2.3.3 GCBs Configuration

Goose Control Block parameters that can be edited appear on a green background:
 desc: GCB name.

 confRev: GCB configuration revision nº.
 appID: text string for Goose identification (it is
normally designated as GoID to be differentiated
from communications parameter APPID).
 datSet: only the values displayed on the window to
the right can be chosen.
These parameters will define the Goose message body, parameters defining the Goose
transmission mode being configured in the communications section.
2.3-4
BCID1207A
2.4 Gooses

2.4.1 Receive Goose Messages ....................................................................................... 2.4-2
2.4.2 Configure an incoming Goose ................................................................................. 2.4-2
2.4.2.a setRef Attribute Configuration ............................................................................ 2.4-3
2.4.2.b intAddr Attribute Configuration ........................................................................... 2.4-6
2.4.2.c Configuration through ZIVerlog® ......................................................................... 2.4-6
2.4.1 Receive Goose Messages

Standard IEC61850 defines the send Goose service through GCB, but not the receive Goose
data.
This is why, by IEC61850 standard criteria and in collaboration with users and other
manufacturers, a totally valid Goose subscription and receive criteria has been created. So, by
subscription to a Goose is meant the Goose message identification in the network and then take
the desired data.
Procedure to configure an “incoming” Goose message:
- Subscribe to a Goose and identify the desired data.

- Map the desired data information to IEC61850 data of our model.
- Assign the IEC61850 data just remapped of the Goose data to an internal relay signal.
2.4.2 Configure an incoming Goose

The necessary parameters to identify a Goose and send the Goose desired data to a data of
our model are configured editing directly the ICD/CID on node GIGGIO1.
ZIV relays have a node GIGGIO1 with 40 data InRef (InRef01-InRef40), which allow a
maximum of 40 subscriptions of the same Goose or different Gooses.
In this way, 40 data from the same Goose, 1 data from 40 Gooses or combinations up to a
maximum of 40 data can be taken.
Each data InRef has 2 attributes: setRef and intAddr.
2.4-2
BCID1207A
2.4 Gooses
2.4.2.a setRef Attribute Configuration

setRef attribute allows to identify a Goose and select desired data from the same. By default,
the attribute will contain: MAC:;APPID:;GCBREF:;GOID:;POS:; where:
 MAC: will be the target MAC where the Goose to be subscribed to will be ‘published’. The
range for a GOOSE, will be according to IEC61850-8-1 from 01-0C-CD-01-00-00 to 01-
0C-CD-01-01-FF.
 APPID: single identifier of the system to which the Goose belongs. It is a hexadecimal
value ranging from 0000 to 3FFF.
 GCBREF: GCB’s IEC61850 reference of the Goose to be subscribed to. It will be of the
type: DeviceLD1/LLN0$GO$gcb01.
 GOID: text string to identify the Goose.
 POS: position of the attribute involved in the Goose message.
E.g. If a 2 data dataset (each comprising 3 attributes: stVal, q and t) is sent by a Goose, and
data 2 stVal is chosen, we must write POS:4 as it is the fourth attribute in the dataset.
Subscription to Input Gooses can be done manually, filling in the box according to the data
format described above, or else in graphic form, opening the CID associated to the Gooses
source IED, selecting the Goose to which we want to subscribe and dragging the value to the
inRef box in Configuración.
To activate the graphic configuration, select option Configure Subscriptions to Gooses within
the application Tools menu.
The tool to configure subscription to gooses looks like the window below:
2.4-3
BCID1207A
A tree with the settable data within the node GIGGIO is shown to the right.
The left part is empty and will display the output Gooses of the CID associated to the IED to
which we want to subscribe.
 Configuration Process
1. Select the data source file:
Click Open file to select the CID source of the Gooses to which we want to subscribe. It
can be a CID or an SCD file: in this case, select one of the CIDs contained in the same
and then click Accept, as shown in the following figure:
If an open CID has no output Gooses to which we can

subscribe, the following warning screen is displayed.
If the file has been correctly open, the output gooses available in the IED are displayed in
the form of a tree to the left of the screen.
2.4-4
BCID1207A
2.4 Gooses
2. Selection of configuration data.
Output Gooses available for subscription are displayed on the right panel. In the tree of
the right panel navigate to the InRef data that we want to configure.
With the mouse, select the source Goose in the left panel and drag to destination (box
setRef). If there is no error, the value of setRef updates in the box.
There must be taken into account that the dragged value may only be associated to the
setRef data. When the Goose is being dragged and we pass over a setRef box, the box
background changes colour to indicate that we can release the Goose on it.
 Other Possible Operations

Close an Open CID File
By clicking the menu option Close File; the open CID to the left closes and the tree is
cleared. This operation is carried out automatically when opening another file.
Clear a Subscription to Goose
Move onto the box setRef that
we want to clear and click the
right button of the mouse. A
contextual menu is displayed
with the option Clear data.
2.4-5
BCID1207A
2.4.2.b intAddr Attribute Configuration

Attribute intAddr is used to remap data information of the subscribed Goose, to the model data
desired.
Mapping is only possible to the 4 types of GIGGIO1node data: Ind01-Ind40 (Single Signals),
DPIn01-DPIn20 (Double Signals), IntIn01- IntIn10 (Integers) and AnIn01-AnIn10 (analog
magnitudes).
Writing must be in ACSI format (Node.Data.Attribute[fc]). E.g., to map a Goose double signal,
write: GIGGIO1. DPInd01.stVal[ST].
2.4.2.c Configuration through ZIVerlog®

Once a Goose has been identified and the desired data has been identified and mapped to the
IEC61850 data of our model, it must be assigned to an internal relay signal in order that it can
be used. The
ZiverCid® logic
editor, the
ZIVerlog® will be
used.
Through the
Communications
menu, the
ZIVerlog® has a
61850 section
where node
GIGGIO can be
configured with the
same ‘target’ data
as for ICD/CID
(Ind, DPInd, IntIn
and AnIn).
2.4-6
BCID1207A
2.4 Gooses
An internal relay signal or user signal with no predefined value must only be assigned to the IEC
61850 reference to which a value has been given in intAddr.
This selected signal will take the same source data of the Goose to which we subscribed in
setRef.
2.4-7
BCID1207A
2.4-8
BCID1207A
2.5 Communications

2.5.1 Edit Communications ............................................................................................... 2.5-2
2.5.1.a General Communications Data .......................................................................... 2.5-2
2.5.1.b Goose Communications Settings ....................................................................... 2.5-3
2.5.1 Edit Communications
Select Configure Communications Settings from the Tool menu or use tool bar button .
The communications data form screen is shown below. Only correctly defined parameters will
be displayed, and the following settings can be edited:
2.5.1.a General Communications Data

- IED name: logic device name. IEC61850 standard suggests creating a name made up of
the substation name made up of the substation name, device bay and the bay voltage
level. This value must be unique in the file.
- IP: device IP address. Should the IP configured in the CID do not coincide with the
physical device address, the CID will not be validated by the relay. Valid format is a must.
- IP-SUBNET: device working subnet. Valid format is a must.
- IP-GATEWAY: external access IP address. Valid format is a must.
- OSI-TSEL: OSI protocol parameter (purely descriptive).
- OSI-SSEL: OSI protocol parameter (purely descriptive).
- OSI-PSEL: OSI protocol parameter (purely descriptive).
- OSI-AP-Title: OSI protocol parameter (purely descriptive).
- OSI-AE-Qualifier: OSI protocol parameter (purely descriptive).
2.5-2
BCID1207A
2.5 Communications
2.5.1.b Goose Communications Settings

- ldInst: for each physical device, there could be one or more logic devices. In case of ZIV
devices, only one instance designated LD1 is available, and can be edited.
- gcb: for each logic device, there could be one or more GCB. In case of ZIV devices, 3
GCB are available, the parameters of which can be accessed through 3 tabs.
- VLAN-ID: identifier of the Virtual LAN to which the Goose message is sent. It is a
hexadecimal value ranging from 000 to FFF.
- VLAN-PRIORITY: parameter to define the message priority. It can be set between 0
(lowest priority) and 7 (highest priority).
- MAC-Address: target MAC where the Goose message is to be published. According to
IEC61850-8-1 it ranges from 01-0C-CD-01-00-00 to 01-0C-CD-01- 01-FF.
- APPID: sole Goose system identifier. It is a hexadecimal value ranging from 0000 to
3FFF.
- desc: descriptive GCB name.
- confRev: revision nº of GCB configuration.
- appID: text string identifying the Goose (as a
general rule it is designated GoID to differentiate
from the communications parameter APPID).
- datSet: it may only be selected from the values
shown in the pull down menu of the window to the
right.
2.5-3
BCID1207A
2.5-4
BCID1207A
2.6 CIDs

2.6.1 Compare CIDs ......................................................................................................... 2.6-2
2.6.1.a Functional Constraint (FC) Tree ......................................................................... 2.6-3
2.6.1.b Copy Differences between Files ......................................................................... 2.6-3
2.6.1 Compare CIDs
Select Compare CIDs from the Tool menu or use the tool bar button .
This function is used to compare IED’s parameters and configuration based on their CIDs.
The screen to compare CIDs is shown below:
This option allows comparing the file being edited with any other file (in case of SCD type files,
also with other SCD’s IED or other CID). There must be taken into account that with this option,
XML files are not being compared, but CID’s logic node attribute settings that are being edited
are compared with attribute settings of the selected CID file. Only the settings with different
values and editable will be shown.
The file comparison process consists of two phases:
 First phase: IED logic configuration settings are compared (name, version, lrc and size).
 Second phase: Ldevice attributes are compared.
The screen with the configuration results will be displayed only when there are differences
between them, otherwise, an informative
message is displayed.
The following icons could appear in the last column of the table in the CID comparison screen
Means that the value can be copied from the external value to the present value.
Means that the external value is not valid, therefore, it cannot be copied to the present value,
the value can be out of range, the value is not allowed within valid values of the CID being
configured, etc.
Means that the values have been copied/edited and are the same.
Means that values cannot be edited.
2.6-2
BCID1207A
2.6 CIDs
2.6.1.a Functional Constraint (FC) Tree

If the tree in the main screen is sorted
in FC mode, this arrangement will be
kept in the present window. In this
case, the Filter FC button will be
enabled, that will allow choosing the
FCs to be shown in the differences
screen.
The following form is used for filtering.
2.6.1.b Copy Differences between Files

Settings that can be copied through the applicable button are:
1) Attribute settings different from the settings of the CID being edited can be copied,
provided they are settings to be copied, they are valid and the setting is editable
(valKind=Set). Apart from being copied, settings detected as differences and shown in the
screen can be edited manually. These settings will be validated automatically before
editing is finished.
2) Regarding the logic, only the complete logic node “Private” can be copied if the IED\type
coincides in both cases. Otherwise, nodes cannot be copied. In this case, copying implies
deleting that node Private first and then register the complete node again just as it is in
the comparison file.
2.6-3
BCID1207A
2.6-4
BCID1207A

2.7.1 Arrangement of the Settings Tree............................................................................ 2.7-2
2.7.1.a Filters for FC mode ............................................................................................. 2.7-2
2.7.2 Search and Replace ................................................................................................ 2.7-2
2.7.3 Expand and Collapse Nodes ................................................................................... 2.7-3
2.7.3.a Expand Tree Nodes ............................................................................................ 2.7-3
2.7.3.b Collapse Tree Nodes .......................................................................................... 2.7-3
2.7.3.c Expand / Collapse in Edit Screen ....................................................................... 2.7-3
2.7.1 Arrangement of the Settings Tree

For easy data handling, the user is given two different modes to arrange the settings tree in the
main screen:
 Common Data Classes (CDC)

 Funcional Contraints (FC)
With this arrangement data is adapted and accessibility is made easier as a function of the type
of the application user. Default tree mode is configurable through the tool configuration option.
2.7.1.a Filters for FC mode

When working with the tree in FC mode in the main screen or in the CID comparison screen,
the user can filter as a function of the setting’s FC.
2.7.2 Search and Replace

Click Search and Replace in the Edit menu, display the contextual menu by clicking the right
button of the mouse or use the tool bar button . This option allows the user to quickly access
/ edit the desired data.
If several tree nodes

have been selected,
clicking this option
displays a screen
similar to the screen
below and only the
last selected node will
keep selected, which
will be highlighted in
red in the tree.
The search and

replace screen is
shown at the right:
2.7-2
BCID1207A
- Search: will search through the left part of the tree if it contains the word entered. The
search can be done through the full structure generated from the file or from the selected
node. The search is not case sensitive to upper and lower case.
- Replace: will replace the searched element with the new element entered. This operation
may only be carried out if the place in which data is to be replaced is editable and the
type of data is valid for said data; otherwise, the replace button will not be enabled.
- Replace all: will replace all matches with the new element entered provided that said
data is editable and valid.
IMPORTANT: Replace / Replace all, are case sensitive for the required element; in case it
is not written exactly the same, that node will not be detected.
After completion of the required operations, clicking the “O.K.” button, keeps the last
searched/replaced node selected and data are loaded into the edit screen
2.7.3 Expand and Collapse Nodes

2.7.3.a Expand Tree Nodes
Select Expand tree Nodes in the edit menu, display the contextual menu by clicking the mouse
right button or use the tool bar button .
This option allows expanding the selected node in the tree to the left to the maximum depth.
Certain nodes can be expanded (as a function of their type) In the edit screen through the
contextual menu.
It is important to take into account that the expansion of certain nodes could be quite long, e.g.
SCL, AccessPoint, IED, Server or LDevicenode expansion.
2.7.3.b Collapse Tree Nodes

Select Collapse tree Nodes in the edit menu, display the contextual menu by clicking the mouse
right button or use the tool bar button .
This option allows collapsing the selected node in the tree to the left. Nodes can also be
collapsed in the edit screen through the contextual menu.
2.7.3.c Expand / Collapse in Edit Screen

The application also allows expanding and collapsing nodes in the edit data screen, for quick
access to all element data, as attributes and child nodes.
This option is not available for nodes with excessive contents as are: SCL, AccessPoint, IED,
Server or LDevice. These nodes have a large volume of data and high running time so the
intended quick access to data is not achieved.
Access to this option is gained through the contextual menu by clicking the mouse right button
on the first column of the edit screen.
2.7-3
BCID1207A
2.7-4
BCID1207A
2.8 Edit Logic

2.8.1 Introduction .............................................................................................................. 2.8-2
2.8.1 Introduction
Clicking the programmable logic configure option displays the configuration module named
ZIVerlog®. Before launching this module, the user will be warned that in order to proceed with
the operation the changes introduced until then must be saved in the document. Then the user
can decide to continue with the operation or abort the same.
In turn, once the logic configuration is completed and the changes saved into the document, the
application validates the changes and displays the result of the operation in the applicable
window. Logic configuration data is shown in the IED’s Private node in the main ZiverCid®
screen.
To carry out this operation, the ZivercomPlus® database must be installed. However, the
complete ZivercomPlus® application is not needed.
For additional information, refer to Chapter 3. Control Configuration Management
2.8-2
BCID1207A
Chapter 3
Managing
Control
Configurations
Content
3.1 Introduction
3.2 Getting Started
3.3 File Menu
3.4 Input / Output Logic
3.5 Configuration-Associated Logic
3.6 Defining Resources
3.7 Communications
3.8 HMI
3.9 Graphical HMI
3.10 Profile Descriptions
3.11 Documentation
3.1 Introduction

3.1.1 Introduction .............................................................................................................. 3.1-2
3.1.2 Functions ................................................................................................................. 3.1-2
3.1.2.a Creating a Configuration ..................................................................................... 3.1-2
3.1.2.b Editing a Selected Configuration ........................................................................ 3.1-2
3.1.2.c Generating Files ................................................................................................. 3.1-3
3.1.2.d Controlling and Checking Configuration Data .................................................... 3.1-3
3.1.2.e Validating a Configuration................................................................................... 3.1-3
3.1.2.f Importing Data from Other Logic Configurations ................................................ 3.1-3
3.1.2.g Controlling and Managing Configurations .......................................................... 3.1-3
3.1.1 Introduction
The ZIVerlog® configuration module is designed to enhance the functionality of the equipment,
enabling the creation of new user logics, command items, configuration of equipment inputs,
outputs and LEDs, configuration of different communication protocols, etc.
This module lets the user design a configuration, and load and edit an existing configuration.
The ZIVerlog® configuration module is installed together with ZiverCid® and is accessed
through it. The ZiverCid® program supplies all the necessary information (profile, configuration,
file to be generated, etc.) to ZIVerlog® when it is called, and ZIVerlog® in turn provides
ZiverCid® with the files that it should send to the equipment.
3.1.2 Functions
3.1.2.a Creating a Configuration
A completely new configuration can be created with the configuration module, either with new
user-created items or using existing items from other configurations. The parts that can make
up the configuration include:
 Configuration of input, output and LED logics (front) in traditional format.

 Configuration of any type of logic in the equipment: inputs, outputs and front (extension of
traditional logic), protection and control. The execution priorities of the different types of
logic in the equipment are:
o Inputs, protection and outputs: High priority.
o Control: Average priority.
o Front: Low priority.
 Definition of new resources for the equipment:
o Digital signals.
o Magnitudes.
o Settings.
o Constants.
o Command items.
 Configuration of different protocols used by the equipment for communications.
 Configuration of data to appear in the HMI.
3.1.2.b Editing a Selected Configuration

You can edit all the items that determine the design of a configuration, namely:
- Editing, adding or deleting logic elements.

- Editing the logic gates (also called opcodes) used in logics.
- Editing the gates' input and/or output signals.
- Alter the order in which logic elements are processed and the logic gates that comprise
the logics.
- Editing settings.
- Editing resources.
- Editing data from the different communications protocols.
- Editing the data that will appear in the HMI.
3.1-2
BCID1207A
3.1 Introduction
3.1.2.c Generating Files

The configurations module generates several files:
- A binary file with the configuration information so that the ZiverCid® program can send it
to the equipment. The file name is determined by the program.
- A configuration file (CFP extension) supplementing the profile data to be used by the
ZiverCid® program to communicate with a piece of equipment. This file is also sent to the
relay, so that when the ZiverCid® program communicates with the equipment, the
configuration loaded in the equipment can be retrieved.
3.1.2.d Controlling and Checking Configuration Data

The configuration module establishes control over the configuration data, so that the application
can check that all the data are correct according to the equipment's profile before sending the
configuration to the equipment.
3.1.2.e Validating a Configuration

All configurations are validated according to the equipment's current profile when loaded in the
ZIVerlog® module.
3.1.2.f Importing Data from Other Logic Configurations

The ZIVerlog® module makes it possile to import logics, parts of logics, resources, and
commands separately from other configurations.
3.1.2.g Controlling and Managing Configurations

For each configuration a checksum is created to enable its management and control.
3.1-3
BCID1207A
3.1-4
BCID1207A
3.2 Getting Started

3.2.1 Loading and Validating the Profile ........................................................................... 3.2-2
3.2.2 Start Menu ............................................................................................................... 3.2-4
3.2.3 Operating Method (Mouse & Keyboard) .................................................................. 3.2-4
3.2.4 Information Displays ................................................................................................ 3.2-5
3.2.5 Using the Controls ................................................................................................... 3.2-5
3.2.6 Selecting Signals ..................................................................................................... 3.2-7
3.2.6.a Signal Selection Screen....................................................................................... 3.2-7
3.2.6.b Signal Types ........................................................................................................ 3.2-8
3.2.6.c Signal Restrictions ............................................................................................... 3.2-8
3.2.1 Loading and Validating the Profile

The ZiverCid® program can pull up the ZIVerlog® configuration module in edit or validation
mode. In both cases, the ZIVerlog® module loads the profile as per the instructions received.
This profile determines multiple aspects of the ZIVerlog® module, such as:
- The parts of the configuration that may be established. This involves disabling parts of
the menu.
- The logic types that may be configured.
- The valid opcodes.
- The equipment's digital signals that the user may use.
- The equipment's analog signals that the user may use.
- The number of digital signals the user may create.
- The number of analog signals the user may create.
This implies that a configuration may be valid for several different pieces of equipment, but if it
has been created with a profile, has been validated, and is correct, it may not be valid any
longer with another profile from another piece of equipment. The reason for this is that there are
signals that may not exist in the new profile, or certain opcodes or logic types are not allowed,
etc.
As a result, after loading the equipment profile, when a configuration is loaded, it is necessary to
recheck and control multiple configuration aspects before validating it for the profile. This can
involve editing the configuration.
The checks made are described below:
- Check of the maximum number of digital signals created by the user.

- Check of the maximum number of analog signals created by the user.
- Check for existence of logic types that are not valid for the current profile.
- Check for the use of opcodes that are not valid for the current profile.
- Check for the existence or validity of all signals (digital and analog) used in the logic.
- Check for the existence and validity of all signals used in the command items.
- Check for the existence of all digital and analog signals used in the different protocol
sections (events, control changes, measurements, commands, counters, etc.).
3.2-2
BCID1207A
3.2 Getting Started
Incompatibilities may be found during loading. In such cases, the configuration module decides
to perform a series of actions. Possible incompatibilities, as well as the action to be performed
in each case by the ZIVerlog® are described below:
- Signal does not exist or is not valid with the new profile (see section Signal
restrictions, for more information about non-valid signals). Different actions are performed
depending on what parts of the configuration are affected by this incompatibility:
o Logic: the signal is deleted leaving the opcode incomplete (the opcode will appear
in red) and highlighting the error.
o Command item: the command item is deleted and the error is highlighted.
o Communications protocols: any label associated with the signal in the different
protocol functions (e.g. events, measurements, meters, commands, etc.) is deleted
and the error is highlighted.
- Number of user-defined digital and analog signals above the permitted amount
with the new profile:
o Signals in excess of the maximum are deleted and the entire configuration is
checked. If one or more such signals is used in a section of the configuration, the
program will proceed as described in the previous point.
- Invalid logic type:
o The records for the invalid logic type are deleted and the error is highlighted.
- Invalid opcode:
o The error is highlighted.
After performing all the

checks, if configuration
corrections were
required, a screen similar
to the one at right is
displayed with the
corrected errors.
3.2-3
BCID1207A
3.2.2 Start Menu

As mentioned earlier, the equipment profile defines what parts of the configuration can be
created and/or edited. This has a direct influence on the menu options the user will see in the
ZIVerlog® configuration module.
Depending on the equipment profile, the following configuration sections may or may not be
displayed in the menu:
- Input, output and LED logic

- Logic
- Communications:
HMI
Protocols:
PROCOME
DNP3
MODBUS
The profile also defines which information for each protocol is user-viewable: events, control
changes commands, measurements, etc.
If a file with the CFP extension does not include a configuration or the configuration is not valid,
the module will start up with the entire menu disabled, except for the following options:
- File:
New Configuration.
Configuration Information.
Load Configuration.
Quit.
- Help:
About.
To access the rest of the menu, it will be necessary to start up a new configuration or load an
existing one.
3.2.3 Operating Method (Mouse & Keyboard)

The desired options can be selected in two different ways in all ZIVerlog® configuration module
screens:
- Using the mouse. The option is selected by clicking on the desired highlighted frame.
- Using the keyboard. To select an option from the menu bar, press and release the ALT
key. This will access the menu, highlighting the first available option. Then press the key
matching the underscored letter in the desired option.
The user can browse the various screens without using the mouse by pressing the Tab key to
scroll from field to field. The keyboard equivalent of a mouse click on a button would be to scroll
through the options using the Tab key until the button is highlighted, and then pressing the
Return key.
3.2-4
BCID1207A
3.2 Getting Started
3.2.4 Information Displays

The user can be informed or consulted about actions that can or should be performed
throughout the entire module. Different types of screens are displayed to the user in such
instances:
- Information: no error has occurred, but

the user is informed about running a
specific action. This is identified by the
letter i.
- Warning: These screens are usually

displayed when an invalid action has been
performed. This is identified by an
exclamation point (!).
- Query: This type of screen allows the user

to choose whether or not to perform an
action. This is identified by a question
mark (?).
3.2.5 Using the Controls

There are controls that are common to many module screens. Their operation is explained
below:
- Accept and Cancel buttons. In almost all

screens, these two buttons offer the user a
choice between exiting while saving data
(Accept button) or without saving data
(Cancel button). If the user clicks on Cancel
after having edited data on the screen, a
new screen is displayed asking the user
whether to save the data (see screen at
right).
In screens that are opened using controls from other screens, the Accept button does
not imply that the information is being saved; it simply means that the entered data are
available for use in the source screen. The changes can only be saved from the main
screen.
It's important to point out that data saved in a screen are saved temporarily. They will not
be saved permanently until the user selects the Save full configuration option.
3.2-5
BCID1207A
- Navigation buttons. These buttons shown

at right let you navigate through the items
being configured in each screen according
to their established order.
You can use them to go to the first item, previous item, next item and last item. The
button bar can be found in screens that do not offer a list of configured items, such as
records, opcodes, settings, etc.
- Sort button. This
button can be
located alongside
the navigation
buttons or as a
standalone button.
Clicking on this
button displays a
screen (shown at
right) allowing the
following items to
be sorted in order:
o All the items to be sorted are displayed in the window to the left of the screen.
o The items are displayed in the new order established by the user in the list
included in the right window. To sort the items, press the Resort button.
- New Button. This button lets you add a new item to the screen being configured.
- Delete button. This button lets you delete the selected screen item.
- Right button in lists. In screens consisting of two pages, a Detail and a List page,
where it is possible to add new signals to the list, by pressing the right button a pop-up
menu is displayed for adding and deleting signals. When the object you wish to add as
a new item is a signal, the signal selection screen is usually displayed (see Signal
Selection Screen). In certain screens, this menu can include more options.
3.2-6
BCID1207A
3.2 Getting Started
3.2.6 Selecting Signals

In most screens you are required to select existing signals, which are either defined in the
profile or created by the user.
To facilitate the selection

of signals, two lists are
usually displayed as
shown in the screen
below.
The first drop-down list indicates the Signal Type. The signals are classified into different
groups for digital and for analog signals.
The Available Signals list depends on the signal type selected from the
previous drop-down list. There may not be an available signal in a specific group; in this case,
the drop-down list of available signals will be empty.
3.2.6.a Signal Selection Screen

The controls mentioned
above can be displayed
directly in any module
screen, but in many
cases they are displayed
in specific signal
selection screens, as
shown below:
The Accept button lets you assign the selected signal or edit an existing signal, depending on
the needs of the control from which the call was made.
The Cancel button has no impact on the control used to call it
3.2-7
BCID1207A
3.2.6.b Signal Types

The digital signal groups are as follows:
- User Configuration Signal

- Hardware digital input
- Hardware digital output
- Hardware LED
- Button
- Pickup protection output
- Trip protection output
- Generic protection input
- Logic input to protection
- Command order
- Module enable control
- Others
- Signal to 1
- Signal to 0
The signals specified in the profile are assigned to any of these groups, except "User
Configuration Signal". This group is reserved for digital signals created by the user (see Digital
Signals).
The analog signal groups are as follows:
- Static Magnitudes
- User Magnitudes
The first group is for analog signals specified in the profile, and the second group is for for
digital signals created by the user (see Digital Signals).
3.2.6.c Signal Restrictions

When the user wishes to select a signal, only the signals of the selected type that can be used
for the required function are displayed.
If a signal is being selected to assign a value to it, or if a value can be assigned to it, then
signals with a default assigned value are not displayed in the drop-down list of available signals.
The signals with assigned values are:
- All signals defined in the profile as having an assigned value.

- All signals to which a value is assigned by the logic (they have been used as an opcode
output).
- All signals used to define a command's actions.
- All communication-labeled signals whose value can be set from another piece of
equipment (usually a central unit).
Command actions are a special case, since although a signal that can be considered to have an
assigned value cannot be selected, signals used in other command actions can still be
assigned.
3.2-8
BCID1207A
3.3 File Menu

3.3.1 New Configuration ................................................................................................... 3.3-2
3.3.2 Configuration Information ........................................................................................ 3.3-2
3.3.3 Load Configuration................................................................................................... 3.3-2
3.3.4 Save Configuration .................................................................................................. 3.3-3
3.3.5 Compile Configuration ............................................................................................. 3.3-3
3.3.6 Quit .......................................................................................................................... 3.3-3
3.3.1 New Configuration

The first option in the File menu is the New configuration option. If changes to the
configuration have been made, you will be prompted to save the changes before creating a new
configuration. A default configuration is then created.
3.3.2 Configuration Information

This option displays a
screen that provides the
user with information
about the current
configuration of the
ZIVerlog® module.
- Configuration ID: this value cannot be edited. It is determined by the first 20 characters
of the configuration file name.
- Description of the configuration: text to be entered by the user.
- Configuration version: version number to be entered by the user.
- Checksum: checksum generated while compiling the configuration.
3.3.3 Load Configuration

This menu option displays a dialog
that allows you to search for the
configuration to be loaded.
Configurations have a CFP extension,
and by default the dialog opens the
Configurations directory, which
directly depends on the directory
where the application was installed.
If the module had a previously-loaded

configuration and changes to the
configuration have been made, you
will be prompted to save the changes
before the above screen is displayed.
When a configuration is loaded, it is

validated by the module as indicated in Loading and Validating the Profile.
3.3-2
BCID1207A
3.3 File Menu
3.3.4 Save Configuration

By clicking on the Save
configuration option, a dialog is
displayed letting you establish the
name and location where you wish to
save the configuration.
When a configuration is saved, a file

with an cfp extension is created with
the configuration information,
including the checksum.
3.3.5 Compile Configuration

This menu option creates the binary file ZiverCid® will send to the equipment for configuration.
The checksum is calculated for each

compilation, but it is only saved when
the configuration is saved. This
checksum gives the user the option of
controlling existing configurations and
of improving the management of
them.
Compiling a configuration controls

possible errors that may have
occurred due to the deletion of
signals, incomplete imports, excess
configured signals, etc.
If compiling errors exist, a screen similar to the one shown below is displayed with information
about each of the errors found.
Double-clicking each individual error takes the user to the screen where the error was found,
making it easier to correct.
3.3.6 Quit
This menu option closes the ZIVerlog® configuration module and returns to ZiverCid®. If a
change in the current configuration has occurred, the module prompts the user to save the
changes.
3.3-3
BCID1207A
3.3-4
BCID1207A

3.4.1 Introduction .............................................................................................................. 3.4-2
3.4.2 Input Logic ............................................................................................................... 3.4-2
3.4.3 Output Logic............................................................................................................. 3.4-4
3.4.4 LEDs Logic............................................................................................................... 3.4-5
3.4.1 Introduction
This menu option provides access to screens for configuring the logic of Digital Inputs, Digital
Outputs and LEDs (if the equipment profile enables each of these options).
These screens provide a more immediate way of configuring these logics than the way
described in section Configuration-Associated Logic. A specific logic is added for each of the
inputs, outputs, or LEDs, so that the user has only to indicate the signals to be used and very
little more.
When the configuration is compiled, the logic of these screens will be added to those configured
in the Logic screen, depending on the type of logic (though they are not displayed in this
screen).
3.4.2 Input Logic

This screen adds the logic
configuration for Digital Inputs.
Each of the digital inputs can be

connected to up to 8 logic signals.
Internally the "MULTIPLE CABLE"
opcode is used for each input (for
more information about opcodes, see
section Definition of Opcodes).
The controls shown on this screen are

as follows:
- Digital Inputs: this drop-down list shows all the digital inputs appearing in the equipment
profile.
- Denied: this checkbox lets you deny the value of the digital input and assign it to the
appropriate logic signal.
3.4-2
BCID1207A
- Signal: clicking on each of the

edit boxes displays the signal
selection screen:
Signal Types: this drop-down
list shows all the types of
signals allowed for this type of
logic. For more information
about signal types, see
section Signal Types.
o Available Signals: this drop-down list shows all the selected types of signals
available for connection according to the existing configuration. For more
information about selecting signals, see section Signal Restrictions.
o Not Used: this checkbox indicates that the signal in the edit box on which you have
clicked will be deleted from the input logic screen.
- Import: this button lets you

import an input logic from
another configuration. The
configured input logic is
deleted and replaced by the
imported configuration. The
following screen is shown to
allow the user to select the
configuration for importing:
Once the import is completed, a message is

displayed indicating whether the configuration to
be imported has input logic configured (first
screen) (in this case, the configured logic is not
deleted) or whether the import was completed
correctly (second screen).
- Delete: this button lets you delete all signals (and their
respective denial boxes) for the digital input selected in the
drop-down list.
3.4-3
BCID1207A
3.4.3 Output Logic

This screen adds the logic configuration for Digital Outputs.
Following the diagram,

two blocks of eight logic
signals are available.
One of the blocks
performs an OR
operation with the
selected signals (any
signal activates the
output). The other block
performs an AND
operation with the
selected signals (all
signals need to be active
to activate the output).
An AND or an OR
operation can also be
performed between
these two blocks. The
pulse option can also be
added to the result of this operation.
The basic operation of the two options, with or without pulses, is as follows:
 Without pulses: by setting the pulse timer to 0, the hardware output remains active for
as long as the signal that activated it.
 With pulses: once the hardware output is activated, it stays activated during the fixed
time whether or not the signal that generated it is deactivated before it or remains active
for longer.
The following illustration shows the logic generated for each digital output.
For more information about opcodes, see section Definition of Opcodes.
The controls shown in this screen are similar to those displayed in the digital inputs
configuration screen, as is their operation (see section Input Logic).
3.4-4
BCID1207A
3.4.4 LEDs Logic

This screen adds the logic configuration for LEDs (indicators on the equipment's front panel).
The way the application

functions when assigning
signals is the same as for
outputs, with the
peculiarity that in this
case, one of the two
blocks has eight signals
that perform an OR
operation (any signal
activates the output),
while the other block has
one signal. The two
blocks together can
perform an OR or an
AND operation without
the subsequent
possibility of using
pulses.
Each LED can be defined as latched or unlatched by activating the Latched checkbox. By
activating the checkbox you can make the LED remain active regardless of whether or not the
combination of signals that activated it disappears.
For the Latched option to be enabled in this screen, the equipment profile must have an "LED
Reset Input" signal; otherwise the option remains disabled.
The following illustration shows the logic generated for each LED.
For more information about opcodes, see section Definition of Opcodes.
The other controls shown in this screen are similar to those displayed in the digital inputs
configuration screen, as is their operation (for more information, see section Input Logic).
3.4-5
BCID1207A
3.4-6
BCID1207A
3.5 Configuration-
Associated Logic

3.5.1 Introduction .............................................................................................................. 3.5-2
3.5.2 Definition of Opcodes............................................................................................... 3.5-2
3.5.3 Records Associated with Logic .............................................................................. 3.5-10
3.5.4 Managing Records ................................................................................................. 3.5-10
3.5.4.a Opcodes............................................................................................................ 3.5-14
3.5.1 Introduction
Logic is the set of functions that a piece of equipment should be able to perform. These
functions work with a number of resources: digital signals, analog signals, settings and
constants. To better understand, structure, and assure maintenance of the logic, it is divided
into records.
These records consist of various opcodes or logic gates that are interconnected by means of
the aforementioned resources or by internal records. The signals that can be used are defined
by the equipment profile, in addition to those that can be configured by the user in the module
(see section Defining Resources).
The allowed opcodes are also defined by the equipment profile, although the total opcodes are
detailed in the next section.
3.5.2 Definition of Opcodes

TThe opcodes that can be used in the logic are detailed below.
AND Adder
OR Subtractor
XOR Multiplier
NOT Divisor
Cable Comparator
Multiple Cable Digital to Analog
Multiplexor Analog Selector
Pulse Pulse Train
Timer A Rising Edge
Timer B Binary to Analog
FFD BCD to Analog
FRS Analog to Binary
Counter Analog to BCD
Analog Cable Finite Value
Level Comparator
The assigning of digital signals, analog signals, settings or constants depends on the selected
opcode.
The type of signal that can be connected for each input or output type is detailed below:
 Digital Input:
Digital Signals
Digital Settings
 Analog Input:
Analog Signals or Magnitudes
Analog Settings
Constants
 Digital Output:
Digital Signals
 Analog Output:
Analog Signals or Magnitudes
Some of the opcodes listed above can be memorized so that it is possible to maintain the
opcode value, or status, in case the logic is reset; thus avoiding resetting to a null value. The
following sections indicate which opcodes have this feature.
3.5-2
BCID1207A
 AND
 Function: performs an AND operation between the digital inputs.
 Operands: from 2 and up to a maximum of 16 digital inputs.
 Results: one digital output.
 Truth table for two inputs:
IN1 IN2 OUT

0 0 0
0 1 0
1 0 0
1 1 1
 Memorized: no.
 OR
 Function: performs an OR operation between the digital inputs.
 Operands: from 2 and up to a maximum of 16 digital inputs.
IN1 IN2 OUT

0 0 0
0 1 1
1 0 1
1 1 1
 Memorized: no.
 XOR
 Function: performs an exclusive OR operation between two digital inputs.
 Operands: two digital inputs.
IN1 IN2 OUT

0 0 0
0 1 1
1 0 1
1 1 0
 Memorized: no.
 NOT
 Function: moves the result of the digital input denial to the digital output.
 Operands: one digital input.
 Truth table:
IN OUT
0 1
1 0
 Memorized: no.
3.5-3
BCID1207A
 Cable
 Function: moves the value of the digital input to the digital output.
 Truth table:
IN OUT
0 0
1 1
 Memorized: no.
 Multiple Cable
 Function: moves the value of the digital input to several digital outputs.
 Results: from 1 and up to a maximum of 16 digital outputs.
 Truth table:
IN OUT1 OUTN
0 0 0
1 1 1
 Memorized: no.
 Multiplexor
 Function: this selector-based opcode sets the value of a digital output to the
value of one of the digital inputs.
 Operands:
One digital input as input selector: SEL
Two digital inputs: E0, E1.
 Results: one digital output
 Truth table:
SEL OUT
0 E0
1 E1
 Memorized: no.
 Pulse
 Function: in this opcode, the output is activated for the time specified as a
parameter when the digital input goes from 0 to 1.
 Operands:
One digital input.
An analog setting or a pulse time constant setting in seconds.
 Memorized: yes.
 Limits: the maximum time must be set between 0.0 and 2147483.648 seconds
(24 days).
3.5-4
BCID1207A
 Timer A
 Function: after the set time from the moment the digital input went from 0 to 1
elapses, it sets the output to 1 until the input resets.
 Operands:
One digital input.
A setting or a delay time constant setting in seconds.
 Operating diagram:
 Memorized: yes.
(24 days).
 Timer B
 Function: activates the output while the input is active or has deactivated after a
time no longer than the set time elapses.
 Operands:
One digital input.
An adjustable or fixed length of time measured in seconds.
 Operating diagram:
 Memorized: yes.
(24 days).
3.5-5
BCID1207A
 FFD
 Function: this opcode is a type D flip-flop. The flip-flop takes the input value each
time a rising edge in the digital input marked as clock occurs.
 Operands:
One digital clock input (CLK).
One digital input (I).
 Truth table:
I CLK Q
0 1 0
1 1 1
 Memorized: yes.
 FFRS
 Function: this opcode is a type RS flip-flop. The flip-flop takes the input value
while the S digital input is active. The flip-flop takes the value 0 when the R input is
activated.
 Operands:
One digital input (R)
One digital input (S)
 Truth table:
R S Qt+t
0 0 Qt
0 1 1
1 0 0
1 1 X
 Memorized: yes.
 Analog Cable
 Function: this opcode moves the value from one analog magnitude to another.
 Operands: one analog input.
 Results: one analog output.
 Memorized: no.
 Counter
 Function: manages a counter that increases with each rising edge of the digital
input marked as clock. The counter resets to 0 when the reset input is activated.
 Operands:
One digital reset input (Res).
One digital clock input (CLK).
 Memorized: no.
 Limits: the counter has a saturation value of 65535. Subsequent increases do not
change the counter's output value.
3.5-6
BCID1207A
 Adder
 Function: sets the value of the analog output to the result of the sum of analog
inputs.
 Operands: two analog inputs.
 Memorized: no.
 Subtractor
 Function: sets the value of the analog output to the result of the subtraction of
analog inputs.
 Operands:
One analog input acting as a minuend
One analog input acting as a subtrahend (-)
Results: one analog output.
 Memorized: no.
 Multiplier
 Function: sets the value of the analog output to the result of the product of analog
inputs.
 Operands: two analog inputs.
 Memorized: no.
 Divisor
 Function: sets the value of the analog output to the result of the division of analog
inputs.
 Operands:
One analog input acting as a dividend
One analog input acting as a divisor (/)
 Memorized: no.
 Comparator
 Function: compares two analog inputs, setting the value of the digital output based
on the result of the comparison. If the comparison type is met between the first
input and the second input, the output is activated.
 Operands:
Two analog inputs (Ent 0, Ent 1).
Comparison type as a constant value inserted in the opcode:
greater than not equal to
less than greater than or equal to
equal to less than or equal to
 Results: digital output signal.
 Memorized: no.
3.5-7
BCID1207A
 Level Comparator
 Function: compares the analog input to a minimum and maximum benchmark
value, setting the digital output based on the comparison:
The output is set to 1 if the input is higher than the maximum benchmark value.
The output is set to 0 if the input is lower than the maximum benchmark value.
Otherwise, the output value remains the same.
 Operands:
One analog input (I).
One analog input as a minimum benchmark value (R L).
One analog input as a maximum benchmark value (R H).
 Memorized: yes.
 Digital to Analog
 Function: converts an analog output with a value of 0 or 1 to a digital input.
 Memorized: no.
 Pulse Train
 Function: this opcode is a logical block that generates a pulse train while the
digital input remains active.
 Operands:
One pulse-train activating digital input (ACT).
One analog input indicating the active pulse time in seconds (H).
One analog input indicating the inactive pulse time in seconds (L).
 Memorized: yes.
 Rising Edge
 Function: activates the digital output when a change from 0 to 1 is detected in the
digital input.
 Operands: one digital output.
 Memorized: no.
 Analog Multiplexor
 Function: this selector-based opcode sets the value of an analog output with the
value of one of the two analog inputs.
 Operands:
One digital input acting as an input selector (Sel).
Two analog inputs (In 0, In 1).
 Truth table:
SEL OUT
0 In0
1 In1
 Memorized: no.
3.5-8
BCID1207A
 Binary to Analog
 Function: this opcode sets the value of an analog output based on a number of
digital inputs.
 Operands: from 1 up to 16 digital inputs (DI1, DI2,..., DI16).
 Results:
One analog output resulting from the following operation:
OUTPUT=DI1+(DI2<<1)+(DI3<<2)+...(DIN<<N)
 Memorized: no.
 BCD to Analog
 Function: sets the value of an analog output based on a number of digital inputs.
 Operands: from 1 up to 16 digital inputs (DI1, DI2,..., DI16).
 Results:
One analog output resulting from the following operation:
OUTPUT = (DI1+(DI2<<1) + (DI3<<2) + (DI3<<3))(DI4+(DI5<<1) + (DI6<<2) +
(DI7<<3))*10+...
 Memorized: no.
 Analog to Binary
 Function: this opcode sets the value of a number of digital outputs that represent
the whole value of the input based on an analog input.
 Results: from 1 up to 16 digital outputs (DO1, DO2,...,DO16).
 Memorized: no.
 Analog to BCD
 Function: this opcode sets the value of a number of digital outputs that represent
the whole value of the BCD format magnitude based on an analog input.
 Results: from 1 up to 16 digital outputs (DO1, DO2,...,DO16).
 Memorized: no.
 Finite Value
 Function: the opcode digital output is set to 1 when the analog input has a finite
value; otherwise, the opcode digital output is set to 0.
 Operands: magnitude, analog setting or input constant.
 Results: output digital signal.
 Memorized: no.
3.5-9
BCID1207A
3.5.3 Records Associated with Logic

The equipment logic consists of a series of logic gates or opcodes that are linked together by
means of different resources (signals, magnitudes, settings, etc.). Each logic can in turn be
divided into Records. A record is a group of opcodes that is given some form of identification.
The records generally represent a specific logic function or feature.
There are five types of logics:
 Digital Inputs.
 Protection.
 Digital Outputs.
 Control.
 Front.
Some of these logic types may not appear, depending on the existing profile. To access and
configure the logic, click on the Logic menu:
3.5.4 Managing
Records
All existing records
according to the logic
type, as well as the
opcodes they contain,
are controlled using the
following screen, Logic
Cards:
This screen displays the

opcodes depending on
the logic type and record
the user has selected.
The controls shown on

this screen are as
follows:
- Logic Type: this drop-down list lets you select the logic type you wish to configure. In
each case only the records belonging to the selected logic type are displayed.
- Card Description: a text box for informational purposes only; cannot be edited or
added to. Shows the description the user entered when creating or renaming the
record.
- Order: a text box for informational purposes only; indicates the order of the record
within the selected logic type.
- Sort, Go to First Record, Previous Record, Next Record, Go to Last Record: these
buttons let you sort and scroll through the records for the selected logic type by their
order number (see section Using the Controls).
- Record: this drop-down list lets you select each of the records of the selected logic type
by name.
3.5-10
BCID1207A
- Opcodes: this list displays the opcodes belonging to the selected record. 5 columns are
displayed:
1st column: this column displays the opcode input descriptions, if any.
2nd column (Inputs): this column displays the descriptions of resources
connected to the input. If the resource is a denied signal, the description of the
connected signal is preceded by "NOT-".
3rd column (Function): this column displays the opcode; if it is memorized, it is
displayed under the name. This column also displays the selected opcode setting
(for those that need them)under the opcode name.
4th column (Outputs): this column displays the descriptions of resources
connected to the output. If the resource is a denied signal, the description of the
connected signal is preceded by "NOT-".
5th column: this column displays the opcode output descriptions, if any.
- New card: this button lets you access the Add record screen, depicted below.
This screen displays two text

boxes: The name of the new
record is entered in the
Identifier field (required).
Once accepted, the value is
checked to make sure it is
unique and the description of
the new record is entered in
the Description field
(optional).
- Import: this button lets you

import different records from
another configuration. The
user is first asked to select
the configuration from which
the records are to be imported
through the following dialog.
The following screen
containing the records of the
desired configuration is
shown once the configuration
is selected.
3.5-11
BCID1207A
This screen shows all the

records existing in the
configuration from which the
records are to be imported.
The identifier or ID are
indicated, along with the
description and the logic
type to which the record
belongs. More than one
record can be selected at the
same time by pressing Ctrl
and keeping it pressed as you
click on the records with the
mouse.
If you select Import to actual logic type, all the records will be imported to the logic
type selected in the logic records screen, regardless of the type of logic they belong to
in the original configuration.
If the name of an imported record matches an existing record name, the imported
record is added by including a hash mark (#) followed by a number in its name, thus
avoiding duplicate record IDs.
The configuration resources used in the records, and that do not exist in the current
configuration, are imported at the same time as the record opcodes. However, the
resources from the profile cannot be imported.
If any incompatibility exists between imported and existing records, existing records are
given priority. In this way, records with incomplete opcodes or opcodes where inputs or
outputs have been deleted because they were not valid signals for the current
configuration and/or profile can be imported.
Upon completing the

importation, if an error has
occurred or incomplete
records have been imported,
the following error screen is
displayed.
3.5-12
BCID1207A
Opcodes not
valid for the
current
configuration, as
well as
improperly
connected or
incomplete
opcodes, are
displayed in red
as shown in the
following screen:
- Delete card: this button lets you delete the

current record. The user is first asked to confirm:
- Rename: this button lets you change the current record's name and/or description.
- Consumption: this button

offers to the user information
approximated on the
consumption of the logic that
has the equipment, in time
and memory. The different
types from logics are grouped
as a matter of priority of
execution according to the
information of the profile, and
for each grouping the
consumption of time in
percentage is offered. The
memory consumption
visualizes in as much by one
hundred for all the set of the
logic.
3.5-13
BCID1207A
- Edit: this button

provides access
to screens where
the user can
enter and
connect
opcodes. If there
are no opcodes
in the record, the
opcode fields are
disabled.
3.5.4.a Opcodes
Opcodes can be added, connected, deleted and edited using the above screen.
The screen provides the following controls:
 Drop-down list in the center of the screen for selecting the opcode.
 Block of 16 controls for selecting opcode inputs.
 Control for selecting opcode output.
 Control for selecting opcode setting.
 Text box showing the order of the opcode within the record.
 Buttons for selecting opcodes according to the order (see section Using controls).
 Button for sorting opcodes (see section Using controls).
 Button for adding a new opcode.
 Button for deleting an opcode.
Depending on whether or not the opcode allows it, fields will be enabled and disabled so that
the inputs and outputs can be referenced from the various controls according to the opcode.
3.5-14
BCID1207A
 Adding Opcodes
The opcode controls are activated after pressing the new button on the Edit opcodes screen.
The central drop-down list is for selecting the opcode you wish to include in the record:
For each opcode the

fields it might need, as
well as indications for
each input or output, are
activated. If a connected
opcode is replaced by
another opcode, the
connections will be
maintained if possible.
Connections that are not
valid, either because the
resource type is different
or it doesn't have the
same number of inputs
and outputs, are deleted.
When selecting the opcode, the user is shown only those fields available in the equipment
profile. It is possible to load a configuration created with a profile that allows for more opcodes
than the current one. In this case the opcodes that are not permitted can be seen, but they can
only be deleted, not edited.
3.5-15
BCID1207A
 Connecting and/or Editing Opcodes

To set the opcode's inputs and
outputs, simply enter the signal or
resource to be connected in the
relevant text box. To disconnect,
simply delete the existing signal.
You can also click on the arrow to the right of the field to display a drop-down screen with the
existing resources that can be connected to the selected opcode.
This screen includes the following opcodes
- Resource Types: the group of options located on the upper left-hand corner of the
screen lets the user select the type of resource to be connected to the opcode. Only
those resources that are allowed for the selected opcode input or output are displayed
as enabled.
- Signal Types:
this drop-down
list lets you
select the signal
type. For more
information
about signal
types, see
section Signal
Types.
- Available Signals: after selecting the signal type, this drop-down list shows all the
selected types of signals available for the opcode input or output. For more information
about selecting signals, see section Signal Restrictions.
- Not Used: this checkbox lets you disconnect the resource connected to the opcode.
- Create New Resource: this button lets you access screens for creating new resources.
These screens can also be accessed from the main menu. You will access one screen
or another depending on the option you select in the resource types screen. The
recently created resources are available once you return to this screen.
Internal Records, both digital and analog, are a special case when it comes to resources.
Internal records are identifiers that let you connect inputs and/or outputs between opcodes
without assigning the value to a specific signal.
3.5-16
BCID1207A
The records are identified by the first three characters:
 Digital Records: these should start by the following characters: RD_

 Analog Records: these should start by the following characters: RA_ or RE_, depending
on the magnitude type (floating comma or integer, respectively).
To connect an opcode's output to another opcode's input using an internal record, for instance
an OR gate output with an AND gate input, simply enter the internal record (RD_text_record) for
the OR gate output and the AND gate input.
In the Available signals screen you can select records that were already defined in the current
logic type. However, a new record can only be created using the edit field.
A specific internal record can only be used within the logic type for which it was defined. It
cannot be accessed from different logic types due to their differing execution priorities.
 Delete Opcodes
The Delete button lets you delete the opcode you are editing. The order of the remaining
opcodes will be adjusted accordingly.
After deleting an opcode, all the output signals can be reused (see section Signal Restrictions,
for more information).
3.5-17
BCID1207A
3.5-18
BCID1207A

3.6.1 Introduction .............................................................................................................. 3.6-2
3.6.1.a Digital Signals ..................................................................................................... 3.6-2
3.6.2 Parameters .............................................................................................................. 3.6-3
3.6.3 Settings .................................................................................................................... 3.6-4
3.6.3.a Settings Group .................................................................................................... 3.6-4
3.6.3.b Defining Settings................................................................................................. 3.6-5
3.6.4 Constants ................................................................................................................. 3.6-6
3.6.5 Commands............................................................................................................... 3.6-7
3.6.5.a Command Element Description .......................................................................... 3.6-7
3.6.5.b Configuring the Command .................................................................................. 3.6-8
3.6.6 Analog Commands ................................................................................................ 3.6-15
3.6.6.a Analog Command Actions ................................................................................ 3.6-15
3.6.6.b Command Blocks.............................................................................................. 3.6-16
3.6.1 Introduction
This section defines the configuration resources, that is, the set of digital signals, magnitudes,
constants, settings and commands to be added to the equipment's resources in order to be
used in logic or communications. These resources can be referenced from ZiverCid®.
Users can access the configuration of the various resources through the Defining Resources
option in the main menu, as shown in the screen below. The resources that can be configured
are: Digital Signals, Magnitudes, Settings, Constants, and Commands. These resources
are added to those available from the equipment and can be referenced both from the logic and
from ZiverCid®.
3.6.1.a Digital Signals

Clicking on the Digital Signals menu option displays the screen for configuring user-defined
digital signals.
To define a new signal,

simply press the New
button. By default, a new
digital signal will be
created with the Control
Signal description
followed by a correlative
number. The user can
position the cursor on the
list and edit the
description of any signal
and its short text.
These signals are added

to the equipment's set of
signals (defined in the
profile) for use in logic,
communications, etc.
They can also be
referenced from
®
ZiverCid .
3.6-2
BCID1207A
3.6.2 Parameters
The Parameters option
lets you configure user
defined analog signals.
This screen is divided

into two distinct sections,
one providing details and
the other a list. Both
contain the same
information, and the
values edited in one
section are also reflected
in the other.
For each user-defined

analog signal or
parameter it is possible
to configure certain
features
- Message: short text used to identify the signal in the HMI.

- Description: description of the analog signal.
- Units: the units that can be selected will be read from the profile of the working
equipment.
- Factor: multiplication factor for defining parameters in non-standardized units. For
instance, if you wish to use a parameter in hundredths of watts, the units parameter
would select the unit and use 0.01 as a factor.
- Type: indicates the parameter precision type (integer or floating comma).
- Rated Value
- Maximum Value: this value is for informational purposes only.
- Minimum Value: minimum value allowed for the parameter. For information only.
- Step: magnitude increment value. For information only.
Some of the described data may or may not appear in the window depending on the data read
in the working profile.
These parameters are added to the equipment's set of signals (defined in the profile) for use in
®
logic, communications, etc. They can also be referenced from ZiverCid .
3.6-3
BCID1207A
3.6.3 Settings
This section explains how to configure user settings with the ZIVerlog® configuration module.
Users can access the Settings Group screen by pressing on the Settings sub-option in the
main menu's Define Resources option.
All settings must belong to a group. The groups and settings defined in this section will be
complementary to the equipment's own settings, and like these, they can be referenced from
ZiverCid®. Groups entered in the configuration will have a unique entry in the tree, from the
settings node of ZiverCid®, under the name User Settings. The different configured groups will
belong to this node, and the settings belonging to a specific group will be displayed under that
group.
A maximum of 16 groups and 256 settings can be configured.
3.6.3.a Settings Group

As described above, the following screen can be accessed from the main menu. This screen
includes the following controls:
- Group: drop-
down list with the
Settings Groups
included in the
configuration.
The group
selected here
conditions the
values shown in
the rest of the
screen. The
name appearing
here is the same
as the name that
will be shown in
the HMI and
®
ZiverCid to
identify the
settings group.
- Description: description of the settings group.
- Group Settings: a sorted list of the settings belonging to the selected group in the drop-
down list labeled Group. The description given here of the setting comprises a starting
number that indicates the order of the setting inside the group, an ID that gives an idea
of the setting type (AA = Analog, AB = Boolean), and finally the message or text
representing the setting in ZiverCid® and in the HMI.
- Edit Settings: button providing access to the screen where the selected setting can be
configured. This screen is described in section Settings. It can also be accessed by
double-clicking on the setting you wish to edit in the Group Settings list.
3.6-4
BCID1207A
- Add Group: button providing

access to the screen where a
new group can be entered.
The screen appearing on the
right, which is the same
screen used to rename
groups, is displayed. This
screen registers the group ID
and description. The ID is
required while the description is optional. By pressing the Accept button on this screen,
the ID value is checked to be valid, i.e. whether it is null and unique in the configuration.
If it is valid, then the new group is registered; otherwise, an error message is displayed.
- Delete Group: deletes the selected group together with its settings. If any one of the
group settings is being used in a logic, then the connection is deleted; this means that
some logic gates or opcodes can be incomplete.
- Sort Groups: button providing access to the screen where the groups are sorted. The
generic sorting screen explained in section Using controls, is displayed. The order given
to each of the groups is the order in which the data will be shown in the HMI and in
®
ZiverCid .
- Rename Group: button providing access to the screen where group data can be
changed. The same screen that is used to add groups is displayed; this is the same
screen used for registering a new group. This screen shows the group ID and
description which can be edited by the user. When you press Accept, the new ID is
checked for validity (it exists and is unique in the configuration). If it is, then the group
information is changed without varying the data of the settings that comprise it or its
order.
3.6.3.b Defining Settings

This screen can be accessed by
pressing the Edit Settings button in
the Settings Group screen, or by
double-clicking on the setting you
wish to edit in the same screen.
This screen includes the following

controls:
- Group: ID of the settings

group to which the settings
belong. This value is for
informational purposes; that
is, it cannot be edited from
this screen.
®
- Message: ID of the setting in the HMI and in ZiverCid . Allows up to 16 characters.
- Description: setting description. This value is not required.
3.6-5
BCID1207A
- Setting Type: drop-down list including valid setting types. The valid types of settings
are:
o Analog: numeric with 3 decimals.
o Boolean: digital value, only allows 0 or 1 values.
- Units: the valid units list will differ according to the selected setting type. The maximum,
minimum and step values allowed can also vary depending on the selected unit.
- Maximum: maximum value allowed for the setting (*).
- Minimum: minimum value allowed for the setting (*).
- Default Value: default value of the setting (*).
- Step: setting step value.
- Tool Bar: bar for moving and sorting settings (see section Using Controls). All the
settings belonging to the selected goup can be scrolled through using this bar.
- New: registers a new setting for the selected group. By default, the following values are
registered:
o Message: 'Setting' followed by the group number (group order) and setting number
(setting order).
o Setting type: Boolean.
o Units: NULL (no units).
o Maximum: 1 (being boolean, it is a fixed, not configurable value).
o Minimum: 0 (being boolean, it is a fixed, not configurable value).
o Default value: 0.
o Step: 1 (being boolean, it is a fixed, not configurable value).
- Delete: deletes the selected setting from the group. If it is being used in the logic, it will
be deleted.
(*) The configuration module will perform all checks for data consistency, that is, it will check to make
sure the minimum value does not exceed the maximum value, that the default value is within the
minimum and maximum values, etc.
3.6.4 Constants
The Constants menu
option lets you configure
user-defined constants.
This screen, like the

Magnitudes screen, is
divided into a Detail and
a List section. The
controls appear in both
sections, and all can be
edited:
- Description:
description of the
constant.
- Value: value of
the constant.
3.6-6
BCID1207A
3.6.5 Commands
3.6.5.a Command Element Description
Some IEDs like IRV, ZLV and others do not have commands or controls by which they operate,
that is, they cannot be directly operated by means of breakers, reclosers, disconnect switches,
or any other elements. Such elements must be defined in the configuration, and this is why they
are always referred to in the application as Command Elements. The IED units do have
unconnected inputs that can be fed by means of commands.
A Command Element is defined by the following information:
- Command Element Name.

- List of digital signals that condition the element's status.
- Element status list: for each status the following have to be defined:
o Text identifying the status.
o Group of signals and their values to be examined in order to determine the element's
status.
- List of actions associated with the element: For each action the following have to be
defined:
o Text identifying the action.
o Signal associated with the action. When a command is executed in relation to the
action a pulse with a fixed duration is being generated over the signal beingdefined.
o The group of element status conditions on which the action can be executed
(optional information).
o The set of status conditions where the element is already in the desired position
when the action is executed (optional information).
A breaker with three status positions - open, closed and unknown will be defined as an
example:
Command Element Name Breaker

Possible status conditions Open, Closed, and Unknown
Possible actions for the element Open and Close
The value of the signals for the different element status conditions is defined:
Status Value of the signal conditioning the status

Open Breaker Closed Breaker
Open Value to 1 Value to 0
Closed Value to 0 Value to 1
Unknown - -
The status conditions in which each action can be executed and the signal associated with the
action are defined:
Actions Signal associated STATUS

with the action Open Closed Unknown
Open Breaker Open In position Not in position -
Command Do not operate Can be operate -
Close Breaker Closed Not in position. In position -
Command Can be operated Cannot be operated -
3.6-7
BCID1207A
3.6.5.b Configuring the Command

This section explains how to configure the Command Element with the ZIVerlog® configuration
module. Users can access the Equipment Command Configuration screen by pressing on the
Commands sub-option in the main menu's Define Resources option. All of the element's
components described in the previous section are going to be configured on the same screen.
This screen is divided into three tabs. Each of the tabs configures one part of the command.
- Signals defining the Status.

- Element Status Conditions.
- Element Actions.
- Element Blockings.
You can switch from one page to another by pressing on the tab located on the top of the box,
identified by the titles listed earlier.
In addition to the aforementioned pages, the following controls can be found in the upper portion
of the screen:
- Element Name: text which identifies the command element. This text can be directly
edited by the user. Moreover, this control is a drop-down list for selecting the command
to be configured so that data appearing on the signal, status condition, and action
pages match the command selected in this list.
- New Command: includes a new command element with no associated status condition,
actions or signals. By default it is given the name Order Element followed by the first
free (unused) number starting from 0. As indicated earlier, this name can be changed
simply by editing the text.
- Delete Command: deletes the command element selected on the list. When the
command element is deleted, not only are its associated actions, status conditions, and
signals deleted, but also the communications if these are used as a command for some
protocols.
- Import Command: lets you import commands defined in another configuration. This
button takes you to the Import Commands screen described further below.
3.6-8
BCID1207A
 Signals defining the Status

These are the signals
that condition the
Command Element's
status.
This screen shows the

complete list of signals
enabled to define the
status of the command
element. The list consists
of two columns. The first
column shows the
description of the group
to which the signal
defining the status (on
the same line but in the
next column) belongs.
For more information
about signal types
(groups), see section
Signal Types.
The following controls can be found in this screen:
- New: shows the signal selection screen (see section Signal Selection Screen). If the
selected signal is accepted, it is included as a status signal and added to the list on the
screen.
- Delete: deletes the signal associated with the selected status.
- Edit: Shows the signal selection screen (see section Signal Selection Screen). In this
way, a different status signal can be selected. When you return to the starting screen,
the signal that was first selected changes to the new selection you have just made.
These signals can also be edited on the list by left-clicking the mouse on Signal Type
or on one of the signals that define the status condition.
3.6-9
BCID1207A
 Command Status Conditions

This screen defines the
command element status
conditions and the data
associated with the
status conditions: A
complete list of command
element status conditions
is displayed on the left,
and the signals defining
the status (configured in
the previous screen),
together with the value
associated with each
signal, are displayed on
the right. For each status
condition you have to
configure the values of
the signals defining the
status condition (see
section Command
Element Description).
The controls shown on this screen are as follows:
- New Status: registers a new status and displays it on the list to the left. By default, the
text given will be Status, followed by the first free number starting from 0.
- Delete Status: deletes the selected status from the list on the left.
- Status Text: list with the description of each status condition associated with the
command element. This text can be edited by the user.
- Status Text Masks: the masks are defined by each of the element's status conditions
so that they are shown at all times on the status signal value list relative to the selected
Status. The selected Status will be the status highlighted in the list on the left side,
which in turn is the status that is displayed in the Status Text Mask title:
o Signals to be examined: list of signals defined in the previous screen that are
common to all status conditions, since they are command element signals.
o Value: the value of each signal. It is used to define the selected status. Since the
signals to be examined are digital, the only valid values are '1', '0' and '-'. The latter
indicates that the value of the signal is not taken into account when determining the
status. To change this value, the user should place the cursor over the box defining
the value and then left-click the mouse to scroll consecutively through all the
possible values.
3.6-10
BCID1207A
 Command Actions
command element
actions and the data
associated with such
actions.
The left side of the

screen contains a
complete list of the
command element
actions and the signal for
each of these actions.
The command element
status list configured in
the previous screen,
together with the status
masks for each action, is
displayed on the right.
The action will be
allowed (or not)
depending on the status of the command element. The link between the action and the status
conditions of the element is configured by defining the status masks. For more information, see
the example in section Command Item Description.
The controls shown on this screen are as follows:
- New Action: shows the signal selection screen (see section Signal Selection Screen). If
you select a signal on this screen and press the Accept button, a new action will be
enabled with the selected signal as the signal associated with the action. By default, the
text given to the action will be Action, followed by the first free number starting from 0.
This text can be edited by the user. The action will be included in the list. If you select a
signal on this screen and press the Cancel button, the action will not be enabled as it
has to be associated with a signal. When the action is executed, what is really
happening is that a pulse with a fixed duration is acting on the selected signal.
- Delete Action: deletes the selected action (and its associated signal) from the list on
the left.
- Action Text: list with the description of each action associated with the command
element. This text can be edited by the user.
- Involved Signal: signal used to generate a pulse when executing an action. When you
left-click on this field, the signal selection screen is displayed (see Signal Selection
Screen) allowing you to edit the signal associated with the action. When you return to
the starting screen (Equipment Command Configuration), the signal that was first
selected changes to the new selection you have just made. Not all digital signals are
valid for commands. For safety reasons, it is not allowed to establish the value of a
signal from more than one source; that is, signals that already have an assigned value,
those that take the value when executed in the logic, or those that establish their value
through communications, cannot be used as signals associated with the action. For
more information about permissions for using signals, see section Signal Restriction.
3.6-11
BCID1207A
- Successful Command Signal: digital signal stating successful command execution.

- Failed Command Signal: digital signal stating failed command execution.
- Timeout Setting: setting stating the waiting time before the command execution is
considered failed.
Note: only given equipment have the possibility to configure these three signals (successful
command execution, command failure and timeout setting). The equipment profile determines
whether these data may or may not be configured.
- Action Text Masks: the masks are defined for each of the control element's actions so
that the status masks for the selected action are shown each time on the list. The
selected action will be the action highlighted in the list on the left-hand side, which in
turn is the action displayed in the Action Text Mask title.
o status list: a list of the status conditions defined for the command element. The
status conditions are common to all actions.
o oper: indicates whether or not the selected action can be performed when the
command element is in the status condition that is being configured (on the same
line in the left column).
o pos: means "in position", and indicates if the command element is in the same
status condition arrived at after executing the action.
 Command Blocking
In this "tab" command
element locks are
defined as well as the
connection between
locks and element
commands. Bear in mind
that the command
configuration screen will
not always show this
"tab", as it would depend
on equipment profile.
Command locks may not
be defined for some
equipment. These shall
directly be carried out
through the logic.
The screen depicted shows to the left a complete list of command element actions, and to the
right a list of locks defined for the element together with the lockout connected signal and
lockout masks for each action. The status of the lockout signal must be checked prior to
command execution.
3.6-12
BCID1207A
This screen shows the following controls:
- New Blocking: displays the signal selection screen (see section signal selection
screen). Selecting a signal on this screen and pressing OK button, a new lockout is
created with the selected signal as connected signal. By default, the lockout text will be
'Lockout' followed by the first free number starting from 0. This text is user modifiable.
The lockout will be shown in the list to the right. Pressing the Cancel button in the
signal selection screen cancels the new lockout, as a lockout must be connected to a
signal.
- Delete Blocking: the lockout (and its signal) selected in the list to the right is deleted.
- Blocking text: list with the description of all locks defined for the command element.
This text is user modifiable.
- Connected signal: signal connected to the lockout. Signal to test whether the
command can be executed. This is previous to testing the status of the command
element. Pressing this field with the main mouse button displays the signal selection
screen (see section signal selection screen) so that the signal connected to the lockout
can be modified. Returning to the former screen, the new signal is shown instead of the
previously selected signal.
- Lockout Action: all command element actions can be locked by a number of locks.
The list to the right of the screen shows all command element locks and the Lockout
Action column shows with a check the checkboxes that lockout the action selected in
the list to the left, which at the same time appears as the column title. To checkmark an
empty checkbox just press on it with the main mouse button. It will be unchecked if the
same operation is made on a checkmarked box.
 Import Command
By pressing the import button in the
command definition screen, the
Windows file selection dialog is
displayed. The user can then choose
the configuration from which to import
the command(s). After selecting the
configuration, the following screen is
displayed containing all the
commands defined in the selected
configuration.
This screen shows a list with the description of all the available commands in the selected
configuration, in addition to indicating if status conditions and actions have been defined for the
configuration. This list is a multiple-selection list. You can select any commands you wish to
include in the work configuration. To make a multiple selection, press and hold down the Ctrl
key while selecting the desired commands by clicking on each of them with the mouse.
3.6-13
BCID1207A
If the name of an imported command matches an existing command name, the imported
command is added by including a hash mark (#) followed by a number in its name, thus
avoiding duplicate command IDs.
The digital configuration signals that are used in the command and do not exist in the current
configuration are imported at the same time as the commands.
Before importing the command, you should study whether the command can be included in the
current configuration. It has already been noted that not all signals can be used as signals
associated with the command's action. If the command to be imported has one or more of these
signals, or other signals that do not exist in the current equipment profile, the command will not
be imported.
After importing, if an error has

occurred or a command has not been
imported for the described reasons,
an error screen like the screen shown
below is displayed.
This screen not only indicates the

total number of errors, but also
provides a brief description of each. In
this way, the user can know the
reason why the command import was
unsuccessful.
3.6-14
BCID1207A
3.6.6 Analog Commands

Pressing the Analog Command option in the main menu Resource Definition, displays the
screen 'Configuration of Equipment Analog Commands'. In this screen the analog command
status signal as well as actions and possible command blocks are configured.
The following controls are located on the upper part of the screen:
- Element Name: text to identify the analog command element that can directly be
modified by the user. Furthermore, this control is a drop down list from which to select
the command to be configured, so that data on the action and lockout pages
correspond to the command selected from this list.
- New Command: creates a new analog command element, with neither status nor
actions and connected signals. By default it is given the name 'Command Element'
followed by the first free number (not used) starting from 0. As stated above, this name
can be modified just modifying the text.
- Delete Command: deletes the command element selected from the list. By deleting the
command element, all actions, status and connected signals are deleted and also it is
deleted from communications if it were being used in any protocol.
- Connected Analog Signal: the analog signal representing the analog command
element status.
3.6.6.a Analog Command Actions

From this screen, both analog command element actions and associated data can be defined.
This screen shows the following controls:
- New Action: displays the analog signal selection screen (see section signal selection
Screen). Selecting an analog signal on this screen and pressing the OK button, a new
action is created with the selected signal as connected signal. By default the action text
will be 'Action' followed by the first free number starting form 0. This is a user modifiable
text. The new action will be included into the list unless the Cancel button is pressed on
the signal selection screen, as an action has to be connected to a signal. When
executing the action what actually occurs is that a fixed duration pulse on that analog
signal takes place and of amplitude over the signal value.
- Delete Action: deletes the action (and connected signal) selected in the list to the left.
- Action Text: list with the description of all actions connected to the command element.
- Connected Signal: analog signal over which a pulse is generated when executing the
action. Pressing the left mouse button on this field displays the signal selection screen
(see section signal selection Screen) so that the analog signal connected to the action
can be modified. Returning to the former screen (Analog Equipment Command
Configuration screen), the new signal is shown instead of the previously selected signal.
Not all analog signals are valid for command execution. For safety reasons, signal
values cannot be established from more than one source, namely, signals with a value
or acquiring value through logic execution or through communications, etc., may not be
used as signals connected to the action.
- Successful Command Signal: digital signal stating successful action execution.
- Failed Command Signal: digital signal stating failed command execution.
- Timeout Setting: setting stating the waiting time before the command execution is
considered failed.
3.6-15
BCID1207A
3.6.6.b Command Blocks

In this screen command element locks are defined as well as the connection between locks and
element actions.
As shown on the right, a

complete list of analog
command element
actions is shown to the
left; a list of locks defined
for the element together
with the lockout
connected signal and
lockout masks for each
action is shown to the
right. The status of the
lockout signal must be
checked prior to
command execution.

following controls:
- New Lockout: displays the signal selection screen (see section signal selection
screen). Selecting a signal on this screen and pressing OK, a new lockout is created
with the selected signal as connected signal. By default, the lockout text will be
'Lockout' followed by the first free number starting from 0. This text is user modifiable.
The lockout will be shown in the list to the right except if the Cancel button is pressed in
the signal selection Screen, as a lockout must be connected to a signal.
- Delete lockout: the lockout (and its signal) selected in the list to the right is deleted.
- Lockout Text: list with the description of all locks defined for the command element.
- Connected Signal: signal connected to the lockout. Signal to test whether the
command can be executed. Pressing with the main mouse button on this field displays
the signal selection Screen (see section signal selection Screen) so that the signal
connected to the lockout can be modified. Returning to the former screen (Analog
Equipment Command Configuration screen), the new signal is shown instead of the
previously selected signal.
- Lockout Action: all command element actions can be locked by a number of locks.
The list to the right of the screen shows all command element locks and the Lockout
Action column shows with a checkmark the checkboxes that lockout the action selected
in the list to the left, which at the same time appears as the column title. To checkmark
an empty checkbox just press on it with the main mouse button. It will be unchecked if
the same operation is made on a checked box.
3.6-16
BCID1207A
3.7 Communications

3.7.1 Introduction .............................................................................................................. 3.7-2
3.7.1.a General Format and Screen Handling ................................................................ 3.7-2
3.7.2 Procome ................................................................................................................... 3.7-4
3.7.2.a Events ................................................................................................................. 3.7-4
3.7.2.b Control Changes ................................................................................................. 3.7-6
3.7.2.c Commands ......................................................................................................... 3.7-9
3.7.2.d Metering Values ................................................................................................ 3.7-11
3.7.2.e Meters ............................................................................................................... 3.7-13
3.7.2.f Output Writings ................................................................................................. 3.7-14
3.7.3 DNP3 ..................................................................................................................... 3.7-19
3.7.3.a Contacts ............................................................................................................ 3.7-19
3.7.3.b Commands ....................................................................................................... 3.7-20
3.7.3.c Metering Values (Profile I) ................................................................................ 3.7-24
3.7.3.d Metering Values (Profile II) ............................................................................... 3.7-26
3.7.3.e Meters ............................................................................................................... 3.7-29
3.7.3.f Analog DNP3 Output Writings (Profile I) .......................................................... 3.7-31
3.7.3.g DNP3 Analog Output Writings (Profile II) ......................................................... 3.7-34
3.7.4 MODBUS Protocol ................................................................................................. 3.7-37
3.7.4.a Inputs and Outputs ........................................................................................... 3.7-37
3.7.4.b Commands ....................................................................................................... 3.7-39
3.7.4.c Metering Values ................................................................................................ 3.7-41
3.7.4.d Meters ............................................................................................................... 3.7-43
3.7.4.e Analog Output Writings ModBus ...................................................................... 3.7-44
3.7.5 61850 Protocol ....................................................................................................... 3.7-47
3.7.5.a Validity Configuration ........................................................................................ 3.7-47
3.7.5.b CSWI Node ....................................................................................................... 3.7-48
3.7.5.c XCBR Node ...................................................................................................... 3.7-51
3.7.5.d XSWI Node ....................................................................................................... 3.7-52
3.7.5.e MCXL Node ...................................................................................................... 3.7-52
3.7.5.f RFTL Node ....................................................................................................... 3.7-53
3.7.5.g MMTR Node ..................................................................................................... 3.7-56
3.7.5.h LPHD Node ....................................................................................................... 3.7-57
3.7.5.i ATCC ................................................................................................................ 3.7-57
3.7.5.j IHMI .................................................................................................................. 3.7-59
3.7.5.k CALH ................................................................................................................ 3.7-59
3.7.5.l SIMG ................................................................................................................. 3.7-60
3.7.5.m GENGGIO ......................................................................................................... 3.7-60
3.7.5.n TGOGGIO and TGO2GGIO ............................................................................. 3.7-62
3.7.5.o YLTC ................................................................................................................. 3.7-63
3.7.1 Introduction
The purpose of this section is to define the communication parameters related to the
configuration for protocols defined in the equipment.
Users can access the configuration of the different protocols through the Communications
option in the main menu. By pressing on Communications a submenu drops down to display a
list of all the protocols supported by the equipment. This information is obtained from the
equipment profile.
By selecting the appropriate option of each submenu, the user accesses the screen where the
communication parameters for each protocol are configured. These parameters are what make
communication with the central unit possible.
3.7.1.a General Format and Screen Handling

The different communication screens are organized according to the following format:
The main screen contains a page frame, that is, there are two configuration areas that are
selectable by clicking on a tab, so only the information in the active tab is displayed. The two
tabs available for these screens are the Detail and List tabs. The protocol option parameters
can be configured in either of the two areas. The basic difference between the two is that the
Detail tab only shows information about the selected signal, while the List tab provides a
complete list of the configured signals with their respective parameters.
The Accept and Cancel buttons are used the same way as described in section Using
Controls.
3.7-2
BCID1207A
3.7 Communications
 Detail Page
At the top of the Detail page, a drop-down list is displayed with the full list of the signals that can
be configured for communications. When a signal is selected, the data representing the
communication parameters at the bottom of the screen are updated. For a signal to be included
in the communications data, simply activate the checkbox identifying the protocol configuration
option. For example, to include a specific signal as DNP3 contact, the desired signal must be
selected from the list of available signals.
Once the signal is

displayed as active in the
list, the labeled checkbox
is enabled (for this
example, as DNP3
Contact). In doing this,
®
the ZIVerlog
configuration module
enables the rest of the
controls in order to
configure the
communication signal
parameters, and it
calculates the DNP3
contact number while
giving the signal. This will
be the first free
communication number
at that time. The number
can be edited by the user
by means of the relevant
numeric control. The rest
of the parameters are
also initialized with their
default values.
 List Page
The List area includes all
the signals that have
been enabled for
communication in the
left-hand column. The
different parameters
applied to each of the
signals are displayed in
the two columns at the
right. New signals are
enabled on this screen
by right-clicking the
mouse and selecting the
New option (see section
Using controls). Similarly,
to delete configuration
signals, select the signal
you wish to delete and
then right-click the
mouse and select Delete.
3.7-3
BCID1207A
3.7.2 Procome
This option of the Communications menu opens a new submenu with the options the equipment
allows to be configured for this protocol. By selecting the desired submenu option, you can
access the screens for configuring the Events, Control Changes, Commands,
Measurements, Counters, and Digital and Analog Outputs for communication using the
Procome protocol.
3.7.2.a Events
This screen lets you configure the user-defined signals that will generate an event. Here is
where the control events, that will complement the equipment-defined protection events in the
log file, are configured. These events will be stored in the log file with the same format as the
protection events, except that the valid range of the records will be from 40000 to 40023. For
each of the records, the first 32 bits are assigned as activation bits and the remaining 32 bits
are deactivation bits. The activation and deactivation bits will be paired, although both status
conditions are not required to generate an event. The fields shown in the Detail tab are:
- Available
Signals: drop-
down list
containing all
user-defined
signals during
configuration
(see Digital
Signals).
- Event
Description: the
user can edit the
text representing
the event in this
text box. By
default, the
description will
match the
description of the signal whose change will generate the event. When the event log is
®
retrieved with ZiverCid , the text displayed for this type of event will appear in the box
preceded by the indication Activation of or Deactivation of, depending on the type of
status change.
3.7-4
BCID1207A
3.7 Communications
- Activation Generates an Event: if this checkbox is marked, an event is generated

when the selected signal (in the list of available signals) is activated. If it is not marked,
an event is not generated.
- Deactivation Generates an Event: if this checkbox is marked, an event is generated
when the selected signal (in the list of available signals) is deactivated. If it is not
marked, an event is not generated.
- Record Number: the number of the record where the event information is stored. The
event information is stored at a specific position in the record. This position is a record
bit. Each record can store up to 64 positions or bits. The first 32 are assigned as
activation events, and the last 32 are for deactivation events.
Valid range for control events: 40000- 40023
- Activation Bit: position (bit) in the record where the activation event is stored. As
indicated earlier, the activation and deactivation events are paired, although the two are
not required to be activated simultaneously. However, their position is always separated
32 bits. The configurations module makes this change automatically. When an event is
enabled, the first free position (by pairs) existing in the first record with free positions is
calculated.
Valid range for control events: 0-31
- Deactivation Bit: position (bit) in the record where the deactivation event is stored.
Valid range for control events: 32-63
The List tab lets the user

configure the same fields
as in the Detail section.
The List and Detail field matches are as follows:
Event Event Description

Act Activation generates an event
De Deactivation generates an event
Proc Reg Record Number
Act Bit Activation Bit
Deact Bit Deactivation Bit
3.7-5
BCID1207A
3.7.2.b Control Changes

This screen lets you
configure the signals that
will generate control
changes. When a
primary equipment unit
(usually a central unit)
makes a request for
control changes to the
equipment, the
equipment will send it the
ID for any
signal labeled as control
changes whose status
has changed since the
last time a request was
made.
The fields shown in the

Detail tab are:
- Signal Type: drop-down list containing the groups of signals that collect- the
equipment's digital signals. For more information, see section Signal types. The list of
available signals will depend on the selected group.
- Available Signals: list of digital equipment signals belonging to the selected group in
signal type. Signals that can be configured as control changes include all equipment-
defined signals and user-defined signals that are included in the configuration. A
maximum of 2048 Procome control changes can be labeled.
- Transmission Cause to be Generated: transmission cause generating the signal on
change of status. Indicates the transmission cause that is activated when a change in
the digital signal associated with the control change (ISC) occurs. The drop-down list
contains a list of the configured Transmission Causes. For further information, see
Transmission Causes below. The control change does not necessarily generate a
transmission cause (default option). The maximum number of signals that can generate
a transmission cause is 256.
- Associated Transmission Causes: causes for the change in a digital signal (ISC or
control change). It is used to determine the reason for the change. One control change
can be associated with different transmission causes; as a result, a complete list of
transmission causes defined for the configuration is displayed under the Description
heading (see Transmission Causes further below). A checkbox is displayed alongside
each of the cause descriptions. The checkbox (titled Act) indicates whether the
attached transmission cause is associated with the Procome control change (checkbox
marked) or not (no marks in checkbox).
- PROCOME Change: this checkbox indicates whether the selected signal is labeled as
a Procome control change (checkbox marked) or not (no marks in checkbox). A
maximum of 2048 Procome changes is allowed.
3.7-6
BCID1207A
3.7 Communications
- Change Number: procome label associated with the control change. Each time a new
control change is enabled, this value is established by default at the first free value for
control changes. The user can change it in order to give it the desired value. Two digital
signals cannot be labeled with the same Procome change number.
Valid Range: 0-2047.

Default Value: first free number starting with 0.
- Transmission Causes Button: this button accesses the screen for configuring valid
Transmission Causes. See Transmission Causes below.
Pressing the List tab tranfers you to the page listing the set of signals labeled as Procome
control changes, together with their associated parameters. As indicated earlier, everything that
is configured in the Detail tab can be configured in the List tab. To add or delete signals labeled
as Control Changes simply right-click on the mouse and select the desired option, as was
indicated for general format and handling of screens when discussing the List Page.
Change Available Signals marked as Change

Cause to be Generate Transmission Cause to be Generated
Change Nº Change Number
COTs Mask Associated Transmission Causes
To configure the Cause to be

Generated and the COTs mask
associated with a control change from
this page, double-click on the Cause
to be Generated checkbox or the
COTs Mask checkbox for the desired
control change. The screen to the
right is displayed when this is done.
The data are configured in the same

way as described above for the List
page.
3.7-7
BCID1207A
 Transmission Causes
Transmission Causes
are defined as a set of
identifiers that pinpoint
the reason for a change
in the control signal.
Some signals labeled as
control changes are also
capable of changing the
active cause when their
status changes. In this
way, changes posted by
communications can be
sent together with an
associated cause
indicating the reason for
the change.
The screen shown on the following page is used to configure the Transmission Causes. The
description and configurable parameters for a transmission cause are displayed at the top,
under the Detail title. The different causes can be accessed in two different ways:
- Using the Navigation Buttons located on the right side of the screen (for more
information about this type of control, see Using controls).
- Placing the cursor on the desired cause in the list displayed at the lower portion of the
screen under the heading Complete List of Transmission Causes. This list shows all
the causes enabled up to that moment, in addition to the parameters associated with
each cause. The maximum number of Transmission Causes that can be configured for
each piece of equipment is 32.
The fields that can be configured on this screen are:
- Identifier: number identifying the transmission cause when sent by communications.

(Procome).
Valid Range: 0-255

Default Value: 100
- Validity (ms): valid time of the cause. This is the time the associated cause is active in
the equipment. This time starts to count the moment the status, or the control change,
signal that 'generates the cause' is changed. The time is expressed in milliseconds.
Valid Range: 0 -10000 ms

Default Value: 0
3.7-8
BCID1207A
3.7 Communications
- Description: the description given to the cause in order to identify it. This description is
what is displayed in the control changes configuration screen (see Control Changes).
- Delete: deletes a transmission cause. When the transmission cause is deleted, the
masks and cause generating signals associated with the control change signals are
recalculated.
- New: enables a new control signal with default values:
Identifier: 100
Valid Time: 0
The maximum number of valid Transmission Causes per configuration is 32.
3.7.2.c Commands
This screen lets you configure the commands that will be sent via communications to the
Procome protocol.
The commands selected here to be used in communications can be referenced from ZiverCid®,
and are displayed under the Actions node. The commands are divided into two groups:
commands defined in the configuration as control commands and those defined as protection
commands. Each group is placed under a different node (though both are subnodes of
Actions) so that the communication commands defined here can be operated from ZiverCid®.
The commands that can be operated through communications are those actions that were
configured when defining the different command elements. For more information about the
command elements or their associated actions, see
section Commands.
The fields shown in the Detail screen are:
- Command
Element: drop-
down list with the
command
elements defined
in the
configuration.
The command
element is
completely user-
configurable and
can represent
any kind of
command, e.g.
from a signal up
to a breaker. For
more information
about the
command elements, see section 5.6.5, Commands. When a specific command element
is selected, the list in the control immediately below the element should be updated with
the available actions for that element. This list does not include those command
elements that have been defined without any associated actions.
3.7-9
BCID1207A
- Available Orders: list with the set of available actions for the element selected in the
previous list.
- Procome Command: this checkbox indicates whether the selected order is labeled as
a Procome control change (checkbox marked) or not (no marks in checkbox). A
maximum of 1024 Procome commands is allowed.
- Order Type: indicates whether the command is a control command or whether it is
considered a protection command.
- Order Number: Procome command label associated with the order for sending via
communications.
Valid Range: 0-1023

Default Value: First free number (not used, starting with 0).
The order number does not have to be unique. Orders associated with the same
Procome label can exist, provided the order type and DCO do not coincide
simultaneously. For example, the same order number can be used for two actions, both
of them labeled control, as long as one of them has the DCO set to ON and the other
has it set to OFF. The configuration module will be capable of making this change when
the user decides to use the same Procome order number.
However, it will not allow that both an order's number and parameters match another's.
If the user tries to perform this operation, the module will not allow it, displaying a
warning reminding the user of the reason for this prohibition.
- DCO: identification of the order type to allow double commands. Valid values are ON
and OFF. As noted in the previous point, two label orders with the same Procome
number, order type and DCO cannot coexist.
Pressing the List tab

transfers you to the page
listing the set of
command actions
labeled as Procome
orders, together with
their associated
parameters. As indicated
earlier, everything that is
configured in the Detail
tab can be configured in
the List tab.
3.7-10
BCID1207A
3.7 Communications
Element Command Element

Order Available Orders
Procome Procome Command
Order Type Order Type
Proc Nº Order Number
DCO DCO
New orders cannot be included in this list, since all orders have to be associated with the
defined command elements. To enable the order as a Procome command, activate the
checkbox marked Procome, just like in the List area. To make the order a non-Procome
command, deactivate the checkbox.
3.7.2.d Metering Values

configure the
measurements that will
be sent via
communications for the
Procome protocol.

Detail screen are:
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
analog signals,
i.e. the
magnitudes, which will be available in the equipment. For more information, see section
Signal types. The list of available signals will depend on the selected group.
- Available Signals: list of analog equipment signals (magnitudes) belonging to the
selected group in signal type. Signals that can be configured as measurements include
all equipment-defined signals and user-defined signals that are included in the
configuration.
- Procome Metering Value: this checkbox indicates whether the selected signal is
labeled as a Procome Metering (checkbox marked) or not (no marks in checkbox). A
maximum of 256 Procome measurements is allowed.
- Metering Value Number: Procome label associated with the measurement. Each time
a new Procome measurement is enabled, this value is established by default at the first
free value for measurements. The user can change it in order to give it the desired
value. Two magnitudes cannot be labeled with the same Procome metering number.
Valid Range: 0-255.

Default Value: First free number (not used, starting with 0).
3.7-11
BCID1207A
The parameters for calculating the measurement to be sent via communications are as follows:
- Offset: offset of the measurement.

- Maximum Limit: taken initially from the bottom of the measurement scale.
- Dependent on Rated Value: this checkbox indicates whether the measurement
calculation is going to be performed depending on the signal's rated value (checkbox
marked ) or not (no marks in checkbox). One formula or another will be displayed
depending on whether or not the calculation information at the bottom of these
parameters is marked.
The user can change the value of these parameters to send the desired value via
communications. For example, if the user wishes to send the measurement value directly (not in
accounts), this value can be set at 4095 and the operation not be performed depending on the
nominal value. Thus, using the second formula, the value sent via communications is the
measurement value (considering offset 0) directly.
The equations for calculating the measurement to be sent via communications are as follows:
- Depending on the nominal value:
(Measurement  offset) 4095

MeasurementComs  
RatedValue limit
- Regardless of the nominal value:
4095
MeasurementComs  (Measurement  offset) 
limit

listing the set of signals
labeled as Procome
measurements, together
with their associated
the List tab. To add or
delete measurements,
simply select the
appropriate menu option
that is displayed when
right-clicking the mouse.
Signal Available Signal Procome Measurement

Procome Nº Measurement number
Proc Offset Offset
Proc Limit Upper limit
Dep Rated Depending on the rated value
3.7-12
BCID1207A
3.7 Communications
3.7.2.e Meters
configure the meters that
will be sent via
Procome protocol.

Detail screen are:
 Signal Type: drop-

down list with the
groups of signals
containing all the
equipment's analog
signals, i.e. the
magnitudes, which
will be available in the
equipment. For more
information, see section Signal types. The list of available signals will depend on the
selected group.
 Available Signals: list of analog equipment signals (magnitudes) belonging to the selected
group in signal type. Signals that can be configured as meters include all equipment-defined
signals and user-defined signals that are included in the configuration.
 Procome Meter: this checkbox indicates whether the selected signal is labeled as a
Procome Meter (checkbox marked) or not (no marks in checkbox). A maximum of 256
Procome counters is allowed.
 Pulse Meter Number: Procome label associated with the meter. Each time a new Procome
Meter is enabled, this value is established by default at the first free value for meters. The
user can change it to give it the desired value. Two magnitudes cannot be labeled with the
same Procome Meter number.
Valid Range: 0-255.

Default Value: first free number (not used, starting with 0).
3.7-13
BCID1207A

listing the set of analog
signals labeled as
Procome counters,
together with their
associated parameters.
As indicated earlier,
everything that is
delete counters, simply
select the appropriate
menu option that is
displayed when right-
clicking the mouse.
The List and Detail field

matches are as follows:
Signal Available signal Procome Counter

Procome Nº Counter Number
3.7.2.f Output Writings

Output means any input or output, software or hardware, analog or digital, in the equipment
whose value is set by the primary unit (generally a central unit). It is called an output because it
is an output datum from the primary station's point of view, since the primary station determines
the value of this signal.
From the application's point of view, it is not convenient to write directly to a hardware output,
since it could be part of the equipment's direct logic outputs and both values could be
contradictory (in addition to the risk of leaving a hardware output with a set value). The ideal
application is writing over equipment logical inputs, even though they may be internally routed
toward the secondary station's hardware outputs.
For this reason, the configurations module will not let those signals that are already assigned a
value or that take on a value when executed in the logic, by a command, etc., to be configured
as output writing signals (both analog and digital). For more information about these limitations,
see section Signal Restrictions.
As described above, the output writing signals can be digital and analogical. The way each of
them is configured is explained below.
3.7-14
BCID1207A
3.7 Communications
 Digital Output Writing Signals

configure the digital
output writing signals that
will be sent via
Procome protocol.

Detail screen are:
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
digital signals
which will be
available in the equipment. For more information, see section Signal Types. The list of
signal type. Signals that can be configured as output writing signals include all IED-
defined signals and user-defined signals that are included in the configuration. A
maximum of 1024 Procome digital writing signals can be labeled.
- Output Writing Signal: this checkbox indicates whether the selected signal is labeled
as a Procome Output Writing Signal (checkbox marked) or not (no marks in
checkbox). A maximum of 1024 Procome digital output writing signals is allowed.
- Procome Number: Procome label associated with the digital output writing signal.
Each time a new Procome output writing signal is enabled, this value is established by
default at the first free value for outputs. The user can change it to give it the desired
value. Two digital output writing signals cannot be labeled with the same Procome
writing signal number (ISS).

3.7-15
BCID1207A

labeled as Procome
digital output writing
signals, together with
their associated
delete signals labeled as
Output Writing Signals,
simply right-click the
mouse button and select
the desired option, as
indicated for the List
Page, or disable the
Proc checkbox for each
of the signals.
Signal Available Output Writing Signal (digital)

Proc Output Writing Signal
ISS Nº Procome Number
3.7-16
BCID1207A
3.7 Communications
 Analog Output Writing Signals

This screen lets you configure the analog output writing signals that will be sent via
communications for the Procome protocol.
- Command on element: select this option to show to the right of the control a list of
analog command elements defined in the configuration as well as actions defined for
each element.
- Command on signal: select this option to show to the right of the control a list of analog
signal types as well as signals defined for each type.
- Command element: this drop down control is shown only if the Command on element
option has been selected. It shows a list with all analog command elements defined in the
configuration. For more information on command elements see chapter Commands. A
drop down list of Available Commands will be displayed as a function of the selected
element and detail area controls will be updated.
- Available commands: list of actions of the analog command element selected in the
Command Element control. Detail area controls will be updated as a function of the
selected command.
- Signal Type: drop-down list with the groups of signals containing all the equipment's
analog signals which will be available in the equipment. For more information, see section
selected group in signal type. Signals that can be configured as analog output writing
signals include all equipment-defined signals and user-defined signals that are included
in the configuration.
- Output Writing Signal: this checkbox indicates whether the selected signal is labeled as
a Procome Analog Output Writing Signal (checkbox marked) or not (no marks in
checkbox). A maximum of 256 Procome analog output writing signals is allowed.
- Procome Number: Procome label associated with the analog output writing signal. Each
time a new Procome output writing signal is enabled, this value is established by default
at the first free value for outputs. The user can change it in order to give it the desired
value. Two analog output writing signals cannot be labeled with the same Procome
analog writing signal number.
Valid Range: 0-255.

The parameters to be used for the calculation of analog output writing received through
communications are as follows:
- Offset: offset of analog output writing.

- Upper Limit: in principle it is the full scale of the analog output writing.
- As a Function of Rated Value: this checkbox states whether analog writing calculation
is made as a function of rated signal value (box checkmarked) or not (empty checkbox).
Different formulas will be shown depending on whether calculation data in the lower part
is checkmarked or not.
3.7-17
BCID1207A
Necessary equations for the calculation of measurements received through communications are
as follows:
- As a function of the rated value:

RatedValue limit
- Irrespective of the rated value:
4095
limit
Pressing the List tab transfers you to the page listing the set of signals labeled as Procome
analog output writing signals, together with their associated parameters. As indicated earlier,
everything that is configured in the Detail tab can be configured in the List tab.
To add or delete signals labeled as Output Writing Signals, simply right-click the mouse
button and select the desired option, as indicated in the List Page section, or disable the Proc
checkbox for each of the signals.
Signal Available Output Writing Signal (analog)

Proc Output Writing Signal
ISS Nº Procome Number
Offset Offset
Limit Maximum Limit
Rated F. Dependent on Rated Value
3.7-18
BCID1207A
3.7 Communications
3.7.3 DNP3
This option of the Communications menu opens a new submenu with the options the equipment
allows to be configured for this protocol. By selecting the desired submenu option, you can
access the screens for configuring the Contacts, Commands, Measurements and Counters
for communication using the DNP3 protocol.
3.7.3.a Contacts
This screen lets you configure the digital signals that will be considered contacts for
communication through the DNP3 protocol.
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
digital signals.
The list of
available signals
will depend on
the selected
group. For more
information, see
section Signal
types.
- Available
Signals: list of
digital
equipment signals belonging to the selected group in signal type. Signals that can be
configured as counters include all equipment-defined signals and user-defined signals
that are included in the configuration.
- DNP3 Contact: this checkbox indicates whether the selected signal is labeled as a
DNP3 contact (checkbox marked) or not (no marks in checkbox). A maximum of 256
contacts is allowed.
- DNP3 Number: DNP3 label associated with the contact. Each time a new contact is
enabled, this value is established by default at the first free value starting with 0. The
user can edit this in order to give it the desired value. Two digital signals cannot be
labeled with the same DNP3 contact number.
Valid Range: 0-255.

Default Value: first free number starting with 0.
3.7-19
BCID1207A

labeled as DNP3
contacts, together with
their associated
the List tab.
To add or delete signals

labeled as Contacts,
simply right-click the
mouse button and select
the desired option, as
Page, or disable the
DNP3 checkbox for the
signal you wish to delete.
Signal Available signals marked as Contacts

DNP3 DNP3 Contact
Nº DNP3 DNP3 Number
3.7.3.b Commands
This screen lets you configure the commands that will be sent via communications for the DNP3
protocol.
Commands on elements or directly on the signal can be made in DNP3. Commands on

elements are, in reality, commands relating to the actions configured when defining each of
the command elements (for more information about command elements or their associated
actions, see section Commands).
From the application's point of view, it is not convenient to perform a command directly to a
hardware output, since it could be part of the equipment's direct logic outputs and both values
could be contradictory (in addition to the risk of leaving a hardware output with a set value). For
this reason, the configurations module will not let those signals that are already assigned a
value or that take on a value when executed in the logic, or signals whose value is established
by the primary station (or other equipment), to be configured as DNP3 commands). It will,
however, allow different commands to be performed on the same signal. For more information
about these limitations, see section Signal Restrictions.
3.7-20
BCID1207A
3.7 Communications
- DNP3
Command:
drop-down list
with all the
enabled DNP3
commands. The
displayed text
consists of a
number, its
DNP3 order
label, followed by
a description of
the command.
This description
will match the
signal's text for
commands on
signals. For
commands on
elements, the description will be the description of the action, with ]the name of the
command element to which the action belongs in parentheses.
- Command over Element: this option is marked if the selected DNP3 command (upper
drop-down list) is performed on a command element action. This value is for information
purposes only; it cannot act directly on the control.
- Command over Signal: this option is marked if the selected DNP3 command (upper
drop-down list) is performed on a digital signal. This value is for information purposes
only; it cannot act directly on the control.
- Command Element: description of the command element containing the action labeled
as DNP3 command. This is a control for informational purposes only; no actions can be
taken regarding this control (for more information about command elements, see
section Commands).
- Available Commands: action of the command element labeled as DNP3 command.
This control is for information purposes only.
- Involved Signal: signal labeled as DNP3 command. This control is for informational
purposes only. To see which signals can be labeled as commands, consult section
Signal restrictions.
- Block Signal: a digital signal that prevents execution of the command if active. This
control is for informational purposes only.
- Order Number: DNP3 command label associated with the order for sending via
communications.

The order number does not have to be unique. Orders associated with the same DNP3
label can exist, provided a set of Trip/Close - execution type permissions does not
coincide simultaneously. The module will not allow both an order's number and
parameters to match another's. If the user tries to perform this operation, the module
will not allow it, displaying a warning reminding the user of the reason for this
prohibition.
3.7-21
BCID1207A
- Permissions: depicts the type of execution the command labeled DNP3 is capable
of allowing and performing. When a DNP3 command is executed, in addition to the
label to which the command is directed, a series of parameters, including the
trip/close and execution type pair, should be sent to identify the command. Before
executing the command the pair is checked for validity; that is, if those permissions
for that specific DNP3 label have been activated in the configuration.
Trip/Close: being a permissions mask, a single DNP3 command label can

be configured with the three permissions active at the same time.
Valid values: default, trip and close.
Running Type: possible execution types for the command label. These
are not exclusive. A single label can allow ON and OFF pulse commands
or ON and OFF status change
Valid values: Latch On, Latch Off, Pulse On, Pulse Off.
In both cases, at least one checkbox must be selected. Only a pulse with a
fixed duration will ever be executed on an order element (signal status
changes are not executed).
- Delete: button for deleting the selected DNP3 command (the highlighted command
in the drop-down list).
- New: button providing access to screens under the heading Select new command
for selecting the signal or command to be enabled as a DNP3 command.
Depending on the selected option, command over element or command over signal, the
screen presentation will be the first or second shown below, respectively. In this case, the
control is the same as that explained for the DNP3 commands detail screen, with the difference
that this control is operable, that is, the user can select the desired option. It is not a control for
informational purposes only.
Command Element:
drop-down list with all the
command elements
defined in the
configuration. For more
information about the
command elements, see
section Commands.
Available Commands: list of actions for the selected command element. The user must select
the action to be labeled as a DNP3 command. This list is updated every time the user selects a
different command element in the previous list. For more information about actions associated
with a command element, see section Commands.
3.7-22
BCID1207A
3.7 Communications
Signal Types: drop-

down list with all the
equipment's digital signal
types. For more
information, see section
Signal Types.
Involved Signal: drop-

down list with the digital
signals belonging to the
group or type selected in the previous list. Only those signals that can be converted to DNP3
commands are displayed. For safety reasons, the signals that already have an assigned value,
or that take on a value through the equipment's logic, or are labeled as output writing signals,
etc. are not displayed. For more information, see section Signal restrictions.
Blocking Signal: drop-down list with the digital signals belonging to the group or type selected
in the signal types list located to the left.
Blocking Signal Not Used: this selectable box lets you indicate whether the block signal
selected in the previous list will be taken into account or not. If the checkbox is marked, the
command will not have an associated block signal.
OK: by pressing this button, the selected signal or action is enabled as a DNP3 command and
is displayed in the DNP3 commands screen.
Cancel: by pressing this button, the selected signal or action is not enabled as a DNP3
command. The commands screen is displayed with no changes..

listing the set of
command actions
labeled as DNP3 orders,
together with their
Permission masks on
this screen cannot be
configured; they are
included here for
information only.
The List and Detail field

matches are as follows:
Command DNP3 Command

DNP3 Nº Order Number
Msk trip/close Trip/close permissions
Msk running Execution type permissions
3.7-23
BCID1207A
3.7.3.c Metering Values (Profile I)

configure the
be sent via
DNP3 protocol (profile I).

Detail screen are:
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
analog signals,
i.e. the
magnitudes, which will be available in the equipment. For more information, see section
configuration.
- DNP3 Metering Value: this checkbox indicates whether the selected signal is labeled
as a DNP3 Metering Value (checkbox marked) or not. A maximum of 256 DNP3
metering values is allowed.
- Metering Value Number: DNP3 label associated with the measurement. Each time a
new DNP3 metering value is enabled, this value is established by default at the first
free value for measurements. The user can change it in order to give it the desired
value. Two magnitudes cannot be labeled with the same DNP3 measurement number.
Valid Range: 0-255.

- As a Function of the Primary Value: states whether the measurement value is sent as
a function of the primary value (box checkmarked) or the secondary (default value,
empty checkbox).
- DNP3 Metering Change: indicates whether a change in the measurement value that
sets the new value above or below the defined bands will be registered as a change
(checkbox marked). The band is defined according to a nominal value percentage and
®
can be set using ZiverCid . A maximum of 16 DNP3 metering changes can be
configured.
3.7-24
BCID1207A
3.7 Communications
T The parameters for calculating the measurement to be sent via communications are as
follows:

- Maximum Limit: taken initially from the bottom of the measurement scale.
- Dependent on Rated Value: this checkbox indicates whether the measurement
marked) or not (no marks in checkbox). One formula or another will be displayed
accounts), this value can be set at 32767, and the operation not be performed, depending on
the nominal value. Thus, using the second formula, the value sent via communications is the
The equations for calculating the measurement to be sent via communications are as follows:

RatedValue limit
32767
limit

labeled as DNP3
metering values,
together with their
everything that is
simply select the
3.7-25
BCID1207A
Signal Available Signal DNP3 Measurem.

DNP Nº Measurement number
Offset Offset
Limit Maximum limit
F. nom Depending on the rated value
Change DNP3 measurement number
Setting Change setting
Primary As a function of the primary value
3.7.3.d Metering Values (Profile II)

configure the
be sent via
DNP3 protocol (profile II).

Detail screen are:
- Signal Type:
drop-down list with
the groups of
signals containing
all the equipment's
analog signals,
i.e. the
magnitudes, which
will be available in the equipment. For more information, see section Signal types. The list
of available signals will depend on the selected group.
configuration.
General Datas:
- DNP3 Measurement: this checkbox indicates whether the selected signal is labeled as a
DNP3 measurement (checkbox marked) or not (no marks in checkbox). A maximum of
256 DNP3 measurements is allowed.
- Measurement Number: DNP3 label associated with the measurement. Each time a new
DNP3 measurement is enabled, this value is established by default at the first free value
for measurements. The user can change it in order to give it the desired value. Two
magnitudes cannot be labeled with the same DNP3 measurement number.
Valid Range: 0-63.

- Measurement in engineering units: activation of this parameter states that the

measurement is sent as a value and not as percentage of the maximum value.
3.7-26
BCID1207A
3.7 Communications
- Multiplier factor: factor by which the measurement is multiplied for transmission through
communications (only meaningful when the measurement is transmitted in engineering
units). Default value is 1.0. Can be either positive or negative and 4 decimal point
precision. Dimensionless.
- DNP3 Measurement Change: indicates whether a change in the measurement value
that sets the new value above or below the defined bands will be registered as a change
(checkbox marked). The band is defined according to a nominal value percentage and
can be set using ZiverCid®. A maximum of 16 DNP3 measurement changes can be
configured.
The parameters for calculating the measurement to be sent via communications are as follows:
- Offset: offset of the measurement. Always expressed in measurement secondary

values. Irrespective of flags "Measurement in rated value "or "Measurement in primary
value".
- Maximum Value: in principle, it is taken as measurement full scale. Values depend on
the activated flags. Expressed in:
o Secondary Units when there are no active flags.
o Times the rated value if flag "As a function of the rated value" is active.
o Primary Units if flag "As a function of the primary value" is active.
o Times the Primary Rated Value if both flags are active.
- Depending on Rated Value: this checkbox indicates whether the measurement
marked) or not (no marks in checkbox). One formula or another will be displayed
a function of the primary value (box checkmarked) or secondary (default value, empty
checkbox). This flag is only meaningful for static magnitudes (relay magnitudes) as user
magnitudes always have a 1:1 transformation ratio (TR = 1).
communications. First, establish whether the measurement is sent as a value or as percentage
of the maximum value. General equations for the calculation of measurements transmitted
through communications:
- Percentage communications measurement value:
TR ( Measurement  offset )
MeasurementComs    (ComsMaxValue)
Vn MaxValue
- Engineering unit communications measurement value:
TR
MeasurementComs   ( Measurement  offset )  ( MultiplierFactor)
Vn
3.7-27
BCID1207A
Where:
TR: Transformation ratio

Vn: Rated value
ComsMaxValue: Maximum value to be transmitted through communications. For
example, if measurement request is made in 16 bits " ComsMaxValue " would be
2^15-1. If request is made in 32 bits (higher precision) this value would be 2^31-1.
If flag As a function of the primary value is not active, in formulas, the value TR would be
considered as "1".
If flag As a function of the rated value is not active, in formulas, the value Vn would be
considered as "1".

labeled as DNP3
measurements, together
with their associated
simply select the
Signal Available Signal for DNP3 Measur.

DNP Nº Measurement number
Offset Offset
Max Limit Maximum Limit
Rated Value Depending on the rated value
Change Change in DNP3 Measurement
Setting Change setting
Primary Depending on the primary value
Ing Units In engineering units
Mul. Fac. Multiplier Factor
3.7-28
BCID1207A
3.7 Communications
3.7.3.e Meters
configure the meters that
will be sent via
DNP3 protocol.

Detail screen are:
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
analog signals,
i.e. the
magnitudes,
which will be available in the equipment. For more information, see section Signal
types. The list of available signals will depend on the selected group.
selected group in signal type. Signals that can be configured as counters include all
equipment-defined signals and user-defined signals that are included in the
configuration.
- DNP3 Meter: this checkbox indicates whether the selected signal is labeled as a DNP3
meter (checkbox marked) or not (no marks in checkbox). A maximum of 20 DNP3
meters is allowed.
- Pulse Meter Number: DNP3 label associated with the counter. Each time a new DNP3
counter is enabled, this value is established by default at the first free value for meters.
The user can change it in order to give it the desired value. Two magnitudes cannot be
labeled with the same DNP3 meter number.
Valid Range: 0-19

Default value: first free number (not used, starting with 0)
- Change in DNP3 Counter: states whether a change in the counter value is to be

annotated as a change (box checkmarked) so that that new value is located above or
below the defined band. The band is defined as percentage of the rated value and is
®
adjustable from the ZiverCid . A maximum of 16 signals as DNP3 counter changes can
be configured.
3.7-29
BCID1207A

labeled as DNP3
counters, together with
their associated
menu option that is
clicking the mouse.
Signal Available signal that is a DNP3 meter

DNP3 Nº Meter number
Change Change in DNP3 meter
3.7-30
BCID1207A
3.7 Communications
3.7.3.f Analog DNP3 Output Writings (Profile I)

This screen (see following figures) allows to configure analog output writings to be transmitted
through communications for protocol DNP3.
Fields shown on the Detail screen are as follows:
- Writing on
Command: this
option is
selected to show
to the right of the
controls the list
of analog
command
elements defined
in the
configuration as
well as actions
defined for each
element.
- Writing on
Signal: this
option is
selected to show to the right of the controls the list of analog signal types as well as
signals defined for each type.
- Command Element: this drop down control is only shown when selecting the
'Command on element' option. A list with all analog command elements defined in the
configuration will be shown. For more information on command elements see section
Commands. A drop down list will be filled with the 'Available Commands' for the
selected element and the detail area controls will be updated.
- Available Commands: list of actions of the analog command element selected in
'Command Element' control. Detail area controls are updated as a function of the
selected command.
- Type of Signal: drop down list containing groups of signals into which all analog signals
available for the equipment are grouped. For more information see section Types of
Signals. The list of available signals will depend on the selected group.
- Available Signals: list of equipment analog signals (magnitudes) belonging to the
group selected in 'types of Signal'. Signals that can be configured as analog output
writings are all those defined in the equipment plus those defined by the user pertaining
to the configuration, not being yet connected to a protection value or from the logic.
- Output Writing: this selection checkbox states whether the signal or selected analog
command element action is tagged as Analog Output Writing DNP3 (box checkmarked)
or not (empty checkbox). A maximum of 256 analog output writings DNP3 are allowed.
A new analog writing is created by checking the box and deleted by unchecking.
3.7-31
BCID1207A
- DNP3 Number: DNP3 tag associated to the analog output writing. Any time a new
DNP3 output writing is created, this value will be established by default to the first free
output value. It can be user modified with the wanted value. Two analog output writings
may not be tagged with the same analog DNP3 writing number.
Validity Range: 0-255.

Default Value: first 'free' number (not used starting from 0).
empty checkbox).

- Upper limit: in principle it is the full scale of the analog output writing.
- As a function of rated value: this checkbox states whether analog writing calculation is
made as a function of rated signal value (box checkmarked) or not (empty checkbox).
Different formulas will be shown depending on whether calculation data in the lower part
is checkmarked or not.
Necessary equations for the calculation of measurements received through communications are
as follows:

MeasurementsComs  
RatedValue limit
32767
MeasurementsComs  (Measurement  offset) 
limit
3.7-32
BCID1207A
3.7 Communications
Pressing on tab tagged

as List displays the
screen that lists the set
of signals tagged as
DNP3 analog output
writing, together with the
As already stated, all that
has been configured in
the Detail screen can be
configured in the List
screen. Signals tagged
as Output Writings can
be added or deleted by
just pressing the right
mouse button and
selecting the desired
option, as stated in
section List Page, or
else, unchecking the
DNP3 box for each
signal.
The connection between fields in the List page and Detail page is as follows:
Signal DNP3 Analog Output Available Signal

DNP3 Writing Output
Nº ISS DNP3 Number
Offset Offset
Límite Upper Limit
F. Nom As a function of rated value
Primario As a function of primary value
3.7-33
BCID1207A
3.7.3.g DNP3 Analog Output Writings (Profile II)

Analog output writings transmitted through communications, for protocol DNP3, are configured
in this screen (see following figures).
Detail screen shows the following fields:
- Writing on command: this option is selected to show to the right of the controls the list of
analog command elements defined in the configuration as well as actions defined for
each element.
- Writing on signal: this option is selected to show to the right of the controls the list of
analog signal types as well as signals defined for each type.
- Command element: this drop down control is only shown when selecting the 'Command
on element' option. A list with all analog command elements defined in the configuration
will be shown. For more information on command elements see section Commands. A
drop down list will be filled the 'Available Commands' for the selected element and the
detail area controls will be updated.
- Available commands: list of actions of the analog command element selected in
selected command.
- Type of signal: drop down list containing groups of signals into which all analog signals
- Available signals: list of equipment analog signals (magnitudes) belonging to the group
selected in 'types of Signal'. Signals that can be configured as analog output writings are
all those defined in the equipment plus those defined by the user pertaining to the
configuration, not being yet connected to a protection value or from the logic.
command element action is tagged as Analog Output Writing DNP3 (box checkmarked)
or not (empty checkbox). A maximum of 64 analog output writings DNP3 are allowed. A
new analog writing is created by checking the box and deleted by unchecking.
- DNP3 number: DNP3 Tag associated to the analog output writing. Any time a new DNP3
output writing is created, this value will be established by default to the first free output
value. It can be user modified with the wanted value. Two analog output writings may not
be tagged with the same analog DNP3 writing number.
Validity Range: 0-63.

Default Value: first 'free' number (not used starting from 0).
empty checkbox). This flag is only meaningful for writings associated to static
magnitudes (relay magnitudes) as user magnitudes always have a 1:1 transformation
ratio (TR = 1).
3.7-34
BCID1207A
3.7 Communications
Parameters for the calculation of measurements transmitted through communications are:
- Offset: offset of analog output writing. Always expressed in measurement secondary

units. It is irrespective of the flags "Rated value measurement "or "Primary value
measurement ".
- Maximum value: in principle, it is the measurement full scale. Values depend on the
activated flags. Expressed in:
o Secondary units when there are no active flags.
o Times the rated value if flag "As a function of the rated value" is active.
o Primary units if flag "As a function of the primary value" is active.
o Times the primary rated value if both flags are active.
- As a Function of the Rated Value: this selection checkbox states whether the analog
writing calculation is a function of the signal rated value (box checkmarked) or not (empty
checkbox). Different formulas will be shown depending on whether calculation data in the
lower part is checkmarked or not.
- As a Function of the Primary Value: states whether the analog output writing is a
function of the primary value (box checkmarked) or secondary (default value, empty
checkbox).
The user can modify these parameters to transmit through communication the desired
value. First, establish whether the analog output writing is sent as measurement value or
as percentage of the maximum value.
General equations for the calculation of analog output writing transmitted through
communications are:
- Percentage communications measurement value:
TR ( Measurement  offset )
MeasurementsComs    (ComsMaxValue)
Vn MaxValue
- Engineering unit communications measurement value:
TR
MeasurementsComs   ( Measurement  offset )  ( MultiplierFactor)
Vn
3.7-35
BCID1207A
Where:
TR: Transformation Ratio.

Vn: Rated value.
ComsMaxValue: maximum value to be transmitted through communications. For
example, if measurement request is made in 16 bits "ComsMaxValue" would be 2^15-1.
If request is made in 32 bits (higher precision) this value would be 2^31-1.
If flag As a function of the primary value is not active, in formulas, the value TR would be
considered as "1".
If flag As a function of the rated value is not active, in formulas, the value Vn would be
considered as "1".
Pressing on tab tagged as List displays the screen that lists the set of signals tagged as DNP3
analog output writing, together with the associated parameters. As already stated, all that has
been configured in the Detail screen can be configured in the List screen. Signals tagged as
Output Writings can be added or deleted by just pressing the right mouse button and selecting
the desired option, as stated in section List Page, or else, unchecking the DNP3 box for each
signal.
The connection between fields in the List page and Detail page is as follows:
Signal DNP3 Analog Output Available Signal

DNP3 Writing Output
Nº ISS DNP3 Number
Offset Offset
Valor Máx. Maximum Value
F. nom As a function of rated value
Primary As a function of primary value
3.7-36
BCID1207A
3.7 Communications
3.7.4 MODBUS Protocol

This option of the Communi-cations menu opens a new submenu with the options the
equipment allows to be configured for this protocol. By selecting the desired submenu option,
you can access the screens for configuring the Inputs and Outputs, Commands,
Measurements and Counters for communication via the MODBUS protocol.
3.7.4.a Inputs and Outputs

configure the digital
signals that will be
considered ModBus
Inputs or Outputs.

Detail screen are:
- Signal Type:
drop-down list
containing the
groups of signals
containing all the
equipment's digital
signals. For more
information, see
section Signal
Types. The list of
'signal type'. Signals that can be configured as ModBus inputs and outputs include all
equipment-defined signals and user-defined signals that are included in the configuration.
Note that a signal cannot be labeled as an input and an output at the same time.
- Inputs Starting Address: starting address for all ModBus inputs. Signals labeled as
Modbus inputs will take consecutive values starting with this value.
- Outputs Starting Address: starting address for all ModBus outputs. Signals labeled as
Modbus outputs will take consecutive values starting with this value.
- Modbus Signal: this checkbox indicates whether the selected signal is labeled as a
Modbus input or output (checkbox marked) or not (no marks in checkbox). By default, it
is enabled as a Modbus Input. A maximum of 1024 Modbus Inputs and 1024 Modbus
Outputs is allowed.
- Input, Output: control for the type of label assigned to the selected signal. A signal
cannot be labeled simultaneously as a Modbus Input and a Modbus Output.
3.7-37
BCID1207A
- Modbus Address: Modbus label associated with the input or output signal. For the
Modbus protocol, the communication labels given to these signals have to be
consecutive. If the user edits the Modbus number value and gives it a value that was
already assigned to another signal, then the new value will be assigned and the other
values are shifted to avoid leaving 'gaps'. Each time a new Modbus signal is enabled, this
value is established by default at the first free value from the starting address for the
signal type (Modbus input or output).
Valid Range for Inputs: from the starting address to (starting address + max
number of enabled inputs -1).
Valid Range for Outputs: from the starting address to (starting address + max
number of enabled outputs -1).
Default Value: First free number beginning with the starting address.

labeled as Modbus
Inputs or Outputs,
together with their
everything that is
delete signals labeled as
Inputs or Outputs, simply
right-click the mouse
button and select the
desired option, as
Page.
Signal Available signals marked as Modbus Inputs or Outputs

Modbus Nº Modbus Direction
Type Inputs and Outputs
3.7-38
BCID1207A
3.7 Communications
3.7.4.b Commands
This screen lets you configure the commands that will be sent via communications for the
Modbus protocol.
The commands that can be operated through communications are those actions that were
configured when defining the different command elements. For more information about the
command elements or their associated actions, see section Commands
- Command Element: drop-down list with the command elements defined in the
configuration. The command element is completely user-configurable and can represent
any kind of command, e.g. from a signal up to a breaker. For more information about the
command elements, see section Commands. When a specific command element is
selected, the list in the control immediately below the element should be updated with the
available actions for that element. This list does not include those command elements
that have been defined without any associated actions.
- Available Commands: list with the set of available actions for the element selected in
the previous list.
- Command Number: this checkbox indicates whether the selected order is labeled as a
Modbus command (checkbox marked) or not (no marks in checkbox). A maximum of
1024 Modbus commands is allowed.
- Order Number: Modbus command label associated with the order for sending via
communications.

Default Value: First free number (not used, starting with 0.
The order number does not have to be unique. Orders associated with the same Modbus
label can exist, provided the COILS do not coincide. For example, the same order
number can be used for two actions, as long as one of them has the COIL set to ON and
the other has it set to OFF. The configuration module will be capable of making this
change when the user decides to use the same Modbus order number. However, it will
not allow both an order's number and parameters to match another's. If the user tries to
perform this operation, the module will not allow it, displaying a warning reminding the
user of the reason for this prohibition.
- COIL: identification of the order type to allow double commands. Valid values are ON and
OFF. As noted in the previous point, two orders or labels with the same Modbus number
and COIL cannot coexist.
3.7-39
BCID1207A

switches you to the page
listing the set of
command actions
labeled as Modbus
orders, together with
their associated
the List tab.
everything that is
the List tab.
Element Command Element

Command Available orders
Modbus Modbus Command
Modbus Nº Order Number
COIL COIL
New orders cannot be included in this list, since all orders have to be associated with the
defined command elements. To enable the order as a Modbus command, activate the
checkbox marked Modbus, just like in the List area. To make the order a non-Modbus
command, deactivate the checkbox.
3.7-40
BCID1207A
3.7 Communications
3.7.4.c Metering Values

configure the metering
values that will be sent
via communications for
the Modbus protocol.
Detail screen are:
- Metering Value
Starting
Address:
starting address
for all ModBus
measurements.
The magnitudes
labeled as
Modbus
measurements
will take consecutive values starting with this value.
analog signals, i.e. the magnitudes, which will be available in the equipment. For more
information, see section Signal Types. The list of available signals will depend on the
selected group.
selected group in 'signal type'. Signals that can be configured as measurements include
configuration.
- Modbus Metering Value: this checkbox indicates whether the selected signal is labeled
as a Modbus measurement (checkbox marked) or not (no marks in checkbox). A
maximum of 256 Modbus measurements is allowed.
- Meatering Value: Modbus label associated with the measurement. Each time a new
Modbus measurement is enabled, this value is established by default at the first free
value for measurements. For the Modbus protocol, the communications labels given to
these signals have to be consecutive. If the user edits the Modbus number value and
gives it a value that was already assigned to another signal, then the new value will be
assigned and the other values are shifted to avoid leaving 'gaps'. Two magnitudes
cannot be labeled with the same Modbus measurement number.
Valid Range: starting address (max. no. of measurements enabled + starting

address - 1)
Default value: first free number (not used, starting with the starting address for the
measurements).
3.7-41
BCID1207A
Parameters for calculating the measurement to be sent via communications:

- Maximum limit: taken initially from the bottom of the measurement scale.
- Dependent on rated value: this checkbox indicates whether the measurement
calculation is going to be performed depending on the signal's nominal value (checkbox
marked) or not (no mark). One formula or another will be displayed depending on
whether or not the calculation information at the bottom of these parameters is marked.
accounts), this value can be set at 32767, and the operation not be performed depending on the
nominal value. Thus, using the second formula, the value sent via communications is the
Equations for calculating the measurement to be sent via communications:
- Depending on the nominal value:

RatedValue limit
- Regardless of the nominal value:
32767
limit

transfers you to the
screen listing the set of
signals labeled as
Modbus measurements,
together with their
everything that is
simply select the
Signal Available signal that is a Modbus measurement

Modbus Nº Measurement number
Offset Offset
Limit Upper Limit
3.7-42
BCID1207A
3.7 Communications
3.7.4.d Meters
configure the counters
that will be sent via
ModBus protocol.

Detail screen are:
- Metering Values
Starting Address:
starting address
for all ModBus
counters. The
magnitudes
labeled as
ModBus counters
will take
consecutive values starting with this value.
analog signals, i.e. the magnitudes, which will be available in the equipment. For more
information, see section 5.2.6.b, Signal types. The list of available signals will depend on
the selected group.
selected group in 'signal type'. Signals that can be configured as counters include all
equipment-defined signals and user-defined signals that are included in the configuration.
- Modbus Meter: this checkbox indicates whether the selected signal is labeled as a
ModBus counter (checkbox marked) or not (no marks in checkbox). A maximum of 256
ModBus counters is allowed.
- Pulse Meter Number: ModBus label associated with the counter. Each time a new
ModBus counter is enabled, this value is established by default as the first free value for
counters from the starting address. The user can change it in order to give it the desired
value. For the ModBus protocol, the communications labels given to these signals have
to be consecutive. If the user edits the ModBus number value and gives it a value that
was already assigned to another signal, then the new value will be assigned and the
other values are shifted to avoid leaving 'gaps'. Two magnitudes cannot be labeled with
the same ModBus counter number.
Valid Range: starting address to (starting address + max no. of counters enabled
- 1)
Default value: first free number (not used, starting with the starting address for
the counters)
3.7-43
BCID1207A

listing the set of analog
signals labeled as
ModBus counters,
together with their
everything that is
menu option that is
clicking the mouse.
Signal Available Signal that is Modbus Counter

Modbus Nº Counter Number
3.7.4.e Analog Output Writings ModBus

Analog output writings transmitted through communications for MODBUS protocol are
configured in this screen.
Detail screen shows the following fields:
- Output Ana-logue Writings Starting Address: starting address for all analog output
writings. Analog magnitudes or actions tagged as MODBUS Analog Output Writings will
take consecutive values starting from this value.
- Command over Element: this option is selected to show to the right of the control both
analog command elements defined in the configuration and actions defined for each
element.
- Command over Analogue Sign: this option is selected to show to the right of the
controls the list of analog signal types as well as signals defined for each type.
- Command Element: this drop down control is only shown when selecting the 'Command
on element' option. A list with all analog command elements defined in the configuration
will be shown. For more information on command elements see section Commands. A
drop down list will be filled with the 'Available Commands' for the selected element and
the detail area controls will be updated.
- Available Commands: list of actions of the analog command element selected in
selected command.
3.7-44
BCID1207A
3.7 Communications
- Signal Type: drop down list containing groups of signals into which all analog signals
- Available Signals: list of equipment analog signals (magnitudes) belonging to the group
selected in 'types of Signal'. Signals that can be configured as analog output writings are
all those defined in the equipment plus those defined by the user pertaining to the
configuration, not being yet connected to a protection value or from the logic.
command element action is tagged as MODBUS Analog Output Writing (box
checkmarked) or not (empty checkbox). A maximum of 256 MODBUS analog output
writings are allowed. A new analog writing is created by checking the box and deleted by
unchecking.
- MODBUS Number: MODBUS tag associated to the analog output writing. Any time a
new MODBUS output writing is created, this value will be established by default to the
first free output value from the starting address, for analog output writings. It can be user
modified with the wanted value. In the case of MODBUS protocol, signal communications
tags must be consecutive. If the user modifies the MODBUS number and gives one
already allocated to other signal, the new value will be allocated the rest of the values
being offset so as not to leave 'gaps'. Two analog output writings may not be tagged with
the same analog MODBUS writing number.
Validity range: beginning direction + 0-255

Default value: first 'free' number (not used starting from 0)
empty checkbox).

- Maximum Limit: in principle it is the full scale of the analog output writing.
- Dependent on Rated Value: this selection checkbox states whether analog writing
calculation is made as a function of rated signal value (box checkmarked) or not (empty
checkbox). Different formulas will be shown depending on whether calculation data in the
lower part is checkmarked or not.
3.7-45
BCID1207A
Equations for the calculation of measurements transmitted through communications:

RatedValue limit
32767
MeasurementsComs  (Measure  offset) 
limit
Pressing on tab tagged as List displays the page that lists the set of signals tagged as
MODBUS analog output writing, together with the associated parameters. As already stated, all
that has been configured in the Detail screen can be configured in the List screen. Signals
tagged as Output Writings can be added or deleted by just pressing the right mouse button and
selecting the desired option, as stated when dealing with the List Page, or else, unchecking the
MODBUS box for each signal.
Signal Available signal that is Output Writing (Analog)

Modbus Output writing
ISS Nº ModBus Number
Offset Offset
Limit Upper limit
3.7-46
BCID1207A
3.7 Communications
3.7.5 61850 Protocol

This Communications menu option displays a new submenu with the configurations available
for this protocol. Selecting the desired option from the submenu (see next figure) displays
screens where CSWI, CILO, XCBR, XSWI, MCXL, RFTL, MMTR, LPHD nodes can be
configured.
Depending on the node version supported by the equipment profile, more or less attributes can
be configured. Version not configurable attributes will not be displayed on configuration screens.
Node data will be detailed in the following sections. The more complete node versions will be
shown.
Prior to detailing nodes, validity configuration and detail, generally applied to most of the
different attributes of nodes of protocol 61850, will be described.
3.7.5.a Validity Configuration

Protocol 61850 allows knowing the validity of the values of the different attributes constituting
the nodes, as well as the reason why the value of an attribute is not valid any more. The way to
configure this "validity" is common for all attributes. As with the validity, the reasons why an
attribute is not valid any more can be configured. In principle, IEC 61850 standard considers the
following non-validity reasons (61850-7-3; 6 Common data attribute types):
Overflow Failure
OutOfRange OldData
BadReference Inconsistent
Oscillatory Inaccurate
For details on the validity

associated to attributes
representing statuses
(related to digital
signals), configuration of
following details:
BadReference,
Oscillatory, Failure,
OldData and Inconsistent
will be possible.
3.7-47
BCID1207A
For details on the validity

associated to attributes
representing statuses
(related to digital
signals), configuration of
all details defined in the
standard will be possible.
Clicking on the validity checkbox or grid detail list checkboxes, displays a signal selection dialog
box defined in section Signal Selection. This dialog box contains both equipment signals and
signals created in the configuration.
3.7.5.b CSWI Node

As shown below, data for
equipment Switch
Controller structure and
associated CILO nodes
are configured in this
screen.
Fields shown on the

Detail screen are:
- Node Attributes
o CSWI
Number:
CSWI node
number
used as its
single
identification
within the system.
o Prefix: prefix used to form the single identifier of the system node.
o Description: node description.
- Status and CILO Control Data: they are configured in different tabs. CILO is not a
CSWI Node control element, but other protocol node, its data being related to CSWI
node control element, hence its configuration together with this node and not regardless
of it.
3.7-48
BCID1207A
3.7 Communications
- POS: CSWI control data:

Control tab:
o CtlVal and Description: command element and description. Logic command
element on which the command is executed.
o Command Failed Time and Description: setting stating the time delay after
which the command is considered failed, if the applicable command execution
confirmation has not been received.
o Action mask: masks for the execution permit of command element actions
selected as 'ctlval' as a function of the command source and of whether the
command is ON or OFF. Sources addressed in the standard are listed in the grid.
State tab:
o State to ON and OFF: statement of the command state to ON and OFF (value with
which to fill stval in the DPC structure). These data may be configured from the
statuses defined into the logic element associated to Ctlval or else directly from
digital signals.
o Validity. The
validity is
configured as
stated in section
Validity
Configuration.
- ACT: configuration of
CSWI state data.
Digital signals and descriptions representing the statuses below are configured in this
section:
o Close-to-open operation in progress.

o Open-to-close operation in progress.
o Successful close-to-open operation.
o Successful open-to-close operation.
o Failed close-to-open operation.
o Failed open-to-close operation.
To configure the ACT types shown in the previous screen, just select with the mouse
(click on it) the desired checkbox in the Signal column. Now the signal selection dialog
box defined in section Signal Selection. This dialog contains both equipment signals
and signals created in the configuration.
ACT description is directly configured writing on the applicable grid box.
Pressing the applicable grid button (tagged 'Validity') displays the ACT validity
configuration screen.
3.7-49
BCID1207A
- CILO: for
every CSWI
there can be
one node
containing
data on CSWI
locks and
permits. The
same as for
the rest of
protocol
61850 nodes,
its
identification number (CILO number), prefix and description must be configured.
Then, opening and closing permits are configured. Furthermore, up to 16 general
locks are allowed.
Locks can be configured, as for ACTs configuration, by just selecting with the mouse
the desired checkbox in 'Lockout' column. Then the following dialog boxes may be
displayed:
o If the selected checkbox corresponds to opening or closing permits, the dialog

box for signal selection defined in section Signal Selection will be displayed.
This dialog box contains both equipment signals and signals created in the
configuration.
o If the selected checkbox corresponds to one of the general locks, the dialog box
for logic element lockout selection will be displayed as shown in the following
screen.
The lockout list will be

filled with the set of
locks defined for the
logic element selected
in the first list.
Returning to the
general CSWI Node
screen, pressing the
tab tagged List
displays the page with
the list of CSWI node
set defined in the
relay together with
main node data. In
this case the List
page is only used for
information.
3.7-50
BCID1207A
3.7 Communications
3.7.5.c XCBR
Node
Data for the definition of
relay Circuit Breaker
physical structure can be
configured in this screen,
shown below.
The following data can

be configured:
- General Node
Data
o XCBR
Number:
XCBR
number
used as its single identification within the system node.
- Control data: the POS attribute of XCBR structure is a DPC (Double Point Controllable)
type attribute. It is configured in the following way:
o POS: CSWI control data:
Control tab:
 CtlVal and Description: command element and description. Logic command
element on which the command is executed. The element is selected from the
drop down list containing all logic elements defined in the configuration.
State tab:
 State to ON and OFF: statement of the command state to ON and OFF (value
with which to fill stval in the DPC structure). It can be represented from the
statuses defined in the logic element or else through the value of the configured
digital signal. The desired value is selected from the drop down list if it depends
on the statuses of the logic element; on the contrary, if it depends on the digital
signal, pressing the applicable checkbox displays a dialog box for signal
selection defined in section Signal Selection. This dialog box contains both
equipment signals and signals created in the configuration.
 Validity. The validity is configured as stated in section Validity Configuration.
- Attributes:
o Local operation.
o Operations counter (OpCnt): INS type attribute (Integer 32 status). Represents
the magnitude stored by the operations counter. All attributes have a structure field
for description.
o Open lockout.
o Close lockout.
o Operation capacity (OpCap): INS type attribute (Integer 32 status). Represents
the magnitude stored by the breaker operation capacity. All attributes have a
structure field for description.
For every attribute, pressing the applicable checkbox displays the signal selection dialog
box defined in Signal Selection. For attributes OpCnt and OpCab the signal selection dialog
box contains both equipment magnitudes and magnitudes created in the configuration. For
the rest of the attributes, the dialog contains all equipment and configuration digital signals.
3.7-51
BCID1207A
3.7.5.d XSWI Node

Node to model the status of equipment breakers.
Data configured in this screen are practically the same as those configured for XCBR node to
model the breaker status. The main difference lies in that in this case the status attributes that
can be configured are:
- Local Operation.
- Operations counter (OpCnt).
- Open lockout.
- Close lockout.
For more information refer to the previous section XCBR Node.
3.7.5.e MCXL
Node
Node to control analog
signal values. It is
configured in the screen
to the right.

be configured:
- General Node
Data
o MCXL
Number:
MCXL node
number
used as its
single identification within the system.
- SPS - Status Data
o StVal and description: states whether the signal has ever reached the maximum
allowable level and never dropped below the minimum. To define the value,
pressing on the applicable box displays the signal selection dialog defined in
section Signal Selection. This dialog contains both equipment digital signals and
o Validity. The validity is configured as stated in section Validity Configuration.
3.7-52
BCID1207A
3.7 Communications
- Settings: node settings configuration for status calculation:

o Operation Time Delay (OpDITmms): operation time delay setting. Minimum time
that the magnitude value must stay above or below the settings to activate or
deactivate the output signal.
o Change in Low Level (MinStrVal): minimum measurement limit. If the
measurement stays below this value for a given time, the node status signal resets.
o Change in High Level (MaxStrVa): maximum measurement limit. If the
measurement stays above this value for a given time, the node status signal
activates.
Clicking the setting

configuration box
displays the setting
selection dialog box
shown in the screen
below:
This dialog box shows

the settings defined in
the configuration
arranged as a function of
the their group.
3.7.5.f RFTL
Node
RFTL node is used for
modelling voltage reset
devices after line voltage
failure. Node modelling
data can be configured in
this screen.

be configured:
- General Node
Data
o RFTL
Number:
RFTL node
number used for single identification within the system.
- AUTO - Control Data: the AUTO attribute of RFTL structure is a SPC (Single Point
Controllable) type attribute stating if the device is connected or not. It is configured as
follows:
Control tab:
o CtlVal and Description: command element and description. Logic command
element on which the command is executed. The element is selected from the drop
down list containing all logic elements defined in the configuration.
3.7-53
BCID1207A
Status Tab:
o Status: states the element status (value with which stval is filled in the SPC
structure). It can be represented from the statuses defined in the logic element or
through the value of the configured digital signal. The desired value is selected
from the drop down list if it depends on the statuses of the logic element; on the
contrary, if it depends on the digital signal, pressing the applicable checkbox
displays a dialog box for signal selection defined in section Signal Selection. This
dialog box contains both equipment signals and signals created in the
configuration.
o Validity. The validity is configured as stated in section Validity Configuration.
Status Information: configuration of RFTL status data. In this "tab" screen are
configured the digital signals and descriptions representing the status of:
o Open command
o Close command
o Device status (ready, in progress, successful)
o Close lockout (activated or deactivated)
o Reset timer timed out (normal or alarm)
o Inconsistent voltage (normal or alarm)
o Busbar malfunction (normal or alarm)
o Line malfunction (normal or alarm)
For every
attribute (in the
Signal column),
pressing the
applicable
checkbox
displays the
signal selection
dialog box
defined in Signal
Selection. This
dialog box
contains both
equipment magnitudes and magnitudes created in the configuration, so that the digital
signal representing the attribute status can be selected. The description field can be
edited directly on the grid. Pressing the attribute 'validity' button displays the validity
screen described in section Validity Configuration.
- Settings: configuration of RFTL node settings. Settings list is:
o RS/RT Selector: selector to state whether the device resets voltage or service. If
service is reset, the breaker is closed when busbar voltage is detected. If voltage is
reset, the breaker is closed when line voltage is detected. It is an ING type data
that can take the values rs, rt, rs/rt or none.
o VL Selector: selector that determines the device operation as a function of busbar
and line voltage. When set to Yes the device operates on presence of voltage at
both terminals. When set to No the device operates on absence of voltage at one
terminal. This ING type data can take 3 values: yes, no and unknown.
o Trip on Absence of Voltage: if the setting takes the value Yes a trip must be
generated on absence of voltage at the busbar or line. If it takes the value No, no
trip is generated.
3.7-54
BCID1207A
3.7 Communications
o Time over (OverflTmms): states the maximum time in ms before operation of the
voltage reset device.
o Voltage Inconsistency Time: adjustable time setting after which it can be
considered there is voltage disagreement and the corresponding alarm can be
generated or the relay locks out. Voltages are construed to be inconsistent when
for a time greater than the inconsistency time, with the breaker closed, there is
absence of line voltage and presence of busbar voltage, or the opposite.
o Trip Condition Time: minimum time during which the trip conditions must be
maintained to generate the trip command.
o Reclose Condition Time: minimum time during which the reclose conditions must
be maintained to generate the reclose command.
o Voltage Absence Level: voltage level setting below which there is absence of
busbar or line voltage, provided it is below the setting at least for a minimum
adjustable time.
o Voltage Presence Level: voltage level setting above which there is presence of
busbar or line voltage, provided it is above the setting at least for a minimum
adjustable time.
Clicking the setting

configuration box
displays the setting
selection dialog dealt
with in the section above
for MCXL node.
3.7-55
BCID1207A
3.7.5.g MMTR
Node
Node used for energy
calculation in three
phase systems. It is
mainly used for
calculation of electricity
rates. Configurable data
are shown in the screen
below.

be configured:
- General Node
Data
o MMTR
Number: MMTR node number used as its single identification within the system.
o Description: Node description.
- Measured Values: BCR (Binary Counter Reading) type attributes.
o Positive Active Energy (SupWh).
o Capacitive Reactive Energy (SupVArh).
o Negative Active Energy (DmdWh).
o Inductive Reactive Energy (DmdVArh).
Pressing the applicable energy box displays the magnitude (or analog signal) selection dialog
defined in section Signal Selection. This dialog contains both equipment magnitudes and
magnitudes created in the configuration.
Every energy configuration setting is associated to the pulse value and corresponding validity.
3.7-56
BCID1207A
3.7 Communications
3.7.5.h LPHD
Node
Node showing Physical
Device Information.
For this node only the

equipment status can be
configured to know
whether it is in the grid or
not.
This value is selected in the same way as any other digital signal: pressing the applicable box
displays the signal selection dialog defined in section Signal Selection. This dialog contains both
equipment signals and signals created in the configuration. The status validity can also be
configured.
3.7.5.i ATCC
ATCC (Automatic Tap
Changer Controller)
structure data can be
configured in this screen
(see figure) for setpoint
management.
The Detail screen shows

the following fields:
- General Node
Data
o ATCC
Number:
ATCC node
number
used for single identification within the system.
- Analog Setpoint Command
o Setpoint Commands and Description: analog command element and
description. Analog command element on which the command is executed. It is
used to place the setpoint in a given value.
o Sources: connection between possible protocol 61850 sources and the actions of
the analog command element configured as command to raise and lower the
setpoint.
 Source: list containing possible sources contemplated for protocol 61850.
 Action: action of the analog command element to be executed upon receipt of
the command from the associated source. Possible actions will be the actions
pertaining to the analog command element configured as setpoint command.
3.7-57
BCID1207A
- Digital Setpoint
Command
o Setpoint
Status and
Description:
status to
reflect the
setpoint
value.
o Setpoint
Control
Command:
command on
which to act
to raise or
lower the
setpoint.
o Sources:
connection between possible protocol 61850 sources and the actions of the analog
command element configured as setpoint command.
 Actions: list of possible actions defined in the digital command used for
setpoint control.
 Action Source Masks: permissible sources and commands must be stated
for every action. For example, the figure shows that for ORC-SUCO action the
box ON is checkmarked in 'from substation' input, namely, if the equipment
receives a command to On from the substation, the ORC-SUCO action of
'Raise-Lower Setpoint' command must be executed.
- Tap control.
The Tap control is
configured in the
same way than
digital setpoint
commands.
o Tap status
and
Description:
status where
the tap value
is reflected.
o Tap control
command:
command to
raise or
lower the
tap.
o Sources:
connection between possible sources for protocol 61850 and the actions of the
digital command element configured as tap control command.
 Actions: list with possible actions defined in the digital command used for tap
control.
 Action Source Masks: permissible sources and commands must be stated
for every action. For example, the figure shows that for ORL-SUCO action the
box ON is checkmarked in 'local' input, namely, if the equipment receives a
local command to On, the ORL-SUCO action of 'Raise-Lower Tap' command
must be executed.
3.7-58
BCID1207A
3.7 Communications
3.7.5.j IHMI
Node used to describe
the 'Man-Machine'
interface. The figure
shows the data to be
configured d.
- General Node
Data
o IHMI
number:
IHMI node
- Node Detail:
o Status in Box: attribute stating whether the equipment is on or not.
Pressing the box corresponding to the grid status displays the signal selection dialog defined in
section Signal Selection. This dialog contains both equipment digital signals and signals created
in the configuration.
The validity is configured as stated in section Validity Configuration.
3.7.5.k CALH
This node is used for
alarm and event
management. The figure
shows the data to be
configured.
- General Node
Data
o CALH
number:
CALH node number used for single identification within the system.
- Node Detail: it has two attributes:
o Urgent Defect Alarm.
o Defect Alarm.
Pressing the box corresponding to the grid status displays the signal selection dialog box
defined in section Signal Selection. This dialog contains both equipment digital signals and
3.7-59
BCID1207A
3.7.5.l SIMG
Node used to supervise
the insulating gas (SF6).
The figure shows the
data to be configured.
- General Node
Data
o SIMG
Number:
SIMG node
o Prefix: prefix used to form the node single identification in the system.
- Node Detail: it has two SPS type attributes:
o Gas Alarms Level 1: critical gas level alarm
o Gas Alarms Level 2: hazardous gas level alarm.
Pressing the box corresponding to the grid status displays the signal selection dialog box
defined in section Signal Selection. This dialog contains both equipment digital signals and
3.7.5.m GENGGIO
General node used for
inputs and outputs. The
general GGIO or
GENGGIO reflects the
status of single inputs.
The following figures
show the data to be
configured.
- General Node
Data
o GENGGIO
number:
GENGGIO
node
number
used for
single identification within the system.
o Prefix: prefix used to form the single identifier of the system node. "GEN" by
default.
- Node Detail: a maximum of 32 alarms and up to a maximum of 32 comments can be
configured.
3.7-60
BCID1207A
3.7 Communications
Pressing the box corresponding to the grid status displays the

signal
selection dialog defined in section Signal Selection. This dialog
contains both equipment digital signals and signals created in the
configuration.
The validity is configured as stated in section Validity

Configuration.
Clicking the right button displays a pop up menu to select records,

display screens for text replacement and modifying the validity of
all or only selected records.
The screen to modify the

validity of several
attributes is the same
than the screen used to
modify only one attribute.
The only
difference being that
there is an additional
control stating the extent
of the change: "Active
record ", "Selected" or
"All".
3.7-61
BCID1207A
3.7.5.n TGOGGIO and TGO2GGIO

General node used for inputs and outputs. TOGGGIO and TGO2GGIO reflect analog
measurement inputs, general single commands and goose outputs. The figures show the data
to be configured.
- Node Attributes
o TGOGGIO Number:
TGOGGIO or
TGO2GGIO node
number used for single
identification within the
system.
o Prefix: prefix used to
form the single identifier
of the system node.
"TGO" for TGOGGIO
node and "TGO2" for
TGO2GGIO node.
o Description: node
description.
- Node Detail. Up to 32 single
commands and one goose
with a maximum of 32 outputs
can be configured.
Pressing the box

corresponding to the grid
status displays the signal
selection dialog defined in
section Signal Selection. This
dialog contains both
equipment digital signals and
signals created in the
configuration.
The same as for GenGGIO node, clicking the right button displays a pop up menu to
introduce modifications in several records simultaneously.
3.7-62
BCID1207A
3.7 Communications
3.7.5.o YLTC
Node used for the Tap
Changer status. The
figure shows the data to
be configured.
- General Node
Data
o YLTC
Number: nº
YLTC node
- Node Detail: it has the following attributes:
o Operations Counter.
o Tap Position Control.
o Top Tap Position Reached.
o Bottom Tap Position Reached.
Pressing the box corresponding to the grid status displays the signal selection dialog defined in
section Signal Selection. This dialog contains both equipment digital signals or magnitudes, as
a function of the attribute type, and signals created in the configuration.
3.7-63
BCID1207A
3.7-64
BCID1207A
3.8 HMI

3.8.1 Introduction .............................................................................................................. 3.8-2
3.8.2 Commands............................................................................................................... 3.8-2
3.8.3 Events ...................................................................................................................... 3.8-3
3.8.4 User Defined HMI Screens ...................................................................................... 3.8-4
3.8.5 HMI Cyclical Screens ............................................................................................... 3.8-5
3.8.5.a HMI Available Screens ....................................................................................... 3.8-6
3.8.1 Introduction
By selecting this menu option, you can access the screens for configuring the configuration data
to be displayed in the equipment's graphic HMI. The configurable data refer to Commands,
types of Events, HMI User Screens and HMI Lineal Screens.
3.8.2 Commands
select the commands
that can be displayed
and handled from the
equipment's HMI.
The available orders for

this purpose are those
actions that were
configured when defining
each of the command
elements. By default,
none of the orders of
these command
elements will be
displayed in the
equipment HMI.
- Command Element: drop-down list with all the command elements defined previously in
the configuration. For more information about the command elements, see section
Commands. When an element is selected, the lower list identified as Available orders is
updated with the data for the selected element.
- Available Orders: this drop-down list contains all the actions defined for the command
element selected in the previous list. The detail area parameters, in this case the
Appears in HMI checkbox, should be updated with the values established for the
selected order.
- Appears in HMI: this checkbox is marked for the selected order to be shown in the HMI
and for it to be operational from the HMI. A blank checkbox means the order will not be
shown in the HMI.
3.8-2
BCID1207A
3.8 HMI
The List section will

display a complete list of
the available command
elements in the
configuration and the
available orders for each
of these elements:
- Element:
Command element
to which the order
shown in the
adjacent column
belongs.
- Order: Action of
the command
element that can
be shown (or not)
in the HMI, and which can be executed (or not).
- HMI: Checkbox indicating whether the selected order is shown in the equipment HMI
(checkbox marked) or not (no marks in checkbox).
In this case, when the right button is pressed, the pop-up menu with the New and Delete
options will not be displayed, since orders not belonging to any of the command elements
already defined in the configuration cannot be enabled. The new actions created for a command
element or the increase in number of command elements with actions are also enabled in this
list.
3.8.3 Events
This screen lets you configure which
types of events will be displayed in the
equipment HMI. In this case the
signals you wish to display are not
detailed; rather, it lets you configure if
the signals that generate events for a
specific protocol will (or won't) be
displayed in the HMI.
The fields shown on the screen are as

follows:
- Show Procome Events: if this checkbox is marked (checkbox marked), when an event
labeled as such for the Procome protocol is generated, the short text representing the
signal that generated the event is shown in the HMI.
- Show DNP3 Events: if this checkbox is marked (checkbox marked), when an event
labeled as such for the DNP3 protocol is generated, the short text representing the signal
that generated the event is shown in the HMI.
3.8-3
BCID1207A
3.8.4 User Defined HMI Screens

This screen allows
programming of the User
Defined HMI Screens,
which are divided in two
types: screens displaying
digital signals, and
screens displaying
parameters.
As shown in the following

figure, the top line in the
screen displays the
option group with two
choices: Digital Signals
and Parameters. The
remaining controls of the
screen refer to the
selected type. It is not
possible to mix Digital
Signals and Parameters
in the same screen.
The fields shown in the top of the screen are:
- Screen Name: pull down menu including the screens of the selected type in the option
group labeled as Screen Type. The data (signals or parameters) shown on the grid will
depend on the option selected. It is possible to edit the list by changing the name of the
screen directly on the menu.
- New Screen: button to create a new screen of the selected type.
- Delete Screen: deletes the selected user defined screen from the list Screen Name.
- Organize Screens: opens the organizing window described in section Control Use.
The signals (or parameters) belonging to the user defined screen selected are displayed in the
lower portion of the screen. It is possible to modify the data included in the screen selecting the
signal or parameter with the mouse to open the corresponding signal selection window (see
section Signal Selection).
3.8-4
BCID1207A
3.8 HMI
The following options are available:
- New: includes a new signal or parameter depending on the screen type being configured.
- Delete: removes a signal or parameter from the screen.
- Modify: opens the corresponding signal selection window (see section Signal Selection).
If the selected screen is for Digital Signals the list of digital signals will be displayed
(protection and user defined). If the selected screen is for Parameters a list of
parameters without angles will be displayed. The second column (in the parameter type)
includes the corresponding angles to the signals in the left column. It is possible to select
these angles for modification.
- Organize: allows sorting the signals or parameters in the screen. Access to the Organize
Window (see section Control Use).
®
The data defined in these windows will be displayed in ZiverCid in the status menu.
3.8.5 HMI Cyclical Screens

HMI Cyclical Screens
that are displayed using
the F2 key on the IED
front panel.
There are two types of

cyclical screens, Default
and User defined. The
user defined screens are
programmed according
to section HMI user
screens. The list on the
top displays the defined
screens in the order that
are displayed on the
HMI.
The options available are:
- Modify: Access the window to create a new screen or remove exiting ones from the list.
- Organize: Allows sorting the signals or parameters in the screen. Access to the Organize
Window (see section Control Use). The selected sequence can be accessed using the F2
key in the IED front panel.
3.8-5
BCID1207A
3.8.5.a HMI Available Screens

This window displays the
complete listing of the
available screens
including default and
user defined screens.
The fields Title and Type

are for information
purposes. The Verify
HMI checkbox allows to
select or remove screens
from the HMI sequence.
3.8-6
BCID1207A
3.9 Graphical HMI

3.9.1 Introduction .............................................................................................................. 3.9-2
3.9.2 Graphic Screens to be Displayed ............................................................................ 3.9-2
3.9.2.a Screens available for the Graphical HMI ............................................................ 3.9-3
3.9.3 Graphical User Screens ........................................................................................... 3.9-3
3.9.3.a Single Line Diagram Data Configuration ............................................................ 3.9-3
3.9.3.b Single Line Diagram Design ............................................................................... 3.9-7
Design ................................................................................................................. 3.9-8
3.9.1 Introduction
As shown in the screen below, from this menu option the screens for the configuration of the
equipment Graphical HMI can be displayed. The data to be configured are data related to
Graphical Screens to be Displayed and Graphical user Screens.
3.9.2 Graphic Screens to be Displayed

From this screen graphical screens to be displayed in the equipment graphical HMI as well as
the display sequence can be configured.
There are two types of

screens: Static screens
and User screens. Static
screens are equipment
default screens, whereas
User screens are the
screens defined in the
configuration and
analysed in the following
section. The list shows in
sequential order the
screens
defined in the
configuration to be
displayed in the
equipment Graphical
HMI.
The following operations can be performed on these screens:
- Modify: Pressing this button displays the screen to create or delete screens on the
Graphical HMI list (see section below).
- Sort: Used to sort out the graphical screens to be displayed. Displays the sorting dialog
box dealt with in section Controls Use. The sequence established will be the sequence in
which equipment Graphical HMI screens are displayed when pressing the INF key.
3.9-2
BCID1207A
3.9 Graphical HMI
3.9.2.a Screens available for the Graphical HMI

Screen with the complete
list of available screens,
considering both Static
screens and User
screens defined in the
configuration.
Title and Type fields are

only for information.
Through the HMI
checkbox the user can
create or delete screens
to be displayed in the
Graphical HMI.
3.9.3 Graphical User Screens

The configuration of graphical user screens is performed in two stages. First, the screen design
must be defined (graphical part) and then, screen element data must be configured so as to
display the correct status when sent to the equipment. Pressing the option Graphical User
Screens, displays the screen to configure element data. Pressing the New Single Line
Diagram button or from Modify Single Diagram in this screen displays the Single Line diagram
design screen.
3.9.3.a Single Line Diagram Data Configuration

From this screen user screen data to be displayed in the graphical HMI of the equipment can be
configured: single line diagrams, alarm lists, measurement, date and time screens, etc.
At the top of the screen

the general data of the
Single Line diagram or
graphical display are
defined. To the left, at
the centre of the dialog
box, the drawing and text
as shown in the graphical
display of the equipment
after the configuration is
sent will be displayed.
The information defining
the object selected will
be displayed to the right.
3.9-3
BCID1207A
- General data of the graphical display (= Single Line diagram)

o Graphical Display Name: drop down list containing the graphical displays defined in
the configuration until now. This list can be edited, so that the screen name can be
directly modified on the control.
- Single Line diagram controls
o New Single Line diagram: with this button a new Single Line diagram (graphical
display) can be created and also display the Single Line diagram Design screen to
add the objects constituting the Single Line diagram.
o Modify Single Line diagram: with this button the Single Line diagram Design
screen can be displayed to modify the existing Single Line diagram, creating new
objects, deleting others, moving objects, adding statuses, etc.
o Delete Single Line diagram: deletes the graphical display selected in the list
Graphical Display Name of the User Screens.
o Import Single Line diagram: used to import a complete graphical display, both the
design and object configuration data from other configuration. This button displays
the screen to import Single Line diagrams, described in section Command
Configuration.
o Sort Single Line diagrams: Displays the sorting dialog box dealt with in section Use
of the Controls.
- Object definition: In this dialog area data of the object of the Single Line diagram
selected in the screen can be configured. The object selected is shown inside a green
frame. To select an object just press on it with the mouse. Objects without configuration
data will be shown inside a red frame.
Data to be configured depend on the type of the selected object. Apart from the base of the
Single Line diagram, objects can be segregated into 4 types, which have no configuration data:
- Command type object

- Status type object
- Magnitude type object
- Text type object
The following data can be defined for these types of objects:
- Attributes: state whether the object is visible, can blink and, in the case of commands,
whether it is selectable. The attribute activates by checking the applicable box
(checkmarked).
- Blink signal or setting: if the 'blink' attribute is activated, activating this signal states that
the object must blink. It will cease when the signal deactivates. If the object is of
magnitude type, instead of a signal, the blink setting will define the time to blink. Clicking
a setting configuration box displays a dialog box for setting selection.
This dialog box shows the analog settings defined in the configuration sorted out as a function
of the group they belong to.
3.9-4
BCID1207A
3.9 Graphical HMI
Specific data for the type of object are:

 Command Object
Command objects represent objects able to adopt a number of states varying from 1 to 16.
Furthermore they can be operated from graphical MMI provided object attributes are configured
as selectable, so that actions can be executed on it (for example, breaker opening or closing).
- Associated Logic Element: command element on which actions are executed and
from which the information defining its status at any time is obtained. The drop down list
shows all logic elements defined in the configuration.
- BMPs Associated to each Status: command type objects have the number of statuses
stated by the associated logic element. In grids the connection between object statuses
and the bmp shown in the graphical display must be established.
Grid Status-BMP shows the

connection mentioned above.
The status list can only be
modified changing the logic
element associated to the
command object; the BMPs is
a function of the bmps
selected when designing the
Single Line diagram (see
section Single Line diagram
Design).
To modify the Status-BMP connection, click the BMP associated to the status to be
modified. Then, the grid to the right identified as BMP is activated and the previous one
disabled, so that any of the bmps defined for the object can be selected, modifying the
connection mentioned and resetting the controls to the original enable / disable status.
- Actions associated to the buttons: The front of

a equipment with graphical display is provided
with 3 buttons to execute , and
actions, which are normally associated to open,
close and lock out actions respectively.
The actions list will correspond to the logic element associated to the object. The
connection between actions and buttons is performed in the same way as described for
the statuses. Apart from the 3 front buttons, in the list of available buttons the
application shows one more button: , which is identified as 'not allocated'. This
button does not correspond to any front physical button, but is used to be associated to
those actions that cannot be executed locally from the equipment front.
3.9-5
BCID1207A
 2 Status Type Object

The 2 status type object represents an object with two statuses depending on the value of the
signal to which it is associated (Deactivated= signal to 0; Activated = signal to 1). No action on
the object from the graphical HMI is possible, its status changes when the signal value changes.
- Associated Signal: it is configured as explained in section Signal Selection.

- BMPs Associated to each Status: A 2 status type object has 2 associated bmps. In
grids the connection between object statuses as a function of the associated signal
value and the bmp shown in the graphical display must be established.
The Status-BMP grid shows

the connection mentioned
above. The status list is
always fixed, the BMPs list is
a function of the bmps
selected when designing the
Single Line diagram (see
section Single Line diagram
Design).
To modify the connection Status-BMP, click on the BMP associated to the status to be
modified. Then, the grid to the right identified as BMP is activated and the previous one
disabled, so that any of the bmps defined for the object can be selected, modifying the
connection mentioned and resetting the controls to the original enable / disable status.
 Magnitude Type Object
- Associated Signal: it is configured as explained in section Signal Selection.
 Text Type Object
- Text: used to modify the object text. Maximum number of characters allowed is 16.
3.9-6
BCID1207A
3.9 Graphical HMI
3.9.3.b Single Line Diagram Design

This section describes
how to design a new
Single Line diagram or
modify an existing one. It
is identified as 'design'
because it is the place
where the Single Line
diagram graphical part is
defined, namely, object
drawings and texts as
well as their position in
the display.
Apart from the object

types defined in the
section above
(Command Type, 2
Status Type, Magnitude
Type and Text Type), the base type appears in the Single Line diagram design. The latter is
not shown in the above case as its data are not configurable. The base is always visible, it will
be the display background and will be represented by a single bmp not depending on any
status.
The meaning and operation of the screen controls are as follows:
- Name: editable text. When a new Single Line diagram is created the application gives it a
default name that can be modified at any time by the user from this control.
- New object: pressing this button creates the object type selected in the option selection
controls to the left of this control. If the type of object selected is magnitude or text type,
the object will be created in the position (0,0) of the Single Line diagram grid and with a
®
default text. If the type of data is status, command or base type the Windows Open
Image window is displayed to select an existing bmp. If a valid bmp is selected the object
will be created in the position (0,0) of the Single Line diagram grid. To modify the object
position in the grid and, thus, in the equipment display, just 'drag' the object with the
mouse to the new position or select the object modifying the numerical controls tagged x
and y, which represent the object coordinates as can be seen later on.
- Text: this control is enabled when selecting a text type or magnitude type object in the
Single Line diagram grid. Allows editing the text to be shown in the Single Line diagram.
Bear in mind that once the configuration has been sent out to the equipment the
magnitude object text edited will not be shown, but the associated magnitude value
together with the units instead.
3.9-7
BCID1207A
- Bmps for object statuses: set of bmps that can represent the object. All selected bmps
must be of one colour and have the same size, as they are representing the same object.
Different bmps will be shown as function of the object status at that time according to the
object configuration (subject dealt with in section Configuration of Single Line diagram
data). This control is only enabled for command type or 2 status type objects.
Command type objects must have at least one bmp to represent them, whereas it is
mandatory that 2 status type objects have two bmps, this being the reason why New and
Delete controls are disabled. One bmp can be modified by pressing it twice
consecutively. This displays the Windows® Open Image window for the user to select the
new bmp.
- Coordinates x,y: show the position of the object within the display taking the box top left
corner as origin of coordinates. These coordinates are the coordinates of the top left
corner of the selected object, not of the center. The object can be moved across the
screen by modifying the value of these controls.
- Import Single Line diagram: this button is enabled only when the screen is displayed
through the New Single Line diagram option. A graphic of a Single Line diagram created
in other configuration or a Single Line diagram saved using the old format (.cfg) can be
imported with this control. This function will be explained in more detail in the next
section.
Pressing the right mouse button on an object of the Single Line diagram grid displays a menu
with the following options:
- Delete object: selecting this option deletes the selected object. Before deleting the object
the program checks if it has been configured, in which case a warning will appear stating
that this action implies deleting the configured connections.
- Send to the background: sends the object to the background so that what is underneath
can be visualized. Bear in mind that objects are opaque.
Design
The application allows importing complete Single Line diagrams with object configuration data
or importing only the graphic design of the same. To Import complete Single Line diagrams
press the button Import Single Line diagram in the Single Line diagram Configuration
screen. To import Single Line diagram graphics press the button Single Line diagram Graphic
in the Single Line diagram Design screen. In both cases, follow the procedure below:
Pressing the above-mentioned button displays the Windows file selection dialog box for the user
to select the configuration from which to import the Single Line diagrams (it must be born in
mind that if Single Line diagram graphics are imported two types of files can be imported:
configuration files (.cfp) or Single Line diagrams with format files (.cfg). In the latter case, the file
contains the information of only one Single Line diagram design, so that this Single Line
diagram design will be directly imported).
3.9-8
BCID1207A
3.9 Graphical HMI
The screen shows a list

with the description of all
available graphical
displays in the selected
configuration. As it is a
multiple selection list, the
user can select all the
Single Line diagrams to
be created in the working
configuration. For a
multiple selection keep
pressed the "Ctrl" key
while the desired controls
are selected with the
mouse.
If Single Line diagrams are imported from the data configuration screen, configuration digital
signals, magnitudes or commands used to define Single Line diagram objects that do not
already exist in the configuration will be imported at the same time than Single Line diagrams
are imported. This type of information or any other information related to attributes, signals or
logic elements associated to the objects is not imported when importing Single Line diagram
design.
Any errors occurred

during the import process
will be displayed in the
error screen at the end of
the import process.

number of errors as well
as a brief description of
the same; this way the
user can know the
reasons why the Single
Line diagram could not
be imported or the
reason why the import
was not complete.
3.9-9
BCID1207A
3.9-10
BCID1207A
3.10 Profile Descriptions

3.10.1 Introduction ............................................................................................................ 3.10-2
3.10.1.a Digital Signals ................................................................................................... 3.10-2
3.10.1.b Analog Signals .................................................................................................. 3.10-2
3.10.1 Introduction
By selecting this menu option, you can access the screens for configuring the digital signal
descriptions and the magnitudes defined in the equipment's profile. These new descriptions will
be used to describe the signals both in the equipment (HMI short texts) and in ZiverCid® and in
ZIVerlog®.
3.10.1.a Digital Signals

configure the
descriptions used to
identify the digital
signals.

Detail screen are:
- Signal Type:
drop-down list
with the groups
of signals
containing all the
equipment's
digital signals,
without taking
into account
user-defined
signals, which are included in the configuration. For more information, see section
Signal Types. The list of available signals will depend on the selected group.
- Available Signals: list of digital equipment signals defined in the profile belonging to
the selected group in 'signal type'.
- Use Profile or User Descriptions: option group letting you indicate if the original profile
description or the user-defined description will be used.
- Description: text box showing the user description assigned to the digital signal for the
profile selected from the list. This box can be edited, i.e. the user can edit the
description.
The List section will show the complete list of digital signals whose descriptions have been
edited compared to the profile descriptions.
As with other list screens, the drop-down list can be accessed using the right button to select
from among the option to enable a new signal for editing or deleting an existing signal from the
list. The right column, user description, can be edited.
3.10.1.b Analog Signals

The configuration of the analog signal descriptions is the same as for digital signals, except that
only the profile's analog signals (magnitudes and angles) are shown. The screens and operating
method are identical. See section Digital Signals.
3.10-2
BCID1207A
3.11 Documentation

3.11.1 Introduction ............................................................................................................ 3.11-2
3.11.2 Reports .................................................................................................................. 3.11-2
3.11.3 Report Output Types.............................................................................................. 3.11-4
3.11.4 Report Parts ........................................................................................................... 3.11-5
3.11.1 Introduction
This menu option access to the screen where the documentation for the current ZIVerlog®
configuration is generated.
Selecting this menu option the

configuration is checked for changes
since the last time it was compiled. If
changes exist the user is notified and
given the option to compile aging the
configuration, since the compilation
checksums are included in the
documentation.
3.11.2 Reports
This menu option access
to the report
configuration tool.
There are different

reports available
depending on the user
profile.
Reports can be selected

in groups (left side
selection) or individually
(right side selection).
The available groups

with the reports included,
depend on the user
profile and are as
follows:
 LOGIC:
 General Logic
 Inputs Logic
 Outputs Logic
 LEDs Logic
 RESOURCES:
 Control Digital Signals
 Control Magnitudes
 Settings
 Commands
3.11-2
BCID1207A
3.11 Documentation
 HMI
 HMI Configuration
 Commands
 User Screens
 GRAPHIC HMI
 Graphic screens to display
 User graphic displays
 PROCOME
 Control Changes
 Meterings
 Counters
 Commands
 COTS
 Events
 Output Writings
 Analogic Output Writings
 DNP3
 Contacts
 Meterings
 Commands
 Counters
 MODBUS
 Inputs
 Outputs
 Meterings
 Commands
 Counters
 CAN
 Control Changes
 Commands
 Output Writings
 Changes Send Signals
 Changes Reception Signals
 61850
 CSWI
 XCBR
 XSWI
 GAPC
 MCXL
 RFTL
 MMTR
 LPHD
 CILO
 PROFILE DESCRIPTIONS
 Digital Signals
 Analogic Signals
3.11-3
BCID1207A
In the left bottom corner the user can fill in the fields for Substation, Bay and Date (the date
default is the current date). These fields are included in the reports.
In the right bottom corner included the button Generate Reports. The report will be sent to the
screen, printer or file depending on the Output Type selected.
Those reports without

data in the configuration
are not generated. At the
end of the process a list
of the selected reports
that have not been
generated is displayed.
3.11.3 Report
Output
Types
There are three different
options for the report
generation:
- Screen: displays
a report preview.
A toll bar allows
navigating
through the
different pages in
the report and
includes a
printing option.
- Printer: reports
are sent directly
to the printer.
3.11-4
BCID1207A
3.11 Documentation
- File: this option allows saving the reports a

".doc" extension file. Depending on the
amount and complexity of the data this
operation can last several minutes. The
user needs to confirm this operation on the
pop-up window.
The default file name includes the configuration name, the character "_" and the
configuration version.
3.11.4 Report Parts

The reports consists on three parts: header, details, and footer.
- Header:
o ZIV P+C logotype.
o Date.
o Report Page.
o Report Title.
o Report Configuration and Version.
o Configuration Checksum.
o Installation, Substation, System, Etc.
o Position.
o Configuration Model.
- Details:
o Configuration Dates.
- Footer:
o Notes.
o Copyright.
3.11-5
BCID1207A
3.11-6
BCID1207A

Bcid 1207 Av 01

Uploaded by

Copyright:

Available Formats

Bcid 1207 Av 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bcid 1207 Av 01

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What are the different types of reports that can be generated?

What are the different types of reports that can be generated?

ercid

IEC61850 Files Editing Program

© ZIV GRID AUTOMATION, S.L. 2012 BCID1207Av01

Terms and Conditions of License

ZIV Aplicaciones y Tecnología S.L.

Chapter 1. Description and Start

1.1 Introduction ................................................................................................ 1.1-1

1.2 Installation and Start ................................................................................. 1.2-1

Chapter 2. Application Development

2.1 Application Management .......................................................................... 2.1-1

2.2 DataSets...................................................................................................... 2.2-1

2.3 RDBs and GCBs ......................................................................................... 2.3-1

2.4 Gooses ........................................................................................................ 2.4-1

2.5 Communications ........................................................................................ 2.5-1

2.6 CIDs ............................................................................................................. 2.6-1

2.7 Display and Edit Data ................................................................................ 2.7-1

2.8 Edit Logic .................................................................................................... 2.8-1

Chapter 3. Managing Control Configurations

3.1 Introduction ................................................................................................ 3.1-1

3.2 Getting Started ........................................................................................... 3.2-1

3.3 File Menu .................................................................................................... 3.3-1

3.4 Input / Output Logic................................................................................... 3.4-1

3.5 Configuration-Associated Logic .............................................................. 3.5-1

3.6 Defining Resources ................................................................................... 3.6-1

3.7 Communications........................................................................................ 3.7-1

3.7.4 MODBUS Protocol ....................................................................................... 3.7-37

3.8 HMI............................................................................................................... 3.8-1

3.9 Graphical HMI ............................................................................................. 3.9-1

3.10 Profile Descriptions ................................................................................... 3.10-1

3.11 Documentation ........................................................................................... 3.11-1

1.1.1 Introducing to the ZIVerCid® File Editing Program

1.1.2.b DataSet Configuration

1.1.2.c RCBs and GCBs Configuration

1.1.2.d Configuration of Goose Message Reception

1.1.2.e Logic Configuration

1.1.2.f File Comparison

1.1.2.g Configuring Communications Data

1.1.2.h Other functions

1.2.1 Minimum Computer Requirements

1.2.2 Preparation for Installation

1.2.3 Program Installation

Installation is made by inserting the CD-ROM and execute filesetup.exe.

1.2.4 General Operation Mode

1.2.4.b Operating Method

1.2.4.c Information Screens

Another way of informing the user is by means of

In the status bar placed in the left low part of

2.1 Application Management

2.1.1 Edit Screen

 Node Name. Description to identify the file node.

 Copy: to copy the text shown.

2.1.2 Menu Options

- Open a CID, SCD or ICD file:

Every time changes are introduced

- Save CID, SCD or ICD file as a