1CPT

Substation
Central Unit

Instructions Manual for 1CPT Models

M1CPTA2005Iv01

REV. 01 - November, 2020 © ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. 2020

 Table of Contents

1. Description ........................................................................................................... 1-1

1.1 General .................................................................................................................. 1-2
1.2 Functions ............................................................................................................... 1-3
1.2.1 Communications .................................................................................................... 1-3
1.2.2 Synchronization ..................................................................................................... 1-3
1.2.3 Databases .............................................................................................................. 1-4
1.2.4 Commands ............................................................................................................ 1-4
1.2.5 Logic ...................................................................................................................... 1-4
1.2.6 Event Management................................................................................................ 1-5
1.2.7 Alarm Management ............................................................................................... 1-5
1.2.8 Control Functions................................................................................................... 1-5
1.2.9 Redundancy ........................................................................................................... 1-5
1.2.10 History Records ..................................................................................................... 1-6
1.2.11 Self-checking ......................................................................................................... 1-6
1.2.12 Human-Machine Interface ..................................................................................... 1-6
1.3 Model Selection ..................................................................................................... 1-7

2. Technical Data ..................................................................................................... 2-1

2.1 Power Supply Voltage ........................................................................................... 2-2
2.2 Hardware Data ....................................................................................................... 2-2
2.3 Status Contact Inputs ............................................................................................ 2-2
2.4 Status Contact Outputs.......................................................................................... 2-3
2.5 Communications Link ............................................................................................ 2-3

3. Standards and Type Tests .................................................................................. 3-1

3.1 Insulation................................................................................................................ 3-2
3.2 Electromagnetic Compatibility ............................................................................... 3-3
3.3 Environmental Test ................................................................................................ 3-4
3.4 Power Supply ......................................................................................................... 3-4
3.5 Mechanical Test..................................................................................................... 3-4

4. Physical Architecture .......................................................................................... 4-1

4.1 General .................................................................................................................. 4-2
4.2 Dimensions ............................................................................................................ 4-2
4.3 Connection Elements............................................................................................. 4-2
4.3.1 Terminal Blocks ..................................................................................................... 4-2
4.3.2 Connectors ............................................................................................................ 4-3
4.3.3 Removing of Printed Circuit Boards (Non Self-shorting) ....................................... 4-4
4.4 Human-Machine Interface ..................................................................................... 4-4

5. Settings ................................................................................................................. 5-1

6. Description of Operation..................................................................................... 6-3

6.1 Introduction ............................................................................................................ 6-4
6.2 Concept of the Equipment ..................................................................................... 6-5
6.3 General Functions ................................................................................................. 6-7
6.3.1 Synchronization ..................................................................................................... 6-7
6.3.2 Daylight Savings / Standard Time Change.......................................................... 6-10
6.3.3 Audible Warning .................................................................................................. 6-10
6.4 Communications .................................................................................................. 6-11
6.4.1 Physical Medium.................................................................................................. 6-11

M1CPTA2005I
I 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Table of Contents

6.4.2 Communication with Level 1 Equipment .............................................................. 6-12

6.4.2.a Interrogation Cycle ............................................................................................... 6-12
6.4.2.b Communications Parameters............................................................................... 6-14
6.4.3 Transparent Communication with Protection Equipment .................................... 6-15
6.4.4 Communication with Level 3 Systems ................................................................. 6-15
6.4.5 Routing Functions ................................................................................................ 6-16
6.5 Integration with Server Terminal model CIC ........................................................ 6-16
6.5.1 CIC Configuration ................................................................................................ 6-17
6.5.1.a Serial Interface Configuration .............................................................................. 6-18
6.5.1.b Network Interface Configuration .......................................................................... 6-20
6.5.1.c Connection Configuration .................................................................................... 6-21
6.5.2 1CPT Configuration ............................................................................................. 6-22
6.6 Level 1 Protocols ................................................................................................. 6-23
6.6.1 PROCOME........................................................................................................... 6-23
6.6.2 DNP3.................................................................................................................... 6-25
6.6.2.a Interrogation Cycle ............................................................................................... 6-25
6.6.2.b Communication Times ......................................................................................... 6-27
6.6.2.c Device Signals ..................................................................................................... 6-28
6.6.3 IEC103 ................................................................................................................. 6-29
6.6.4 SPABUS............................................................................................................... 6-30
6.6.5 MODBUS RTU ..................................................................................................... 6-31
6.6.6 IEC61850 ............................................................................................................. 6-31
6.6.6.a IEC61850 Client ................................................................................................... 6-32
6.6.6.b IEC61850 Server ................................................................................................. 6-32
6.7 Level 3 Protocols ................................................................................................. 6-33
6.8 Control Functions ................................................................................................. 6-34
6.8.1 Detection of Resistive Grounds ........................................................................... 6-34
6.8.1.a Contact Inputs ...................................................................................................... 6-35
6.8.1.b Contact Outputs ................................................................................................... 6-35
6.8.1.c Settings ................................................................................................................ 6-35
6.8.1.d Status Flow Chart ................................................................................................ 6-36
6.8.1.e Operation ............................................................................................................. 6-37
6.8.1.f Reset .................................................................................................................... 6-38
6.8.1.g Own Signals ......................................................................................................... 6-38
6.8.2 H Control Function ............................................................................................... 6-39
6.8.2.a Voltage Presence / Absence Control Functions .................................................. 6-40
6.8.2.b Control Function for the Definition of High Voltage Status .................................. 6-42
6.8.2.c Control Function for High Voltage Manoeuvres ................................................... 6-44
6.8.2.d Control Function for Medium Voltage Manoeuvres ............................................. 6-49
6.8.2.e Control Function for Switching due to Protection Tripping .................................. 6-52
6.8.2.f Own Digital Signals .............................................................................................. 6-54
6.8.2.g Own Commands .................................................................................................. 6-55
6.8.2.h External Signals ................................................................................................... 6-56
6.8.3 H2 Control Function ............................................................................................. 6-57
6.8.3.a Line Voltage Presence / Absence Control Functions .......................................... 6-58
6.8.3.b Control Function for the Definition of High Voltage Status .................................. 6-60
6.8.3.c Control Function for High Voltage Manoeuvres ................................................... 6-62
6.8.3.d Automatic Switching by Protection Trip ............................................................... 6-69
6.8.3.e Own Digital Signals .............................................................................................. 6-76
6.8.3.f Own Commands .................................................................................................. 6-77
6.8.3.g External Signals ................................................................................................... 6-77
6.8.4 Y Control Function (Specific case of H) ............................................................... 6-79
6.8.5 Automatic Service Reset Equipment (ERAS) ...................................................... 6-82
6.8.5.a UCERAS1 ............................................................................................................ 6-83
6.8.5.b UCERAS2 ............................................................................................................ 6-84
6.8.5.c UCERAS3 ............................................................................................................ 6-87
6.8.5.d TERAS1 ............................................................................................................... 6-88
6.8.5.e TERAS2 ............................................................................................................... 6-89

M1CPTA2005I
1CPT: Substation Central Unit II
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Table of Contents

6.8.5.f TERAS3 ............................................................................................................... 6-92

6.8.5.g TERAS4 ............................................................................................................... 6-93
6.8.5.h Own Signals ......................................................................................................... 6-94
6.8.5.i Own Commands .................................................................................................. 6-96
6.8.5.j External Signals ................................................................................................... 6-96
6.9 UCS as Virtual Equipment ................................................................................... 6-97
6.9.1 Virtual Central Equipment ISC-s (Digital Signals) ............................................... 6-97
6.9.2 Virtual Central Equipment ISE-s (Commands) .................................................... 6-99
6.9.3 Virtual Central Equipment ISS-s (Output Writes) .............................................. 6-100
6.10 Programmable Logic.......................................................................................... 6-100
6.11 Remote Console ................................................................................................ 6-106
6.12 Commands ........................................................................................................ 6-107
6.12.1 Group Commands ............................................................................................. 6-108
6.12.2 Master Commands ............................................................................................ 6-108
6.12.3 Commands sent to IEC 61850 Devices............................................................. 6-109
6.13 LEDs .................................................................................................................. 6-109
6.14 Digital Inputs ...................................................................................................... 6-109
6.15 Digital Outputs ................................................................................................... 6-109
6.16 Logs (optional) ................................................................................................... 6-110
6.16.1 Logs Collecting .................................................................................................. 6-110
6.16.1.a Metering Logs .................................................................................................... 6-110
6.16.1.b Counter Logs ..................................................................................................... 6-110
6.16.1.c Change Logs ..................................................................................................... 6-110
6.16.2 Reports and Trends ........................................................................................... 6-111
6.16.2.a Connection to the 1CPT Relay .......................................................................... 6-112
6.16.2.b Graphic Type Report Generation ...................................................................... 6-113
6.16.2.c Chart Type Report Generation .......................................................................... 6-119
6.16.2.d Deleting the Database ....................................................................................... 6-122
6.16.2.e Database Disconnection .................................................................................... 6-122
6.16.2.f Installation Instructions ...................................................................................... 6-123
6.17 Redundancy ....................................................................................................... 6-124
6.17.1 Introduction ........................................................................................................ 6-124
6.17.2 Communications Topologies ............................................................................. 6-124
6.17.3 Redundancy Functions ...................................................................................... 6-128
6.17.3.a Central Units ...................................................................................................... 6-128
6.17.3.b Automatic Switch over Mechanism.................................................................... 6-130
6.17.3.c Manual Switching Mechanism ........................................................................... 6-137
6.17.3.d Bay Device Communications ............................................................................. 6-138
6.17.3.e Remote Control Communications ...................................................................... 6-139
6.17.3.f Operation HMIs .................................................................................................. 6-139
6.17.4 Configuration Parameters .................................................................................. 6-140
6.17.4.a Redundancy Types ............................................................................................ 6-140
6.17.4.b Configuration Parameters .................................................................................. 6-142
6.18 Substation Configuration Server: UCSConf ...................................................... 6-143
6.19 Maintenance Options ......................................................................................... 6-144

7. Alphanumeric Keypad and Display ................................................................... 7-1

7.1 Alphanumeric Display and Keypad ........................................................................ 7-2
7.2 Keys, Functions and Operation Mode ................................................................... 7-3
7.3 Function Access Using the Keypad ....................................................................... 7-6

8. Receiving Tests ................................................................................................... 8-1

8.1 General .................................................................................................................. 8-2
8.2 Preliminary Inspection ........................................................................................... 8-2
8.3 In Service Test ....................................................................................................... 8-2
8.4 Start Up .................................................................................................................. 8-3
8.5 Port Test ................................................................................................................ 8-4
8.6 LEDs Status ........................................................................................................... 8-5

M1CPTA2005I
III 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Table of Contents

8.7 Installation .............................................................................................................. 8-5

A. Configuration Files for CPX / CPP / CPT .......................................................... A-1

A.1 Introduction ........................................................................................................... A-2
A.2 Configuration File for CENTRAL Task: CENTRAL.CFG ...................................... A-7
A.3 Physical Device File: DBASE.CFG ..................................................................... A-14
A.4 History Files: HISTORIC.CFG ............................................................................ A-18
A.4.1 Measurements History Record ........................................................................... A-18
A.4.2 Meters History Record ........................................................................................ A-19
A.4.3 Changes History Record (Signals)...................................................................... A-19
A.5 Configuration Files of the LOGIC Task ............................................................... A-21
A.5.1 LOGIC Task Signals File: LOGICA.CFG ............................................................ A-21
A.5.2 LOGIC Task Programming File: LOGICA.COD .................................................. A-24
A.6 Configuration File of COMMAND Task: MANDO.CFG ....................................... A-32
A.7 Communications Configuration Files: PUERTOS.CFG ...................................... A-35
A.8 LED Configuration File: LEDS.CFG .................................................................... A-38
A.9 Configuration File for Establishing a Connection Via Modem with the
HMI: RASSRV.CFG (Only for CPX-A) ................................................................ A-40
A.10 Central Unit Redundancy Files: REDUNDA.CFG............................................... A-44
A.11 Remote HMI File: REMOTA.CFG ....................................................................... A-47
A.12 Network Configuration Files ................................................................................ A-49
A.12.1 Operating System Network Configuration File: AUTORUN.CFG ....................... A-49
A.12.2 Central Unit Application Network Configuration File: TCP.CFG ......................... A-50
A.13 Control Function Configuration Files .................................................................. A-52
A.13.1 H Control Function File: AUTOH.CFG ................................................................ A-52
A.13.2 H2 Control Function File: AUTOH2.CFG ............................................................ A-62
A.13.3 Resistive Ground Control Function Files: TIERR_i.CFG .................................... A-74
A.13.4 Eras Control Function File: ERAS.CFG .............................................................. A-79
A.13.4.a Eras Control Function Virtual Terminal File: TVIRTUAL.CFG ............................ A-81
A.14 Summer / Winter Time Configuration File: HORARIO.CFG. .............................. A-85
A.15 Remote Access Server (RAS) Configuration File: RMONITOR.CFG
(Only CPX/CPP-B/CPT)...................................................................................... A-87
A.16 Routing Table Configuration File: ROUTE.CFG (only CPX-B / CPT)................. A-88
A.17 Configuration File of Client/Server Synchronisation Module SNTP:
SNTP.CFG (only 1CPT)...................................................................................... A-90
A.18 File to Configure the Communications with Terminal Servers:
TScoms.CFG ...................................................................................................... A-94

B. Configuration of Protocol Emulators ................................................................ B-1

B.1 Introduction ........................................................................................................... B-2
B.2 CEI 870-5-101 Family Protocols ........................................................................... B-3
B.2.1 Non-Balanced Type III: CEI101C.CFG ................................................................. B-3
B.2.2 Unbalanced Type IV: CEI101A.CFG .................................................................. B-12
B.2.3 Balanced / Unbalanced /104: CEI101B.CFG...................................................... B-18
B.2.4 Unbalanced Type VIII: CEI101I.CFG .................................................................. B-41
B.2.5 Gateway 104-101: GW104101.CFG ................................................................... B-60
B.2.6 IEC60870-5-101 Balanced / IEC60870-5-104: C101104I.CFG.......................... B-64
B.2.7 IEC101 Master Emulator Balanced/Unbalanced: M101B.CFG .......................... B-85
B.3 DNP3 Protocol: DNP3.CFG ................................................................................ B-93
B.4 DNP3 Protocol in Master Mode: DNP3MS.CFG............................................... B-107
B.5 Slave MODBUS Protocol: MODBUS.CFG ....................................................... B-113
B.6 Master MODBUS Protocol: MODBUSMS.CFG ................................................ B-124
B.7 PID1 Protocol: PID1.CFG ................................................................................. B-151
B.8 SEVCO 6802 Protocol: SEVCO.CFG ............................................................... B-161
B.9 Protocolo Wisp+.: WISP.CFG ........................................................................... B-167
B.10 Communications with SIEMENS SIMATIC PLCs ............................................. B-172
B.10.1 SINEC H1 Protocol: COMSINEC.CFG (only CPD) .......................................... B-172

M1CPTA2005I
1CPT: Substation Central Unit IV
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Table of Contents

B.10.2 RK512/3964R Protocol: COM3964R.CFG ........................................................ B-174

B.10.3 Configuration file for COMPLC Task: COMPLC.CFG ....................................... B-176
B.10.4 Configuration File for COMSCD Task: COMSCD.CFG (only CPD) .................. B-184
B.10.5 MODBUS PLC Protocol: MODBMSPLC.CFG ................................................... B-187
B.11 GESTEL Protocol: GESTEL.CFG ..................................................................... B-189
B.12 SPABUS Master Protocol: SPABUSMS.CFG and MODULSPA.CFG .............. B-196
B.12.1 Device Emulation File: SPABUSMS.CFG ......................................................... B-196
B.12.2 Device Description File: MODULSPA.CFG ....................................................... B-201
B.13 PROCOSLV Protocol: PROCOSLV.CFG .......................................................... B-220
B.14 SEVCO Master Protocol: SEVCOMS.CFG ....................................................... B-226
B.15 Communications with CGC. COMSCGC.CFG .................................................. B-228
B.16 Wisp+ Master Protocol: WISPMS.CFG ............................................................. B-230
B.17 IEC-61850 Module (1CPT Models) ................................................................... B-235
B.17.1 Configuration of IEC-61850 Client: 61850CLI.CFG .......................................... B-235
B.17.2 Configuration of 61850 IEDs in the CPT ........................................................... B-239
B.17.3 Configuration of Central Unit IEC-61850 Server ............................................... B-266
B.17.3.a GOOSEs Configuration File: IECGOOSE.INI.................................................... B-267
B.17.3.b IEC-61850 Server Configuration File: 61850SRV.CFG .................................... B-270
B.17.4 Configuration File of IEC-61850 Communications: RFC1006.CFG [Lines
1-9] ..................................................................................................................... B-276
B.18 IEC103 Protocol: IEC103MS.CFG .................................................................... B-278
B.19 SNMP Client Module: SRVSNMP.CFG and SNMPCLI.CFG Files (1CPT
Models) .............................................................................................................. B-283
B.19.1 SRVSNMP Module: SRVSNMP.CFG File ......................................................... B-283
B.19.2 SNMPCLI Module: SNMPCLI.CFG File ............................................................ B-285
B.20 Configuration of Substation configuration Server: File UCSCONEC.INI
(1CPT Models) ................................................................................................... B-290

C. Schemes and Drawings ..................................................................................... C-1

D. List of Illustrations and Tables .......................................................................... D-1

D.1 List of Figures ....................................................................................................... D-2
D.2 List of Tables ........................................................................................................ D-4

M1CPTA2005I
V 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Table of Contents

M1CPTA2005I
1CPT: Substation Central Unit VI
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 1. Description

1.1 General................................................................................................................ 1-2

1.2 Functions ............................................................................................................. 1-3
1.2.1 Communications ................................................................................................. 1-3
1.2.2 Synchronization ................................................................................................... 1-3
1.2.3 Databases ........................................................................................................... 1-4
1.2.4 Commands .......................................................................................................... 1-4
1.2.5 Logic .................................................................................................................... 1-4
1.2.6 Event Management ............................................................................................. 1-5
1.2.7 Alarm Management ............................................................................................. 1-5
1.2.8 Control Functions ................................................................................................ 1-5
1.2.9 Redundancy ........................................................................................................ 1-5
1.2.10 History Records ................................................................................................... 1-6
1.2.11 Self-checking ....................................................................................................... 1-6
1.2.12 Human-Machine Interface ................................................................................... 1-6
1.3 Model Selection ................................................................................................... 1-7
 Chapter 1. Description

1CPT relays, together with Level 1 protection and control devices, are part of the Integrated
Substation Protection and Control System (SIPCO), operating both as Substation Central Unit
(UCS) with Integrated WEB Console and remote control terminal (RTU).

Among the general functions of the 1CPT are the following: communication with Level 1
equipment, integration of all substation control information in a common real-time database,
communication with equipment of the same or higher level with protocol emulation, execution
of programmable control functions at the substation level and ability to execute manoeuvres
with interlocking management at the substation level.

1.1 General
The 1CPT is designed to solve all communication and data processing needs with a
substation’s protection, control and metering equipment, providing new functions that make
most of the information available to these units. The 1CPT is responsible for communications
with level 1 equipment and for real-time database maintenance, incorporation of automatic
devices and logic at substation level being possible.

1CPT relays are also provided with a web server to access the Integrated Web Console (built
into the 1CPT itself) that can at the same time be accessed via web client from any substation
computer, serving the purpose of interface between user and system.

On the other hand, 1CPT relays can be used to establish communications with the remote
control office or SCADA.

The entire system can be configured through Zivergraph© software. This program enables the
system to be configured to adapt to the substation’s characteristics: equipment connected,
signals associated with each unit, representation of the information on displays, logic functions
at the substation level, desired functionality, etc.

M1CPTA2005I
1CPT: Substation Central Unit 1-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 1. Description

1.2 Functions
1.2.1 Communications
Communication between 1CPT relays and substation protection and control equipment is made
via standard IEC-61850 communications protocol through a network interface Ethernet 100-
BaseT.

However, communications between 1CPT relays and level 1 equipment can be established via
serial connections (fibre optic – plastic or glass- or RS-232) using conventional protocols such
as PROCOME, DNP3.0, MODBUS, IEC103, SPABUS.

It also communicates with the control station, emulating the necessary protocol in each case, to
inform the same of the events occurring at the substation and enable it to manoeuvre on its
active elements.

The technical office also communicates with the 1CPT through a modem connected to the
remote port. By using the manufacturer's program, protection data can be transparently
accessed, so that queries can be made regarding the status of the protections, etc. This
connection is also possible from the local port. This functionality is included in all 1CPT models
for equipment using the PROCOME protocol. For equipment with other protocols, it will depend
on the model.

As stated above, the Operations Console associated to the Substation Central Unit is built into
the 1CPT itself, so that the user only needs a computer with MS Windows for connection with
the web page of the 1CPT integrated console. Access to the Central Unit is via the 1CPT
Ethernet 100-BaseT interface, so that a high speed connection (above 1 Mbit/s) is needed,
which will be 100 Mbit/s within the system local area network, and several Mbit/s if access is
external via WAN from the company engineering department.

Finally, the 1CPT has an interface to obtain the standard GPS clock signal, with the ability to, on
the one hand, receive the signal delivered directly through a GPS antenna, and on the other
hand, also offer a connection to a GPS receiving device.

1.2.2 Synchronization
The 1CPT is responsible for keeping the entire system synchronized with a single clock source.
This source may be external or internal. If external synchronization is not possible, the 1CPT
uses the internal real-time clock (RTC) as a standard to synchronize the clocks of the different
equipment connected to it.

Several non-exclusive synchronization methods can be used as a source of external

synchronization. Using the particular communications protocol, the 1CPT is synchronized
periodically from the control office via the control program.

If a GPS clock is used, the 1CPT has several communications interfaces with this clock. Thus,
the 1CPT relay can be synchronized with a GPS clock using analog IRIG-B interface, serial
interface, or Ethernet interface with SNTP (Simple Network Time Protocol) synchronization
protocol. Said interfaces will be explained later.

M1CPTA2005I
1-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 1. Description

1.2.3 Databases
The 1CPT collects data from the substation’s IED, control and metering units and maintains a
database with this data, updated in real time (the update cycle will depend on the number of
units connected, on the communication parameters and on the protocol used). This database
supports the information of the operations console built into the 1CPT itself and all other
applications that communicate with the central unit, such as remote controls, internal tasks, etc.

The 1CPT database is stored in an internal format and is volatile, i.e., it is a copy of the level 1
equipment data. No log of this information is kept.
The 1CPT not only emulates higher-level communications protocols; it also maintains a
database in the particular format of the protocol emulated, so that it makes the higher-level
equipment think that it is communicating with a unit from the original manufacturer.

1.2.4 Commands
The 1CPT allows commands to be executed on the installation's configurable elements. The
command may originate internally (control functions, logic) or externally (Web client connected
to the 1CPT operations console, remote control). The 1CPT modifies the format of commands
between the different protocols so that the command reaches the equipment that must execute
it, regardless of the manufacturer of the equipment. Likewise, it closes the communication loop,
if the communications protocol supports this, by sending the unit’s response to an order to the
equipment from which the order originated.

There is a blocking logic that prevents performing dangerous or forbidden manoeuvres in

certain situations.

1.2.5 Logic
The 1CPT has an internal task responsible for executing a fully programmable logic program by
means of certain functions: logic gates (AND, OR, NOT, etc.), flip-flop (RS, JK), commands, etc.
This logic program may be used to implement control functions at the substation level, group
signals to send to the control office, etc.

M1CPTA2005I
1CPT: Substation Central Unit 1-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 1. Description

1.2.6 Event Management

The 1CPT captures level 1 device data following the guidelines of the communications protocol
used, but in all cases the first step is to request the status of all available signals,
measurements and counters. Then, for most of conventional protocols, said signal,
measurement and counter changes are requested in a cyclical manner. Standard IEC-61850
provides services for level 1 devices to spontaneously send to the 1CPT all signal,
measurement and counter changes. After reception by the 1CPT, said changes are sent to the
internal Central Unit tasks that have previously requested the same to its database.

However, not all signal changes occurring at the substation will be useful to the user; in other
words, not all will be defined as events. Events associated to the signal changes received are
filtered by the 1CPT, so that the integrated Web Console will only show the events the user
considers of use for the system.

Similarly, each database client task will receive all signal changes collected from the equipment,
and it will be its job to filter them, keeping those that are to its interest and discharging those
that are not.

1.2.7 Alarm Management

The same as with the events, not all signal changes are alarms. The 1CPT is responsible for
managing the alarms occurring at the substation filtering at 1CPT integrated web console level,
which level 1 device changes received are alarms and which not.

Control room alarm management is user’s responsibility. The only thing the 1CPT does is filter
the changes and send along only those that are of interest.

1.2.8 Control Functions

The 1CPT can execute certain control functions at the substation level, in which signals from
different equipment take part. These control functions can be of two types: fixed or
programmable. The former category includes those whose functionality is fixed and cannot be
altered; they may only be configured and set. The latter includes those that are programmed
within control logic.

1.2.9 Redundancy
In some relevant systems a redundant system must be installed. 1CPT redundancy can be of
two types: Hot-Stand-By (HSB) and Complete. In both cases, the Primary 1CPT carries out
1CPT typical functions, monitoring at the same time certain critical variables. The Secondary
1CPT stands by until a failure is detected to take over the control of the substation. The
difference rests on the fact that with Complete redundancy, both 1CPT databases are updated
all the time, whereas with HSB redundancy, the Secondary 1CPT is NOT.

M1CPTA2005I
1-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 1. Description

1.2.10 History Records

Another optional functionality of the 1CPT is to log changes in signals, measurements and
meters. These are daily history records of data to be stored into the 1CPT flash disk. These
records will be retrieved from the 1CPT integrated Console web page, which will process them
later.

1.2.11 Self-checking
The central unit periodically checks the integrity of the hardware and the software stored on its
permanent memory devices. It also has a system that picks up any error that occurs when the
unit’s hardware is accessed, so that the system can continue operating in an emergency mode
if necessary, until the problem can be solved.

1.2.12 Human-Machine Interface

There is an operator interface that allows to obtain information regarding the equipment’s
functionality, as well as information that will enable the supervision of the central unit’s
performance and operability at all times. This interface has an LCD display, a keypad with basic
functions and a series of configurable LEDs which show the status of certain system control
signals.

M1CPTA2005I
1CPT: Substation Central Unit 1-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 1. Description

1.3 Model Selection

1CPT 5 0 20 A
1 2 3 4 5 6 7 8 9 10 11

1 Functions
A UCS + WEB Console C RTU + WEB Console (default option)
B RTU
2 Communications Ports
Ethernet (LAN 1 and 2) Local Port Serial Port P3-P4 Serial Port P1-P2
2 100TX – 2 x RJ45 USB 2 x FOP 2 x RS232
2 100TX – 2 x RJ45 USB 2 x FOC ST 2 x RS232
3 Optional Hardware Module
B (Keypad, Display and LEDs) + IRIG-B V123
4 Auxiliary Voltage
Power Supply Digital Inputs
2 110/125 VDC (±20%) 110 VDC
3 220/250 VDC (±20%) 250 VDC
7 Compact-Flash
0 256 Mbytes Compact-Flash
9 Enclousure Type
F 2 U x 1 19" rack
11 Finishing
- Stainless Steel + Printed Circuit Board NO Tropicalized
L Stainless Steel + Tropicalized Printed Circuit Board

M1CPTA2005I
1-7 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 1. Description

M1CPTA2005I
1CPT: Substation Central Unit 1-8
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 2. Technical Data

2.1 Power Supply Voltage ......................................................................................... 2-2

2.2 Hardware Data .................................................................................................... 2-2
2.3 Status Contact Inputs .......................................................................................... 2-2
2.4 Status Contact Outputs ....................................................................................... 2-3
2.5 Communications Link .......................................................................................... 2-3
 Chapter 2. Technical Data

2.1 Power Supply Voltage

Terminals are provided with an auxiliary power supply the value of which is:

110/125 VDC (±20%)

220 / 250 VDC (+-20%)

Note: in case of an auxiliary power supply voltage failure, terminal units can tolerate a maximum interruption
of 100ms at 110Vdc.

2.2 Hardware Data

CPU board with microprocessor at 533MHz with industrial temperature range (includes two chips for
Ethernet Network with 100Base-T connection, Compact-Flash and master USB controller).

128 Mb of RAM.
Internal Flash Memory of 16 Mb.
Removable Compact-Flash disk of 256 Mb (expandable).
2 Ethernet Ports Type 100Base-T.
Coaxial Connector for IRIG-B123 Signal.
8 Digital Status Contact Inputs and 8 Digital Status Contact Outputs.
USB Master Port.
Front panel with HMI (Keyboard and Display) and LEDs (optional).

2.3 Status Contact Inputs

8 digital status contact inputs with polarity.

Rated Voltage Burden V ON

125 VDC 800 mW 75 VDC
250 VDC 1W 150 VDC

M1CPTA2005I
1CPT: Substation Central Unit 2-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 2. Technical Data

2.4 Status Contact Outputs

Double Contact Outputs.

I DC Maximum Limit (with resistive load) 30 A in 1 s

I DC Continuous Service (with resistive load) 8A
Close 2500 W
Breaking Capability (with resistive load) 150 W - max. 8 A - (48 VDC)
55 W (80 VDC - 250 VDC)
1250 VA
Break (L/R = 0.04 s) 60 W at 125 VDC
Switching Voltage 250 VDC

2.5 Communications Link

Glass Fiber Optics

Type Multimode
Wavelength 820 nm
Connector ST
Transmitter Minimum Power
50/125 Fiber - 20 dBm
62.5/125 Fiber - 17 dBm
100/140 Fiber - 7 dBm
Receiver Sensitivity - 25.4 dBm

Plastic Fiber Optics (1 mm)

Wavelength 660 nm
Transmitter Minimum Power - 16 dBm
Receiver Sensitivity - 39 dBm

RS232-Full Modem Transmission

DB-9 connector (9 pins), signals used Pin 1 - DCD
(P1 and P2) Pin 2 - RXD
Pin 3 - TXD
Pin 4 - DTR
Pin 5 - GND
Pin 6 - DSR
Pin 7 - RTS
Pin 8 - CTS
Pin 9 - RI

M1CPTA2005I
2-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 2. Technical Data

RJ45 Transmission
Signals used Pin 1 - TX+
Pin 2 - TX-
Pin 3 - RX+
Pin 4 - N/C
Pin 5 - N/C
Pin 6 - RX-
Pin 7 - N/C
Pin 8 - N/C

Coaxial Connector for Synchronizer Clock with IRIGB-123 Interface

B: 100pps
1: Amplitude Modulated Wave
2: 1kHz/1ms
3: BCD, SBS
Internal Connection - Signal
External Connection - GND

M1CPTA2005I
1CPT: Substation Central Unit 2-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 3. Standards and Type Tests

3.1 Insulation ............................................................................................................. 3-2

3.2 Electromagnetic Compatibility ............................................................................. 3-3
3.3 Environmental Test ............................................................................................. 3-4
3.4 Power Supply ...................................................................................................... 3-4
3.5 Mechanical Test .................................................................................................. 3-4
 Chapter 3. Standards and Type Tests

The equipment satisfies the requirements of IEC-255 (EN 21-136) at the maximum class for the
values indicated below.

3.1 Insulation

Insulation Test (Dielectric Strength) IEC-60255-5

Between all circuit terminals and ground 2 kV, 50/60 Hz, for 1min; or
(PS, DI’s, DO’s) 2.5 kV, 50/60 Hz, for 1s

Between all circuit terminals (PS, DI’s, DO’s) 2 kV, 50/60 Hz, for 1min; or
2.5 kV, 50/60 Hz, for 1s

Between comm. ports and ground 0.5 kV, 50/60 Hz, for 1min; or
1 kV, 50/60 Hz, for 1s

Insulation Resistance Measurement IEC-60255-5

Common mode R ≥ 100 MΩ or 5µA
Differential mode R ≥ 100 kΩ or 5mA

Voltage Impulse Test IEC-60255-5 (UNE 21-136-83/ 5)

Common mode
DI’s, DO’s and Power Supply 5 kV; 1.2/50 µs; 0.5 J
Comm.ports 0.5 kV; 1,2/50 µs; 0,5 J
Differential mode
DI’s 5 kV; 1,2/50 µs
DO’s 1 kV; 1.2/50 µs
PS 3 kV; 1,2/50 µs

M1CPTA2005I
1CPT: Substation Central Unit 3-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 3. Standards and Type Tests

3.2 Electromagnetic Compatibility

1 MHz Burst Test IEC-60255-22-1 Class III

(UNE 21-136-92/22-1)
Common mode 2.5kV
Differential mode 2.5kV

Fast Transient Disturbance Test IEC-60255-22-4 Class IV

(UNE 21-136-92/22-4)
(IEC 61000-4-4)
PS, DI’s and DO’s 4 kV (5kHz)
Comm. ports 2 kV (5kHz)

Radiated Electromagnetic Field Disturbance IEC 61000-4-3 Class III

Amplitude modulated (EN 50140)10 V/m
Pulse modulated (EN 50204)10 V/m

Conducted Electromagnetic Field Disturbance IEC 61000-4-6 Class III (EN 50141)
Amplitude modulated 10 V

Surge Immunity IEC 61000-4-5 Class III

(UNE 61000-4-5)
(1.2/50µs - 8/20µs)
Common mode
PS 2 kV
DI’s, DO’s 4 kV
Comm. Ports 2 kV
Differential mode
PS, DI’s and DO’s 2 kV

Electrostatic Discharge IEC 60255-22-2 Class IV

(UNE 21-136-92/22-2) (IEC 61000-4-2)
On contact ±8 kV ±10 %
In the air ±15 kV ±10 %

Electromagnetic Immunity at IEC61000-4-8

Industrial Frequency (50/60Hz)

Radio Frequency Emissivity EN55022 (Radiated)

EN55011 (Conducted)

M1CPTA2005I
3-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 3. Standards and Type Tests

3.3 Environmental Test

Temperature IEC 60068-2

Cold work limit conditions IEC 60068-2-1
-25º C, 16 hours
Dry heat limit conditions IEC 60068-2-2
+70º C, 16 hours
Humid heat IEC 60068-2-78
+40º C, 93% relative humidity,
10 days
Quick temperature changes IEC 60068-2-14 (IED disconnected)
-25º C for 3h and
+70º C for 3h (5 cycles)
Transition time: 1ºC/min
Operating range From -25º C to +70º C
Storage range From -40º C to +85º C

3.4 Power Supply

Power Supply Interference and Ripple IEC 60255-11 / UNE 21-136-83 (11)
< 20 % and 100 ms
Supply Voltage Polarity Reversal IEC 61131-2

3.5 Mechanical Test

Vibration (sinusoidal) IEC-60255-21-1 Class I

a) Response: (Equipment running). Class II
b) Endurance: (Equipment off). Class I
Mechanical Shock and Bump Test IEC-60255-21-2 Class I

The models comply with the IEC 89/336 standard of electromagnetic compatibility

M1CPTA2005I
1CPT: Substation Central Unit 3-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 4. Physical Architecture

4.1 General................................................................................................................ 4-2

4.2 Dimensions.......................................................................................................... 4-2
4.3 Connection Elements .......................................................................................... 4-2
4.3.1 Terminal Blocks ................................................................................................... 4-2
4.3.2 Connectors .......................................................................................................... 4-3
4.3.3 Removing of Printed Circuit Boards (Non Self-shorting) .................................... 4-4
4.4 Human-Machine Interface ................................................................................... 4-4
 Chapter 4. Physical Architecture

4.1 General
The 1CPT is made up of several cards with different functions:

- Power Supply
- Digital Status Contact Inputs / Outputs
- Communication Ports
- IRIG-B Synchronization Interface
- Ethernet Connection
- Processor Module
- Frontal Card

Figure 4.1: Front View of a 1CPT.

4.2 Dimensions
The IEDs are fixed to enclosures of 1 19" rack width and 2 rack heights. They are designed to
be installed semi-flush mounted in panels. The enclosure is graphite grey.

4.3 Connection Elements

4.3.1 Terminal Blocks
The terminal blocks are arranged horizontally at the rear part of the 1CPT. They are distributed
as follows:

- 1 terminal block with 20 terminals for the power supply and 8 digital status contact
outputs.
- 1 terminal block with 16 terminals for 8 digital status contact inputs.

The terminals can take wire up to #14 AWG.

M1CPTA2005I
1CPT: Substation Central Unit 4-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 4. Physical Architecture

4.3.2 Connectors
The equipment is supplied with a number of connectors, as follows:

- Power supply connector (B1..B3): Located on the back of the equipment, at the 20
terminal block.
- Connector for 8 digital outputs (B5..B20): Located on the back of the equipment, at the
20 terminal block.
- Connector for 8 digital inputs (A1..A16): Located on the back of the equipment, at the
16 terminal block.
- Connector RS-232 for remote control communication (P1). Located on the back of
the equipment and tagged as P1. Allows for serial communication between 1CPT and a
control station. Communication parameters may be configured for this port.
- Connector RS-232 for communication with miscellaneous equipment (P2). Located
on the back of the equipment and tagged as P2. Allows for serial communication between
1CPT and a remote or local PC running the Zivercom® application for transparent
communication with ZIV level 1 equipment. It may also be used for other protection and
recording equipment with serial interface (e.g. equipment with DNP3, etc.).
Communication parameters may be configured for this port.
- Connector for external synchronizing clock input. Located on the back of the
equipment. 1CPT equipment are provided with a BNC connector arranged for connection
to IRIG-B external synchronizing system.
- Optical fibre connectors for communication with protection and recording
equipment (P3, P4). Located on the back of the equipment. 2 pairs (TxD and RxD) of
connectors for plastic or crystal optical fibre are incorporated.
- Connection Ethernet 100 Base-T RJ-45 (LAN1 and LAN2): Located on the back of the
equipment. To connect the 1CPT to an Ethernet LAN over which communications via
TCP/IP protocol can be established. It is used for communications between the 1CPT,
among others, and IEC-61850 relays, remote control centres (via IEC 60870-5-104, TCP
DNP3.0, etc.), for access to the 1CPT Integrated Web Console via HTTP, as well as
access to its TELNET server and FTP server.
- Earthing screw. Located on the back of the equipment.

The rear view of a generic 1CPT is shown at Figure 4.2:

Figure 4.2: Rear View of a 1CPT.

M1CPTA2005I
4-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 4. Physical Architecture

Figures 4.3 and 4.4 show in detail the digital input and output diagram, respectively:

Figure 4.3: Digital Inputs of the 1CPT. Figure 4.4: Power Supply and Digital Outputs of the
1CPT.

4.3.3 Removing of Printed Circuit Boards (Non Self-shorting)

The equipment has been designed to enable removal of some printed circuit boards. The
Current Analog Input terminal connector block, where the external wiring is landed, is attached
to both the terminal connector on the printed circuit board and the equipment case, using self-
tapping screws. These screws must be removed before the board is withdrawn.

Whenever this operation is performed, the protection should be placed in the Not in Service
mode, and turned off.

4.4 Human-Machine Interface

Front peripherals allow the interaction between user and 1CPT. The following can be found
among them:
• Display and Keyboard
A display composed of 20 columns and 4 rows is provided to show operation menus and data. It
features a function keyboard composed of 4 keys F1 to F4, and 16 additional keys to access the
different menu options.
• USB Master Port
This port allows connecting a USB key to transfer files between the 1CPT Compact-Flash and
the final user.
• LEDs
The equipment is provided with 5 pairs of LEDs (transmission and reception) to indicate
whether communication in one or other direction is active:

- Green lamp for reception: signal RxD

- Red lamp for transmission: signal TxD

There is also an additional LED to show relay Ready and there are 4 LEDs to signal user
configurable alarms.

M1CPTA2005I
1CPT: Substation Central Unit 4-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
5. Settings
 Chapter 5. Settings

The 1CPT is a highly configurable unit, with a large number of parameters. The functions
available depend on the software model.

The 1CPT gets configuration data from some files in text mode which are generated through
Zivergraph software. Through this software, a central unit can be customized to an
installation, configuring all the necessary parameters for each function.

Except for the programmable control functions, the 1CPT has no parameters whose execution
time can be adjusted. Any modification of the parameters must be done from the Zivergraph
software, after which the 1CPT can be reconfigured with the newly modified files. As this is a
complex procedure, the parameter variation ranges and settings will not be discussed here;
they will be indicated in the Zivergraph manual and in the annexes describing the
configuration files.

The adjustable parameters for the control functions are described in the section corresponding
to each one of them.

M1CPTA2005I
1CPT: Substation Central Unit 5-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 6. Description of Operation

6.1 Introduction.......................................................................................................... 6-4

6.2 Concept of the Equipment................................................................................... 6-5
6.3 General Functions ............................................................................................... 6-7
6.3.1 Synchronization ................................................................................................... 6-7
6.3.2 Daylight Savings / Standard Time Change ....................................................... 6-10
6.3.3 Audible Warning ................................................................................................ 6-10
6.4 Communications ............................................................................................... 6-11
6.4.1 Physical Medium ............................................................................................... 6-11
6.4.2 Communication with Level 1 Equipment ........................................................... 6-12
6.4.2.a Interrogation Cycle ............................................................................................ 6-12
6.4.2.b Communications Parameters ............................................................................ 6-14
6.4.3 Transparent Communication with Protection Equipment.................................. 6-15
6.4.4 Communication with Level 3 Systems .............................................................. 6-15
6.4.5 Routing Functions ............................................................................................. 6-16
6.5 Integration with Server Terminal model CIC ..................................................... 6-16
6.5.1 CIC Configuration .............................................................................................. 6-17
6.5.1.a Serial Interface Configuration ........................................................................... 6-18
6.5.1.b Network Interface Configuration ....................................................................... 6-20
6.5.1.c Connection Configuration.................................................................................. 6-21
6.5.2 1CPT Configuration ........................................................................................... 6-22
6.6 Level 1 Protocols ............................................................................................... 6-23
6.6.1 PROCOME ........................................................................................................ 6-23
6.6.2 DNP3 ................................................................................................................. 6-25
6.6.2.a Interrogation Cycle ............................................................................................ 6-25
6.6.2.b Communication Times ...................................................................................... 6-27
6.6.2.c Device Signals .................................................................................................. 6-28
6.6.3 IEC103 .............................................................................................................. 6-29
6.6.4 SPABUS ............................................................................................................ 6-30
6.6.5 MODBUS RTU .................................................................................................. 6-31
6.6.6 IEC61850 .......................................................................................................... 6-31
6.6.6.a IEC61850 Client ................................................................................................ 6-32
6.6.6.b IEC61850 Server ............................................................................................... 6-32
6.7 Level 3 Protocols ............................................................................................... 6-33
6.8 Control Functions .............................................................................................. 6-34
6.8.1 Detection of Resistive Grounds......................................................................... 6-34
6.8.1.a Contact Inputs ................................................................................................... 6-35
6.8.1.b Contact Outputs ................................................................................................ 6-35
6.8.1.c Settings ............................................................................................................. 6-35
6.8.1.d Status Flow Chart .............................................................................................. 6-36
6.8.1.e Operation ........................................................................................................... 6-37
6.8.1.f Reset ................................................................................................................. 6-38
6.8.1.g Own Signals ...................................................................................................... 6-38
6.8.2 H Control Function ............................................................................................ 6-39
6.8.2.a Voltage Presence / Absence Control Functions ................................................ 6-40
6.8.2.b Control Function for the Definition of High Voltage Status ................................ 6-42
6.8.2.c Control Function for High Voltage Manoeuvres ................................................ 6-44
6.8.2.d Control Function for Medium Voltage Manoeuvres ........................................... 6-49
6.8.2.e Control Function for Switching due to Protection Tripping ................................ 6-52
6.8.2.f Own Digital Signals ........................................................................................... 6-54
6.8.2.g Own Commands ................................................................................................ 6-55
6.8.2.h External Signals................................................................................................. 6-56
6.8.3 H2 Control Function .......................................................................................... 6-57
6.8.3.a Line Voltage Presence / Absence Control Functions ........................................ 6-58
6.8.3.b Control Function for the Definition of High Voltage Status ................................ 6-60
6.8.3.c Control Function for High Voltage Manoeuvres ................................................ 6-62
6.8.3.d Automatic Switching by Protection Trip ............................................................. 6-69
6.8.3.e Own Digital Signals ........................................................................................... 6-76
6.8.3.f Own Commands ................................................................................................ 6-77
6.8.3.g External Signals................................................................................................. 6-77
6.8.4 Y Control Function (Specific case of H) ............................................................ 6-79
6.8.5 Automatic Service Reset Equipment (ERAS) ................................................... 6-82
6.8.5.a UCERAS1.......................................................................................................... 6-83
6.8.5.b UCERAS2.......................................................................................................... 6-84
6.8.5.c UCERAS3.......................................................................................................... 6-87
6.8.5.d TERAS1 ............................................................................................................. 6-88
6.8.5.e TERAS2 ............................................................................................................. 6-89
6.8.5.f TERAS3 ............................................................................................................. 6-92
6.8.5.g TERAS4 ............................................................................................................. 6-93
6.8.5.h Own Signals ...................................................................................................... 6-94
6.8.5.i Own Commands ................................................................................................ 6-96
6.8.5.j External Signals................................................................................................. 6-96
6.9 UCS as Virtual Equipment ................................................................................. 6-97
6.9.1 Virtual Central Equipment ISC-s (Digital Signals) ............................................. 6-97
6.9.2 Virtual Central Equipment ISE-s (Commands).................................................. 6-99
6.9.3 Virtual Central Equipment ISS-s (Output Writes) ............................................ 6-100
6.10 Programmable Logic ....................................................................................... 6-100
6.11 Remote Console .............................................................................................. 6-106
6.12 Commands ...................................................................................................... 6-107
6.12.1 Group Commands ........................................................................................... 6-108
6.12.2 Master Commands .......................................................................................... 6-108
6.12.3 Commands sent to IEC 61850 Devices .......................................................... 6-109
6.13 LEDs ................................................................................................................ 6-109
6.14 Digital Inputs .................................................................................................... 6-109
6.15 Digital Outputs ................................................................................................. 6-109
6.16 Logs (optional) ................................................................................................ 6-110
6.16.1 Logs Collecting ................................................................................................ 6-110
6.16.1.a Metering Logs ................................................................................................. 6-110
6.16.1.b Counter Logs ................................................................................................... 6-110
6.16.1.c Change Logs ................................................................................................... 6-110
6.16.2 Reports and Trends ........................................................................................ 6-111
6.16.2.a Connection to the 1CPT Relay ....................................................................... 6-112
6.16.2.b Graphic Type Report Generation .................................................................... 6-113
6.16.2.c Chart Type Report Generation ........................................................................ 6-119
6.16.2.d Deleting the Database..................................................................................... 6-122
6.16.2.e Database Disconnection ................................................................................. 6-122
6.16.2.f Installation Instructions .................................................................................... 6-123
6.17 Redundancy .................................................................................................... 6-124
6.17.1 Introduction...................................................................................................... 6-124
6.17.2 Communications Topologies ........................................................................... 6-124
6.17.3 Redundancy Functions ................................................................................... 6-128
6.17.3.a Central Units ................................................................................................... 6-128
6.17.3.b Automatic Switch over Mechanism ................................................................. 6-130
6.17.3.c Manual Switching Mechanism......................................................................... 6-137
6.17.3.d Bay Device Communications .......................................................................... 6-138
6.17.3.e Remote Control Communications ................................................................... 6-139
6.17.3.f Operation HMIs ............................................................................................... 6-139
6.17.4 Configuration Parameters ............................................................................... 6-140
6.17.4.a Redundancy Types ......................................................................................... 6-140
6.17.4.b Configuration Parameters ............................................................................... 6-142
6.18 Substation Configuration Server: UCSConf .................................................... 6-143
6.19 Maintenance Options ...................................................................................... 6-144
 Chapter 6. Description of Operation

6.1 Introduction
The 1CPT’s software is made up of two independent tasks:

- Substation Central Unit or Remote Control Unit application.

- Integrated Web Console application.

The Substation Central Unit or Remote Control Unit application is in charge of permanently
updating a centralised substation protection and control equipment database and allows the
Remote Control Centre and the 1CPT Integrated Web Console to gain access to said database.
This application will also implement substation level programmable logic and automatic controls.

In its own right, the Integrated Web Console application through the 1CPT web server will be in
charge of serving the different command and control screens to the various system clients.

The Substation Central Unit application includes several independent tasks carrying out specific
functions executed over a multitask environment. Many of these tasks are fixed and constitute
what is known as 1CPT core. Other tasks will be included depending on the 1CPT model and of
the loaded configuration.

The main task is to collect information from other equipment at a lower conceptual level,
process it and serve it to a higher conceptual level equipment. To do this, it uses
communications protocols which are emulated and adapted to the 1CPT’s internal structure.

There are also other tasks that provide additional functionality, giving the 1CPT great potential
for processing data from the installation.

M1CPTA2005I
1CPT: Substation Central Unit 6-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.2 Concept of the Equipment

In the 1CPT’s internal structure, all signals (digital and analog) come from a specific unit and
are uniquely identified by a pair of numbers: unit and signal. The Unit identifier is, in general
terms, the address of the unit in the communications protocol. The Signal identifier is a signal’s
index within a group of signals from a unit: digital inputs, digital outputs, analog inputs, etc.; in
other words, each group of signals is made up of signals identified by a consecutive number
from 0 to 1023.

Each of these groups has a mnemonic that distinguishes it: ISC, digital inputs; MEA, analog
inputs; ISE, commands; CON, counters; ISS, digital output writing signals; ISM, analog output
writing signals. These identifiers are taken from the PROCOME protocol, but thanks to the
emulation of other protocols, they can be applied to all equipment connected to the 1CPT.

As an example, we can say that the open breaker signal corresponds to ISC 52 from unit 22, or
that the voltage of a bus is MEA 3 from unit 12.
• Virtual Units
In order to incorporate into the system the signals generated by the 1CPT’s different functions,
a number of internal units have been created which have no physical correspondence (i.e.,
virtual), which have these signals associated with them.

The virtual units that may be present in the 1CPT are the ones shown in Table 6.1. Both the
model and the configuration of the 1CPT determine what virtual units will be present in a certain
installation.

M1CPTA2005I
6-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6.1 also indicates the range of signals that each of the virtual units has. Each one will be
described further on when its functionality is discussed:

Table 6-1: Range of Signals of the Virtual Units

Address Signals Description
256 ISC: 0...1023
ISE: 0...1023
ISS: 0 Logic. This task that is responsible for
executing the logic program generates its own
MEA: 0…255 signals as a result of that execution.
CON:0…255
ISM: 0..255
257 ISC: 0 ... 345 Central. Groups the signals generated by the
ISE: 0 ... 33 central unit itself considered as a unit. These
signals are, among others, communications
ISS: 0 … 7
failures with equipment, internal signals, status
of the 1CPT’s digital inputs, etc. It gathers
virtual Central equipment commands and 1CPT
digital output writes (refer to section 6.9).
258 ISC: 0…7 Remote control. Indicates the status of
communications with the control office.
259 ISC: 0...7 + NPos Control function to detect resistive grounds.
The number of signals depends on the number
of IEDs configured.
260 ISC: 0...28 H Control function.
ISE: 0...13
261 ISC: 0...23 + ERAS Control function.
40 * Terminal
ISE: 0 ... 3
262 ISC: 0...7 + NPos Control function to detect resistive grounds.
Module 2.
263 ISC: 0...7 + NPos Control function to detect resistive grounds.
Module 3.
264 ISC: 0...7 + NPos Control function to detect resistive grounds.
Module 4.
265 ISC: 0...7 + NPos Control function to detect resistive grounds.
Module 5.
266 ISC: 0 … 1023 Communications task with a PLC.
ISE: 0 …1023
MEA: 0 … 255
CON:0 … 255
267 - Spare.
268 - Spare.
269 ISC: 0 ... 20 Task in charge of 1CPT redundancy.
ISE: 0 ... 3
270 Spare.
288 ISC: 0...1023 IEC-61850 Server.
ISE: 0...1023

These addresses are configurable but, for convenience and portability, it is recommended to
use them.

On the other hand, there may exist several remote control emulator instances to which
addresses other than the one shown in the table above must be assigned; for example, from the
address 270.

M1CPTA2005I
1CPT: Substation Central Unit 6-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.3 General Functions

6.3.1 Synchronization
The 1CPT can be responsible for keeping all lower-level equipment present in the installation
synchronized with a reference date and time. Level 1 device synchronization is carried by the
1CPT in two neatly differentiated ways:

- Through periodical synchronization message transmission gathered in the

communications protocol used for level 1 device control communications. In this case, the
1CPT will send a synchronization message with configurable periodicity through
parameter Synchronization Time. If the protocol allows it, the synchronization message
is broadcast, i.e., all relays for one port are synchronized at once.

- Through the use of a specific communications protocol for synchronization of equipment

connected to the network. The 1CPT features a time synchronization server via protocol
SNTP (Simple Network Time Protocol), which can operate both in broadcast or multicast
mode and unicast mode. In broadcast or multicast mode, the 1CPT will send periodically
a synchronization message that can be retrieved by all level 1 equipment configured to
this end. In unicast mode, level 1 equipment will be in charge of requesting periodically
the date and time to the 1CPT server SNTP.

In addition, in order to ensure that the equipment is synchronized with reliable data, the 1CPT
itself is synchronized from different sources. The origin of these sources depends on the
configuration and on the status of the sources; there are several possibilities.
• Synchronization from the operating console
The 1CPT’s internal clock is synchronized by the user from the operating console. To do this,
the Synchronize 1CPT option from the Engineering display is used. The data entered is sent to
the 1CPT, which uses it to change its internal time and then synchronize the equipment.

Synchronization is enabled through the 1CPT operations Console provided synchronization is

not being carried out through other external synchronization sources or when said
synchronization sources suffer from anomalies that hamper correct 1CPT synchronization.
• 1CPT Synchronization from the HMI
1CPT date and time can also be set from the relay HMI. To this end option Date and Time of
the maintenance menu is used. Data entered are used by the 1CPT to change the internal time
and then devices are synchronized.

The 1CPT enables setting the date and time through the HMI provided synchronization is not
being carried out through other external synchronization sources or when said synchronization
sources suffer from anomalies that hamper correct 1CPT synchronization.

M1CPTA2005I
6-7 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Synchronization from the control office

The control office periodically sends the time to the 1CPT using the appropriate
communications protocol. The 1CPT uses this data to change its internal time and then
synchronize the equipment.
• GPS clock synchronization
If there is an external GPS synchronizer, the data it supplies will be used for synchronization.
Depending on the interface connecting to the clock, the sync method and the necessary
parameters will be different. In all cases, using a certain protocol, the GPS clock sends, updated
date, time and status data at periodic intervals; the 1CPT uses this data to synchronize its
internal clock. In case of synchronization through protocol SNTP, the 1CPT SNTP client can be
configured to periodically request the time to a number of SNTP servers accessible through the
electrical utility communications network.

First of all, on the configuration of the 1CPT there is a parameter (GPS Clock) that indicates
whether a GPS clock is connected to the 1CPT, and if so, what type it is. The types available for
the 1CPT are the following:

- IRIG-B123: this interface accepts a connection with any clock that complies with the
IRIG-B123 protocol. A coaxial connector is used.
- IKOR 232 serial (also ZIV 1GPS 232 serial): this option is used to connect a clock
specific to the IKOR company, or a ZIV clock, using their RS232 serial interface. The
clock sends time data in a serial frame with a certain format. One of the
communications ports labelled P1-P2 is used. The format of the frame is as shown in
the table below.

Table 6-2: Frame Format

[STX]D:dd.mm.aa;T:n;U:hh.mm.ss;#*S![ETX]
[STX] Start of frame (0x02)
D Block indicator
dd Day of the month (2 digits)
mm Month (2 digits)
aa Year (2 digits)
T Block indicator
n Day of the week
U Block indicator
hh Hours (2 digits)
mm Minutes (2 digits)
ss Seconds (2 digits)
#/Espacio Possible sync error greater than 3ms/OK
*/Espacio Internal clock failure/OK
S/Espacio Daylight savings time / Standard time
!/Espacio Less than one hour until standard-daylight savings change/NO
[ETX] End of frame (0x03)

- SNTP: the 1CPT SNTP client is connected via Ethernet to the SNTP servers available
in the communications network and can be configured to operate in unicast mode and
in broadcast or multicast mode.

M1CPTA2005I
1CPT: Substation Central Unit 6-8
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

All of these types of clocks are mutually exclusive and only one may be connected to the 1CPT
at one time.

From a software and a hardware standpoint, all of the interfaces are available, and the one
desired is chosen through configuration.

For the serial interfaces, the communications parameters must also be configured: serial port,
speed, parity, stop bits. This is done with the Zivergraph software.

Communications problems with the GPS clock are indicated through the generation of a change
in the PROCOME 256 signal from the central virtual unit (address 257). If there is no
communication with the clock or if the data being received is not correct, a signal change with
status of 1 is generated; when communication is restored, a change to 0 is generated. During
this entire time, the system behaves as if no GPS clocks were connected, allowing
synchronization from other sources (office, console). The parameter Time Allowed with no
Interruptions controls the time passed from the moment an error situation is detected until the
respective signal is generated (this parameter will not be used by the 1CPT SNTP client).
Under certain circumstances, the time difference between the 1CPT’s internal time and the
GPS clock’s time may be more than 20 ms. In this case, there is considered to be a sync error,
and a change (activation) is generated in the PROCOME 257 signal from the central unit (257).
When this difference is less than 20 ms. another change (deactivation) is generated for that
signal. This function is configurable and can be enabled / disabled with the Deviation Error
parameter.

If the function is enabled, this sync error situation is maintained for the time marked by the
parameter Time with GPS Error before Considering it Incorrect. Once this time has elapsed,
the 1CPT’s internal clock is updated with the GPS time, and the new time is considered to be
the correct one.

If the synchronization system is via GPS clock and it is working properly, the 1CPT will not
accept another type of synchronization: operating console, control office.

There is an additional synchronization system function relating to the emulator of the PID1
remote control protocol, which will be explained in the chapter dealing with this emulator.

M1CPTA2005I
6-9 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.3.2 Daylight Savings / Standard Time Change

The 1CPT can manage the daylight savings / standard time change if it is configured to do so,
for external synchronization systems with a different procedure.

Some synchronization systems use UTC (Universal Time Coordinated) format and, therefore,
the summer / winter time change is managed by the 1CPT. This is also carried out by the 1CPT
in systems without GPS and with some Remote Controls.

However, a number of synchronization systems operate in local time with DST (Daylight Saving
Time) information, the summer / winter time change being carried out in this instance by the
external synchronization system, notifying the 1CPT.

The daylight savings / standard time change function consists of moving the 1CPT’s time
forward or backward on a specific date at a specific time. This function is configurable and can
be disabled / enabled. The number of hours that the time must go forward / backward can also
be configured, as well as when the change should take place.

There are two parameters that relate this function to the GPS clock. One of them indicates
whether the GPS is managing the time change, or whether the 1CPT must do it, while the other
indicates whether the GPS indicates the current time period.

All of these parameters are configured through the Zivergraph® software, from the general
settings display.

6.3.3 Audible Warning

The audible warning function is closely linked to the alarms. It consists of an audible warning
going off every time an alarm is received in the 1CPT. This function has been implemented as a
generic command on a unit. Every time an alarm is received, this command is executed. When
configuring the signals for each unit, the user can indicate, on an individual basis, which alarms
will make the audible warning sound.

The audible warning will be connected to the digital output of a unit (a level 1 equipment or the
1CPT) so that when the latter receives the command it will close the contact that will turn on the
warning. This contact will remain closed for a certain amount of time.

There is a parameter indicating whether the audible warning is enabled or not. There is no
additional functionality for acknowledgment of the warning or time settings. If necessary, this will
have to be implemented with external logic.

M1CPTA2005I
1CPT: Substation Central Unit 6-10
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.4 Communications
Communications are the key element of the 1CPT. The 1CPT is responsible for collecting
information from level 1 equipment and distributing it to a higher or same level equipment. In
order to perform this task, a series of communications protocols is used to adapt to the existing
or required architecture in each installation.

6.4.1 Physical Medium

The connection between the 1CPT and bay devices is carried out mainly by:

- Fiber Optic. Available only for serial connections. There are two reasons why this
physical medium is used: one, to isolate the 1CPT from possible damage from
overvoltages in the rest of the equipment; and two, to prevent possible interference with
communications caused by existing wires at the installations. The 1CPT has 2 fiber optic
ports, labelled as P3 and P4.

- Twisted pair Ethernet 10-100 Base-T. Used for communications over IEC-61850
Ethernet networks. The 1CPT is provided with 2 net ports with RJ-45 electrical type
interface, labelled LAN1 and LAN2.

The RS232C interface is also used to communicate with other equipment, especially when
modems are used. All of the 1CPT’s ports are isolated by means of optical couplers.

To connect the 1CPT to level 3 systems (remote control, SCADA, etc.), there are several
RS232C serial ports with DB9H connectors, with all lines available (RX, TX, CD, DTR, RTS,
CTS, etc.). Radio or telephone modems, converters (RS232-FO, RS232-RS485), etc. may be
connected to these ports. Communications between the 1CPT and level 3 systems is possible
through LAN1 and LAN2 Ethernet ports, if the protocol so requires.

In case more communications ports are needed, it is possible to connect two terminal servers
model CIC, with 9 serial ports each.

M1CPTA2005I
6-11 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.4.2 Communication with Level 1 Equipment

Integrated Protection and Control System (SIPCO) functions are distributed over the various
installation devices. The data capture and processing function is carried out by bay devices,
which can perform other functions: protection, measurement, supervision, etc. the 1CPT is in
charge of retrieving and processing data from bay devices, and distribute the same to the rest of
higher level devices.

In order to carry out these functions, all different elements must be linked. 1CPT uses
communications protocols adequate for each device.

Communications with bay devices is carried out through a number of 1CPT tasks. These tasks
have been designed such that data are captured with a given speed and reliability.

CPTs interrogate devices in sequential form per port. In the configuration, each device is
assigned a port to which it is connected. In the configuration database, the device list is saved
in the same sequence as they were configured. In general, this list is not optimal from a
communications point of view, therefore, once all devices have been created into said list,
another list is generated with the port connected devices. In this way, for each port there will be
a list with the port connected devices. This list is valid both for 1CPT own ports and CIC ports.

6.4.2.a Interrogation Cycle

There exist a great diversity of communications protocols, but they can be segregated into two
main groups: unbalanced and balanced. In the first case, the device sends data only when the
master requests. In this case, 1CPT acts as master and the rest of devices as slaves, and the
interrogation cycle consists of cyclic control data requests to each level 1 device in order to
update the database.

In the second case, after some communication initialisation messages, the 1CPT waits for the
device to send any data that might be changed.

Standard IEC-61850, DNP3 e IEC-60870-5-101 is among this second type protocols. The rest
of protocols are comprised in the first type.

For level 1 devices with no IEC-61850 communications an interrogation cycle is established to

update the database in the least possible time. This control cycle is of high priority, but can
occasionally be interrupted by protection messages.

M1CPTA2005I
1CPT: Substation Central Unit 6-12
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The messages that make up this monitoring cycle depend to a large degree on the protocol
used to communicate with the equipment. However, in basic terms, a generic interrogation cycle
can be established, divided into three parts: initialization, continuous cycle and periodic
requests. This interrogation cycle is applied to each device and each port.

• Initialization: This procedure is used every time communication begins with a unit for the
first time or after a communications failure.
• Communications initialization.
• Time synchronization.
• Change request.
• Refresh request.

• Continuous cycle: This is the normal procedure for updating information at the substation.
• Change request and control measures.

• Periodic requests: These procedures are used periodically; the period is configurable.
• Counter request.
• Synchronization.
• Refresh request.

• Asynchronous procedures: These procedures are used as an answer to an external

“event”.
• Commands.
• Output Writings.
• Transparent communications.

Figure 6.1 Device Interrogation Procedure.

M1CPTA2005I
6-13 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

These cycles are applied individually to each device, except for periodic procedures, which are
applied equally to all. The periodic synchronism procedure is carried out in broadcast mode per
port, in this way, all port connected devices receive the time signal at once. As a general rule
devices are in continuous cycle and will occasionally switch to periodic cycle. Asynchronous
procedures are also individual and are only applied to affected devices.

There are variations on this interrogation cycle, resulting from the different protocols that the
1CPT uses to communicate with the equipment. 1CPT adapts to the protocol or device
distinctive features.

If a unit does not respond to a message sent by the 1CPT before a configurable period of time
has elapsed, the 1CPT will generally try to resend. However, this depends on the protocol, so
this will be explained further on. When the configured number of attempts is reached, a device
communication fail signal is generated, switching to initialisation state.

In a first stage, level 1 IEC-61850 devices are configured by the 1CPT to spontaneously send to
the 1CPT all device signal changes. The second stage is to request a complete refresh of all
bay device databases and then the 1CPT spontaneously receives the changes generated by
each configured bay device.

6.4.2.b Communications Parameters

Level 1 device communications parameters can be configured through the 1CPT:

- Serial Communication: speed, parity, number of bits, stop bits, delay times, etc. The
Zivergraph® software lets the user configure all communications port parameters:
speed, parity, stop bits, number of bits, times. Some of these parameters are
associated with the port, and will be configured from the display corresponding to
communications and port cards.

- Ethernet Communications: IP address and 1CPT sub-network mask. These parameters

associated to Ethernet communications can be configured via the Zivergraph
programme.

There exist many other protocol or device parameters configured via the Zivergraph software
or in the protocol configuration file.

M1CPTA2005I
1CPT: Substation Central Unit 6-14
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.4.3 Transparent Communication with Protection Equipment

The 1CPT is designed to communicate with control equipment. However, it can also be
connected to protection equipment. The 1CPT provides a mechanism for accessing protection
data, but only for equipment using PROCOME as their protection protocol. This communication
is not possible for any other equipment.

The only thing the user needs to do is use the communications program with the PROCOME
unit and connect to the 1CPT by one of the methods it allows: RS-232 serial connection (P2
port), and TCP/IP Ethernet network connection (LAN1 or LAN2 ports). Once the connection
with the 1CPT is made, the user can communicate with the PROCOME unit desired. The 1CPT
routes the messages it receives from this program towards the port where the unit in question is
connected, and sends the latter’s responses towards the program.

This function is called Transparent Communication, because from the standpoint of the user
and the manufacturer’s program, the 1CPT sets a logic link between both ends.

6.4.4 Communication with Level 3 Systems

An important part of the 1CPT’s communications is being able to communicate outside of the
substation, toward the higher level layer. This makes it possible to remotely monitor and control
the substation using the appropriate medium.

The 1CPT has two RS232C serial ports to communicate with external equipment. This
communication takes place through a communications protocol specific to each installation. The
one that is used depends on the client’s requirements.

Communication with the level 3 system takes place through the emulation of the protocol in
question. Not only are the protocol’s own messages emulated, but to the extent possible, the
behaviour of the original equipment using the protocol is emulated. In this way, the level 3
system is made to believe that it is communicating with an original unit instead of an emulated
one.

This is not always possible, because in some cases, the protocol is designed to communicate
with a unit (RTU type), while in the case of an installation with 1CPT, it would be communicating
with a distributed system.

When emulating these protocols, the 1CPT behaves like a slave terminal, responding to
information requests from the master terminal and carrying out the commands it receives from
the latter.

Furthermore, the 1CPT features two Ethernet network interfaces which can be used for
communications with Level 3 devices, keeping the same serial interface functions. Few
protocols allow using these network interfaces for communications with level 3 systems: IEC-
60870-5-104, DNP3 and MODBUS.

M1CPTA2005I
6-15 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.4.5 Routing Functions

The 1CPT keeps a routing table that is automatically generated when started. Said table is used
to handle data inputs and decide whether to accept them or not.

Also, the 1CPT features a function to add inputs to said table to expand or limit the networks
from which access to the 1CPT is enabled. Said function is configured through the Zivergraph
using the configuration file route.cfg.
Up to four inputs to be added to the 1CPT routing table can be included into the configuration
file.

If a universal communications port is required it must configured in said file. Simply add an input
with parameters 0.0.0.0 both for the target IP address and the network mask, and with said port
IP address in the gateway IP address field.

6.5 Integration with Server Terminal model CIC

1CPT own communications interfaces have been dealt with in the above section. For relatively
large substations or when devices from various manufacturers with different protocols must be
integrated, more communications interfaces are needed. In this case, the Terminal Server
model CIC device is used.

CIC features 9 serial ports with RS232 interface or fibre optic in different combinations
depending on model. Also, it features two RJ45 ports that behave as ethernet switches. It also
features a front RS232 port for maintenance and configuration.

1CPT and CIC are connected through the network ports, using the substation network or point
by point using one of the two RJ45 connectors provided for each one. In this way both devices
could be in the same cabinet or separated, even several kilometres.

The diagram below shows the way CIC is integrated with the rest of the substation devices. It is
only an example where a switch has been used to interconnect all devices with the network
interface.

M1CPTA2005I
1CPT: Substation Central Unit 6-16
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.2 Example of CIC Integration with the rest of the Substation Devices.

The main CIC function we are interested on is to encapsulate /de-encapsulate messages into
TCP/IP frames. Internal logic connections between TCP ports and physical serial ports are
established such that everything received by a given serial port is sent via the network interface
of the applicable TCP port and the opposite, everything received by the CIC, bound for TCP
port, is sent via the associated serial port.

One of the main features of CIC is that it has remote access to serial port parameters through
protocol RFC2217. In this way, serial port communications parameters can be modified hot from
the network interface. On the other hand, it is also possible to operate on the modem control
lines and check their status as well.

6.5.1 CIC Configuration

In order for the 1CPT to use CIC serial ports, it must be configured in agreement with the 1CPT
configuration. The CIC can be configured by a network interface via web access or using the
front service port by means of CLI (Command Line Interface).

In order to access CIC through the web interface, its IP address must be known beforehand. By
default, the IP address is in the range 192.168.0.1/24. If the IP address is not known, it can be
found by connecting to the front serial port through a flat cable using a terminal programme
configured to 115200,8,p,1 and then access the rest of configuration parameters via the web
interface.

Access is protected by password. There exist two different users: “guest” and “admin”. The first
user has only read access and the password is “passwd01”. The second user has all
permissions and the password is “passwd02”.

M1CPTA2005I
6-17 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

As a general rule the CIC configuration is adequate to communicate with the 1CPT,
nevertheless, the IP address might need modifying for integration into the 1CPT network. Below
are the parameters to be configured for integration into the 1CPT.

6.5.1.a Serial Interface Configuration

Baud rate, data bits, parity and stop bits can be configured for each of the nine CIC serial ports.
Setting values must be adequate although these settings can be edited through protocol
RFC2217.

On the other hand, logic parameters must be configured with values adequate for 1CPT
requirements. Thus, the figure below shows the values.

Figure 6.3 Values of 1CPT Logic Parameters.

M1CPTA2005I
1CPT: Substation Central Unit 6-18
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Parameters to be taken into account are:

- Interface: RS232 shall be selected, even if the physical interface is fibre optic.
- Baudrate: Port baud rate.
- Databits: Number of port bits. Normally, 8 is configured.
- Parity: Port parity. Normally “even” is used
- Stopbits: Configured with the value 1.
- Flow control: Configures with the value “none”. If the port connected device needs
modem control line management, it will be carried out from the 1CPT application via
protocol RFC2217.
- Protocol: “packed”. This protocol shall be used, as it is generic. It is 1CPT application
task interpreting and processing the received packets in accordance with the
configuration protocol.
- Packed time: Time, in milliseconds, of line inactivity elapsed before the packet received
can be deemed complete. When this time, from the last byte received, times out, the set
of bytes received is considered as a packet and is sent through the socket to the 1CPT.
An adequate value shall be set in view of the baud rate. Normally 10 ms is used.
- Packed size: Maximum packet size is normally 300. It must be configured above the
maximum size of the packet to be sent/received in order to use only the timeout
criterion to determine if a packet is received (Packet time).

On the other hand, page “Flow” shows a table

with the 9 serial ports and corresponding
Identifiers, which we must use later to carry out
the connections with TCP ports. This table is
represented in the figure to the right.

Figure 6.4 Serial Port Table.

M1CPTA2005I
6-19 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.5.1.b Network Interface Configuration

As many passive TCP ports as the number of serial ports are defined for the network interface,
namely, 9. They are assigned a name in order to carry out later associations as well as a TCP
port, which must be configured in the applicable 1CPT configuration file.

The applicable page is displayed through the link “Flow” in the menu to the left of the page.
Click the Add button in the table “Passive TCP” to add all the necessary ports, one for each
serial port.

Fields must be filled in as shown in the figure below.

Figure 6.5 Network Interface Configuration Screen.

Parameters to take into account are:

- Identifier: “Virtual port” name.

- Port: Number of the TCP port associated with the “Virtual Port”. The first port will be
assigned the value 1001, and consecutive numbers for the rest of the values, ending up
with 1009 for the ninth port.
- Packed time: Time, in milliseconds, of line inactivity elapsed before the packet received
can be deemed complete. When this time, from the last byte received, times out, the set
of bytes received is considered as a packet and is sent through the socket to the 1CPT.
An adequate value shall be set in view of the baud rate. Normally 10 ms is used.
- Packed size: Maximum packet size is normally 300. It must be configured above the
maximum size of the packet to be sent/received in order to use only the timeout
criterion to determine if a packet is received (Packet time).
- RFC2217: State whether protocol RFC2217 is enabled.
- Enable: State whether the port is enabled or not.

M1CPTA2005I
1CPT: Substation Central Unit 6-20
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.5.1.c Connection Configuration

After configuring serial ports and TCP ports, they must be connected to each other. This is
made in the Connection page, which is displayed from option “Flow  Connection” in the
menu to the left.

Although CIC allows making any connection, from the point of view of the 1CPT functionality,
each physical serial port will be associated with its corresponding TCP port. In order to safely
carry out this operation, the names given in the identifier fields in the “Flow” page must be
remembered.

Click the Add button and write the name of the serial port Identifier field in the field to the left
and the name of the TCP port Identifier field in the field to the right. Proceed in this way for all
CIC ports.

Figure 6.6 Connection Configuration Screen.

M1CPTA2005I
6-21 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.5.2 1CPT Configuration

After knowing how to configure CIC, the way to configure 1CPT must be known in order to use
CIC resources.

1CPT port assignment varies depending on the port functions. In some cases virtual ports are
used, as is the case for device configuration in dbase.cfg file and physical ports are used in
other cases, such as remote controls and some emulators.

At the time of stating the CIC port to be used, this requirement must be taken into account,
which must be perfectly integrated with the rest of the configuration tools, such as the
Zivergraph.

In order to ease the configuration and create mnemonic rules, CIC ports are identified with a
virtual number, such that, just looking at it, we can quickly know which CIC port is being used.
Also, in order to send data to the CIC, we must associate the TCP port to be used to send data
to the CIC with each virtual port. This TCP port is the port configured in advance in the Port field
in table “Passive TCP” of the CIC “Flow” page. This association will be made in the
“TSComs.cfg” configuration file. In this file we can configure up to two Terminal Servers. For
each of them, the assigned IP address and the port assignment to be made must be stated.
Although this is an editable file, we will work on a fixed port assignment, the contents of which is
summarised in the tables below.

First CIC Second CIC

Virtual TCP Virtual TCP
Port Port Port Port
201 1001 211 1001
202 1002 212 1002
203 1003 213 1003
204 1004 214 1004
205 1005 215 1005
206 1006 216 1006
207 1007 217 1007
208 1008 218 1008
209 1009 219 1009

We have kept the same TCP port assignment for both CIC with the purpose to ease device
maintenance in case a faulty CIC must be replaced by a new CIC; only its IP address must be
adequately configured, with no need to know whether a “First” or “Second” CIC is being
replaced.

Taking into account this virtual port numbering, let us define the way to use them in the various
files. So that, if the port to which the device is connected is identified using the logic port
number, such as in dbase.cfg, now, we just will state the virtual port directly taken from the
above table.

If the device is connected to a COM type port, the port will be indicated replacing the COMx
string by a string starting with V followed by the virtual port, namely, a string with format Vxyz.
For example, if the device is connected at the third port of the first CIC we will write V203 to
identify said port.

M1CPTA2005I
1CPT: Substation Central Unit 6-22
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

CIC implements protocol RFC2217 to be able to modify the communications characteristics and
modem line control via the TCP connection. This function can be deactivated by means of the
web server. If it is deactivated, the physical port is configured with the parameters assigned in
its configuration.

These parameters can be modified from the 1CPT through protocol RFC2217, however, this
operation is not required for all ports. As a general rule, the own CIC configuration is used.
Modem lines used are: DTR and RTS as CIC output signals and CTS and CD as input signals.
No data management is performed with them by CIC, they just notify a change of status in CTS
and CD and activates or deactivates DTR or RTS when requested from the 1CPT. This function
is only activated when the applicable 1CPT configuration file is adequately configured.

On the other hand, as is logical, in fibre optic ports no modem control line management is
performed.

6.6 Level 1 Protocols

Information is transmitted between the IEDs and the 1CPT using different communications
protocols. The standard protocol, which is on all 1CPT models, is PROCOME. In addition to this
protocol, the 1CPT can communicate with level 1 equipment using the following: MMS for IEC-
61850, DNP 3.0, MODBUS RTU, IEC103, etc. All of the protocols cannot be used at the same
time in the same unit; the types of equipment that can be connected depend on the model.

The PROCOME and DNP 3.0 and IEC103 protocols allow equipment to be connected at fiber
optic ports (P3 and P4) of 1CPT or CIC. All accept more than one unit at each port, although
equipment with different protocols cannot be mixed at the same port.

IEC-61850 communications with bay devices is only available through one of the 1CPT
Ethernet ports (LAN1 or LAN2); such that the desired port must be selected in advance through
the 1CPT configuration.

6.6.1 PROCOME
PROCOME is a protocol based on European standards which is specifically designed to handle
data in electrical substation protection and control systems. All 1CPT models are equipped with
this protocol.

Equipment with the PROCOME protocol is configured as normal equipment using Zivergraph®
or the DBASE.CFG file. This equipment can only be connected at fiber optic ports (P3 and P4)
of the 1CPT of the 1CPT, or in any CIC port.

PROCOME device interrogation cycle is described in section 6.4.2.a, this status machine being
individually applied to each device. Also, several more or less simultaneous interrogation cycles
are sustained, one per port, in order to make the most of the 1CPT multi-processing capacity.
Thus, while waiting for a device response at a port, the response of other device at other port
can be processed. After the last in the list has been interrogated, it starts again with the first.

M1CPTA2005I
6-23 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

There are different priorities in the interrogation procedures. Commands and output writings are
the highest priority and Interrogation of Changes and Control Measurements, namely, the
continuous cycle procedure, the lowest priority.

If a unit does not respond to a message sent by the 1CPT before a certain (configurable)
amount of time has elapsed, given by the Communications timeout parameter (in
Zivergraph®, in the equipment properties display; in DBASE.CFG, Time parameter in General
equipment data), the 1CPT tries to resend. If it does not respond to this retry, an internal signal
is generated from virtual unit 257, indicating a communications failure with that unit, and the
1CPT goes on to the next unit.

When it is again the turn of a failed communication device, the initialisation procedure is applied
instead of the procedure that caused the failure. In this INITIALISATION status, if no response
is obtained in five consecutive cycles, it is brought out of the continuous cycle and it is
interrogated at a lower rate (every 5 times); moreover, under this situation the value of
Communications Timeout setting is not taken as waiting time, but a lower configurable time
setting is taken, Failed communication Timeout, in the Zivergraph, in the device features
screen; in dbase.cfg, parameter TimeReconex, in Device General data).

Sometimes, when there is only a single device per port, the continuous cycle could mean an
excessive communications processing load, so the interrogation rate must be decreased by
introducing delays before sending a new message. There is a configuration parameter which
indicates whether this delay should be introduced or not (Delay sending messages in
Zivergraph® and BitDelay in CENTRAL.CFG). The number of milliseconds in the delay can
also be configured (Time between interrogations in Zivergraph® and QuesTime in
CENTRAL.CFG). This time is general and is applied to all ports with PROCOME equipment.

If a unit is the only one connected to a port, the delay is introduced before each message sent
to the unit, even if the function is not enabled.

Finally, after a broadcast message (message directed to all units at one port), a certain waiting
period is required before another message is sent so the equipment can process the first one.
There is a fixed parameter (70 ms) which indicates how long the next query should be delayed
to the next unit. This time is general and is applied to all ports with PROCOME and DNP3
equipment.

Asynchronous procedures, commands, output writings, PROCOME transparency are applied

“as soon as possible”, although, it always waits for the completion of the procedure in progress
with the device being interrogated during the cycle of the affected port, even if the procedure is
of higher priority.

M1CPTA2005I
1CPT: Substation Central Unit 6-24
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.2 DNP3
DNP3 is a generic control communications protocol widely used in the industry (www.dnp.org).
Although it is a matter of a standard procedure, there exist many data transmission alternatives,
so that there are several different implementations depending on the manufacturer. This is the
reason why an interoperability profile for each device is required in order to know if it can be
integrated into the 1CPT. This profile must be cross checked with the 1CPT profile.

Equipment with the DNP3 protocol is configured as normal equipment using Zivergraph® or the
DBASE.CFG file stating that the type of control is DNP3. This equipment can be connected at
fiber optic ports (P3 and P4) or at RS-232 serial port (P1 and P2) and to any CIC serial port.

There are certain parameters that only affect equipment with DNP3 protocol; these are
configured in Zivergraph® in the Specific DNP3 protocol data display or in the DNP3MS.CFG
file.

6.6.2.a Interrogation Cycle

The equipment interrogation cycle can be configured by port, and a different cycle can be used
for each port, all devices connected to the same port sharing said cycle. The parameters that
are configurable by port are the ones shown in the table below. Whether one type or another is
chosen will depend on the equipment connected to each port. The information necessary to
correctly configure these parameters will be obtained from the control profile for the DNP3 unit.

By default, Zivergraph® enables the InterC0, InterC1 and InterC2 parameters, leaving the rest
disabled.

Table 6-3: Interrogation Cycle Parameters

Parameter Description
InterC0 If the value is different to 0, the type of interrogation is via the CLASS0 data request
message. If the value is 0, this interrogation does not take place.
InterC1 If the value is different to 0, the type of interrogation is via the CLASS1 data
request message. If the value is 0, this interrogation does not take place.
InterC2 If the value is different to 0, the type of interrogation is via the CLASS2 data
request message. If the value is 0, this interrogation does not take place.
InterC3 If the value is different to 0, the type of interrogation is via the CLASS3 data
request message. If the value is 0, this interrogation does not take place.
InterBI If the value is different to 0, the type of interrogation is via the Binary Input
request message. If the value is 0, this interrogation does not take place.
InterBIC If the value is different to 0, the type of interrogation is via the Binary Input
Change request message. If the value is 0, this interrogation does not take
place.
InterAI If the value is different to 0, the type of interrogation is via the Analog Input
request message. If the value is 0, this interrogation does not take place.
InterAIC If the value is different to 0, the type of interrogation is via the Analog Input
Change request message. If the value is 0, this interrogation does not take
place.
HUSC1 If the value is different to 0, unsolicited messages are enabled for Class1
data. If the value is 0, this enabling does not take place.
HUSC2 If the value is different to 0, unsolicited messages are enabled for Class2
data. If the value is 0, this enabling does not take place.
HUSC3 If the value is different to 0, unsolicited messages are enabled for Class3
data. If the value is 0, this enabling does not take place.

M1CPTA2005I
6-25 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Fields InterC0 to InterAIC (Inter# in generic mode), accept a complex configuration to allow for
different interrogation modes. There are two interrogation cycles in the 1CPT: Refresh and
Changes. The first mode (included in the periodic Cycle, CF. 6.4.2.a) has a configurable period
through IntervRefrescoSen setting, and the second mode is included in the Continuous Cycle.
Each of the above fields controls which request is used in each cycle. Depending on the values
assigned to each field, said requests will be associated to one or both cycles. These fields will
be construed as bits fields. The value 0 means that said request is not used.

Protocol DNP3 allows, among others, two device interrogation forms: one generic, in that the
device particular data are associated to generic data: CLASS0 for static data and CLASS1,
CLASS2 and CLASS3 for changes in data. And other form in which master interrogates about
specific data: Binary Input (BI) and Analog Input (AI) for static data and Binary Input Change
(BIAC) and Analog Input Change (AIC) for change in data.

In the 1CPT every request can be associated with one or both cycles by assigning different
values to different fields. For compatibility with older devices, there exist three possibilities:
Standard Interrogation (INT_STANDARD=1), in the Refresh cycle (INT_REFRESCO=2) or in
the Change cycle (INT_CAMBIOS=4). The value to be configured for the different above-
mentioned Inter# parameters will be given by the combination, through the OR function, of the
relevant interrogation cycles.

In the Standard mode, CLASS0, Binary Input (BI) and Analog Input (AI) requests are associated
to the Refresh cycle; and CLASS1, CLASS2, CLASS3, Binary Input Change (BIAC) and Analog
Input Change (AIC) requests are associated to the Change cycle. In order to be able to activate
these interrogation modes the applicable fields will be assigned the value 1. This is the
compatibility mode with old devices that must be used by default.

If requests are to be mixed in different cycles, another bit in said field must be “activated”. Thus,
for example, if master is to interrogate for Class 0 both in the refresh cycle and change cycle,
InterC0 must be set to 5 (INT_STANDARD | INT_CAMBIOS). If master is to interrogate for
Changes in Binary Inputs both in the change cycle and the refresh cycle, InterBIC must be set
to 3 (INT_STANDARD | INT_REFRESCO).

The HUSCx parameters are used to indicate that spontaneous data sending is used by the
equipment at that port, instead of polling the 1CPT; the latter only performs periodic status
interrogation. If spontaneous data is used, the polling cycle should not be used: InterC1,
InterC2, InterC3, InterBIC and InterAIC.

M1CPTA2005I
1CPT: Substation Central Unit 6-26
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.2.b Communication Times

The DNP3 protocol is divided into layers or levels that are independent from each other. As it is
a protocol that adds many control bytes and checksums to the data, it can be implemented in
several ways, although one is recommended in order to improve refresh times. In the link layer,
messages can be sent with confirmation (SEND/CONFIRM function) or without it
(SEND/NO_REPLY function). ZIV has chosen this last method in order to improve refresh times
however, if the IED requests confirmation in its messages, the 1CPT sends the applicable
message.
In the configuration file, the times and parameters referring to the link layer (Level 2) have been
maintained for compatibility reasons, although they are not used. The ones that are used are
the ones affecting the application layer (Level 7). There is one exception, and this is that during
initialization of the unit, the first message that is sent is a link layer initialization message. This
message corresponds to the Reset Remote Link procedure (SEND/CONFIRM function). This
procedure involves a link layer response from the equipment. The time waited for the arrival of
this message is given by the L2ConfWaitTime parameter (in the DNP3MS.CFG file).

For all other messages, no response is expected at the link level, because there is none;
however, there should be one at the application level. If a unit does not respond to a message
sent by the 1CPT before a certain (configurable) amount of time has elapsed, given by the
Maximum delay time for application level response parameter (in Zivergraph®; in the
DNP3MS.CFG file, L7ConfWaitTime), the 1CPT tries to resend it a number of times given by
the Number of retries at the application level parameter (in DNP3MS.CFG, NumRetriesL7). If
it does not respond to any of these retries, an internal signal is generated from virtual unit 257,
indicating a communications failure with that unit, and the 1CPT goes on to the next unit. This
time should be on the order of several seconds, because if the unit's configuration is large, or if
several queries are strung together in the interrogation cycle (several active InterCx or InterBIC
and InterAIC activated), the time it takes the data sent by a unit to reach the 1CPT's application
layer is on this order; thus, this fact must be taken into account.

When it is once again the turn of the unit with the communications failure, the initialization
procedure is used instead of the procedure that cause the failure.

After a broadcast message (message directed to all units at one port), you should wait a while
so that the equipment can process said message before sending another message. There is a
configuration parameter (BrdcstMsgDel in the DNP3MS.CFG file) which indicates in
milliseconds how long the next query should be delayed to the next unit. This time is general
and is applied to all ports with DNP 3 equipment.

M1CPTA2005I
6-27 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.2.c Device Signals

The 1CPT interrogates devices for available signals. Protocol DNP3 allows to request the
information in a specific form, however, the 1CPT does not use it, but requests the information
in generic form, the way to send said information being decided by the IED. If there should be
disagreement between the forms supported by the 1CPT and the forms sent by the IED, this
must be solved changing the IED configuration, if possible, or requesting a 1CPT firmware
modification to be able to support said form.

Data supported by the 1CPT are shown in the table encl.

Table 6-4: Data supported by the 1CPT

Group Num Var Num Description
1 1 Binary Input – Packed format
1 2 Binary Input – With flags
2 1 Binary Input Event – Without time
2 2 Binary Input Event – With absolute time
2 3 Binary Input Event – With relative time
10 1 Binary Output – Output status Packed format
10 2 Binary Output – Output status with flags
20 1 Counter – 32-bit with flag
20 2 Counter – 16-bit with flag
20 5 Counter – 32-bit without flag
20 6 Counter – 16-bit without flag
21 1 Frozen Counter – 32-bit with flag
21 2 Frozen Counter – 16-bit with flag
21 9 Frozen Counter – 32-bit without flag
21 10 Frozen Counter – 16-bit without flag
30 0 Analog Input – Any Variation
30 1 Analog Input – 32-bit with flag
30 2 Analog Input – 16-bit with flag
30 3 Analog Input – 32-bit without flag
30 4 Analog Input – 16-bit without flag
32 2 Analog Input Event – 16-bit without time
32 4 Analog Input Event – 16-bit with time
40 1 Analog Output Status – 32-bit with flag
40 2 Analog Output Status – 16-bit with flag
40 3 Single-precision, floating-point with flag
40 4 Double-precision, floating-point with flag

M1CPTA2005I
1CPT: Substation Central Unit 6-28
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.3 IEC103
The IEC 870-5-103 protocol is a European communications standard for protection equipment.
This protocol is included on some 1CPT models. Although a standard protocol is involved, many
data have been “coded” in its private part, so there are several different implementations
depending on the manufacturer. This is why the configuration profile of every device is required
in order to be integrated into the 1CPT.

Equipment with the IEC103 protocol is configured as normal equipment using Zivergraph® or
the DBASE.CFG file. This equipment can only be connected at fiber optic ports.

For units with the PROCOME and DNP3 protocol, their data is directly assigned to the 1CPT's
internal data. For equipment with the IEC103 protocol, data types must be converted, because
this protocol is specifically for protection and the 1CPT uses control data. This assignment is
performed with the IEC103MS.CFG file.

Protocol IEC103 is a Master-Slave protocol in which the 1CPT acts as master and the relay as
slave. The interrogation mode conforms to the mode in section 6.4.2.a, it being worth
highlighting that in the continuous cycle, the interrogation is for Class 2 data and if the device
returns that it has Class 1 data with bit ACD, they are requested.

The General Interrogation procedure for IEC103 devices usually requires a long time for
completion, so a parameter is defined in the 1CPT, which controls the way the procedure is
carried out:

- RepCiclosIG: Consecutive repetitions during the general interrogation cycle. The General
Interrogation can be very long, so that segregation between the various devices is
recommended. The number of questions sent to a device in each part is given by this
parameter, the value of which varies between 2 and 100, taking 6 as default value. In
case it is configured to -1, the general interrogation will be fully executed for one device
before going on the next.
Note: For devices other than Siemens, configuring this parameter to -1 is recommended.

When information is requested from the device, it could be some time before it is available to be
sent to the master. During this time the device replies with a NAK message. There are two
generic parameters of the protocol implementation into the 1CPT, affecting all devices, that
control said time. They must be configured for the most unfavourable case.

- MaxReintNakMandos: After sending a command, the device normally takes some time to
send a reply, during which it replies with NAK messages. This parameter defines the
maximum number of times the NAK message is received before the command procedure
is deemed failed. Values vary from 3 to 200, taking 5 as default value. For AREVA P132
devices, this parameter must be configured with a high value: 30.

- MaxReintNakGI: This parameter has a meaning similar to the above, but it is used in the
General Interrogation procedure. If this maximum number of NAKs is reached during a
General Interrogation, next device will be interrogated, but next cycle the outstanding GI
for the relay in progress will be taken again. Values vary from 3 to 200, taking 5 as default
value. In case it is configured to -1, next device will not be interrogated until the General
Interrogation of the current device is completed.

M1CPTA2005I
6-29 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

On the other hand, there exist other parameters for each specific device, which control,
somehow, the interrogation mode.

- TipoReset: It denotes the type of RESET message sent to the device: 0=ResetCU and
1=ResetFCB (Endesa). Default value is 0.
- TipoReintento: It denotes the way to carry out attempts on communications failure:
0=Consecutive attempts, 1=Attempts per cycle (Endesa). Default value is 0.
- TipoCiclo: It denotes the type of cycle to be used to retrieve device data:
0=RequestDataClass2, 1=RequestDataClass1 (Endesa). Default value is 0.
- TipoRecuperaError: It denotes the method used to recover the device from error status.
Value 0 denotes that the interrogation is repeated the number of times configured, every
cycle turn. Value 1 (Endesa) denotes that, in case the communication with the device
fails, the interrogation cycle is cancelled for one minute, after which its recovery is
attempted. This procedure is carried out because SIEMENS devices take one minute to
recover after a cold start.

6.6.4 SPABUS
This protocol is included on some 1CPT models. Equipment with this protocol is configured with
an additional file named SPABUSMS.CFG. This equipment can only be connected to a COM-X
serial port.

In this case, the information provided by the equipment must be transformed. The task that
communicates with this equipment is responsible for making this conversion. To do this, it uses
the configuration file called MODULSPA.CFG. This file indicates what data will be collected
from each of the units, and how it will be mapped in the 1CPT’s internal configuration.

All of the equipment with this protocol will be connected to the same port. This means that, if a
large number of units is connected, the interrogation cycle will be slow.

M1CPTA2005I
1CPT: Substation Central Unit 6-30
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.5 MODBUS RTU

The MODBUS RTU protocol is a de facto communications standard for protection and control
equipment. It was initially developed to communicate with control equipment in industrial
environments (PLC’s), but it has spread and is now used for protection as well as control. This
protocol is included on some 1CPT models. Information can be found in www.modbus.org

With this protocol, data must be converted from the MODBUS format to the 1CPT’s format. The
data required to integrate MODBUS equipment into the 1CPT are in the MODBUSMS.CFG file.

The MODBUS protocol was designed for transferring simple data: digital signals and 16 or 32
bit records. The procedures and functions for data collection are well documented in the
protocol specification.

However, records can be considered as table cells in which more complex data can be stored:
settings, events, reports, etc. After all, this is a drawback from the integration point of view
because manufacturers arrange said data in the most convenient form and, as a general rule,
they are different from each other. In view of the foregoing, the MODBUS profile of the devices
to be connected to the 1CPT must be known in order to be able to analyse whether the 1CPT
will be able to interpret device available data.

1CPT can integrate devices from different manufacturers, taking into account the features of
each device.

6.6.6 IEC61850
Standard IEC61850 defines the substation communications bus, mainly to define:

- Which data are available and how to name and describe them.
- How data are accessed and interchanged between the different devices.
- How to connect the different elements to the communications networks.

One of the benefits worth mentioning of IEC61850 is to avoid the loss of context suffered by
data transmitted using standard communications protocols (DNP3.0, etc).

When a standard protocol is used data to be transmitted must be arranged within the applicable
protocol format, making use of a method to establish which data go into each message so as to
be able to use it correctly by the receiver. However, IEC61850 segregates data into groups,
these at the same time into classes and finally data are mapped into a given logic device within
a physical element. Each IEC61850 element gains access to data, without loss of context,
through a tree formed by the different data classifications.

On the one hand, the 1CPT incorporates standard IEC-61850 at substation bus level through
the communications protocol MMS and, on the other hand, makes use of IEC-61850 data
model to shape its own internal functions.

1CPT IEC61850 module is broken down into:

- IEC61850 Client.
- IEC-61850 Server.

M1CPTA2005I
6-31 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.6.6.a IEC61850 Client

The IEC-61850 client is in charge of establishing the link to each IED configured in the 1CPT
from their IP addresses. Available 1CPT IEC61850 Client services are as follows:

- Subscribe and configure Buffered type Report-Control-Blocks of an IEC61850 server.

- Subscribe and configure Unbuffered type Report-Control-Blocks of an IEC61850 server.
- Command execution of controllable IED elements, according to the IEC61850 control
model Direct-Operate with normal reliability and enhanced reliability.
- Read analog and binary counter type data of an IED.
- Check periodically parameterisation and configuration attributes of each IED logic device.
- Gain access to an IED SCL-Control-Block to validate and activate a new configuration file
(file CID) in the IED.

IEC61850 protocol devices are configured the same than normal devices within the
Zivergraph or in file dbase.cfg. These devices can be connected to any of two 1CPT Ethernet
ports (LAN1 and LAN2). The information required to map IED IEC61850 data model into the
1CPT internal database is generated via the Zivergraphutility for IEDs IEC61850 integration
into the Central Unit. Mapping information of this type of IEDs will be incorporated into a file
.CFG specific for each IED that will be named the same as the IED. Finally, the Zivergraph
generates for the current substation the file 61850cli.cfg that includes the list of IEDs linked to
the 1CPT.

6.6.6.b IEC61850 Server

The 1CPT IEC61850 server uses IEC61850 data to shape at logic level the 1CPT internal
functions that have to be visible by other substation IEDs. The 1CPT IEC61850 server features
the following elements and services:

- A logic device that includes a number of logic nodes to show data of interest for other
IEDs.
- Capacity to subscribe to GOOSE-Control-Blocks of other substation IEDs to receive
GOOSE messages.
- Capacity to publish GOOSE messages, from GOOSE-Control-Blocks.
- Capacity to publish Buffered type Reports, from Report-Control-Blocks.
- Capacity to publish Unbuffered type Reports, from Report-Control-Blocks.
- Capacity to accept commands from other IEDs on IEC61850 controllable data.

Although 1CPT IEC61850 server data model is configured during the programming stage,
settings can be introduced through the 1CPT configuration file 61850srv.cfg. GOOSE message
settings to which the 1CPT is subscribed and GOOSE message settings published by the 1CPT
will be configured through the file iecgoose.ini.

M1CPTA2005I
1CPT: Substation Central Unit 6-32
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.7 Level 3 Protocols

The information that the database collects from the substation equipment (virtual or real) is
available to be used by other systems, internal or external. Depending on the client and on the
geographic area where the installation is located, a certain communications protocol is used to
transfer this information to level 3 systems.

The different protocols emulated by the 1CPT to communicate with Level 3 or Level 2
equipment are the following:

1. DNP3. (Available with serial interfaces RS232 and TCP/IP).

2. CEI-870-5-101, Iberdrola and Coelba Profile (Cei101i). (It can communicate through a
Terminal Server).
3. CEI-870-5-101 and CEI-870-5-104, Endesa Profile. (Cei101b).
4. CEI-870-5-101, Electropaz Profile. (Cei101a).
5. CEI-870-5-101, CERJ/AMPLA Profile. (CEI101C).
6. CEI-870-5-101/104, Iberdrola Profile. (C101104I).
7. MODBUS RTU: Serial, TCP and TCP/IP. (It can communicate through a Terminal
Server).

The operating principle of these emulators is similar in all cases. The emulation task collects the
information from the 1CPT internal database and adapts it to the data format of the remote
control SCADA or level 2 SCADA linked to the 1CPT. When the SCADA interrogates the 1CPT,
the latter responds with a message with the data requested.

In order to perform the required conversation, a configuration file indicating how this conversion
shall be done is needed. The name of the file depends on the protocol to be emulated; however,
in general, its name will relate to the name of the protocol. This file will contain the data
necessary for the emulator, which is customized for each substation.

The files have a generic structure. Firstly, there is a block with general equipment-related
parameters. Next, the parameters necessary to adapt the information to the format expected by
the remote command are configured. This will generally consist of a table in which the name of
the remote command signal appears on one side, with the name of the 1CPT signal on the
other. The type and number of signals supported depend on the type of protocol in question.

M1CPTA2005I
6-33 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8 Control Functions

The 1CPT can perform control functions at the substation level, encompassing operations on all
of the substation equipment. If the control function is simple, it can be performed through the
logic program.

For more complex control functions, specific code modules are implemented, which are
executed as an independent task and will be associated to a set of device input signals, a set of
internal signals and commands, a set of device output signals and device settings.

6.8.1 Detection of Resistive Grounds

This control function is responsible for determining the origin of a resistive ground problem on
medium voltage lines. An external device generates an alarm, indicating that resistive grounds
have been detected, but it does not indicate on which line they have been detected. The control
function determines which line has caused the alarm.

The control function requires some configuration data, such as the number of breakers, their
priority, detection times, etc. The 1CPT allows up to four independent control functions,
depending on the topology of the substation. This data is configured through the Zivergraph©
software, and the control function’s task gets the data from the tierr_x.cfg file (where x indicates
the control function module, i = 1, 2, 3, 4).

The detection method is by means of consecutively opening all of the breakers configured. After
each one is opened, there is a configurable delay in order to determine whether the alarm
disappears. If it disappears, the breaker remains open and an event is generated, indicating the
line on which the problem occurred; if, on the other hand, the alarm does not disappear, that
breaker is closed and the next one on the list is opened. If the origin of the alarm cannot be
determined by the end of the entire process, the status returns to default and an event
indicating “stopped without detection” is generated.

When there are several modules of the control function for grounds, they can be coordinated so
that they behave as a single unit when the coupling circuit breaker for both buses is closed, and
as two separate modules when it is open.

The information below refers to the control function applied to a single module; however, it can
be extended to several control functions, duplicating the settings, signals, etc.

In the configuration of the substation, there is an In Service parameter (AJ_R_SERV). When it

takes value 1, the control function for resistive grounds is ready to operate, and an In service
signal is activated (R_SERV). When it takes value 0, the control function is Out of service.

The control function may be activated / deactivated from three different locations:

1. From the central unit’s console.

2. From remote control.
3. From the coupling IED (activate / deactivate function 64).

M1CPTA2005I
1CPT: Substation Central Unit 6-34
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Whatever the origin of the activation of the control function, it causes the ACT signal to take the
value 1. Deactivating the control function causes it to take the value 0.

A priority of between 1 and 50 is defined for each of the IEDs, bearing in mind the fact that there
cannot be two IEDs with the same priority. The priorities need not be consecutive; in other
words, there may be unassigned priority indexes.

Henceforth, it will be assumed that the priority indexes are consecutive, i.e., that the actual
index setting has been transformed to facilitate the operation of the control function.

6.8.1.a Contact Inputs

The input signals to the control function are the following:

Table 6-5: Resistive Ground Contact Inputs

Signal Description
ACT Activation of the Control Function
ALARMA Resistive Ground alarm
INT(n)_A Breaker (n) Open
F(n)_OA Failure (n) of Open Command
F(n)_OC Failure (n) of Close Command

The index (n) indicates the priority number assigned to each breaker.

6.8.1.b Contact Outputs

The output signals of the control function are the following:

Table 6-6: Resistive Ground Contact Inputs

Signal Description
R_SERV Control Function in Service
ARR Control Function Picked Up
BLQ Control Function Blocked
OA(n) Open Command on Breaker (n)
OC(n) Close Command on Breaker (n)
ODACT64 Desactivate 64 Command

The index (n) indicates the priority number assigned to each breaker.

6.8.1.c Settings
The control function’s settings are the following:

Table 6-7: Resistive Ground Settings

Setting Description Margin Unit Step Default
AJ_T_ALA Pickup delay time 0 - 600 s 1 60
AJ_T_COM Verification time 0 - 10 s 1 5
AJ_PRIxx Set priority of IED (xx) 1 - 50 1
SERxx IED (xx) in service YES - NO YES

M1CPTA2005I
6-35 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.1.d Status Flow Chart

The flow chart of the control function’s status is shown below.

Figure 6.7 Control Function Status Flow Chart.

M1CPTA2005I
1CPT: Substation Central Unit 6-36
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

In the diagram above, 1 represents the open / closed condition of a breaker in the module
corresponding to the control function. The open / closed status may be detected as a change in
the open breaker signal [INT(n)_A].

In the diagram above, 2 represents the open condition of a breaker in the module
corresponding to the control function, excluding the one over which the control function is
sending commands at that moment or the closing of any of the breakers, including that one. The
open / closed status may be detected as a change in the open breaker signal [INT(n)_A].

In the diagram above, 3 represents the closed condition of a breaker in the module
corresponding to the control function, excluding the one over which the control function is
sending commands at that moment or the opening of any of the breakers, including that one.
The open / closed status may be detected as a change in the open breaker signal [INT(n)_A].

6.8.1.e Operation
The automaton is initialized with the ARR variable with value 0 and n variable with value 1, in
the E_REPOSO (default condition) status.

It exits the default status when the activation of the following function takes place:

ALARMA x ACT = 1[1]

When it exits the default status, the value 1 is given to the ARR signal and it goes to
E_T_ALAR status. In this status, a timer with the setting AJ_T_ALAR starts up.

- If function [1] is reset while timing is taking place, the automaton goes into E_REPOSO
status, after giving the ARR signal a value of 0.
- If the opening or closing of any of the breakers associated with the control function is
detected (condition 1 ), the automaton goes to E_BLQ status and gives a value of 1 to
the BLQ signal.
- In either of the above two cases, the timer stops.
- If T_OUT is detected, indicating that the timer has stopped counting, the E_T_ALAR
status is exited.
- If the SER setting associated with the breaker is NO, the index goes up, and this action
is repeated until an index whose breaker has the SER setting at YES is reached. Once
this point has been reached, signal INT(n)_A is verified to see whether it is inactive,
indicating that the breaker is closed. If this is the case, an open command will be given,
and the status will change to E_ESPERA_A. If this signal is inactive, indicating that the
breaker is already open, the index will go up by one unit and the verifications of SER
and INT(n)_A will be repeated.

In the E_ESPERA_A status, nothing happens; this is a waiting period to see whether the open
command that was issued is obeyed or fails.

- If the opening of any of the breakers associated with the control function is detected,
other than the one on which the manoeuvre is taking place, or if the closing of any of
them, including the one in question, is detected (condition 2 ), the automaton goes to
E_BLQ status and gives a value of 1 to the BLQ signal.
- If the failure of open command signal [F(n)_OA] is detected for the breaker on which the
manoeuvre is taking place, the automaton goes to E_BLQ status and gives a value of 1
to the BLQ signal.
- If the open breaker signal [INT(n)_A] is detected for the breaker on which the
manoeuvre is taking place, the automaton goes to E_T_COM status.

M1CPTA2005I
6-37 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

In E_T_COM status, the automaton starts up a timer with the setting AJ_T_COM.

- If, while in this status, the drop of the ALARMA signal is detected, the ARR signal is
deactivated, a signal that a ground has been detected on line(n) is generated, and
E_REPOSO status is entered.
- If the opening or closing of any of the breakers associated with the control function is
detected (condition 1 ), the automaton goes to E_BLQ status and gives a value of 1 to
the BLQ signal.
- If T_OUT is detected, indicating that the timer has stopping counting, the E_T_COM
status is exited, a close command is given for the breaker and E_ESPERA_C status is
entered.

In the E_ESPERA_C status, nothing happens; this is a waiting period to see whether the close
command that was issued is obeyed or fails.

- If the closing of any of the breakers associated with the control function is detected,
other than the one on which the manoeuvre is taking place, or if the opening of any of
them, including the one in question, is detected (condition 3 ), the automaton goes to
E_BLQ status and gives a value of 1 to the BLQ signal.
- If the failure of close command signal [F(n)_OC] is detected for the breaker on which
the manoeuvre is taking place, the automaton goes to E_BLQ status and gives a value
of 1 to the BLQ signal.
- If the closed breaker signal [INT(n)_C] is detected, verification is made of whether the
end has been reached, i.e., the last breaker in the sequence. If this is the case, the
automaton goes to E_BLQ status and gives a value of 1 to the BLQ signal. Otherwise,
the index goes up by one unit and the automaton goes on to the next breaker.

6.8.1.f Reset
When the ALARMA1 signal takes the value 0, the control function will exit blocked status and
will go to E_REPOSO status.

6.8.1.g Own Signals

The control function for resistive grounds has 8 fixed, consecutive digital signals, with indexes
ranging from ISC 0 to ISC 7. These signals are the following:

Table 6-8: Resistive Ground Signals

ISC Nº Description
0 Control function module 1 in service
1 Control function module 1 active
2 Pickup of control function model 1
3 Control function stopped with no detection / Blocked
4 Cycle has ended without detecting origin of the fault
5 Spare
6 Spare
7 Control function module 1 setting error

From signal 8 onwards, the “Ground detected on line(n)” signals are mapped; these are
configurable and depend on the number of bays in the bus.

M1CPTA2005I
1CPT: Substation Central Unit 6-38
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2 H Control Function

The H control function involves automatically resetting the voltage in high voltage buses when it
disappears for some unexpected reason. This control function works in substations where the
high voltage part has an H-shaped topology. This control function is not included in all 1CPT
software models.

This control function is made up of several subautomata that perform simpler tasks. These
subautomata are:

- Voltage presence / absence control function. This is responsible for determining whether
or not voltage is present in each of the elements involved: high voltage lines and medium
voltage buses.
- Control function for the definition of high voltage statuses. This processes the information
generated by the aforementioned control functions and determines the different statuses
that the high voltage pair may have.
- Control function for high voltage manoeuvres. If any of the operating conditions are met, it
performs the appropriate manoeuvres to reset the voltage in the bus where it was lost.
- Control function for medium voltage manoeuvres. This control function acts on the high
voltage lines when there is a loss of voltage in the medium voltage buses.
- Control function for switching due to protection tripping. If the loss of voltage is caused by
a protection tripping, this control function safely resets the voltage.

There is an In service setting (AJ_H_SERV). When it takes the value 1, the above control
functions will operate, and an IN SERVICE signal (H_SERV) will be activated. When it takes the
value 0, the control functions will be out of service.

The control function may be in manual or automatic mode. In manual mode, it does not operate,
and behaves as if it were out of service. In automatic mode, there are up to three modes of
operation, depending on the preference given to each line. We can supply power to the buses
through one line (Preference A), through the other (Preference B) or each bus through its
respective line (Preference AB).

Operating preferences for the control function are selected through the operating console, or
from the remote control office via the appropriate protocol. However, the selection of a
preference is made, it causes the signal associated with that preference to take the value 1,
while all the rest take the value 0, according to the table below:

Table 6-9: H Control Function Operating Preferences

Signal
P_A P_B P_AB MAN
Selection PREF_A 1 0 0 0
PREF_B 0 1 0 0
PREF_AB 0 0 1 0
MAN 0 0 0 1

During normal operation, the control functions may become blocked. Said blocking causes all
switching modules (high and medium voltage manoeuvres and switching because of
protection tripping) to simultaneously become blocked. A reset command takes them out of
this condition. This command is the same for all control functions, so if they are blocked, they
will all be reset at the same time.

M1CPTA2005I
6-39 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.a Voltage Presence / Absence Control Functions

There is a control function for each of the voltages involved in the operation of the H control
function. They all have identical structures; only the measuring signals, the settings that
determine their evolution and the outputs they provide vary.

Each of the automata has an output that indicates the presence or absence of the controlled
voltage.

The measuring inputs and logic outputs are the following:

Table 6-10: Voltage Presence / Absence Control Functions Measuring Inputs

and Logic Outputs
Automaton Measure Output provided by the automaton
1a MULA ULA
1b MULB ULB
1c MUA04 UA
MUA08
MUA48
1d MUB04 UB
MUB08
MUB48

The origin of all of these measurements is configurable and are defined according to the
installation.

Each of the control functions has a voltage presence setting, and another voltage absence
setting, as well as presence time and absence time settings. The margins for each of them are
indicated below; they are the same for all voltages.

Table 6-11: Voltage Presence / Absence Control Functions Settings Margins

Setting Description Margin Unit Step Default
AJ_PRES Presence level 50 - 100 % de Vnom 0.1 80%
AJ_AUSEN Absence level 0 - 70 % de Vnom 0.1 50%
AJ_T_PRES Presence time 0.5 - 5 s 0.1 1
AJ_T_AUSEN Absence time 0.5 - 5 s 0.1 1

The outputs for the control function were defined in Table 6-10.

M1CPTA2005I
1CPT: Substation Central Unit 6-40
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Operation
With regard to the figure describing the control function's operation, the following statuses have
been defined:

E_AUS_V:Voltage absence status

E_PRES_V:Voltage presence status
E_T_AUS:Counting absence time status
E_T_PRES:Counting presence time status

At the start, the control

function will be taken
to E_AUS_V status,
with the output signal
value being U=0.
When the variable
measured exceeds the
value of the AJ_PRES
setting, its status
changes to
E_T_PRES, in which a
counter with the
AJ_T_PRES setting
will start up.

Figure 6.8 Voltage Presence / Absence Control Function.

In the case of automata 1c and 1d, their status changes from E_AUS_V when the three
voltages used in their operation exceed the threshold value set.

The E_T_PRES status will change either when the variable measured drops below
0.95xAJ_PRES (in the case of automata 1c and 1d, it will be when any voltage drops below
0.95xAJ_PRES), or when the timer times out; in the former case, the status will return to
E_AUS_V and in the latter, it will go to E_PRES_V.

When the status goes to E_PRES_V, U will equal 1. When the variable measured drops below
the value of the AJ_AUS setting, the status changes to E_T_AUS, in which a counter with the
AJ_T_AUS setting will start up.

In the case of automata 1c and 1d, their status changes from E_PRES_V when any of the three
voltages used in their operation is lower than the threshold value set.

The E_T_AUS status will change either when the variable measured exceeds the value of
1.05xAJ_AUS (in the case of automata 1c and 1d, it will be when all of the voltages exceed the
value of 1.05xAJ_AUS), or when the timer times out; in the former case, the status will return to
E_PRES_V and in the latter, it will go to E_AUS_V.

When the status goes to E_AUS_V, U will equal 0.

M1CPTA2005I
6-41 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.b Control Function for the Definition of High Voltage Status

This control function uses some of the output signals of the preceding one to define the status
of the high voltage pair.

The inputs to this control function are the following:

Table 6-12: Definition of High Voltage Status Control Function Inputs

Input Description
ULA Presence of voltage on Line A
ULB Presence of voltage on Line B

The settings used by this control function are the following:

Table 6-13: Definition of High Voltage Status Control Function Settings

Setting Description Margin Unit Step Default
AJ_T_EST Stability time 0 - 300 s 0.1 60
AJ_T_CONM Switch time 0 - 10 s 0.1 5
P_T_ESP Equality delay time Fixed s Fixed 1

The last setting is not, strictly speaking, a setting, but a system parameter, with a fixed value of
1 second.

The outputs provided by this control function are:

Table 6-14: Definition of High Voltage Status Control Function Outputs

Input Description
S_00 Absence of both voltages
S_01 Absence of voltage on line A and presence on line B
S_10 Presence of voltage on line A and absence on line B
S_11 Presence of voltage on both lines

• Operation
With regard to the figure describing the control function's operation, the following statuses have
been defined:

E_00: no voltage on either line.

E_01: ready to switch with voltage on line B and no voltage on line A.
E_10: ready to switch with voltage on line A and no voltage on line B.
E_11: ready to switch with voltage on both lines.
E_ESP(01): status with no voltage on line A, waiting for voltage drop on line B.
E_ESP(10): status with no voltage on line B, waiting for voltage drop on line A.
E_ESP_EST: counting stability time.
E_CONM(01): counting switch time with voltage on line B and no voltage on line A.
E_CONM(10): counting switch time with voltage on line A and no voltage on line B.
E_BLQ_X: blocked by the AUT_ACT signal.

At the start, the control function will be taken to E_00 status, with the output S_00 at 1 and all
others at 0.

M1CPTA2005I
1CPT: Substation Central Unit 6-42
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The status flow chart can be seen in the figure below. The flow is prompted by the changes in
the ULA, ULB and AUT_ACT signals. When it is indicated that a signal must take a value of 1
when a certain status is reached, it is understood that all the others must go to 0.

In the E_ESP_(XX) statuses, a timer with a value of P_T_ESP starts up.

In the E_ESP_EST status, a timer with a value of AJ_T_ESP starts up.

In the E_CONM(XX) statuses, a timer with a value of AJ_T_CONM starts up.

In all transitions, the AUT_ACT signal should be at 1. If AUT_ACT=0 were to occur in any
status, a transition to E_BLQ status would take place (not shown in the diagram); the latter is a
non-operating status, which would change automatically once the AUC_ACT signal was
activated.

The AUT_ACT signal is generated through a programmable logic function of some of the
database signals.

Figure 6.9 Control Function for the Definition of High Voltage Statuses.

M1CPTA2005I
6-43 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.c Control Function for High Voltage Manoeuvres

In response to the start event, this control function executes a sequence of manoeuvres which
end back in the E_REPOSO (default) status, or in a E_BLQ (blocked) status if any manoeuvre
in the sequence fails.

The sequence of manoeuvres is determined by the values of a set of signals, as defined further
on.

The event that starts the sequence, taking the automaton from the default status, is any one of
those listed below:

- The change in value of any of the CLOSED BREAKER signals of any of the H breakers
(or what amounts to the same thing, if any of the OPEN BREAKER or CLOSED
BREAKER signals change to 1).
- The change in value of any of the automaton’s output signals for high voltage statuses.
- The change in value of the CONTROL FUNCTION CONDITION ACTIVE signal
(AUT_ACT).
- The modification of any preference.
- The resetting of either of the 86s (86A=0 or 86B=0).

The input signals to the control function are the following:

Table 6-15: High Voltage Manoeuvres Control Function Inputs

Input Description
52LA_C Breaker 52LA closed
52LA_A Breaker 52LA open
52LB_C Breaker 52LB closed
52LB_A Breaker 52LB open
52LAB_C Breaker 52LAB closed
52LAB_A Breaker 52LAB open
AUT_ACT Control function condition active
S_00 Absence of voltage on both lines
S_01 Absence of voltage on line A and presence on line B
S_10 Presence of voltage on line A and absence on line B
S_11 Presence of voltage on both lines
P_A Preference A
P_B Preference B
P_AB Preference AB
MAN Manual
MED_ACT Medium voltage control function activated
86TA_ACT Trip 86A
86TB_ACT Trip 86B

M1CPTA2005I
1CPT: Substation Central Unit 6-44
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Each signal’s index is configurable and will be determined for each substation.

At the start, the control function executes the sequence selection logic; once this has been
done, it can go to default, carry out a sequence of manoeuvres or go to blocked if any
command fails or finds no sequence to be executed.

After the pickup event, a 3 s. timer starts up for coordination with the control function for
switching because of protection tripping; once the timer has finished, the sequence to be
executed is selected.

Sequence selection, whether at the start or after a pickup event, is done according to the table
below.

In this table, the MED_ACT signal comes from the medium voltage control function, and the
way it is generated is described further on. It is used in calculating the sequence to be selected:
if this signal has a value of 1, the control function remains in the default status.

If either of the two 86s (signals 86TA and 86TB to 1) trips, this control function for high voltage
manoeuvres is prevented from operating, as if these signals are activated, the control function
for switching because of protection tripping is the one that should operate.

The automaton changes to non-operating status if the AUT_ACT signal is inactive. It

automatically changes from this status if either of the following conditions occurs:

- If the AUT_ACT signal is activated, with its status changing to default (E_REPOSO).
- If the control function is blocked, with its status changing to blocked (E_BLQ).
If the control function for medium voltage manoeuvres or the one for switching because of
protection tripping is blocked, this control function for high voltage manoeuvres will also be
blocked. To change the status from blocked, it will be necessary to reset the control function.

M1CPTA2005I
6-45 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-16: High Voltage Manoeuvres Control Function Sequence Selection

52LA_C 52LAB_C 52LB_C S_00 S_01 S_10 S_11 P_A P_B P_AB MAN 86TA 86TB MED_ACT AUT_ACT SEQ
X X X X X X X X X X X X X X 0 Default
X X X X X X X 0 0 0 1 X X X 1 Default
X X X X X X X X X X X X X 1 1 Default
0 0 1 0 0 0 1 1 0 0 0 0 0 0 1 16
0 0 1 0 0 0 1 0 1 0 0 0 0 0 1 2
0 0 1 0 0 0 1 0 0 1 0 0 0 0 1 3
0 0 1 0 0 1 0 X X X 0 0 0 0 1 1
0 0 1 0 1 0 0 X X X 0 0 0 0 1 2
0 0 1 1 0 0 0 X X X 0 0 0 0 1 Default
1 0 0 0 0 0 1 1 0 0 0 0 0 0 1 2
1 0 0 0 0 0 1 0 1 0 0 0 0 0 1 17
1 0 0 0 0 0 1 0 0 1 0 0 0 0 1 5
1 0 0 0 0 1 0 X X X 0 0 0 0 1 2
1 0 0 0 1 0 0 X X X 0 0 0 0 1 4
1 0 0 1 0 0 0 X X X 0 0 0 0 1 Default
1 0 1 0 0 0 1 1 0 0 0 0 0 0 1 6
1 0 1 0 0 0 1 0 1 0 0 0 0 0 1 7
1 0 1 0 0 0 1 0 0 1 0 0 0 0 1 Default
1 0 1 0 0 1 0 X X X 0 0 0 0 1 8
1 0 1 0 1 0 0 X X X 0 0 0 0 1 9
1 0 1 1 0 0 0 X X X 0 0 0 0 1 Default
1 1 0 0 0 0 1 1 0 0 0 0 0 0 1 Default
1 1 0 0 0 0 1 0 1 0 0 0 0 0 1 10
1 1 0 0 0 0 1 0 0 1 0 0 0 0 1 11
1 1 0 0 0 1 0 X X X 0 0 0 0 1 Default
1 1 0 0 1 0 0 X X X 0 0 0 0 1 12
1 1 0 1 0 0 0 X X X 0 0 0 0 1 Default
0 1 1 0 0 0 1 1 0 0 0 0 0 0 1 13
0 1 1 0 0 0 1 0 1 0 0 0 0 0 1 Default
1 0 1 1 0 0 0 X X X 0 0 0 0 1 Default
1 0 1 1 0 0 0 X X X 0 0 0 0 1 Default
1 1 0 0 0 0 1 1 0 0 0 0 0 0 1 Default
1 1 0 0 0 0 1 0 1 0 0 0 0 0 1 10
1 1 0 0 0 0 1 0 0 1 0 0 0 0 1 11
1 1 0 0 0 1 0 X X X 0 0 0 0 1 Default
1 1 0 0 1 0 0 X X X 0 0 0 0 1 12
1 1 0 1 0 0 0 X X X 0 0 0 0 1 Default
0 1 1 0 0 0 1 1 0 0 0 0 0 0 1 13
0 1 1 0 0 0 1 0 1 0 0 0 0 0 1 Default
0 1 1 0 0 0 1 0 0 1 0 0 0 0 1 14
0 1 1 0 0 1 0 X X X 0 0 0 0 1 15
0 1 1 0 1 0 0 X X X 0 0 0 0 1 Default
0 1 1 1 0 0 0 X X X 0 0 0 0 1 Default
0 0 0 0 0 0 1 1 0 0 0 0 0 0 1 16
0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 17
0 0 0 0 0 0 1 0 0 1 0 0 0 0 1 18
0 0 0 0 0 1 0 X X X 0 0 0 0 1 16

M1CPTA2005I
1CPT: Substation Central Unit 6-46
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6.16: High Voltage Manoeuvres Control Function Sequence Selection

52LA_C 52LAB_C 52LB_C S_00 S_01 S_10 S_11 P_A P_B P_AB MAN 86TA 86TB MED_ACT AUT_ACT SEQ
0 0 0 0 1 0 0 X X X 0 0 0 0 1 17
0 0 0 1 0 0 0 X X X 0 0 0 0 1 Default
1 1 1 0 0 0 1 1 0 0 0 0 0 0 1 1
1 1 1 0 0 0 1 0 1 0 0 0 0 0 1 4
1 1 1 0 0 0 1 0 0 1 0 0 0 0 1 19
1 1 1 0 0 1 0 X X X 0 0 0 0 1 1
1 1 1 0 1 0 0 X X X 0 0 0 0 1 4
1 1 1 1 0 0 0 X X X 0 0 0 0 1 19
0 1 0 0 0 0 1 1 0 0 0 0 0 0 1 3
0 1 0 0 0 0 1 0 1 0 0 0 0 0 1 5
0 1 0 0 0 0 1 0 0 1 0 0 0 0 1 20
0 1 0 0 0 1 0 X X X 0 0 0 0 1 3
0 1 0 0 1 0 0 X X X 0 0 0 0 1 5
0 1 0 1 0 0 0 X X X 0 0 0 0 1 Default
X X X X X X X X X X X 1 X 0 1 Default
X X X X X X X X X X X X 1 0 1 Default

In the preceding table, when DEFAULT appears in the SEQ column, it refers to sequence 0.

The operations to be performed in each of the sequences are the following:

Table 6-17: Operations of each Sequence

SEQ nº Operations
0 Default
1 Open 52LB
2 Close 52LAB
3 Close 52LA
4 Open 52LA
5 Close 52LB
6 Close 52LAB and open 52LB
7 Close 52LAB and open 52LA
8 Open 52LB and close 52LAB
9 Open 52LA and close 52LAB
10 Close 52LB and open 52LA
11 Close 52LB and open 52LAB
12 Open 52LA and close 52LB
13 Close 52LA and open 52LB
14 Close 52LA and open 52LAB
15 Open 52LB and close 52LA
16 Close 52LA and close 52LAB
17 Close 52LB and close 52LAB
18 Close 52LA and close 52LB
19 Open 52LAB
20 Close 52LA and close 52LB and open 52LAB
21 Put control function in Manual

Each of these commands is configurable, because although the sequences are fixed, the
equipment and its configuration depend on each substation.

M1CPTA2005I
6-47 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Execution of sequences
Each sequence of manoeuvres is made up of a number of elementary manoeuvres. The
manoeuvres are executed one after another: the next one is executed only after the previous
one has been fully completed.

If the AUT_ACT signal is found to be inactive prior to the execution of a sequence, the
sequence is interrupted and the status changes to non-operating. When this signal is once
again activated, the status changes to default (E_REPOSO).

If a manoeuvre in the sequence fails, the sequence is interrupted and the control function goes
to blocked (E_BLQ) status. The control function must be reset so that it can once again
operate.

After the execution of the last manoeuvre in the sequence, the sequence automaton stays in
default (E-REPOSO) status.

Figure 6.10 Execution of Sequences.

The procedure for the execution of sequences is shown in the accompanying diagram. There
are two settings associated with this procedure that determine whether a delay should be
included between two consecutive commands in the same sequence. These settings are:

Table 6-18: High Voltage Manoeuvres Control Function Settings

Setting Description Margin Unit Step Default
AJ_PERM_RET Enable delay 0-1 BOOL - 1
AJ_RETARDO Command delay time 100 - 65535 miliseg 1 500

When the automaton specific to the manoeuvre to be executed is entered, the command
indicated in the table of manoeuvres is sent, and the status then changes to waiting
(E_ESPERA). This status is changed by the activation of the manoeuvre failure signal or by
completing the manoeuvre. In the former case, the status changes to blocked (E_BLQ), and in
the latter, it goes on to execute the next manoeuvre, if any, or returns to the default
(E_REPOSO) status, if there are no other manoeuvres.

M1CPTA2005I
1CPT: Substation Central Unit 6-48
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.11 Manoeuvre Execution Procedure.

6.8.2.d Control Function for Medium Voltage Manoeuvres

This control function is responsible for switching lines if it detects a loss of voltage in the
medium voltage buses. There is a MEDIUM VOLTAGE CONTROL FUNCTION IN SERVICE
setting (AJ_M_SERV). When it takes the value 1, the control function described in this heading
operates and a MEDIUM VOLTAGE CONTROL FUNCTION IN SERVICE (M_SERV) signal is
activated. When it takes the value 0, the control function is out of service. This control function
uses the following as input signals:

Table 6-19: Medium Voltage Manoeuvres Control Function Inputs

Input Description
UA Presence / absence of voltage on A buses
UB Presence / absence of voltage on B buses
ULA Presence / absence of voltage on line A
ULB Presence / absence of voltage on line B
52LA_C Breaker 52LA closed
52LB_C Breaker 52LB closed
52LAB_C Breaker 52LAB closed
52TA_C Line A transformer breaker closed
52TB_C Line B transformer breaker closed
52B12_C Breaker between bus 1 and 2 closed
MAN Manual
AUT_ACT Control function condition active

It has the following settings:

Table 6-20: Medium Voltage Manoeuvres Control Function Settings

Setting Description Margin Unit Step Default
AJ_T_M Medium voltage switch time 0 - 10 s 0.1 5

M1CPTA2005I
6-49 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

At the start, the control function executes the sequence selection logic, causing the MED_ACT
signal to take the value 0. Once this has been done, it can go to default (E_REPOSO) or carry
out a sequence of manoeuvres.

From the default (E_REPOSO) status, the trip event (that causes the control function to exit its
default (E_REPOSO) status) is the change in any UA or UB signal from 1 to 0, or the activation
of the AUT_ACT signal, in which case the control function will exit non-operating status.

Figure 6.12 Sequence of Medium Voltage Manoeuvres.

Once the control function is no longer in its default (E_REPOSO) status, the sequence of
manoeuvres is decided, the same as in the control function for high voltage manoeuvres.

Once the sequence is selected, and before proceeding to execute it, a timer with the value
AJ_T_M is started. While the timing is taking place, the automaton remains in E_T_M status.
When the timeout takes place, this status changes; however, before it goes into the next one,
the continuity of the switching conditions is checked (sequence chosen). If the response is
negative, a new sequence is chosen and once again it goes to timing status (E_T_M); if it is
affirmative, the sequence of manoeuvres is executed.

Both in the case of a failure in any manoeuvre in the sequence or successful execution, the
automaton’s status changes to blocked (E_BLQ), causing the MED_ACT signal to take the
value 1 to indicate that the medium voltage control function has operated.

The blocked (E_BLQ) status can only be exited if a reset (REP) command is received; this
command makes the automaton go into its default (E_REPOSO) status.

M1CPTA2005I
1CPT: Substation Central Unit 6-50
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The automaton will change to non-operating status if the AUT_ACT signal is inactive. It will
automatically exit this status if any of the following conditions occurs:

- If the AUT_ACT signal is activated, with its status changing to default (E_REPOSO).
- If the automaton for medium voltage manoeuvres is taken out of service from the
console, with its status changing to out of service.
- If the control function is blocked, with its status changing to blocked (E_BLQ).

If the control function for high voltage manoeuvres or the one for switching because of
protection tripping is blocked, this control function for medium voltage manoeuvres will also be
blocked. To exit this blocked status, it will be necessary to reset the control function.
• Selection of sequences
The selection of the sequence of manoeuvres to be executed takes place according to the
following table. The numbers indicating the sequence of operations refer to the table of
sequences defined for the control function for high voltage manoeuvres.

The destinations of the commands issued for manoeuvres are the same as the ones in the table
defined for the control function for high voltage.

Table 6-21: Medium Voltage Manoeuvres Control Function Sequence Selection

52LA_C 52LB_C 52LAB_C 52TA_C 52TB-C 52B12_C UA UB ULA ULB MAN AUT_ACT SEQ
1 0 1 1 X 1 0 0 1 1 0 1
1 0 1 1 0 0 0 X 1 1 0 1 10
1 0 1 1 1 0 0 0 1 1 0 1
0 1 1 X 1 1 0 0 1 1 0 1
0 1 1 0 1 0 X 0 1 1 0 1 13
0 1 1 1 1 0 0 0 1 1 0 1
1 1 0 1 0 0 0 X 1 1 0 1 7
1 1 0 1 1 0 0 1 1 1 0 1
1 1 0 0 1 0 X 0 1 1 0 1 6
1 1 0 1 1 0 1 0 1 1 0 1
X X X X X X X X X X 1 1 Default
X X X X X X X X X X X 0 Default
1 0 1 1 X 1 0 0 1 1 0 1
1 0 1 1 0 0 0 X 1 1 0 1 10
1 0 1 1 1 0 0 0 1 1 0 1
0 1 1 X 1 1 0 0 1 1 0 1

M1CPTA2005I
6-51 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.e Control Function for Switching due to Protection Tripping

This control function switches the lines when a loss of voltage situation arises when protection
has tripped. The input signals it uses are the following:

Table 6-22: Switching due to Protection Tripping Control Function Inputs

Input Description
ULA Presence / absence of voltage on line A
ULB Presence / absence of voltage on line B
52LA_C Breaker 52LA closed
52LB_C Breaker 52LB closed
52LAB_C Breaker 52LAB closed
86TA_ACT Trip 86A
86TB_ACT Trip 86B
MAN Manual
DISP_DEF Definitive trip
AUT_ACT Control function condition active

The start event occurs whenever any of the 52LA_C, 52LB_C or 52LAB_C signals are
deactivated, or any of the 86TA_ACT, 86TB_ACT, ULA, ULB, DISP_DEF or AUT_ACT signals
are activated.

The start event starts up a 3-second timer; after this timer runs, it checks to see whether the two
86s have tripped simultaneously, in which case it goes to MAN (manual) and the status
changes to default. Otherwise, a manoeuvre is selected, according to the table below:

Table 6-23: Switching due to Protection Tripping Control Function Maneouvre

Selection
52LA_C 52LB_C 52LAB_C 86TA 86TB ULA ULB DISP_DEF MAN AUT_ACT SEQ
X X X X X X X X 1 1 Default
X X X X X X X 1 0 1 21
0 0 0 1 0 X 1 0 0 1 5
0 0 0 0 1 1 X 0 0 1 3
1 0 0 0 1 1 X 0 0 1 21
0 1 0 1 0 X 1 0 0 1 21
X X X X X X X X X 0 Default

If none of the combinations from the table above are met, no sequence is selected and the
automaton's status changes to default (E_REPOSO).

Once the manoeuvre has been executed, the preferences take the value indicated in the
accompanying diagram and the automaton remains in its default condition (E_REPOSO) in
manual (MAN) status. If the execution of the manoeuvre fails, the system will be blocked, and
this situation can only be exit by means of a reset (REP) command.

M1CPTA2005I
1CPT: Substation Central Unit 6-52
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.13 Sequence of Switching because of Protection Tripping.

The automaton changes to non-operating status if the AUT_ACT signal is inactive. It

automatically exits this status if either of the following conditions occurs:

- If the AUT_ACT signal is activated, with its status changing to default (E_REPOSO).
- If the control function is blocked, with its status changing to blocked (E_BLQ).

If the control function for high or medium voltage manoeuvres is blocked, this one for switching
because of protection tripping will also be blocked. To exit this blocked (E_BLQ) status, it will
be necessary to reset the control function.

M1CPTA2005I
6-53 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.f Own Digital Signals

The H control function, as a logic equipment, has its own digital signals which may be used by
the other tasks.

The digital signals provided by this control function are the following.

Table 6-24: H Control Function Digital Signals

Number Signal
0 High Volt. Cont. Func. For Pres./Abs. of Voltage A
1 High Volt. Cont. Func. For Pres./Abs. of Voltage A
2 Absence of Both Voltages
3 Absence of Volt. on A and Pres. on B
4 Presence of Volt. on A and Volt. on B
5 Presence on Both Lines
6 Cont. Func. For High Voltage Maneouvers Blocked
7 Control Function in Manual Mode
8 Preference A
9 Preference B
10 Preference AB
11 Medium Voltage Control Function Activated
12 Med. Volt. Cont. Func. for Pres./Abs. of Voltage A
13 Med. Volt. Cont. Func. for Pres./Abs. of Voltage B
14 Med. Volt. Control Function in Service
15 Medium Voltage Control Function Blocked
16 Cont. Func. for Trip Conditions Blocked
17 Loss of UA Voltage
18 Loss of UB Voltage
19 Loss of ULA Voltage
20 Loss of ULB Voltage
21 Spare 21 (isc_86TA)
22 Spare 22 (isc_86TB)
23 ISC_A_UNO
24 ISC_A_CERO
25 Control Function Blocked
26 Command Failure
27 Spare 27

M1CPTA2005I
1CPT: Substation Central Unit 6-54
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.g Own Commands

The H control function has 14 commands, as follows:

Table 6-25: H Control Function Commands

Number Command
0 Preference A from panel
1 Preference B from panel
2 Preference AB from panel
3 Manual from panel
4 Control function reset command (from panel)
5 Preference A from remote control
6 Preference B from remote control
7 Preference AB from remote control
8 Manual from remote control
9 Spare 9
10 Preference A from control function
11 Preference B from control function
12 Preference AB from control function
13 Manual from control function

M1CPTA2005I
6-55 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.2.h External Signals

In order to function properly, the H control function uses signals that report on the status of the
substation. As some of these signals depend on the installation, they are not fixed, but
configurable. However, the meaning related to each signal is fixed, and these meanings are
shown in the table below:

Table 6-26: H Control Function External Signals

Signal Meaning
0. 52LA Closed Line A breaker closed
1. 52LAB Closed Breaker between lines A and B closed (not used)
2. 52LB Closed Line B breaker closed
3. S_00 Absence of voltage on lines A and B
4. S_01 Absence of voltage on line A and presence on line B
5. S_10 Presence of voltage on line A and absence on line B
6. S_11 Presence of voltage on lines A and B
7. P_A Preference A
8. P_B Preference B
9. P_AB Preference AB
10. MAN Control function in manual mode
11. MED_ACT Medium voltage control function activated
12. AUT_ACT Authorization for operation
13. 52TA Closed Line A transformer breaker closed
14. 52TB Closed Line B transformer breaker closed
15. 52B12 Closed Breaker between bus 1 and 2 closed
16. UA Voltage on bus A
17. UB Voltage on bus B
18. 86TA Tripping in A transformer
19. 86TB Tripping in B transformer (not used)
20. ULA Voltage on line A
21. ULB Voltage on line B
22. DISP_DEF Final trip

M1CPTA2005I
1CPT: Substation Central Unit 6-56
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3 H2 Control Function

The H2 control function involves automatically resetting the voltage in high voltage buses when
it disappears for some unexpected reason. This control function works in substations where the
high voltage part has an H-shaped topology. This control function is not included in all 1CPT
software models.

This control function is made up of several subautomata that perform simpler tasks. These
subautomata are:

- Voltage presence / absence control function. This is responsible for determining whether
or not voltage is present in each of high voltage lines.
- Control function for the definition of high voltage statuses. This processes the information
generated by the aforementioned control functions and determines the different statuses
that the high voltage pair may have.
- Control function for high voltage manoeuvres. If any of the operating conditions are met, it
performs the appropriate manoeuvres to reset the voltage in the bus where it was lost.
- Control function for switching due to protection tripping. If the loss of voltage is caused by
a protection tripping, this control function safely resets the voltage.

There is an In service setting (AJ_H_SERV). When it takes the value 1, the above control
functions will operate, and an IN SERVICE signal (H_SERV) will be activated. When it takes the
value 0, the control functions will be out of service.

The control function may be in manual or automatic mode. In manual mode, it does not operate,
and behaves as if it were out of service. In automatic mode, there are up to three modes of
operation, depending on the preference given to each line. We can supply power to the buses
through the line 1 (Preference 1), through the line 2 (Preference 2) or each bus through its
respective line (Preference 1-2).

Operating preferences for the control function are selected through the operating console, or
from the remote control office via the appropriate protocol. However, the selection of a
preference is made, it causes the signal associated with that preference to take the value 1, and
the value 0 for all the others, according to the following table:

Table 6-27: H2 Control Function Operating Preferences

Signal
P_1 P_2 P_1-2 MAN
Selection PREF_1 1 0 0 0
PREF_2 0 1 0 0
PREF_1-2 0 0 1 0
MAN 0 0 0 1

During normal operation, the control functions may become blocked. Said blocking causes all
switching modules (high and medium voltage manoeuvres and switching because of
protection tripping) to simultaneously become blocked. A reset command takes them out of
this condition. This command is the same for all control functions, so if they are blocked, they
will all be reset at the same time.

M1CPTA2005I
6-57 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.a Line Voltage Presence / Absence Control Functions

There is a control function for each of the voltages involved in the operation of the H2 control
function. They all have identical structures; only the measuring signals, the settings that
determine their evolution and the outputs they provide vary.

Each of the automata has an output that indicates the presence or absence of the controlled
voltage.

The measuring inputs and logic outputs are the following:

Table 6-28:Voltage Presence / Absence Control Functions Measuring Inputs and Logic
Outputs
Automaton Measure Output provided by the automaton
1a MUL1 ULA
1b MUL2 ULB

The origin of all of these measurements is configurable and are defined according to the
installation.

Each of the two control functions has a voltage presence setting, and another voltage absence
setting, as well as presence time and absence time settings. The margins for each of them are
indicated below; they are the same for all voltages.

Table 6-29:Voltage Presence / Absence Control Functions Settings Margins

Setting Description Margin Unit Step Default
AJ_PRES Presence level 50 - 100 % de VNom 0.1 80%
AJ_AUSEN Absence level 0 - 70 % de VNom 0.1 50%
AJ_T_PRES Presence time 0.5 - 5 s 0.1 1
AJ_T_AUSEN Absence time 0.5 - 5 s 0.1 1

The outputs for the control function were defined in Table 6-32.

M1CPTA2005I
1CPT: Substation Central Unit 6-58
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Operation
With regard to the figure describing the control function's operation, the following statuses have
been defined:

E_AUS_V:Voltage absence status

E_PRES_V:Voltage presence status
E_T_AUS:Counting absence time status
E_T_PRES:Counting presence time status

At the start, the control

function will be taken
to E_AUS_V status,
with the output signal
value being U=0.
When the variable
measured exceeds the
value of the AJ_PRES
setting, its status
changes to
E_T_PRES, in which a
counter with the
AJ_T_PRES setting
will start up.

Figure 6.14 Voltage Presence / Absence Control Function.

The E_T_PRES status will change either when the variable measured drops below
0.95xAJ_PRES or when the timer times out; in the former case, the status will return to
E_AUS_V and in the latter, it will go to E_PRES_V.

When the status goes to E_PRES_V, U will equal 1. When the variable measured drops below
the value of the AJ_AUS setting, the status changes to E_T_AUS, in which a counter with the
AJ_T_AUS setting will start up.

The E_T_AUS status will change either when the variable measured exceeds the value of
1.05xAJ_AUS or when the timer times out; in the former case, the status will return to
E_PRES_V and in the latter, it will go to E_AUS_V.

When the status goes to E_AUS_V, U will equal 0.

M1CPTA2005I
6-59 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.b Control Function for the Definition of High Voltage Status

This control function uses some of the output signals of the preceding one to define the status
of the high voltage pair.

The inputs to this control function are the following:

Table 6-30:Definition of High Voltage Status Control Function Inputs

Input Description
ULA Presence of voltage on Line 1
ULB Presence of voltage on Line 2

The settings used by this control function are the following:

Table 6-31: Definition of High Voltage Status Control Function Settings

Setting Description Margin Unit Step Default
AJ_T_EST Stability time 0 - 300 s 0.1 60
AJ_T_CONM Switch time 0 - 10 s 0.1 5
P_T_ESP Equality delay time Fixed s Fixed 1

The last setting is not, strictly speaking, a setting, but a system parameter, with a fixed value of
1 second.

The outputs provided by this control function are:

Table 6-32: Definition of High Voltage Status Control Function Outputs

Input Description
S_00 Absence of both voltages
S_01 Absence of voltage on line 1 and presence on line 2
S_10 Presence of voltage on line 1 and absence on line 2
S_11 Presence of voltage on both lines

• Operation
With regard to the figure describing the control function's operation, the following statuses have
been defined:

E_00: no voltage on either line.

E_01: ready to switch with voltage on line 2 and no voltage on line 1.
E_10: ready to switch with voltage on line 1 and no voltage on line 2.
E_11: ready to switch with voltage on both lines.
E_ESP(01): status with no voltage on line 1, waiting for voltage drop on line 2.
E_ESP(10): status with no voltage on line 2, waiting for voltage drop on line 1.
E_ESP_EST: counting stability time.
E_CONM(01): counting switch time with voltage on line 2 and no voltage on line 1.
E_CONM(10): counting switch time with voltage on line 1 and no voltage on line 2.
E_BLQ_X: blocked by the AUT_ACT signal.

At the start, the control function will be taken to E_00 status, with the output S_00 at 1 and all
others at 0.

The status flow chart can be seen in the figure below. The flow is prompted by the changes in
the ULA, ULB and AUT_ACT signals. When it is indicated that a signal must take a value of 1
when a certain status is reached, it is understood that all the others must go to 0.

M1CPTA2005I
1CPT: Substation Central Unit 6-60
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

In the E_ESP_(XX) statuses, a timer with a value of P_T_ESP starts up.

In the E_ESP_EST status, a timer with a value of AJ_T_ESP starts up.

In the E_CONM(XX) statuses, a timer with a value of AJ_T_CONM starts up.

In all transitions, the AUT_ACT signal should be at 1. If AUT_ACT=0 were to occur in any
status, a transition to E_BLQ status would take place (not shown in the diagram); the latter is a
non-operating status, which would change automatically once the AUC_ACT signal was
activated.

The AUT_ACT signal is generated through a programmable logic function of some of the
database signals.

START

Figure 6.15 Control Function for the Definition of High Voltage Statuses.

M1CPTA2005I
6-61 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.c Control Function for High Voltage Manoeuvres

In response to the start event, this control function executes a sequence of manoeuvres which
end back in the E_REPOSO (default) status, or in a E_BLQ (blocked) status if any manoeuvre
in the sequence fails.

The sequence of manoeuvres is determined by the values of a set of signals, as defined further
on.

The event that starts the sequence, taking the automaton from the default status, is any one of
those listed below:

- The change in value of any of the CLOSED BREAKER signals of any of the H breakers
(or what amounts to the same thing, if any of the OPEN BREAKER or CLOSED
BREAKER signals change to 1).
- The change in value of any of the automaton’s output signals for high voltage statuses.
- The change in value of the CONTROL FUNCTION CONDITION ACTIVE signal
(AUT_ACT).
- The modification of any preference.
- Resetting any of the 86 trips (86A=0 or 86B=0) or the bus differential trips (DFB1=0 or
DFB2=0).

The input signals to the control function are the following:

Table 6-33: High Voltage Manoeuvres Control Function Inputs

Input Description
52LA_C Breaker 52L1 closed
52LA_A Breaker 52L1 open
52LB_C Breaker 52L2 closed
52LB_A Breaker 52L2 open
52LAB_C Breaker 52L12 closed
52LAB_A Breaker 52L12 open
AUT_ACT Control function condition active
S_00 Absence of voltage on both lines
S_01 Absence of voltage on line 1 and presence on line 2
S_10 Presence of voltage on line 1 and absence on line 2
S_11 Presence of voltage on both lines
P_A Preference 1
P_B Preference 2
P_AB Preference 12
MAN Manual
86TA_ACT Trip 86A
86TB_ACT Trip 86B

Each signal’s index is configurable and will be determined for each substation.

In the initial stage (E_INIT), the state of the actuation signal of the automation (AUT_ACT) will
be evaluated, and in case it is deactivated, it will go to the non-actuation state
(E_NO_ACTUAC) to remain there until this signal is activated again. During this period, the
automatism will be deactivated. After the signal is activated, it will go directly to the blocking
state (E_BLOQUEO) to force the automatism to be reset in order to return to the normal
situation.

M1CPTA2005I
1CPT: Substation Central Unit 6-62
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

From this initial stage, the control function executes the sequence selection logic; once this has
been done, it can go to default, carry out a sequence of manoeuvres or go to blocked if any
command fails or finds no sequence to be executed.

After these checks, and after a wait of 3 seconds for coordination with the other control function,
it is changed to the "command sequence evaluation status" (E_EVAL_SEQ), where the first
command sequence evaluation to be executed will be performed. After it, it will reach the
"default status" (E_REPOSO) if there is no command to be executed, or execute the
corresponding maneuver sequence. If this execution is correct, it will go to the "default status",
but if the execution itself fails, it will go to the "blocking status" (E_BLOQUEO).

Once the "default status" is reached, the control function will remain there, until the activation of
the "trigger event" that announces the arrival of changes in the input signals involved in the
control function, going back to the "sequence evaluation status".

In this table, the trip of any of the two 86 (signals 86TA and 86TB to 1) prevents the activation of
this high voltage manoeuvres control function, as if these signals are activated, the control
function for switching because of protection tripping is the one that should operate.

If the control function for switching due to protection tripping is blocked, this control function for
high voltage manoeuvres will also be blocked. To change the status from blocked, it will be
necessary to reset the control function.

The selection of command sequences to be executed is described in the table below, and it can
be seen that each command sequence in the table (except the so-called "default" which has no
associated maneuver) has a specific time of execution of the command, which may be one of
the following, these being configured in the configuration file:

- Maneuver time (T_MANIO).

- Switching time (T_CONMUTA).
- Normalization time (T_NORMAL).
- Coupling time (T_ACOPL).

M1CPTA2005I
6-63 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-34: High Voltage Manoeuvres Control Function Sequence Selection

CLOSED BREAKER TL2 TL1 PREFERENCE
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
X X X X X X X X X X X X X 0 DEFAULT
X X X X X X X 0 0 0 1 X X 1 DEFAULT
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
0 0 0 1 0 0 0 1 0 0 0 0 0 1 DEFAULT
0 0 0 1 1 0 0 0 0 0 1 CLOSE-52 L1 T_MANIO
0 0 0 1 1 0 0 0 0 0 1 CLOSE-52 L2 T_MANIO
0 0 0 1 1 0 0 0 0 0 1 CLOSE-52 L1 T_MANIO
1 0 0 1 1 0 0 0 0 0 1 DEFAULT
1 0 0 1 1 0 0 0 0 0 1 CLOSE-52 L3 T_MANIO
1 0 0 1 1 0 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 0 0 1 1 0 0 0 0 0 1 CLOSE-52 L3 T_MANIO
0 0 1 1 1 0 0 0 0 0 1 DEFAULT
0 0 1 1 1 0 0 0 0 0 1 OPEN-52 L2 T_CONMUT
0 0 1 1 1 0 0 0 0 0 1 CLOSE-52 L3 T_MANIO
0 0 1 1 1 0 0 0 0 0 1 CLOSE-52 L1 T_MANIO
1 0 1 1 1 0 0 0 0 0 1 DEFAULT
1 0 1 1 1 0 0 0 0 0 1 OPEN-52 L2 T_CONMUT
1 0 1 1 1 0 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 0 1 1 1 0 0 0 0 0 1 CLOSE-52 L3 T_MANIO
0 1 0 1 1 0 0 0 0 0 1 DEFAULT
0 1 0 1 1 0 0 0 0 0 1 CLOSE-52 L1 T_MANIO
0 1 0 1 1 0 0 0 0 0 1 CLOSE-52 L2 T_MANIO
0 1 0 1 1 0 0 0 0 0 1 CLOSE-52 L1 T_MANIO
1 1 0 1 1 0 0 0 0 0 1 DEFAULT
1 1 0 1 1 0 0 0 0 0 1 DEFAULT
1 1 0 1 1 0 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 1 0 1 1 0 0 0 0 0 1 DEFAULT
0 1 1 1 1 0 0 0 0 0 1 DEFAULT
0 1 1 1 1 0 0 0 0 0 1 OPEN-52 L2 T_CONMUT
0 1 1 1 1 0 0 0 0 0 1 DEFAULT
0 1 1 1 1 0 0 0 0 0 1 CERRAR-52 L1 T_NORMAL
1 1 1 1 1 0 0 0 0 0 1 OPEN-52 L3 T_ACOPL
1 1 1 1 1 0 0 0 0 0 1 OPEN-52 L2 T_MANIO
1 1 1 1 1 0 0 0 0 0 1 OPEN-52 L1 T_MANIO
1 1 1 1 1 0 0 0 0 0 1 OPEN-52 L2 T_MANIO
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
0 0 0 1 0 1 0 0 0 0 1 DEFAULT
0 0 0 1 0 1 0 0 0 0 1 CLOSE-52 L1 T_MANIO
0 0 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_MANIO
0 0 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_MANIO
1 0 0 1 0 1 0 0 0 0 1 DEFAULT
1 0 0 1 0 1 0 0 0 0 1 CLOSE-52 L3 T_MANIO

M1CPTA2005I
1CPT: Substation Central Unit 6-64
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-34: High Voltage Manoeuvres Control Function Sequence Selection

CLOSED BREAKER TL2 TL1 PREFERENCE
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
1 0 0 1 0 1 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 0 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_MANIO
0 0 1 1 0 1 0 0 0 0 1 DEFAULT
0 0 1 1 0 1 0 0 0 0 1 OPEN-52 L2 T_CONMUT
0 0 1 1 0 1 0 0 0 0 1 CLOSE-52 L3 T_MANIO
0 0 1 1 0 1 0 0 0 0 1 CLOSE-52 L3 T_MANIO
1 0 1 1 0 1 0 0 0 0 1 DEFAULT
1 0 1 1 0 1 0 0 0 0 1 OPEN-52 L2 T_CONMUT
1 0 1 1 0 1 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 0 1 1 0 1 0 0 0 0 1 CLOSE-52 L3 T_MANIO
0 1 0 1 0 1 0 0 0 0 1 DEFAULT
0 1 0 1 0 1 0 0 0 0 1 CLOSE-52 L1 T_CONMUT
0 1 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_MANIO
0 1 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_MANIO
1 1 0 1 0 1 0 0 0 0 1 DEFAULT
1 1 0 1 0 1 0 0 0 0 1 DEFAULT
1 1 0 1 0 1 0 0 0 0 1 OPEN-52 L1 T_CONMUT
1 1 0 1 0 1 0 0 0 0 1 CLOSE-52 L2 T_NORMAL
0 1 1 1 0 1 0 0 0 0 1 DEFAULT
0 1 1 1 0 1 0 0 0 0 1 OPEN-52 L2 T_CONMUT
0 1 1 1 0 1 0 0 0 0 1 DEFAULT
0 1 1 1 0 1 0 0 0 0 1 DEFAULT
1 1 1 1 0 1 0 0 0 0 1 OPEN-52 L3 T_ACOPL
1 1 1 1 0 1 0 0 0 0 1 OPEN-52 L2 T_MANIO
1 1 1 1 0 1 0 0 0 0 1 OPEN-52 L1 T_MANIO
1 1 1 1 0 1 0 0 0 0 1 OPEN-52 L1 T_MANIO
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
0 0 0 1 0 0 1 0 0 0 1 DEFAULT
0 0 0 1 0 0 1 0 0 0 1 CLOSE-52 L1 T_MANIO
0 0 0 1 0 0 1 0 0 0 1 CLOSE-52 L2 T_MANIO
0 0 0 1 0 0 1 0 0 0 1 CLOSE-52 L1 T_MANIO
1 0 0 1 0 0 1 0 0 0 1 DEFAULT
1 0 0 1 0 0 1 0 0 0 1 CLOSE-52 L3 T_CONMUT
1 0 0 1 0 0 1 0 0 0 1 OPEN-52 L1 T_CONMUT
1 0 0 1 0 0 1 0 0 0 1 CLOSE-52 L2 T_CONMUT
0 0 1 1 0 0 1 0 0 0 1 DEFAULT
0 0 1 1 0 0 1 0 0 0 1 OPEN-52 L2 T_CONMUT
0 0 1 1 0 0 1 0 0 0 1 CLOSE-52 L3 T_CONMUT
0 0 1 1 0 0 1 0 0 0 1 CLOSE-52 L1 T_CONMUT
1 0 1 1 0 0 1 0 0 0 1 DEFAULT
1 0 1 1 0 0 1 0 0 0 1 OPEN-52 L2 T_CONMUT
1 0 1 1 0 0 1 0 0 0 1 OPEN-52 L1 T_CONMUT

M1CPTA2005I
6-65 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Tabla 6-34: High Voltage Manoeuvres Control Function Sequence Selection

L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME
1 0 1 1 0 0 1 0 0 0 1 DEFAULT
0 1 0 1 0 0 1 0 0 0 1 DEFAULT
0 1 0 1 0 0 1 0 0 0 1 CLOSE-52 L1 T_MANIO
0 1 0 1 0 0 1 0 0 0 1 CLOSE-52 L2 T_MANIO
0 1 0 1 0 0 1 0 0 0 1 OPEN-52 L3 T_MANIO
1 1 0 1 0 0 1 0 0 0 1 DEFAULT
1 1 0 1 0 0 1 0 0 0 1 DEFAULT
1 1 0 1 0 0 1 0 0 0 1 OPEN-52 L1 T_CONMUT
1 1 0 1 0 0 1 0 0 0 1 CLOSE-52 L2 T_NORMAL
0 1 1 1 0 0 1 0 0 0 1 DEFAULT
0 1 1 1 0 0 1 0 0 0 1 OPEN-52 L2 T_CONMUT
0 1 1 1 0 0 1 0 0 0 1 DEFAULT
0 1 1 1 0 0 1 0 0 0 1 CLOSE-52 L1 T_NORMAL
1 1 1 1 0 0 1 0 0 0 1 OPEN-52 L3 T_ACOPL
1 1 1 1 0 0 1 0 0 0 1 OPEN-52 L2 T_MANIO
1 1 1 1 0 0 1 0 0 0 1 OPEN-52 L1 T_MANIO
1 1 1 1 0 0 1 0 0 0 1 OPEN-52 L3 T_MANIO
L1 L12 L2 S00 S01 S10 S11 P_A P_B P_AB MAN 86TA 86TB AUT_ACT COMMAND TIME

Each command to be carried out has a code, and it will also be configurable since, although the
purpose of them is fixed from the point of view of control function in general, the equipment and
its configurations will be different in each substation.

Table 6-35: Type of Commands

COMMAND NUMBER OPERATION EQUIPMENT SIGNAL
0 Default X X
1 Open 52L1 X X
2 Close 52L1 X X
3 Open 52L2 X X
4 Close 52L2 X X
5 Open 52L1-2 X X
6 Close 52L1-2 X X
7 Put control function in Manual X X

M1CPTA2005I
1CPT: Substation Central Unit 6-66
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Execution of the Command

Each selection of maneuver to be carried out in this control function consists of only one
maneuver described in the table above (as opposed to the H automation, in which some of
them are composed of two or three commands, which are executed one after the other, and in
which the execution of the next one is only carried out when the previous one has been totally
completed).

If before the execution of a command, it is detected the signal of AUT_ACT inactive, the
execution is interrupted and goes to a non-actuation status (E_NO_ACTUAC). In this status,
when this signal is activated again, it always goes to the blocking status.

Associated with the execution of the command, there are four time settings that can be
associated for each particular command, and that are delayed before the command is
performed. These settings are as follows:

Table 6-36: High Voltage Manoeuvres Control Function Settings

Setting Description Margin Unit Step Default
AJ_T_MANIO Manoeuvre Time, which is the time you 0 - 60000 ms 100 2000
wait before performing a maneuver in
such a way as to energize the high
voltage buses. It is also applied in
actions after preference changes or after
unblocking the control function.
AJ_T_CONMUTA Switching Time, which is the time you 0 - 60000 ms 100 3000
wait before launching a command to
perform a switching due to lack of
voltage.
AJ_T_NORMAL Normalization Time, which is the time 0 - 300000 ms 100 10000
you wait before normalizing your
situation due to the presence of voltage.
AJ_T_ACOPL Coupling Time, which is the time you 0 - 300000 ms 100 2000
wait before launching an open command
on the coupling breaker when the lines
are coupled.

If the execution of the command fails, the control function system will go to the blocking state
(E_BLOQUEO). It will stay there until the control function is reset, after which it will return to the
initial state (E_INIT), starting the cycle again.

If the execution of the command is correct, the control function will go to a default state and will
stay there until the arrival of new events indicated by a "trigger event" that make the possibility
of executing some command be evaluated again.

In the following diagram of the execution of the control function, the different stages already
mentioned are appreciated.

M1CPTA2005I
6-67 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 6. Description of Operation

Figure 6.16 Command Execution.

M1CPTA2005I
1CPT: Substation Central Unit 6-68
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.d Automatic Switching by Protection Trip

This control function monitors the possible triggering of the protections that protect the buses,
which can result in the loss of power to any of them. The purpose of this is to carry out a
switching operation that leaves the "healthy" bus fed so that it can continue to supply voltage. In
this kind of occasions, thecontrol function system should be switched to manual mode
automatically.

The possible cases of trip that can cause this behavior are the following:

- Relay 86 trip, due to the activation of the machine protections of one of the two
transformers. This only applies to the three breaker control function, given that in the five
breaker the transformer breaker is tripped without affecting the line or coupling breakers.
We will call these trips 86T1 and 86T2 in the table.
- Trip of the differential of one of the buses. Unlike the old version of the H control function,
in which it used the definitive trip generic signal, in this one we will use the specific trip
signals of the differential equipment of each of the buses. These trips will be called DFB1
and DFB2 in the table.

The execution methodology of this control function is similar to that of high voltage maneuvers
described above, so its state diagram is the same. In response to the start event, executes a
sequence of maneuvers, which end, always in case of correct performance, in the MANUAL
status. In case of failure of any maneuver will be passed to the BLOCKINGstatus.

The maneuver to be performed is determined by the values of a set of signals, as defined

below. The event that starts the sequence, taking the control function out of default state, is any
of the following:

- The change of value of any of the signals of CLOSED BREAKER (or what is the same
putting to 1 of any of the signals of OPEN BREAKER or CLOSED BREAKER) of any of
the breakers of the H.
- The change of value of any of the output signals of the High Voltage Manoeuvres Control
Function .
- The activation of any of the trips 86 (86A=0 or 86B=0) or the trips of the bus differential
(DFB1=0 or DFB2=0).
- The modification to any preference from the manual status.
- The change of value of the active control function condition signal (AUT_ACT).

M1CPTA2005I
6-69 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The input signals used by this control function are the following.

Table 6-37: Input Signals of the Protection Trip Switching Control Function
Input Description
52LA_CLOSED 52L1 Breaker Closed
52LB_CLOSED 52L2 Breaker Closed
52LAB_CLOSED 52L1-2 Breaker Closed
S_00 Voltage absence in both lines
S_01 Absence of voltage on line 1 and presence on line 2
S_10 Presence of voltage on line 1 and absence on line 2
S_11 Voltage presence in both lines
86T1_ACT Trafo 1 Trip 86A
86T2_ACT Trafo 2 Trip 86A
DIFF BUSES 1 Bus Differential 1 Trip
DIFF BUSES 2 Bus Differential 2 Trip
MAN Manual
AUT_ACT Control function condition active

Each signal’s index is configurable and will be determined for each substation.

In the initial stage (E_INIT), the state of the actuation signal of the automation (AUT_ACT) will
be evaluated, and in case it is deactivated, it will go to the non-actuation state
(E_NO_ACTUAC) to remain there until this signal is activated again. During this period, the
automatism will be deactivated. After the signal is activated, it will go directly to the blocking
state (E_BLOQUEO) to force the automatism to be reset in order to return to the normal
situation.

From that initial stage, the state of the other control function, the one of high voltage
maneuvers, will be checked, since if it was blocked, we would go directly to the blocking status,
since if one control function is blocked all the others are also blocked.

After these checks, and after a wait of 3 seconds for coordination with the other control function,
it is changed to the "command sequence evaluation status" (E_EVAL_SEQ), where the first
command sequence evaluation to be executed will be performed. After it, it will reach the
"default status" (E_REPOSO) if there is no command to be executed, or execute the
corresponding maneuver sequence. If this execution is correct, it will go to the "default status",
but if the execution itself fails, it will go to the "blocking status" (E_BLOQUEO).

Once the "default status" is reached, the control function will remain there, until the activation of
the "trigger event" that announces the arrival of changes in the input signals involved in the
control function, going back to the "sequence evaluation status".

The joint trigger of the two 86 (both signals 86TA and 86TB to 1) makes the control function go
directly to manual mode.

If the control function for switching due to protection tripping is blocked, this control function for
high voltage manoeuvres will also be blocked. To change the status from blocked, it will be
necessary to reset the control function.

The selection of command sequences to be executed is described in the table below. In all of
them, a wait is carried out before the execution itself, this time being the so-called “Maneuver
time” (T_MANIO).

M1CPTA2005I
1CPT: Substation Central Unit 6-70
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The manoeuvre selection table for this control function is as follows:

Table 6-38: Protection Trip Switching Control Function Command Selection

CLOSED BREAKER TL2 TL1

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

X X X X X X X X X X X X 0 -

X X X X X X X X X X X 1 1 -

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

0 0 0 1 0 0 0 1 0 0 0 0 1 MAN
0 0 0 1 0 0 0 0 1 0 0 0 1 MAN
0 0 0 1 0 0 0 0 0 1 0 0 1 MAN
0 0 0 1 0 0 0 0 0 0 1 0 1 MAN

0 0 0 0 0 1 0 1 0 0 0 0 1 MAN
0 0 0 0 0 1 0 0 1 0 0 0 1 MAN
0 0 0 0 0 1 0 0 0 1 0 0 1 CLOSE L1
0 0 0 0 0 1 0 0 0 0 1 0 1 CLOSE L1

0 0 0 0 1 0 0 1 0 0 0 0 1 CLOSE L2
0 0 0 0 1 0 0 0 1 0 0 0 1 CLOSE L2
0 0 0 0 1 0 0 0 0 1 0 0 1 MAN
0 0 0 0 1 0 0 0 0 0 1 0 1 MAN

0 0 0 0 0 0 1 1 0 0 0 0 1 CLOSE L2
0 0 0 0 0 0 1 0 1 0 0 0 1 CLOSE L2
0 0 0 0 0 0 1 0 0 1 0 0 1 CLOSE L1
0 0 0 0 0 0 1 0 0 0 1 0 1 CLOSE L1

L1 L1-2 L2 S00 S001 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

1 0 0 1 0 0 0 1 0 0 0 0 1 -
1 0 0 1 0 0 0 0 1 0 0 0 1 -
1 0 0 1 0 0 0 0 0 1 0 0 1 MAN
1 0 0 1 0 0 0 0 0 0 1 0 1 MAN

1 0 0 0 0 1 0 1 0 0 0 0 1 -
1 0 0 0 0 1 0 0 1 0 0 0 1 -
1 0 0 0 0 1 0 0 0 1 0 0 1 MAN
1 0 0 0 0 1 0 0 0 0 1 0 1 MAN

1 0 0 0 1 0 0 1 0 0 0 0 1 -
1 0 0 0 1 0 0 0 1 0 0 0 1 -
1 0 0 0 1 0 0 0 0 1 0 0 1 MAN
1 0 0 0 1 0 0 0 0 0 1 0 1 MAN

1 0 0 0 0 0 1 1 0 0 0 0 1 -
1 0 0 0 0 0 1 0 1 0 0 0 1 -
1 0 0 0 0 0 1 0 0 1 0 0 1 MAN
1 0 0 0 0 0 1 0 0 0 1 0 1 MAN

M1CPTA2005I
6-71 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-38: Protection Trip Switching Control Function Command Selection

CLOSED BREAKER TL2 TL1

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

0 0 1 1 0 0 0 1 0 0 0 0 1 MAN
0 0 1 1 0 0 0 0 1 0 0 0 1 MAN
0 0 1 1 0 0 0 0 0 1 0 0 1 -
0 0 1 1 0 0 0 0 0 0 1 0 1 -

0 0 1 0 0 1 0 1 0 0 0 0 1 MAN
0 0 1 0 0 1 0 0 1 0 0 0 1 MAN
0 0 1 0 0 1 0 0 0 1 0 0 1 -
0 0 1 0 0 1 0 0 0 0 1 0 1 -

0 0 1 0 1 0 0 1 0 0 0 0 1 MAN
0 0 1 0 1 0 0 0 1 0 0 0 1 MAN
0 0 1 0 1 0 0 0 0 1 0 0 1 -
0 0 1 0 1 0 0 0 0 0 1 0 1 -

0 0 1 0 0 0 1 1 0 0 0 0 1 MAN
0 0 1 0 0 0 1 0 1 0 0 0 1 MAN
0 0 1 0 0 0 1 0 0 1 0 0 1 -
0 0 1 0 0 0 1 0 0 0 1 0 1 -

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND
1 0 1 1 0 0 0 1 0 0 0 0 1 -
1 0 1 1 0 0 0 0 1 0 0 0 1 -
1 0 1 1 0 0 0 0 0 1 0 0 1 -
1 0 1 1 0 0 0 0 0 0 1 0 1 -

1 0 1 0 0 1 0 1 0 0 0 0 1 -
1 0 1 0 0 1 0 0 1 0 0 0 1 -
1 0 1 0 0 1 0 0 0 1 0 0 1 -
1 0 1 0 0 1 0 0 0 0 1 0 1 -

1 0 1 0 1 0 0 1 0 0 0 0 1 -
1 0 1 0 1 0 0 0 1 0 0 0 1 -
1 0 1 0 1 0 0 0 0 1 0 0 1 -
1 0 1 0 1 0 0 0 0 0 1 0 1 -

1 0 1 0 0 0 1 1 0 0 0 0 1 -
1 0 1 0 0 0 1 0 1 0 0 0 1 -
1 0 1 0 0 0 1 0 0 1 0 0 1 -
1 0 1 0 0 0 1 0 0 0 1 0 1 -

M1CPTA2005I
1CPT: Substation Central Unit 6-72
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-38: Protection Trip Switching Control Function Command Selection

CLOSED BREAKER TL2 TL1

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND
0 1 0 1 0 0 0 1 0 0 0 0 1 -
0 1 0 1 0 0 0 0 1 0 0 0 1 -
0 1 0 1 0 0 0 0 0 1 0 0 1 -
0 1 0 1 0 0 0 0 0 0 1 0 1 -

0 1 0 0 0 1 0 1 0 0 0 0 1 -
0 1 0 0 0 1 0 0 1 0 0 0 1 -
0 1 0 0 0 1 0 0 0 1 0 0 1 -
0 1 0 0 0 1 0 0 0 0 1 0 1 -

0 1 0 0 1 0 0 1 0 0 0 0 1 -
0 1 0 0 1 0 0 0 1 0 0 0 1 -
0 1 0 0 1 0 0 0 0 1 0 0 1 -
0 1 0 0 1 0 0 0 0 0 1 0 1 -

0 1 0 0 0 0 1 1 0 0 0 0 1 -
0 1 0 0 0 0 1 0 1 0 0 0 1 -
0 1 0 0 0 0 1 0 0 1 0 0 1 -
0 1 0 0 0 0 1 0 0 0 1 0 1 -

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

1 1 0 1 0 0 0 1 0 0 0 0 1 -
1 1 0 1 0 0 0 0 1 0 0 0 1 -
1 1 0 1 0 0 0 0 0 1 0 0 1 -
1 1 0 1 0 0 0 0 0 0 1 0 1 -

1 1 0 0 0 1 0 1 0 0 0 0 1 -
1 1 0 0 0 1 0 0 1 0 0 0 1 -
1 1 0 0 0 1 0 0 0 1 0 0 1 -
1 1 0 0 0 1 0 0 0 0 1 0 1 -

1 1 0 0 1 0 0 1 0 0 0 0 1 -
1 1 0 0 1 0 0 0 1 0 0 0 1 -
1 1 0 0 1 0 0 0 0 1 0 0 1 -
1 1 0 0 1 0 0 0 0 0 1 0 1 -

1 1 0 0 0 0 1 1 0 0 0 0 1 -
1 1 0 0 0 0 1 0 1 0 0 0 1 -
1 1 0 0 0 0 1 0 0 1 0 0 1 -
1 1 0 0 0 0 1 0 0 0 1 0 1 -

M1CPTA2005I
6-73 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-38: Protection Trip Switching Control Function Command Selection

CLOSED BREAKER TL2 TL1

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

0 1 1 1 0 0 0 1 0 0 0 0 1 -
0 1 1 1 0 0 0 0 1 0 0 0 1 -
0 1 1 1 0 0 0 0 0 1 0 0 1 -
0 1 1 1 0 0 0 0 0 0 1 0 1 -

0 1 1 0 0 1 0 1 0 0 0 0 1 -
0 1 1 0 0 1 0 0 1 0 0 0 1 -
0 1 1 0 0 1 0 0 0 1 0 0 1 -
0 1 1 0 0 1 0 0 0 0 1 0 1 -

0 1 1 0 1 0 0 1 0 0 0 0 1 -
0 1 1 0 1 0 0 0 1 0 0 0 1 -
0 1 1 0 1 0 0 0 0 1 0 0 1 -
0 1 1 0 1 0 0 0 0 0 1 0 1 -

0 1 1 0 0 0 1 1 0 0 0 0 1 -
0 1 1 0 0 0 1 0 1 0 0 0 1 -
0 1 1 0 0 0 1 0 0 1 0 0 1 -
0 1 1 0 0 0 1 0 0 0 1 0 1 -

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

1 1 1 1 0 0 0 1 0 0 0 0 1 -
1 1 1 1 0 0 0 0 1 0 0 0 1 -
1 1 1 1 0 0 0 0 0 1 0 0 1 -
1 1 1 1 0 0 0 0 0 0 1 0 1 -

1 1 1 0 1 0 0 1 0 0 0 0 1 -
1 1 1 0 0 0 0 1 0 0 0 1 -
1 1 1 0 0 0 0 0 1 0 0 1 -
1 1 1 0 1 0 0 0 0 0 1 0 1 -

1 1 1 0 0 1 0 1 0 0 0 0 1 -
1 1 1 0 0 0 0 1 0 0 0 1 -
1 1 1 0 0 0 0 0 1 0 0 1 -
1 1 1 0 0 1 0 0 0 0 1 0 1 -

1 1 1 0 0 0 1 1 0 0 0 0 1 -
1 1 1 0 0 0 1 0 1 0 0 0 1 -
1 1 1 0 0 0 1 0 0 1 0 0 1 -
1 1 1 0 0 0 1 0 0 0 1 0 1 -

L1 L1-2 L2 S00 S01 S10 S11 86T1 DFB1 86T2 DFB2 MAN ACT COMMAND

M1CPTA2005I
1CPT: Substation Central Unit 6-74
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.17 Switching due to Protection Tripping Sequence.

M1CPTA2005I
6-75 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.e Own Digital Signals

The H2 control function, as a logic equipment, has its own digital signals which may be used by
the other tasks. The digital signals provided by this control function are the following.

Table 6-39: H Control Function Digital Signals

Number Signal
0 High Volt. Cont. Func. For Pres./Abs. of Voltage Line 1
1 High Volt. Cont. Func. For Pres./Abs. of Voltage Line 2
2 Absence of Both Voltages (S00)
3 Absence of Voltage on Line 1 and Presence on Line 2 (S01)
4 Presence of Voltage on Line 1 and Voltage on Line 2 (S10)
5 Presence on both Lines (S11)
6 Control Function for High Voltage Maneouvers Blocked
7 Control Function in Manual Mode
8 Preference 1
9 Preference 2
10 Preference 1-2
11 Medium Voltage Control Function Activated
12 Medium Voltage Control Function for Presence/Absence of Voltage Line 1
13 Medium Voltage Control Function for Presence/Absence of Voltage Line 2
14 Medium Voltage Control Function in Service
15 Medium Voltage Control Function Blocked
16 Control Function for Trip Conditions Blocked
17 Loss of UA Voltage
18 Loss of UB Voltage
19 Loss of ULA Voltage
20 Loss of ULB Voltage
21 Spare 21 (isc_86TA)
22 Spare 22 (isc_86TB)
23 ISC_A_UNO
24 ISC_A_CERO
25 H Control Function Blocked
26 Command Failure
27 In Service Setting
28 In Service
29 Coupled Lines
30 Communications Failure
31 Spare 31
32 Spare 32

M1CPTA2005I
1CPT: Substation Central Unit 6-76
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.3.f Own Commands

The H2 Control Function has the same 14 controls as in the case of the H Control Function, as
follows:

Table 6-40: H Control Function Commands

Number Command
0 Preference 1 from panel
1 Preference 2 from panel
2 Preference 1-2 from panel
3 Manual from panel
4 Control function reset command (from panel)
5 Preference 1 from remote control
6 Preference 2 from remote control
7 Preference 1-2 from remote control
8 Manual from remote control
9 Command to reset the control function (from remote control)
10 Preference 1 from control function
11 Preference 2 from control function
12 Preference 1-2 from control function
13 Manual from control function

6.8.3.g External Signals

In order to function properly, the H control function uses signals that report on the status of the
substation. As some of these signals depend on the installation, they are not fixed, but
configurable. However, the meaning related to each signal is fixed, and these meanings are
shown in the table below:

Table 6-41: H Control Function External Signals

Ind. Signal Meaning
0 52LA Closed Line 1 breaker closed
1 52LAB Closed Breaker between lines 1 and 2 closed (not used)
2 52LB Closed Line 2 breaker closed
3 S_00 Absence of voltage on lines 1 and 2
4 S_01 Absence of voltage on line 1 and presence on line 2
5 S_10 Presence of voltage on line 1 and absence on line 2
6 S_11 Presence of voltage on lines 1 and 2
7 P_A Preference 1
8 P_B Preference 2
9 P_AB Preference 1-2
10 MAN Control function in manual mode
11 MED_ACT Medium voltage control function activated
12 AUT_ACT Authorization for operation
13 52TA Closed Line 1 transformer breaker closed
14 52TB Closed Line 2 transformer breaker closed
15 52B12 Closed Breaker between bus 1 and 2 closed
16 UA Voltage on bus 1
17 UB Voltage on bus 2
18 86TA Tripping in line 1 transformer
19 86TB Tripping in line 2 transformer (not used)

M1CPTA2005I
6-77 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 6. Description of Operation

Table 6-41: H Control Function External Signals

Ind. Signal Meaning
20 ULA Voltage on line 1
21 ULB Voltage on line 2
22 DISP_DEF Definite trip
23 DISP_DIFF_BARRAS_1 Bus differential 1 trip
24 DISP_DIFF_BARRAS_2 Bus differential 2 trip
25 DISP_TT_L1 Line 1 VT trip
26 DISP_TT_L2 Line 2 VT trip
27 SECC_CERRADOS Disconnector switches closed
28 FALLO_SUSCR_GOOSE Goose Subscription Failure
29 DISP_51_L1 Line 1 overcurrent trip
30 DISP_51_L2 Line 2 overcurrent trip
31 DISP_51_T1 Transformer 1 overcurrent trip
32 DISP_51_T2 Transformer 2 overcurrent trip
33 DISP_51_ENLACE Coupling overcurrent trip
34 LLAVE_69_L1 Line 1 key 69
35 LLAVE_69_L2 Line 2 key 69
36 LLAVE_69_ACOPL Coupling 69 key
37 DISP_SF6 SF6 trip

M1CPTA2005I
1CPT: Substation Central Unit 6-78
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.4 Y Control Function (Specific case of H)

This section explains a specific case of
the H control function: where there are
two high voltage lines and a single
medium voltage bus (see figure).

In this particular case of the H control

function, everything that was previously
said for this function is valid, with some
nuances.

- It makes no sense to have

preference AB, as one of the lines
is used as a spare for the other,
and power will never be supplied
through both lines simultaneously.
- There will be a single control
function for presence / absence of
voltage on medium voltage buses,
as we only have one bus (the
control function for presence /
absence of voltage on bus A will
be used).
Figure 6.18 Y Control Function.

- All of the previous information for the control function for HIGH VOLTAGE STATUSES is
valid.
- All of the previous information for the control function for HIGH VOLTAGE MANEUVERS
is valid, except for the input signals to the control function, the sequences to be executed
and the operations to be performed in each sequence, reflected in the tables below (note
that preference AB is not taken into consideration when selecting the sequence to be
executed).

Table 6-42: Y Control Function Inputs Signals (I)

Signal Description
89LA_C Disconnect Swtich 89LA Closed
89LA_A Disconnect Swtich 89LA Open
89LB_C Disconnect Swtich 89LB Closed
89LB_A Disconnect Swtich 89LB Open
52AB_C Breaker 52AB Closed
52AB_A Breaker 52AB Open
AUT_ACT Control Function Condition Active
S_00 Absence of Voltage on Both Lines
S_01 Absence of Voltage on Line A and Presence on Line B
S_10 Presence of Voltage on Line A and Absence on Line B
S_11 Presence of Voltage on Both Lines
P_A Preference A
P_B Preference B
P_AB Preference AB (not used)
MAN Manual
MED_ACT Medium Voltage Control Function Activated
86TA_ACT Trip 86A
86TB_ACT Trip 86B (not used)

M1CPTA2005I
6-79 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 6. Description of Operation

Table 6-43: Y Control Function Sequence Selection (I)

89LA_C 52LAB_C 89LB_C S_00 S_01 S_10 S_11 P_A P_B MAN 86TA MED_ACT AUT_ACT SEQ
X X X X X X X X X X X X 0 Default
X X X X X X X 0 0 1 X X 1 Default
X X X X X X X X X X X 1 1 Default
1 1 0 1 0 0 0 X X 0 0 0 1 Default
1 1 0 0 1 0 0 X X 0 0 0 1 1
1 1 0 0 0 1 0 X X 0 0 0 1 Default
1 1 0 0 0 0 1 1 0 0 0 0 1 Default
1 1 0 0 0 0 1 0 1 0 0 0 1 2
0 1 1 1 0 0 0 X X 0 0 0 1 Default
0 1 1 0 1 0 0 X X 0 0 0 1 Default
0 1 1 0 0 1 0 X X 0 0 0 1 3
0 1 1 0 0 0 1 1 0 0 0 0 1 4
0 1 1 0 0 0 1 0 1 0 0 0 1 Default
1 0 1 1 0 0 0 X X 0 0 0 1 5
1 0 1 0 1 0 0 X X 0 0 0 1 6
1 0 1 0 0 1 0 X X 0 0 0 1 7
1 0 1 0 0 0 1 1 0 0 0 0 1 7
1 0 1 0 0 0 1 0 1 0 0 0 1 6
0 0 0 1 0 0 0 X X 0 0 0 1 Default
0 0 0 0 1 0 0 X X 0 0 0 1 8
0 0 0 0 0 1 0 X X 0 0 0 1 9
0 0 0 0 0 0 1 1 0 0 0 0 1 9
0 0 0 0 0 0 1 0 1 0 0 0 1 8
1 0 0 1 0 0 0 X X 0 0 0 1 Default
1 0 0 0 1 0 0 X X 0 0 0 1 10
1 0 0 0 0 1 0 X X 0 0 0 1 11
1 0 0 0 0 0 1 1 0 0 0 0 1 11
1 0 0 0 0 0 1 0 1 0 0 0 1 10
0 0 1 1 0 0 0 X X 0 0 0 1 Default
0 0 1 0 1 0 0 X X 0 0 0 1 11
0 0 1 0 0 1 0 X X 0 0 0 1 12
0 0 1 0 0 0 1 1 0 0 0 0 1 12
0 0 1 0 0 0 1 0 1 0 0 0 1 11
1 1 1 1 0 0 0 X X 0 0 0 1 5
1 1 1 0 1 0 0 X X 0 0 0 1 13
1 1 1 0 0 1 0 X X 0 0 0 1 5
1 1 1 0 0 0 1 1 0 0 0 0 1 5
1 1 1 0 0 0 1 0 1 0 0 0 1 13
0 1 0 1 0 0 0 X X 0 0 0 1 Default
0 1 0 0 1 0 0 X X 0 0 0 1 14
0 1 0 0 0 1 0 X X 0 0 0 1 15
0 1 0 0 0 0 1 1 0 0 0 0 1 15
0 1 0 0 0 0 1 0 1 0 0 0 1 14
X X X X X X X X X 0 1 0 1 Default

M1CPTA2005I
1CPT: Substation Central Unit 6-80
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-44: Y Control Function Operations

SEQ Nº Operations
0 Default
1 Open 52AB, Open 89LA, Close 89LB and Close 52AB
2 Close 89LB and Open 89LA
3 Open 52AB, Open 89LB, Close 89LA and Close 52AB
4 Close 89LA and Open 89LB
5 Open 89LB
6 Open 89LA and Close 52AB
7 Open 89LB and Close 52AB
8 Close 89LB and Close 52AB
9 Close 89LA and Close 52AB
10 Open 89LA, Close 89LB and Close 52AB
11 Close 52AB
12 Open 89LB, Close 89LA and Close 52AB
13 Abrir 89LA
14 Open 52AB, Close 89LB and Close 52AB
15 Open 52AB, Close 89LA and Close 52AB
16 --- (Default)
17 --- (Default)
18 --- (Default)
19 --- (Default)
20 --- (Default)
21 Put Control Function in Manual Mode

- All of the previous information for the control function for MEDIUM VOLTAGE
MANEUVERS is valid, except the input signals to the control function and the
sequences to be executed, which are reflected in the tables below:

Table 6-45: Y Control Function Inputs Signals (II)

Input Description
UA Voltage presence / absence control function
UB (Not used)
S_11 Control function for high voltage statuses
89LA_C Disconnect switch 89LA closed
89LB_C Disconnect switch 89LB closed
52AB_C Breaker 52AB closed
52TA_C Line A transformer breaker closed
52TB_C (Not used)
52B12_C (Not used)
MAN Manual
AUT_ACT Control function condition active

Table 6-46: Y Control Function Sequence Selection (II)

89LA_C 89LB_C 89LAB_C 52TA_C S_11 UA MAN AUT_ACT SEQ
1 0 1 1 1 0 0 1 2
0 1 1 1 1 0 0 1 4
X X X X X X 1 1 Default
X X X X X X X 0 Default

M1CPTA2005I
6-81 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

- In this case, the control function for SWITCHING DUE TO PROTECTION TRIPPING
operates when the DISP_DEF signal is activated or 86A trips. In both cases, the control
function goes to manual (MAN) mode. The input signals to this control function and the
sequences to be executed are reflected in the tables below.

Table 6-47: Switching Due to Protection Tripping Control Function Input Signals
Input Origin
ULA Presence / absence of voltage on line A
ULB Presence / absence of voltage on line B
89LA_C Disconnect switch 89LA closed
89LB_C Disconnect switch 89LB closed
52AB_C Breaker 52AB closed
86TA_ACT Trip 86A
86TB_ACT (Not used)
MAN Manual
DISP_DEF Definitive trip
AUT_ACT Control function condition active

Table 6-48: Switching Due to Protection Tripping Control Function Sequence

Selection
89LA_C 89LB_C 52AB_C 86TA ULA ULB DISP_DEF MAN AUT_ACT SEQ
X X X X X X X 1 1 Default
X X X X X X 1 0 1 21
X X X 1 X X 0 0 1 21
X X X X X X X X 0 Default

6.8.5 Automatic Service Reset Equipment (ERAS)

The ERAS control function is responsible for performing an ordered connection of the high and
very high voltage breakers of an electrical substation after a loss of voltage situation has been
detected on the buses.

When a loss of voltage is detected on the buses, the control function opens all of the breakers
connected at that time; and after checking for voltage on the different power supply lines, it
proceeds to consecutively close each of the breakers, according to preset programming.

This control function is structured in the form of independent units: one central unit and as many
terminal units as there are high voltage breakers. The central unit of the ERAS is made up of
three independent automata: UCERAS1, UCERAS2 and UCERAS3. There is an In service /
Out of service setting, which affects all of the central unit’s automata.

The detection of an external close not generated by the ERAS at the terminals that are picked
up takes place at the ERAS’ terminals themselves. When any terminal detects this situation, it
sends a signal to the ERAS to block it.

The S_TX signal is used as an input for the terminals, which are alerted to this situation through
this signal and then proceed to reset. The ERAS (UCERAS2 control function) is reset because
this signal has been detected and the terminals have been reset.

Each of the ERAS’ terminals is made up of four automata: TERAS1, TERAS2, TERAS3 and
TERAS4. There is an IN SERVICE / OUT OF SERVICE setting for each of the terminals, which
affects all of the automata.

M1CPTA2005I
1CPT: Substation Central Unit 6-82
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.a UCERAS1
This automaton is responsible for controlling the Blocked statuses. When the automaton is
started, signal S_BLQ goes to 0 and signal S_CIEXT to 0, and the status changes to X_NBLQ,
described below.
• Statuses

Table 6-49: UCERAS1 Statuses

Status Description
X_NBLQ Non-blocked status. In this status, the system is checking the value of the
function (F1+F2+S_BLOQUEO) and the arrival of a block command. If the
previous function changes to a value of “1”, the system changes from X_NBLQ
status to X_BLQ_P, causing S_BLQ=1. If it receives a block command, the
system will change to X_BLQ_I status, causing S_BLQ=1. It will also change
status if the F5 function is activated, changing to X_BLQ_I, causing S_BLQ=1
and S_CX=1.
X_BLQ_P Blocked status because an input has a constant incorrect level (not pulsed). In
this status, the system is checking the value of the logic function that caused this
status (F1+F2+S_BLOQUEO) or the occurrence of a block command. It changes
status when the previous function takes the value “0” and switches to X_NBLQ,
causing SBLQ=0. If it receives a block command, it will change to X_BLQ_I.
X_BLQ_I Blocked status due to a block command. In this status, the system is checking the
arrival of a unblock command. When this occurs, the status changes. If the
function (F1+F2+S_BLOQUEO) has the value “1,” it will change to X_BLQ_P; if
the value of that function were “0,” it would go to X_NBLQ, causing S_BLQ=0.

• Contact Inputs

Table 6-50: UCERAS1 Contact Inputs

Signal Description
98Tt/B-A Tripping of the cut-out for bus A voltage.
98Tt/B-B Tripping of the cut-out for bus B voltage.
S_TBLQ(N) Terminal N blocked. There are as many inputs of this type as there are high
voltage terminals at the substation.
S_BLOQUEO Blocking input.
S_CIEXT(N) External close signal detected by terminal N.

• Contact Outputs

Table 6-51: UCERAS1 Contact Outputs

Signal Description
S_BLQ Control function blocked. This output is used as an input in the terminals to
prevent them from performing, both opening and closing manoeuvres.

M1CPTA2005I
6-83 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Commands

Table 6-52: UCERAS1 Commands

Signal Description
OB Block command.
ODB Unblock command.

• Flow Chart

Table 6-53: UCERAS1 Flow Chart

Function Description
F1 OR for all 98Tt/B inputs.
F2 AND for all terminal blocked signals
F5 OR for external close indications (S_CIEXT(N)) detected by the ERAS terminals.

6.8.5.b UCERAS2
This automaton is responsible for issuing close commands to the terminals in reset conditions,
according to the priorities set.

When the automaton is started, signal S_ARR goes to 1 and the status changes to
X_REPOSO, described below.
• Statuses

Table 6-54: UCERAS2 Statuses

Status Description
X_REPOSO Default status. This status changes when the F3 function is activated with the
ERAS not unblocked ( F3 ⋅ S _ BLQ = 1 ), switching to X_PKUP status, making
the signal S_PKUP=1.
X_ARR ERAS picked up status. It is exited:
1. Because F3 is cancelled, with the ERAS unblocked, or F3 is cancelled with
the excessive reset time signal having been activated
(F3 ⋅ S _ TX + F3 ⋅ S _ BLQ = 1), changing to X_REPOSO status, and making
S_ARR=0.
2. Because it has been detected that a terminal has reset conditions, with the
ERAS unblocked, or the excessive reset time value has been exceeded
(F4 ⋅ S _ BLQ = 1) , changing to the function of selecting the terminal to be
reset. After the selection, it changes to X_TREP(M) status if the end of the
list of resets has not been reached, or to X_REPOSO if it has been reached,
making S_ARR=0.
X_TREP(M) Account status of the reset time for the priority terminal (M) . This status may be
exited:
1. Because the count has finished (T_OUT). In this case, a close command is
generated for the priority terminal (M) and the status changes to X_1S.
2. Because the S_BLQ signal is activated; in this case, the counter stops,
memorizing the account, and it switches to the waiting status X_ESP(M).
3. Because priority terminal M loses its reset conditions (S_CREP(M)=0). In
this case, the value of F4 is checked; if it is 0, the status changes to X_ARR,
and if it is 1, it goes to the selection function.

M1CPTA2005I
1CPT: Substation Central Unit 6-84
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Table 6-54: UCERAS2 Statuses

Status Description
X_ESP(M) Waiting status. It is exited:
1. By deactivating the S_BLQ signal, in which case the status changes to
X_TRES(M), where the count that was initiated ends.
2. Because priority terminal M loses its reset conditions (S_CREP(M)=0). In this
case, the value of F4 is checked; if it is 0, the status changes to X_ARR, and
if it is 1, it goes to the selection function.
X_TRES(M) Continues with rest of count. It is exited:
1. Because the count has finished (T_OUT). In this case, a close command is
generated for the priority terminal (M) and the status changes to X_1S.
2. Because the S_BLQ signal is activated; in this case, the counter once again
stops, memorizing the count, and it switches to the waiting status X_ESP(M).
3. Because priority terminal M loses its reset conditions (S_CREP(M)=0). In this
case, the value of F4 is checked; if it is 0, the status changes to X_ARR, and
if it is 1, it goes to the selection function.
X_1S 1 s counting status. It is exited when the count finishes (T_OUT).

• Contact Inputs

Table 6-55: UCERAS2 Contact Inputs

Signal Description
S_ARR(N) Signal for terminal (N) picked up. There will be as many signals of this type as
there are terminals in service.
S_BLQ ERAS blocked signal.
S_CREP(N) Signal for terminal (N) with reset conditions.

• Contact Outputs

Table 6-56: UCERAS2 Contact Outputs

Signal Description
S_ARR ERAS signal picked up.

• Commands

Table 6-57: UCERAS2 Commands

Signal Description
OC(M) Close command for priority terminal (M).

M1CPTA2005I
6-85 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Settings

Table 6-58: UCERAS2 Settings

Name Description Margin
AJ_TREP(N) Setting for terminal (N) reset time. 3 - 30 s
AJ_TREPLRL(N) Setting for terminal (N) reset time due to LRL (reserve to 3 - 60 s
line).
AJ_PRI Setting for priorities. Indicates the order in which the 1 - 20
terminals picked up will be reset.

As can be seen, there are two reset time settings for each terminal: AJ_TREP(N) and
AJ_TREPLRL(N). You select one or the other depending on the type of pickup:
AJ_TREPLRL(N) is used when the S_ARRLRL signal is active.
• Flow Chart
Functions used in the status changes of the automaton:

Table 6-59: UCERAS2 Flow Chart

Function Description
F3 OR for all S_ARR(N) inputs.
F4 OR for all S_CREP(N) inputs.

There is a selection function that determines the next terminal to be reset, according to the
priorities set. There is a table that determines the order (M) according to the priority settings and
to the terminals in service and picked up. Only terminals that are in service and picked up are
reset. The one with the highest priority is chosen from among all the ones that are picked up
and have reset conditions.

Once the close command has been given to a terminal, a selection is made from among those
with the highest priority from the remaining ones that are picked up, bearing in mind the fact that
others with higher priority may have reached reset conditions, and these will have to be taken
into account.

In other words, the list of terminals to be reset may vary because some terminals lose reset
conditions, because others reach them (change in S_ARR(N) from 0 to 1) or because some
have been reset. A terminal that has already been reset will only get back on the list if a change
from 0 to 1 in its S_ARR(N) signal is detected.

M1CPTA2005I
1CPT: Substation Central Unit 6-86
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.c UCERAS3
This automaton is responsible for controlling the Excessive Reset Time. When the automaton
is started, signal S_TX goes to 1 and the status changes to X_EXREP, described below.
• Statuses

Table 6-60: UCERAS3 Statuses

Status Description
X_EXREP Default status. It is exit when function F3 is activated, changing to X_TEX status.
X_TEX Status with ERAS counting excess reset time (5 hours). It is exited:
1. Because F3 is cancelled, changing to X_EXREP status.
2. Because the count has finished (T_OUT). In this case, the status changes to
X_TX, making S_TX=1
X_TX Status with excessive reset time value exceeded. It is exited by receiving an
unblock command (ODB), changing to X_EXREP status, making S_TX=0.

• Contact Inputs

Table 6-61: UCERAS3 Contact Inputs

Signal Description Origin
S_ARR(N) Signal for terminal (N) picked up. There will be as many Terminals
signals of this type as there are terminals in service.

• Contact Outputs

Table 6-62: UCERAS3 Contact Outputs

Signal Description
S_TX Signal for excessive reset time value exceeded.

• Commands

Table 6-63: UCERAS3 Commands

Signal Description
ODB Reset command.

• Settings

Table 6-64: UCERAS3 Settings

Name Description
AJ_TEX Setting for excessive reset time (5 hours).

• Flow Chart
Functions used in the status changes of the automaton:

Table 6-65: UCERAS3 Flow Chart

Function Description
F3 OR for all S_ARR(N) inputs.

M1CPTA2005I
6-87 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.d TERAS1
This automaton is responsible for controlling the Blocked (BLQ) statuses. When the automaton
is started, signal S_TBLQ goes to 0 and the status changes to H_NBLQ, described below.
• Statuses

Table 6-66: TERAS1 Statuses

Status Description
H_NBLQ Non-blocked status.
H_T_PT Status counting time of voltage presence on line and absence on buses, while the
breaker is closed. This time will be 2 s.
H_BLQ_I Blocked status. This status may only be exit by an unblock command.
H_BLQ_P Blocked status. This status lasts as long as the signals leading to it last.

• Contact Inputs

Table 6-67: TERAS1 Contact Inputs

Signal Description
98Tt/L Tripping of the cut-out for line voltage
VL Line voltage
VB Bus voltage
IC Breaker closed
FOA Open command failure
FOC Close command failure
S_AVB Tripping of the cut-out for line voltage
S_CEX External close signal

• Contact Outputs

Table 6-68: TERAS1 Contact Outputs

Signal Description
S_TBLQ Terminal blocked.

• Commands

Table 6-69: TERAS1 Commands

Signal Description
ODBT Unblock command

• Logic
The VB signal to be used by the automaton will be determined by the position of the line
disconnect switches in the case of a double bus. Of the two voltages available, the one
corresponding to the closed disconnect switch will be used.

M1CPTA2005I
1CPT: Substation Central Unit 6-88
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.e TERAS2
This automaton is responsible for undervoltage opening and for detecting pickup (ARR) and
reset (REP) conditions, as well as for giving the close commands received from the ERAS
central unit.

It controls the functions for faults on buses and lines, as well as the close orders for cut-outs.
• Statuses

Table 6-70: TERAS2 Statuses

Status Description
H_REP Default status.
H_T_SUBT Status of counting time for undervoltage opening. This time is a setting
(AJ_T_SUBT).
H_ESPABR Status of waiting for opening, after an open command has been issued. If
opening does not take place, an OCF will be generated which will send the
TERAS1 to blocked status. TERAS2 will remain in this status and will return to
default condition when the unblock order is received, which will also take
TERAS1 to non-blocked status.
H_ESPCR Status of waiting for reset conditions.
H_ARRIMPLRL Status of pickup impossible due to LRL. This occurs when there are pickup
conditions, but the breaker had not been open long enough beforehand.
H_ARRIMPLRB Status of pickup impossible due to LRB. This occurs when there are pickup
conditions, but the breaker had not been open long enough beforehand.
H_ESPOC Status of waiting for close order from UCERAS.
H_ESPCER Status of waiting for close. Similar to H_ESPABR.
H_C_AVERÍA Status of fault check after close. It will remain in this status for 3 s.
H_AVERÍA Fault status.
H_CEX Status of external close detected.

• Contact Inputs

Table 6-71: TERAS2 Contact Inputs

Signal Description
98Tt/L Tripping of the cut-out for line voltage.
98Tt/B Tripping of the cut-out for bus voltage.
VL Line voltage.
VB Bus voltage.
IC Closed breaker.
IA Open breaker.
S_TBLQ Terminal blocked signal.
S_ETBLQ External block signal.
S_BLQ ERAS blocked signal.
S_IC_TA Signal for breaker closed long enough.
S_IA_TA Signal for breaker open long enough.
S_FSINC No sync signal.
S_TX Signal for excess reset time.

M1CPTA2005I
6-89 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Contact Outputs

Table 6-72: TERAS2 Contact Outputs

Signal Description
S_TARR Terminal picked up.
S_CREP There are reset conditions.
S_CEX External close detected.
S_OC_EB Close command due to EB.
S_OC_EL Close command due to EL.
S_OC_AT Close command due to AT.
S_OC_LRB Close command due to LRB.
S_OC_LRL Close command due to LRL.
S_AVBA Fault on A buses.
S_AVBB Fault on B buses.
S_AVL Fault on line.
S_C_AVERÍA Signal for fault check, after close command executed.

The S_AVBA and S_AVBB signals will be generated from S_AVB, taking into consideration to
which bus the terminal is connected.

• Other signals used

Table 6-73: TERAS2 other signals used

Signal Description
S_ARRLRL Signal for pickup due to LRL.
S_ARRLRB Signal for pickup due to LRB.
S_ARRST Signal for pickup due to undervoltage.
S_CREPL Signal for reset conditions due to EL or LRL.
S_CREPB Signal for reset conditions due to EB or LRB.
S_CARR Signal that pickup conditions exist (breaker closed for more than the time set)
before open command is given.

• Commands issued by the terminal

Table 6-74: TERAS2 Commands issued by the terminal

Command Description
OA Open command to be sent to the associated IED.
OC Close command to be sent to the associated IED.

• Commands received by the terminal

Table 6-75: TERAS2 Commands received by the terminal

Command Description
OC_ERAS Close command from ERAS central unit.
ODBT Terminal unblock command.

M1CPTA2005I
1CPT: Substation Central Unit 6-90
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Settings

Table 6-76: TERAS2 Settings

Name Description Margin
AJ_T_SUBT Setting for disconnect time due to undervoltage. 0 - 10 s
EB Setting for terminal with energizing of buses. YES / NO
EL Setting for terminal with energizing of line. YES / NO
AT Setting for terminal with voltage coupling. YES / NO
LRL Setting for terminal with reserve to line. YES / NO
LRB Setting for terminal with reserve to buses. YES / NO

The EB, EL, AT, LRL and LRB settings may be simultaneous.
• Logic
The VB signal to be used by the automaton, as well as the 98Tt/B signal, will be determined by
the position of the line disconnect switches in the case of a double bus. Of the two voltages and
98Tt/B available, the one corresponding to the closed disconnect switch will be used.

In the case of a double bus, there will be two S_AVB signals (signal for fault on a bus). A
terminal will generate one signal or the other depending on what bar it is connected to.
Likewise, one signal or the other will be used to control the blocking automaton (TERAS1).
• Flow Chart
The following functions will be used in the description of the flow chart:

Table 6-77: TERAS2 Flow Chart

Function Description
F6 IC ⋅ VL ⋅ VB ⋅ 98Tt / L ⋅ 98Tt / B ⋅ S_ TBLQ ⋅ S_ BLQ
F7 IA ⋅ VB ⋅ 98Tt / B ⋅ S_ TBLQ ⋅ S_ BLQ ⋅ LRB
F8 IA ⋅ VL ⋅ 98Tt / L ⋅ S_ TBLQ ⋅ S_ BLQ ⋅ LRL
F9 VL ⋅ VB ⋅ ( EB + LRB) ⋅ 98Tt / B
F10 VB ⋅ VL ⋅ ( EL + LRL ) ⋅ 98Tt / L
F11 VL ⋅ VB ⋅ S_ FSINC

• Interaction with Block Signals

In the H_REP status, the S_TBLQ signal will be checked. When this signal is active, the status
can only be exit by activating F6. In the H_T_SUBT and H_ESPABR statuses, S_TBLQ need
not be checked; in all other statuses, S_TBLQ must be at 0 in order to be able to exit them.

M1CPTA2005I
6-91 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.f TERAS3
This automaton is responsible for detecting whether bus and line voltages drop while the fault
check is being performed. This is necessary because the length of time that the voltage drop
must last in order for there to be a fault is 2 s, while the verification time is 3 s; in other words,
they are two different times that must run simultaneously.
• Statuses

Table 6-78: TERAS3 Statuses

Status Description
W_REP Default status.
W_NVLNVB2 Counting 2 s after detecting the drop in both voltages while the fault is being
checked
W_ESPNAV Waiting for TERAS2 to exit the fault check status (H_C_AVERÍA)

• Contact Inputs

Table 6-79: TERAS3 Contact Inputs

Input Description
98Tt/L Tripping of the cut-out for line voltage
98Tt/B Tripping of the cut-out for bus voltage.
VL Line voltage.
VB Bus voltage.
S_C_AVERÍA Fault check signal

• Contact Outputs

Table 6-80: TERAS3 Contact Outputs

Output Description
S_NVLVB2 Signal that voltages have dropped for 2 s.

• Logic
The VB signal to be used by the automaton, as well as the 98TtB signal, will be determined by
the position of the line disconnect switches in the case of a double bus. Of the two voltages and
98Tt/B available, the one corresponding to the closed disconnect switch will be used.

M1CPTA2005I
1CPT: Substation Central Unit 6-92
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.g TERAS4
This automaton is responsible for determining whether the breaker has been closed long
enough to pick up the terminal.
• Statuses

Table 6-81: TERAS4 Statuses

Status Description
E_REP Default status.
E_CTA_AB Status of Counting Open Time for the Time Set.
E_CTA_CE Status of Counting Closed Time for the Time Set.
E_TA_AB Status of Open for the Time Set.
E_TA_CE Status os Closed for the Time Set.

All of the times mentioned above are 10 s.

• Contact Inputs

Table 6-82: TERAS4 Contact Inputs

Input Description
IA Open Breaker.
IC Closed Breaker.
IDES Unknown Breaker.

• Contact Outputs

Table 6-83: TERAS4 Contact Outputs

Output Description
S_IA_TA Breaker Open for the Time Set.
S_IC_TA Breaker Closed for the Time Set.

M1CPTA2005I
6-93 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Operation

Figure 6.19 TERAS4 Control Function.

6.8.5.h Own Signals

As a virtual unit, the ERAS control function has a number of signals that provide information to
the other tasks. This number of signals depends on the number of virtual terminals it has. There
are 24 fixed signals for the control function, and then there will be 40 more for each terminal.

The following table shows what these signals are and how the terminals are mapped in the
control function’s signals as a whole. The fixed digital signals are:

Table 6-84: ERAS Own Signals

Signal Meaning
0. ERAS_SERVICIO ERAS in service
1. S_BLQ ERAS blocked
2. S_CX ERAS connected
3. OB Block command
4. ODB Unblock command
5. ARR ERAS picked up
6. TX Excessive reset time value exceeded
7. AUTO ERAS in automatic mode
8. MANUAL ERAS in manual mode
9..23 Spare

M1CPTA2005I
1CPT: Substation Central Unit 6-94
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The signals for each terminal are:

Table 6-85: Signals for each terminal

Signal Meaning
24. 98t-B terminal Tripping of the cut-out for bus voltage
25. VB Bus voltage
26. S_TBLQ Terminal blocked
27. S_TARR Terminal picked up
28. S_CREP There are reset conditions
29. S_CREPB Signal for reset conditions due to EB1or LRB2
30. S_CREPL Signal for reset conditions due to EL3 or LRL4
31. S_CARR Signal that pickup conditions exist (breaker closed for more than the time set)
before open command is given
32. S_ARRLRL Signal for pickup due to LRL
33. S_ARRLRB Signal for pickup due to LRB
34. S_ARRST Signal for pickup due to undervoltage
35. S_CEX External close signal
36. S_OC_EB Close command due to EB
37. S_OC_EL Close command due to EL
38. S_OC_AT Close command due to AT5
39. S_OC_LRB Close command due to LRB
40. S_OC_LRL Close command due to LRL
41. S_AVBA Fault on A Buses
42. S_AVBB Fault on B Buses
43. S_AVB Signal for fault on buses
44. S_AVL Signal for fault on line
45. S_C_AVERIA Fault check after close
46. S_NVLVBL Signal indicating that voltages have dropped for more than 2s
47. S_IA_TA Breaker open during the time set
48. S_IC_TA Breaker closed during the time set
49. ODBT Unblock command
50. OC_ERAS Close command
51. OC_TEL Close command from remote control
52. ORD_AUT Automatic / manual command
53. VLi Status of calculated VL or VL
54. 98Tt_Li Tripping of the cut-out for line voltage
55. S_CREPAT Signal for terminal with voltage coupling with reset conditions
56. S_CREPLRL = Signal for terminal with reserve to line with reset conditions
57. S_CREPLRB = Signal for coupling terminal for reserve to buses with reset conditions
58. UT_SERVICIO = Terminal in service
59..63.- Spare

(1) EB = Energizing of Buses

(2) LRB = Reserve to Buses
(3) EL = Energizing of Line
(4) LRL = Reserve to Line
(5) AT = Voltage Coupling

M1CPTA2005I
6-95 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.8.5.i Own Commands

The ERAS control function has 4 commands that modify its status. They are the following:

Table 6-86: ERAS Commands

0 ERAS Block
1 Unblock
2 Put in Auto Mode
3 Put in Manual Mode

6.8.5.j External Signals

Each IED terminal needs certain information about the status of the different elements
associated with the IED it controls. For each terminal there are 15 signals, which are (in order):

Table 6-87: ERAS External Signals

Signal Meaning
ISC_98Tt_L Signal for tripping of the cut-out for line voltage
ISC_89LA Signal for line A disconnect switch status
ISC_89LB Signal for line B disconnect switch status
ISC_VL Line voltage signal
ISC_IA Open breaker signal
ISC_IC Closed breaker signal
ISC_IDES Unknown breaker signal
ISC_FOA Open command failure signal
ISC_FOC Close command failure signal
ISC_S_ETBLQ ERAS external block signal
ISC_ERAS_BLQ Signal for ERAS blocked, generated by UCERAS11
ISC_ERAS_TX Excessive reset time signal generated by UCERAS32
ISC_S_FSINC No sync signal
ISC_S_AUTO Signal for ERAS in automatic mode
ISC_S_S_MANUAL Signal for ERAS in manual mode

(1) UCERAS1 = automaton belonging to the ERAS control function, responsible for controlling Blocked
statuses.
(2) UCERAS3 = automaton belonging to the ERAS control function, responsible for controlling excess reset
time.
UCERAS2 = automaton belonging to the ERAS control function, responsible for issuing close commands to
the terminals in reset conditions, according to the priorities set.

M1CPTA2005I
1CPT: Substation Central Unit 6-96
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.9 UCS as Virtual Equipment

6.9.1 Virtual Central Equipment ISC-s (Digital Signals)
The digital signals of this logic equipment can amount up to 287, 300, 324 and even 345 (as a
function of the software version used, number of digital inputs of the CPX/CPP/1CPT and GPS
used). Below, please find their numbering and meaning for the case of 345 signals:

Table 6-88: Virtual Central Equipment Digital Signals

Signal Description
0 … 254 Communications failure with the equipment whose PROCOME address is 0..254
255 Spare
256 Communications failure with the GPS clock
257 Synchronization failure with the GPS clock
258 Booting CPX/CPP/1CPT
259 Communications failure with any CPU
260 Communications failure with CPX/CPP/1CPT
261 Communications failure with PCD
262 Internal GPS defect
263 Connection through modems established
264 Access denied due to invalid credentials
265 Manual equipment synchronization via MMI or via telnet (1CPT equipment only)
266 Communications failure with any 2nd board CPU
267 Communications failure with any 3rd board CPU
268 Communications failure with any 4th board CPU
269 Communications failure with PLC Redundant Mod2
270 Communications failure with PLC [Redundant Mod1]
271 Communications failure with SCD
272 Critical Error in Central Unit
273 Communications with PLC through Port 1
274 Communications with PLC through Port 2
275 CPX/CPP/1CPT synchronized1
276 CPX/CPP/1CPT1 synchronizing source
277 CPX/CPP/1CPT communications failure with remote HMI
278 Remote HMI communications failure with CPX/CPP/1CPT
279 Remote HMI enabled
280 Loss of changes file
281 Loss of alarm file
282 1st communications board failure (CPX equipment only)
283 2nd communications board failure (CPX equipment only)
284 LAN1 off (1CPT equipment only)
285 LAN2 off (1CPT equipment only)
286..288 Spare
289 The relay configuration Data Base of the Substation Configuration Server
(UCSConf) not updated

M1CPTA2005I
6-97 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Tabla 6-88: Virtual Central Equipment Digital Dignals

Signal Description
290 1st double ring’s 1st ring failure
291 1st double ring’s 2nd ring failure
292 2nd double ring’s 1st ring failure
293 2nd double ring’s 2nd ring failure
294 3rd double ring’s 1st ring failure
295 3rd double ring’s 2nd ring failure
296..299 Spare
300..307 Status of CPX/CPP/1CPT digital inputs 1-8
307..315 Status of CPX digital inputs 9-16
316..319 Spare
320 NTP 1 LOCAL2 Server
321 NTP 2 LOCAL2 Server
322 NTP 3 LOCAL2 Server
323 NTP 4 LOCAL2 Server
324 NTP 5 LOCAL2 Server
325 NTP 1 Server last Date and Time3
326 NTP 2 Server last Date and Time3
327 NTP 3 Server last Date and Time3
328 NTP 4 Server last Date and Time3
329 NTP 5 Server last Date and Time3
330 NTP 1 Server Communications failure4
331 NTP 2 Server Communications failure4
332 NTP 3 Server Communications failure4
333 NTP 4 Server Communications failure4
334 NTP 5 Server Communications failure4
335 NTP 1 Server Leap Indicator Error5
336 NTP 2 Server Leap Indicator Error5
337 NTP 3 Server Leap Indicator Error5
338 NTP 4 Server Leap Indicator Error5
339 NTP 5 Server Leap Indicator Error5
340 NTP 1 Server Threshold Error6
341 NTP 2 Server Threshold Error6
342 NTP 3 Server Threshold Error6
343 NTP 4 Server Threshold Error6
344 NTP 5 Server Threshold Error6

1. These signals are NOT implemented into 1CPX-A and 1CPP-A relays.

2. Indicates that the NTP Server is in the same subnet as 1CPT. These signals are only used in 1CPT relays.
Refer to the meaning of these signals in the Annex.

3. Indicates the NTP server with which the last synchronization is made.

4. Indicates that server n sends a date and time with wrong format or not responding.

5. Indicates that server n sends a date and time with correct format but with one indication or unreliable time
flag. These signals are only used in 1CPT relays.

6. Indicates that the time difference between the time received from server n and the internal time of the central
unit exceeds the value configured in sntp.cfg, and therefore the central unit does not synchronize its internal
time with the time received from server n. These signals are only used in 1CPT relays.

M1CPTA2005I
1CPT: Substation Central Unit 6-98
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.9.2 Virtual Central Equipment ISE-s (Commands)

Table 6-89: Virtual Central Equipment Commands

ISE Descripción
0 Change the entire substation to Local
1 Change the entire substation to Remote Control
2 Change Group 1 to Local
3 Change Group 1 to Remote Control
4 Change Group 2 to Local
5 Change Group 2 to Remote Control
6 Change Group 3 to Local
7 Change Group 3 to Remote Control
8 Change Group 4 to Local
9 Change Group 4 to Remote Control
10 Change Group 5 to Local
11 Change Group 5 to Remote Control
12 Change Group 6 to Local
13 Change Group 6 to Remote Control
14 Change Group 7 to Local
15 Change Group 7 to Remote Control
16 Change Group 8 to Local
17 Change Group 8 to Remote Control
18 Change Group 9 to Local
19 Change Group 9 to Remote Control
20 Change Group 10 to Local
21 Change Group 10 to Remote Control
22 Change Group 11 to Local
23 Change Group 11 to Remote Control
24 Change Group 12 to Local
25 Change Group 12 to Remote Control
26 Change Group 13 to Local
27 Change Group 13 to Remote Control
28 Change Group 14 to Local
29 Change Group 14 to Remote Control
30 Change Group 15 to Local
31 Change Group 15 to Remote Control
32 Change the remote operating HMI to Operating Mode (may issue commands)1
33 Change the remote non-operating HMI to Monitoring Mode (may not issue
commands)1.

1. These ISE-s are only used in UCX_A11000000 relays.

M1CPTA2005I
6-99 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.9.3 Virtual Central Equipment ISS-s (Output Writes)

The 1CPT has 8 configurable digital outputs. These outputs update through the output writes
into the virtual central equipment. Output write 1 activates the physical output 1, output write 2,
the output 2, etc.

Table 6-90: Virtual Central Equipment Output Writes

ISE Description
0 Activates the physical output 1
1 Activates the physical output 2
2 Activates the physical output 3
3 Activates the physical output 4
4 Activates the physical output 5
5 Activates the physical output 6
6 Activates the physical output 7
7 Activates the physical output 8

6.10 Programmable Logic

The 1CPT has a task that behaves like a logic equipment, whose function is to execute a logic
program that performs certain programmable functions at the substation level. Among other
things, this logic makes it possible to group signals, perform relatively simple control functions,
etc.
It uses all of the signals in the 1CPT's database as input variables. For outputs, it provides its
own signals, which are configurable. In addition, it can perform commands on substation
equipment.
This logic program is executed sequentially and continuously from beginning to end. To do this,
it uses the status of the database immediately prior to execution. Changes in the logic signals
are generated at the end, once the full program has been executed. The logic works by
statuses, not by changes, so a short pulse is not processed.

The input and output variables that may be used in the different operations are shown in the
following table:

Table 6-91: Input and Output Variables for Logical Operations

Variable Description
ISC Digital Signals
ISE Commands
ISS Writing Outputs
MEA Analog Inputs
CON Counters
Internal Records Internal Logic Records

M1CPTA2005I
1CPT: Substation Central Unit 6-100
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Apart from these variables, settings can be used in the TEMPOR, DNIVEL and CMPCONT
operations. The settings have the AJn format, where n varies between 0 and NumAjs-1, and
NumAjs is the number of settings configured. They can be used in the above operations instead
of the fixed parameters.

These settings may be modified during execution from the operating console. If fixed values are
used in the parameters of the TEMPOR, DNIVEL and CMPCONT operations, they can only be
modified from the logic editor included in Zivergraph®. However, if settings are used, they may
be changed at any time from the respective Control Function Configuration screen in the
operating console.

Setting changes take place immediately, as soon as they are sent from the operating console.
The level detectors (DNIVEL) begin operating with the new values. Any timers that were running
at that moment are reset and start counting from the beginning. In other words, if a timer is
running and it has to count 8 seconds, if any logic setting is changed (it does not necessarily
have to be the setting relating to that timer) when 6 seconds have elapsed, this timer would start
over again and would finish at the end of 14 (6+8) seconds. This overcounting only happens the
first time after a setting change, and only if the timer is running.

The logic program has the following limitations:

- Maximum number of inputs per logical operation: 32.

- Maximum number of outputs per logical operation: 32. In addition, logical operation
outputs may only be addressed to internal registers or to signals of the LOGICA virtual
unit itself.
- Maximum number of internal logic registers: 1024 (0 … 1023). Several outputs may not
be addressed to the same register in a single logical operation.
- Maximum number of timers available: 200.
- Maximum number of RS flip-flops: 225.
- Maximum number of JK flip-flops: 20.
- Maximum number of D flip-flops: 20.
- Maximum number of MANDO-type logical operators: 200.
- Maximum number of FMANDO-type logical operators: 40.
- Maximum number of ESC-type logical operators: 30.
- Maximum number of settings: 20.
- Maximum number of counters CONT: 10.
- Maximum number of counter comparators CMPCONT: 10.

This logic program is created using the logic editor included in the Zivergraph® software.

The different operations that can be performed in this programming are listed below.
• OR
This is a logical OR operation with several inputs and several outputs.

Table 6-92: OR Truth Table

In1 In2 Out
0 0 0
0 1 1
1 0 1
1 1 1

M1CPTA2005I
6-101 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• AND
This is a logical AND operation with several inputs and several outputs.

Table 6-93: AND Truth Table

In1 In2 Out
0 0 0
0 1 0
1 0 0
1 1 1

• XOR
This is a logical exclusive-OR operation with several inputs and several outputs.

Table 6-94: XOR Truth Table

In1 In2 Out
0 0 0
0 1 1
1 0 1
1 1 0

• NOT
This is a logical NOT operation: it negates the input and assigns that value to the respective
outputs.

Table 6-95: NOT Truth Table

In1 Out
0 1
1 0

• CABLE
This is an assignment, i.e., the value of the input is assigned to the different outputs.

Table 6-96: CABLE Truth Table

In1 Out
0 0
1 1

• FFRS
This is an RS flip-flop.

Table 6-97: FFRS Truth Table

R S Qt+∆t
0 0 Qt
0 1 1
1 0 0
1 1 X

M1CPTA2005I
1CPT: Substation Central Unit 6-102
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• FFJK
This is a JK flip-flop.

Table 6-98: FFJK Truth Table

J K Qt+∆t
0 0 Qt
0 1 1
1 0 0
1 1 __Qt

• COMMAND
It executes a command in the following way:

If the input signal is activated (goes from 0 to 1 or vice versa if it is negated), the command
indicated with the desired operation code is executed, and whatever value the input signal has
is assigned to the outputs.

Commands
belonging to the
LOGICA virtual
unit itself may not
be used as a
command
parameter in this
logical operation,
because it makes
no sense for a
unit to send
commands to
itself. Its
operation is
shown in figure.

Figure 6.20 Operation of the MANDO Logical Operation.

• FMANDO
This is a variation of the preceding function: if the input signal is activated, the command
associated with the operation code indicated is executed, and there is a delay of the time set for
the execution of the command to see whether the test signal is activated. If it is activated during
that time, the “command executed” output signal will be activated. If it is not activated during the
time set, the “command not executed” output will be activated.

Commands belonging to the LOGICA virtual unit itself may not be used as a command
parameter in this operation, because it makes no sense for a unit to send commands to itself.

M1CPTA2005I
6-103 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• ESC
This is a function
that executes the
output writing
indicated with the
activation operation
code if the input
signal is active, or
with the
deactivation
operation code if
the input signal is
inactive. In
addition, whatever
value the input
signal has is
assigned to the
outputs.
Figure 6.21 Operation of the ESC Logical Operation.

• TEMPOR
This is a timer whose
operation is shown in
Figure 6-22.

TA and TB are
expressed in full
seconds.

Figure 6.22 Operation of the Timer.

• DNIVEL
This is a range evaluator
which works as follows:

The value of the field

measurement (in volts or
amperes) is taken and
compared with {VC},
{VMIN} and {VMAX} as
indicated in Figure 6.23.

Figure 6.23 Operation of the Range Evaluator.

M1CPTA2005I
1CPT: Substation Central Unit 6-104
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

- If the measurement > {VMAX}  The (ISC_MAYOR) output signal is activated.

- If the measurement = {VC}  The (ISC_IGUAL) output signal is activated.
- If the measurement < {VMIN}  The (ISC_MENOR) output signal is activated.
• DEACT
This is a detector for the only active input from among several inputs.

Table 6-99: DEACT Truth Table (Particular Case of 3 Inputs)

In1 In2 In3 Out
0 0 0 0
0 0 1 1
0 1 0 1
0 1 1 0
1 0 0 1
1 0 1 0
1 1 0 0
1 1 1 0

• CONT
It is a Pulse Counter, which increases when an ascending pulse is introduced into the Q input
and resets if it receives an ascending signal from the other R input. In case both inputs activate,
a counter reset will occur.

The number of defined counters must not surpass a maximum value stipulated as 10 counters.

Table 6-100: CONT Truth Table

Q R CONT
0 0 -
0 01 The value resets
01 0 The value is increased by one.
01 01 The value resets

• CMPCONT
It is a Counter Comparator, in such a manner that a value of a counter is compared with the set
point value (Vc), fixed or declared in a logic adjustment. If the value is greater or equal to it, the
definite output signal will activate. Otherwise, said signal will deactivate.

The number of defined counter comparators must not surpass a maximum value stipulated as
10 counters.

If CON >= Vc, the ISC activates

If CON < Vc, the ISC deactivates

M1CPTA2005I
6-105 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.11 Remote Console

Los modelos de 1CPT incorporan la funcionalidad de acceso remoto a la información de control
Some models of the 1CPT let a remote console be connected, which makes it possible to
display and manoeuvre the different elements of the installation from a computer outside of the
installation. This access is gained through the remote web client linked to the 1CPT integrated
Web Console. Also access to transparent mode data is allowed for devices using the
PROCOME protocol.

Here, the word “remote” not only stands for “distant” but also refers to a different function. Local
web clients are usually in a PC WorkStation beside the 1CPT, whereas remote web clients are
usually outside the substation. However, configurations with both consoles outside or inside the
substation are possible. The distinctive function of each are maintained no matter the physical
location.

Connection of said remote access can be: RTC line, GSM line, dedicated line and Ethernet
network. Access through direct serial connection (cable or fibre optic) is not possible and a
telephone modem is compulsory. Connection to an Ethernet network is carried out via device
internal LAN ports, with RJ45 connection.

From the functional point of view, up to six remote web clients can be connected simultaneously
to the 1CPT integrated Web Console.
Discerning between local web client and remote web clients will be carried out via the
configuration of the IP address used by the local web client in the 1CPT integrated Web
Console. The difference between IP addresses enables discerning, partly, the functions allowed
for each type of web client, as shown below.

All clients connected to the 1CPT Web Console, whether local or remote, will receive the same
events and alarms. The maximum number of alarms received is 250. The maximum number of
events can be configured, 500 being the default value. These parameters are shared by all the
1CPT integrated Console Web clients.

There is the possibility to enable (or not) command execution from remote Web clients. A
parameter within the 1CPT Web Console enables configuring different remote access functions.
For instance, a remote web client can be used as a second console to allow the execution of
commands or, on the contrary, remote web clients can be configured only for display mode (for
more information please refer to the 1CPT Web Console manual).
This remote access basically provides the same functions than the local web Client connection.
From a remote web client, the 1CPT cannot be configured with a new configuration. This
operation can only be carried out from the local web client.

Access of a Remote web client to the 1CPT Integrated Web Console via an Ethernet network
using TCP/IP protocol involves no difficulties it being enough to configure, in the 1CPT
Integrated Web Console, the IP address of the Local web Client and the parameter that enables
/ disables the capacity to execute commands from Remote web Clients (for more information
please refer to the 1CPT Web Console manual).

However, when a telephone line is used (whether RTC, GSM or dedicated), the 1CPT remote
access server must be configured stating the serial port RS-232 (COM1 or COM2) used for the
connection, as well as the type of the connection itself.

M1CPTA2005I
1CPT: Substation Central Unit 6-106
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.12 Commands
There is a task in the 1CPT known as MANDO which is responsible for managing commands
for different elements in the installation not associated to a specific command execution task.

The desire to perform a command may come from outside the 1CPT (of a web client connected
to the integrated operations console or remote control room console) or internally (the logic or a
control function). The final destination of the command may be a position IED (UCP) or the
1CPT. This intention is collected by the MANDO task, which processes it and routes it towards
the final destination after performing a series of checks. In case the command receiver is
associated to a specific command execution task, as is the case for IEC-61850 devices, the
command is captured and processed by the task, which, in turn, routes it towards the final
destination after performing a series of checks.

The MANDO task first checks to see whether the element is already in position. If so, the
command is not given. For this to take place, the status signal associated with the command
must be configured in Zivergraph®. If this signal is not configured, no verification takes place.

After this filter, verification is made of whether there are any blocks at the 1CPT level. If there
are block signals configured and any are active, the command will not be given. Otherwise, it
will follow its route.

If the destination is an internal logic equipment of the 1CPT, it is sent to the respective task to
be carried out. If it is an external unit, the command is sent to that unit.

If the command is external, the unit may, in turn, have its own blocking logic and command
management. As a result, we will generally obtain positive or negative confirmation of the
command being performed. In some cases, we will also obtain the reason why the command
was not performed. This information is once again received by MANDO, which processes it and
sends it back to the command requester.

The accompanying figure shows a schematic diagram of the route that commands take through
the 1CPT. Depending on the configuration and on the model of the UCP, the checks and results
may be different.

M1CPTA2005I
6-107 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.24 Command Logic (Example).

6.12.1 Group Commands

Another additional function of the MANDO task is to perform a particular control function relating
to LOCAL / REMOTE CONTROL commands. In general, IEDs have a status indicating whether
remote control is allowed, or whether only control local to the substation is allowed. This is a
function relating to the worker safety.

If we put an IED in local mode, we may want the rest of the IEDs associated with it (same bus,
transformer, etc.) to also be put in local mode, thus preventing operations from being performed
on them from the remote control office.

This function is standard in the 1CPT. Using configuration information, the MANDO task
monitors the status of the LOCAL / REMOTE CONTROL signals from all of the IEDs that have
been configured within a command group. Whenever any of these changes its status, MANDO
initiates commands to the rest of the IEDs, in order to put them in the same status as the one
that changed.

6.12.2 Master Commands

writing groups are configured in which one acts as the master and the rest as slaves. When the
signal associated with the master changes, a chain of command or writing is initiated for the
slave elements, in order to switch them to the desired status.

This control function is used to transmit signals horizontally between different units through the
1CPT, thus avoiding the need for wiring between them.

For example, bus voltage is usually measured by the unit associated with the coupling IED. This
unit’s inputs are wired to the outputs of the medium voltage transformers. This unit has the
analog value of the voltage measurements. The rest of the units connected to this bus do not
need the analog value of the voltage; they only need to know whether or not there is voltage on
the bus. This information is calculated by the coupling IED and is sent to the 1CPT through the
communications protocol. The 1CPT takes this signal and sends it to any units that need it. This
operation is performed whenever a change is detected in the originating signal: presence of
voltage on buses.

M1CPTA2005I
1CPT: Substation Central Unit 6-108
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

This functionality can be applied to a multitude of signals in the substation. The 1CPT makes it
possible to transfer signals horizontally between different bay IEDs. The use of this function
depends on the configuration and the installation.

These commands are affected by the blocking logic explained in point 6.10.1.

6.12.3 Commands sent to IEC 61850 Devices

Commands sent to IEC61850 compatible bay devices will not be managed by the MANDO task,
but by the main IEC61850 task itself owing to command singularities described in standard
IEC61850, where different procedures for IED control command execution are proposed.

In the same way as the 1CPT overall task for command processing, MANDO task, operates, the
main task corresponding to the 1CPT IEC61850 module first checks whether the element is
already in position. If the answer is yes, the command is not executed. To this end the status
signal associated to the command in the Zivergraph must be configured. This check will not
take place if said signal is not configured.

After this filter, the 1CPT is checked for blocks. If there are some blocking signals configured
and any is active, the command is not executed. Otherwise, it proceeds to send the command
to said device through the applicable communications service.

The device can have in turn a blocking and command management logic. As a result, a
confirmation on whether the command has been executed or not will be received. In some
cases, the reason for command failure will also be received. Said information is again received
by the IEC61850 task, which after processing sends it back to the petitioner.

6.13 LEDs
The 1CPT has 4 configurable LEDs at the right side of the front panel. Any digital signal from
the database may be assigned to these LEDs. When the associated signal is active, the LED
will light up, while if it is not, the LED will remain off.

For each LED, the associated signal, whether it is negated and whether it is flashing can be
configured. If it is configured as flashing, it is possible to indicate the frequency of said flashing.

6.14 Digital Inputs

The 1CPT has 4 digital inputs. These digital inputs are mapped as digital signals within the
CENTRAL logic equipment, starting with signal 300. In other words, the first digital input
corresponds to signal 300 in the CENTRAL unit, the second to 301, etc. The reading period is
configurable in multiples of 6 ms.

The reading logic of the digital inputs has a debounce filter. The status must be maintained for
at least 3 reading periods for a change to be considered valid.

6.15 Digital Outputs

The 1CPT has 8 configurable digital outputs for generic use. These outputs are externally
accessible through writing outputs on the CENTRAL logic equipment.

Writing output 1 activates physical output 1, writing 2 activates output 2, etc.

M1CPTA2005I
6-109 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16 Logs (optional)

Some 1CPT models incorporate a functionality know as logs, which makes it possible to
periodically collect and store information about certain signals at the installation for later
external processing.

There is a specific task responsible for performing the work related to this functionality.

As the 1CPT’s disk is limited in size, files are stored using a FIFO system. When a new file is
created every night at midnight, the oldest file is deleted. The number of days that the 1CPT
stores the information is, at first, configurable, but it depends on the size of the flash disk and on
the amount of information one wishes to store.

These data files are extracted through the operating console, which exports them to swap files
so that they can be easily processed using commercial software.

There are three types of logs: for meters, for counters and for changes.

6.16.1 Logs Collecting

6.16.1.a Metering Logs
The metering logs are responsible for periodically saving information to disk about
measurements that are configured. The period is one minute.

Every minute at second 0, a record is saved to disk of the values of the configured
measurements stored at that moment in the database. This data is stored in a file on the 1CPT's
disk, ordered in such a way that one file is created per day with all the data for that day.

6.16.1.b Counter Logs

The counter logs are responsible for periodically saving information to disk about the counters
that are configured. The period is configurable, with a default period of 15 minutes.

Every period at second 0, a record is saved to disk of the values of the configured counters
stored at that moment in the database. This data is stored in a file on the 1CPT's disk, ordered
in such a way that one file is created per day with all the data for that day.

6.16.1.c Change Logs

The change logs are responsible for storing a record on disk when a change occurs in one of
the signals that are configured. It is possible to choose whether both activation and deactivation
are recorded.

The data is also ordered in daily files with the same number of days stored as for the other
types of logs.

M1CPTA2005I
1CPT: Substation Central Unit 6-110
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2 Reports and Trends

The purpose of the Web Report application is to manage historical data measured by the 1CPT
by displaying them in graphic and chart type reports. The main application screen consists of
two menus and a work area.

- Tool menu. It contains direct access to the capture and display menus of the three types
of data captured in the 1CPT: measurement history data, counter history data, signal
history data. In turn, these menus consist of different submenus as a function on whether
a graphic type report (measurements and counters) or chart type report (measurement,
counters and signals) is to be created.

- Connection menu. Allows to specify the connection parameters to the 1CPT such as the
IP of the specific equipment together with the related user name and password.

- Work area. It is the part of the application where the selection, configuration and display
screens of the reports to be generated are shown.

Figure 6.25 Home Screen of the Web Report Application.

M1CPTA2005I
6-111 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2.a Connection to the 1CPT Relay

As mentioned above, in order to connect to the remote relay, the user must disclose the IP
address of the 1CPT together with the necessary access codes: User Name and Password.

Figure 6.26 Connection Menu.

In case there is an error in the relay access data or this is not available, the message below will
be displayed notifying the connection attempt error.

Figure 6.27 Connection Attempt Error Message.

Otherwise, if the relay is available and a connection has been possible, the user will be notified
by means of the confirmation message below.

Figure 6.28 Correct Connection Message.

Once the connection is established, the user can select the type of report to be generated. In
case of signal and measurement data, the user can choose from configuring a Graphic type or
a Chart type report. In case 1CPT events are to be captured, the only possible display is Chart
type.

In parallel with the frontend of the report display, a script or daemon has been worked out for
daily capture of data measured by the remote relays. If the PC where the application is being
run contains also this script, the database will gradually be filled without the intervention of the
user. If this is not the case, the initial database together with the applicable configuration folders
will be created during the first application run.

M1CPTA2005I
1CPT: Substation Central Unit 6-112
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2.b Graphic Type Report Generation

Once the type of unit and the type of report has been selected, the user must enter the range of
dates to be consulted. The user will receive the applicable warning messages in case of range
description error (final date earlier than the starting date) or no date associated to the required
range neither in the database nor in the 1CPT.

As an example, we take the

configuration of the Measurement
element Graphic and Chart type
reports. The same steps are required
for the generation of counter and
signal element reports.

Figure 6.29 Consultation Date Range Selection.

Figure 6.30 Message for no Consultation Range Data.

In case the data were captured in the

1CPT but not in the database, the
application will notify the user, giving
him the option to display through the
saved records or to download the
1CPT records in order to save them in
the database and include them in the
graphic.

Figure 6.31 Unloading 1CPT Data.

M1CPTA2005I
6-113 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Once the existence of data has been checked within the required range, and having selected
the option for graphic type report generation, the Configuration screen is displayed. Here the
user sets the parameters on which the record curve will be generated.

For measurement reports, the user can set up the sampling scale (minutes, hours, days,
months or years) as well as the values to be displayed (normal values, mean values, minimum
and maximum values).

Figure 6.32 Graphic Type Report Configuration Screen.

M1CPTA2005I
1CPT: Substation Central Unit 6-114
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Under the Report

Attributes menu, the
Report Attributes
Configuration submenu
can be found, which will
open a new window to
configure the elements to
be displayed in the
graphic diagram.
Figure 6.33 Report Attributes Menu

In the configuration window, the user can select up to a maximum of ten elements from the
ones recorded by the 1CPT.

Figure 6.34 Configuring the Elements of the Graphic Type Report.

The curve colour and the report title, in case the default title is not representative enough, can
be selected, as well as the elements to be displayed at any time.

This configuration can be changed as many times as required when generating the display
data.

M1CPTA2005I
6-115 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Every time the selected configuration is confirmed, the application will capture from the
database the records required and will draw the graphic curve based on the above defined
parameters. If the Interpolation option is deactivated, the curve will be built by sections, and
can be scrolled by means of the slider at the bottom of the screen.

Figure 6.35 Curve Display with no Interpolation.

M1CPTA2005I
1CPT: Substation Central Unit 6-116
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

If the Interpolation option is activated, the application will display the complete evolution of the
curve in only one screen, adjusting the sampling range as required.

Figure 6.36 Curve Display with Interpolation.

Once the graph is generated, the user

can print it by gaining access to the
Print menu, within the File menu.
Apart from the file name, the elements
to be displayed in the final reports,
such as Title, Subtitle, Page Header
or Page Foot, can be configured.

Figure 6.37 Print Configuration.

M1CPTA2005I
6-117 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 6. Description of Operation

Figure 6.38 Acceptance of the Report to be Printed.

Figure 6.39 Display of the Final Report.

M1CPTA2005I
1CPT: Substation Central Unit 6-118
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2.c Chart Type Report Generation

The steps to be followed for generating chart type reports are the same as those described in
the section above.

Configuration of report
attributes will allow the
user to select up to ten
elements from the ones
configured in the 1CPT
as well as the names to
be shown at the columns
of the charts in case the
default values were not
representative enough.

Figure 6.40 Configuration of the Chart Type Report.

Figure 6.41 Chart Type Display of the Measurements Recorded in the 1CPT.

M1CPTA2005I
6-119 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

For chart type reports, two types of export are possible as required: PDF format or Excel
format. The same as before, configuration parameters can be entered through the submenus
located at the File menu.

Figure 6.42 Chart Type Report File Menu.

The Excel format export configuration

screen is displayed to the right.
.

Figure 6.43 Excel Format Export Configuration.

On the other hand, the PDF format

export configuration screen is also
displayed beside it.

Figure 6.44 PDF Format Export Configuration.

M1CPTA2005I
1CPT: Substation Central Unit 6-120
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Below are the charts to

display the export of
chart type reports both to
Excel format and PDF
format.

Figure 6.45 Export of Chart Type Report to Excel Format.

Figure 6.46 Export of Chart Type Report to PDF Format.

M1CPTA2005I
6-121 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2.d Deleting the Database

If so required, the user can opt to delete all database records. In case the deleted records are
not anymore in the 1CPT, recovering these records to save them to the database would be
impossible.

Figure 6.47 File Menu Options in the Main Tool Bar.

Figure 6.48 Confirm Deletion of the Database.

6.16.2.e Database Disconnection

At completion of graphic type report
generation, the user may disconnect
the remote relay through the
Disconnect button located at the
disconnection tool bar.

Figure 6.49 Confirm Disconnection.

M1CPTA2005I
1CPT: Substation Central Unit 6-122
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.16.2.f Installation Instructions

• Installation of the Web Report Application
1. Unzip the file InformesWeb_pass_ziv.zip to a local folder.
2. Edit the file WebReports.jnlp (with a text editor) and replace the text "localhost" by the IP
address of the 1CPT.
3. If required, set the language of file WebReports.jnlp: replace the file extensions by
adequate extensions:
- en and GB --> for British English.
- es and ES --> for Spanish.
4. Copy folder "WebReports" to the 1CPT in folder \CFDisk\www\wwwpub\ConsoleViewer.
5. In order to launch the Web Report application from the Engineering menu of the web
HMI, the file protec.cfg. must be adequately configured. An input must be added as
follows:
# REPORT application 1
REPORTS, // Button name
c:\windows\system32\javaws.exe c:\WebReports\webreports.jnlp

• Installation of the Web Report Application Launcher

1. Copy the file "WebReports" to the root directory (C:\) of the PC where the Web client is to
be run.
2. Replace the file WebReports.jnlp by the file modified in the section above (or edit it with
the same criteria).
3. To check everything is correct, run the program C:\WebReports\InfWeb.bat
4. To install the automatic download task, run the file
c:\WebReports\daemon\RunDaemon.bat. The periodic task is downloaded to the PC.
5. Program the periodic task for automatic file capture in Windows xp systems.
- Click Start -> Control Panel -> Scheduled Tasks -> Add Scheduled Task and click
Next.
- Click Examine and scroll to c:\Documents and Settings\usuario\ziv\dirIP\daemon,
select daemon.ziv and click Open.
- Write the task name. For example, WebReports.
- Select Daily and click Next.
- Choose the start time: 00:10. Leave the rest of the fields at their default settings:
Everyday and Start Date -> the current day. Click Next.
- If required, enter the user password and click Next.
- Check all data are correct and click End.
6. Program the periodic task for automatic file capture in Windows 7 systems.
- Select Control panel -> Administrative tools -> Task scheduler.
- On the panel to the right, select Create basic task.
- Enter the task name and description and click Next.
- Select the time (00:10). Select Repeat every 1 day and click Next.
- On Start a program, click Examine. Scroll to c:\Usuarios\usuario\ziv\dirIP\daemon
and select daemon.ziv.
- Leave Add extensions and Start at empty. Click Next.
- Check the configuration and click End.

M1CPTA2005I
6-123 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.17 Redundancy
6.17.1 Introduction
This section describes the operation of the Substation Control and Protection System (PCS)
with Hot Stand By, for Fibre Optic star topology with PROCOME protocol devices and network
topologies for IEC61850 protocol devices.

In view of the different criteria to refer to the various substation components, we establish that,
from now on, the term Substation Control and Protection will be used to refer to the devices
constituting it: Central Unit (1CPT) and HMI (PCD). The Central Unit itself is referred to as 1CPT
and the HMI as PCD.

In as much as the 1CPT activity status, it will be construed as active while it is interrogating
devices and communicating with the Substation Control Centre (COS), whereas it will be
construed as passive while it is in stand by.

With reference to the activity status with which 1CPT devices must start within the redundant
system, 1CPT devices can be classified as primary, it being the device that will initially under
normal circumstances start in active status (device interrogation and communication with COS)
and secondary or backup, which will start in passive mode, waiting for problems to occur or
operator command to take control.

Primary and secondary classifications are not interchangeable between both 1CPT devices,
namely, by configuration, one 1CPT device will be associated with the roll of primary whereas
the other, also by configuration, will be permanently the secondary 1CPT.

This classification extends to PCDs depending on which 1CPT they are connected to and which
is their status. Thus, the primary PCD will be connected to the primary 1CPT and will be active
if the 1CPT is active; on his part the secondary PCD will be connected to the secondary
1CPT and will be active if the 1CPT active. There exists another modality in which only one
PCD exists, which will be connected to the active 1CPT.

6.17.2 Communications Topologies

The communications system with its bay devices depends on their characteristics. If IEC61850
devices are involved, a local area network connection will be used. If PROCOME protocol
devices are involved, a fibre optic star connection between each other will be used.

The figure below shows graphically the Hot Stand By redundant system architecture with
IEC61850 devices.

M1CPTA2005I
1CPT: Substation Central Unit 6-124
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.50 Hot Standby Redundant System Architecture with IEC61850 Devices.

M1CPTA2005I
6-125 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The figure below shows the redundant system architecture using star topology, which is the
level 1 topology adopted in case of using PROCOME protocol devices.

Figure 6.51 Assembly Architecture with Level 1 Star Topology.

M1CPTA2005I
1CPT: Substation Central Unit 6-126
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.52 shows the redundant system architecture with PROCOME protocol devices
connected with star topology using Terminal Servers (CIC). This architecture will be used when
the number of 1CPT connected devices is high.

Figure 6.52 Assembly Architecture with Level 1 Star Topology using CIC.

The above figures are schematic in as much as there could exist more bay devices connected
to the 1CPT, as well as other interface elements for other devices: converters, switches, etc.

Also, other devices with other protocols connected to the 1CPT could exist using the same or
similar topology; however, these devices will not be part of the system switch over conditions.

M1CPTA2005I
6-127 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.17.3 Redundancy Functions

6.17.3.a Central Units
As stated above, the control system is redundant at Substation Central Station level. This
means there are two 1CPT devices, with one (connected to the active 1CPT) or two HMI, one
of the 1CPT devices being primary whereas the other device will be secondary or backup, this
being on permanent basis through a setting.

Under normal operating conditions, the primary 1CPT will be in active mode carrying out the
interrogation function on level 1 devices, execution of substation logic, execution of the different
automatic controls, communication with the remote control room, etc., whereas the secondary
1CPT will be in passive mode, receiving, on the one side, events and alarms sent by the
primary 1CPT and, on the other side, monitoring the status of the primary 1CPT and the status
of the communications between the latter and level 1 devices, in order to take control of the
substation in case the primary 1CPT goes out of service.

It must be made clear that 1CPT in passive mode, whether primary 1CPT or secondary
1CPT, will not perform substation logic, execution of the different automatic controls,
communications with the remote control room, although it will update level 1 device databases
on the part of the other 1CPT, in such a way that when switched to active it will not produce
coherence changes. The HMI associated to the passive 1CPT will show updated level 1 device
databases as well as events and alarms generated at the substation, as the active 1CPT sends
to the passive 1CPT every event and alarm generated by level 1 devices and 1CPT logic
devices.

The two Central Stations will be communicated via a configurable redundancy channel that can
be:

- RS-232 type serial connection using TCP/IP over PPP protocol.

- LAN connection through any of 1CPT LAN adapters (LAN1 or LAN2).

This communication will allow a 1CPT to know the status of another 1CPT, interchange events
and alarms received from bay devices, as well as to transmit level 1 device databases and
commands to change from a 1CPT the activity status of the other 1CPT.

In case of IEC61850 topologies, 1CPTs can also be connected through own digital input /
output signals, as a redundancy channel backup for interchanging just the status of each 1CPT.
This is useful when on the failure of the redundancy channel (serial or LAN), both 1CPTs can
know the status of the other, only one being active at any time.

M1CPTA2005I
1CPT: Substation Central Unit 6-128
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The redundancy status of the 1CPT is sent to the other 1CPT through 6 digital outputs:

- The first 3 outputs (SR1, SR2, SR3) to send the status as a 3 bit code.
- The next 3 outputs (SR1, SR2, SR3) to send the complement of said status in order to
check at the target terminal the correct operation of the outputs of the other 1CPT and
the inputs of the own 1CPT (checking that the status received through the 3 first inputs
is complementary to the status received through the next 3) thus inferring that the status
is valid and reliable.

The redundancy status of the other 1CPT is received through 6 digital inputs:

- The first 3 inputs (ER1, ER2, ER3) to receive the status as a 3 bit code.
- The next 3 inputs (ER1, ER2, ER3) to receive the complement of said status in order to
check at the target terminal the correct operation of the outputs of the other 1CPT and
the inputs of the own 1CPT thus inferring that the status is valid and reliable.

Coding the 1CPT redundancy status using 3 bits results into the following:

- 000: Invalid status.

- 001: Active.
- 002: Passive.
- 003. Pick-up.
- 004: Attempting to establish communication with level 1 devices.
- 005: Dead.
- 006: Switching (from passive to active or the opposite).
- 007: Invalid status.

Figure 6.53 shows the wiring between the two CPTs to interchange the redundancy status
through digital Inputs / Outputs:

Figure 6.53 Connection through Digital Inputs / Outputs.

When 1CPT devices are interrogating level 1 devices and communicating with COS, they are
considered to be active, whereas if they are not performing any of these operations, they are
considered to be passive.

M1CPTA2005I
6-129 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.17.3.b Automatic Switch over Mechanism

On normal operating conditions of the redundant system, the primary 1CPT will be active
whereas the secondary will be passive. The system looks for this situation after rebooting any
of both 1CPT devices, provided a previous switch over, namely, a situation in which the
secondary 1CPT is in Active mode, has not occurred, as in this case the primary 1CPT will
switch automatically to passive status after starting.

Automatic switch over means the mechanism by which the primary 1CPT (which was in active
mode) goes out of service on any problem and consequently the secondary 1CPT (which was
in passive mode) reacts and switches to active mode, without external intervention. Under this
situation, if the primary 1CPT recovers, this will automatically switch to passive mode and both
1CPT devices will remain in this situation until the operator manually restores the system to the
normal operating condition, or until the system makes it automatically upon the occurrence of
any problems with the secondary 1CPT.

When the redundant system switches again to normal operation, where the Active 1CPT is the
primary 1CPT and the Passive 1CPT is the secondary 1CPT, is known as automatic system
reset.

The automatic switch over of the redundant system will be controlled by the following indicators:

a) Activity status (active/passive) of both CPTs.

b) Status of communications with level 1 devices.

A necessary condition, in order for the automatic redundant system switching (switch
over and reset) to operate correctly, is the permanent connection between both 1CPT
devices, allowing them to know the activity status of the other 1CPT. This condition guarantees
the stability of the system, meaning that one 1CPT is in active mode and the other in passive
mode. Otherwise, error situations could be reached (of low probability of occurrence), which
could bring the redundant system to a situation of incompetence, in which the secondary 1CPT
attempts to switch to active mode, with the primary 1CPT operating also in active mode. This
situation will be present when the secondary 1CPT, which is in passive mode, has problems in
obtaining the status of communications between it and bay devices (hardware or
communications software problems).

CPTs in active mode are in charge of interrogating bay devices, updating data sent by them to
the 1CPT real time database. Also, the active 1CPT will transfer the data received to the
associated HMI and the COS.

M1CPTA2005I
1CPT: Substation Central Unit 6-130
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

On the contrary, 1CPTs in passive mode do not interrogate bay devices and, thus, cannot keep
its real time database updated. This is the reason why it cannot respond to requests received
from the COS, nor will it have its internal logic or internal automation functions operative, nor will
it allow the execution of commands on substation bays and can just attend possible manual
switch over commands received from the associated HMI or commands received via the
connection with the 1CPT in active mode. However, it can make use of every substation event
or alarm, as they are sent by the active 1CPT provide the connection between both 1CPT
devices is operative, as well as of the level 1 device databases.

From the data sent by bay devices and received by the active 1CPT, events and alarms will be
drawn up which will be transferred to the passive 1CPT via the redundant channel (serial or
LAN), in order for both Operation HMIs to show the same information.

Both Operation HMIs will display on their event and alarm screens, events and alarms received
from their respective 1CPT devices.

In order for both Operation HMIs to show the same events and alarms, communication between
both 1CPT devices must exist sometime, so that if no communication ever exists between both
devices, the Active 1CPT must save said events and alarms in the Compact Flash. In this way,
when the communications channel between both 1CPT devices is restored, events and alarms
saved into the Flash disc of the 1CPT that has been active during the period in which said
communication did not exist, are sent to the 1CPT that was passive for this in turn to send the
same to the associated HMI.

On the other hand, it must be said that the contemplated Hot Stand By redundant system will
not transfer configuration and settings changes carried out in one Control Station to the other
Control Station, but it will the operator’s responsibility to transfer said changes from one Station
to the other. A mechanism will exist, which, based on the connection between both 1CPT
devices, will validate that both CPTs have the same configuration (except for the setting
indicating whether the 1CPT operates as primary or secondary). To that effect, it will compare
cyclic redundancy codes or CRC calculated in advance from CPTs configuration, so that if
differences between the configurations of both CPTs are detected, each 1CPT will generate its
own alarm to indicate different configurations between both 1CPT devices, which will reach on
the one hand the COS from the active 1CPT, and on the other hand both Operation HMIs.

Figures 6.54 and 6.55 describe the operation of the automatic switching mechanism, by
displaying the status diagrams that will govern the operation of each of both 1CPT devices,
displaying primary 1CPT and secondary 1CPT status diagrams respectively:

M1CPTA2005I
6-131 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 6. Description of Operation

Figure 6.54 Primary 1CPT Status Diagram.

M1CPTA2005I
1CPT: Substation Central Unit 6-132
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

Figure 6.55 Secondary 1CPT Status Diagram.

M1CPTA2005I
6-133 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The figures above show the five statuses described below:

a) PICK-UP: This status is reached after rebooting the 1CPT, in which the initialisation
process of the different modules that constitute the 1CPT software are carried out.

b) LEVEL 1 COMMUNICATIONS SET UP: This status is reached when the 1CPT tries to
take control of the level 1 device network as a previous step towards the active status.
In this status the level 1 device network is surveyed to establish whether there are any
communications with any level 1 device connected to the 1CPT.

In case of IEC61850 devices, it will be checked whether there is any MMS association
established with any relay.

In case of PROCOME devices, several interrogation cycles will be used to find out the
link status of every bay device configured in the CPX, with the end purpose of
determining if communication with any bay device has been established.

c) PASSIVE: This status is reached when the 1CPT cannot switch to active status and
also when it exits the same. In this status, the 1CPT, apart from monitoring changes in
the activity status of the active 1CPT, goes into listening mode to monitor whether there
is level 1 line activity. For IEC61850 devices, the existence of any Report Control Block
(hereafter RCB) is checked, which means that the other 1CPT is in active status and
has enabled the RCBs. For PROCOME devices, it goes into listening mode to monitor,
in level 1 lines, bay device feedback in response to the interrogations of the other CPX
(that is in active status).

Not all passive 1CPT functions are operative, but on the contrary, the operability of the
internal Logic, Command and Automation modules will be disabled. Only switch over
commands from the associated HMI or commands sent by the other 1CPT via the
communications channel between both 1CPT devices will be executed, apart from
database refreshment with refresh data and changes from the other 1CPT.

The HMI associated to the Passive 1CPT, will be updated in real time, provided the
connection between both 1CPT devices is available, with the events, alarms and refresh
data sent from the active 1CPT to the passive 1CPT, via their communications
channel.

Nor will the communications with the Remote Control station be enabled.

M1CPTA2005I
1CPT: Substation Central Unit 6-134
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

In this status, the 1CPT monitors the activity of level 1 line communications (checking
whether RCBs are enabled from the other 1CPT, which means it is active) and also
monitors the status of the other 1CPT in order to be able to carry out the automatic
switching of the system, whether on a switch over basis (Primary 1CPT passive and
Secondary 1CPT active) or reset basis (Primary 1CPT active and Secondary 1CPT
passive).

d) ACTIVE: In this status the 1CPT is in charge of interrogating bay devices and
processing the feedback from the same. Therefore, in this mode all functions featured
by ZIV Central Units, such as real time Databases, Logic, Commands and Automation
will be operative.

In this status, the 1CPT transmits in real time to the Passive 1CPT, provided the
connection between both 1CPT devices is available, the events, alarms and refresh
data received from bay devices, in order for the Operation HMI associated with the
1CPT that is in passive status, to display reliable substation data. Should the
connection between both 1CPT devices be out of service, events and alarms will be
saved in the Compact Flash of the Active 1CPT until communications are restored, at
which moment said data is transferred to the Passive 1CPT, which at the same time will
send it to the Operation HMI.

In a Control Station in active mode, the PROCOME transparent system will operate
with ZIV devices, through the 1CPT.

e) DEAD: This status means 1CPT problems with the network (its IP becomes 0.0.0.0) or
with the starting (file errors detected and indicating Incomplete Start).

In this status, the 1CPT is out of service for the redundancy. Under these
circumstances, the 1CPT cannot backup the other 1CPT.

The 1CPT will automatically exit the dead status to go into the passive status once the
problem is resolved (start completed or IP address recovered).

On the other hand, in this dead status the 1CPT will not execute switch over commands
from the associated HMI or the other 1CPT received via the communications channel
between both 1CPT devices.

On the other hand, a special feature of the redundant system is that during the starting phase
the Primary 1CPT has preference over the Secondary 1CPT to set to active mode, only if the
latter is not already in this mode or has already initiated to establish communications with bay
devices. This preference for starting solves the problem of taking control of level 1
communications, that is achieved by assigning to the Secondary 1CPT a greater starting time
than the time assigned to the Primary 1CPT. In this way, once the starting of the system has
initiated, if no communications have been established between both CPTs, the Primary 1CPT
will monitor level 1 lines to determine whether there is activity with bay devices before the
Secondary 1CPT, and, as the initial situation will be of no activity with the devices (RCBs are
disabled) the Primary 1CPT will set to active status and the Secondary 1CPT will set to
passive status.

M1CPTA2005I
6-135 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The essential feature of the automatic Hot Stand By redundant system switch over mechanism
is that if the Primary 1CPT, being in the active status at a given time, switches off or goes out
of service (due to a hardware or software problem), will switch to passive or dead status and
the Secondary 1CPT must take control and switch to active status, under which it will
interrogate devices and communicate with COS.

The switch over process, from the time the Active 1CPT switches off until the system is fully
operative, can take several minutes. After a communications loss with the other 1CPT, the
Passive 1CPT checks the status of level 1 communications, in order to discern whether the
other 1CPT has switched off or their mutual communication has been lost. Other factor affecting
the switch over time is the number of devices connected to the 1CPT.

If with a 1CPT operating in active mode, the other 1CPT is initiated, whether the communication
between both 1CPT devices is in service or not, the 1CPT that is initiated must monitor the
communications with bay devices and the status of the other 1CPT (provided the
communication between both 1CPT devices is available), and if it detects activity in level 1
lines, or the status of the other 1CPT prevents it to set to active status, it will remain in passive
mode; otherwise, it will try to set to active mode, going previously, if required, through level 1
communication set up status.

Moreover, another feature of the automatic switch over mechanism is based on the search for a
non balanced state of both CPTs, namely a situation in which both devices always have
opposed activity statuses (one 1CPT in active mode and the other 1CPT in passive mode). In
this way, provided there is communication between both 1CPT devices, if one device changes
the activity status (active / passive status), then the other 1CPT must automatically set to the
status just left by the first. If it is the Primary 1CPT the 1CPT that goes from passive status to
active status, this will be referred to as automatic reset, whereas if it is the Secondary 1CPT
the 1CPT that goes from passive status to active status, this will be referred to as automatic
switch over again.

However, after an automatic switch over (Primary 1CPT in passive status or out of service,
and Secondary 1CPT in active status), which remains stable (without problems in the
Secondary 1CPT), the resetting of the redundant system (Primary 1CPT set to active status
and Secondary 1CPT set to passive status) will be manual, namely, the Primary 1CPT in
passive mode cannot switch over spontaneously to active mode (if the Secondary 1CPT is in
active mode) even if it recovers from the error situation, but operator intervention will be
required. To this end, the possibility to carry out manual Control Station switch over and reset
will be provided, through commands from the Operation HMIs.

One more feature of the redundant system is its reaction upon lack of communications with bay
devices. If the Primary 1CPT is active then it must switch over to passive mode provided the
Secondary 1CPT is not dead, and the Secondary 1CPT will set to active mode. However, if
the Secondary 1CPT is active then it will switch to passive status if the Primary 1CPT is in
passive status.

If the communications channel between both 1CPT devices is out of service and the
Secondary 1CPT is in passive mode and moreover it does not detect any activity with bay
devices through level 1 lines, then it will leave the passive status in order to attempt to take
control of bay device network, switching to level 1 communications set up status. If
communications with any bay device is not achieved, then the Secondary 1CPT will switch
back to passive status.

M1CPTA2005I
1CPT: Substation Central Unit 6-136
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

When automatic redundant system switch over or reset occurs, the 1CPT that sets to passive
mode sets the internal real time database to disabled status, and the 1CPT that sets to active
mode after updating bay device data in its real time database, will set it to enabled status for the
rest of 1CPT software modules (logic, automation, etc.). In this way, a controlled activation and
deactivation of both 1CPT devices will be guaranteed.

Any malfunction detected in the 1CPT of the Primary Central Station, causes a system
automatic switch over to the Secondary Central Station, whereas, a malfunction of the
Primary Central Station Operation HMI will not imply an automatic system switch over.
However, a manual system switch over can be made from the Secondary Operation HMI,
provided there is communication between both 1CPT. Loss of communications with the
Remote Control will not imply an automatic system switch over.

6.17.3.c Manual Switching Mechanism

Manual switch over and reset can be carried out by the operator from the Operation HMIs (PCD
devices), but not from COS. These manual commands will allow switching both Primary and
secondary 1CPT statuses, to any of the possible operating statuses (active / passive) handing
over the substation control to any of the Control Stations. This will be the only command
accepted by 1CPT when in passive status.

Also, provided the TCP/IP connection between both 1CPT devices is active, launching the
status change command on a 1CPT from its associated HMI will suffice, as the command will
be transferred to the other 1CPT, through their communications channel. Moreover, this
communication between both CPTs will allow that, no matter over which 1CPT the system
switch over or reset command is initially executed, the sequence of the change in activity status
will always be initiated in the active 1CPT, which is set to passive in order to prevent both
CPTs from being in active status. Then, the passive 1CPT switches to active status.

This orderly redundant system switch over or reset sequence, in which the active 1CPT sets to
passive first, and then, the passive 1CPT sets to active, will prevent the loss of changes from
level 1 devices.

As the manual switch over and reset must be able to be carried out over one 1CPT, even when
no communications exist between both 1CPT, the status of the 1CPT over which the command
is issued (passive mode o active mode) and the status of communications between both 1CPT
must be taken into account and, in case the latter is not available, the status of communications
between the 1CPT and level 1 devices.

Therefore, two situations are contemplated for the manual redundant system switch over and
reset processes as a function of the status of communications between both 1CPT devices:

a) If communications between both CPTs is established, manual switch over and reset
commands can be issued from any Operation HMI, so as to guarantee that the status
change sequence of both 1CPT devices, initiates with the setting to passive mode of
the active 1CPT followed by the setting to active mode of the passive 1CPT. This
orderly sequence will be achieved through command transfer between both CPTs.

M1CPTA2005I
6-137 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

b) If communications between both CPTs is not established, system switch over or reset
must be carried out in sequence:

- First, the active 1CPT is set to passive.

- Then, the passive 1CPT is set to active.

If the sequence above is not taken into account, when no communications is established
between both 1CPT devices and a manual command is issued to set the passive 1CPT to
active mode the command will be blocked in case this 1CPT detects level 1 line activity, which
indicates that the other 1CPT is active at that very moment.

As for manual switch over and reset commands, it must be guaranteed that the automatic
switch over mechanism remains disabled during the whole manual switch over and reset
process, whether communications are established between both CPTs or not. In this way, the
1CPT that has manually set to passive mode is prevented from setting back again to active
mode, by the action of the automatic switch over mechanism.

Once the manual switch over or reset process is completed, the automatic switch over
mechanism will be enabled again.

6.17.3.d Bay Device Communications

• IEC-61850 Devices
Protection devices will be connected through switches with both primary and secondary 1CPTs.

Only one of the 1CPT devices (the Active 1CPT) will interrogate bay devices, enabling the
Report Control Blocks and retrieving all changes and refreshed signals, measurements and
meters allowing the execution of operations on the same. The Passive 1CPT will also be
connected to bay devices, but only to monitor level 1 activity, namely, if there are enabled
RCBs.

CPTs are continuously checking whether there is level 1 line activity or not, in order to be able
to decide whether to switch over or not when there is no communications between the 1CPTs.
To this end, the task in charge of the redundancy will ask in a continuous fashion the task un
charge of device interrogation whether there is level 1 line activity or not. The task in charge of
device interrogation will be based on the existence of enabled RCBs (only the Active 1CPT
enables the RCBs) and device MMS associations, using the following criterion:

• It is deemed there is activity in level 1 lines when:

o At least one RCB is enabled.
o At least one report has been received from the last interrogation of activity
in level 1 lines.
o If there are no device MMS associations. This case indicates there is
activity because there is no point in trying to switch if there is no connection
with any bay device.
- It is deemed there is NO activity in level 1 lines when:
o There are no Report Control Blocks.
o All the RCBs are disabled.

M1CPTA2005I
1CPT: Substation Central Unit 6-138
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

In the level 1 communications set up status, the 1CPT tries to determine whether there are
communications set up with level 1 devices. To this end it checks whether there are MMS
associations established.

- It is deemed there are communications with level 1 devices when the 1CPT has
been successful in establishing any MMS association with at least one bay
device.
- It is deemed there are NO communications with level 1 devices when the 1CPT
has not been successful in establishing any MMS association with at least one
bay device.
• PROCOME Devices
Devices are wired through fibre optic links to 4CCN type ZIV concentrator / diffuser devices,
which in turn are provided with two main fibre optic ports to allow for the connection, via fibre
optic links, to the Primary 1CPT and Secondary 1CPT. In case there exist CICs, the
connections will be made to CIC FO ports.

Only the active 1CPT will carry out the control interrogation cycle over bay devices, retrieving
all changes and refreshed signals, measurements and meters; and allowing the execution of
operations on the same. Also, only the active 1CPT will allow the transparent connection of the
Zivercom© through it to get access to protections.

6.17.3.e Remote Control Communications

As it is a redundant installation and there exists a switch over possibility between the two
Control Stations, the modem connection to link the COS (remote control station, SCADA,…)
must be shared through a multiplexer device, to allow for both 1CPTs to be connected to the
modem.

Both 1CPTs will receive messages from the COS through the connection to the multiplexer
device, but only the 1CPT active at that time will respond.

On the other hand, a system switch over or reset will not be possible by commands issued from
the COS, and the Operation HMI must be used for that.

As mentioned above, the loss of communications with the Remote Control will not imply
an automatic system switch over.

6.17.3.f Operation HMIs

The control system consists of one or more Operation HMIs:

− In case of one Operation HMI, it will be connected to the Active 1CPT.

− In case of two Operation HMIs, the HMI connected to Primary 1CPT is referred to as
Primary HMI, and the one connected to the Secondary 1CPT, Secondary HMI.

Also, if the 1CPT is active, the applicable HMI will be Active, namely, and it will be the only fully
functional HMI.

M1CPTA2005I
6-139 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The manual switch over or reset of both 1CPTs can be carried out from any of the Operation
HMIs provided there is communication between said devices. That is, commands to switch the
Primary 1CPT to passive mode and the Secondary 1CPT to active mode, or system reset,
switching the Primary 1CPT to active mode and the Secondary 1CPT to passive mode can
be issued either from the Primary HMI or from the Secondary HMI, no matter if they are in
active or passive mode. Of course, in case there is only one HMI, this will only be able to
switch the Active 1CPT to passive mode, which will result in the other 1CPT being switched to
active mode.

Both HMIs must allow to perform all the operations and data consultations when Active.
However, when in passive mode, commands over the substation cannot be issued, except for
redundant system switch over or reset commands.

An HMI in passive status will receive in real time, provided the connection between both 1CPTs
is operative, every new event and alarm received by the active 1CPT from bay devices or
generated by any Central Unit logic device, as well as bay device refreshed data.

The Operation HMI will be considered a non-critical system device, so that a failed Primary HMI
does not imply system switch over. This does not reduce the operational capacity of the system
for if any operation must be carried out, the redundant system can be switched over from the
Secondary HMI and, once the operation is completed, reset back the redundant system.

6.17.4 Configuration Parameters

6.17.4.a Redundancy Types
Within the DUAL configuration Central Unit, the 1CPT features two types of HSB redundancy:
• Type 1 HSB Redundancy
It is a redundant system for conventional substation architectures with PROCOME using serial
type level 1 communications protocol. The system consists of two 1CPT coordinated with each
other (primary 1CPT and secondary 1CPT) linked via a dedicated serial communications
channel separate from level 1 communications network or via the substation local net.

HSB redundancy operates as follows:

- Mode 1: In this mode of operation both 1CPT relays will have different IP address to
allow the simultaneous connection of web clients. Both Local Operations Consoles
will be available (Primary 1CPT console and secondary 1CPT console), only one
being Active (the active 1CPT console at that time) providing the operator with full
operativeness via Web Client connection to the IP address of the active 1CPT. The
other console remains in Passive state showing substation events and alarms via
Web Client connection to the IP address of the passive 1CPT. This mode
corresponds to the a value of 0 for the parameter TipoRedundaHSB of the
redundancy configuration file (redunda.cfg).

M1CPTA2005I
1CPT: Substation Central Unit 6-140
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

• Type 2 HSB Redundancy

It is a redundant system for substation architectures based on standard IEC-61850. The system
consists of two 1CPT coordinated with each other (primary 1CPT and secondary 1CPT) linked
via a dedicated communications channel (serial or Ethernet) separate from the level 1 IEC-
61850 communications network (Ethernet network). In this case of redundancy both 1CPT
relays the real time database is updated all the time via their common communications channel.

Two modes of operation are available for this type of HSB redundancy:

- Mode 1: In this mode of operation, the primary 1CPT and secondary 1CPT have their
own IEC-61850 substation data bus IP address. Only one 1CPT will be Active carrying
out typical 1CPT functions, as well as monitoring given critical variables, whereas the
other 1CPT will be in stand by ready to take over control of the substation when a
failure is detected. Both 1CPT relays can gain access to a web client connection to the
Integrated Web console so that the local operator can read the status of all substation
elements, events and alarms in both operations Consoles, but commands can only be
executed and settings changed from the Active 1CPT Integrated Web Console at that
time. This mode corresponds to a value of 2 for the parameter TipoRedundaHSB of
the redundancy configuration file (redunda.cfg).

- Mode 2: In this mode of operation the primary 1CPT and secondary 1CPT share the
same MAC address and IP address (virtual addresses) within the IEC-61850
substation data bus. Virtual MAC and IP addresses will only be activated in the active
1CPT at that time and will be the addresses used within the IEC-61850 substation
data bus with the rest of substation IEDs, as well as enable the web client connection
to the Active 1CPT Web Console. Therefore, the local operator will only have access
to the Active 1CPT Web Console.

However, each 1CPT will feature its own MAC address and IP address to carry out the
rest of the tasks derived from HSB redundancy, as well as maintenance operations
over the 1CPT devices themselves.

This mode corresponds to a value of 3 for the parameter TipoRedundaHSBof of the

redundancy configuration file (redunda.cfg).

M1CPTA2005I
6-141 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.17.4.b Configuration Parameters

Below are the main configuration parameters. For a description of the rest of the parameters
and the configuration file format, please refer to the applicable chapter in the appendix.

- InterfaceCanalRedundante: Interface of the redundant channel to connect both

Central Units. It states whether the communications between both Central Units is
made through serial port (0) or network, and this can be LAN1 (1) or LAN2 (2). If it is
not configured, the default value is 0.

- UsaEntSalDig: Denotes whether digital inputs and outputs are used (1) or not (0) to
interchange the redundancy status of both Central Units. If it is not configured, the
default value is 0. This parameter is only available for 1CPT.

- DirIPOtroCPT: In case of a 1CPT (serial redundancy): The Secondary 1CPT does

not use this parameter, and the Primary 1CPT uses it as base address in order for the
DHCP to generate an IP address for the primary and the secondary. For the 1CPT it
will be 198.168.1.1.

In case of CPTs with network redundancy, the IP address of the other 1CPT will be
configured in both CPTs.

- TipoRedundaHSB: This field states the HMI connection considered for each Hot Stand
By type of redundancy (see section 6.15):
 HSB type 1 redundancy:
− If it is 0 (zero), there are two HMIs, each connected to one 1CPT.
 HSB type 2 redundancy (1CPT):
− If it is 2, there are two HMIs, each connected to one of the CPTs, each with
its IP and MAC address.
− If it is 3, there is only one HMI connected to the Active 1CPT at that time.
Said HMI will be connected to a single IP address that is the one taken by
the Active 1CPT at that time (as well as a single MAC address if desired). In
this way, the active 1CPT will always be perceived as a single device, with
the same IP and the same MAC.

- VirtualIP: IP address of the Active 1CPT in HSB type 2 redundancy. In case this
address is to be used, parameter TipoRedundaHSB must be 3. Otherwise this IP
address will not be used. If it is not configured, this IP address will not be used by
default. This parameter is only available for 1CPT.

IMPORTANT: in case this address is used and, furthermore, a web HMI exists,
this same IP address value must be configured in field “ServerCurrentIP” of the
web HMI configuration file “ConsoleBaseConfig.xml” (refer to the CWE -
Embedded Web HMI - manual).

M1CPTA2005I
1CPT: Substation Central Unit 6-142
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

6.18 Substation Configuration Server: UCSConf

The 1CPT incorporates the function of IEC61850 substation configuration server, via module
UCSConf. Module UCSConf will operate as configuration server for all IEC61850 IEDs that
constitute the substation automation and control system, keeping a centralised database with
configuration files SCL (files CIDs/SCDs in XML format) for each of them (including the Central
Unit itself).
IED configurations are distributed from the UCSConf to the IEDs themselves but always through
operator manual operation.

Also, UCSConf module continuously checks IED configuration and parameterisation changes
with the data stored in the module database, highlighting the differences detected.

UCSConf module is supported by two sub-modules that cooperate with each other to provide
the function of IEC61850 configuration server. One of the two sub-modules is a part of the
Central Unit application itself and, therefore, resides in the 1CPT relay, but the other sub-
module resides in the PC that operates as substation Workstation. The UCSConf sub-module
that resides in the 1CPT is in charge of checking via IEC61850 substation bus the parameters
that maintain parameterisation and configuration revisions in each substation IED and, also,
provides functions for the validation and activation of a new CID file pre-stored in the IED.

For its part, the UCSConf sub-module (UCS-Conf.exe software), outside the 1CPT, will be the
UCSConf database manager. This will be in charge of handling the substation configuration files
(SCD file) and IED configuration files (CID file). Also, it will keep a database centralised in the
PC Workstation with the latest revisions of the substation SCD and CID files.

This second sub-module will be linked on the one hand to the sub-module that resides in the
1CPT to capture in real time revised parameterisation and configuration data of IEDs connected
to the 1CPT, and will be linked to the UCSConf web interface at the request of the operator and
transmit updated data of the UCSConf database and will be linked to the IEDs to send or
retrieve CID configuration files via FTP protocol.

After completing the IED configuration and parameterisation stage, the engineering and
configuration tool will generate the SCD file, which gathers the final CID files of all substation
IEDs, and will later be uploaded to the UCSConf module. Once the SCD file with the substation
configuration is uploaded to the UCSConf module, this will operate as configuration provider for
all substation IEDs and operators.

M1CPTA2005I
6-143 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 6. Description of Operation

The UCSConf configuration server will have a web interface with a main page accessible (via a
control button) from the System Status Overall Screen part of the Central Unit Web Console
and from the main menu.

UCSConf module screens will show the status of the UCSConf module itself and the
configurations of all substation IEDs.

Operations available to the operator from the UCSConf WEB page are:

- Uploading substation SCD file to the UCSconf database, via USB or via FTP.
- Downloading substation SCD file from the UCSconf database, via USB or via FTP.
- Uploading the CID file of a substation IED to UCSconf database, via USB or via FTP.
- Downloading the CID file of a substation IED from the UCSconf database, via USB or via
FTP.
- Transfer of the CID file of a substation IED from the UCSconf database to the IED via
FTP, validation and activation of the CID file in the IED.
- Transfer of the CID file of a substation IED from the IED itself to the UCSconf database
via FTP.

6.19 Maintenance Options

A number of options referred to as maintenance options are available in the relay menu. Said
options are not commonly used and must be handled by qualified personnel, and are protected
by a password well differentiated from the rest. Below are the different currently available
options:

- Date and Time: allows to change relay date and time from the keyboard.
- Language: allows to change menu language as well as the language of the information
shown from the different options.
- Software Update: allows to update central unit application software (file ucs.exe),
copying it from a USB disk inserted into the relay port.
- Test Mode Activation: only available for manufacturer use.
- Password Change: allows to change the password for the relay maintenance menu.

M1CPTA2005I
1CPT: Substation Central Unit 6-144
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 7. Alphanumeric Keypad and
Display

7.1 Alphanumeric Display and Keypad ..................................................................... 7-2

7.2 Keys, Functions and Operation Mode................................................................. 7-3
7.3 Function Access Using the Keypad .................................................................... 7-6
 Chapter 7. Alphanumeric Keypad and Display

7.1 Alphanumeric Display and Keypad

The liquid crystal alphanumeric display has a
4-row by 20-character matrix. It displays
information about IED alarms, settings,
metering, states, etc. There are 4 auxiliary
function keys (F1, F2, F3 and F4) under the
display. The next section explains their
functions. Figure 7.1 shows the default graphic
display and the function keys.

Figure 7.1: Alphanumeric Display.

• Default Display
As you can see in figure 7.1, the default display shows the IED model, the date and the time.

During the start-up process, an icon can appear on the upper right corner of the screen
(alternating between and ) to show that the different software modules that constitute the
relay are being initiated (as well as first update of the real time database).

Finally, to point out that if the removable USB device is connected, the corresponding icon
will appear to the right of the second line.

• Keypad Associated with the Display

The keypad consists of 16 keys arranged in a 4 x 4 matrix.
Figure 7.2 shows the layout of the keypad.

In addition to the keys corresponding to the digits (keys from

0 to 9), there are the selection keys (↑ and ↓), the
confirmation key (ENT), the escape key (ESC) and the
contrast key ( ).

Figure 7.2: Keypad.

M1CPTA2005I
1CPT: Substation Central Unit 7-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 7. Alphanumeric Keypad and Display

7.2 Keys, Functions and Operation Mode

This section explains the functions of the keys, both the ones associated with the alphanumeric
display as well as those on the keyboard.
• Keypad

Confirmation Key
Key ENT is used to confirm a selection or after changing settings.

Escape Key
The ESC key is used to quit a screen in case no settings changes are required or
to quit a data screen or go back to previous menus. In any case, pressing this key
the system goes back to the previous screen.

Display Selection Keys

Use the arrow keys to browse through the different options of the menus available
in the 1CPT.

Contrast Key
Press this key to modify the contrast level of the 1CPT display.

M1CPTA2005I
7-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 7. Alphanumeric Keypad and Display

• Function Keys

When this key is pressed,

you access a looped
display with information
about the 1CPT. The
number of screens
depends on the amount of
separate modules installed
in the 1CPT.

The first display shows information about the executable file:

• Equipment Model.
• UCS Software Model.
• UCS Software Version.
• UCS Software Checksum.
• Version of the multitask operating system.
• Version of the TCP library.

The second screen shows

data on the 1CPT
operative system:

• Version of the real

time operative
system.
• Version of the
application
programming
interface layer.

Next screen shows data on the rest of DLL type 1CPT modules (Dynamic Link
Library:

• Version of first DLL module.

• Version of second DLL module.
• ...

In the next screen, shows

information about the
status of certain of the
1CPT's internal
parameters:

• The configuration’s IP address.

• Size (in bytes) of the logic.
• Size (en bytes) of the free memory.
• Status of the sockets: C = Central, P = Protection, M = Monitor.
• 00 = Waiting for connection; 03 = Connection established.

M1CPTA2005I
1CPT: Substation Central Unit 7-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 7. Alphanumeric Keypad and Display

A new screen shows

information on the
identification number of
each 1CPT software
component, according to
ZIV internal identification
system:

• Operative system
drawing number.
• UCS/RTU application
drawing number.
• Drawing number of
the rest of DLL type
modules.

Next screens show

information on the
checksum codes for each
1CPT software component:

• Operative System
Checksum.
• UCS/RTU application Checksum.
• Checksums for the rest of DLL Type Modules.

Finally, we go back to the default display, access to which can again be gained
pressing ESC.

Pressing this key, while at 1CPT home screen, displays a screen requesting the
password to reboot the relay. After introducing the correct password, the operator
is prompted to confirm reboot, via F1 and F2 keys.

M1CPTA2005I
7-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 7. Alphanumeric Keypad and Display

7.3 Function Access Using the Keypad

Pressing any key (except ESC and
contrast keys), while at home screen,
displays the main menu. After previous
selection, a number of submenus
arranged by levels are associated to
this main menu.

The figures below schematically represent relay menu architecture.

• Relay Status
This option of the main menu is used to
gain access to data of the two relay
network adapters, as well as data on
the status of relay synchronization with
an external GPS clock.

Network Adapter Data

For each network adapter incorporated
into the relay, the network adapter
name, the IP address, the sub-network
mask, the MAC address (hardware), the
internal adapter index, the DHCP client
status (Enabled or disabled) and the
default gateway IP address are shown
separately.

These data are shown in two windows,

and switching between windows is done
by pressing ↓ or ↑ key

DHCP client is a network service that

enables the relay to get IP addresses
automatically if its network is provided
with a DHCP server. Pressing ESC
displays again the menu Relay status.

These data are important for

maintenance operations: installation of
devices into the local network.

M1CPTA2005I
1CPT: Substation Central Unit 7-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 7. Alphanumeric Keypad and Display

External Clock Information

An option within the Relay status menu
shows information on the external GPS
clock used as a relay time
synchronization source, including the
status of relay synchronisation with the
external clock.
• Maintenance Options
Access to relay maintenance operations
via keyboard is restricted by the use of
a specific password. Factory set
password for maintenance is 0412.

Users logged on as maintenance user

can modify the password. The figure
shows the available options.

M1CPTA2005I
7-7 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 7. Alphanumeric Keypad and Display

M1CPTA2005I
1CPT: Substation Central Unit 7-8
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 8. Receiving Tests

8.1 General................................................................................................................ 8-2

8.2 Preliminary Inspection ......................................................................................... 8-2
8.3 In Service Test .................................................................................................... 8-2
8.4 Start Up ............................................................................................................... 8-3
8.5 Port Test .............................................................................................................. 8-4
8.6 LEDs Status ........................................................................................................ 8-5
8.7 Installation ........................................................................................................... 8-5
 Chapter 8. Receiving Tests

8.1 General
Improper handling of electrical equipment is extremely dangerous; therefore, only skilled and
qualified personnel familiar with appropriate safety procedures and precautions should work
with this equipment. Damage to equipment and injury to personnel can result when proper
safety precautions are not followed. The following general safety precautions are provided as a
reminder:

• High magnitude voltages are present in auxiliary supply and metering circuits even after
equipment has been disconnected.
• Equipment should be solidly grounded before handling or operating.
• Under no circumstances should the operating limits of the equipment be exceeded
(auxiliary voltage, current, etc.).
• The auxiliary supply voltage (AC or DC) should be disconnected from the equipment
before extracting or inserting any module, otherwise damage may result.

The number, the type and the specific characteristics of the acceptance tests are model
dependent and are detailed in the following table.

Preliminary Inspection
“In Service” Test
Ports Test
1CPT
LEDs Supervision Test
Installation
Start Up

8.2 Preliminary Inspection

Examine the following aspects to conduct the preliminary inspection:

• The relay is found in perfect physical condition, all of the parts are securely attached and
no assembly fasteners are missing.
• The front board is perfectly centred and aligned.
• The protective cover and the box are in perfect condition.
• The model numbers and specifications agree with the equipment order.

8.3 In Service Test

Verify the In Service/Out of Service contact closes when the auxiliary power supply voltage is
removed from the equipment and opens when the auxiliary power supply voltage is restored.

M1CPTA2005I
1CPT: Substation Central Unit 8-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 8. Receiving Tests

8.4 Start Up
The 1CPT, by default, leaves the factory with the software and setup used for factory tests. The
software will not as a general rule coincide with the software requested by the client. Also, test
setup is not the setup required by the installation.

With the test settings, upon connection of the 1CPT, the central unit program is automatically
run, showing the date and time on the front display. Also, a continuous blinking of LEDs
associated to communication ports connected to already set up position equipment takes place.
LEDs will blink red when transmitting but no receiving. This is normal, as substation equipment
will not match equipment setup.

If the 1CPT features the integrated Web Console function, the 1CPT can be connected to a PC
via the LAN to which the 1CPT is connected, for which the PC’s MS Internet Explorer browser
must be used for connection to the 1CPT integrated Console web page. In this way the good
operation of the complete system can be checked.

After the 1CPT has been updated with final configurations and software adequate for the
system requirements, bay devices must be connected to the 1CPT and then check the proper
operation of the complete system.

The system features a method to check data coherence (models and configurations) between
the Central Unit application and the Integrated Web Console application, both installed within
the 1CPT. The method is used for checking whether the console and central unit belong to the
same substation and whether both units have been set up with the same equipment.
Communication between both equipment is established after completion of the step above,
provided the consistency process is found to be correct.

To check the proper operation of the system, first browse the 1CPT integrated Console web
page using MS Internet Explorer, where all the Central Unit Operations Console functions are
shown. Select the window SIPCO status from the main menu and check for communications
errors with the different system devices. This guarantees communication setup is satisfactory.

Once equipment has been checked for proper operation with the setup used for the test, final
setup and software adequate for the installation requirements shall be loaded. Now position
equipment may be connected to the 1CPT.

Once the 1CPT has been updated with final setup and software, the proper operation of the
system shall be tested. To this end, all possible signals the substation can generate shall be
produced checking that said signals are correctly updated on every console screen (if any) or
on the control room screens (if any). If any error should occur, the system setup shall be
checked. If the error persists, please contact your supplier.

M1CPTA2005I
8-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 8. Receiving Tests

8.5 Port Test

As said above, the 1CPT leaves the factory set up for the test, and this setup will not coincide
with the setup required for the intended installation. In order that communication ports can be
checked for proper operation adequate setup must be loaded connecting the equipment to the
proper ports. Transmission and reception of said ports must be checked through the LEDs.

• If equipment should be connected to port 3, P3 RX and TX LEDs shall be on when 1CPT is

retrieving information from equipment related to this port.
• If equipment should be connected to port 4, P4 RX and TX LEDs shall be on when 1CPT is
retrieving information from equipment related to this port.
• If the remote port should be used for communication with Zivercom© program, P2 Rx, Tx
LEDs shall be on when transparent communication is established with one equipment.
• If the remote port should be used for communication with the control room, P1 Rx, Tx
LEDs shall be on.

Network port may be checked in two different ways. If the 1CPT model features Central Unit
with Integrated Web Console function, the 1CPT can be connected to a PC via the LAN to
which the 1CPT is connected, for which the PC’s MS Internet Explorer browser must be used
for connection to the 1CPT integrated Console web page and then check for proper connection.
Also, in the SIPCO screen check that all devices connected to the 1CPT are properly displayed.

If the 1CPT model only features the RTU function, therefore the Integrated Web Console not
being available, a PC will be connected to the 1CPT via the system LAN and a ping to the 1CPT
will be sent writing from the PC the following command: PING MMM.NNN.XXX.YYY, where
MMM.NNN.XXX.YYY is the 1CPT IP address, checking that the 1CPT responds to ICMP
messages generated by the PC PING programme.

This network port checking procedure must be repeated for the second 1CPT network port.

M1CPTA2005I
1CPT: Substation Central Unit 8-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Chapter 8. Receiving Tests

8.6 LEDs Status

If the 1CPT model features Central Unit with Integrated Web Console function, the default
configuration of user LEDs to the left of the relay front panel will be as follows:

- 1CPT Alarm. LED lights up when a critical error occurs in the 1CPT. It is off under normal
conditions.
- Time SYNC. This LED lights on when communications with the GPS clock fail.
- Coms IEDs. This LED is on when communications with at least one level 1 device fails.
- Coms IHM. This LED is on when the 1CPT Integrated Web Console application is not
available. This LED is on at start-up, and goes off after a few seconds if the 1CPT
Integrated Web Console application initialises correctly.

If the 1CPT model features the RTU function, the default configuration of user LEDs to the left
of the relay front panel will be as follows:

- 1CPT Alarm. This LED lights on when a critical 1CPT error occurs. It is normally off.
- Time SYNC. This LED lights on when communications with the GPS clock fails.
- Coms Telem. This LED is off when starting up and lights on if after a while,
communications with the remote control is not established.
- Coms IEDs. This LED is on when communications with at least one level 1 device fails.

8.7 Installation
• Location
The location where the Terminal Unit is to be installed should meet the following minimum
conditions to ensure correct operation, long service life, ease of installation and ease of
maintenance:

• Absence of dust
• Absence of dampness
• Absence of vibration
• Adequate lighting
• Easy access
• Front panel in an upright and vertical position

Mounting should be in accordance with the instructions regarding installations in the dimension
diagram (at the end of this Instruction Manual.
• Connection
Terminal 1 should be solidly grounded to ensure disturbance filtering circuits operate properly.
The wire used for grounding these terminals should be stranded 14 AWG. Ground wire length
should be minimized and should not exceed 12”. The ground terminal of the enclosure located
on the rear panel of the equipment should also be grounded.

M1CPTA2005I
8-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Chapter 8. Receiving Tests

M1CPTA2005I
1CPT: Substation Central Unit 8-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
A. Configuration Files for CPX /
CPP / CPT
 Annex A. Configuration Files for CPX / CPP / CPT

A.1 Introduction
The various files for the configuration of the central substation unit shall be documented as
follows. Many of these define digital signals, controls, writes, measurements and meters. To this
avail, its structure will be currently defined and shall be referenced each time they appear.
• DIGITAL SIGNALS (ISC)
The following data is provided:

NumISCs ,
ISC , Alarma , F_activ , F_desactiv , Neg , Bocina , (*)

(*) This is repeated for each digital signal from the device. There will be as many signals as
indicated under NumISCs.
• NumISCs: Number of digital signals from the device.
• ISC: Identifier of a digital signal from a device within the database in real time from the
Central Unit. The scope of this identifier shall be limited to the set of digital signals
associated to a device configured within the database of the Central Unit.
• Alarma: Alarm bit, which indicates if the signal is considered an alarm (1) or not (0).
• F_activ: Bit that filters activation, which indicates whether activation of the signal is
considered an incident (0) or not (1).
• F_desac: Bit that filters deactivation, which indicates whether activation of the signal is
considered an incident (0) or not (1).
• Neg: Bit that rejects alarm, which indicates if it deems the situation as alarm when the
signal adopts the value 1 (0), or when it adopts the value 0 (1).
• Bocina: Horn bit, which indicates whether the horn should sound (1) or not (0) when the
signal is activated, as long as this is considered as being an alarm (its alarm bit is set to
1). This bit shall appear, or not, in the corresponding file, depending on the version of the
application of the Central Unit. The type of horn that sounds is defined under the
configuration file “central.cfg” and shall be commented in section A.2.

Ex: 3,// Num. Digital Signals

0,0,0,1,0,0,
1,0,0,1,0,0,
2,1,0,0,0,1,

M1CPTA2005I
1CPT: Substation Central Unit A-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• CONTROLS (ISE)
The following data is provided:

Num
ISEs ,
ISE DirEq ISC Time Neg Dir EqOK ISC DirEq
, Est , Est , , , , OK , Fail ,

ISC , Doble , Num , Dir , ISC , Neg , TipoRespuestaMan (*)

Fail Blqs EqBlq Blq Blq do ,

(**)
(*) This is repeated for each of the device’s controls. There will be as many as indicated
under NumISEs.
(**) This is repeated for each blocking signal received from the corresponding control. There
will be as many as indicated under NumBlqs.

• NumISEs: Number of controls present in the device.

• ISE: Identifier of controls in the device.
• DirEqEst 1: Address of the device related to the command Status Signal.
• ISCEst: Identifier of Status Signal (signal that changes the status as a result of the
implementation of the control).
• Time: Implementation time (in msec.).
• Neg: Bit that rejects the Status Signal.
• DirEqOK 1: Address of the device related to the OK Signal.
• ISCOK: Identifier of the OK Signal.
• DirEqFail 1: Address of the device that the Failure Signal of the control belongs to.
• ISCFail: Identifier of the Failure Signal.
• Doble: Bit that indicates if it is a double control (1) or not (0).
• NumBlqs: Number of failed commands (maximum 4 failed commands per each control).
• DirEqBlq 1: Address of the device related to the failed command.
• ISCBlq: Identifier of Failed Control Signal.
• NegBlq: Bit that rejects the Failed control Signal.
• TipoRespuestaMando: Indicates the type of treatment that the Central Unit will provide as
a response to the command execution, i.e., how the CONTROL task, or main task
pertaining to module IEC61850 will send a reply from the control to the task that required
this action processing the next queued command:
o 0: Normal, i.e., it sends a response when the control finishes the task (default value).
 0.a) If either ISCOK or ISCFail have been configured, this sends the response
when it receives instructions from the relay with the CIN indicated by the latter.
 0.b) If ISCOK and/or ISCFail have been configured, this sends the reply when it
receives the ISCOK, ISCFail from the relay, or when it forwards the timeout Time.

1
The address field for IEC61850 devices will be the internal address in the real time database of the CPT and
shall be an integer ranging from 0 to 254, which will be configured by the user and will not be related to the IP
address of the device.

M1CPTA2005I
A-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

o 1: It only sends a reply when it receives an answer from the relay, but if ISCOK
and/or ISCFail have been configured, it continues to wait for some time until it
receives ISCOK or ISCFail before processing the next queued command in the
process.
o 2: If the ISCOK and/or ISCFail have been configured, it sends two replies, one as
soon as confirmation is received from the relay and the second one when the
ISCOK, ISCFail receives the relay or when the timeout Time has lapsed.

If this parameter has not been configured, it adopts the value 0 as a default value.

IMPORTANT: If a control is configured as type 1 or 2 and either ISCOK or

ISCFail HAVE NOT BEEN CONFIGURED, this control will behave as type 0.a.

Ex: 4,// Num. Controls

11,10,40,30000,0,10,56,10,54,0,1,10,59,0,0,
12,10,40,30000,0,10,56,10,54,0,1,10,59,0,0,
13,10,40,30000,0,10,56,10,54,0,1,10,59,0,0,
14,10,43,10000,0,10,43,10,-1,0,2,10,64,0,10,43,0,0,

• WRITES (ISS)
The following data is provided:

NumISSs ,
ISS , DirEq , ISC , Time , Neg , Analog , (*)

(*) This is repeated for each of the writes for the device. There will be as many as
indicated under NumISSs.

• NumISSs: Number of writes for the device.

• ISS: Identifier of the writes.
• DirEq 1: Address of the device related to the Status Signal for the writes.
• ISC: Identifier of the Status Signal.
• Time: Implementation time (in msec.).
• Neg: Bit that rejects the Status Signal.
• Analog: Analogue signal write Bit. The default value for all the writes is NO (0).

Ex: 2,// Num. Writes

0,10,-1,10000,0,0,
1,10,-1,10000,0,0,

2
The address field for IEC61850 devices will be the internal address in the real time database of the CPT and
shall be an integer ranging from 0 to 254, which will be configured by the user and will not be related to the IP
address of the device.

M1CPTA2005I
1CPT: Substation Central Unit A-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• ANALOGICAL WRITE (ISM)

The following data is provided:

NumISMs ,
ISM , MEA , (*)
DirEq

(*) This is repeated for each of the analogical writes of the device. There will be as
many as indicated under NumISMs.

• NumISMs: Number of analogical writes in the device.

• ISM: Identifier of analogical writes.
• DirEq: Address of the device related to the Measure associated to the write.
• MEA: Identifier of the measurement.

Ex:2,// Num. Analogical Writes

0,1,0,
1,1,2,

Note: the block that configures analogical writes (ISM) shall be included in the file DBASE.CFG, after the block
of configuration data for the meters belonging to the physical device, only if the existence of any analogical
write has been indicated in the block of settings of the general data belonging to the physical device.

• MEASUREMENTS (MEA)
The Central Unit can handle measurements in the following formats:

- Measurements in integer format of up to 16 bits with sign (PROCOME, DNP3.0, etc).

- Measurements in floating point format with simple precision (IEC 61850).
Measurements in Integer Format
The type of measurements that are forwarded by non IEC61850 device at ZIV level 1, are
digitally encoded by a 12-bit word and, hence, a linear-type conversion shall be required to
obtain the engineering values associated to each analogical measurement. To carry out this
conversion, the straight line that relates the range of values from –4096 to +4095, forwarded by
the ZIV relays, must be defined for each of the measurements configured at the Central Unit,
with the range of engineering values associated to the measurement. Hence, it will be essential
to know the full scale value defined in that relay for each of the analogical magnitudes to be
measured.
Measurements in Simple Precision Floating Point Format
This type of measurement, as forwarded by ZIV level-1 IEC61850 device, has a 32-bit format
and contains the actual engineering values associated to each of the analogical measurements.
Nevertheless, the Central Unit offers the possibility of carrying out a scaling of engineering
process values for these measurements.

M1CPTA2005I
A-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The following data is required for defining conversion slopes adjusted to engineering values:

NumMEAs ,
Pendiente , Origen , (*)

(*) This is repeated for each of the measurements carried out on the device. There will
be as many as indicated under NumMEAs.

• NumMEAs: Number of measurements carried out on the device.

• Pendiente (a): Conversion slope for the measurement (parameter a). See figure A.1-1.
• Origen (b): Origin of the Conversion slope (parameter b). See figure A.1.

Value_Measure
ment_Engineeri
ng =
(Value_Measure
ment_Device *
Slope ) + Origin.

Figure A.1: Conversion Slope for Measurements and Meters.

Ex: 2,//Num. Measurements

1.0,0,
0.00029304,0,

• METERS (CON)
The following data is provided:

NumCONs ,
Pendiente , Origen , (*)

(*) This is repeated for each of the meters on the device. There will be as many as
indicated under NumCONs.

• NumCONs: Number of meters on the device.

• Pendiente: Pending on the Conversion slope of the meter (parameter a). See figure A.1.
• Origen: Origin of the Conversion slope (parameter b). See figure A.1-1.

Ex: 1,//Num. Meters

1.0,0,

M1CPTA2005I
1CPT: Substation Central Unit A-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.2 Configuration File for CENTRAL Task: CENTRAL.CFG

This file contains a series of parameters that affect the CENTRAL task, which is in charge of the
start-up and monitorization of the Central Unit: settings related to the communications’ card,
setting of redundant units, settings related to the Central Unit and configuration of the digital
signals of the Central task (virtual device whose internal address on the database of the Central
Unit is number 257). This file is called “central.cfg”.

The digital signals of this logic equipment can amount up to 287, 300, 324 and even 345 (as a
function of the software version used, number of digital inputs of the CPX/CPP/CPT and GPS
used). For complete table, go to section 6.9 UCS as Virtual Equipment.

The file has the following format:

• Data Pertaining to Settings Made On Communications with Bay Device:
[Lines 2-6]

PerioSincr , SincroMS , FuenteSincro , TimeSincroOK , TimeSincroKO ,

PerioLectCon , TimeWaitAfterISE ,
PerioLectMed , NumCiclBajoUmbMinMedOK , UmbMinMedErr ,
PerioRecup , TimePreg , TimeReset , BitRetardo ,
TipoInterrog , BitReint , ToutCaract ,

• PerioSincr: Synchronization period for non IEC61850 device (in msec.).

• SincroMS: Indicates if msec units are forwarded in the synchronization to non- IEC61850
device. If result is 1 = they are forwarded; if 0 = they are not forwarded and it is
synchronized by resolution to hundredths. If no values are indicated, the default value will
be 0.
• FuenteSincro: Indicates the default source of synchronization for the CPX/CPT
(0=Protocol; 1=External clock /GPS). Each time the CPX/CPT is started this source will
be used for synchronizing purposes. If no values are indicated, the default value will be 1.
Once the functionality of this parameter is associated, there is the signal [257,276], which
indicates if the CPX/CPT is being synchronized by protocol (0) or by external clock /GPS
(1).
N.B.: This parameter does not exist in models 1CPX-A.
• TimeSincroOK: Indicates the time (in seconds) that the CPX/CPT will be receiving the
correct date/hour from the synchronizing source, in order to be considered as being
synchronized. This is only used when the CPX/CPT is being synchronized by the
external/GPS clock. If it is synchronized by protocol, as soon as the synchronization is
received, it will be immediately considered as being synchronized. This timing will be
operative when the external/GPS clock date/hour is accepted in the CPX/CPT
(“MaxRecupGPS” milliseconds, correctly receiving date/hour). If no information is issued,
the default value will be 1.
N.B.: This parameter does not exist in models 1CPX-A.
• TimeSincroOK: Indicates the time (in seconds) that the CPX/CPT remains without
receiving the date/hour correctly from the external clock/GPS, or without receiving
synchronizations by protocol, to be deemed as not being synchronized. This time will
begin to count, when the CPX/CPT is synchronized by the external clock/GPS, once the
date/hour from the external clock/GPS is deemed as being faulty at the CPX/CPT
(“MaxErrGPS” milliseconds without receiving the date/hour correctly). If no information is
added, the default value will be 1.
N.B.: This parameter does not exist in models 1CPX-A.
Signal [257,275] is associated to the functionality of both parameters, which indicates
whether CPX/CPT is synchronized (1) or non synchronized (0).

M1CPTA2005I
A-7 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex A. Configuration Files for CPX / CPP / CPT

• PerioLectCon: Meter readings period for meters (in msec.), only for non IEC61850
devices.
• TimeWaitAfterISE: Time (in msec.) that the CPX/CPT waits after implementing a
command, as long as the latter has received a signal of implemented order and/or failure
of order associated, in order that the implemented order signal and/or order failure signal
is deactivated and does not interfere in the implementation of the next command. (If no
information is added, the default value will be 0).
• PerioLectMed: Measurement reading period for broadcast interrogation (in msec.).
• NumCiclBajoUmbMinMedOK: Number of interrogation cycles that a measure must be
under the Minimum Threshold (defined under the next parameter) to be able to store this
under BD. A value other than 0 indicates the existence of the Control of Detection and
Filtering of Peaks, or Voltage Drops, and if set to zero (which is its default value), or if no
data is added (in which case it applies the default value, 0), this command will not be
taken into account.
• UmbMinMedErr: Minimum threshold below which a measurement can be considered as
being faulty. Its default value is 20 counts, and if no data is added, this will be the default
value.
• PerioRecup: Period for retries to recover a device under error (in sec.), only for non
IEC61850 devices.
• TimePreg: Waiting time between a response and the next interrogation (in msec.), only
for non IEC61850 devices. Its minimum value is 66 msec. This timing is applied if one of
the following two conditions takes place:
- If there is only one device in a port.
- If the message delay bit (*) is set to 1.
• TimeReset: Time that the CPX takes to reset when detecting an error (in msec.). This
field is valid only for FENIX software model for CPX. Nevertheless, it does not apply to
CPT.
• (*)BitRetardo: Bit that indicates if the forwarding of messages to devices must be delayed
(1) or not (0), only for non IEC61850 devices. This is only valid for FENIX software model.
• TipoInterrog: Type of interrogation (1 = Broadcast, 2 = Changes), only for non IEC61850
devices.
• BitReint: Bit that indicates if a retry is sent (1) or whether communications are reset (0)
when an error takes place during the device interrogation cycle, only for non IEC61850
devices.
• ToutCaract: Allowable timeout between characters to consider a frame as being correct.
If the separation between two consecutive bytes of a frame should exceed this value, the
frame will be deemed as being faulty (in msec.), only for non IEC61850 devices. The
default value used will be 15 msc. For communications with GSM modems, the value to
be configured must not be under 1500.

Ex: 60000,1,1,3,10,
20000,0,
5000,
5,66,5500,0,
2,1,15,

M1CPTA2005I
1CPT: Substation Central Unit A-8
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data Concerning Settings to Redundant Units: [line 8]

UCSRedund , TipoUCS , TipoRed ,

• UCSRedund: Bit that indicates if there is a redundant (1) CPX/CPT, or not (0).
• TipoUCS(CPX/CPT): Bit that indicates the type CPX/CPT: primary (0) or secondary (1). It
is only taken into account if there is a redundant CPX/CPT (previous bit set to 1).
• TipoRed: Bit that indicates the type of device network: star (0), or double redundant ring
(1).

Ex: 0,0,0,

• Data Pertaining to Settings Made On Each Station: [Line 10]

Modelo , TipoCPU , Watchdog , TipoEquipo ,

• Model: CPX/CPT hardware model (maximum number of characters: 15).

• TipoCPU: Code for the CPU model used by the CPX/CPT (0: ICP; 1: ADVANTECH
PCA-6155V/PCA6359; 2: CPU TEKNOR PCI-936, 6: CPU PCA6002, 7: CPU
IXP425). For 1CPX-A device families (16 bits), this parameter is automatically
calculated). For 1CPX-B (Windows CE) families, this must be adequately configured.
• Watchdog: Maximum time, in seconds, allowed for pressing the Watchdog to avoid the
latter from being enabled and causing a reset in the CPU. It is only used for
ADVANTECH, PCA6002 or IXP425 CPUs. The default time will be 10 seconds for
1CPX devices; and 50 seconds for 1CPT devices.
• TipoEquipo: Type of functionality incorporated by the CPT, which can be UCS (value
1), RTU (value 2) or both (value 0). If this parameter has not been configured, it will be
assumed that the CPT incorporates both functionalities (UCS + RTU).

Ex: 1CPXA03201000WA,6,10,0,

• Data Pertaining to GPS Clock Settings: [Line 11]

RelojGPS , ErrorDispers , MaxErrGPS , MaxRecupGPS , GPSVerificaIRQ ,

Port , Baudios , Paridad , Bits , BitsStop (Only if RelojGPS = 3 ó 4)

GestionaST , NotificaST ,

NumEDSincro , (Only if RelojGPS = 5)

NumIRQ ,

• RelojGPS: Indicates if it has a GPS clock, and the type in question. 0: Not available; 1:
IKOR Parallel PC; 2: IRIG-B; 3: IKOR series 232; 4: GC14 series 232; 5: Synchronization
to the nearest hourly quarter by Pressing Digital input; 6: SNTP 3 (does not apply to the
rest of the settings under this section).

3
The SNTP-type GPS has its own configuration file, “SNTP.CFG”, within the CPT.

M1CPTA2005I
A-9 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex A. Configuration Files for CPX / CPP / CPT

• ErrorDispers: Bit that indicates if there is a dispersion error in the GPS (1), or not (0).
• MaxErrGPS: Time that the GPS has an error sign in order to be assigned as being faulty
and to run the time internally. In ms. 500-300000 ms. Default value 30000 ms.
• MaxRecupGPS: Time required for correct performance of GPS clock after displaying
error sign, to be considered correct. In ms. 500-300000 ms. Default value 30000 ms.
• GPSVerificaIRQ: Time allowed without entering interruptions. In seconds. 5--> sec.
Default value 30 seconds. For type 5, this value is used for the time (in seconds) that
must lapse without a synchronism pulse before activating the communications Failure
signal with the GPS; for this case, the default value is 1800 seconds, which amounts to
30 minutes.
• Port: Serial port where the GPS will be connected (this field will only apply to types 3 and
4).
• Baudios: Baud for the serial port (this field will only apply to types 3 and 4).
• Bits: Number of data Bits (this field will only apply to types 3 and 4).
• Paridad: Type of parity (this field will only apply to types 3 and 4).
• BitsStop: Number of stop bits (this field will only apply to types 3 and 4). .
Note: the fields Port, Bauds, Bits, Parity and BitsStop shall only be applied in the cases of type 3 and 4
clocks. They must not be applied to the rest of the clocks. If these fields are configured in the case of type
1, 2 and 5 clocks, an error will arise as regards the Summer/Winter timetable.
• GestionaST: This indicates if the GPS clock handles the Summer/Winter timetable (1) or
not (0). By “handling”, this means it increases the hour during the summer and decreases
the same in the winter.
• NotificaST: This indicates whether the GPS clock informs if it is in summer or wintertime
timetable (1) or not (0).
Note: For Type 2 GPS clocks (IRIG-B), this value will currently be set to 0, even if the
IRIG-B clock could provide this information, the card processing the IRIG-B signal,
located in the central unit, FILTERS this information.
• NumEDSincro: This is the digital entry number [1-8] which is going to be used to receive
the synchronizing pulse of the nearest hourly Quarter. Synchronization only takes place
with the leading edge. This parameter must only be set for type-5 clocks.
• NumIRQ: IRQ Number used for communicating with the GPS IRIGB. For CPXs that end
in 2WA, the value is 12; and for those that end in 3WA, the value is 7.

Ex: 3,1,30000,30000,COM4,9600,e,8,1,1,1,12,

M1CPTA2005I
1CPT: Substation Central Unit A-10
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data Concerning Coherent Settings and Blocking/Unblocking of Signals due

to Excessive Number of Changes [Line 12]

Coherencia , CoherenciaAlr , NumMaxSuc ,

NumCambDes , NumCambAct , TimeActDes ,

• Coherencia: Bit that indicates whether information on the coherent system must be
activated (1) or not (0).
• CoherenciaAlr: Bit that indicates whether alarm coherent system must be activated (1) or
not (0). It does not currently have an associated functionality. Default value, 0.
• NumMaxSuc: Maximum number of events that are stored in the Central Unit files. By
default, this stores 500 events. The maximum number of accumulated events is limited to
2000.
• NumCambDes(*): Maximum number of changes for a signal in the Central Unit’s real time
database, within the time configured within the setting "TimeActDes" to deactivate it
(block it).
• NumCambAct(*): Maximum number of changes for a signal, in the Central Unit’s real time
database, within the time configured in the setting "TimeActDes" to activate it when it was
previously deactivated.
• TimeActDes(*): Time (in sec.) for activation/deactivation of signals due to excessive
number of changes on the UCS.

(*) If any of the above three values should be configured to 0, the functionality for
blocking/unblocking of signals due to excessive number of changes on the UCS is deactivated.

Ex:
1,0,500,10,10,2,

• Data Pertaining to Horn Settings [Lines 13-14]

TipoBocina ,
DirEq , ISE , DCO ,

• TipoBocina: Type of acoustic alarm (horn): 0 = No horn, 1 = Central Horn, 2 = HMI

Horn (reserved, and not available in WEB HMI). If a signal is considered an alarm (alarm
bit set on 1), the type of horn indicated under this parameter will set off.
• DirEq 4: Address of the device related to the command that activates the horn.
• ISE: Identifier of this command.
• DCO: DCO of the command.

Ex:
0,
30,0,2,

4
In IEC61850 devices, the field of address for the device shall be the internal address of the device as per the
real time database of the CPT, and shall be an integer ranging from 0 and 254, to be configured by the user and
will not be related to the IP address of the same.

M1CPTA2005I
A-11 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data for Signals from the Central task

The data related to the different signals of the Central task, as well as the General Blocking of
Substation Local, are configured.

NumISCs , NumISS , HabBlqGralLocSET , EqBlq , IscBlq , NegBlq ,

• NumISCs: Number of digital signals from the device.

• NumISSs: Number of writes from the device.
• HabBlqGralLocSET: This parameter indicates whether the functionality of the General
Blocking of the substation's Local is enabled (1). If the value set is 0, this means that it is
not enabled. If it is enabled, when the signal configured as follows is set to 1, the
commands are blocked from the remote control; if, on the contrary, it is set to 0, the
remote controls are accepted, but the HMI commands are blocked. The default value for
this field will be 0.
• EqBlq: Device that the blocking sign belongs to.
• IscBlq: Identifier of blocking signal.
• NegBlq: Indicates if the above signal has been rejected (1) or not (0).

Ex: 308,4,1,257,300,0,

• Configuration Data for the ISCs from Central Task

These are defined as laid out under section A.1: [lines 16-21]

Ex: 308,4,1,257,300,0,// Nº Signals, Nº Writes

0,1,0,0,0,1,
1,1,0,0,0,1,
2,1,0,0,0,1,
…
307,1,0,0,0,1,

• Configuration Data for the Writes from the Device

These are configured according to the description set out under section A.1. The first 4 writes of
the central task enable acting, in the same order, directly on the four digital outputs of the CPX:
[lines 23-27]. For the CPT up to 8 digital outputs will be available.

Ex: 4,// Num. writes

0,257,-1,10000,0,0,
1,257,-1,10000,0,0,
2,257,-1,10000,0,0,
3,257,-1,10000,0,0,

The file remains as follows:

[1] # CTL CARD SETTINGS

[2] 60000,1,1,3,10,// Period for device synchronizations. ( x 1 ms )
[3] 20000,0,// Period for meter reading. ( x 1 ms )
[4] 5000, // Period for Measurement reading. ( x 1 ms )
[5] 5,66,5500,0, // Period Recup, Time Preg, Time Reset, Bit Retard
[6] 2,1, //Type int.: 1=BROADCAST, 2=CHANGES; 1=Retry, 0=Reset CU
[7] # Settings for redundant units
[8] 0,0,0, // CPX backup ?, CPX primary, Network type (0) star. (1) ring
[9] # SETTINGS FROM CENTRAL

M1CPTA2005I
1CPT: Substation Central Unit A-12
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

[10] 1CPXA03201000WA,2,10,//CPX/CPP Model, CPU Type, Watchdog Time

[11] 3,1,30000,30000,15,COM4,9600,e,8,1,1,1,
[12] 1,0,500, //Coherence, Coherence Alr, NumSuc
[13] 0, //Type of Horn
[14] 30,0,2, // Command for horn
[15] # CONFIGURATION OF CENTRAL TASK ISCs
[16] 308,4, 1,257,300,0,//NUMBER OF ISCs, Number of writes
[17] 0,1,0,0,0,1, // Comm. Failure with device whose Procome address is 0
[18] 1,1,0,0,0,1, // Comm. Failure with device whose Procome address is 1
[19] 2,1,0,0,0,1, // Comm. Failure with device whose Procome address is 2
[20] …
[21] 307,1,0,0,0,1,// Status of the eight digital input of the CPX
[22] # CONFIGURATION OF ISSs FROM CENTRAL TASK
[23] 4,// Number of writes
[24] 0,257,-1,10000,0,0,
[25] 1,257,-1,10000,0,0,
[26] 2,257,-1,10000,0,0,
[27] 3,257,-1,10000,0,0,

M1CPTA2005I
A-13 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.3 Physical Device File: DBASE.CFG

It is the file “dbase.cfg” and contains a number of data on the different substation physical
devices (digital signals, commands, measurements, meters, writes, etc.). File formal is as
follows:
• Overall Substation Data: [Line 2]

NumEqFisicos , NumISCTotal8 , NumEqLogicos ,

• NumEqFisicos: Total number of substation physical devices with communications

protocol within the possible values allowed by “Control” setting. File “dbase.cfg” only
contains the configuration applicable to these devices.
• NumISCTotal8: Total number of substation digital signals ISC, calculated as the sum of
the first multiple of 8 immediately above the ISCs number of each device ( Σ (ISC)8),
added for all the substation physical devices.
• NumEqLogicos: Total number of substation logic bay devices, namely, physical devices
not using any of the communications protocols allowed by “Control” setting, which are
therefore emulated by the Central Unit. The configuration used by the Central Unit for
these devices resides in manufacture specific configuration files.

Below are data of the different devices configured sequentially. The following data are display
for each physical device:
• General Physical Device Data for CPX/CPP models: [Line 6]

Dir , Port , Time , N_ISC , N_ISE , N_ISS , N_MEA ,

N_CON , N_ISM , Protecc , Control , TimeReconex , TipoFuncProc ,

• Dir: Device communications address. 1…254.

• Port: Communications port to which it is connected.
• Time: Communication error timeout (in msec.). The value -1 means the default timeout is
selected.
• N_ISC: Number of device Digital Signals (ISC).
• N_ISE: Number of device Commands (ISE).
• N_ISS: Number of device Writes (ISS).
• N_MEA: Number of device Measurements (MEA).
• N_CON: Number of device Meters (CON).
• N_ISM: Number of device output writes (ISM).
• Protecc: Bit stating whether the device has Protection (1) or not (0).
• Control: Type of device Control protocol. 0: No control; 1: PROCOME; 2: Type DNP3; 3:
IEC103; 4: SEVCO 6802; 5: CGC; 6: IEC61850; 7: SPABUS, 8: MODBUS, 9:101B.
• TimeReconex: Relay response waiting time (in millisec.) during reconnection with the
same (timeout to recover a device in error).
• TipoFuncProc: Number that states the data processing function being used. Default value
is 0: normal processing. If the value is 1, a special processing will be applied on device
refreshment: For relays IRD-M**-***9***B. Undefined for the rest of relays.
Note: devices with the field Control configured to 0, will not be introduced into the Central Unit control
interrogation cycle; but access can be gained through protection transparent connection with software
Zivercom©.

Ex:10,1,200,100,16,2,7,1,0,1,1,50,0,

M1CPTA2005I
1CPT: Substation Central Unit A-14
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• General Physical Device Data for CPT Models: [Line 6]

Dir , Port , Time , N_ISC , N_ISE , N_ISS , N_MEA ,

N_CON , Protecc , Control , TimeReconex , FormatoMed , N_ISM ,

TipoFuncProc , DirIP , TCP_Port ,

• Dir 5: Device communications address.

• Port: Communications port to which it is connected. Communications port to which it is
connected. For IEC-61850 equipment, the value 200 will be used to indicate that the
network port will be used. For all other equipment the logic port will be used: 1 and 2 for
CPT fibre optic ports, 101 and 102 for COM1 and COM2 ports, and 201 to 219 for CIC
ports. DNP3 relays may also be connected to the network port (200).
• Time: Communication error timeout (in msec.). The value -1 means the default timeout is
selected. For IEC-61850 relays timeout values below 10000 msec may not be configured.
• N_ISC: Number of device Digital Signals (ISC).
• N_ISE: Number of device Commands (ISE).
• N_ISS: Number of device Output Writes (ISS).
• N_MEA: Number of device Measurements (MEA).
• N_CON: Number of device Meters (CON).
• Protecc: Bit stating whether the device has Protection (1) or not (0).
• Control 6: Type of device Control protocol. 0: No control; 1: PROCOME; 2: Type DNP3; 3:
IEC103; 4: SEVCO 6802; 5: CGC; 6: IEC61850.
• TimeReconex: Relay response waiting time (in millisec.) during reconnection with the
same (timeout to recover a device in error). This parameter is not used in IEC61850
devices.
• FormatoMed: Format of measurements received from the device. 0: integer format 12 to
16 bits; 1: single precision floating point format (32 bits).
• N_ISM: Number of device output writes (ISM).
• TipoFuncProc: Number that states the data processing function being used. Default value
is 0: normal processing. If the value is 1, a special processing will be applied on
equipment refreshment: For relays IRD-M**-***9***B. Undefined for the rest of relays.
• DirIP: Equipment IP address in case of network communications (Port = 200).
• TCP_Port: TCP port used for network communications with the equipment.

Ex: 10,1,200,100,16,2,7,1,0,1,1,50,0,0, 192.168.1.30,20000,

5
In IEC61850 devices the field of the device address will be the internal address of the device in the CPT real
time database, and will be an integer between 0 and 254, that will be configured by the user and has nothing to
do with the IP address of the same.

6
Equipment whose Control field is configured to 0, will not be introduced within the Central Unit interrogation
control cycle; although they will be accessible by means of a transparent protection communication with the
Zivercom© program.

M1CPTA2005I
A-15 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Device Digital Signals

They are configured as explained in section A.1: [lines 8-13]

Ex: 100,// Num. Digital signals

0,0,0,1,0,1,
1,0,0,1,0,1,
…
99,0,0,0,0,0,

• Configuration Data of Device Commands

They are configured as explained in section A.1: [lines 15-21]

Ex: 16,// Num. Commands

0,10,16,1000,0,10,16,10,-1,0,0,0,
1,10,17,1000,0,10,17,10,-1,0,0,0,
…
15,10,43,10000,1,10,-1,10,-1,0,1,10,43,1,0,

• Configuration Data of Device Output Writes

They are configured as explained in section A.1:

Ex: 2,// Num. Output writes

0,10,-1,10000,0,0,
1,10,-1,10000,0,0,

• Configuration Data of Device Measurements

They are configured as explained in section A.1:

Ex: 7,// Num. Measurements

1.0,0,
0.00029304,0,
…
1.0,0,

• Configuration Data of Device Meters

They are configured as explained in section A.1:

Ex: 1,// Num. Meters

1.0,0,

M1CPTA2005I
1CPT: Substation Central Unit A-16
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # FILE DBASE.CFG

[2] 6,816,// Num. physical devices, Num. ISCs
[3] # Device nº: 1
[4] # dir, port, timeout, nº ISC, nº ISE, nº ISS, nº MEA, nº CON, protec,
[5] # control, reconnection time
[6] 10,1,200,100,16,2,7,1,1,1,50,0,0, // *** 10 *** TRAFO 1 45 kV
[7] # ISCs configuration
[8] 100, // Nº device ISCs
[9] # isc,alarm,filter act.,filter deact., alr edge, horn
[10] 0,0,0,1,0,1,
[11] 1,0,0,1,0,1,
[12] …
[13] 99,0,0,0,0,0,
[14] # ISEs configuration (commands)
[15] 16, // Nº of device ISEs
[16] # ISE, ISC exe (dir,isc), Time, neg, ISCOK (dir,isc), ISCFail,
(dir,isc), neg,
[17] # double, nº blqs….
[18] 0, 10,16, 1000, 0, 10,16, 10,-1, 0, 0, 0,
[19] 1, 10,17, 1000, 0, 10,17, 10,-1, 0, 0, 0,
[20] …
[21] 15, 10,43,10000, 1, 10,-1, 10,-1, 0, 1, 10,43,1, 0,
[22] # ISSs configuration(output writes)
[23] 2, // Nº of device ISSs
[24] # ISS,Dir,Isc,time,neg,Analog ?
[25] 0,10,-1,10000,0,0,
[26] 1,10,-1,10000,0,0,
[27] # MEAs Configuration (measurement conversion factors)
[28] # MEA * FACTOR = Actual value
[29] 7, // Nº of device MEAs
[30] 1.0,0, // Slope and origin of conversion line
[31] 0.00029304,0, // Slope and origin of conversion line
[32] …
[33] 1.0,0, // Slope and origin of conversion line
[34] # CON Configuration (meters conversion factors)
[35] # CON * FACTOR = Actual value
[36] 1, // Nº of device CONs
[37] 1.0,0, // Slope and origin of conversion line
[38] #
[39] # Configuración de las ISM
[40] #
[41] 2,
[42] 0,10,0,
[43] 1,10,2,
[44]
[45] # Device nº: 2
[46] …

M1CPTA2005I
A-17 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.4 History Files: HISTORIC.CFG

The file name is “historic.cfg” and configures the different existing history records (they can be
three types: measurement, meter and change records) together with the measurements, meters
or signals that constitute it.

File format is as follows:

• Data on the Number of History Records: [Line 2]

NumHistoricos , NumDiasHist ,

• NumHistoricos: Number of history records.

• NumDiasHist: This parameter states the maximum number of days stored of the history
records generated; namely, history records of the last NumDiasHist days are stored.
Default value is 183 (6 months)

Ex: 3, 183,

Then, the different history records generated are configured in sequence. The following data will
be given as a function of the type of history record:

A.4.1 Measurements History Record

• Data on Measurements History Records: [Lines 4-11]

TipoHist ,
NumMEAs ,
DirEq , MEA , Descripción , (*)

(*) It repeats for each applicable history record. There will be as many as shown in
NumMEAs.

• TipoHist: Type of history record (0 = measurement).

• NumMEAs: Number of measurements of the history record.
• DirEq: Address of the device that the measurement belongs to, within the Central
Unit real time database.
• MEA: Measurement identifier.
• Descripción: Description of the signal to be used in report applications.

Ex: 1, // Type history record

30, // Num. Measurements
15, // Sampling interval
10,0, INCOMING ACTIVE ENERGY,
10,1, INCOMING REACTIVE ENERGY,
…
22,4, PULSES,

M1CPTA2005I
1CPT: Substation Central Unit A-18
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.4.2 Meters History Record

• Data on Meters History Record: [Lines 13-21]

TipoHist ,
NumCONs ,
IntMuestreo ,
DirEq , CON , Descripción , (*)

(*) It repeats for each applicable history record meter. There will be as many as shown in
NumCONs.

• TipoHist: Type of history record (1 = meter).

• NumCONs: Number of meters of the history record.
• IntMuestreo: Sampling interval of meters (in minutes).
• DirEq: Address of the device that the meter belongs to, within the Central Unit real time
database.
• CON: Meter identifier.
• Descripción: Description of the signal to be used in report applications.

Ex: 1, // Type history record

30, // Num. Measurements
15, //Sampling interval
10,0, INCOMING ACTIVE ENERGY,
10,1, INCOMING REACTIVE ENERGY,
…
22,4,PULSES,

A.4.3 Changes History Record (Signals)

• Data on Changes History Record: [Lines 23-30]

TipoHist ,
NumISCs ,
DirEq , ISC , F_activ , F_desactiv , (*)

Descripción , Activ , Desactiv , (*)

(*)It repeats for each applicable history record signal. There will be as many as shown in
NumISCs.

• NumISCs: Number of signals of the history record.

• DirEq: Address of the device that the signal belongs to, within the Central Unit real time
database.
• ISC: Signal identifier.
• F_activ: Filter Bit for signal activation (0 = signal switching from 0 to 1 is not annotated; 1
= said switching is annotated).
• F_desactiv: Filter bit for signal deactivation (0 = signal switching from 1 to 0 is not
annotated; 1 = said switching is annotated).

M1CPTA2005I
A-19 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: 2,// Type history record

262,// Num. Signals
10,2,1,1,BUS BREAKER, OPEN, CLOSED
10,3,1,1,GROUND SWITCH, OPEN, CLOSED,
…
257,22,1,1, COMMS FAILURE EQUIP 22, ALARM, NORMAL,

The file becomes:

[1] # Number of History records

[2] 3,
[3] # Type of History records
[4] 0, // Measurements history record
[5] # measurements history record settings
[6] 30, // Number of measurements
[7] # dir, mea
[8] 10,0,
[9] 10,1,
[10] …
[11] 22,4,
[12] # Type of history records
[13] 1, // Meters history record
[14] # Meters history record settings
[15] 30, // Number of meters
[16] 15, // Sampling interval
[17] # dir, con
[18] 10,0, INCOMING ACTIVE ENERGY,
[19] 10,1, INCOMING REACTIVE ENERGY,
[20] …
[21] 22,4, PULSES
[22] # Type of history records
[23] 2, // Change history record
[24] # Change history record settings
[25] 262, // Number of signals
[26] # dir, isc, fil_activ, fil_deactiv
[27] 10,2,1,1, BUS BREAKER, OPEN, CLOSED,
[28] 10,3,1,1, GROUND SWITCH, OPEN, CLOSED,
[29] …
[30] 257,22,1,1, COMMS FAILURE EQUIP 22, ALARM, NORMAL,…

M1CPTA2005I
1CPT: Substation Central Unit A-20
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.5 Configuration Files of the LOGIC Task

Below are described the two configuration files of the LOGIC task:

- LOGICA.CFG: Configuration file of logic signals, commands, outputs, measurements and

meters.
- LOGICA.COD: Logic programming file.

A.5.1 LOGIC Task Signals File: LOGICA.CFG

This is the configuration file of digital signals, commands, outputs, measurements and meters
involved in the Central Unit Logic tasks (virtual device the address of which within the Central
Unit real time database is 256). File name is “logica.cfg”.

File format is as follows:

• Overall Data of the Physical Device in Question:

N_ISC , N_ISE , N_ISS , N_MEA , N_CON ,

• N_ISC: Number of Digital Signals (ISC) of the Logic device.

• N_ISE: Number of Commands (ISE) of the Logic device.
• N_ISS: Number of Output Writes (ISS) of the Logic device. These are not configured
for the moment, so its value is 0.
• N_MEA: Number of Measurements (MEA) of the Logic device. These are not
configured for the moment, so its value is 0.

Ex: 90,2,0,4,2,2, // Number of each type of signal.

• Configuration Data of Logic Digital Signals

They are configured as explained in section A.1: [lines 3-8]

Ex: 90,// Num. Signals

0,0,1,1,0,0,
1,0,1,1,0,0,
2,0,1,1,0,0,
…
89,0,0,0,0,0,

• Configuration Data of Logic Commands

They are configured as explained in section A.1: [lines 10-14]

Ex: 2,// Num. Commands

0,256,84,500,0,256,-1,256,-1,0,0,0,
1,256,33,500,1,256,-1,256,-1,0,0,0,

M1CPTA2005I
A-21 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Logic Digital Outputs

They are not configured for the moment so they will be set to 0.

Ex: 0,// Num. Digital Outputs

• Configuration Data of Logic Measurements

Floating-Point Logic (32 bits). Configured as explained in section A.1.

Ex: 4,// Num. Measurements

1.0, 0.0,
1.0, 0.0,
1.0, 0.0,
1.0, 0.0,

• Configuration Data of Logic Meters

Se configuran como se expuso en el apartado A.1:

Ex: 2,// Num. Meters

1.0,0.0,
1.0,0.0,

• Configuration Data of Logic Settings: [Lines 16-20]

NumAjs ,
Tipo , VDefecto , VMin , VMax , Paso ,

Descripcion , Unidad , (*)

(*) It repeats for each setting. There will be as many as shown in NumAjs.

• NumAjs: Number of settings to be configured. Max = 20.

• Tipo: Type of setting: 1 = Integer; 2 = Floating point.
• VDefecto: Default value for the first time the CPX/CPT is started or after a configuration
change. This value can be modified from the logic settings change screen of the HMI 7.
• VMin: Minimum value of the setting.
• VMax: Maximum value of the setting.
• Paso: Increment/decrement value when changing the setting from the MMI.
• Description: Setting description text. It is used in the MMI setting change screen as
identifier. Maximum size = 23 characters.
• Unidad: Text describing the Unit in which the setting is expressed. It is used for
information purposes. Maximum size = 5 characters.

Ex: 4,// Num. settings

1,10,1,100,1, Time,sec,
2,13.7,2.5,15.8,0.1, Busbar voltage,kV,
2,255.0,100.0,345.0,1.0, Current,A,
1,30,1,60,1, Start delay,sec,

7
Logic settings change screen is not available in the CPT embeded WEB MMI.

M1CPTA2005I
1CPT: Substation Central Unit A-22
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Analog Write Configuration Data (ISM)

They are configured as explained in section A.1:

Ex: 2,//Analog Write Num.

0,256,0,
1,256,2,

The file becomes:

[1] # FILE LOGICA.CFG

[2] # NumISC,NumISE,NumISS,NumMEA,NumCON,
[3] 90,2,0,0,2,
[4] # Logic ISCs
[5] 90,// Num. Signals
[6] 0,0,1,1,0,0,// SIGNAL ALWAYS TO 0
[7] 1,0,1,1,0,0,// SIGNAL ALWAYS TO 1
[8] 2,0,1,1,0,0,// INCOMING ACTIVE POWER MIRAFLORES
[9] …
[10] 89,0,0,0,0,0,// RESERVE
[11] # Logic ISE's
[12] 2,// Num. Commands
[13] # command,isc status (eq,signal),time,neg,isc ok(eq,signal),isc fail
(eq,signal),
[14] # double, blqs
[15] 0,256,84,500,0,256,-1,256,-1,0,0,0, // SWITCH TO LOCAL
[16] 1,256,33,500,1,256,-1,256,-1,0,0,0, // SWITCH TO REMOTE CONTROL
[17] # Logic ISS
[18] 0,
[19] # Logic MEA
[20] 4,
[21] 1.0, 0.0,
[22] 1.0, 0.0,
[23] 1.0, 0.0,
[24] 1.0, 0.0,
[25] # Logic CON
[26] 2,
[27] 1.0,0.0,
[28] 1.0,0.0,
[29] # SETTINGS
[30] 4, //Num. Settings
[31] 1,10,1,100,1, Close Time ,sec,
[32] 2,13.7,2.5,15.8,0.1,Busbar voltage,kV,
[33] 2,255.0,100.0,345.0,1.0,Current,A,
[34] 1,30,1,60,1,Start delay,sec,
[35] # Logic ISM
[36] 2,
[37] 0, 256,1,
[38] 1, 256, 2,
[39]

M1CPTA2005I
A-23 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.5.2 LOGIC Task Programming File: LOGICA.COD

The file name is “logica.cod” and it contains the logic programming. Each line of the file
corresponds to a logic operation. The overall structure of each line is:
OPERACIÓN<[Input1][Input2],…>(Output1)(Output2)…

When referring to a negated signal the symbol “\” is used before the signal in the form: [256,\10]
(signal 10 from device 256 negated).

Input and Output variables that can be used with their format are shown in Table A-1:

Table A-1: Logic Input and Output Variables

Variable Format Description
ISC Device address, Signal Digital Signals
ISE Device address, Signal Commands
MEA Device address, Measurement Measurements
ISS Device address, Signal Output writes
CON Device address, Signal Counters
Internal Registers $, Register Internal Logic Registers

Besides these variables, settings can be used in TEMPOR and DNIVEL operations. Settings
format is AJn where n varies between 0 and NumAjs-1. These can be used in the above
mentioned operations instead of fixed parameters.

The different programming operations are given below. As a general rule, when an operation
has several inputs, for example one AND, the AND of the first two inputs is made and an
intermediate output is obtained. Then the AND of this intermediate output is made with the third
input and a second intermediate output is obtained. Then the AND of this second intermediate
output is made with the fourth input and so on until the final output is obtained. This end value is
assigned to all outputs with the operation in question.
• OR: [line 6]
It is a logical OR operation with a number of inputs and outputs.

Format: OR<[ISC][ISC]…>(ISC)(ISC)…

Table A-2: Truth Table (OR)

In1 In2 Out
0 0 0
0 1 1
1 0 1
1 1 1

Ex: OR<[256,1][256,11][256,12]>(256,0)

M1CPTA2005I
1CPT: Substation Central Unit A-24
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• AND: [line 7]
This is a logical AND operation with several inputs and several outputs.

Format:AND<[ISC][ISC]…>(ISC)(ISC)…

Table A-3: Truth Table (AND)

In1 In2 Out
0 0 0
0 1 0
1 0 0
1 1 1

Ex: AND<[1,8][7,8][3,40][9,8][11,8][8,8][5,40][14,8]…
…[17,8]>(256,13)

• XOR: [line 4]
This is a logical exclusive-OR operation with several inputs and several outputs.

Format:XOR<[ISC][ISC]…>(ISC)(ISC)…

Table A-4: Truth Table (XOR)

In1 In2 Out
0 0 0
0 1 1
1 0 1
1 1 0

Ex: XOR<[10,8][11,8][12,8]>($,0)

• NOT: [line 11]

This is a logical NOT operation: it negates the input and assigns that value to the respective
outputs.

Format:NOT<[ISC]>(ISC)(ISC)…

Table A-5: Truth Table (NOT)

In1 Out
0 1
1 0

Ex: NOT<[260,7]> (256,2)

M1CPTA2005I
A-25 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• CABLE: [line 16]

This is an assignment, i.e., the value of the input is assigned to the different outputs:

Format:CABLE<[ISC]>(ISC)(ISC)…

Table A-6: Truth Table CABLE

In1 Out
0 0
1 1

Ex: CABLE<[20,8]>($,0)(256,40)

• FFRS: [line 17]

This is an RS flip-flop.

Format:FFRS<[ISC_R][ISC_S]>(ISC)(ISC)…

Table A-7: Truth Table (FFRS)

R S Qt+∆t
0 0 Qt
0 1 1
1 0 0
1 1 X

Ex: FFRS<[10,8][10,9]>($,0)(256,40)

• FFJK: [line 18]

This is a JK flip-flop.

Format:FFJK<[ISC_J][ISC_K]>(ISC)(ISC)…

Table A-8: Truth Table (FFJK)

J K Qt+∆t
0 0 Qt
0 1 1
1 0 0
1 1 __Qt

Ex: FFJK<[10,8][10,9]>(256,40)

M1CPTA2005I
1CPT: Substation Central Unit A-26
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• MANDO: [line 19]

It executes a command in the following way:

If the input signal [ISC] is activated (goes from 0 to 1 or vice versa if it is negated) the command
[ISE] is executed with {DCO} and whatever value the input signal [ISC] has is assigned to the
outputs.

Commands
belonging to the
LOGICA device
itself may not be
used as ISE
parameter in this
logic operation,
because it makes
no sense for a
device to send
commands to
itself. The
operation is shown
in figure A.2:

Figure A.2: Operation of the MANDO Logical Operation.

Format:MANDO<[ISC][ISE]{DCO}>(ISC)(ISC)…

Ex: COMMAND <[10,8][10,0]{2}>(256,40)

• FMANDO 8: [line 20]

This is a variation of the preceding function: if the input signal [ISC] is activated, the command
[ISE] is executed with {DCO} and there is a time delay setting (as explained in section A.1) for
command execution to see whether the test [ISC_T] is activated. If it activates within that time
the output signal (ISC_OK) will be activated. If it is not activated within the set time delay, output
(ISC_FAIL) will be activated.

Commands belonging to the LOGICA device itself may not be used as a command parameter in
this logical operation, because it makes no sense for a device to send commands to itself.

Format:FMANDO<[ISC][ISE][ISC_T]{DCO}>(ISC_FAIL)(ISC_OK)

Ex: FMANDO<[256,1][10,0][10,8]{2}>(256,40)(256,9)

8
This function is only implemented in 1CPX-A.

M1CPTA2005I
A-27 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• ESC: [line 21]

This is a function
that executes [ISS]
writes with
{DCO_ON} if the
[ISC] signal is
activated or with
{DCO_OFF} if the
[ISC] signal is
deactivated. In
addition, whatever
value the input
signal [ISC] has is
assigned to the
outputs.

Figure A.3: ESC Logic Operation.

Format:ESC<[ISC][ISS]{DCO_ON,DCO_OFF}>(ISC)(ISC)…

Ex: ESC<[10,8][10,0]{2,1}>(256,40)

• TEMPOR: [lines 15 and 16]

This is a timer
whose operation is
shown in figure
A.4:

Figure A.4: Timer Operation.

Format:

TEMPOR<[ISC]{TA}{TB}>(ISC)(ISC)

where TA and TB are expressed in full seconds. Any of these values can be replaced by
settings if desired.

Ex: TEMPOR<[1,105]{0}{10}>($,1)
TEMPOR<[10,0]{12}{AJ0}>(256,5)

M1CPTA2005I
1CPT: Substation Central Unit A-28
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• DNIVEL: [lines 24 and 25]

This is a range
evaluator which
works as follows.

The value of field

[MEA]
measurement is
compared with
{VC}, {VMIN} and
{VMAX} as shown
in figure A.5 and in
the following
diagram:

Figure A.5: Operation of the Range Evaluator.

- If [MEA]>={VMAX}  (ISC_MAYOR) output signal is activated.

- If [MEA]={VC}  (ISC_IGUAL) output signal is activated.
- If [MEA]<={VMIN}  (ISC_MENOR) output signal is activated.

Any of the parameters VC, VMAX and VMIN can be replaced by a setting.

Format: DNIVEL <[MEA]{VC}{VMIN}{VMAX}>

(ISC_MENOR)(ISC_IGUAL)(ISC_MAYOR)

Ex: DNIVEL<[10,5]{0.8}{0.5}{1}>(256,9)($,1)(256,10)
DNIVEL<[10,7]{AJ6}{AJ8}{AJ3}>(256,8)($,2)(256,15)

• DEACT: [line 26]

This is a detector for the only active input from among several inputs.

Format:DEACT<[ISC][ISC]…>(ISC)(ISC)…

Table A-9: Truth table (Particular Case of 3 Inputs)

In1 In2 In3 Out
0 0 0 0
0 0 1 1
0 1 0 1
0 1 1 0
1 0 0 1
1 0 1 0
1 1 0 0
1 1 1 0

Ex: DEACT<[10,8][11,8][12,8]>($,0)

M1CPTA2005I
A-29 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• CONT: [line 27]

It is a Pulse Counter, which increases when a rising pulse is introduced from the Q input and
resets if it receives a rising pulse from the other R input. In case both inputs activate, a counter
reset will occur.

The number of defined counters must not surpass a maximum value stipulated as 10 counters.

Format:CONT<[ISC_Q][ISC_R]>(CON)

Table A-10: Truth table (CONT)

Q R CONT
0 0 -
0 01 The value resets
01 0 The value is increased by one.
01 01 The value resets

Ex: CONT<[256,2][256,3]>(256,0)

• CMPCONT: [line 28]

It is a Counter Comparator, such that a counter value is compared with a fixed or logic variable-
declared counter value. If the comparison is greater or equal to it, the output signal will activate.
Otherwise, said signal will deactivate.

The number of defined counter comparators must not surpass a maximum value stipulated as
10 comparators.

It is a logic counter.

Format: CMPCONT<[CON]{Vc}>(ISC)

If CON >= Vc, ISC activates

If CON < Vc, ISC activates

Ex: CMPCONT<[256,0]{AJ0}>(256,6)
CMPCONT<[100,0]{100}>(100,45)
CMPCONT<[256,0]{9999}>(100,75)
CMPCONT<[100,1]{AJ8}>(256,7)

The code of the logic in this file has the following limitations:

- Maximum number of inputs per logic operation: 32.

- Maximum number of outputs per logic operation: 32. In addition, logic operation outputs
may only be addressed to internal registers or to signals of the LOGICA virtual device
itself.
- Maximum number of logic internal registers: 1024 (0 … 1023). Several outputs may not
- be addressed to the same register in a single logical operation.
- Maximum number of timers available: 200.
- Maximum number of R-S flip-flops: 255.
- Maximum number of J-K flip-flops: 20.
- Maximum number of D flip-flops: 20.
- Maximum number of MANDO-type logic operators: 200.
- Maximum number of FMANDO-type logical operators: 40.

M1CPTA2005I
1CPT: Substation Central Unit A-30
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

- Maximum number of ESC-type logical operators: 30.

- Maximum number of CONT meters: 10.
- Maximum number of CMPCONT counter comparators: 10.
- As the rest of the central unit configuration files each line of logic operations, in this case,
may not exceed 80 characters.

The file becomes:

[1] # FILE LOGICA.COD

[2] # ---- LOGICA UCS N 0 ----
[3] OR<[1,8][1,9]>(256,1)
[4] XOR<[10,8][11,8][12,8]>($,0)
[5] …
[6] OR<[256,1][256,11][256,12]>(256,0)
[7] AND<[1,8][7,8][3,40][9,8][11,8][8,8][5,40][14,8][17,8]>(256,13)
[8] AND<[1,17][7,17][3,/40][9,17][11,17][8,17][5,/40][14,17][17,17]>(256,29)
[9] #
[10] # ---- LOGICA UCS N 1 ----
[11] NOT<[260,7]>(256,2)
[12] #
[13] …
[14] # ---- LOGICA UCS N 3 ----
[15] TEMPOR<[1,105]{0}{10}>($,1)
[16] TEMPOR<[10,0]{12}{AJ0}>(256,5)
[17] CABLE<[20,8]>($,0)(256,40)
[18] FFRS<[10,8][10,9]>($,0)(256,40)
[19] FFJK<[10,8][10,9]>(256,40)
[20] MANDO<[10,8][10,0]{2}>(256,40)
[21] FMANDO<[256,1][10,0][10,8]{2}>(256,40)(256,9)
[22] ESC<[10,8][10,0]{2,1}>(256,40)
[23] …
[24] DNIVEL<[10,5]{0.8}{0.5}{1}>(256,9)($,1)(256,10)
[25] DNIVEL<[10,7]{AJ6}{AJ8}{AJ3}>(256,8)($,2)(256,15)
[26] DEACT<[10,8][11,8][12,8]>($,0)
[27] CONT<[256,2][256,3]>(256,0)
[28] CMPCONT<[100,0]{AJ0}]>(100,45)

M1CPTA2005I
A-31 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.6 Configuration File of COMMAND Task: MANDO.CFG

This file “mando.cfg” contains configuration data of the COMMAND task, in charge of
executing the commands issued from the HMI or from controllers, addressed to elements for
which no specific command tasks have been assigned.

For easy command execution, devices are grouped into UCPs groups and slave master groups.
File format is:
• Configuration Data of UCP Groups: [Lines 2-17]

NumGrps ,
Num UCPs ISE
, ini ,
DirUCP ISE DCO ISE DCO (*) (**)
, local , local , telem , telem ,

(*) It repeats for each UCP in the group in question. There will be as many as shown in
NumUCPs.
(**)It repeats for each UCP group. There will be as many as shown in NumGrps.

• NumGrps: Number of UCP groups (e.g.: high, low, etc.).

• NumUCPs: Number of UCPs in the group.
• ISEini: Setting that indicates whether after starting, the central unit executes the
command ISElocal (ISEini = 1) or the command ISEtelem (ISEini = 0).
• DirUCP: UCP address within the Central Unit real time database.
• ISElocal: Identifier of the command to switch said UCP to local.
• DCOlocal: DCO of the switch to local command.
• ISEtelem: Identifier of the command to switch the UCP to remote control.
• DCOtelem: DCO of the switch to remote control command.

Ex: 3,//Num. Groups

# * Group 1
1,0,//NumUCPs, ISEini
1,0,2,1,2,
# * Group 2
4,0,//NumUCPs, ISEini
7,0,2,1,2,
3,12,2,13,2,
9,0,2,1,2,
11,0,2,1,2,
# * Group 3
4,0,//NumUCPs, ISEini
8,0,2,1,2,
5,12,2,13,2,
14,0,2,1,2,
17,0,2,1,2,

M1CPTA2005I
1CPT: Substation Central Unit A-32
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Masters: [Lines 21-40]

NumMaestras ,
DirMaestra ,
Mando? ISE ISE Num
, locMae , telMae , EsclaMan ,
DirEsclaMan ISE DCO ISE DCO (*) (***)
, locEsc , locEsc , telEsc , telEsc ,
Escritura? ISC Neg Num
, , , EsclaEscr ,
DirEsclaEscr , ISS , DCO_ON , DCO_OFF , (**)

(*) It repeats for each Command slave. There will be as many as shown in NumEsclaMan.
(**) It repeats for each Write slave. There will be as many as shown in NumEsclaEscr.
(***) It repeats for each master. There will be as many as shown in NumMaestras.

• NumMaestras: Number of masters.

• DirMaestra: Address of master within the Central Unit real time database.
• Mando?: Bit that indicates whether it is command master (1) or not (0).
• ISElocMae: Identifier of the command to switch said master to local.
• ISEtelMae: Identifier of the command that switches said master to remote control.
• NumEsclaMan: Number of command slaves associated to said master.
• DirEsclaMan: Address of the applicable command slave within the Central Unit real time
database
• ISElocEsc: Identifier of the command that switches the command slave to local.
• DCOlocEsc: DCO of the switch to local command.
• ISEtelEsc: Identifier of the command that switches the command slave to remote control.
• DCOtelEsc: DCO of the switch to remote control command.
• Escritura?: Bit that indicates whether the output Write is master (1) or not (0).
• ISC: Identifier of the digital signal (ISCISS) that causes the output Write.
• Neg: Negation Bit of said digital signal.
• NumEsclaEscr: Number of associated output write slaves.
• DirEsclaEscr: Address of the slave within the Central Unit real time database.
• ISS: Identifier of the output write that writes on the write slave.
• DCO_ON: DCO for activation: DCO_ON (2). Is the DCO associated to the ISS when the
signal (ISCISS) activates.
• DCO_OFF: DCO for deactivation: DCO_OFF (1). Is the DCO associated to the ISS when
the signal (ISCISS) deactivates

M1CPTA2005I
A-33 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: 11,//Num. Masters

# MASTER 1
2,//Dir. Master 1
# Command
1,0,1,1,
5,0,2,1,2,// Command Slave 1
# Writes
1,0,0,2,
1,0,2,1,// Write Slave 1
7,2,2,1,// Write Slave 2
# MASTER 2
…
# MASTER 11
8,//Dir. Master 11
# Commands
0,0,1,0,
# Writes
1,8,0,1,
2,1,2,1,// Write Slave 1

The file becomes:

[1] ############## GROUPS ####################

[2] 3, // Number of groups
[3] # * Group 1
[4] 1,0, // group HIGH
[5] 1,0,2,1,2,
[6] # * Group 2
[7] 4,0, // num. ucps in group, initial state (default) Group LOW A
[8] 7,0,2,1,2, // dir,ISEl,DcoL,ISEt,DcoT
[9] 3,12,2,13,2,
[10] 9,0,2,1,2,
[11] 11,0,2,1,2,
[12] # * Group 3
[13] 4,0, // num. ucps in group, initial state (default) Group LOW B
[14] 8,0,2,1,2, // dir,ISEl,DcoL,ISEt,DcoT
[15] 5,12,2,13,2,
[16] 14,0,2,1,2,
[17] 17,0,2,1,2,
[18] ############# MASTERS ###################
[19] 11, // Number of Masters
[20] # MASTER 1
[21] 2, // Master Address
[22] 1,0,1,1, // Command ?,IseL,IseT,N. Elm.
[23] # Master element list
[24] 5,0,2,1,2,// Dir,IseL,DcoL,IseT,DcoT
[25] # Master data for output Write
[26] 1,0,0,2, // Write ?,Isc,Neg,N. Elm.
[27] # Master element list
[28] 1,0,2,1, // Dir,ISS,ON,OFF
[29] 7,2,2,1, // Dir,ISS,ON,OFF
[30] # MASTER 2
[31] …
[32] # MASTER 11
[33] 8, // Master address
[34] 0,0,1,0, // Command ?,IseL,IseT,N. Elm.
[35] # Master data for output Write
[36] 1,8,0,1, // Write ?,Isc,Neg,N. Elm.
[37] # Master element list
[38] 2,1,2,1, // Dir,ISS,ON,OFF

M1CPTA2005I
1CPT: Substation Central Unit A-34
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.7 Communications Configuration Files: PUERTOS.CFG

This file “puertos.cfg” contains configuration data of serial communications ports of cards
installed on substation Central Units.

File format is as follows:

• Configuration Data of Communications Cards: [Lines 3-13]

NumTarjs ,
TarjNum Num
, Ports ,
PortNum Veloc Tipo Bits Bits Est Tipo
, , Par , Datos , Stop , Ini , Port ,

Tout Caract , (*) (**)

(*) It repeats for each applicable card port. There will be as many as shown in NumPorts.
(**) It repeats for each existing communications card. There will be as many as shown in
NumTarjs.

• NumTarjs: Number of cards to be configured. Maximum value is 4 cards.

• TarjNum: Card number.
• NumPorts: Number of ports configured in said card.
• PortNum: Card port number. The range is 1 to 8. When port is number 7 (Remote port –
TipoPort = 2 for this port - ) two parameters can be added to the line to enable the
MODEM initialization function. These parameters are explained below.
• Veloc: Port baud rate. Possible values are 300, 600, 1200, 2400, 4800, 9600, 19200 and
38400.
• TipoPar: Type of parity. Possible values are none (‘N’ or ‘n’), even (‘P’ or ‘p’) and odd (‘I’
or ‘i’).
• BitsDatos: Number of bits per character. Possible values are 5, 6, 7 and 8.
• BitsStop: Number of stop bits. Possible values are 1 and 2.
• EstIni: Initial status of modem control lines. Possible values are 0, 1 (RTS), 2 (DTR) and
3 (RTS and DTR).
• TipoPort: Type of communications port (0 = Device port, 1 = Local port, 2 = Remote port).
This parameter is kept for compatibility reasons. From the hardware point of view, port 7
is labelled as REMOTE and port 8 as LOCAL; the remaining ports are used for devices.
In order to avoid problems with different software versions, port 7 must be configured as
remote Port and port 8 as local Port, never as device Port.
• ToutCaract: Maximum time gap between two consecutive bits of a message to take it for
good. If the time gap between the two bits is greater than ToutCaract milliseconds the
message is taken as bad and is discarded. This time is measured in milliseconds. The
default value is 15. The maximum value is 65535.

M1CPTA2005I
A-35 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

To configure the remote port (port 7) two more parameters are added which are related to the
MODEM initialization function. This function consists of sending periodically an initialization
chain to the MODEM provided there is no connection, namely, provided the CD signal of the
CPX/CPT is not active. Therefore, it is important that this signal is hard wired through the
MODEM to CPX/CPT connection cable. These parameters are:

Port Veloc Tipo Bits Bits Est Tipo Tout Msg Tout
Num , , Par , Datos , Stop , Ini , Port , Cnx , Init , Caract ,

• ToutCnxRemota: Time with no connection that defines the transmission period of the
initialization chain to the modem. It is measured in seconds and the range is 1  ∞. The
function is disabled if the value is 0 or negative and the chain is never sent to the modem;
in this case nor the following parameter is read. This time starts timing from the initial
moment and every time the deactivation of the CD line is detected.
• MsgInitModem: Modem initialization chain. Maximum chain size is 49 characters and
must not contain the comma character (,) in within. This chain of characters is sent every
ToutCnxRemota seconds to the MODEM provided telephone connection is not
established. If parameter ToutCnxRemota takes the value 0 or is negative, it must not be
set.

For the remote port, parameter ToutCaract must be set to a value noticeably greater than that
for the other ports if GSM modems are used. Due to a special feature of wireless telephone
networks, messages can be segregated into several parts during the transmission. In order for
the CPX/CPT to accept these messages this parameter must be set to a value of several
seconds. The exact value must be figured out by a hit and miss procedure as it greatly depends
on countries and network saturation.

The CPT has two optic fibre ports to communicate with devices, so only the two first ports will
be configured. If the remote port will also be used, port number 7 will be configured. Field
NumPorts will be configured as per these considerations; it takes a value of 3 when the remote
port is configured, and 2 when not configured.

For CPX/CPT, the file becomes.

Ex: 1,//Num. Cards

# CARD 1
1,8,//Card number, Num. Ports
1,19200,p,8,1,2,0,15,
2,19200,p,8,1,2,0,15,
3,19200,p,8,1,2,0,15,
4,19200,p,8,1,2,0,15,
5,19200,p,8,1,2,0,15,
6,19200,p,8,1,2,0,15,
7,9600,n,8,1,3,2,2700,AT,1500,
8,4800,p,8,1,2,1,15,

M1CPTA2005I
1CPT: Substation Central Unit A-36
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

For CPT, the file becomes:

Ex: 1,//Num. Cards

# CARD 1
1,3,//Card number, Num. Ports
1,19200,p,8,1,2,0,15,
2,19200,p,8,1,2,0,15,
7,9600,n,8,1,3,2,2700,AT,1500,

The file becomes:

[1] # Configuration of card communication ports

[2] # in UCS.
[3] 1, // Number of cards to be configured
[4] # CARD 1
[5] 1,8,
[6] 1,19200,p,8,1,2,0,15,
[7] 2,19200,p,8,1,2,0,15,
[8] 3,19200,p,8,1,2,0,15,
[9] 4,19200,p,8,1,2,0,15,
[10] 5,19200,p,8,1,2,0,15,
[11] 6,19200,p,8,1,2,0,15,
[12] 7,9600,n,8,1,3,2,2700,AT,1500,
[13] 8,4800,p,8,1,2,1,15,

M1CPTA2005I
A-37 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.8 LED Configuration File: LEDS.CFG

This file “leds.cfg” contains configuration data of CPX/CPT device front LEDs. LEDs can be
assigned the status of any digital signal configured within the Central Unit. Up to eight LEDs (0
to 7) will be configured for CPX; 4 LEDs (0 to 3) for CPT.

File format is as follows:

• LED Configuration Data: [Lines 3-9]

NumLeds ,
IndLed , DirEq , Isc , Negada , Modo , Time_ON , Time_OFF , (*)

(*) It repeats for each CPX/CPT LED to be configured. There will be as many as shown in
NumLeds.

• NumLeds: Number of LEDs configured in CPX/CPT devices. Maximum value is 8 LEDs.

• IndLed: CPX/CPT front LED number (from 0 to 7, top to bottom).
• DirEq: Address of the device (physical or logic), within the Central Unit real time
database, that the digital signal to be associated to the LED belongs to.
• Isc: Identifier of the digital signal to be associated to the LED.
• Negada: Indicates whether the negation status is to be associated to the digital signal
(0:normal, 1:negated).
• Modo: Indicates whether the LED activation will be steady (Mode = 0), or blinking (Mode
= 3).
• Time_ON: Time during which the LED is on in blinking mode when it is activated. The
time setting is configured in multiples of 55 milliseconds.
• Time_OFF: Time during which the LED is off in blinking mode when it is activated. The
time setting is configured in multiples of 55 milliseconds.

Ex: 5,// Num. leds configured (Maximum 8 Leds)

0,256,29,1,0,0,0,//Led,Eq,Isc,Neg,Modo,Ton,Toff
1,258,0,0,0,0,0,
2,257,256,0,0,0,0,
3,257,263,0,0,0,0,
4,257,259,0,0,0,0,

M1CPTA2005I
1CPT: Substation Central Unit A-38
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data for CPX/CPT Digital Input Sampling: [Lines 10-11]

TimeMuestreo , NmuestrasFiltro , LimInfCambSeg , LimSupCambSeg ,

• TimeMuestreo: Sampling period in milliseconds of the status of CPX/CPT digital input.

• NmuestrasFiltro: Number of samples that validate a digital input change of status, as an
anti-rebounce filter.
• LimInfCambSeg: Number of changes per second that automatically enable again a digital
input that had previously been disabled.
• LimSupCambSeg: Maximum number of digital input changes per second allowed. The
digital input is automatically disabled above this frequency of changes.

• Configuration Data for CPX/CPT Digital Input Enable: [Lines 16-17]

HabilED0 , HabilED1 , HabilED2 , HabilED3 , HabilED4 ,

HabilED5 , HabilED6 , HabilED7 , (*)

(*) It repeats for each CPX/CPT hardware card that features digital inputs.

• HabilEDi: Enables change collection on the ith CPX/CPT digital input (0: ED not enabled,
1: ED enabled).

The file becomes:

[1] # FILE LEDS.CFG, THAT CONFIGURES CPX/CPT FRONT LEDs.

[2] 5, // Number of leds configured (Maximum 8 Leds).
[3] # Nº del led(de 0 a 7), Device address, ISC, Negated, Mode(0:Steady,
3:Blinking),
[4] # T_ON (ms/55), T_OFF (ms/55),
[5] 0,256,29,1,0,0,0,
[6] 1,258,0,0,0,0,0,
[7] 2,257,256,0,0,0,0,
[8] 3,257,263,0,0,0,0,
[9] 4,257,259,0,0,0,0,
[10] # CONFIGURATION FOR SAPLING CPX/CPT DIGITAL INPUTS.
[11] 6,2,10,60,// TimeMuestreo,NmuestrasFiltro,LimInfCambSeg,LimSupCambSeg
[12] # CONFIGURATION FOR CPX/CPT DIGITAL INPUT ENABLE.
[13] 1,0,0,0,0,0,0,0,// 0: ED not enabled 1: ED enabled

M1CPTA2005I
A-39 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.9 Configuration File for Establishing a Connection Via

Modem with the HMI: RASSRV.CFG (Only for CPX-A)
This file contains data on establishing a connection via modem with the HMI. File name is
“rassrv.cfg”.

File format is as follows:

• Data on SLIP Packet Driver Interruption and Trace Monitoring Level: [Lines 2-
3]

InterrupSLIP ,
NivelMonitor ,

• InterrupSLIP: SLIP Packet Driver interruption number.

• NivelMonitor: Trace monitoring level.

Ex: 128,
0

• Data on Test Messages on HMI Status and User and Password Request:
[Lines 4-6]

MsjConsOcup ,
MsjUsuario ,
MsjPassword ,

• MsjConsOcup: Message for engaged local HMI (maximum number of characters: 39).
• MsjUsuario: Message for user name request (maximum number of characters: 19).
• MsjPassword:

Ex: LOCAL HMI CONNECTED,

USER:,
PASSWORD:,

• Data on Authorised User and Password: [Lines 7-8]

Usuario ,
Password ,

• Usuario: Valid user name (maximum number of characters: 8).

• Password: Valid user password (maximum number of characters: 8).

Ex: ZIV,
ZIV,

M1CPTA2005I
1CPT: Substation Central Unit A-40
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data on Accepted and Denied Access Messages: [Lines 9-10]

MsjAceptado ,
MsjDenegado ,

• MsjAceptado: User accepted message (maximum number of characters: 19).

• MsjDenegado: User access denied message (maximum number of characters: 19).

Ex: ACCEPTED,
ACCESS DENIED,

• Data on Working Mode, Connection Times and Modem Response and

Number of Rings: [Lines 11-12]

ModoTrabajo , TimeoutConex ,
TimeRespModem , NumRings ,

• ModoTrabajo: This number indicates whether working in normal mode (0), Windows 95
(1), dedicated line (2), or TRAME mode (3).
• TimeoutConex: Connection timeout (in msec.).
• RetCarTrame: Time gap between characters send to the TRAME. If the working mode is
ModoTrame, the gap between messages sent to the TRAME must be equal to this
setting. If the mode is not TRAME configured as 0 (Zero). Expressed in milliseconds.
Typical value 200.
• TimeEsperaReset: Time delay for internal modem initialisation before sending
CmdModemInit. Expressed in milliseconds. Typical value: 2000.
• TimeChgCtrlModem: Time delay for the modem to detect the change of the signal DTR
when the connection is to be closed. Expressed in milliseconds. Typical value: 900.
• TimeRespModem: Modem response time (in msec.).
• NumRings: Number of rings of the modem before picking up.

Ex: 0,60000,200,2000,900
15000,1,

• Data on Modem Reset and Initialisation Commands: [Lines 13-14]

ComReset ,
ComInicio ,

• ComReset: Modem reset command (maximum number of characters: 14).

• ComInicio: Modem initialisation command (maximum number of characters: 48).

Ex: ATZ,
ATE0V1X1M0S0=0,

M1CPTA2005I
A-41 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data on Incoming Call Indicator: [Lines 15-16]

IndTxtLlamadaEnt ,
IndNumLlamadaEnt ,

• IndTxtLlamadaEnt: Incoming call indicator in text mode (maximum number of characters:

24).
• IndNumLlamadaEnt: Incoming call indicator in numeric mode (maximum number of
characters: 14).

Ex: RING,
2,
• Data on Modem pick up Commands, Switching from Transparent to
Command Mode, Modem Hang up and Pick up and Start Dialogue with other
Modem: [lines 17-20]

DescolgModem ,
ModoTran-ModoCom ,
ColgModem ,
DialOtroModem ,

• DescolgModem: Modem pick up command (maximum number of characters: 14).

• ModoTran-ModoCom: Command to switch the modem from transparent mode to
command mode (maximum number of characters: 14).
• ColgModem: Modem hang up command (maximum number of characters: 14).
• DialOtroModem: Command to pick up and start dialogue with other modem (answer)
(maximum number of characters: 14).

Ex: ATH1,
+++,
ATH0,
ATA,

• Data on connection Established and Correct Command Response Indicators:

[Lines 21-24]

IndTxtCxEstabl ,
IndNumCxEstabl ,
IndTxtRespOK ,
IndNumRespOK ,

• IndTxtCxEstabl: Text indicator for connection established (maximum number of

characters: 24).
• IndNumCxEstabl: Numeric indicator for connection established (maximum number of
characters: 14).
• IndTxtRespOK: Text indicator for correct command response (maximum number of
characters: 14).
• IndNumRespOK: Numeric indicator for correct command response (maximum number of
characters: 14).

Ex: CONNECT,
1,
OK,
0,

M1CPTA2005I
1CPT: Substation Central Unit A-42
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data on the Dialling Command and the Telephone Number: [Line 25]

ComMarcado , NumTeléfono ,

• ComMarcado: Modem dialling command.

• NumTeléfono: Telephone number to dial (maximum number of characters: 64)

Ex: ATDT0,4157922,

• Data on the Connection Script: [Line 26]

ScriptConex ,

• ScriptConex: Connection script name (maximum number of characters: 64).

Ex: IBMNET.SCP

The file becomes:

[1] # Configuration of the remote access service

[2] 128, // INT 0x80 Interruption of SLIP Packet Driver
[3] 0, // Trace monitoring level
[4] CONSOLA LOCAL CONECTADA, // HMI engaged
[5] USER:, // User name request prompt
[6] PASSWORD:, // password request prompt
[7] ZIV, // Authorised user
[8] ZIV, // password
[9] ACCEPTED, // Acceptance indicator
[10] ACCESS DENIED, // Reject indicator
[11] 0,60000, // Win95 Mode, connection Time out (in ms)
[12] 15000,1, // Modem response time (in ms),number of rings
[13] ATZ, // Modem reset
[14] ATE0V1X1M0S0=0, // Modem initialisation command
[15] RING, // Incoming call indicator
[16] 2, // Numeric mode indicator
[17] ATH1, // pick up telephone
[18] +++, // switch from transparent mode to command mode
[19] ATH0, // hang up telephone
[20] ATA, // pick up and start dialogue with other modem
[21] CONNECT, // states connection established
[22] 1, // idem in numeric mode
[23] OK, // correct command response
[24] 0, // idem in numeric mode
[25] ATDT0,4157922,// Dialling command with telephone number
[26] IBMNET.SCP, // Connection script

M1CPTA2005I
A-43 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.10 Central Unit Redundancy Files: REDUNDA.CFG

This file “redunda.cfg” contains data on CPX/CPT central unit redundancy.

File format is:

• Data on Communications between Redundant Central Units: [Lines 1-4]

InterrupSLIP , NivelTraza , InterfaceRedunda , UsaEntSalDig ,

DirIPOtroCPX ,
PuertoRedunda , TipoRedundaHSB , VirtualIP , VirtualMAC ,
TimeAbortSocket , TimeRespCPX , TimePasiva , TimeArranqueFrio ,

• InterrupSLIP: SLIP Packet Driver interruption number.

• NivelTraza: REDUNDA task trace monitoring level. This parameter is only available on
CPT.
• InterfaceCanalRedundante: Interface of the redundant channel to connect both Central
Units. It indicates whether the communications between both Central Units is made
through serial port (0) or network, and this can be LAN1 (1) or LAN2 (2). If it is not
configured, the default value is 0. This parameter is only available for the CPT.
• UsaEntSalDig: Denotes whether digital inputs and outputs are used (1) or not (0) to
interchange the redundancy status of both Central Units. If it is not configured, the default
value is 0. This parameter is only available for CPT.
• DirIPOtroCPX: IP address of the other CPX in case of the CPX-A. In case of CPX-B/CPT
(serial redundancy); the secondary CPX/CPT does not use this parameter for serial
connection with the primary, and is used in the primary as base address for the DHCP to
generate an IP address for the primary and the secondary. For CPX-B/CPT it will be
198.168.1.1. In case of CPT with network redundancy, the IP address of the other CPT
will be configured in both CPTs.
• PuertoRedunda: Puerto de la redundancia.
• TipoRedundaHSB: Este campo indica para cada tipo de redundancia Hot Stand By (ver
Capítulo 6.16) cómo se considera la conexión con la consola:
• PuertoRedunda: Redundancy port.
• TipoRedundaHSB: This field states the HMI connection considered for each Hot Stand
By type of redundancy (see section 6.16):
 HSB type 1 redundancy (CPX/CPT):
− If it is 0 (zero), there are two HMIs, each connected to one CPX/CPT.
− If it is 1, there is only one HMI connected to the active CPX/CPT at that time. In the
latter case, the remote HMI, if it exists, will behave in the same manner.
 HSB type 2 redundancy (CPT):
− If it is 2, there are two HMIs, each connected to one of the CPTs, each with its IP
and MAC address.
− If it is 3, there is only one HMI connected to the Active CPT at that time. Said HMI
will be connected to a single IP address that is the one taken by the Active CPT at
that time (as well as a single MAC address if desired). In this way, the active CPT
will always be perceived as a single device, with the same IP and the same MAC.
 Hot-Hot Redundancy (CPT):
- If set to 4, two HMI exist, each one connected to one CPT, each with its IP address
and MAC. With this type, both CPTs interrogate the IEDs in IEC61850.

M1CPTA2005I
1CPT: Substation Central Unit A-44
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• VirtualIP: IP address of the Active CPT in HSB type 2 redundancy. In case this address
is to be used, parameter TipoRedundaHSB must be 3. Otherwise this IP address will not
be used. If it is not configured, this IP address will not be used bydefault. This parameter
is only available for CPT.
IMPORTANT: in case this address is used and, furthermore, a web HMI exists, this same
IP address value must be configured in field “ServerCurrentIP” of the web HMI
configuration file “ConsoleBaseConfig.xml” (refer to section A.22.2 of the LCWE0904A-
Embedded Web HMI manual).
• VirtualMAC: MAC address of the Active CPT in HSB type 2 redundancy. In case this
MAC address is to be used, parameter TipoRedundaHSB must be 3. Otherwise this MAC
address will not be used. If the IP address but not its MAC address of the active CPT is to
be changed, the “NONE” value will be configured. If it is not configured, this MAC address
will not be used by default. This parameter is only available for CPT.
• TimeAbortSocket: Socket abort timeout.
• TimeRespCPX: Response time of the other CPX/CPT.
• TimePasiva: Maximum time (in seconds) to wait in start mode for the other CPT to
complete the start-up process and determine in this way whether it switches to active or
passive. If it is not configured, the default value is 30. This parameter is only available for
CPT.
• TimeArranqueFrio: Time (in minutes) to determine whether after switching to active, CPT
starting is cold (must reject device changes previous to the first refresh) or hot. If the CPT
database has not been updated for more than this time, it will be considered a cold start.
If this function is not to be used, it must be configured to –1. If it is not configured, the
default value is -1. This parameter is only available for CPT.

Ex: 132,0,0,1,
128.127.60.15,
31000,3,128.127.60.1,00e0ab029006,
30,6,60,1440,

• Digital Signal Configuration Data

They are configured as explained in section A.1: [lines 6-12]

Ex: 21,// Num. Signals

0,0,0,0,0,
1,0,0,0,0,
2,0,0,0,0,
…
20,0,0,0,0,

• Command Configuration Data

They are configured as explained in section A.1: [lines 14-18]

Ex: 2,// Num. Commands

0,269,2,500,0,269,2,269,-1,0,0,0,
1,269,2,500,1,269,2,269,-1,0,0,0,

M1CPTA2005I
A-45 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] 132,0,0,1,// packet driver interruption,NivelTraza,Interface,UsaIODig,

[2] 128.127.60.15, // IP address of the other CPX
[3] 31000,3,128.127.60.1,00e0ab029006,
//PuertoRedun,TipoRedun,VirtualIP,VirtualMAC,
[4] 30,6,60,1440,// TimeAbort,TimeRespuesta,TimePasiva,TimeAranqueFrio,
[5] # Digital signal configuration
[6] 21,// ISCs Number
[7] 0,0,0,0,0,0, // COMMUNICATIONS ACTIVITY LEVEL 1
[8] 1,0,0,0,0,0, // UCS 1
[9] 2,0,0,0,0,0, // UCS 1
[10] 3,0,1,1,0,0, // INCONSISTENT DATABASES
[11] 4,1,0,0,0,1, // CENTRAL POSTS COMMUNICATIONS FAILURE
[12] 5,1,0,0,0,1, // DIFFERENT CONFIGURATIONS BETWEEN UCS´S
[13] 6,0,0,0,0,0, // SPARE 6
[14] 7,1,0,0,0,1, // BACKUP UCS OUT OF SERVICE
[15] 8,0,0,0,0,0, // SPARE 8
[16] 9,0,0,0,0,0, // SPARE 9
[17] 10,0,0,0,0,0, // SPARE 10
[18] 11,0,0,0,0,0, // SPARE 11
[19] 12,0,0,0,0,0, // SPARE 12
[20] 13,0,0,1,0,0, // CHANGE TO ACTIVE COMMAND
[21] 14,0,0,1,0,0, // CHANGE TO PASIVE COMMAND
[22] 15,1,0,0,0,1, // ACTIVE / PASIVE STATE SWITCHING
[23] 16,0,0,0,0,0, // COMMUNICATIONS ACTIVITY LEVEL 1 UCS BCK
[24] 17,1,0,0,0,1, // UCS OUT OF SERVICE
[25] 18,1,0,0,0,1, // COMMUNICATIONS FAILURE BETWEEN UCS´S I/O
[26] 19,0,0,0,0,0, // BACKUP UCS
[27] 20,0,0,0,0,0, // UCS PICKUP
[28] # Command configuration
[29] 2,// Num. commands
[30] # command,isc status(device,signal nr),time,negation,isc
ok(device,signal nr),
[31] # isc failure(device,signal nr),double,nr blockings,(device, dig.
signal) per blocking
[32] 0,269,2,500,0,269,2,269,-1,0,0,0, // INTERROGA
[33] 1,269,2,500,1,269,2,269,-1,0,0,0, // LISTEN

M1CPTA2005I
1CPT: Substation Central Unit A-46
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.11 Remote HMI File: REMOTA.CFG

This file “remota.cfg” contains remote HMI configuration data of CPX and CPT central units.

File format is as follows:

• Data on Remote HMI Configuration: [Lines 1-3]

SocketRemota ,
ResetOperativo ,
Mandos ,

• SocketRemota: Number of Central unit communications port to connect to the remote

HMI. Default value is 32009 that must match the field PortComRemota of the Remote
HMI’s “tcp.cfg” file.
• ResetOperativo: States whether on central unit reset the remote HMI starts enabled by
default, namely, with the operating permissions configured in HMI’s “remota.cfg” (1) or
not enabled, namely, without operating permissions (0). The default value is 1.
• Mandos: This bit states whether the CPX/CPT executes remote HMI commands (1) or
not (0). The default value is 0.

Ex: 32009,
1,
0,

• Data on Server Socket Configuration: [Lines 4-5]

These data are used by the Additional Remote HMI’s access function. (Refer to section A.6 for
details).

SocketServidor , ToutSockServ ,
MandosServ ,

• SocketServidor: Number of Central unit communications port to connect to the remote

HMI servers. The default value is 32010 that must match field PortComRemota of the
Additional Remote HMI’s “tcp.cfg” file.
• ToutSockServ: Amount of time without receiving any message by the HMI for the
connection to be deemed broken. If this time times out, the socket related to this
connection is closed. The value is expressed in seconds.
• MandosServ: This bit states whether CPX/CPT executes commands received from
remote HMI servers (1) or not (0). The default value is 0. This field affects all HMIs
connected to the SocketServidor port.

Ex: 32010,30,
0,

M1CPTA2005I
A-47 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] 32009,// Remote Socket

[2] 1, // Operating Reset
[3] 0,// Remote HMI commands NOT allowed
[4] 32010,30,// Server Socket, ToutSockServ,
[5] 0,// Server commands.

M1CPTA2005I
1CPT: Substation Central Unit A-48
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.12 Network Configuration Files

Data on the IP address of Central Unit ethernet ports will be available at Central Unit application
level within tcp.cfg file for all models CPX/CPT.

Also, CPT models count on a file autorun.cfg to configure IP addresses of Central Unit ethernet
ports at operating system level, therefore, before running the Central Unit application itself.

A.12.1 Operating System Network Configuration File: AUTORUN.CFG

This file contains network configuration data of the Central Unit ethernet ports, only for CPT
models.

File format is as follows:

• Address, Subnet Mask and DHCP 9 Client Configuration Data:

IP1 = DirIP1Value
NETMASK1 = NetMask1Value
DHCP1 = DHCP1Value
IP2 = DirIP2Value
NETMASK2 = NetMask2Value
DHCP2 = DHCP2Value

• DirIP1Value: IP address of first CPT network adapter.

• NetMask1Value: Subnet mask of first CPT network adapter.
• DHCP1Value: CPT’s DHCP client enable (value 1) / disable (value 0) flag of first network
adapter.
• DirIP2Value: IP address of second CPT network adapter.
• NetMask2Value: Subnet mask of second CPT network adapter.
• DHCP2Value: CPT’s DHCP client enable (value 1) / disable (value 0) flag of second
network adapter.

Ex: IP1 = 10.193.60.201

NETMASK1 = 255.255.255.0
DHCP1 = 0

IP2 =
NETMASK2 =
DHCP2 = 1

9
DHCP: Dynamic Host Configuration Protocol to obtain the network configuration automatically from a network
server.

M1CPTA2005I
A-49 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] IP1 = 10.193.60.201

[2] NETMASK1 = 255.255.255.0
[3] DHCP1 = 0
[4]
[5] IP2 =
[6] NETMASK2 =
[7] DHCP2 = 1

A.12.2 Central Unit Application Network Configuration File: TCP.CFG

This file “tcp.cfg” contains central address and communications port data.

File format is as follows:

• Central Address and Communications Port Configuration Data: [Lines 1-12]

DirIP_LAN1 , DirIP_LAN2 , IndexLANCentral ,

PortCentral ,
PortPROCOME ,
PortMONITOR ,
PortHISTORIC ,
TimeoutSocketCENTRAL , TimeoutSocketREMOTA ,
TimeoutSocketHISTORIC ,
TimeoutSocketPROCOME ,
TimeoutSocketMONITOR ,
NetMask1 , NetMask2 ,
DefaultGateway , IndexLAN_GW ,
DirDNS_LAN1 , DirDNS_LAN2 ,

• DirIP_LAN1: IP address of Central Unit first network adapter.

• DirIP_LAN2: IP address of Central Unit second network adapter (only available for CPT
models).
• IndexLANCentral: Index of the network adapter to be used by the Central Unit application
(1: First network adapter; 2: Second network adapter). If this parameter is not configured
the default value will be taken.
• PortCentral: CENTRAL socket communication port number. It must match parameter
PortComLocal of HMI’s “tcp.cfg” file.
• PortPROCOME: PROCOME socket communications port number.
• PortMONITOR: MONITOR socket communications port number.
• PortHISTORIC: HISTORIC socket communications port number.
• TimeoutSocketCENTRAL: CENTRAL socket timeout (in msec.). If this socket connection
remains established without interchanging data for a time exceeding
TimeoutSocketCentral, the socket will abort the connection.
• TimeoutSocketREMOTA: REMOTA socket timeout (in msec.). This field is only included if
a remote HMI exists. The default value is 60000 msec.
• TimeoutSocketHISTORIC: HISTORIC socket timeout (in msec.).

M1CPTA2005I
1CPT: Substation Central Unit A-50
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• TimeoutSocketPROCOME: PROCOME socket timeout (in sec.). The default value is 300
seconds.
• TimeoutSocketMONITOR: MONITOR socket timeout (in sec.). The default value is 300
seconds.
• NetMask1: Subnet mask of first network adapter (only available for CPT models).
• NetMask2: Subnet mask of second network adapter (only available for CPT models).
• DefaultGateway: IP address associated to the default Gateway (only available for CPT
models).
• IndexLAN_GW: Network adapter index associated to the default Gateway (only available
for CPT models).
• DirDNS_LAN1: IP address of the DNS server associated to the first network adapter (only
available for CPT models).
• DirDNS_LAN2: IP address of the DNS server associated to the second network adapter
(only available for CPT models).

IMPORTANT: As the default Gateway can also be configured through a routing input
within route.cfg file, in order to obtain the desired operation of the Central Unit routing
table, it is recommended to configure the default Gateway only in one of the two files,
route.cfg or tcp.cfg, but never in both files.

Ex: 128.127.60.26,
32000,
32001,
32002,
32003,
60000,60000,
7600,
300,
300,
255.255.0.0,0,
128.127.60.250,1,
0,0,

The file becomes:

[1] 128.127.60.26, // Central IP

[2] 32000, // Central Port
[3] 32001, // PROCOME
[4] 32002, // MONITOR port
[5] 32003, // HISTORICOS port
[6] 60000,60000, // CENTRAL Socket Timeout, Timeout Socket REMOTA
[7] 7600,// HISTORIC Socket Timeout
[8] 300,// PROCOME Socket Timeout
[9] 300, // MONITOR Socket Timeout
[10] 255.255.0.0,0,// Subnet masks
[11] 128.127.60.250,1,// Default Gateway, Associated LAN Index
[12] 0,0,// DNS Servers

M1CPTA2005I
A-51 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.13 Control Function Configuration Files

In this section the configuration files of the different control functions are described. These files
are:

- AUTOH.CFG: H and Y control function configuration file.

- AUTOH2.CFG: H2 control function configuration file.
- TIERR_i.CFG: Ground control function configuration file.
- ERAS.CFG: Eras control function configuration file.
- TVIRTUAL.CFG: Eras control function virtual terminal configuration file.

A.13.1 H Control Function File: AUTOH.CFG

This file “autoh.cfg” saves data related to the H control function (virtual device the address of
which within the Central Unit database is 260), as well as its settings. The H control function
consists at the same time of five subcontrol functions. These five subcontrol functions need
certain parameters:

Voltage Presence / Absence Control Function. This control function is at the same time
segregated into four additional control functions. There will be a control function for each of the
voltages involved in the H control function operation. All of them have the same structure.
Every control function has a voltage presence setting and a voltage absence setting, as well as
a voltage presence time setting and a voltage absence time setting.

Control Function for the Definition of High Voltage Status. This control function, together
with the above control function, defines the status of the high voltage pair.

Control function settings are the stability time, switch time and equality delay time (the latter is
fixed).

Medium Voltage Switchgear Control Function. Control function settings are configured in
order to operate system medium voltage circuits. Two parameters are needed, one to activate
the control function and the other for medium voltage switching time.

High Voltage Switchgear and Protection Trip Switching do not have user parameterised
settings and are therefore transparent.

Settings of these subcontrollers are saved in this file. File format is as follows:
• List of Control Functions that Pick up: [Lines 2-9]

BitArrPRESMULA ,
BitArrPRESMULB ,
BitArrPRESUA ,
BitArrPRESUB ,
BitArrESTALTA ,
BitArrMANALTA ,
BitArrMANMEDIA ,
BitArrCONDISP ,

M1CPTA2005I
1CPT: Substation Central Unit A-52
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• BitArrPRESMULA: This bit indicates whether the line A voltage presence control function
activates (1) or not (0).
• BitArrPRESMULB: This bit indicates whether the line B voltage presence control function
activates (1) or not (0).
• BitArrPRESUA: This bit indicates whether the busbar A voltage presence control function
activates (1) or not (0).
• BitArrPRESUB: This bit indicates whether the busbar B voltage presence control function
activates (1) or not (0).
• BitArrESTALTA: This bit indicates whether the high voltage status control function
activates (1) or not (0).
• BitArrMANALTA: This bit indicates whether the high voltage switchgear control function
activates (1) or not (0).
• BitArrMANMEDIA: This bit indicates whether the medium voltage switchgear control
function activates (1) or not (0).
• BitArrCONDISP: This bit indicates whether the protection trip switching control function
activates (1) or not (0).

Ex: 1,//PRESMULA
1,//PRESMULB
0,//PRESUA
0,//PRESUB
1,//ESTALTA
1,//MANALTA
1,//MANMEDIA
1,//CONDISP

• H Control Function Settings: [Lines 11-12]

Servicio , V_NominalAlta , ExisteEspera , TimeEspera , TipoAuto ,

HY
ISCDefecto ,

• Servicio: This bit indicates whether H control function settings can be changed from the
HMI (1) or not (0).
• V_NominalAlta: Nominal voltage level to detect high voltage presence/absence.
• ExisteEspera: Enables the delay time between commands in the same sequence.
• TimeEspera: Configurable delay time (in milliseconds) between commands in the same
sequence.
• TipoAutoHY. Indicates the type of control function to be activated: 1 = H Control Function;
2 = and Control Function. Default value: 1.
• ISCDefecto: Digital signal identifier that reflects the default status of the H control function
(set to manual by default).

Ex: 0,30.0,1,2000,1,
7,

M1CPTA2005I
A-53 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Line A Voltage Presence/Absence Control Function

(PRESMULA): [Lines 14-16]

DirEq , MEA ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq: Address of the device that measurement MULA belongs to, within the Central Unit
database.
• MEA: Identifier of said measurement.
• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.
• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 1,0,
80.0,50.0,
1000,1000,

• Configuration Data of Line B Voltage Presence/Absence Control Function

(PRESMULB): [Lines 18-20]

DirEq , MEA ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq: Address of the device that measurement MULB belongs to, within the Central Unit
database.
• MEA: Identifier of said measurement.
• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.
• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 1,1,
80.0,50.0,
1000,1000,

M1CPTA2005I
1CPT: Substation Central Unit A-54
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Busbar A Voltage Presence/Absence Control Function

(PRESUA): [Lines 22-26]

DirEq_B , MEA_B ,
DirEq_C , MEA_C ,
DirEq_BC , MEA_BC ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq_B: Address of the device that phase B measurement belongs to, within the Central
Unit database.
• MEA_B: Identifier of phase B measurement.
• DirEq_C: Address of the device that phase C measurement belongs to, within the Central
Unit database.
• MEA_C: Identifier of phase C measurement.
• DirEq_BC: Address of the device that phase BC measurement belongs to, within the
Central Unit database.
• MEA_BC: Identifier of phase BC measurement.
• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.
• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 14,1,
14,1,
14,1,
80.0,50.0,
1000,1000,

• Configuration Data of Busbar B Voltage Presence/Absence Control Function

(PRESUB): [Lines 28-32]

DirEq_B , MEA_B ,
DirEq_C , MEA_C ,
DirEq_BC , MEA_BC ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq_B: Address of the device that phase B measurement belongs to, within the Central
Unit database.
• MEA_B: Identifier of phase B measurement.
• DirEq_C: Address of the device that phase C measurement belongs to, within the Central
Unit database.
• MEA_C: Identifier of phase C measurement.
• DirEq_BC: Address of the device that phase BC measurement belongs to, within the
Central Unit database.

M1CPTA2005I
A-55 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• MEA_BC: Identifier of phase BC measurement.

• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.
• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 14,2,
14,2,
14,2,
80.0,50.0,
1000,1000,

• Configuration Data of High Voltage Status Control Function (ESTALTA):

[Lines 34-36]

TimeEstabilidad ,
TimeConmutación ,
TimeEsperaIgualdad ,

• TimeEstabilidad: Stability time (in msec.). The range of possible values is 0-300000, the
default value being 60000 milliseconds. Step is 100 milliseconds.
• TimeConmutación: Switch time (in msec.). The range of possible values is 0-10000, the
default value being 5000 milliseconds. Step is 100 milliseconds.
• TimeEsperaIgualdad: Equality Delay Time (It is FIXED: 1000 msec.).

Ex: 60000,
5000,
1000,

• Configuration Data of Medium Voltage Switchgear Control Function

(MANMEDIA): [Lines 38-39]

Servicio , V_NominalMedia ,
TimeConmutación ,

• Servicio: Bit que indica si el automatismo está en servicio (1) o no (0).

• V_NominalMedia: Nivel de tensión nominal para la detección de presencia/ausencia
de tensión en baja.
• TimeConmutación: Tiempo de Conmutación de media (en mseg.). El rango de
valores posibles es 0-10000, siendo el valor por defecto 5000 milisegundos. El
paso es de 100 milisegundos.

Ex: 1, 13.0,
5000,

M1CPTA2005I
1CPT: Substation Central Unit A-56
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of High Voltage Switchgear Control Function (MANALTA):

[Lines 44-50]

NumMandos ,
DirEq , ISE , DCO , (*) (**)

(*) It repeats for each command i the corresponding sequence. There will be as many as
shown in NumCommands.
(**) It repeats for each sequence of MANALTA controller. There will be 22 sequences (0-21)
that will be listed below.

• NumCommands: Number of commands per sequence (maximum 4 commands).

• DirEq: Address of the equipment that the command belongs to, within the Central Unit
database.
• ISE: Command Identifier.
• DCO: Command DCO.

A table with 22 sequences is displayed. For the H Control Function said sequences are:

Table A-11: H Control Function Operations

SEQ Nr Operations
0 Default status
1 Open 52LB
2 Close 52LAB
3 Close 52LA
4 Open 52LA
5 Close 52LB
6 Close 52LAB and open 52LB
7 Close 52LAB and open 52LA
8 Open 52LB and close 52LAB
9 Open 52LA and close 52LAB
10 Close 52LB and open 52LA
11 Close 52LB and open 52LAB
12 Open 52LA and close 52LB
13 Close 52LA and open 52LB
14 Close 52LA and open 52LAB
15 Open 52LB and close 52LA
16 Close 52LA and close 52LAB
17 Close 52LB and close 52LAB
18 Close 52LA and close 52LB
19 Open 52LAB
20 Close 52LA and close 52LB and open 52LAB
21 Set the control function to manual

Ex: # SEQUENCE 0
1, //Num. Commands
260,9,2,
# SEQUENCE 1
…
# SEQUENCE 21
1, //Num. Commands
260,13,2,

M1CPTA2005I
A-57 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

For the case of the Y Control Function, the sequences are as follows:

Table A-12: Y Control Function Operations

Nº de SEQ Operaciones
0 Default status
1 Open 52AB, Open 89LA, Close 89LB and Close 52AB
2 Close 89LB and Open 89LA
3 Open 52AB, Open 89LB, Close 89LA and Close 52AB
4 Close 89LA and Open 89LB
5 Open 89LB
6 Open 89LA and Close 52AB
7 Open 89LB and Close 52AB
8 Close 89LB and Close 52AB
9 Close 89LA and Close 52AB
10 Open 89LA, Close 89LB and Close 52AB
11 Close 52AB
12 Open 89LB, Close 89LA and Close 52AB
13 Open 89LA
14 Open 52AB, Close 89LB and Close 52AB
15 Open 52AB, Close 89LA and Close 52AB
16 --- (Reset)
17 --- (Reset)
18 --- (Reset)
19 --- (Reset)
20 --- (Reset)
21 Set the control function to manual

• Configuration Data of H Control Function Digital Signals. They are Configured

as Explained in Section A.1: [Lines 52-56]

Ex: 28,// Num. Signals

0,0,1,1,0,
1,0,1,1,0,
…
27,0,1,1,0,

• Configuration Data of H Control Function Commands. They are Configured

as Explained in Section A.1: [Lines 58-64]

Ex: 14,// Num. Commands

0,260,8,1,0,260,-1,260,-1,0,0,0,
1,260,9,1,0,260,-1,260,-1,0,0,0,
…
13,260,7,1,0,260,-1,260,-
1,0,1,256,24,0,0,

M1CPTA2005I
1CPT: Substation Central Unit A-58
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of H Control Function Input Signals (Sequence Signals):

[Lines 66-69]

DirEq , ISC , (*)

(*) It repeats for each H control function digital signal. There will be 23 signals listed below.

• DirEq: Address of the device that the signal belongs to, within the Central Unit database.
• ISC: Signal Identifier.

Fort he H Control Function, said signals are:

Table A-13: H Control Function Digital Signal

Signal Description
1. 52LA Closed
2. 52LAB Closed (Not used)
3. 52LB Closed
4. S_00 (Voltage absence on lines A and B)
5. S_01 (Voltage absence on line A and presence on line B)
6. S_10 (Voltage presence on line and absence on line B)
7. S_11 (Voltage presence on lines A and B)
8. P_A (Preference A)
9. P_B (Preference B)
10. P_AB (Preference AB)
11. MAN (Manual)
12. MED_ACT (Medium voltage control function Actuated)
13. AUT_ACT (Action authorised)
14. 52TA Closed
15. 52TB Closed
16. 52B12 Closed
17. UA
18. UB
19. 86TA
20. 86TB (Not used)
21. ULA
22. ULB
23. Final trip

M1CPTA2005I
A-59 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

For the case of the Y Control Function, the signals are as follows:

Table A-14: Control Function Digital Signal (I)

Señal Descripción
0 89LA_C Disconnect Swtich 89LA Closed
1 89LA_A Disconnect Swtich 89LA Open
2 89LB_C Disconnect Swtich 89LB Closed
3 89LB_A Disconnect Swtich 89LB Open
4 52AB_C Breaker 52AB Closed
5 52AB_A Breaker 52AB Open
6 AUT_ACT Control Function Condition Active
7 S_00 Absence of Voltage on Both Lines
8 S_01 Absence of Voltage on Line A and Presence on Line B
9 S_10 Presence of Voltage on Line A and Absence on Line B
10 S_11 Presence of Voltage on Both Lines
11 P_A Preference A
12 P_B Preference B
13 P_AB Preference AB (not used)
14 MAN Manual
15 MED_ACT Medium Voltage Control Function Activated
16 86TA_ACT Trip 86A
17 86TB_ACT Trip 86B (not used)

Ex: 1,46,
1,246,
…
20,2,

• Configuration Data of Signal that Indicates whether the Substation is Set to

Local: [Line 71]

DirEq , ISC ,

• DirEq: Address of the device that the signal belongs to, within the Central Unit database.
• ISC: Digital signal Identifier.

Ex: 256,0,

M1CPTA2005I
1CPT: Substation Central Unit A-60
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # List of devices that pick up

[2] 1, // PRESMULA
[3] 1, // PRESMULB
[4] 0, // PRESUA
[5] 0, // PRESUB
[6] 1, // ESTALTA
[7] 1, // MANALTA
[8] 1, // MANMEDIA
[9] 1, // CONDISP
[10] # H control function settings
[11] 0,30.0,1,2000, // In Service, Vn Alta, Habil. Espera, TimeEspera (ms)
[12] 7, // (ISC number) MANUAL by default
[13] # PRESMULA settings
[14] 1,0, // Address and number (MEA)of measurement MULA
[15] 80.0,50.0, // AJ. PRES,AUSEN
[16] 1000,1000, // AJ, T. PRES,AUSEN
[17] # PRESMULB Settings
[18] 1,1, // Idem MULB
[19] 80.0,50.0, // AJ. PRES,AUSEN
[20] 1000,1000, // AJ. T.PRES,AUSEN
[21] # PRESUA Settings
[22] 14,1, // MEA (MuA04)
[23] 14,1, // MEA (MuA08)
[24] 14,1, // MEA (MuA48)
[25] 80.0,50.0, // AJ. PRES,AUS
[26] 1000,1000, // AJ. T.PRES, AUSEN
[27] # PRESUB Settings
[28] 14,2, // MEA (MuB04)
[29] 14,2, // MEA (MuB08)
[30] 14,2, // MEA (MuB48)
[31] 80.0,50.0, // AJ. PRES,AUS
[32] 1000,1000, // AJ. T.PRES, AUSEN
[33] # ESTALTA Settings
[34] 60000, // TI. ESTABLE
[35] 5000, // TI. CONMUTA
[36] 1000, // TI ESPERA IGUAL.
[37] # MANMEDIA Settings
[38] 1,13.0, // EN SERVICIO, Vn Media
[39] 5000, // TI. CONMUTA.
[40] # MANALTA Sequence table (22 inputs)

M1CPTA2005I
A-61 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

[41] # every input 0-21 has a number of commands to execute

[42] # and the list of commands (DIR,ISE,DCO)
[43] # SEQ 0 (Default) never executes
[44] 1, // Num. Commands
[45] 260,9,2, // Dir, label and DCO
[46] # SEQ 1 // ABRIR 52LB
[47] …
[48] # SEQ 21 // SET CONTROL FUNCTION TO MANUAL
[49] 1,
[50] 260,13,2, // Set to Manual from Control Function
[51] # List of AUTO H ISCs
[52] 28, // Number of ISCs
[53] 0,0,1,1,0,
[54] 1,0,1,1,0,
[55] …
[56] 27,0,1,1,0,
[57] # List of ISE (commands) of AUTO H
[58] 14, // Number of ISEs
[59] # ISE,ISC exe(dir,isc),Tiempo,neg,ISC OK(dir,isc), ISC
fail(dir,isc),doble,
[60] # nº blqs,.....
[61] 0,260,8,1,0,260,-1,260,-1,0,0,0, // PREF A FROM PANEL
[62] 1,260,9,1,0,260,-1,260,-1,0,0,0, // PREF B FROM PANEL
[63] …
[64] 13,260,7,1,0,260,-1,260,-1,0,1,256,24,0,0, // MAN FROM CONTROL
FUNCTION
[65] # List of sequences ISCs (Dir,Isc)
[66] 1,46, // 52LA Closed
[67] 1,246, // 52LAB Closed (Not used)
[68] …
[69] 20,2, // FINAL TRIP
[70] # Substation ISC to Local
[71] 256,0,

A.13.2 H2 Control Function File: AUTOH2.CFG

This file “autoh2.cfg” saves data related to the H2 control function (virtual device the address
of which within the Central Unit database is 260), as well as its settings. The H2 control function
consists at the following subcontrol functions. These subcontrol functions need certain
parameters:

Voltage Presence / Absence Control Function. This control function is at the same time
segregated into two additional control functions. There will be a control function for each of the
voltages involved in the H2 control function operation. The two control functions have the same
structure.
Every control function has a voltage presence setting and a voltage absence setting, as well as
a voltage presence time setting and a voltage absence time setting.

Control Function for the Definition of High Voltage Status. This control function, together
with the above control function, defines the status of the high voltage pair.
Control function settings are the stability time, switch time and equality delay time (the latter is
fixed).

High Voltage Switchgear and Protection Trip Switching do not have user parameterised
settings and are therefore transparent.

M1CPTA2005I
1CPT: Substation Central Unit A-62
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Settings of these subcontrollers are saved in this file. File format is as follows:
• List of Control Functions that Pick up: [Lines 2-9]
In this AUTOH2 version, three of the existing control functions in the previous version do
NOT exist. They are the following:

- Voltage presence/absence in the A bus control function.

- Voltage presence/absence in the B bus control function.
- Medium Voltage Maneuvers control function.

BitArrPRESMULA ,
BitArrPRESMULB ,
BitArrPRESUA , This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0
BitArrPRESUB , This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0
BitArrESTALTA ,
BitArrMANALTA ,
BitArrMANMEDIA , This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0
BitArrCONDISP ,

• BitArrPRESMULA: This bit indicates whether the line A voltage presence control function
activates (1) or not (0).
• BitArrPRESMULB: This bit indicates whether the line B voltage presence control function
activates (1) or not (0).
• BitArrPRESUA: This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0.
• BitArrPRESUB: This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0.
• BitArrESTALTA: This bit indicates whether the high voltage status control function
activates (1) or not (0).
• BitArrMANALTA: This bit indicates whether the high voltage switchgear control function
activates (1) or not (0).
• BitArrMANMEDIA: This control function does NOT exist in AUTOH2. It is ALWAYS
configured to 0.
• BitArrCONDISP: This bit indicates whether the protection trip switching control function
activates (1) or not (0).

Ex: 1,//PRESMULA
1,//PRESMULB
0,//PRESUA
0,//PRESUB
1,//ESTALTA
1,//MANALTA
0,//MANMEDIA
1,//CONDISP

• H Control Function Settings: [Lines 11-12]

Servicio , V_NominalAlta , ExisteEspera , TimeEspera , TipoAutoHYH2 ,

ISCDefecto ,

M1CPTA2005I
A-63 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Servicio: This bit indicates whether H control function settings can be changed from the
HMI (1) or not (0).
• V_NominalAlta: Nominal voltage level to detect high voltage presence/absence.
• ExisteEspera: Enables the delay time between commands in the same sequence. In this
case the AUTOH2 will ALWAYS be enabled (at 1).
• TimeEspEntreMandos: Configurable delay time (in milliseconds) between commands in
the same sequence. Its default value is 2000 ms
• TipoAutoHYH2. Indicates the type of control function to be activated: 1 = H Control
Function; 2 = and Control Function; 3 = H2 Control Function. The default value is 3, and it
will be a fixed value in this file
• ISCDefecto: Digital signal identifier that reflects the default status of the H control function
(set to manual mode by default).

Ex: 0,30.0,1,2000,3,
7,

• Configuration Data of Line 1 Voltage Presence/Absence Control Function

(PRESMULA): [Lines 14-16]

DirEq , MEA ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq: Address of the device that measurement MULA belongs to, within the Central Unit
database.
• MEA: Identifier of said measurement.
• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.
• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 10,0,
80.0,50.0,
1000,1000,

The values of the percentage settings and voltage presence and absence times will
only be configured in this section associated to Line 1, since in the case of Line 2 they
will ALWAYS be the same.
• Configuration Data of Line 2 Voltage Presence/Absence Control Function
(PRESMULB): [Lines 18-20]

DirEq , MEA ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

• DirEq: Address of the device that measurement MULB belongs to, within the Central Unit
database.
• MEA: Identifier of said measurement.
• NivelPresencia: Voltage presence level (in % of Vnominal). The range of possible values
is 50-100, the default value being 80%. Step is 0.1%.

M1CPTA2005I
1CPT: Substation Central Unit A-64
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• NivelAusencia: Voltage absence level (in % of Vnominal). The range of possible values is
0-70, the default value being 50%. Step is 0.1%.
• TimePresencia: Voltage presence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.
• TimeAusencia: Voltage absence delay time (in msec.). The range of possible values is
500-5000, default value being 1000 milliseconds. Step is 100 milliseconds.

Ex: 11,1,
80.0,50.0,
1000,1000,

The values of the percentage settings and voltage presence and absence times in this
section will ALWAYS be the same as those defined in the previous section.

• Configuration Data of Busbar A Voltage Presence/Absence Control Function

(PRESUA): [Lines 22-26]
Although this automation is NOT included in the AUTOH2, it will be configured as if it
existed to maintain compatibility with configurations made with the previous version
(AUTOH). For this, as its values will not be used at execution time, we will be able to configure
them with any value so we will use those previously configured in previous automatisms.
Specifically, we will use those of the presence/absence of voltage automatism in Line A.

The first three lines refer to three measurements (of phases B, C and BC), so they will be
configured with the only existing measurement associated with the presence/absence of voltage
on Line A control function, which has been previously configured. We will do the same with the
levels of presence and absence, and their associated times, which we will also take from said
control function.

DirEq_B , MEA_B ,
DirEq_C , MEA_C ,
DirEq_BC , MEA_BC ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

Ex: 10,1,
10,1,
10,1,
80.0,50.0,
1000,1000,

• Configuration Data of Busbar B Voltage Presence/Absence Control Function

(PRESUB): [Lines 28-32]
Although this automation is NOT included in the AUTOH2, it will be configured as if it
existed to maintain compatibility with configurations made with the previous version
(AUTOH). For this, as its values will not be used at execution time, we will be able to
configure them with any value so we will use those previously configured in previous
automatisms. Specifically, we will use those of the presence/absence of voltage automatism
in Line B.

M1CPTA2005I
A-65 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The first three lines refer to three measurements (of phases B, C and BC), so they will be
configured with the only existing measurement associated with the presence/absence of voltage
on Line B control function, which has been previously configured. We will do the same with the
levels of presence and absence, and their associated times, which we will also take from said
control function.

DirEq_B , MEA_B ,
DirEq_C , MEA_C ,
DirEq_BC , MEA_BC ,
NivelPresencia , NivelAusencia ,
TimePresencia , TimeAusencia ,

Ex: 14,2,
14,2,
14,2,
80.0,50.0,
1000,1000,

• Configuration Data of High Voltage Status Control Function (ESTALTA):

[Lines 34-36]

TimeEstabilidad ,
TimeConmutación ,
TimeEsperaIgualdad ,

• TimeEstabilidad: Stability time (in msec.). The range of possible values is 0-300000, the
default value being 60000 milliseconds. Step is 100 milliseconds.
• TimeConmutación: Switch time (in msec.). The range of possible values is 0-10000, the
default value being 5000 milliseconds. Step is 100 milliseconds.
• TimeEsperaIgualdad: Equality Delay Time (It is a FIXED value: 1000 msec.). This setting
is NOT CONFIGURABLE. It is for information only, and will NOT be displayed on the
HMI's control function settings screen.

Ex: 60000,
5000,
1000,

• Configuration Data of Medium Voltage Switchgear Control Function

(MANMEDIA): [Lines 38-39]
Although this automation is NOT included in the AUTOH2, it will be configured as if it
existed to maintain compatibility with configurations made with the previous version
(AUTOH). Since their values will not be used at execution time, we can configure them with any
value.

The first configuration parameter indicates that the control function is in service, so we will set
the default value to 0. The second one indicates the nominal value for detecting Medium
Voltage presence/absence, so we will configure it, for example, with the default value of 13 KV.
As for the third parameter, which was the switching time associated with that control function,
we will configure it to the default value of 5000 ms.

M1CPTA2005I
1CPT: Substation Central Unit A-66
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Servicio , V_NominalMedia ,
TimeConmutación ,

Ex: 0, 13.0,
5000,

• Configuration Data of High Voltage Switchgear Control Function (MANALTA):

[Lines 44-66]

NumMandos ,
DirEq , ISE , DCO , (*) (**)

(*) It repeats for each command i the corresponding sequence. There will be as many as
shown in NumCommands.
(**) It repeats for each sequence of MANALTA controller. There will be 8 sequences (0-7)
that will be listed below.

• NumCommands: Number of commands per sequence (maximum 4 commands).

• DirEq: Address of the equipment that the command belongs to, within the Central Unit
database.
• ISE: Command Identifier.
• DCO: Command DCO.

A table with 8 sequences is displayed. For the H2 Control Function said sequences are:

Table A-15: H2 Control Function Operations

SEQ Nr Operations
0 Default
1 Open 52L1 Breaker
2 Close 52L1 Breaker
3 Open 52L2 Breaker
4 Close 52L2 Breaker
5 Open 52L1-2 Breaker (Coupling)
6 Close 52L1-2 Breaker (Coupling)
7 Swith to MANUAL

M1CPTA2005I
A-67 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: # SEQUENCE 0 (default)

1, //Num. Commands
260,9,2,
# SEQUENCE 1 (Open 52L1)
1,//Num. Commands
10,6,2,
# SEQUENCE 2 (Close 52L1)
1,//Num. Commands
10,7,2,
# SEQUENCE 3 (Open 52L2)
1,//Num. Commands
11,6,2,
# SEQUENCE 4 (Close 52L2)
1,//Num. Commands
11,7,2,
# SEQUENCE 5 (Open 52L1-2)
1,//Num. Commands
12,6,2,
# SEQUENCE 6 (Close 52L1-2)
1,//Num. Commands
12,7,2,
# SEQUENCE 7
1,//Num. Commands
260,13,2,

• Configuration Data of H2 Control Function 33 Digital Signals. They are

Configured as Explained in Section A.1: [Lines 68-72]

Ex: 33,//Num. Signals

0,0,1,1,0,0,
1,0,1,1,0,0,
…
31,0,1,1,0,0,
32,0,1,1,0,0,
• Configuration Data of H2 Control Function 14 Commands. They are
Configured as Explained in Section A.1: [Lines 74-80]

• Datos de configuración de los 14 mandos del automatismo de la H2. Se

configuran de la manera explicada en el apartado A.1: [líneas 74-80 They will
be the same configured in the previous version.

Ex:14,//Num. Commands
0,260,8,500,0,260,-1,260,-1,0,0,0, //activate pref1 from Panel
1,260,9,500,0,260,-1,260,-1,0,0,0, //activate pref2 from Panel
2,260,10,500,0,260,-1,260,-1,0,0,0,//activate pref12 from Panel
3,260,7,500,0,260,-1,260,-1,0,0,0, //auto to manual from Panel
4,260,-1,500,0,260,-1,260,-1,0,0,0,//reset auto from Panel
5,260,8,500,0,260,-1,260,-1,0,0,0, //activate pref1 from Remote
Control
6,260,9,500,0,260,-1,260,-1,0,0,0, // activate pref2 from Remote
Control
7,260,10,500,0,260,-1,260,-1,0,0,0,// activate pref12 from Remote
Control
8,260,7,500,0,260,-1,260,-1,0,0,0, //auto to manual from Remote
Control

M1CPTA2005I
1CPT: Substation Central Unit A-68
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

9,260,-1,500,0,260,-1,260,-1,0,0,0,//rset auto from Remote Control

10,260,8,500,0,260,-1,260,-1,0,0,0,//activate pref1 from Control
Function
11,260,9,500,0,260,-1,260,-1,0,0,0,// activate pref2 from Control
Function
12,260,10,500,0,260,-1,260,-1,0,0,0,// activate pref12 from Control
Function
13,260,7,500,0,260,-1,260,-1,0,0,0,//auto to manual from Control
Function

• Configuration Data of H2 Control Function first 23 Input Signals (Sequence

Signals): [Lines 77-85]
The rest of the digital signals up to a total of 38 will be configured later. This is done for
compatibility with settings made in the previous version (AutoH).
DirEq , ISC , (*)

(*)It repeats for each H control function digital signal. There will be 23 signals listed
below.

• DirEq: Address of the device that the signal belongs to, within the Central Unit database.
• ISC: Signal Identifier.

Fort he H Control Function, said signals are:

Table A-16: H2 Control Function Digital Signal

Signal Description
1. 52L1 Closed
2. 52L12 Closed
3. 52L2 Closed
4. S_00 (Voltage absence on lines 1 and 2)
5. S_01 (Voltage absence on line 1 and presence on line 2)
6. S_10 (Voltage presence on line 1 and absence on line 2)
7. S_11 (Voltage presence on lines 1 and 2)
8. P_A (Preference 1)
9. P_B (Preference 2)
10. P_AB (Preference 1-2)
11. MAN (Manual)
12. MED_ACT (Medium voltage control function Actuated)
13. AUT_ACT (Action authorised)
14. 52TA Closed
15. 52TB Closed
16. 52B12 Closed
17. UA (Medium Voltage Control Function: Voltage 1 Presence / Absence)
18. UB (Medium Voltage Control Function: Voltage 2 Presence / Absence)
19. 86TA
20. 86TB
21. ULA (High Voltage Control Function: Voltage 1 Presence / Absence)
22. ULB (High Voltage Control Function: Voltage 2 Presence / Absence)
23. Definite Trip

M1CPTA2005I
A-69 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: # Relation of the Command Sequences first 23 ISCs (Dir,Isc)

10,71, // 52L1 Closed
12,71, // 52L1-2 Closed
11,71, // 52L2 Closed
260,2, // Voltage absence Lines L1 and L2
260,3, // Voltage absence L1 and Voltage presence L1
260,4, // Voltage presence L1 and Voltage absence L2
260,5, // Voltage presence lines L1 and L2
260,8, // Preference 1
260,9, // Preference 2
260,10, // Preference 1-2
260,7, // Manual
260,11, // Medium voltage control function Actuated
256,1, // Action authorised
260,24, // 52TA Closed
260,24, // 52TB Closed
260,24, // 52B12 Closed
260,12, //Auto.Medium: Voltage 1 Presence / Absence
260,13, //Auto.Medium: Voltage 2 Presence / Absence
2,0, //86TA
2,1, //86TB
260,0, //Auto.High: Voltage 1 Presence / Absence
260,1, //Auto.High: Voltage 2 Presence / Absence
260,24, //Definite Trip

• Configuration Data of Signal that Indicates whether the Substation is Set to

Local: [Line 87]

DirEq , ISC ,

• DirEq: Address of the device that the signal belongs to, within the Central Unit database.
• ISC: Digital signal Identifier.

Ex: # ISC of Local Substation

256,0,

• NEW Time Configuration Data incorporated in Version 2: [line 90]

TimeLineasAcopl , TimeEspReposBloq ,

• TimeLineasAcopl: Time of Coupled Lines (in msec.). The range is 100-30000, default value
5000 ms. step 100 ms.
• TimeEspReposBloq: Blocking Reset Time Delay (in msec.). The range is 100-5000, default
value 2000 ms. step 100 ms.

Ex: # New Times V2: TimeLineasAcopl, TimeEspReposBloq

5000,2000,

M1CPTA2005I
1CPT: Substation Central Unit A-70
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of the REST of Digital Signals (from Input 24 to 38) used
by the Control Function in the Signals of the Sequences: [line 92-106]

DirEq , ISC , (*)

(*) It is repeated for each digital signal used by the H Control Function. There will be 15
digital signals in addition to the first 23 signals. This is done for compatibility with the old
version.

• DirEq: Address of the equipment to which the signal belongs, within the Central Unit
database.
• ISC: Identifier of the signal.

In the case of H2 Control Function, these are the 15 remaining signals, which will be
configured with signals that do not belong to the automation.

Table A-17:
24. Bus Differential 1 Trip
25. Bus Differential 2 Trip
26. VT Trip Line 1
27. VT Trip Line 2
28. Disconnector Switches Closed
29. Goose Subscription Failure
30. 51 Trip Line 1
31. 51 Trip Line 2
32. 51 Trip Transformer 1
33. 51 Trip Transformer 2
34. 51 Trip Link
35. Key 69 Line 1
36. Key 69 Line 2
37. Key 69 Coupling
38. SF6 Trip

In the file it will be configured as follows:

# Descriptor on file DirEq ISC

24 Bus Differential 1 Trip * *
25 Bus Differential 2 Trip * *
26 VT Trip Line 1 * *
27 VT Trip Line 2 * *
28 Disconnector Switches Closed * *
29 Goose Subscription Failure * *
30 51 Trip Line 1 * *
31 51 Trip Line 2 * *
32 51 Trip Transformer 1 * *
33 51 Trip Transformer 2 * *
34 51 Trip Link * *
35 Key 69 Line 1 * *
36 Key 69 Line 2 * *
37 Key 69 Coupling * *
38 SF6 Trip * *

M1CPTA2005I
A-71 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # List of control functions that pick up

[2] 1, // PRESMULA
[3] 1, // PRESMULB
[4] 0, // PRESUA
[5] 0, // PRESUB
[6] 1, // ESTALTA
[7] 1, // MANALTA
[8] 0, // MANMEDIA
[9] 1, // CONDISP
[10] # H Control Function Settings
[11] 0,30.0,1,2000, //EnServicio,VnAlta,HabilEspera,TimeEspEntreMandos(ms)
[12] 7, // (ISC Number) MANUAL by default
[13] # PRESMULA settings
[14] 10,0, // Address and number (MEA)of measurement MULA
[15] 80.0,50.0, // AJ. PRES,AUSEN
[16] 1000,1000, // AJ, T. PRES,AUSEN
[17] # Ajustes del autómata PRESMULB
[18] 11,1, // Idem MULB
[19] 80.0,50.0, // AJ. PRES,AUSEN
[20] 1000,1000, // AJ. T.PRES,AUSEN
[21] # Ajustes del autómata PRESUA
[22] 10,1, // MEA (MuA04)
[23] 10,1, // MEA (MuA08)
[24] 10,1, // MEA (MuA48)
[25] 80.0,50.0, // AJ. PRES,AUS
[26] 1000,1000, // AJ. T.PRES, AUSEN
[27] # Ajustes del autómata PRESUB
[28] 11,2, // MEA (MuB04)
[29] 11,2, // MEA (MuB08)
[30] 11,2, // MEA (MuB48)
[31] 80.0,50.0, // AJ. PRES,AUS
[32] 1000,1000, // AJ. T.PRES, AUSEN
[33] # ESTALTA Control Function Settings
[34] 60000, // TI. ESTABLE
[35] 5000, // TI. CONMUTA
[36] 1000, // TI ESPERA IGUAL.
[37] # Ajustes del autómata MANMEDIA
[38] 0,13.0, // EN SERVICIO, Vn Media
[39] 5000, // TI. CONMUTA.
[40] # MANALTA Sequence table (8 inputs)
[41] # every input 0-7 has ONLY one command to be executed
[42] # and the specific command relation (DIR,ISE,DCO) of said command
[43] # SEQUENCE 0 (default)
[44] 1,
[45] 260,9,2,
[46] # SEQUENCE 1 (AbrirIntL1)
[47] 1,
[48] 10,6,2,
[49] # SEQUENCE 2 (CerrarIntL1)
[50] 1,
[51] 10,7,2,
[52] # SEQUENCE 3 (AbrirIntL2)
[53] 1,
[54] 11,6,2,
[55] # SEQUENCE 4 (CerrarIntL2)
[56] 1,
[57] 11,7,2,

M1CPTA2005I
1CPT: Substation Central Unit A-72
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

[58] # SEQUENCE 5 (AbrirInt1-2)

[59] 1,
[60] 12,6,2,
[61] # SEQUENCE 6 (CerrarInt1-2)
[62] 1,
[63] 12,7,2,
[64] # SEQUENCE 7 (switch to manual)
[65] 1,
[66] 260,13,2,
[67] # List of 28 first ISCs of AUTO H2
[68] 33, // ISCs Number
[69] 0,0,1,1,0,
[70] 1,0,1,1,0,
[71] …
[72] 32,0,1,1,0,
[73] # ISE Relation (commands) of AUTO H
[74] 14, // ISEs Number
[75] # ISE,ISCexe(dir,isc),Tiempo,neg,ISCOK(dir,isc),ISCfail(dir,isc),doble,
[76] # nº blqs,.....
[77] 0,260,8,1,0,260,-1,260,-1,0,0,0, // PREF 1 FROM PANEL
[78] 1,260,9,1,0,260,-1,260,-1,0,0,0, // PREF 2 FROM PANEL
[79] …
[80] 13,260,7,1,0,260,-1,260,-1,0,1,256,24,0,0, // MAN FROM CONTROL
FUNCTION
[81] # RelatioN ISCs (Dir,Isc) of the sequences
[82] 1,46, // 52L1 Closed
[83] 1,246, // 52L1-2 Closed (Not used)
[84] …
[85] 20,2, // DISP DEFIN
[86] # Substation ISC in Local
[87] 256,0,
[88] # Added by V2 from Iberdrola
[89] # New Settings: TimeLineasAcopl, TimeEspReposBloq
[90] 5000,2000,
[91] # New Input Signals
[92] 2,2 // Trip.Diff B1
[93] 2,3, // Trip.Diff B2
[94] 10,4, // Trip.VT L1
[95] 11,4, // Trip.VT L2
[96] 256,3, // Disconnector Switches Closed
[97] 256,0, // Goose Subscription Failure
[98] 256,0, // Trip.51L1
[99] 256,0, // Trip.51L2
[100] 2,4, // Trip.51T1
[101] 2,5, // Trip.51T2
[102] 256,0,// Trip.51Link
[103] 10,5, // Key 69 L1
[104] 11,5, // Key 69 L2
[105] 12,5, // Key 69 Coupl
[106] 256,4,// Trip.SF6

M1CPTA2005I
A-73 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.13.3 Resistive Ground Control Function Files: TIERR_i.CFG

These files save data related to the Resistive Ground control function (virtual devices the
PROCOME addresses of which are 259, 262, 263, …), as well as its settings.

The purpose of this control function is to detect, upon activation of the resistive ground alarm,
the medium voltage line that caused the problem. To this end, a sequence of openings is
initiated according to a programmed priority. It will be stopped when detecting alarm
deactivation after an open command, keeping the breaker open and blocking the close
operation.

The name of these files is “tierr_i.cfg”, with i equal to 1, 2, 3, … and will be associated to the
virtual devices with PROCOME address 259, 262, 263, … respectively.

File format is as follows:

• Data on General Settings of the Ground Detection Control Function: [Lines 2-
6]

Servicio ,
TimeArranque ,
TimeComprobación ,
NumPosiciones ,

• Servicio: This setting indicates whether the control function is in service (1) or not (0).
• TimeArranque: Control function pickup time, after alarm detection (in sec.). The range of
possible values is 0-600, the default value being 60 seconds. Step is 1 second.
• TimeComprobación: Open line check time (in sec.). The range of possible values is 0-10,
the default value being de 5 seconds. Step is 1 second.
• NumPosiciones: Number of bays controlled by the control function.

Ex: 1,
20,
5,
2,

• Configuration Data of Digital Signals (ISC) of Control Function

They are configured as per section A.1: [lines 8-13]

Note: the Resistive Ground control function has 8 fixed and consecutive digital signals, with ISC indexes going
from ISC_0 to ISC_7. The following table shows the 8 digital signals and associated function:

Table A-18: Digital Signals (ISC) of Control Function

Label ISC number Description
ISC_R_SERV1 0 Module 1 control function in service
ISC_ACT1 1 Module 1 control function active
ISC_ARR1 2 Module 1 control function pickup
ISC_BLQ1 3 Control function stopped without detection/ Blocked
ISC_FIN_CICLO 4 Cycle completed without detection of fault source
ISC_RESERVA_5 5 Reserve
ISC_RESERVA_6 6 Reserve
ISC_ERR_AJSDEF 7 Module 1 control function setting errors

M1CPTA2005I
1CPT: Substation Central Unit A-74
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: 13,// Num. Signals

0,0,0,0,0,
1,0,0,0,0,
…
12,0,0,0,0,

• Configuration Data of Control Function Commands

They are configured as per section A.1. COMMANDS DO NOT EXIST for the Ground control
function: [line 15]

Ex: 0,//Num. Commands

• Configuration Data of Bay Commands

For each bay p controlled by the control function, data on open and close commands of the
breaker associated to said bay will be given: [lines 20-21]

DirEq_A , ISE_A , DCO_A , DirEq_C , ISE_C , DCO_C , (*)

(*) It repeats for each bay. There will be as many as shown in NumBays.

• DirEq_A: Address of the device that the open command corresponding to the bay p
breaker belongs to.
• ISE_A: PROCOME label of open command.
• DCO_A: DCO of open command.
• DirEq_C: Address of the device that the close command corresponding to the bay p
breaker belongs to.
• ISE_C: PROCOME label of close command.
• DCO_C: DCO of close command.

Ex: 9,13,2,9,10,2,// Bay1

11,13,2,11,10,2,// Bay2

• Configuration Data of Ground Detection Signals: [Lines 23-24]

ISC , (*)

(*) It repeats for each bay. There will be as many as shown in NumBays.

• ISC: PROCOME label (of logic ground control function) of bay p ground detection signal.

Ex: 8,// Bay1

9,// Bay2

• Configuration Data of 64 Deactivate Command: [Line 27]

DirEq , ISE , DCO ,

• DirEq: Address of the device that the command belongs to.

• ISE: PROCOME label of the command.
• DCO: DCO of the command.

Ex: 13,22,2,

M1CPTA2005I
A-75 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data on Bay Breaker Status: [Line 29]

InterruptServ , InterruptServ , … InterruptServ ,

• InterruptServ: This bit indicates whether a bay breaker is in service (1) or out of service
(0). There will be as many as shown in NumPosiciones.

Ex: 1,1, //2 Bays

• Configuration Data of Control Function Signals

There are two: Trip Relay 64 Módulo 1 Disconnected and Alarma Tierra Resistente Barras
Módulo 1: [lines 31-32]

DirEqDisp64 , ISCDisp64 ,
DirEqAlrTR , ISCAlrTR ,

• DirEqDisp64: Address of the device that the Trip Relay 64 Módulo 1 Disconnected signal
belongs to.
• ISCDisp64: PROCOME label of said signal.
• DirEqAlrTR: Address of the device that Alarma Tierra Resistente Barras Módulo 1 signal
belongs to.
• ISCAlrTR: PROCOME label of said signal.

Ex: 13,134,// Relay 64 Trip

13,118,// Resistive Ground alarm

• Data on Bay Priorities: [Lines 34-35]

Prioridad , (*)

(*) It repeats for each bay. There will be as many as shown in NumPosiciones.

• Prioridad: Bay priority. The range of possible values is 1-50. Step is 1.

Ex: 1, //Bay1
2, //Bay2

• Data on Bay Identification: [Lines 37-38]

Identificación , (*)

(*) It repeats for each bay. There will be as many as shown in NumPosiciones.

• Identificación: Bay name (maximum number of characters: 80).

Ex: 13kV 52-1 L-1,//Bay1

13kV 52-3 L-3,//Bay2

M1CPTA2005I
1CPT: Substation Central Unit A-76
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data on Module Priorities

This setting is used to coordinate two control functions when the busbars they refer to are
connected because the tie breaker is closed: [lines 34-35].

PrioMódulo ,

• PrioMódulo: Module priority. The range of possible values is 0,1,2. If the setting is 0,
there is no coordination. If it is set to 1, this control function is the first to start detecting
the source of the fault. If it is set to 2, it waits for the other to finalise before starting. For
these operations to be carried out an external logic is needed to define every situation of
the control functions.

Ex: 1,// Line priority

• Data on Tie Breaker Closed Signal: [Lines 20-21]

DirEqAcopl , ISC_Acopl ,

• DirEqAcopl: Address of the device that the tie breaker signal belongs to.
• ISC_Acopl: PROCOME label of the tie breaker closed signal.

Ex: 13,56,// 52 Coupling Closed

• Number of Additional Bays

When two modules are coupled, breaker signals of the other module must be configured in
each of the control functions in order to detect possible untimely operations of the same and
switch the control function to blocked: [lines 34-35]

NumPosAdic ,
DirEq_A , ISC_Abierto , DirEq_C , ISC_Cerrado , (*)

(*) It repeats for each additional bay. There will be as many as shown in NumPosAdic.

• NumPosAdic: Number of additional bays to check untimely operations.

• DirEq_A: Address of the device that the breaker opened signal belongs to.
• ISC_Abierto: PROCOME label of the breaker opened signal.
• DirEq_C: Address of the device that the breaker closed signal belongs to.
• ISC_Closed: PROCOME label of the breaker closed signal.

Ex: 3,
12, 45, 12, 46,
14, 45, 14, 46,
15, 37, 15, 38,

M1CPTA2005I
A-77 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # In service / Out of service

[2] 1,
[3] # Settings of the GROUND Control Function
[4] 20, // Pickup Time
[5] 5, // Check Time
[6] 2, // Number of bays
[7] # Control function ISC
[8] 13, // Number of ISCs
[9] 0,0,0,0,0, // R_SERV1
[10] 1,0,0,0,0, // ACT1
[11] 2,0,0,0,0, // ARR1
[12] …
[13] 12,0,0,0,0, // Settings error
[14] # Control function Commands
[15] 0, //Number of ISEs
[16] # ISE,ISC ... etc.
[17] # Bay commands
[18] # [ISE Open],[ISE Close]
[19] # dirA,iseA,dcoA,dirC,iseC,dcoC
[20] 9,13,2,9,10,2,
[21] 11,13,2,11,10,2,
[22] # Detected Ground ISC
[23] 8, // GROUND L-1 13kV
[24] 9, // GROUND L-3 13kV
[25] # 64 Deactivate Command
[26] # dir,ise,dco
[27] 13,22,2, // OBSOLETE
[28] # Breakers in service/out of service
[29] 1,1,
[30] # List of external ISC used
[31] 13,134, // From UCP TRIP RELE 64
[32] 13,118, // Resistive Ground alarm
[33] # Bay priorities
[34] 1,
[35] 2,
[36] # Bay identification
[37] 13kV 52-1 L-1,
[38] 13kV 52-3 L-3,
[39] # Module priority
[40] 1,
[41] # Tie breaker closed signal.
[42] 13, 56,
[43] # Additional bays
[44] 3,
[45] 12, 45, 12, 46,
[46] 14, 45, 14, 46,
[47] 15, 37, 15, 38,

M1CPTA2005I
1CPT: Substation Central Unit A-78
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.13.4 Eras Control Function File: ERAS.CFG

This file “eras.cfg” contains the data required to configure the Eras control function.

File format is as follows:

• Configuration Data of Eras Control Function Settings: [Lines 2-5]

Servicio ,
TimeDesconex ,
BloqAutomático ,
NumTerminales ,

• Servicio: This bit indicates whether the Eras control function is in service (1) or not (0).
• TimeDesconex: Disconnection timeout (in sec.). The range of valid values is 0-10. Step is
1 second.
• BloqAutomático: This bit indicates whether the automatic blocking option after
disconnection is activated (1) or not (0).
• NumTerminals: Number of Eras control function terminals.

Ex: 1,
5,
0,
3,

• Data on Terminal Priority: [Line 7]

Prioridad , Prioridad , … Prioridad ,

• Prioridad: Terminal priority. The range of valid values is 1-20. Step is 1. There will be as
many as shown in NumTerminals.

Ex: 0,1,2,// 3 terminals

• Configuration Data of Eras Control Function Digital Signals

They are configured as explained in section A.1: [lines 9-14]

Ex: 150,//Num. signals

0,0,0,0,0,
1,0,1,1,0,
2,0,1,1,0,
…
149,0,0,0,0,

M1CPTA2005I
A-79 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Eras Control Function Commands

They are configured as explained in section A.1: [lines 16-22]

Ex: 4,// Num. Commands

0,261,3,1,0,261,-1,261,-1,0,0,0,
1,261,4,1,0,261,-1,261,-1,0,0,0,
2,261,-1,1,0,261,-1,261,-1,0,0,0,
3,261,-1,1,0,261,-1,261,-1,0,0,0,

• Configuration Data of Eras Control Function External ISCs: [Lines 24-28]

DirEq_98TtBA , ISC_98TtBA ,
DirEq_98TtBB , ISC_98TtBB ,
DirEq_VBA , ISC_VBA ,
DirEq_VBB , ISC_VBB ,
DirEq_BLQ , ISC_BLQ ,

• DirEq_98TtBA: Address of the device that signal Trip del automático de Tensión de
Barras A belongs to.
• ISC_98TtBA: PROCOME label of said signal.
• DirEq_98TtBB: Address of the device that signal Trip del automático de Tensión de
Barras B belongs to.
• ISC_98TtBB: PROCOME label of said signal.
• DirEq_VBA: Address of the device that signal Tensión en Barra A belongs to.
• ISC_VBA: PROCOME label of said signal.
• DirEq_VBB: Address of the device that signal Tensión en Barra B belongs to.
• ISC_VBB: PROCOME label of said signal.
• DirEq_BLQ: Address of the device that signal Entrada de Bloqueo belongs to.
• ISC_BLQ: PROCOME label of said signal.

These fixed signals are listed below, in sequential order:

Table A-19: Table A-16:Eras Control Function External ISCs

Signal Description
1. 98TtBA Trip of Busbar A Voltage breaker
2. 98TtBB Trip of Busbar B Voltage breaker
3. VBA Voltage in Busbar A
4. VBB Voltage in Busbar B
5. S_BLQ Blocking input

Ex: 12,176,// 98TtBA

12,177,// 98TtBB
12,0,// VBA
12,1,// VBB
256,32,// S_BLQ

M1CPTA2005I
1CPT: Substation Central Unit A-80
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # ERAS settings

[2] 1,// In service
[3] 5,// Disconnection timeout
[4] 0,// Automatic blocking after disconnection
[5] 3,// Number of terminals
[6] # List of terminals by priority
[7] 0,1,2,
[8] # ERAS ISCs
[9] 150, // Number of ISCs
[10] 0,0,0,0,0, // ERAS_SERVICE
[11] 1,0,1,1,0, // ERAS_S_BLQ
[12] 2,0,1,1,0, // ERAS_S_CX
[13] …
[14] 149,0,0,0,0,
[15] # List of H Control ISEs (commands)
[16] 4, // Number of ISEs
[17] # ISE,ISC exe(dir,isc),Tiempo,neg,ISC OK(dir,isc), ISC
fail(dir,isc),doble,
[18] # nº blqs,.....
[19] 0,261,3,1,0,261,-1,261,-1,0,0,0, // Blocking of ERAS
[20] 1,261,4,1,0,261,-1,261,-1,0,0,0, // Unblocking
[21] 2,261,-1,1,0,261,-1,261,-1,0,0,0, // Set to Auto
[22] 3,261,-1,1,0,261,-1,261,-1,0,0,0, // Set to Manual
[23] # These signals are COUPLING 45K and are common
[24] 12,176, // ISC_98Tt_BA
[25] 12,177, // ISC_98Tt_BB
[26] 12,0, // ISC_VBA
[27] 12,1, // ISC_VBB
[28] 256,32, // ISC_S_BLOQUEO (fixed to 0) External blocking signal

A.13.4.a Eras Control Function Virtual Terminal File: TVIRTUAL.CFG

This file “tvirtual.cfg” contains necessary data to configure Eras control function virtual
terminals.

File format is as follows:

• Data on the Number of Eras Control Function Virtual Terminals: [Line 2]

NumTerminales ,

• NumTerminals: Number of virtual terminals of the Eras control function.

Ex: 3,

Now, configuration data of all virtual terminals (one after the other) are included. The
information below will be given for each virtual terminal:

M1CPTA2005I
A-81 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Physical Device Connections: [Lines 4-18]

DirEq , ISC , (*)

(*) It repeats as many times as there are connections of bay devices with ISCs (15 times).

• DirEq: Address of the bay device that the ISC signal in question belongs to.
• ISC: PROCOME label of said signal ISC

The different signals are in sequential order:

Table A-20: Configuration Data of Physical Device Connections

Nº Signals Description
0. ISC_98Tt_L
1. ISC_89LA
2. ISC_89LB
3. ISC_VL
4. ISC_IA
5. ISC_IC
6. ISC_IDES
7. ISC_FOA
8. ISC_FOC
9. ISC_S_ETBLQ (External blocking signal)
10. ISC_ERAS_BLQ (Blocked ERAS generated by UCERAS 1)
11. ISC_ERAS_TX (Excessive reset time generated by UCERAS 3)
12. ISC_S_FSINC (Lack of synchronism)
13. ISC_S_AUTO (ERAS to automatic)
14. ISC_S_S_MANUAL (ERAS to manual)

Ex: 10,155, // ISC_98Tt_L

10,33, // ISC_89LA
10,39, // ISC_89LB
10,161, // ISC_VL
10,45, // ISC_IA
10,46, // ISC_IC
10,47, // ISC_IDES
10,136, // ISC_FOA
10,135, // ISC_FOC
256,32, // ISC_S_ETBLQ
261,1, // SC_ERAS_BLQ
261,6, // ISC_ERAS_TX
256,32, // ISC_S_FSINC
261,7, // ISC_S_AUTO
261,8, //ISC_S_S_MANUAL

M1CPTA2005I
1CPT: Substation Central Unit A-82
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Configuration Data of Open and Close Commands of Physical Terminal:

[Lines 20-21]

DirEqAp , ISEAp , DCOAp ,

DirEqCi , ISECi , DCOCi ,

• DirEqAp: Address of the device that the open command of the physical terminal belongs
to.
• ISEAp: PROCOME label of said open command.
• DCOAp: DCO of said open command.
• DirEqCi: Address of the device that the close command of the physical terminal belongs
to.
• ISECi: PROCOME label of said close command.
• DCOCi: DCO of said close command.

Ex: 10,33,2,// Open command

10,30,2,// Close command

• Configuration Data of Virtual Terminal Settings: [Lines 23-35]

EnServicio ,
Prioridad ,
NivelTension1 ,
DosBarras ,
EnergBarras ,
EnergLinea ,
AcoplamTens ,
ReserLinea ,
ReserBarra ,
TimeReposTerm ,
TimeReposLRL ,
TimeSubtensLR ,
NombTerminal ,

• EnServicio: Indicates whether the terminal is in service (1) or out of service (0).
• Prioridad: Terminal priority. Possible values are 1-20.
• NivelTension1: Voltage level: 1 = YES, 0 = NO.
• EnergBarras: Busbar energizing: 1 = YES, 0 = NO.
• EnergLinea: Line energizing: 1 = YES, 0 = NO.
• AcoplamTens: Voltage coupling: 1 = YES, 0 = NO.
• ReserLinea: Reserve to line: 1 = YES, 0 = NO.
• ReserBarra: Reserve to busbar: 1 = YES, 0 = NO.
• TimeReposTerm: Terminal reset time (in sec.). The range of valid values is 3-30. Step is
1 second.
• TimeReposLRL: Reset time due to (in sec.). The range of valid values is 3-60. Step is 1
second.
• TimeSubtensLR: Undervoltage time LR (in sec.). The range of valid values is 0-10. Step
is 1 second.
• NombTerminal: Terminal description (maximum number of characters: 15).

M1CPTA2005I
A-83 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

Ex: 1,// In service

1,// Priority
0,// Voltage level
1,// Two busbars
1,// Busbar energizing
0,// Line energizing
0,// Voltage coupling
0,// Reserve to line
1,// Reserve to busbars
3,// Terminal reset time
10,// Reset time due to LRL
10,// Undervoltage time LR
TERMINAL 1,// Description

The file becomes:

[1] # Number of Terminals

[2] 3,
[3] # Terminal 1
[4] 10,155, # ISC_98Tt_L
[5] 10,33, # ISC_89LA
[6] 10,39, # ISC_89LB
[7] 10,161, # ISC_VL
[8] 10,45, # ISC_IA
[9] 10,46, # ISC_IC
[10] 10,47, # ISC_IDES
[11] 10,136, # ISC_FOA
[12] 10,135, # ISC_FOC
[13] 256,32, # ISC_S_ETBLQ External blocking signal (fixed to 0)
[14] 261,1, # ISC_ERAS_BLQ Signal generated by (UCERAS1)
[15] 261,6, # ISC_ERAS_TX Signal generated by (UCERAS3)
[16] 256,32, # ISC_S_FSINC Lack of synchronism (fixed to 0)
[17] 261,7, # ISC_S_AUTO
[18] 261,8, # ISC_S_S_MANUAL
[19] # Open and close commands of the physical terminal
[20] 10,33,2, # Open
[21] 10,30,2, # Close
[22] # Settings of terminal 1
[23] 1, # In service
[24] 1, # Priority
[25] 0, # Voltage level 1
[26] 1, # Two busbars
[27] 1, # Busbar energ. (EB)
[28] 0, # Line energ. (EL)
[29] 0, # Voltage coupling (AT)
[30] 0, # Reserve to line (LRL)
[31] 1, # Reserve to busbar (LRB)
[32] 3, # Terminal reset time
[33] 10, # Reset time due to
[34] 10, # Undervoltage time LR (TSUB)
[35] TERMINAL 1, # Terminal description
[36] # Terminal 2
[37] …
[38] # Terminal 3
[39] …

M1CPTA2005I
1CPT: Substation Central Unit A-84
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.14 Summer / Winter Time Configuration File:

HORARIO.CFG.
This file contains a number of data on Central Unit management of summer / winter time. This
file is “horario.cfg”. File format is as follows:
• Data Stating whether the Central Unit Handles Summer / Winter Time or not:
[Line 2]

ExisteHorarioST , LocalTimeOffset , UCSUsaHoraUTC ,

• ExisteHorarioST: Indicates whether the Central Unit handles summer / winter time (1) or
not (0).
• LocalTimeOffset: Local time offset with respect UTC time, expressed in hours, (Madrid is
in the UTC+1 time zone, therefore, LocalTimeOffset will be 1). For noninteger offsets, the
values will be floating point numbers, namely, if the time zone is UTC+3:30, the value will
be 3.50. The range of this setting is -12.00 to +13.00. Only available in CPT relays.
• UCSUsaHoraUTC: Indicates whether the Central Unit operates with UTC time (1) or local
time (0). If this parameter is not configured, it takes the value of 0 by default. Only
available in CPT models.

IMPORTANT: IEC 61850 operates with time tags in UTC 10 format and also puts forward
the standard SNTP 11 to carry out device time synchronisation, that also uses UTC time
and date. In this case, LocalTimeOffset and UCSUsaHoraUTC must be configured for the
Central Unit to convert UTC time tags transmitted by IEC 61850 relays into time tags in
accordance with the local time of the country where the Central Unit is installed, that will
be set via LocalTimeOffset. This conversion from UTC time into local time will only be
carried out when UCSUsaHoraUTC is set to 1.

Ex: 1,0,0,

• Data on the Date and Time in which the Change to Summer or Winter Time will
be Produced: [Line 4]

IdDiaVer , DiaSemanaVer , MesVer , HoraVer , ..

.. IdDiaInv , DiaSemanaInv , MesInv , HoraVer , NumHoras ,

• IdDiaVer: This parameter indicates whether the change to summer time is carried out the
first (1), second (2), third (3), fourth (4) or last (0) day “DiaSemanaVer” of the month (see
Example in next page).
• DiaSemanaVer: Day of the week in which the change to summer time is carried out:
(1=SUNDAY, 2=MONDAY, 3=TUESDAY, 4=WEDNESDAY, 5=THURSDAY, 6=FRIDAY,
7=SATURDAY).

10
UTC: Universal Time Coordinated
11
SNTP: Simple Network Time Protocol (RFC 2030)

M1CPTA2005I
A-85 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• MesVer: Month in which the change to summer time is carried out (1-12).
• HoraVer: Time at which the change to summer time is carried out (0-23).
• IdDiaInv: This parameter indicates whether the change to winter time is carried out the
first (1), second (2), third (3), fourth (4) or last (0) day “DiaSemanaInv” of the month.
• DiaSemanaInv: Day of the week in which the change to winter time is carried out:
(1=SUNDAY, 2=MONDAY, 3=TUESDAY, 4=WEDNESDAY, 5=THURSDAY, 6=FRIDAY,
7=SATURDAY).
• MesInv: Month in which the change to winter time is carried out (1-12).
• HoraInv: Time at which the change to winter time is carried out (0-23).
• NumHoras: Amount of hours the clock is put forward or backward in summer or winter
respectively.

Ex: 0,1,3,2,0,1,10,3,1,

Example: with these data, considering the current year is 2002, the dates of change to summer
and winter times will be:

Summer: last (0) sunday (1) of March (3) at 2.00h (2)  Day:31/03/2002 At 02:00h
becomes 03:00h.
Winter: last (0) sunday (1) of October (3) at 3.00h (3)  Day:27/10/2002 At 03:00h
becomes 02:00h.

The file becomes:

[1] # The Central Unit handles summer / winter time (0) or not.
[2] 1,0,0,
[3] #IdDiaVer,DiaSemVer,MesVer,HoraVer,IdDiaInv,DiaSemInv,MesInv,HoraInv,Num
Horas,
[4] 0,1,3,2,0,1,10,3,1,

M1CPTA2005I
1CPT: Substation Central Unit A-86
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.15 Remote Access Server (RAS) Configuration File:

RMONITOR.CFG (Only CPX/CPP-B/CPT)
This file contains data to configure el Remote Access Server (RAS), to gain access via modem
to the CPX/CPP/CPT, for example to connect to a remote HMI (to CPX and CPP but not the
CPT), TELNET, FTP, etc., or gain access via a serial cable, for example to connect to other
CPX/CPP/CPT in case of Central Unit redundancy. The file is “rmonitor.cfg”. File format is as
follows:
• Data on the Serial Port the Modem is Connected to: [Line 2]

PuertoCOM , Velocidad ,

• PuertoCOM: CPX/CPP/CPT serial port the modem is connected to for remote access.
Port data are fixed: 9600 baud, no parity, 8 data bits and 1 stop bit.
• Velocidad: Baud rate (in bps) associated to the remote access port. If it is not configured,
the default value is 9600.

Ex: COM2,115200,

• Server RAS and Modem Command Configuration Data: [Lines 3-7]

TipoServicio , NumLineasComandosModem ,
Comando , (*)

(*) It repeats as many times as commands are necessary to initialise the modem
(NumLineasComandosModem times).

• TipoServicio: States the type of remote service to be configured: 0: Not enabled; 1:

Remote HMI by modem; 2: Redundant CPX connection by direct serial port.
• NumLineasComandosModem: Number of lines of AT commands sent automatically to
initialise the modem. A maximum of 5 commands can be configured. When TipoServicio
= 2 is configured, these commands are not used, so 0 (zero) will be configured in this
field.
• Comando: AT commands sent to initialise the modem. End the chain of the command
text with “<cr>” to symbolise a carriage return.

Ex: 1,4,
at+cicb=0<cr>,
at+cbst=0,0,1<cr>,
at+ifc=2,2<cr>,
at&D1<cr>,

The file becomes:

[1] # Remote Access Server (RAS) configuration

[2] COM2,115200,// Port the modem is connected to, Baud rate,
[3] 1,4,// Enable RAS, Nº lines AT commands
[4] at+cicb=0<cr>, // Next call for data
[5] at+cbst=0,0,1<cr>, // Automatic modulation transactions
[6] at+ifc=2,2<cr>, // Stream control hardware
[7] at&D1<cr>,// Switch to command mode when DTR switches to inactive state

M1CPTA2005I
A-87 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.16 Routing Table Configuration File: ROUTE.CFG (only

CPX-B / CPT)
In CPX-B and CPT models the routing table may be modified by adding more entries defining
them in this file: ROUTE.CFG. With this file a Gateway can be added to CPX/CPT. To do this,
just configure one entry in which both the destination and mask address is 0.0.0.0.

Up to 32 entries can be added to this file.

File format is as follows:

NumEntradas ,

DirIPDest ,
MaskDest ,
DirIPGateway , (*)
IFNet ,

(*) It repeats as many times as shown in NumEntradas.

• NumEntradas: Number of entries to be added to the CPX/CPT routing table. Maximum

32.
• DirIPDest: Destination IP address. It is an IP address used to determine whether a device
can be connected to the CPX/CPT. Enter 0.0.0.0 in this field to add a generic Gateway.
• MaskDest: Destination mask. In conjunction with the field DirIPDest it will determine a
range of IP addresses that can be connected to the CPX/CPT. Enter 0.0.0.0 in this field
to add a generic Gateway.
• DirIPGateway: IP address of the Gateway device that routes the messages directed to
devices having IP addresses within the subnet determined by DirIPDest and MaskDest
fields. Configure the corresponding IP address here to add a generic Gateway.
• IFNet: This parameter is not used in CPX relays. In CPT relays, the network interface that
the entry in the routing table is assigned to shall be entered; it can be 1 or 2.

Ex: 2,// Number of entries

112.11.0.0,// Subnet 112.11.xxx.yyy
255.255.0.0,
128.127.70.1,
0,//
0.0.0.0,// Generic Gateway
0.0.0.0,
180.112.12.4,
2, //

M1CPTA2005I
1CPT: Substation Central Unit A-88
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

The file becomes:

[1] # Routing table configuration

[2] 2,// 2 entries in table
[3] 112.11.0.0,// Subnet 112.11.xxx.yyy
[4] 255.255.0.0,
[5] 128.127.70.1,
[6] 0,// Reserve
[7] 0.0.0.0,// Generic Gateway
[8] 0.0.0.0,
[9] 180.112.12.4,
[10] 0,// Spare

M1CPTA2005I
A-89 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.17 Configuration File of Client/Server Synchronisation

Module SNTP: SNTP.CFG (only 1CPT)
The configuration parameters of the Central Unit synchronisation module SNTP reside in file
“SNTP.CFG”.

The file is segregated into four parts: Configuration of the Central Unit as SNTP server,
configuration of the Central Unit as Broadcast SNTP client, configuration of the Central Unit as
Unicast SNTP client and configuration of SNTP general parameters.

File format is as follows:

• Data to Configure the Central Unit as SNTP Server: [See Example, Lines 3-7]

ServerRole , ServerStartAtBegin ,
IsServerMcast , McastAddress , McastPeriod , McastIgnoreTLC ,

• ServerRole: Indicates whether the Central Unit operates as SNTP server (1) or not (0).
• ServerStartAtBegin: Indicates whether the Central Unit is to operate as SNTP server from
the start (1) or not (0). The option to configure by default will be that the Central Unit be a
server from the start (1). The option of not being a server from the start (0) is reserved for
the cases in which the Central Unit must only be SNTP server under certain conditions to
be checked in operation (not implemented).
• IsServerMcast: Indicates whether the multicast/broadcast SNTP server for the periodic
transmission of synchronisation messages is activated (1) or not (0). Even if this setting is
not active, when the CPT switches from not synchronised to synchronised, and vice
versa, a spontaneous multicast/broadcast synchronisation message will be sent to its
clients to reflect the new situation.
• McastAddress: IP address of the multicast/broadcast SNTP server used both for periodic
synchronisation transmissions and spontaneous transmissions.
• McastPeriod: States how often (in msec) the multicast/broadcast server will send a SNTP
synchronisation.
• McastIgnoreTLC: Indicates whether the multicast/broadcast SNTP server sends
synchronisations (1) or not (0) when the time is not reliable.

Ex: 1,1,
0,255.255.255.255,10000,1,

M1CPTA2005I
1CPT: Substation Central Unit A-90
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data to Configure the Central Unit as Broadcast SNTP Client: [See Example,
Line 12]

IsClientBcast , BcastT2off , BcastT2on ,

• IsClientBcast: Indicates whether the Central Unit operates as Broadcast SNTP client (1)
or not (0). The Central Unit will only admit broadcast synchronisers from server
configured in the list of Unicast servers (see next configuration lines).
• BcastT2off: Time (in msec.) without receiving a correct broadcast synchronisation to
consider the Broadcast client not reliable (offline). Configure 0 to state that this
parameter will not be used, namely, that once the Central Unit considers this parameter
reliable (online), it will never switch to non reliable. Maximum setting is 1000 (excluding
said 0).
• BcastT2on: Time (in msec.) receiving correct broadcast synchronisations to consider the
Broadcast client reliable (online). Configure 0 to state that this parameter will not be used
and the Central Unit will switch to consider the Broadcast client reliable immediately after
the first synchronisation received. Minimum setting is 1000 (excluding said 0).

Ex: 0,0,0,

• Data to Configure the Central Unit as Unicast SNTP Client: [See Example,
Line 17-21]

IsClientUcas , Refresh , ConRetries , RecRefres , Thresho , …

t h ld

… UcastT2on , UcastT2off , SegWait ,

AnswerSrv

NumServers ,
IPServer , (*)

(*) It repeats for each SNTP server the Central Unit is connected to as Unicast client. There
will be as many as shown in NumServers.

• IsClientUcast: Indicates whether the Central Unit operates as Unicast SNTP client (1) or
not (0).
• Refresh: Time (in msec.) between synchronisations with SNTP servers. Minimum setting
is 10000.
• ConRetries: Number of connection attempts with each SNTP server. Maximum setting is
10.
• RecRefresh: Time (in msec.) between synchronisations with SNTP servers after a failed
synchronisation. It is applicable when the connection with ALL servers has failed. This
parameter must be less or equal than “Refresh”.
• Threshold: Time difference (in msec.) between the time received from the server and the
internal time of the Central Unit above which the Central Unit does not synchronise its
internal time with the time received from the server. Default value is 0. Minimum setting is
1000 (excluding said 0).

M1CPTA2005I
A-91 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex A. Configuration Files for CPX / CPP / CPT

• UcastT2on: After a SNTP server has dropped, if recovery is detected (response with
reliable time), a number of correct Unicast synchronizing attempts must take place
(response with reliable time) before considering said server reliable (online) and therefore
synchronising the Central Unit with its time. Said number of Unicast attempts is figured
out by dividing "UcastT2on" by "Refresh". If the result is not an integer, it is rounded to
the next higher integer.
Ex1: UcastT2on = 10000; Refresh = 10000 => NumIntentos = 10000 / 10000 = 1.
Ex2: UcastT2on = 12000; Refresh = 10000 => NumIntentos = 12000 / 10000 = 1.2 = 2.
In this way, if upon receiving a reliable time from a SNTP server, said server is to be
considered reliable (online) immediately, "UcastT2on" = "Refresh" must be configured.
Minimum setting is 10000 and this must be greater or equal than “Refresh”.
• UcastT2off: If the Central Unit is being configured by a SNTP server and the server has
dropped or is sending not reliable time, a number of Unicast synchronisation attempts
must take place while the server is dropped or sending not reliable time before
considering the server not reliable (offline). Said number of Unicast attempts is figured
out by dividing "UcastT2off" by "Refresh". If the result is not an integer, it is rounded to
the next higher integer.
Ex1: UcastT2off = 10000; Refresh = 10000 => NumIntentos = 10000 / 10000 = 1.
Ex2: UcastT2off = 12000; Refresh = 10000 => NumIntentos = 12000 / 10000 = 1.2 = 2.
In this way, if upon the drop of a SNTP server or receiving not reliable time, said server is
to be considered not reliable (offline) immediately, "UcastT2off" = "Refresh" must be
configured. Minimum setting is 10000 and this must be greater or equal than “Refresh”.
• SegWaitAnswerSrv: SegWaitAnswerSrv Number of timeout seconds for SNTP server
response. Default value is 1 second. Maximum allowable value depends on other values
previously configured.
[if (ConRetries > 0) then MaxSegWaitAnswerSrv= RecRefresh / ConRetries]
• NumServers: Number of SNTP servers the Central Unit can connect to in Unicast client
mode. Maximum number of servers is 10 (primary SNTP server and secondary SNTP
servers).
• IPServer: IP address of the server the Central Unit is to be connected to in Unicast client
mode.

Ex:

1,10000,3,10000,0,20000,30000,
1,
2,
128.127.160.159,
128.127.160.160,

M1CPTA2005I
1CPT: Substation Central Unit A-92
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

• Data to Configure General Parameters: [See Example, Line 25-27]

IgnoreLI2Sync , FollowLI ,
TrazasSNTP ,

• IgnoreLI2Sync: Indicates whether the SNTP client (Unicast / Broadcast) will synchronise
(1) or not (0) with the time received from the SNTP server when the latter is tagged as not
reliable time (“Leap Indicator” equals 3).
• FollowLI: Indicates whether the SNTP client (Unicast / Broadcast) is considered
synchronised (online) or not synchronised (offline) following exactly the “Leap Indicator”
(LI) of the time received from the SNTP server (1) or using the configured online and
offline times (“BcastT2on”, “BcastT2off”, “UcastT2on” and “UcastT2off”).
• TrazasSNTP: Indicates whether traces of SNTP module to file activate (1) or deactivate
(0). The trace file is saved in the memory (\\temp\sntp.log).

Ex: 0,0,
0,

The file becomes:

[1]# FILE SNTP.CFG, THAT CONFIGURES SNTP PARAMETERS.

[1] ########################## Server ##################################
[2] # Activates the SNTP server, It activates at the start of the UCS,
[3] 1,1,
[4] # Multicast Server (1=Yes;0=No), multicast address
[5] # 255.255.255.255=Broadcast), Multicast period(msec),
[6] # IgnorarTrustLocalClockParaEnviarMulticast,
[7] 0,255.255.255.255,10000,1,
[8] ########################## Client ###################################
[9] # ******************** Broadcast client *****************************
[10] # Broadcast client(1=Si;0=No),TimeToOffline(mseg;0=No se
[11] # usa),TimeToOnline(mseg;0=No se usa),
[12] 0,0,0,
[13] # ******************** Unicast client *******************************
[14] # Client
[15] # Unicast(1=Si;0=No),Refresh(msec),ConRetries,RecoveryRefresh(msec),
[16] # Threshold,TimeToOnline(msec),TimeToOffline(msec),SegWaitAnswerSrv,
[17] 1,10000,3,10000,0,20000,30000,1,
[18] # Number of servers
[19] 2,
[20] 128.127.160.159,// IP server 1
[21] 128.127.160.160,// IP server 2
[22] #
[23] ############### SNTP general parameters ############################
[24] # IgnoreLI2Sync,FollowLI,
[25] 0,0,
[26] # SNTP Traces (0=No;1=Si),
[27] 0,

M1CPTA2005I
A-93 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

A.18 File to Configure the Communications with Terminal

Servers: TScoms.CFG
The file “TSComs.cfg” contains data to configure the communications with Terminal Server
model CIC. This file shows the IP addresses and TCP ports used to communicate with Terminal
Servers.

File format is as follows:

• Terminal Server Communications Data
NumTS , Timeout ,

• NumTS: Number of Terminal Servers configured in the file. Maximum 2.

• Timeout: Terminal Server communications timeout. This value is expressed in seconds
and can be any value from 1 to 32767. Default value is 10.

DirIP , NumPuertos , (**)

PuertoVirtual , PuertoTCP , (*)

(**) It repeats for each Terminal Server to be configured. There will be as many as
shown in NumTS.
(*) It repeats for each Terminal Server Port to be configured. There will be as many as
shown in NumPuertos.

• DirIP: IP address of the Terminal Server (CIC). It is used by the CPT to carry out TCP
connections. If the IP address is within the LAN1 range, the connections will be carried
out using said interface. If it is within the LAN2 range, the connections will be carried out
using this other interface. In case the ranges coincide, LAN1 will be used.
• NumPuertos: Number of ports to be configured in the Terminal Server. The 9 available
ports will be configured by default.
• PuertoVirtual: States the logic port number assigned to each Terminal Server port. They
must be configured in consecutive order, with no skips, namely, the first line is for the first
port, the second line for the second port, etc. The values to take down here are the ones
shown in the following table.
• PuertoTCP: Number of the TCP port that the corresponding physical port is associated to
in the CIC. As a general rule the values to be used are shown in the following table, but, if
the configuration of the installation network so requires, these can be changed to other
values provided the same numbers are placed in this file and the CIC configuration.

M1CPTA2005I
1CPT: Substation Central Unit A-94
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex A. Configuration Files for CPX / CPP / CPT

First CIC Second CIC

Virtual TCP Virtual TCP
Puerto port Puerto port
201 1001 211 1001
202 1002 212 1002
203 1003 213 1003
204 1004 214 1004
205 1005 215 1005
206 1006 216 1006
207 1007 217 1007
208 1008 218 1008
209 1009 219 1009

The file for two CICs becomes:

# TSCOMS.CFG
# NumTS, Timeout,
2,10,
#For each Terminal Server the block below is configured.
# IP, Num ports,
128.127.88.77,9,
# Virtual port, TCP port,
201,1001,
202,1002,
203,1003,
204,1004,
205,1005,
206,1006,
207,1007,
208,1008,
209,1009,
# IP, Num ports,
128.127.88.78,9,
# Virtual port, TCP port,
211,1001,
212,1002,
213,1003,
214,1004,
215,1005,
216,1006,
217,1007,
218,1008,
219,1009,

M1CPTA2005I
A-95 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex A. Configuration Files for CPX / CPP / CPT

M1CPTA2005I
1CPT: Substation Central Unit A-96
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
B. Configuration of Protocol
Emulators
 Annex B. Configuration of Protocol Emulators

B.1 Introduction
This Enclosure contains a description of the configuration files for the different protocol
emulators that can be included in the CPX/CPP/CPT software.

Electricity companies have a communication mechanism with electrical substations that enables
them access to part of the information from the same, and this, in turn, enables them to
manoeuvre certain elements. One of the most important characteristics of the CPX/CPP/CPT is
that it enables external access to substation data in order that the previously described
operations can be carried out.

The communications’ mechanism used by each of the electricity companies varies quite a lot,
even within the same company. Generally speaking, all communications are carried out via
series, albeit the physical environment usually varies: radio waves, carrier waves, optic fibre,
etc. In the end, the interphase with the CPX/CPP/CPT is translated into a series RS-232
connector, which connects with the CPX/CPP/CPT on one side and with a modem on the other.
Communication with control offices is also possible through a TCP/IP link on Ethernet.

The main difference lies on the communications’ protocol used for linking both devices. In order
to be able to connect to these devices, the CPX/CPP/CPT must not only implement the
communications’ protocol in question, but must also emulate certain functionality characteristics
that are associated to this protocol. This functionality is supported in the CPX/CPP/CPT via a
protocol emulator.

A protocol emulator is an internal task of the CPX/CPP/CPT which emulates a specific

behaviour, different from that of the CPX/CPP/CPT itself, to communicate with one or various
top level devices, in such a way that they will understand that the CPX/CPP/CPT is the type of
device that they expect. This task is in charge of implementing messages and communications’
protocol procedures themselves, apart from setting the data according to the formats expected
by the other device.

A configuration file is associated to each of these protocols, which is used to link data within the
CPX/CPP/CPT database with data from the database of the electricity company.

The following sections will provided a detailed explanation of each of these configuration files.

M1CPTA2005I
1CPT: Substation Central Unit B-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2 CEI 870-5-101 Family Protocols

B.2.1 Non-Balanced Type III: CEI101C.CFG
Data referring to the remote control is configured in the file called “cei101c.cfg”, using non-
balanced Type III CEI-870-5-101 protocol: general data, orders (simple), tap change
commands, contact-type signals (simple and double), measurements, meters, set point
regulation commands and causal associations. These orders, commands, signals,
measurements and meters are referenced under protocol address 101 (Dir101). Each of these
shall be associated to a CPX/CPP order, signal, measurement or meter.

The file format is as follows:

• Configuration Data of Remote Communications Failure Signal
This will be carried out as described under section A.1: [lines 2-3]

Ex: 1,
0,1,0,0,0,

• RTU emulation data: [Line 5]

DirRTUEmul , DirASDU ,

• DirRTUEmul: Address of the RTU to emulate.

• DirASDU: ASDU address. Generally speaking, the same as DirRTUEmul.

Ex: 3,3,

• Configuration Data of Port Communications: [line 7]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications Port. Possible values are COM1, COM2, COM3 and COM4.
• Veloc: Baud rate. It can use the following values 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can use values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’,‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. It can use values 1 and 2.

Ex: COM1,1200,e,8,1,

M1CPTA2005I
B-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Remote Control Time Parameters: [Line 10]

RxRTSon , RTSon , RTSoff , CTS , ErrorTel , NivelMonitor ,

• RxRTSon: Time lapsed from the moment a message is received until the RTS is
activated ( in ms; from 0-32767, in 11 ms increments).
• RTSon: Time that the RTS remains ON before transmitting (in ms; from 0-32767, in 11
ms increments).
• RTSoff: Time that the RTS remains OFF after transmitting (in ms; from 0-32767, in 11 ms
increments).
• CTS: Indicates activation (1) or not (0) of the CTS command.
• ErrorTel: Time lapsed before remote control error is issued (in sec.).
• NivelMonitor: Trace monitoring level.

Ex: 200,100,100,0,90,0,

• Configuration Data of Remote Control Single Commands

Each remote control single command is associated a CPX/CPP command. It is essential to put
Dir101s in ascending order: [lines 12-22]

NumOrdenes ,
Dir101 , DirEq , ISE , (*)

(*) This repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of Remote Control Single Commands.

• Dir101: Address of 101 protocol single command.
• DirEq: Address of the equipment that the CPX/CPP command belongs to.
• ISE: PROCOME label of CPX/CPP command.

Ex: 03,// Num. Single commands

3001,22,12,
3002,12,0,
3003,12,1,

• Configuration Data of Tap Change Commands (Equivalent to RTN Tap

Change)
Two commands (raise and lower the tap) are associated to each tap change command from the
CPX/CPP and a measurement where one can read the tap. It is essential to put Dir101s in
ascending order: [lines 24-27]

NumComandos ,
Dir101 , DirEq , ISEsubir , ISEbajar , MEA , (*)

(*) This repeats for each remote control tap change command. There will be as many as
indicated under NumCommands. They will be displayed in ascending order of Dir101.

• NumCommands: Number of remote control tap change commands.

• Dir101: Address 101 protocol command.
• DirEq: Address of the equipment that CPX/CPP commands and measurement belong to.
• ISEsubir: PROCOME label of CPX/CPP command to raise tap.
• ISEbajar: PROCOME label of CPX/CPP command to lower tap.
• MEA: PROCOME label of the CPX/CPP measurement where the tap is read.

M1CPTA2005I
1CPT: Substation Central Unit B-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 02,// Number of Tap Change commands

5001,17,4,5,1,
5002,21,4,5,1,

• Configuration Data of the Single Remote Control Contact Type Signals

A CPX/CPP digital signal is associated to each single remote control contact type signal. It is
essential to put Dir101s in ascending order: [lines 29-39]

NumSD ,
Dir101 , DirEq , ISC , COT , GRUPO , (*)

(*) This repeats for each single remote control contact type signal. There will be as many as
indicated under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of single remote control contact type signals.

• Dir101: Address of 101 protocol single contact digital signal.
• DirEq: Address of the equipment that the associated CPX/CPP digital signal belongs to.
• ISC: PROCOME label of the CPX/CPP digital signal.
• COT. Cause of transmission. In general = 3 (Spontaneous)
• GRUPO. Group that the digital signal belongs to. In general = 20 (Global)

Ex: 10,// NumSD

1,10,0,3,20,
2,10,1,3,20,
3,10,2,3,20,
…
10,14,31,3,20,

• Configuration Data of the Remote Control Double Contact Signals

Each of this type of remote control signal is associated to three CPX/CPP digital signals. It is
essential to put Dir101s in ascending order: [lines 41-54]

NumSD ,
Dir101 , DirEq , ISC_OFF , ISC_ON , ISC_DESC ,

, COT , GRUPO , (*)

(*) This repeats for each remote control double contact signal. There will be as many as
indicated under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control double contact signals.

• Dir101: Address of 101 protocol double contact signal.
• DirEq: Address of the equipment that the associated CPX/CPP digital signals belong to.
• ISC_OFF: PROCOME label of the CPX/CPP digital signal that indicates the OFF status
of the double contact signal.
• ISC_ON: PROCOME label of the CPX/CPP digital signal that indicates the ON status of
the double contact signal.
• ISC_DESC: PROCOME label of the CPX/CPP digital signal that indicates the
UNKNOWN status of the double contact signal.
• COT. Cause of transmission. In general = 3 (spontaneous))
• GRUPO. Group that the digital signal belongs to. In general = 20 (Global)

M1CPTA2005I
B-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 22, // NumSD

10000,22,10,11,0,3,20,
10002,22,12,13,0,3,20,
10004,22,14,15,0,3,20,
…
10022,22,52,53,0,3,20,

• Configuration Data of Remote Control Measurements

A CPX/CPP measurement is associated to the remote control measurement. It is essential to
put Dir101s in ascending order. Measurement values in this protocol implementation are scaled:
[lines 56-79]
NumMeds , Escala , TimeCaptura , MaxCapturas ,

Dir101 , Dir , Med , Ope1 , Ope2 , Ope3 , Ope4 , Ope5 , ..

.. Ope6 , VBA , PBA , LINF , LISUP , VMAX , VMIN , (*)

(*) This repeats for each remote control measurement. There will be as many as indicated
under NumMeds.

• NumMeds: Number of remote control measurements.

• Escala: Measurement scale value. It must be configured as 1.0.
• TimeCaptura: Indicates how many seconds elapse between captures of the configured
remote control measurements. These captures will be documented in a circular file and
forwarded as class-2 data when required by the control facility. If this is not configured,
the default parameter value is 40 seconds.
• MaxCapturas: Maximum number of periodic data captures to be saved into the circular
file. If the parameter is not configured, the default value will be 3 captures.
• Dir101: Address of 101 protocol measurement.
• Dir: Address of the equipment that the CPX/CPP measurement belongs to.
• Med: PROCOME label of CPX/CPP measurement.
• Ope1: VBA parameter use indicator: Always set to 1 = In use.
• Ope2: PBA parameter use indicator: Always set to 0 = Not in use.
• Ope3: LINF parameter use indicator: Always set to 0 = Not in use.
• Ope4: LISUP parameter use indicator: Always set to 0 = Not in use.
• Ope5: VMAX parameter use indicator: Always set to 0 = Not in use.
• Ope6: VMIN parameter use indicator: Always set to 0 = Not in use.
• VBA: Band Value indicates the minimum variation between two measurement values in
order for the new value to be sent to the Master Station.
• PBA: Band Period is the time elapsed for the measurement to be considered valid for
sending. Not in use. (=0)
• LINF: Low Limit indicates the value below which the Alarm status is produced. Not in use.
(=0)
• LISUP: High Limit indicates the value above which the Alarm status is produced. Not in
use. (=0)
• VMAX: Maximum Value indicates the engineering value of the maximum value that the
user sensor can deliver to the capture card.
WARNING: This value must be multiplied by the Scale factor.
• VMIN: Minimum Value indicates the engineering value of the minimum value that the user
sensor can deliver to the capture card.
WARNING: This value must be multiplied by the Scale factor.

M1CPTA2005I
1CPT: Substation Central Unit B-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

VBA, LINF, LISUP, VMAX and VMIN parameters must be configured in scaled engineering
values, i.e., within the scale determined by the Escala parameter.
In order to obtain the conversion ratio from the 12 bit digital values sent by the relays to the
engineering values used by this IEC-102 remote control profile, the VMAX and VMIN
parameters must be enabled and configured. Thus, two new parameters, Corr and Offset, will
be calculated internally in the Central Unit from the values configured for VMAX and VMIN. This
two new parameters define, for each measurement, the conversion ratio that will enable the
conversion of the 12 bit digital values sent by the relays into the engineering values used by this
IEC-102 remote control profile prior to being translated to the scale defined by the Escala
parameter. Once the conversion to engineering values has been made, the measurement value
is translated to the scale defined by the Escala parameter.

Value_Measurement_101 = [ ( Value_Measurement_Equip * Corr ) + Offset ] * Scale

Parameters VBAMin and VBAMax in primary values (please, bear in mind that scaled values
will be configured in the file between VMAX and VMIN) are different for each type of
measurement:

Parameters for each Measurement Type

MEASUREMENT MIN MAX
CURRENT (A) 0 100
VOLTAGE (V) 0 1000
ACTIVE P (W) 0 2000
REACTIVE P (VAR) 1000 1000
V. ref. RTN (V) 1 1
TAP VALUE 1 1
WINDING TEMP (ºC) 0 10
OIL TEMP (ºC) 0 10
SUBST.VDC (V) 0 10
SUBST. VAC (V) 0 10

Ex: 4,1.0,40,3, // Num. measurements

6001,22,0,1,0,0,0,0,0,60,0,50,150,300,0,
6002,22,1,1,0,0,0,0,0,65,0,60,160,300,0,
6003,22,2,1,0,0,0,0,0,65,0,60,160,300,0,
6004,22,3,1,0,0,0,0,0,65,0,60,160,300,0,

M1CPTA2005I
B-7 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Counters

Each remote control counter is associated a CPX/CPP counter. It is essential to put Dir101s in
ascending order: [lines 81-90]

NumConts ,
Dir101 , DirEq , CON , GRUPO , (*)

(*) This repeats for each remote control counter. There will be as many as indicated under
NumConts. They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• Dir101: Address of 101 protocol counter.
• DirEq: Address of the equipment that the CPX/CPP counter belongs to.
• CON: PROCOME label of CPX/CPP counter.
• GRUPO. Group that the digital signal belongs to.

Ex: 4,// Num. Counters

7001,22,0,20,
7002,22,1,20,
7003,22,2,20,
7004,22,3,20,

• Configuration Data of Set Point Change Commands (Equivalent to a Change

of RTN Set Point)
Each remote control set point change command is associated to two CPX/CPP commands
(raise and lower the set point) and a measurement to read the set point value. It is essential to
put Dir101s in ascending order: [lines 92-95]

NumComandos ,
Dir101 , DirEq , ISEsubir , ISEbajar , MEA , Paso , (*)

(*) This repeats for each remote control set point change command. There will be as many as
indicated under NumCommands. They will be arranged in ascending order of Dir101.

• NumCommands: Number of remote control set point change commands.

• Dir101: Address of 101 protocol command.
• DirEq: Address of the equipment that the CPX/CPP commands and measurement belong
to.
• ISEsubir: PROCOME label of the CPX/CPP command to raise the set point.
• ISEbajar: PROCOME label of the CPX/CPP command to lower the set point.
• MEA: PROCOME label of CPX/CPP measurement where to read the set point value
from.
• Paso: Number of units the set point value is increased or decreased for each set point
change command. It must be configured by default as 205. This value is calculated by
dividing 4095 (range of points of the set point) by 20 (maximum number of times the set
point of an RTN ca be raised or lowered).

Ex: 02, // Num. Set point change commands

8001,17,2,3,1,205,
8002,21,2,3,1,205,

M1CPTA2005I
1CPT: Substation Central Unit B-8
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Causal Associations

The association between PROCOME cause of transmissions (COT) which are going to be
derived from the changes and the corresponding IEC101 COTs used for forwarding these
changes to the control facility are defined hereunder.: [lines 97-102].

NumAsocCausales ,
COT_PROCOME , COT_CEI101 , (*)

(*) This repeats for each causal association. There will be as many as indicated under
NumAsocCausales.

• NumAsocCausales: Number of causal associations.

• COT_PROCOME: Cause of PROCOME change transmission.
• COT_CEI101: Cause of IEC101 transmission with which changes received through
COT_PROCOME must be sent.

Ex: 4,// Num. causal assoc.

128,48,// Desconocido
129,49,// Protección
130,50,// Automatismo
131,51,// Manual

The file becomes:

[1] # Configuration of RTU CEI101c

[2] 1,
[3] 0,1,0,0,0,
[4] # Address of the RTU to emulate
[5] 3,3, // Link and ASDU
[6] # Parameters for port communications
[7] COM1,1200,e,8,1,
[8] # RTS ON (CS0T), RTS OFF timing in millisec, Flow CTS (on/off), remote
control error
[9] # in seconds,monitor
[10] 200,100,100,0,90,0,
[11] # Single commands
[12] 03, // Num. of single commands
[13] # DIR101,DIR,ISE,ISCon,ISCoff,ISCdes Association.
[14] # It is essential to put Dir101s in ascending order.
[15] # DIR 101 is the address of the COMMAND-type objects.
[16] # DIR,ISE are the PROCOME addresses and the 7IRD command that executes
the command.
[17] # ISCon is the ISC that indicates the activation of the order (Eg.:
OPEN).
[18] # ISCoff is ISC deactivation (E.g.: CLOSED.
[19] # ISCdes indicates (E.g.:UNKNOWN).
[20] 3001,22,12, // Close
[21] 3002,12,0, // Open
[22] 3003,12,1,
[23] # Tap change commands (change of tap) ).
[24] 02,
[25] # ADD 101,Dir,ISE (RAISE),ISE (LOWER), Measurement Nº where the TAP is
read.
[26] 5001,17,4,5,1,
[27] 5002,21,4,5,1,
[28] # Nº Single CONTACT signals
[29] 10,

M1CPTA2005I
B-9 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[30] # DIR101,DIR,ISC association.

[31] # It is essential to arrange DIR101 in ascending order .
[32] # DIR 101 is the address of single CONTACT objects.
[33] # DIR,ISC are the PROCOME address and the 7IRD signal where
[34] # COT contact is ( =3: Spontaneous) and GROUP ( =20: Global)
[35] 1,10,0,3,20,
[36] 2,10,1,3,20,
[37] 3,10,2,3,20,
[38] ...
[39] 10,14,31,3,20,
[40] # Nº Double CONTACT signals,
[41] 22,
[42] # Double contacts are calculated from single contacts, therefore, here,
[43] # three ISCs must be configured for each double contact.
[44] # DIR101,DIR,ISC,ISC,ISC association.
[45] # It is essential to put Dir101s in ascending order.
[46] # DIR 101 is the address of double CONTACT objects.
[47] # DIR,ISC_ON,ISC_OFF,ISC_DESC are the PROCOME addresses and signals
[48] # of the 7IRD where the contact is.
[49] # COT ( =3: Spontaneous) and GROUP ( =20: Global)
[50] 10000,22,10,11,0,3,20,
[51] 10002,22,12,13,0,3,20,
[52] 10004,22,14,15,0,3,20,
[53] ...
[54] 10042,22,52,53,0,3,20,
[55] # Measurements
[56] 4,1.0,40,3,// Nº measurements.
[57] # Since the values of the measures for this implementation of the 101
[58] # are Standard values.
[59] # DIR 101 is the address of MEASUREMENT objects.
[60] # E.g.: 15001 is the MEASUREMENT address.
[61] # DIR,MED are the PROCOME addresses and the 7IRD Measurement Number.
[62] # CORRECTION is the factor that enables conversion of equipment
[63] # measurement values to 101 measurement values. (Not always used).
[64] # OFFSET is the offset that enables conversion of equipment measurement
[65] # values to 101 measurement values. (Not always used).
[66] # OPE(6) corresponds to parameter use indicator; 0 indicates not
[67] # In use. 1 indicates in use.
[68] # VBA,PBA,LINF,LISUP,VMAX,VMIN parameter default values.
[69] # These values may be changed any moment through communications.
[70] # The use of these parameters is explained in the implementation
[71] # document "LOADING PARAMETERS".
[72] # NOTE: Only VBA,LINF and LISUP are used for this implementation.
[73] # LINF and LISUP are not used in ELIOP control facility.
[74] # OPE values set to 0.
[75] # DIR101,DIR,MED,OPE(6),VBA,PBA,LINF,LISUP,VMAX,VMIN,ENVIO,VBAMin,VBAMax
[76] 6001,22,0,1,0,0,0,0,0,60,0,50,150,300,0,
[77] 6002,22,1,1,0,0,0,0,0,65,0,60,160,300,0,
[78] 6003,22,2,1,0,0,0,0,0,65,0,60,160,300,0,
[79] 6004,22,3,1,0,0,0,0,0,65,0,60,160,300,0,
[80] # Counters
[81] 4, // Num. Counters
[82] # Counters of this profile (COELBA) are periodically gathered
[83] # and sent to the control facility as Class1.
[84] # DIR 101 is the address of COUNTER type objects.
[85] # DIR,CON are the PROCOME address and COUNTER number of 7IRD.
[86] # DIR101,DIR,CON, GRUPO ( =20: Global)

M1CPTA2005I
1CPT: Substation Central Unit B-10
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[87] 7001,22,0,20,
[88] 7002,22,1,20,
[89] 7003,22,2,20,
[90] 7004,22,3,20,
[91] # Set point control commands
[92] 2,// Num. Commands
[93] # DIR101,DIR,ISEsubir,ISEbajar,MEA,Tab,
[94] 8001,17,2,3,1,205,
[95] 8002,21,2,3,1,205,
[96] # Causal associations
[97] 4,// Num. Causal assoc.
[98] # COT Procome, COT CEI101
[99] 128,48,// Unknown
[100] 129,49,// Protection
[101] 130,50,// Control function

M1CPTA2005I
B-11 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.2 Unbalanced Type IV: CEI101A.CFG

In this file, “cei101a.cfg”, the parameters of IEC 870-5-101 remote communication protocol,
IEC 870-101 protocol emulator Unbalanced type IV parameters are configured: general data,
orders, signals, measurements and counters. These orders, signals, measurements and
counters are referenced with a 101 protocol address (Dir101). Each of these shall be associated
a CPX/CPP order, signal, measurement or meter. The file format is as follows:
• Configuration Data of Remote Communications Failure Signal
This will be carried out as described under section A.1: [lines 2-3]

Ex: 1,
0,1,0,0,0,0,

• RTU Emulation Data: [line 5]

DirRTUEmul ,

• DirRTUEmul: Base address of the RTU to emulate.

Ex: 14,

• Configuration Data of Port Communications: [line 7]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications Port. Possible values are COM1, COM2, COM3 and COM4.
• Veloc: Baud rate. It can use the following values 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can use values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’,‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. It can use values 1 and 2.

Ex: COM1,9600,e,8,1,

• Remote Control Time Parameters: [Line 10]

RTSon , RTSoff , CTS , ErrorTel , NivelMonitor , CDOff ,

• RTSon: Time that the RTS remains ON before sending (in msec.).
• RTSoff: Time that the RTS remains OFF before sending (in msec.).
• CTS: CTS activation (1) or not (0).
• ErrorTel: Delay time for issuing a remote control error signal (in sec.).
• NivelMonitor: Trace monitoring level (0,1,2, or 3).
• CDOff: Time elapsed since the last character of the frame is received until the RTS is
activated.

Ex: 22,22,0,60,0,99,

M1CPTA2005I
1CPT: Substation Central Unit B-12
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Commands

Each remote control command is associated a CPX/CPP command. It is essential to put
Dir101s in ascending order: [lines 18-28]

NumOrdenes ,
Dir101 , DirEq , ISE , (*)

(*) This repeats for each remote control command. There will be as many as indicated under
NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control commands.

• Dir101: Address of 101 protocol command.
• DirEq: Address of the equipment that the CPX/CPP command belongs to.
• ISE: PROCOME label of the CPX/CPP command.

Ex: 09,// Num. Commands

3001,10,0,
3002,10,1,
3003,11,0,
…
3009,10,2,

• Configuration Data of Single Contact Remote Control Signals

Each remote control signal of this type is associated a CPX/CPP digital signal. It is essential to
put Dir101s in ascending order: [lines 32-43]

NumSD , DirSeñOverflow ,
Dir101 , DirEq , ISC , (*)

(*) This repeats for each remote control digital signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of digital signals of the remote control.

• DirSeñOverflow: Address of the Overflow signal. This overflow address is the contact that
indicates the queue is full. The address of the object that represents it is indicated here.
• Dir101: Address of 101 protocol digital signal.
• DirEq: Address of the equipment that the CPX/CPP digital signal belongs to.
• ISC: PROCOME label of the CPX/CPP digital signal.

Ex: 40,2049,// NumSD, Addr Signal Overflow

1,10,1,
2,10,2,
3,10,3,
…
40,13,2,

M1CPTA2005I
B-13 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Measurements

A CPX/CPP measurement is associated to the remote control measurement. It is essential to
put Dir101s in ascending order. Measurement values in this protocol implementation are scaled:
[lines 45-72]

NumMeds , Escala ,
Dir101 , DirPar , Dir , Med , Corr , Ope1 , Ope2 , Ope3 , Ope4 ,

Ope5 , Ope6 , VBA , PBA , LINF , LISUP , VMAX , VMIN , (*)

(*) This repeats for each remote control measurement. There will be as many as indicated
under NumMeds.

• NumMeds: Number of remote control measurements.

• Escala: Scaling factor of the measurement (x10, x100,…).
• Dir101: Address of 101 protocol measurement.
• DirPar: Address of parameter-type objects. 6 associated parameters are considered for
each of the measurements, and, hence, DirPar is the first parameter object's address.
The rest of the parameters (5) go under successive addresses. In the example:
6001 is the measurement address.
11001 is the address of the first parameter associated to the measurement (Band Value
VBA).
11002 is the address of the Band Period (PBA) parameter.
11003 is the address of the Low Limit (LINF) parameter.
11004 is the address of the High Limit (LISUP) parameter.
11005 is the address of the Maximum Value (VMAX) parameter.
11006 is the address of the Minimum Value (VMIN) parameter.
• Dir: Address of the equipment that the CPX/CPP measurement belongs to.
• Med: PROCOME label of CPX/CPP measurement.
• Corr: Correction factor to convert equipment measurement values into 101 measurement
values. (Not always used).
• Ope1: Use indicator of VBA parameter: 0 = Not in use; 1 = In use.
• Ope2: Use indicator of PBA parameter: 0 = Not in use; 1 = In use.
• Ope3: Use indicator of LINF parameter: 0 = Not in use; 1 = In use.
• Ope4: Use indicator of LISUP parameter: 0 = Not in use; 1 = In use.
• Ope5: Use indicator of VMAX parameter: 0 = Not in use; 1 = In use.
• Ope6: Use indicator of VMIN parameter: 0 = Not in use; 1 = In use.
• VBA: Value de Banda indicates the minimum variation between two measurement values
in order for the new value to be sent to the Master Station.
• PBA: Band Period is the time elapsed for the measurement to be considered valid for
sending.
• LINF: Low Limit indicates the value below which the Alarm status is produced.
• LISUP: High Limit indicates the value above which the Alarm status is produced.
• VMAX: Maximum Value indicates the engineering value of the maximum value that the
user sensor can deliver to the capture card.
• VMIN: Minimum Value indicates the engineering value of the minimum value that the user
sensor can deliver to the capture card.

VBA, LINF, LISUP, VMAX and VMIN parameters must be configured in scaled engineering
values, i.e., within the scale determined by the Escala parameter.

M1CPTA2005I
1CPT: Substation Central Unit B-14
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

When the use of VMAX and VMIN parameters is enabled, the value configures in the file
“cei101.cfg” for Corr is not used. In this case, the value of this parameter is calculated internally
by the Central Unit from the values configured for VMAX and VMIN parameters. Also, a
parameter, Offset, is calculated.

With Corr and Offset, the conversion ratio to convert the 12 bit digital values sent by relays into
engineering values used by this IEC-101 remote control profile, before being translated into the
scale defined by the Escala parameter, is obtained. Once the conversion into engineering
values has been made, the measurement value is translated to the scale defined by the Escala
parameter.

Value_Measurement_101 = [ ( Value_Measurement_Equipo * Corr ) + Offset ] * Escala

Ex: 2,10.0, // Num. measurements, scaled value x 10

6001,11001,10,0,1.0,1,0,1,1,1,1,100,0,50,150,300,0,
6007,11007,10,1,1.0,1,0,1,1,1,1,100,0,60,160,360,0,

• Configuration Data of Remote Control Counters

Each remote control counter is associated a CPX/CPP counter. It is essential to put Dir101s in
ascending order: [lines 74-81]

NumConts ,
Dir101 , DirEq , CON , (*)

(*) This repeats for each remote control counter. There will be as many as indicated under
NumConts. They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• Dir101: Address of 101 protocol counter.
• DirEq: Address of the equipment that the CPX/CPP counter belongs to.
• CON: PROCOME label of CPX/CPP counter.

Ex: 4,// Num. Counters

7001,22,0,
7002,22,1,
7003,22,2,
7004,22,3,

M1CPTA2005I
B-15 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # Configuration of RTU CEI101

[2] 1,
[3] 0,1,0,0,0,
[4] # Address of the RTU to emulate
[5] 14, // Base
[6] # Parameters for port communications
[7] COM1,9600,e,8,1,
[8] # Time of RTS ON (CS0T) and RTS OFF in msec, CTS activation, remote
control error in
[9] # seconds, monitor level , CDOff in msec.
[10] 22,22,0,60,0,99,
[11] #
[12] # The data shown here are explained in section "DIRECCION OBJETO de
[13] # INFORMACIÓN/INFORMATION OBJECT ADDRESS" document
[14] # IEC-870 Version 3.2”. This section contains a table that defines the
range of
[15] # addresses of the different types of profile objects
[16] # Commands
[17] 09, // Num. of commands
[18] # DIR101,DIR,ISE Association. It is essential to arrange DIR101
[19] # in ascending order
[20] # DIR 101 is the address of the COMMAND-type objects
[21] # DIR,ISE are the PROCOME addresses and the 7IRD command that executes
the command
[22] 3001,10,0,
[23] 3002,10,1,
[24] 3003,11,0,
[25] ...
[26] 3009,10,2,
[27] # Nº Single CONTACT signals, Signal Overflow Class1 address
[28] # The overflow signal is the contact that indicates the queue is full
[29] # The address of the object that represents it is indicated here
[30] 40,2049,
[31] # DIR101,DIR,ISC association. It is essential to arrange DIR101
[32] # in ascending order. DIR 101 is the address of CONTACT type objects
[33] # single. DIR,ISC are the PROCOME address and the signal of the 7IRD
where
[34] # the contact is located
[35] 1,10,1,
[36] 2,10,2,
[37] 3,10,3,
[38] ...
[39] 40,13,2,
[40] # Measurements
[41] 2,10.0, // Measurement number, scaling value x10
[42] # Since the values of the measurements in the implementation of the 101
[43] # are displayed in scaled values. The scale used is indicated here

M1CPTA2005I
1CPT: Substation Central Unit B-16
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[44] # DIR 101 is the address of the MEASUREMENT type

[45] # DIR PARAM is the address of the PARAMETER-type objects. It is deemed
that
[46] # there are 6 associated PARAMETERS for each MEASUREMENT, hence DIR
PARAM is the
[47] # first address of the parameter object associated to the MEASUREMENT
which object address
[48] # is DIR 101, the 5 remaining parameters go in successive addresses.
[49] # E.g.: 6001 is the address of the MEASUREMENT
[50] # 11001 is the address of the first associated parameter (Band
value VBA)
[51] # 11002 is the Band period (PBA)
[52] # 11003 Low Limit (LINF)
[53] # 11004 High Limit (LISUP)
[54] # 11005 Maximum value (VMAX)
[55] # 11006 Minimum Value (VMIN)
[56] # DIR,MED Are the PROCOME address and the Measurement Number for 7IRD
[57] # CORRECCION is the factor that enables conversion of equipment
measurement values into
[58] # 101 measurement values. (Not always used)
[59] # OPE(6) Corresponds to parameter use indicators
[60] # 0 indicates not in use. 1 in use
[61] # VBA,PBA,LINF,LISUP,VMAX,VMIN are parameter default values
[62] # these values can be changed any moment through communications
[63] # To learn the use of these parameters please refer to “Description
[64] # Protocol IEC-870 V3.2” in section "PARAMETER LOADING"
[65] #
DIR101,DIRPARAM,DIR,MED,CORRECCION,OPE(6),VBA,PBA,LINF,LISUP,VMAX,VMIN,
[66] 6001,11001,10,0,1.0,1,0,1,1,1,1,100,0,50,150,300,0,
[67] 6007,11007,10,1,1.0,1,0,1,1,1,1,100,0,60,160,360,0,
[68] # Counters
[69] 4,// Num. Counters
[70] # DIR 101 is the address of the COUNTER type objects
[71] # DIR,CON are the PROCOME address and the COUNTER number of 7IRD
[72] # DIR101,DIR,CON
[73] 7001,22,0,
[74] 7002,22,1,
[75] 7003,22,2,
[76] 7004,22,3,

M1CPTA2005I
B-17 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.3 Balanced / Unbalanced /104: CEI101B.CFG

Data related to the remote control with balance and non-balanced CEI 870-5-101/104 protocol
is configured under file “cei101b.cfg” . This profile is highly configurable and enables adjusting
to a great variety of IEC101 communication profiles. Apart from parameters associated to
signals that are going to be forwarded or received from the master orders (simple and double),
(regulation commands, set point regulation commands, contact-type signals (simple and
double), measurements and meters), there are also parameters related to the customization of
the emulator to suit a specific profile. Thus, one can choose the sizes of the protocol's
configurable fields, the ASDU used for forwarding the various types of data, etc.

This profile is used, among others, for the following customers/SCADAS: Endesa, Siemens,
ABB, and Enersul. As regards Enersul, there are a series of parameters that must be configured
in accordance with SCADA’s requirements. These parameters will be displayed at the end of
the document.

Should CEI870-5-104 also be used, file GW104101.CFG, described under section B.2.8, must
also be configured in accordance with data describing the data sizes that are displayed further
on.

The format file is as follows:

• [BLQ_1] Configuration Data of Remote Control Communication Failure Signal
This will be carried out as described under section A.1: [lines 3-4]

Ej: 13,
0,1,0,0,0,1, // Remote Control Communications failure
1,1,0,0,0,1, //ISC Command NOT available
2,1,0,0,0,1, //ISC Local Command Blocking
3,1,0,0,0,1, //spare
4,1,0,0,0,1, //spare
5,1,0,0,0,1, // Client 1 connected or disconnected
6,1,0,0,0,1, //Client 2 connected or disconnected
7,1,0,0,0,1, //Client 3 connected or disconnected
8,1,0,0,0,1, //Client 4 connected or disconnected
9,1,0,0,0,1, //Client 5 connected or disconnected
10,1,0,0,0,1, //Client 6 connected or disconnected
11,1,0,0,0,1, //Client 7 connected or disconnected
12,1,0,0,0,1, //Client 8 connected or disconnected

• [BLQ_2] Data of the RTU to emulate

DirLINK , DirASDU , FrameMaxLenght , Interface104 , NumPortsCEI101B , ..

.. DirEnlaceLength , CotLength , DirAsduLength , DirObjLength ,

• DirLINK: Link address of the RTU to emulate.

• DirASDU: Common ASDU address.
• FrameMaxLenght: Maximum length in bytes (L), understood as being the maximum
sizeof the ASDU, plus the control byte and the address bytes for the link level. This value
cannot exceed 255, nor be lower than 50. If this parameter is not configured, the default
value adopted by the CPX/CPP is 126 bytes.
• Interface104: Indicates if communication is IEC101 (value 0) or IEC104 (value 1). In the
latter, file GW104101.CFG is required and task GW104101 is launched during run time.
The default value is 0 (zero).

M1CPTA2005I
1CPT: Substation Central Unit B-18
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumPortsCEI101B: Indicates the number of serial ports (1 or 2, no more) linked to the

Remote Control through communications. The default value is 1. Configuration
parameters for these ports are dealt with in the lines below. If not configured, the default
value is 1.
• DirEnlaceLength: Size in bytes of the link address (1 or 2).
• CotLength: Size in bytes of the cause of transmission (1 or 2).
• DirAsduLength: Size in bytes of the common ASDU address (1 or 2).
• DirObjLength: Size in bytes of the address of the data object (1, 2 or 3).

The default values, if nothing is configured for the above-mentioned sizes, are as follows:

Parameter Size
DirEnlaceLength 2
DirAsduLength 2
CotLength 2
DirObjLength 3

Note: If the 104 interface is configured this must be done in balanced mode in the “TipoEnlace” (LinkType)
parameter described below.

Ex: 111,111,126,0,1,2,2,2,3,

• [BLQ_3] Configuration Data of Port Communications

Puerto , Veloc , TipoPar , NumBits , NumStop , TamañoFIFO ,

If there is no 104 interface, the type of 101 link to use must be configured. There are two
possibilities: serial connection with one or two ports and network interface (encapsulated).

If a RS232 serial connection is used, the configuration parameters are as follows. If two ports
are used, two lines must be configured, one for each port.

• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4.
• Veloc: Baud rate. Possible values are 600, 1200, 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can take the values ‘N’ or ‘n’ (none); ‘O’ or ‘o’, (odd number); ‘E’
or ‘e’, (even number).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. Possible values are 1 and 2.
• TamañoFIFO: Is the size of FIFO in bytes. Possible values are 1, 4, 8, 14 or 0 (FIFO not
used). Default value is 1.
Ej: COM1,1200,e,8,1,1,
Ej2: COM1,1200,e,8,1,1,
COM2,1200,e,8,1,1,

M1CPTA2005I
B-19 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

If instead a network connection is used, namely, IEC101 messages are encapsulated in TCP/IP
packets, the configuration parameters are as follows. It is imperative that NumPortsCEI101B is
configured as 1.

DirIP , PuertoTCP ,

• DirIP: IP address configured in the Central Unit communications interface to

communicate with the control facility 101, using TCP/IP encapsulated IEC101 messages.
• PortTCP: TCP port used to communicate with SCADA using TCP/IP encapsulated IEC
101 protocol. Default value is 2405.

• [BLQ_4] Remote control time parameters

TimeLineaIdle , TimeWait , RTSon , RTSoff , CTS , ErrorTel , ..

.. NivelMonitor , TimeCambMando , TimeoutSel , TimeEntreConsig , ..

.. RTSAlwaysON , DSR , TimePuertoNoActivo PermisoSincronizar , …

.. ToutEntreCaracteres ,

• TimeLineaIdle: Minimum time lapse (in msec.) between successive transmissions to the
control facility. This is known as “idle line time”.
• TimeWait: Delay time (in msec.) from the moment the transmission is due until RTS sets
to ON (provided RTSon is other than 0), or else, delay time (in msec.) from the moment
the transmission is due until the transmission begins (if RTSon is set to 0). Default value
is 0.
• RTSon: Delay time from the moment RTS sets to ON until transmission begins (in msec.).
Default value is 0, which means RTS will never set to ON and, therefore, the transmission
will start immediately after TimeWait times out.
WARNING: If the RTS control line is not to be used, setting this parameter to 0 is
mandatory.
• RTSoff: Delay time (in msec.) between the moment of transmission until RTS sets to
OFF. Default value is 0, which means the RTS line will not be used.
• CTS: Indicates whether the CTS line is checked (1) or not (0) before transmitting. Default
value is 0.
• ErrorTel: Delay time (in sec.) before remote control error is issued. Default value is 60
seconds. Not used for the Balanced mode of the protocol.
• NivelMonitor: Trace monitoring level. Default value is 0.
• TimeCambMando: Timeout (in sec.), from command completion, to label the associated
changes with non spontaneous cause. Default value is 1 second.
• TimeoutSel: Timeout in seconds to automatically deselect a previously selected
command. It only has meaning when commands are run through the SELECT AND
EXECUTE method. Default value is 10 seconds.
• TimeEntreConsig: Delay time (in msec) between two successive set point commands.
Default value is 22 milliseconds.
• RTSAlwaysON: Indicates whether the RTS line must always be set to ON (1) (e.g., for
the balanced case when the CPX/CPP RTS is hard wired to the CTS of the control
facility) or not (0). If not configured, the default value is 0.

M1CPTA2005I
1CPT: Substation Central Unit B-20
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DSR: Indicates whether the DSR line must be checked (1) or not (0). If not configured,
the default value is 0.
• TimePuertoNoActivo: Timeout for (in seconds) for a port to be deemed non active and
switch to receive the adequate message through the other port. By default, the value will
be 0. This parameter is used in dual communications port configurations.
• PermisoSincronizar: Indicates whether synchronizations are enabled from the control
facility. The value 1 indicates they are enabled. The value 0 indicates they are not
enabled. This parameter must be configured in accordance with the rest of remote
controls, since synchronizations may only be supported from one source.
• ToutEntreCharacters: Timeout between characters to reject a frame (if 0, the value
calculated internally taking into account the port features: baud rate, bits,..) is used. By
default, this value will be 0, namely, the value calculated internally is used.

Ex: 35,0,0,0,0,60,0,1,10,22,0,0,10,1,0,

• [BLQ_5] Link Level Configuration Data

TipoEnlace , DirTxFisica , NumReintN2 , TimeoutN2 , ..

.. MaxNumCamb , MaxCambAntIntGen , DesechaCambSiOV , EnviaASDU70SiOV , ...

… , CfgDco , SenalesCOTComandoRemoto , IgnoraASDUDesconocido , …

… , NoEnviaASDU70Inicio , TipoPerfil ,

• TipoEnlace: Type of link level: 0=Balanced, 1=Unbalanced. By default, it is 0.

• DirTxFisica: Address of physical transmission. Equivalent to the DIR bit of the 101 frame
control byte: 1= Control facility ->RTU, 0= RTU->Control facility. Default value is 0.
• NumReintN2: Maximum number of link level retries to issue a communications error with
the control facility. Default value is 3 retries. It is meaningless for the Unbalanced mode.
• TimeoutN2: Timeout between link level retries (in msec.). Default value is 3000
milliseconds (3 seconds). It is meaningless for the Unbalanced mode.
• MaxNumCamb: Maximum number of changes kept in the queue. Above this number of
changes, a queue overflow signal is issued and all changes produced are discarded until
the queue is reduced. Default value is 1000 changes.
• MaxCambAntIntGen: Maximum number of changes previous to a general interrogation
request to be sent to the control facility between the moment of receiving this general
interrogation and the moment of sending the application (ACT_CON) of confirmation to
the general interrogation. Default value is de 10 changes.
• DesechaCambSiOV: Indicates, when the class 1 queue is full, whether the rest of
changes are discarded until there is space to introduce more data (1) or data are
introduced in the queue, overwriting the older data (0). If not configured, the default value
is 1.
• EnviaASDU70SiOV: Indicates, when the class 1 queue is full, whether an end-of-
initialization with Local Reset cause ASDU70 must be sent (1) or not (0). If not
configured, the default value is 0.
• CfgDco: Indicates the command DCO Configuration is enabled. By default, it is 0, and the
value DCO_ON is taken as command DCO, the value of which is 2.

M1CPTA2005I
B-21 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• SenalesCOTComandoRemoto: Indicates whether Remote Command Cause of

transmission (COT = 11) will be used (1), or not (0) for signals (single, alarm and double).
If not used, they will be sent as spontaneous (COT = 3). By default, it is used and will be
sent as spontaneous.
• IgnoraASDUUnknown: This parameter indicates the response sent to the control facility
when an interrogation is received from unknown ASDU. If the value is 1, it is ignored; if
the value is 0, the same ASDU is used for the reply, but with COT field P/N=1. By default,
the value is 0.
• NoEnviaASDU70Inicio: This parameter indicates if ASDU 70 is not forwarded (End of
Initialization) when the UCS is initialized. 0= IT IS sent and 1= IT IS NOT sent. By default,
it will be configured to 0. For ENERSUL, 1 must be configured.
• TipoPerfil: Indicates which of the 101 profiles is to be used. Certain profiles require
modification of complicated aspects of the implementation, hence they must be grouped
within this field. Possible values are: 0 =ENDESA+Value-by- Default, 1= ENERSUL.

Ex: 0,0,3,3000,1000,10,1,0,1,0,0,0,0,

• [BLQ_6] Time Synchronizing Configuration Data

GestionaST , NotificaST , TimeAjusteSync , CfgTimeSinSincro , EnviaConfSincroSiGPSOK , ..

.. ModoRTUSincro ,

• GestionaST: Indicates if the control facility sends the updated date and hour with
summer/winter time change (1) or not (0). Default value is 1.
• NotificaST: Indicates if the control facility sends the ST bit, indicating the summer/winter
time (1), or not (0). Default value is 1.
• TimeAjusteSync: Timeout (in msec) to adjust the time synchronization to compensate for
possible clock drift, channel delays, etc. Default value, 0.
• CfgTimeSinSincro: Time elapsed without RTU being synchronized by the control facility
in order that the RTU is considered NOT SYNCHRONIZED (in seconds). If this is
configured as 0, it entails that the time lapsed without synchronizing is not checked
(which is the default option).
• EnviaConfSincroSiGPSOK: Indicates if (ACT_CON) confirmation is sent (1), or not (0) to
a synchronization request (ASU 103), when the CPX/CPP is being correctly synchronized
by a GPS. By default, not sent (value set to 0).
• ModoRTUSincro: Indicates how the CPX is considered from the point of view of
synchronization with respect to the remote control. If the value is 0, when there is no
communication with the remote control, the CPX will be considered as being Non-
Synchronized. If the value is 1, the communications failure will not indicate CPX Not
Synchronized. Default value, 0.

Ex: 1,1,-11,0,0,0

• [BLQ_7] Configuration Data of Periodic Captures of Analogical

Measurements and/or Collections
MaxCapturas , TimeCiclo1 , TimeCiclo2 , TimeDespGI , TimeCicloDespGI , ..

.. CausaResetEnvioCiclico , ThresCalcCycle ,

• MaxCapturas: Maximum number of periodic captures of measurements and/or taps that

will be saved. Default value is 1.
• TimeCiclo1: Indicates after how many seconds data is captured during cycle 1. Default
value is 4 seconds.

M1CPTA2005I
1CPT: Substation Central Unit B-22
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TimeCiclo2: Indicates after how many seconds data is captured during cycle 2. Default
value is 12 seconds.
• TimeDespGI: Some of the measurements are sent to the control facility and, some time
after a General Interrogation (TimeDespGI) and after this, optionally, this is done in a
cyclic manner after a certain time lapse (TimeCicloDespGI). An example of this is the
measurements sent 12 seconds after a GI and, after this, they are sent periodically every
hour. It is indicated in seconds and its default value, if not configured, is 12 seconds.
• TimeCicloDespGI: See previous parameter. It is indicated in seconds and, if not
configured, the default value is 0, namely, measurements are only sent after a General
Interrogation and not periodically after.
• CausaResetEnvioCiclico: Possible causes for resetting the seconds timer for cyclic
transmission. Possible values are:
- 0: Never reset.
- 1: Reset upon receiving a synchronization from the control facility.
By default, if not configured, set to 1.
• ThresCalcCycle: Number of seconds for the Threshold algorithm calculation period. If the
value is 0, this function is not used. The value ranges between 0 and 3600. It is used in
Hidrocantábrico.

Ex: 1,4,12,12,0,1,0,

• [BLQ_8] Configuration Data of Remote Control Single Commands Type

ON=Pulse, OFF=Do Nothing
A CPX/CPP command is associated to each of the remote control single commands. It is
essential to put Dir101s in ascending order:

NumOrdenes , EjecSimple , CommandActTerm ,

Dir101 , DirEq , ISE , Dco , DirEqOn , ISCon , …

… DirEqOff , ISCoff , DirEqDes , ISCdes , (*)

(*) It repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.
• NumOrdenes: Number of Remote Control Single Commands type ON=Pulse, OFF=Do
Nothing.
• EjecSingle: Indicates if the single commands (both ON=Pulse, OFF=Do Nothing and
ON=Pulse, OFF=Pulse) are being run using DIRECT EXECUTE (0) or SELECT AND
EXECUTE (1). Default value is 1.
• CommandActTerm: Indicates if single command end of activation (ACT_TERM) is sent
(1) or not (0). By default, End of Activation is sent (TRUE=1).
• Dir101: Address of 101 protocol single command.
• DirEq: Address of the equipment that the CPX/CPP command belongs to.
• ISE: PROCOME label of the CPX/CPP command.
• Dco: Value of the CPX/CPP command Dco. Note: This field will only exist if the
command DCO configuration (CfigDco) is enabled. Otherwise, the DCO_ON will be
assumed.
• DirEqOn: Address of the equipment that the digital signal ISCon belongs to.
• ISCon: PROCOME label of the digital signal that indicates the command activation.
• DirEqOff: Address of the equipment that the digital signal ISCoff belongs to.
• ISCoff: PROCOME label of the digital signal that indicates the command deactivation.
• DirEqDes: Address of the equipment that the digital signal ISCdes belongs to.
• ISCdes: PROCOME label of the digital signal that indicates lack of information on the
status of the command.

M1CPTA2005I
B-23 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 2,1,1, // Num. Single commands,Type Ejec,CommandActTerm,

33000,10,1,2, 10,87, 10,93, 10,-1,
33001,10,4,2, 10,88, 10,94, 10,-1,

• [BLQ_9] Configuration data of Remote Control Single Commands type

ON=Pulse, OFF=Pulse
Each remote control single command is associated to a CPX/CPP command. It is essential to
put Dir101s in ascending order.

NumOrdenes ,
Dir101 , DirEq , ISEon , DcoOn , ISEoff , DcoOff , … (*)
... DirEqOn , ISCon , DirEqOff , ISCoff , DirEqDes , ISCdes ,

(*) It repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control single commands type ON=Pulse, OFF=Pulse.

• Dir101: Address of 101 protocol single command.
• DirEq: Address of the equipment that the CPX/CPP command belongs to.
• ISEon: PROCOME label of the CPX/CPP activation command of the double command
(close).
• DcoOn: Value of the CPX/CPP command Dco On. Note: This field will only exist if the
command DCO configuration (CfigDco) is enabled. Otherwise, the DCO_ON will be
assumed.
• ISEoff: PROCOME label of the CPX/CPP deactivation command of the double command
(open).
• DcoOff: Value of the CPX/CPP command Dco Off. Note: This field will only exist if the
command DCO configuration (CfigDco) is enabled. Otherwise, the DCO_ON will be
assumed.
• DirEqOn: Address of the equipment that the digital signal ISCon belongs to.
• ISCon: PROCOME label of the digital signal that indicates the command activation.
• DirEqOff: Address of the equipment that the digital signal ISCoff belongs to.
• ISCoff: PROCOME label of the digital signal that indicates the command deactivation.
• DirEqDes: Address of the equipment that the digital signal ISCdes belongs to.
• ISCdes: PROCOME label of the digital signal that indicates lack of information on the
status of the command.

Ej: 1, // Num. Single commands,

34000,10,1,2, 4,2, 10,87, 10,88, 10,-1,

• [BLQ_10] Configuration Data of Remote Control Double Commands

Each remote control double command is associated to two CPX/CPP commands. It is essential
to put Dir101s in ascending order:

NumOrdenes , EjecDouble , CommandDoubleActTerm ,

Dir101 , DirEq ISEon , DcoOn , ISEoff , DcoOff , … (*)
... DirEqOn ISCon , DirEqOff , ISCoff , DirEqDes , ISCdes ,

(*) This repeats for each remote control double command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

M1CPTA2005I
1CPT: Substation Central Unit B-24
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumOrdenes: Number of remote control double commands.

• EjecDouble: Indicates if the double commands are being run with DIRECT EXECUTE (0)
or SELECT AND EXECUTE (1). Default value is 1.
• CommandDoubleActTerm: Indicates if the single command end of activation
(ACT_TERM) signal is sent (1) or not (0). By default, End of activation is sent (TRUE=1).
• Dir101: Address of 101 protocol double command.
• DirEq: Address of the equipment that CPX/CPP commands to be associated to the
double command belong to.
• ISEon: PROCOME label of the CPX/CPP activation command of the double command
(close).
• DcoOn: Value of the CPX/CPP command Dco On. Note: This field will only exist if the
command DCO configuration (CfigDco) is enabled. Otherwise, the DCO_ON will be
assumed.
• ISEoff: PROCOME label of the CPX/CPP deactivation command of the double command
(open).
• DcoOff: Value of the CPX/CPP command Dco Off. Note: This field will only exist if the
command DCO configuration (CfigDco) is enabled. Otherwise, the DCO_ON will be
assumed.
• DirEqOn: Address of the equipment that the digital signal ISCon belongs to.
• ISCon: PROCOME label of the digital signal that indicates the double command
activation (ISEon command activation).
• DirEqOff: Address of the equipment that the digital signal ISCoff belongs to.
• ISCoff: PROCOME label of the digital signal that indicates the double command
deactivation (ISEoff command activation).
• DirEqDes: Address of the equipment that the digital signal ISCdes belongs to.
• ISCdes: PROCOME label of the digital signal that indicates lack of information on the
status of the double command.

Ex: 1,1,1,// Num.Double Commands,TipoEjec, CommandDoubleActTerm,

30000, 10, 1,2, 4,2, 10,87, 10,88, 10,-1,

• [BLQ_11] Configuration data of tap change commands (equivalent to an RTN

tap change)
Each remote control tap change command is associated to two CPX/CPP commands (raise and
lower the tap) and one measurement from which the tap is read. It is essential to put Dir101s in
ascending order.

NumMandos , EjecToma , CommandPasoActTerm ,

Dir101 , DirEq , ISEsubir , DcoSubirTo , ISEBajar , DcoBajarT , MEA , (*)
ma oma

(*) This repeats for each remote control tap change command. There will be as many as
indicated under NumCommands. They will be arranged in ascending order of Dir101.

• NumMandos: Number of remote control tap change commands.

• EjecToma: Indicates if the tap change commands are being run using DIRECT
EXECUTE (0) or SELECT AND EXECUTE (1). Default value is 1.
• CommandPasoActTerm: Indicates if tap change end of activation (ACT_TERM) is sent
(1) or not (0). By default, End of Activation is sent (TRUE=1).
• Dir101: Address of 101 protocol command.
• DirEq: Address of the equipment that CPX/CPP commands and measurement belong to.
• ISEsubir: PROCOME label of the CPX/CPP raise the tap command.

M1CPTA2005I
B-25 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DcoSubirToma: Value of the CPX/CPP command Dco On. Note: This field will only
exist if the command DCO configuration (CfigDco) is enabled. Otherwise, the
DCO_ON will be assumed.
• ISEbajar: PROCOME label of the CPX/CPP lower the tap command.
• DcoBajarToma: Value of the CPX/CPP command Dco On. Note: This field will only
exist if the command DCO configuration (CfigDco) is enabled. Otherwise, the
DCO_ON will be assumed.
• MEA: PROCOME label of CPX/CPP measurement where the tap is read.

Ex: 1,1,1, // Num.Tap Change Commands, TipoEjec.,

CommandPasoActTerm,
40000,104, 4,2, 5,2, 2,

• [BLQ_12] Configuration Data of Remote Control Single Contact Signals

Each remote control signal of this type is associated a CPX/CPP digital signal. It is essential to
put Dir101s in ascending order:

NumSD , DirSeñalOV , TipoASDUCambioSimple ,

Dir101 , DirEq , ISC , Grupo , (*)

(*) It repeats for each remote control single contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control single contact signals.

• DirSeñalOV: Address of the signal that indicates that the queue of data is full, namely,
overflow has occurred. Default value is -1, that means that the transmission function of
this signal is not enabled.
Note: This field will be configured as 0 for ERZ.
• TipoASDUCambioSingle: This parameter enables configuration of the ASDU to be used
to send digital signal changes to SCADA. It can take two values 2 (M_SP_TA_1: Single-
Point Information with Time Tag (CP24Time2a)) and 30 (M_SP_TB_1: Single-Point
Information with time tag CP56Time2a). The default value will be 30. Value 1
(M_SP_TA_1) will be used for ENERSUL profile.
• Dir101: Address of 101 protocol single contact digital signal.
• DirEq: Address of the equipment that the associated CPX/CPP digital signal belongs to.
• ISC: PROCOME label of the CPX/CPP digital signal.
• Grupo: Number of the group associated to the General Interrogation mode (ASDU_100)
that the single signal belongs to. The specific data profile of the Client in question must
be known to fill in this field, in order to determine the group that each single signal
belongs to. Allowed group values range from 1 (Group 1) to 16 (Group 16), and the value
0 is reserved for global interrogation of all data. Default value is 0, namely, global
interrogation request of all data.

Ex: 2,0,30, // NumSD, Addr Signal Overflow,TipoAsduSD,

1, 10,1, 0,
2, 10,2, 1,

M1CPTA2005I
1CPT: Substation Central Unit B-26
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• [BLQ_13] Configuration Data of Remote Control Alarm Signals

Only the activation of these signals, never the deactivation, is sent to the control facility.
Each remote control signal of this type is associated a CPX/CPP digital signal. It is essential to
put Dir101s in ascending order:

NumAla ,
Dir101 , DirEq , ISC , (*)

(*) It repeats for each remote control single contact signal. There will be as many as indicated
under NumAla. They will be arranged in ascending order of Dir101.

• NumAla: Number of remote control alarm signals. If they should not exist, (as is the case
for Chilectra) they are configured as 0.
• Dir101: Address of 101 protocol alarm digital signal.
• DirEq: Address of the equipment that the associated CPX/CPP digital signal belongs to.
• ISC: PROCOME label of the CPX/CPP digital signal.

Ex: 0, // NumAla,

• [BLQ_14] Configuration Data of Remote Control Double Contact Signals

Each remote control signal of this type is associated three CPX/CPP digital signals. It is
essential to put Dir101s in ascending order:

NumSD , TipoASDUCambioDoble ,
Dir101 , DirEq , ISC_OFF , ISC_ON , ISCdesconocido , Grupo , (*)

(*) It repeats for each remote control double contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control double contact signals.

• TipoASDUCambioDoble: This parameter enables configuration of the ASDU to be used
for forwarding the digital signal changes to the SCADA- Two values can be used, 4
(M_DP_TA_1: Double-Point Information with Time Tag (CP24Time2a)), and 31
(M_DP_TB_1: Double-Point Information with time tag CP56Time2a). The default value
will be 31. Value 4 (M_DP_TA_1) shall be used for ENERSUL’s profile
• Dir101: Address of 101 protocol double contact signal.
• DirEq: Address of the equipment that the associated CPX/CPP digital signals belong to.
• ISC_OFF: PROCOME label of the CPX/CPP digital signal that indicates the OFF status
(open) of the double contact signal.
• ISC_ON: PROCOME label of the CPX/CPP digital signal that indicates the ON status
(closed) of the double contact signal.
• ISCdesconocido: PROCOME label of the CPX/CPP digital signal that indicates the
unknown status of the double contact signal.
• Grupo: Number of the group associated to the General Data Interrogation Mode
(ASDU_100) that the double contact signal belongs to. To fill in this field, it will be
necessary to know the specific data profile of the actual customer in order to determine
the group that each double contact signal belongs to. Allowed group values range from 1
(Group 1) to 16 (Group 16), and 0 is reserved for global interrogation of all data. Default
value is 0, namely, global interrogation request of all data.

Ex: 1,31, // NumSD

7000,10,16,17,18,0,
7001,10,19,20,21, 1,

M1CPTA2005I
B-27 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• [BLQ_15] Configuration Data of Remote Control Taps

Each remote control tap is associated a CPX/CPP measurement. It is essential to put Dir101s
in ascending order:

NumTomas , EnviaTomasACero , TiempoTomaACero , TipoASDUTomas , …

… , TomaCOTComRem , TomaCOTCambEspon ,

Dir101 , DirEq , MEA , TipoEnvio , IntGen , Grupo , (*)

(*) It repeats for each remote control tap. There will be as many as indicated under
NumTomas. They will be arranged in ascending order of Dir101.

• NumTomas: Number of remote control taps.

• EnviaTomasACero: Indicates whether transient changes to zero that occur when
changing tap in our RTN's are sent to the control facility (1) or are filtered (0). If not
configured, the default value is 1.
This field will be configured as 1 for Chilectra.
This field will be configured as 0 for ERZ.
• TiempoTomaACero: Timeout (in seconds) to confirm a tap change to zero. When this
time times out, the tap will be sent to the control facility as invalid with the bit IV. Default
value is 10 seconds.
• TipoASDUTomas: Reads the type of ASDU used for spontaneous taps. It can take the
following values: 5 (M_ST_NA_1), 6 (M_ST_TA_1) or 32 (M_ST_TB_1). Periodic taps
and the ones in a General Interrogation (GI), are sent with the ASDU 5. If it is not
configured or is different from the allowed values, the default value is taken: 5
(M_ST_NA_1).
• TomaCOTComRem: Reads the parameter that Indicates whether to use (1) or not to use
(0) the cause of transmission COT_11, namely, tap change caused by a remote
command (from control facility). If not configured, the default value is (1) .
• TomaTipoCOTCambEspon: Reads the parameter that indicates the cause of
transmission to be used in spontaneous tap changes. Possible values are 3
(spontaneous) or 12 (caused by local command). If not configured, the default value is
12.
• Dir101: Tap address within 101.
• DirEq: Address of the equipment that the associated CPX/CPP measurement belongs to.
• MEA: PROCOME label of CPX/CPP measurement.
• TipoEnvio: Indicates whether taps are cyclically sent in cycle 1 (1), in cycle 2 (2) or are
not cyclically sent at all (0). No matter this cyclic transmission, taps will always sent
spontaneously if changed. Default value: 0.
• IntGen: Indicates whether the tap is sent (1) or not (0) as response to a General
Interrogation. If not configured, the default value is 1.
• Grupo: Number of the group associated to the General Interrogation mode (ASDU_100)
that the tap belongs to. The specific data profile of the Client in question must be known
to fill in this field, in order to determine the group that each tap belongs to. Allowed group
values range from 1 (Group 1) to 16 (Group 16), and the value 0 is reserved for global
interrogation of all data. Default value is 0, namely, global interrogation request of all
data.

Ej: 2,1,10,5,1,12, // Num.Taps, EnviaTomasACero, TiempoTomaACero,

TipoASDUTomas, TomaCOTComRem TomaTipoCOTCambEspon,
90000,104,2,0,1, 0,//Dir101,Dir,Mea,TipoEnv,IntGen,Grupo,
90001,105,2,0,1, 1,

M1CPTA2005I
1CPT: Substation Central Unit B-28
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• [BLQ_16] Configuration Data of Remote Control Measurements

A CPX/CPP measurement is associated to the remote control measurement. It is essential to
put Dir101s in ascending order. Measurement values in this protocol implementation are scaled:

NumMeds , TipoASDUMedidas ,
Dir101 , Dir , Med , VBA , VMAX , VMIN , FondoEscala , ..

.. TipoEnvio , IntGen , Offset , Threshold , Grupo , (*)

(*) This repeats for each remote control measurement. There will be as many as indicated
under NumMeds.

• NumMeds: Number of remote control measurements.

• TipoASDUMedidas: Reads the type of ASDU used for analog measurements. Possible
values are: 9 (standard value), 11 (scaled value) or 13 (floating point value). If not
configured or if it is different from the previous values, the default value is 11 (scaled).
• Dir101: Address of 101 protocol measurement.
• Dir: Address of the equipment that the CPX/CPP measurement belongs to.
• Med: PROCOME label of CPX/CPP measurement.
• VBA: Value de Banda, indicates the minimum variation between two measurement
values above which the new measurement value will be spontaneously sent to the control
facility. For this, TipoEnvio must be adequately configured ha: bit 4 active.
• VMAX: Maximum Value, indicates the engineering value of the maximum value that the
user sensor can deliver to the capture card.
• VMIN: Minimum Value, indicates the engineering value of the minimum value that the
user sensor can deliver to the capture card.
• FondoEscala: Indicates the number of units of the equipment measurement full scale.
Default value is 4095, which is the full scale of our PROCOME equipment.
• TipoEnvio: Indicates the measurement transmission mode to the control facility. Possible
values, considered as bit, are:
o 0: Not sent.
o 1: Cyclically sent in cycle 1 (every "TimeCiclo1" seconds).
o 2: Cyclically sent in cycle 2 (every "TimeCiclo2" seconds).
o 4: Spontaneously by VBA.
o 8: Sent "TimeDespGI" seconds after a General Interrogation and then, cyclically,
every "TimeCicloDespGI" seconds.
o 16: Sent using the threshold algorithm.
These values can be mixed with each other. Default value is 1.
• IntGen: Indicates whether the measurement is sent as response to a General
Interrogation (1) or not (0). Default value is 0.
• Offset: Indicates the offset value of the conversion line calculated with VMAX and VMIN
parameters. Default value is 0.
• Threshold: This parameter is used to send measurements by the Threshold method. If
the value is 0.0, not in use; if other than zero, then it is used as algorithm reference value.
In order to activate this function, it must also be activated in field TipoEnvio.
• Grupo: Number of the group associated to the General Interrogation mode (ASDU_100)
that the measurement belongs to. The specific data profile of the Client in question must
be known to fill in this field, in order to determine the group that each measurement
belongs to. Allowed group values range from 1 (Group 1) to 16 (Group 16), and the value
0 is reserved for global interrogation of all data. Default value is 0, namely, global
interrogation request of all data.

M1CPTA2005I
B-29 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

In order to obtain the conversion ratio from the digital values sent by the relays to the
engineering values used by this IEC60870-5-101 protocol profile, VMAX, VMIN, FondoEscala
and Offset must be adequately configured. In this way, two new parameters, Pendiente and
Desplazamiento, are calculated internally in the Central Unit from the values configured for
VMAX, VMIN, FondoEscala and Offset. These two new parameters define, for each
measurement, the conversion ratio that will enable the conversion of the digital values sent by
the relays into the engineering values used by this protocol profile.

Value_Measurement_101 = [ ( Value_Measurement_Equipo * Pendiente) +

Desplazamiento]

VMAX - VMIN
where Pendiente = -----------------------
FondoEscala

Desplazamiento = VMIN (if Offset is 0).

o
Desplazamiento = Offset (if Offset is other than 0).

• Measurement Transmission Algorithm by Threshold

Only if the band value is exceeded, the SCADA could issue a warning as for the reason for the
measurement not being updated.

With this method, if the difference is maintained for a given time, it is sent to the SCADA even if
the change is small.

The current value of the measurement is taken periodically and the difference is calculated with
the last transmitted value. The difference is added to the accumulated value of the previous
differences. If this value exceeds a settable value, threshold, the current value is sent to the
SCADA and is taken as the new reference value. To calculate the accumulated value, the sign
of the difference is taken into account, however, to compare with the threshold, it is not.

If a value keeps constant for a given time, its accumulated value increases in proportion to the
difference, reaching, at last, the threshold value.

M1CPTA2005I
1CPT: Substation Central Unit B-30
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Threshold value monitoring in the UCS.

Event channel activation with threshold means that the event channel connected to the object is
not activated immediately when the value is updated in the process database. Instead, a certain
type of algorithm is used to calculate when the activation is to happen.

We call event channel to the event of transmiting.

The purpose of thresholding is to lower the load of frequent event channel activations, for
example in cases where the event channel is used to send the value to another control station
via a slow communication channel. Event channel activation with threshold applies to analog
input signals. There is a variable called “threshold attribute” defined in the application which
implements the threshold. The value of this variable is set and can be changed by the user.

The algorithm used is an integrating threshold algorithm that works like this:

When AI (Analog Input) is updated and the new value differs from the last reported value (the
value of AI at the time of last activation), the threshold integral is set to zero and threshold
calculation is started.

On each calculation cycle (100 ms in current implementation) the time integral of the difference
between AI and the reported value is added to the threshold integral. For example, if the
reported value is 240.0 and AI is 243.0, value 0.3 is added to the integral.

If the absolute value of the integral reaches or exceeds the threshold attribute value, the
associated event channel is activated and the threshold calculation is stopped.

The algorithm guarantees that if the value is changed once and then stays in that new value,
the change is sooner or later reported.

Assigning a new value to threshold attribute does not restart the possible on-going threshold
calculation. The algorithm always uses the current value of threshold.

M1CPTA2005I
B-31 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Figure B.1: Event Channel Activation with Threshold.

Primary (left) y-axis represents the analog input value, here without unit. Secondary (right) y-
axis is the time integral of the analog input value. The value of the threshold attribute in this
example is 0,5. When the value of the threshold reaches or exceeds he value of 0,5, an event
channel is activated and the threshold calculation is reset.

Ex: 9,11, // Num. Measurements,TipoASDUMeasurements,

10000,10,0,10, 200,0,4095, 1,0,0,0, 1,
...
10008,104,1,0, 110,90,4095,1,0,0,0, 9,

M1CPTA2005I
1CPT: Substation Central Unit B-32
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• [BLQ_17] Configuration Data of Set Point Change Commands

There are two types of set point commands:

- Set point command by raise/lower the set point control function: after receiving a set
point change command, the Central Unit starts a control function to find out the number of
times to raise/lower the set point value to reach the desired value. This mode will be
applied for commands on CPUs that do not allow direct set point commands (only allow
raise/lower set point commands). Each set point command by control function is
associated two commands (raise and lower set point) and a measurement where the set
point can be read.
- Direct set point command: a direct command is run upon the CPU in order to set the set
point to a value. Each direct set point command is associated an analog output write in
order to write the set point value to the CPU and a measurement where the set point can
be read.

It is essential to put Dir101s in ascending order:

NumComandos , Ejec , TipoASDUC , NumComandos ,

Autom onsignas Direct
Dir101A , DirEqA , ISEsubir , DCOsubir , ...
(*)
... ISEbajar , DCObajar , MedA , Paso ,

Dir101D , DirEqD , ISM , MedD , (**)

(*) It repeats for each set point change command by raise/lower the set point control function.
There will be as many as indicated under NumCommandsAutom. They will be arranged in
ascending order of Dir101.
(**) It repeats for each direct set point change command. There will be as many as indicated
under NumCommandsDirect. They will be arranged in ascending order of Dir101.

• NumCommandsAutom: Number of remote control set point change commands by

raise/lower the set point control function.
• Ejec: Indicates if the set point change commands are being run using DIRECT EXECUTE
(0) or SELECT AND EXECUTE (1). Default value is 1.
• TipoASDUConsignas: Reads the type of ASDU used for set point commands. If it is not
configured, or is different from 48 (Standard), 49 (Scaled) or 50 (Floating point). Default
value is 49 (Scaled).
• NumComandosDirect: Number of remote control direct set point change commands. If
not configured, the default value is 0.
• Dir101A: Address of 101 protocol command.
• DirEqA: Address of the equipment that the CPX/CPP commands and measurement
belong to.
• ISEsubir: PROCOME label of the CPX/CPP command to raise the set point.
• DcoSubirConsigna: Value of the CPX/CPP command Dco On. Note: This field will only
exist if the command DCO configuration (CfigDco) is enabled. Otherwise, the
DCO_ON will be assumed.
• ISEbajar: PROCOME label of the CPX/CPP command to lower the set point.
• DcoBajarConsigna: Value of the CPX/CPP command Dco On. Note: This field will only
exist if the command DCO configuration (CfigDco) is enabled. Otherwise, the
DCO_ON will be assumed.
• MedA: PROCOME label of CPX/CPP measurement where the set point is read.
ATTENTION: this measurement must be included as remote control measurement
(section above) in order to configure its scaling parameters.

M1CPTA2005I
B-33 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Paso: Allows calculating the number of times the raise or lower the set point command
must be run to reach the required set point value, as follows:

|Current_Value-Required_Value|
Number of command runs = ----------------------------------------------
Paso
Default value is 205.

• Dir101D: Address of the direct command within protocol IEC-101.

• DirEqD: Address of the equipment (CPU) the analog output write belongs to and the
measurement in the Central Unit database.
• ISM: Analog output write identifier of the Central Unit to write the set point value to the
CPU.
• MedD: Measurement identifier of the Central Unit where the set point is read.
IMPORTANT: this measurement must be configured in the measurements section
(Configuration data of remote control measurements) in order to know its maximum
and minimum values and full scale to be able to scale up the set point. If the
measurement is not configured, the UCS will issue an error and the remote control will
not start.

Ex: 1,1,49,1,
35000,104,2,2, 3,2, 1, 205,
35001,10,0,0,

• [BLQ_18] Configuration Data of Remote Control Counters

Each remote control counter is associated a CPX/CPP counter. It is essential to put Dir101s in
ascending order:

NumConts , TimeAdq , TimeEnvio , RstCntCadaHora , ValLimCnt , EnviaBitCY ...

, MaxCapturasCont , ModoTransmisionContadores ,

Dir101 , DirEq , CON , (*)

(*) This repeats for each remote control counter. There will be as many as indicated under
NumConts. They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• TimeAdq: Counter capture interval in minutes, synchronized with CPX/CPP time. Default
value is 5 minutes.
• TimeEnvio: Time in seconds elapsed from counter capture to transmission to the control
facility. Default value is 15 seconds.
• RstCntCadaHora: Indicates whether counter values must be reset every hour (1) or not
(0). If not configured, the default value is 1.
• ValLimCnt: Counter limit value, causes it to be sent to the control facility indicating
Overflow. If not configured, the default value is 231.
• EnviaBitCY: Indicates whether, upon counter value overflow, this indication is sent to the
control facility with the carry bit CY (1) or not (0). If not configured, the default value is 1.
• MaxCapturasCont: indicates the maximum number of counter pictures (captures) to be
saved in case they are not requested or cannot be sent to the control facility. By default, it
is 1 picture.

M1CPTA2005I
1CPT: Substation Central Unit B-34
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• ModoTransmisionContadores: Indicates counter transmission mode:

- 0: ENDESA mode: Counters are sent as response to data request (class 1 or 2 as a
function of the configuration) if the protocol is UNBALANCED or spontaneously if the
protocol is BALANCED.
- 1: REE mode: Counters are sent as a response to receiving a counter interrogation
command (ASDU 101). If not configured or other than 0 or 1, the default value is 0
(ENDESA mode).
• Dir101: Address of 101 protocol counter.
• DirEq: Address of the equipment that the CPX/CPP counter belongs to.
• CON: PROCOME label of CPX/CPP counter.

Ex: 2,15,0,1,2147483648,1,1,0, // Num. Counters

20000,100,0,
20001,100,1,

• [BLQ_19] The Next Line of the Configuration File will only be Configured if the
Protocol is UNBALANCED
This will be used to configure whether the different data that can be sent to the control facility
are sent as response to a Class 1 or Class 2 data request

EI , ACT_CON_GI , GI_DATA , ACT_TERM_GI , ACT_CON_SYNC , ...

... ACT_CON_SC , ACT_TERM_SC , ACT_CON_DC , ACT_TERM_DC , ...

... ACT_CON_RC , ACT_TERM_RC , ACT_CON_SE , SP , DP , ...

... MEA_CICL , MEA_BANDA , TOMA_CICL , TOMA_ESP , ...

... CONT_CICL , ACT_CON_RST_PROC , NACK_ASDU_UNKNOWN , …

... TIPODATOCONFINTCONT , TIPODATOTERMINTCONT , …

... TIPODATOCONFTESTCOMMAND ,

• EI: Indicates if the “End of initialization” (ASDU 70) is sent as class 1(1) or class 2 (2).
Default value is 1.
• ACT_CON_GI: Indicates if the “General Interrogation” (ASDU 100) activation
confirmation (ACT_CON) is sent as class 1 (1) or class 2 (2). Default value is 2.
• GI_DATA: Indicates if data sent as response to “General Interrogation” (ASDU’s 1, 3, 5,
and/or 11) are sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_TERM_GI: Indicates if a “General Interrogation” (ASDU 100) end of activation
(ACT_TERM) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_CON_SYNC: Indicates if a “Synchronization” (ASDU 103) activation confirmation
(ACT_CON) is sent as class 1(1) or class 2 (2). Default value is 1.
• ACT_CON_SC: Indicates if the “Single Command” (ASDU 45) activation confirmation
(ACT_CON) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_TERM_SC: Indicates if the “Single Command” (ASDU 45) end of activation
(ACT_TERM) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_CON_DC: Indicates if the “Double Command” (ASDU 46) activation confirmation
(ACT_CON) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_TERM_DC: Indicates if the “Double Command” (ASDU 46) end of activation
(ACT_TERM) is sent as class 1(1) or class 2 (2). Default value is 2.

M1CPTA2005I
B-35 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

• ACT_CON_RC: Indicates if the “Regulating Step Command” (ASDU 47) activation

confirmation (ACT_CON) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_TERM_RC: Indicates if the “Regulating Step Command” (ASDU 47) end of
activation (ACT_TERM) is sent as class 1(1) or class 2 (2). Default value is 2.
• ACT_CON_SE: Indicates if the activation confirmation (ACT_CON) de un “Set Point
Command” (ASDU 49) is sent as class 1(1) or class 2 (2). Default value is 2.
• SP:Indicates if single digital changes (ASDU 30) are sent as class 1(1) or class 2 (2).
Default value is 1.
• DP: Indicates if double digital changes (ASDU 31) are sent as class 1(1) or class 2 (2).
Default value is 1.
• MEA_CICL: Indicates if cyclic analog measurements (ASDU 11) are sent as class 1(1) or
class 2 (2). Default value is 2.
• MEA_BANDA: Indicates if spontaneous analog measurements by band value (ASDU 11)
are sent as class 1(1) or class 2 (2). Default value is 2.
• TOMA_CICL: Indicates if cyclic captures (ASDU 5) are sent as class 1(1) or class 2 (2).
Default value is 2.
• TOMA_ESP: Indicates if spontaneous captures (ASDU 5) are sent as class 1(1) or class
2 (2). Default value is 2.
• CONT_CICL: Indicates if cyclic counters (ASDU 15) are sent as class 1(1) or class 2 (2).
Default value is 2.
• ACT_CON_RST_PROC: Indicates if the “Process Reset” (ASDU 105) activation
confirmation (ACT_CON) is sent as class 1 (1) or class 2 (2). Default value is 2.
• NACK_ASDU_UNKNOWN: Indicates if NACK response after an unknown ASDU request
is sent as class 1 (1) or class 2 (2). Default value is 2.
• TIPODATOCONFINTCONT: Indicates the type of counter interrogation (ASDU 101)
command activation confirmation data, namely, if it is sent as class 1 (1) or class 2 (2).
Default value is 2.
• TIPODATOTERMINTCONT: Indicates the type of counter interrogation (ASDU 101) end
of activation command data, namely, if it is sent as class 1 (1) or class 2 (2). Default
value is 2.
• TIPODATOCONFTESTCOMMAND: Indicates the type of Test Command (ASDU104)
message confirmation data, namely, if it is sent as class 1 (1) or class 2 (2). Default value
is 2.

Ex: 1,2,2,2,1,2,2,2,2,2,2,2,1,1,2,2,2,1,2,2,2,2,2,2,

M1CPTA2005I
1CPT: Substation Central Unit B-36
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Guide of some ENERSUL Profile Parameters

Configuration of Enersul profile.

Parameter Value Description

DirEnlaceLength 1 Size of Link Address field

DirAsduLength 1 Size of ASDU Address field
CotLength 1 Size of COT field
DirObjLength 2 Size of Object Address field
TipoEnlace 1 Unbalanced
DesechaCambiosSiOverflow 0
EnviaASDU70SiOV 0
CfgDco 0
NoEnviaASDU70Inicio 1
TipoPerfil 1 ENERSUL profile
MaxNumCamb 1000
EjecSimple 1 Select Before Operate
CommandActTerm 0 ACTTERM message not used
EjecDouble 1 Select Before Operate
CommandDoubleActTerm 0 ACTTERM message not used
EjecToma 1 Select Before Operate
CommandPasoActTerm 0 ACTTERM message not used
TipoASDUCambioSimple 2 Type of ASDU for Single Change
TipoASDUCambioDoble 4 Type of ASDU for Double Change
TipoASDUTomas 6 Type of ASDU for Tap Change
TipoASDUMedidas 9 Type of ASDU for Measurements

BLQ 19 1 All block parameters as Class1.

The file becomes:

[1] # Configuration of RTU CEI101B

[2] # This configuration is for TESTS
[3] 13,
[4] 0,1,0,0,0,1,
[5] 1,1,0,0,0,1,
[6] 2,1,0,0,0,1,
[7] 3,1,0,0,0,1,
[8] 4,1,0,0,0,1,
[9] 5,1,0,0,0,1,
[10] 6,1,0,0,0,1,
[11] 7,1,0,0,0,1,
[12] 8,1,0,0,0,1,
[13] 9,1,0,0,0,1,
[14] 10,1,0,0,0,1,
[15] 11,1,0,0,0,1,
[16] 12,1,0,0,0,1,

M1CPTA2005I
B-37 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[17]
[18] # Address of RTU to emulate
[19] 111,111,126,0,1,2,2,2,3 // Link address, ASDU address,
FrameMaxLenght,
[20] # Port communications parameters
[21] COM1,1200,e,8,1,1,
[22] # Time to set RTS to ON, time from RTS ON to tx (msec),
[23] # time from end of tx to set RTS to OFF (msec), Control CTS (on/off),
[24] # remote control error (sec), monitor, Command Change Time(sec),
[25] # Command Selection Time, Time between set points, RTSAlwaysON, Control
DSR
[26] 35,0,0,0,0,60,0,1,10,22,0,0,10,1,
[27] # Link Type, Number of link level retries, Timeout between
[28] # retries (msec), Maximum number of changes, NumMaxCambAntIntGen,
[29] # DesechaCambSiOV,,EnviaASDU70SiOV, CfgDco, SenalesCOTComandoRemoto,
[30] 0,0,3,3000,1000,10,1,0,1,0,0,
[31] # GestionaST,NotificaST,TimeAjusteSync,CfgTimeSinSincro,
EnviaConfSincroSiGPSOK,
[32] 1,1,-11,0,0,
[33] #
MaxCapt,Ciclo1,Ciclo2,TimeDespGI,TimeCicloDespGI,CausaReseteoEnvioCiclic
o,
[34] 1,4,12,12,0,1,
[35] # ------------------------------------------------------------
[36] [36]# OBJECT TYPE | ADDRESS RANGE
[37] # ------------------------------+------------------------------
[38] # Single Dig. St. | 00001 - 06999
[39] # Double Dig. St. | 07000 - 09999
[40] # Analog Measurements | 10000 - 19999
[41] # Tap position) | 10000 - 19999 ???
[42] # Int. Tot. Meas. (counters) | 20000 - 29999
[43] # Single commands | 33000 - 33999
[44] # Double commands | 30000 - 32999
[45] # Analog set point commands | 35000 - 39999 ???
[46] # Tap change commands | 40000 - 44999
[47] # ------------------------------+------------------------------
[48] # In this section there is a table that defines the address range
[49] # of the different types of profile objects
[50] ####################
[51] # Commands
[52] [52]2,1,1, // Num of single commands ON, Type of run,
CommandActTerm,
[53] # Association of DIR101,DIR,ISE,ISCon,ISCoff,ISCdes
[54] # it is essential to arrange DIR101
[55] # in ascending order
[56] # DIR 101 is the address of COMMAND type objects
[57] # DIR,ISE are the PROCOME address and the 7IRD command that runs the
command
[58] # ISCon is the ISC that indicates the command activation (E.g.:OPEN)
[59] # ISCoff is the ISC deactivation (E.g.:CLOSED)
[60] # ISCdes indicates (E.g.: UNKNOWN)
[61] 33000,10,1,2, 10,87, 10,93, 10,-1,
[62] 33001,10,4,2, 10,88, 10,94, 10,-1,
[63] ####################
[64] 1, // Num of single commands ON/OFF
[65] # Single ON/OFFtype commands are run through single commands
[66] # so that two single commands must be configured for each
[67] # single ON/OFF command
[68] # Association of DIR101,DIR,ISEon,ISEoff,ISCon,ISCoff,ISCdes
[69] # it is essential to arrange DIR101
[70] # in ascending order
[71] 34000,10,1,2, 4,2, 10,87, 10,88, 10,-1,
[72] ####################

M1CPTA2005I
1CPT: Substation Central Unit B-38
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[73] [73]1,1, // Num. de double commands

[74] # Double commands are run through single commands so that
[75] # two single commands must be configured
[76] # for each double command
[77] # Association of DIR101,DIR,ISEon,ISEoff,ISCon,ISCoff,ISCdes
[78] # it is essential to arrange DIR101
[79] # in ascending order
[80] 30000,10,1,2, 4,2, 10,17, 10,16, 10,-1,
[81] ####################
[82] # Tap change commands
[83] 1,1,
[84] # ADD 101,Dir,ISE (RAISE),ISE (LOWER),Measurement Nº where the TAP is
read
[85] 40000,104,4,2, 5,2, 2,
[86] ####################
[87] # Single signals
[88] 2,0,
[89] # Association of DIR101,DIR,ISC
[90] # it is essential to arrange DIR101
[91] # in ascending order
[92] 1,10,1,
[93] 2,10,2,
[94] ####################
[95] # Operating alarms
[96] 0,
[97] # Association of DIR101,DIR,ISC
[98] # it is essential to arrange DIR101
[99] # in ascending order
[100] ####################
[101] # Num. Nº Double CONTACT signals,
[102] 1,
[103] # Double contacts are calculated from single contacts
[104] # so that two ISCs must be configured
[105] # for each double contact
[106] # Association of DIR101,DIR,ISC,ISC
[107] # it is essential to arrange DIR101
[108] [108]# in ascending order
[109] # DIR 101 is the address of double CONTACT objects
[110] # DIR,ISCabierto,ISCcerrado,ISCunknown are the PROCOME addresses
[111] # and 7IRD signals
[112] # where the contact is
[113] 7000,10,16,17,18,
[114] ####################
[115] # Captures
[116]
#NumTomas,EnviaTomasACero,TiempoTomaACero,TipoASDUTomas,TomaTipoCOTCambE
spon,
[117] 1,1,10,5,12,
[118] 90000,104,2,0,1,1,
[119] ####################
[120] # NumMeasurements, TipoASDUMeasurements,
[121] 9,11,
[122] # Since the measurement values of this 101 implementation
[123] # are scaled values.
[124] # DIR 101 the address of the MEASUREMENT type objects
[125] # E.g.: 10001 is the MEASUREMENT address
[126] # DIR,MED are the PROCOME address and the number of 7IRD Measurement
[127] # VBA is the band value (amount a measurement must change to be
[128] # spontaneously sent to the control facility).
[129] [129]# VMAX maximum value of the measurement (already multiplied by the
scale factor).
[130] # VMIN is the minimum measurement value (already multiplied by the scale
factor).

M1CPTA2005I
B-39 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[131] [131]# Dir101,Dir,MEA,VBA,VMAX,VMIN,FondoEscala,Ciclo,IntGen,

[132] # In a cycle of 4 seconds
[133] 10000,10,0,10,200,0,4095,1,0,
[134] ...
[135] 10008,104,1,0,110,90,4095,1,0,
[136] ####################
[137] # Set point change commands,TipoEjec,TipoASDUConsigna,
[138] 1,1,49,1,
[139] # ADD 101,Dir,ISE (RAISE),ISE (LOWER), Nº Mea where the SET POINT,TAP is
read
[140] 35000,104,2,2, 3,2, 1, 205,
[141] # ADD 101,Dir,ISM,Nº Mea where the SET POINT is read,
[142] 35001,10,0,0,
[143] ####################
[144] # Num. Counters, Freeze time in minutes, Time from freezing
[145] # to capture for sending, ResetCadaHora, ValorLimite, EnviaBitCY
[146] 2,15,0,1,2147483648,1,1,0,
[147] # DIR 101 is the address of COUNTER type objects
[148] # DIR,CON Are the PROCOME address and the number of 7IRD COUNTER
[149] # DIR101,DIR,CON
[150] 20000,100,0,
[151] 20001,100,1,
[152] ####################
[153] # Type of data transmission (1=Class 1, 2=Class 2)
[154] # EI, ACT_CON_GI, GI_DATA, ACT_TERM_GI, ACT_CON_SYNC,
[155] # ACT_CON_SC, ACT_TERM_SC, ACT_CON_DC, ACT_TERM_DC, ACT_CON_SC,
ACT_TERM_SC,
[156] # ACT_CON_RC, ACT_TERM_RC, ACT_CON_SE, SP, DP, MEA_CICL, MEA_BANDA,
[157] # TOMA_CICL, TOMA_ESP, CONT_CICL, ACT_CON_RST_PROC, NACK_ASDU_UNKNOWN,
[158] 1,2,2,2,1,2,2,2,2,2,2,2,1,1,2,2,2,1,2,2,2,2,2,

M1CPTA2005I
1CPT: Substation Central Unit B-40
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.4 Unbalanced Type VIII: CEI101I.CFG

In this file, “cei101i.cfg”, IEC60870-5-101 unbalanced Type VIII remote control data are
configured: general data, commands (single and double), tap and set point change commands,
contact type signals (single and double), tap positions, measurements and counters. These
orders, commands, signals, measurements and counters are referenced with a IEC60870-5-101
(Dir101) address. Each of these shall be associated a command, signal, capture, measurement
or counter of the Central Unit. This profile uses the following sizes for the protocol variable
parameters:

Parameter Size Format

Dir de Enlace 2 Not structured
Dir de ASDU 2 -
Dir de Information Object 3 Not structured
Transmission Cause 1 -

This emulator is used for Coelba, Iberdrola Distribución and Iberdrola Generación (META
profile) profiles. It fully complies with the Coelba profile, while the implementation does not
comply with the latest version of Iberdrola Distribución profile, but it corresponds to versions
previous to the adoption of 104 profile.

It is not fully implemented for Iberdrola Generación (META) profile: Commands, counters or set
points are not supported.

File format is as follows:

• Configuration Data of Virtual Remote Control Equipment Signals
It will be carried out as described in section A.1: [refer to example, lines 3-5]
The two virtual Remote Control equipment signals will be configured:

- Signal 0: Indicates communications failure with the Remote Control facility.

- Signal 1: Indicates if any point of the Remote Control is blocked.

Ex: 2,
0,1,0,0,0,1,
1,1,0,0,0,1,

• Data on Central Unit (RTU) Addresses: [refer to example, line 7]

DirEnlace , DirASDU ,

• DirEnlace: Link address of the Central Unit. Default setting is 1.

• DirASDU: ASDU address of the Central Unit. Default setting is 1.

Ex: 3,10007,

M1CPTA2005I
B-41 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Port Communications: [refer to example, lines 9-

11]
NumPuertos ,
Puerto , Veloc , TipoPar , NumBits , NumStop , TamañoFIFO , (*)

(*) It repeats for each port. There will be as many ports as indicated under NumPuertos.

• NumPuertos: Number of ports to communicate with the control facility. Default setting is
2.
• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4 for
CPX relays. For CPP and CPT relays, possible values are COM1 and COM2. By default
they are configured as COM1 and COM2.
• Veloc: Baud rate. It can take the values 600, 1200, 2400, 4800, 9600 and 19200 baud.
Default setting is 9600.
• TipoPar: Type of parity. It can take the following values:
 ‘N’ or ‘n’ = None.
 ‘O’, ‘o’, ‘I’ or ‘i’ = Odd.
 ‘E’, ‘e’, ‘P’ or ‘p’ = Even.
By default, it will configured as even.
• NumBits: Number of bits. Possible values are 7 and 8 bits. Default setting is 8.
• NumStop: Number of stop bits. Possible values are 1 and 2. Default setting is 1.
• TamañoFIFO: Size of FIFO in bytes. Possible values are 1, 4, 8, 14 or 0 ( FIFO not
used). Default value is 1.

Ex: 2,
COM1,1200,e,8,1,1,
COM2,1200,e,8,1,1,

• General Data Related to Modem Line Control and Various Times used by the
Central Unit: [refer to example, line 17]
TimeCDon , TimeCDoff , TimeRTSon , TimeRTSoff , SwCTS , SwCDTx , …

... SwCDRx , RTSAlwaysOn , TimeErrTelem , TimePortNoActivo , ...

... NivelTraza , TimeCambMando , TimeSel , TimeEntreConsig , ...

... RRLResetClase2 , TimeEntreMsjTF , TimeTotalTF , MaxSegmPorSeccion , ...

... TimeVigilaEstIntermToma , PermisoSincronizar , MaxNumReintSeccion , ...

... MaxNumReintFichero , ToutChar , PerfilProtocolo , PerfilMeta ,

• TimeCDon: Timeout (in msec.) for CD ON in order for data received to be deemed good.
Default value will be 0.
• TimeCDoff: Timeout (in msec.) waiting for transmission before CD sets to OFF. If
SwCDTx is 0, it will always wait. If SwCDTx is 1 and the time for CD to OFF times out, the
transmission will be aborted. Default value will be 100.

M1CPTA2005I
1CPT: Substation Central Unit B-42
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TimeRTSon: Timeout (in msec.) to start the transfer from the time RTS sets to ON. If
SwCTS is 0, it will always wait and, when it times out, the transmission begins. If SwCTS
is 1, this is the Timeout for CTS to set to ON. If this time times out, CTS remains OFF,
and the transmission is aborted. Default value will be 100.
• TimeRTSoff: Timeout (in msec.) for RTS to set to OFF after transmission. In case
RTSAlwaysOn is 1, it always waits, but at the end of transmission RTS will not be set to
OFF. Default value will be 11.
• SwCTS: Indicates whether the CTS line is checked (1) or not (0) before transmission.
Default value will be 1.
• SwCDTx: Indicates whether the CD line is checked (1) or not (0) for transmission. If
checked, CD must be set to OFF before transmission. Default value will be 1.
• SwCDRx: Indicates whether the CD line is checked (1) or not (0) for receiving. If checked,
the CD must be set to ON for TimeCDon milliseconds to start receiving data. Default
value will be 1.
• RTSAlwaysOn: Indicates if the RTS always remains set to ON (1) or on the contrary it
sets to ON and to OFF before and after transmission respectively. Default value will be 0.
• TimeErrTelem: Timeout (in sec.) before issuing remote control communications error.
Default value will be 60.
• TimePortNoActivo: Timeout (in sec.) without receiving messages through one port to be
able to switch to the other communications port. Default setting is 10.
• NivelTraza: Trace monitoring level by the screen. The value 0 disables traces and this is
the value to be configured by default.
• TimeCambMando: Timeout (in sec.), from command completion, to label the associated
changes with non spontaneous cause. Default value will be 10.
• TimeSel: Timeout (in sec.) to automatically deselect a previously selected command. It
only has sense when commands are run with the SELECT AND EXECUTE method.
Default value is 10 seconds.
• TimeEntreConsig: Timeout (in msec) between two consecutive set point commands.
Default value is de 22 milliseconds.
• RRLResetClase2: Indicates if, after receiving a Reset Remote Link, class 2 data queues
must be reset (1) or not (0). Default setting is 1.
• TimeEntreMsjTF (for Iberdrola profile only): Timeout (in sec.) between file transfer
messages to abort the transfer. Default setting is 60.
• TimeTotalTF (for Iberdrola profile only): Timeout (in sec.) to abort a file transfer. Default
setting is 300.
• MaxSegmPorSeccion (for Iberdrola profile only): Maximum number of segments of each
section that will be sent in the file transfer. Default setting is 10.
• TimeVigilaEstIntermToma: Timeout (in sec.) for the Central Unit to monitor the
intermediate status of a capture (wrong value, namely, no capture or simultaneous
capture). When this times out with the capture to wrong value, it will be sent as invalid to
the control facility. If not configured, the default value is 10 seconds.
• PermisoSincronizar: Indicates if the control facility is (1) or is not (0) enabled to
synchronize the Central Unit. Only one of those control facilities which will interrogate the
Central Unit may have this parameter set to 1. The rest of them will have it set to 0. If
more than one protocol is configured as possible synchronization source, the protocol
which started first in the Central Unit will be the only one to enable the corresponding
control facility synchronize the Central Unit. Default setting is 1.
• MaxNumReintSeccion (for Iberdrola profile only): Maximum number of section send
retries to abort file transfer. They are retries, therefore one section will be sent
“MaxNumReintSeccion” + 1 times. The range is 1..100. If not configured, the default
value is 2 retries.

M1CPTA2005I
B-43 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• MaxNumReintFichero (for Iberdrola profile only): Maximum number of file send retries to
abort file transfer. They are retries, therefore one file will be sent “MaxNumReintFichero”
+ 1 times. The range is 1..100. If not configured, the default value is 2 retries.
• ToutChar: Timeout between characters to reject a frame. If configured to 0, the timeout
between characters will be the one calculated internally by the Central Unit, adapted to
each baud rate. If not configured, the default value is 0.
• PerfilProtocolo: Indicates the protocol profile to be emulated: 0 (Iberdrola) or 1 (Coelba).
If not configured, the default value is 0 (Iberdrola).
• PerfilMeta: Indicates if the protocol profile to be emulated is Distribución de Iberdrola (0)
or generation, META profile, (1). Default value is 0 (Distribución)

These two last settings must be configured adequately as a function of whether it is

Coelba, Iberdrola Distribución or Iberdrola Generación profile. Adequate combinations
are.

PerfilProtocolo PerfilMeta
Coelba 1 0
Iberdrola Distribución 0 0
Iberdrola Generación (META) 0 1

Ex:
0,500,500,11,1,1,1,0,60,5,0,10,10,22,0,60,2100,5,10,1,2,2,0,0,0,

• Data on the Size of the Different Data Queues: [refer to example, line 19]
TamColaClase1 , TamColaClase2 , TamColaComandos , TamColaÓrdenes ,

• TamColaClase1: Size of class 1 data queue. Once class 1 data number has been
attained, a queue overflow will occur and data will not be stored until an application Reset
is received. It will be configured by default as 1000.
• TamColaClase2: Size of each of class 2 data queues. Once the number of class 2 data
has been attained, data will not be stored until there is space in the queue for more data.
It will be configured by default as 1000.
• TamColaCommands: Size of the command queue. This is the maximum number of
nonprocessed commands (data requests) that the Central Unit can store. It will be
configured by default as 10.
• TamColaÓrdenes: Size of the command queue. It is the maximum number of commands
pending confirmation that the Central Unit is capable of processing. By default, it will be
configured as 3.

Ex: 1000,1000,10,3,

M1CPTA2005I
1CPT: Substation Central Unit B-44
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Time Synchronizing Configuration Data: [refer to example, line 22]

GestionaST , NotificaST , TimeAjuste , Fuente , TimeSincro , TimeSincro , ...
Sincro Sincro KO OK

... DiffTimeParaLanzar ,
SincroSNTP

• GestionaST: Indicates if the control facility sends the updated date and hour with
summer/winter time change (1) or not (0). Default value is 1.
• NotificaST: Indicates if the control facility sends the ST bit, indicating the summer/winter
time (1), or not (0). Default value is 1.
• TimeAjusteSincro: Timeout (in msec) to adjust the time synchronization to compensate
for possible clock drift, channel delays, etc. Default value, 0.
• FuenteSincro (CPX/CPP-A relays only): Indicates the default synchronizing source:
0=Protocol, 1=External clock. Default setting is 0.
• TimeSincroKO (CPX/CPP-A relays only): Timeout (in sec.) without receiving
synchronizations to deem the Central Unit NOT synchronized. Default setting is 2100.
• TimeSincroOK (CPX/CPP-A relays only): Timeout (in sec.) receiving correct
synchronizations from the external clock to deem the Central Unit synchronized. Default
setting is 3.
• DiffTimeParaLanzarSincroSNTP: Time difference (in msec.) between the time received
by protocol and the internal time of the Central Unit, under which a multicast/broadcast
SNTP synchronization is not sent when the Central Unit is synchronized by control
facility. This parameter has meaning only if the Central Unit is configured as SNTP
server. If not configured, the default value is 0.

Ex: 1,1,0,0,2100,5,0,

• Configuration Data of Remote Control Single Commands

Each remote control single command is associated to a Central Unit command. It is essential
to put Dir101s in ascending order: [refer to example, lines 41-45]

NumOrdenes , Ejec , OrdenConmutaFteSincro ,

Dir101 , DirEq , ISE , DCO , DirEqOn , ISCon , ...

... DirEqOff , ISCoff , DirEqDes , ISCdes , ... (*)

... TimeEsp ,
InfoRetorno

(*) It repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control single commands.

• Ejec: Indicates if these single commands are being run through the DIRECT EXECUTE
(0) (default value) or SELECT AND EXECUTE (1) method. Default value is 0.
• OrdenConmutaFteSincro (for Iberdrola profile only): Address of the IEC-101 command
protocol used to switch the synchronizing source. Default address is 62501.
• Dir101: Address of the single command within protocol IEC-101.

M1CPTA2005I
B-45 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DirEq: Address of the equipment (CPU) that the command belongs to within the Central
Unit database.
• ISE: Central Unit command identifier.
• DCO: DCO with which the ISE command of the DirEq equipment will be run. Default
value will be 2.
• DirEqOn: Address of the equipment (CPU) that the ISCon digital signal belongs to within
the Central Unit database.
• ISCon: Digital signal identifier that indicates the command activation. If this signal is not
to be used, it will be configured in this field with the value –1.
• DirEqOff: Address of the equipment (CPU) that the ISCoff digital signal belongs to within
the Central Unit database.
• ISCoff: Digital signal identifier that indicates the command deactivation. If this signal is
not to be used, this field will be configured as –1.
• DirEqDes: Address of the equipment (CPU) that the ISCdes digital signal belongs to
within the Central Unit database.
• ISCdes: Digital signal identifier that indicates lack of information on the status of the
command. If this signal is not to be used, this field will be configured as –1.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the
associated changes (signals On, Off and Des) with non spontaneous cause. If not
configured, the default value is “TimeCambMando”.

Ex: 3,0,62501,
30001,22,12,2,22,0,22,1,22,9,5,
30251,12,0,2,12,78,12,76,12,9,10,
30252,12,1,2,12,79,12,77,12,9,15,

• Configuration Data of Remote Control Double Commands

Two commands from the Central Unit are associated to two commands from the Central Unit. It
is essential to put Dir101s in ascending order: [see example, lines 50-55]

NumOrdenes , Ejec ,
Dir101 , DirEq , ISEon , DCOon , ISEoff , DCOoff , ...

... DirEqOn , ISCon , DirEqOff , ISCoff , DirEqDes , ISCdes , ... (*)

... TimeEsp ,
InfoRetorno

Each remote control double command is associated to two Central Unit commands. It is
essential to put Dir101s in ascending order: [refer to example, lines 50-55]

• NumOrdenes: Number of remote control double commands.

• Ejec: Indicates if the double commands are being run with DIRECT EXECUTE (0)
(default value) or SELECT AND EXECUTE (1) method. Default value is 0.
• Dir101: Address of the double command within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the commands to be associated to the
double command belong to, within the Central Unit database.
• ISEon: Central Unit command identifier corresponding to double command activation.
• DCOon: DCO with which the ISEon command of DirEq equipment (double command
activation) will be run. Default value will be 2.

M1CPTA2005I
1CPT: Substation Central Unit B-46
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• ISEoff: Central Unit command identifier corresponding to double command deactivation.

• DCOoff: DCO with which the ISEoff command of DirEq equipment (double command
deactivation) will be run. Default value will be 2.
• DirEqOn: Address of the equipment (CPU) that the ISCon digital signal belongs to within
the Central Unit database.
• ISCon: Digital signal identifier that indicates the double command activation (ISEon
command activation). If this signal is not to be used, this field will be configured as –1.
• DirEqOff: Address of the equipment (CPU) that the ISCoff digital signal belongs to, within
the Central Unit database.
• ISCoff: Digital signal identifier that indicates the double command deactivation (ISEoff
command activation). If this signal is not to be used, this field will be configured as –1.
• DirEqDes: Address of the equipment (CPU) that ISCdes digital signal belongs to, within
the Central Unit database.
• ISCdes: Digital signal identifier that indicates lack of information on the status of the
double command. If this signal is not to be used, this field will be configured as –1.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the
associated changes (signals On, Off and Des) with non spontaneous cause. If not
configured, the default setting is “TimeCambMando”.

Ex: 3,0,
35001,12,0,2,1,2,12,80,12,0,12,4,5,
35002,12,6,2,7,2,12,81,12,0,12,4,10,
35003,12,8,2,9,2,12,82,12,0,12,4,15,

• Configuration Data of Tap Change Commands

Each remote control tap change command is associated to two Central Unit commands (raise
and lower the tap) and one measurement from which the tap is read. It is essential to put
Dir101s in ascending order: [refer to example, lines 60-63]

NumComandos , Ejec ,
Dir101 , DirEq , ISEsubir , DCOsubir , ...

... ISEbajar , DCObajar , MEA , ... (*)

... TimeEsp ,
InfoRetorno

(*) This repeats for each remote control tap change command. There will be as many as
indicated under NumCommands. They will be arranged in ascending order of Dir101.

• NumCommands: Number of remote control tap change commands.

• Ejec: Indicates if the tap change commands are being run using DIRECT EXECUTE (0)
(default value) or SELECT AND EXECUTE (1). Default value is 0.
• Dir101: Address of command within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that Central Unit commands and measurement
belong to.
• ISEsubir: Central Unit command identifier to raise the tap.

M1CPTA2005I
B-47 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DCOsubir: DCO with which the ISEsubir command of DirEq equipment (to raise the tap)
will be run. Default value will be 2.
• ISEbajar: Central Unit command identifier to lower the tap.
• DCObajar DCO with which the ISEbajar command of DirEq equipment (to lower the tap)
will be run. Default value will be 2.
• MEA: Measurement identifier of the Central Unit where the tap is read.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the first tap
change with non spontaneous cause. If not configured, the default setting is
“TimeCambMando”.

Ex: 2,0,
45001,17,4,2,5,2,1,15,
45002,21,4,2,5,2,1,20,

• Configuration Data of Set Point Change Commands

There are two types of set point commands:

- Set point command by raise/lower the set point control function: after receiving a set
point change command, the Central Unit starts a control function to find out the number of
times to raise/lower the set point value to reach the desired value. This mode will be
applied for commands on CPUs that do not allow direct set point commands (only allow
raise/lower set point commands). Each set point command by control function is
associated two commands (raise and lower set point) and a measurement where the set
point can be read.
- Direct set point command: a direct command is run upon the CPU in order to set the set
point to a value. Each direct set point command is associated an analog output write in
order to write the set point value to the CPU and a measurement where the set point can
be read.

It is essential to put Dir101s in ascending order: [refer to example, lines 68-74]

NumComandos , Ejec , TipoASDU , NumComandos ,

Autom Direct
Dir101A , DirEqA , ISEsubir , DCOsubir , ...

... ISEbajar , DCObajar , MedA , Paso , ... (*)

... TimeEsp ,
InfoRetornoA

Dir101D , DirEqD , ISM , MedD , ...

(**)
... TimeEsp ,
InfoRetornoD

(*) It repeats for each set point command by raise/lower the set point control function. There
will be as many as indicated under NumCommandsAutom. They will be arranged in ascending
order of Dir101.
(**) It repeats for each direct set point command. There will be as many as indicated under
NumCommandsDirect. They will be arranged in ascending order of Dir101.

M1CPTA2005I
1CPT: Substation Central Unit B-48
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumCommandsAutom: Number of remote control set point change commands by

raise/lower the set point control function.
• Ejec: Indicates if the set point change commands are being run using DIRECT EXECUTE
(0) (default value) or SELECT AND EXECUTE (1). Default value is 0.
• TipoASDU: Indicates the type of ASDU used for remote control set point commands.
Possible values are: 48 (standard) and 50 (in floating point). If not configured, the default
value is 48 (standard).
IMPORTANT: If there are configured set points (whether by control function and/or direct)
and are floating point (TipoASDU=50), measurements cannot be standard (ASDU 9),
since the UCS will issue an error and the remote control will not start, as the
measurement full scale is needed to scale the set point.
• NumCommandsDirect: Number of remote control direct set point change commands. If
not configured, the default value is 0.
• Dir101A: Address of the command by control function within protocol IEC-101.
• DirEqA: Address of the equipment (CPU) that the Central Unit commands and
measurement belong to.
• ISEsubir: I Central Unit command identifier to raise the set point.
• DCOsubir: DCO with which the ISEsubir command of DirEq equipment (to raise the set
point) is run. Default value will be 2.
• ISEbajar: Central Unit command identifier to lower the set point.
• DCObajar: DCO with which the ISEbajar command of DirEq equipment (to lower the set
point) is run. Default value will be 2.
• MedA: Measurement identifier of the Central Unit where the set point is read.
IMPORTANT: If set points are not standard (TipoASDU other than 48) or MedA
measurement is floating format (refer to FormatoMed parameter in “DBASE.CFG”), this
measurement must be configured in the measurements section (Configuration data of
remote control measurements) in order to know the full scale and correction factors
and so be able to scale the set point. If the measurement is not configured, the UCS will
issue an error and the remote control will not start.
• Paso: Allows calculating the number of times the raise or lower the set point command
must be run to reach the required set point value, as follows:

| Current_Value-Required_Value |
Number of command runs = --------------------------------------------------
Paso
Default value is 205.
• TimeEspInfoRetornoA: Timeout (in sec.) for the set point to reach the value requested
from the control facility. When this time times out, if the value is not reached, a failed
command completion will be reported to the control facility. If not configured, the default
value is 127.
• Dir101D: Address of the direct command within protocol IEC-101.
• DirEqD: Address of the equipment (CPU) the analog output write belongs to and the
measurement in the Central Unit database.
• ISM: Analog output write identifier of the Central Unit to write the set point value to the
CPU.
• MedD: Measurement identifier of the Central Unit where the set point is read.
IMPORTANT: If set points are not standard (TipoASDU other than 48) or MedA
measurement is floating format (refer to FormatoMed parameter in “DBASE.CFG”), this
measurement must be configured in the measurements section (Configuration data of
remote control measurements) in order to know the full scale and correction factors
and so be able to scale the set point. If the measurement is not configured, the UCS will
issue an error and the remote control will not start.

M1CPTA2005I
B-49 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TimeEspInfoRetornoD: Timeout (in sec.) to receive the command completion from the
CPU. When this time times out, if the command completion is not received from the CPU,
a failed command completion will be reported to the control facility. If not configured, the
default value is 127.

Ex: 2,0,50,2,
40001,17,2,2,3,2,0,205,30,
40001,21,2,2,3,2,0,205,35,
40001,10,0,0,5,
40002,11,0,0,10,

• Configuration Data of Remote Control Single Contact Signals

Each remote control signal of this type is associated a Central Unit digital signal. It is essential
to put Dir101s in ascending order: [refer to example, lines 86-90]

NumSD , DirSeñOverflow , X% , Y% , TimeCambioPeriodico ,

Dir101 , DirEq , ISC , Neg , (*)

(*) It repeats for each remote control single contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control single contact signals (excluding system information
signals).
• DirSeñOverflow: Address of the signal that indicates that class 1 queue is totally full (it
will be configured with the value 60001). The rest of system information signals will be
consecutive :
 60002: Queue X% full (half full) signal .
 60003: File transfer active signal.
 60004: Periodic and spontaneous change signal.
 60005: Central Unit (RTU) synchronized signal.
 60006: Synchronizing source signal.
NOTE: For Coelba profile, there only exist system signals 60001 and 60002.

• X%:% at which class 1 queue X% full signal is generated. For Iberdrola profile, if wrongly
configured (valid limits are 20% to 95%) the default value (70%) will be taken.
• Y%: % at which class 1 queue X% full (near empty) signal is generated. For Iberdrola
profile, if wrongly configured (valid limits are 0% to 80%) the default value (30%) will be
taken.
• TimeCambioPeriodico (for Iberdrola profile only): Indicates how often (in seconds) the
periodic and spontaneous change 60004 is generated. Default setting is 0.
• Dir101: Address of the single contact digital signal within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the associated digital signal belongs to,
within the Central Unit database.
• ISC: Central Unit digital signal identifier.
• Neg: Indicates if the digital signal is negated (1) or not (0) to send it to the control facility.
If not configured, the default value is 0.

Ex: 3,60001,70,30,1440,
1,10,0,0,
2,10,1,0,
3,10,2,0,

M1CPTA2005I
1CPT: Substation Central Unit B-50
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Double Contact Signals

Each remote control signal of this type is associated three Central Unit digital signals. It is
essential to put Dir101s in ascending order: [refer to example, lines 95-99]

NumSD ,
Dir101 , DirEq , ISCabierto , ISCcerrado , ISCunknown , Neg , (*)

(*) It repeats for each remote control double contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control double contact signals.

• Dir101: Address of the double contact signal within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the associated digital signals belong to,
within the Central Unit database.
• ISCabierto: Central Unit digital signal identifier that indicates double contact signal open
status. If this signal is not used, it will be configured with the value –1.
• ISCcerrado: Central Unit digital signal identifier that indicates double contact signal
closed status. If this signal is not used, it will be configured with the value –1.
• ISCunknown: Central Unit digital signal identifier that indicates double contact signal
unknown status. If this signal is not used, it will be configured with the value –1.
• Neg: Indicates if the double signal is negated (1) or not (0) to send it to the control facility.
If not configured, the default value is 0.

Ex: 3,
10001,22,10,11,-1,0,
10002,22,12,13,0,0,
10003,22,14,15,0,0,

• Configuration Data of Remote Control Taps

Each remote control tap is associated a Central Unit measurement. It is essential to put
Dir101s in ascending order: [refer to example, lines 104-107]

NumTomas ,
Dir101 , DirEq , MEA , UCSVigilaE , UsaValor , Value , (*)
stInterm TomaErronea TomaErronea

(*) It repeats for each remote control tap. There will be as many as indicated under
NumTomas. They will be arranged in ascending order of Dir101.

• NumTomas: Number of remote control taps.

• Dir101: Address of the tap within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the associated measurement belongs to,
within the Central Unit database.
• MEA: Central Unit measurement identifier.
• UCSVigilaEstInterm: Indicates if the Central Unit must monitor the intermediate status of
the tap (1) or not (0). If not configured, the default value is 1. For CPUs that manage the
intermediate status of the tap (i.e. IEC61850) this parameter is configured to 0. When the
Central Unit monitors the intermediate status, it will use “TimeVigilaEstIntermToma” as
monitoring time.

M1CPTA2005I
B-51 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• UsaValorTomaErronea: Indicates if the CPU uses “ValorTomaErronea” as wrong tap

value (no tap or simultaneous tap) (1) or instead, this value is not used and the last
known value with flag IV=1 is used as wrong tap value (0). If not configured, the default
value is 1, for compatibility with ZIV’s RTN regulator. For IEC61850 CPUs this parameter
is configured to 0.
• ValorTomaErronea: Value sent by the CPU when the tap is wrong (no tap or
simultaneous tap). It is only used when the previous parameter “UsaValorTomaErronea”
is 1. If not configured, the default value is 0, for compatibility with ZIV’s RTN regulator.
For IEC61850 CPUs this parameter is configured to 0.

Ex: 2,
20001,17,1,0,0,0,// RTV IEC61850
20002,21,1,1,1,0,// RTN PROCOME

• Configuration Data of Remote Control Measurements

Each remote control measurement is associated a Central Unit measurement. It is essential to
put Dir101s in ascending order. Measurement values in this protocol implementation can be
standard (ASDU 9) or floating point (ASDU 13): [refer to example, lines 112-118]

NumMedidas , TimeCapturasMedidas , TipoASDU , PorcentajeOverflow ,

Dir101 , Dir , Medida , Corr , Offset , Ope1 , Ope2 , ...

... Ope3 , Ope4 , Ope5 , Ope6 , VBA , PBA , ...

... LINF , LISUP , VMAX , VMIN , FondoEscalaSup , ...

... FondoEscalaInf , UCSGestionaOverflow , (*)

(*) This repeats for each remote control measurement. There will be as many as indicated
under NumMeasurements.

• NumMedidas: Number of remote control measurements.

• TimeCapturasMedidas: Timeout (in sec.) to explore measurements. If not configured, the
default value is 1.
• TipoASDU: Indicates the ASDU with which measurements are sent. Possible values are
9 (standard) or 13 (floating point). If not configured, the default value is 9. IMPORTANT: If
these measurements are standard (TipoASDU=9) and there are configured set points
(whether by control function and/or direct) and they are floating point (ASDU 50) the UCS
will issue an error and the remote control will not start, since measurement full scales are
needed to scale the set point.
• PorcentajeOverflow: Rate per unit of the full scale to indicate overflow. It is only used for
measurement overflows managed by the Central Unit ( “UCSGestionaOverflow” to 1). If
not configured, the default value is 4090/4095. For CPUs that manage measurement
overflow (i.e. IEC61850), this value must be configured to 1.0.
• Dir101: Address of the measurement within protocol IEC-101.
• Dir: Address of the equipment (CPU) that the measurement in the Central Unit database
belongs to.
• Medida: Central Unit measurement identifier.
• Corr: Correction factor that enables the conversion of Central Unit database
measurement values into IEC-101 measurement values. Default value is 1.0.

M1CPTA2005I
1CPT: Substation Central Unit B-52
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Offset: Offset that allows to convert Central Unit database measurement values into IEC-
101 measurement values. Default value is 0.0.

Value_Measurement_101 = Value_Measurement_BD_UCS * Corr + Offset

• Ope1: VBA parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 1.
• Ope2: PBA parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• Ope3: LINF parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• Ope4: LISUP parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to
0.
• Ope5: VMAX parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to
0.
• Ope6: VMIN parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• VBA: Band Value, indicates the minimum variation between two measurement values in
order for the new value to be sent to the control facility. It is configured in rate per unit (1
= 100%).
Iberdrola default values are:
- 0.1%: For voltage measurement (V), LV (VOLT).
- 0.2%: For active power (P), reactive power (Q), temperature (T), distance-to-fault
(DFAL) measurements.
- 0.8%: For current measurements (I).
- 2%: For set point voltage measurements (VCON).
• PBA: Band Period, is the timeout to deem the measurement valid for transmission (not
used).
• LINF: Low Limit, is the value below which the alarm status occurs (not used).
• LISUP: High Limit, is the value above which the alarm status occurs (not used).
• VMAX: Maximum Value, is the engineering value of the maximum value that the user
sensor can deliver to the capture card (not used).
• VMIN: Minimum Value is the engineering value of the minimum value that the user
sensor can deliver to the capture card (not used).
• FondoEscalaSup: Upper equipment measurement full scale. Default value is 4095 for
16bit measurements 32767 for float measurements.
Values to be configured for:
- PROCOME: 4095.
- DNP3: 32767.
- IEC61850: Maximum measurement value (“rangeC$max” attribute) (i.e. 7 A, 132
kV..).
• FondoEscalaInf: Lower equipment measurement full scale. If not configured, the default
value is 0.
Values to be configured for:
- PROCOME: 0 (for single pole measurement) or –4095 (for bipolar measurement).
- DNP3: 0 (for single pole measurement) or –32767 (for bipolar measurement).
- IEC61850: Minimum measurement value (“rangeC$min” attribute) (i.e. 0 A, -132
kV..).
IMPORTANT: FondoEscalaSup must be greater than FondoEscalaInf. If this is not
configured this way, the UCS will issue an error and the remote control will not start.

M1CPTA2005I
B-53 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• UCSGestionaOverflow: Indicates whether the measurement overflow is managed by the

Central Unit (1) or the CPU (0) If not configured, the default value is 1 for compatibility
with our PROCOME CPUs. For CPUs that manage measurement overflows (i.e.
IEC61850) this parameter will be configured to 0.

This protocol implementation only uses the VBA (band value) parameter. The Corr and Offset
factors will be used for example to convert to floating point (ASDU 13) 16 bit whole
measurements (i.e. PROCOME accounts ):

- Ex: If a PROCOME measurement measures 0 to 7 amp (single pole measurement), the

units [0 to 4095] must be scaled to floating point format. For this, calculations are as
follows:

Corr = ABS(Vmax – Vmin) / (fesup – feinf) = ABS(7 – 0) / (4095 – 0) = 0.00171.

Offset = Vmin = 0

Since Value_Measurement_101 = (Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 0 A.

Value_Measurement_BD_UCS = 1024 units  Value_Measurement_101 = 1,75 A.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 3,5 A.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 7 A.

- Ej: If a PROCOME measurement measures 80 to 120 amp (single pole

measurement), the units [0 to 4095] must be scaled to floating point format. For this,
calculations are as follows:

Corr = ABS(Vmax – Vmin) / (fesup – feinf) = ABS(120 – 80) / (4095 – 0) = 0.00976801.

Offset = Vmin = 80

Since Value_Measurement_101 = (Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 80 kV.

Value_Measurement_BD_UCS = 1024 units  Value_Measurement_101 = 90 kV.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 100 kV.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 120 kV.

- Ej: If a PROCOME measurement measures -132 to 132 kV (single pole

measurement), the units [-4095 to 4095] must be scaled to floating point format. For
this, calculations are as follows:

Corr = MAX[ABS(Vmax ),ABS(Vmin)] / (fesup) = 132 / 4095 = 0.032234

Offset = 0

Since Value_Measurement_101 = ( Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = -4095 units Value_Measurement_101 = -132 kV.

Value_Measurement_BD_UCS = -2048 units  Value_Measurement_101 = -66 kV.
Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 0 kV.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 66 kV.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 132 kV.

M1CPTA2005I
1CPT: Substation Central Unit B-54
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

However, in case (ASDU 9) measurements must be standardized to floating point (i.e.

IEC61850), Corr and Offset are automatically calculated by the Central Unit (namely, the
values configured in the file for these parameters will be ignored), using the following criterion
agreed upon with Iberdrola:

- If the measurement is single pole, namely ABS(FondoEscalaSup) is other than

ABS(FondoEscalaInf) (asymmetric measurement), this floating point measurement will be
scaled between the standard values 0 and 32767.
- If the measurement is bipolar, namely ABS(FondoEscalaSup) is equal to
ABS(FondoEscalaInf) (symmetric measurement), this floating point measurement will be
scaled between the standard values -32767 and 32767.

Ex: 4,2,13,1.0,
15001,22,0,0.009768,80.0,1,0,0,0,0,0,0.02,0,0,0,0,0,4095,0,0,
15002,23,1,0.032234,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,4095,-4095,0,
15005,24,2,1.0,0.0,1,0,0,0,0,0,0.008,0,0,0,0,0,7.0,0.0,0,
15006,25,3,1.0,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,132.0,-132.0,0,

• Configuration Data of Remote Control Counters

Each remote control counter is associated a Central Unit counter. It is essential to put Dir101s
in ascending order: [refer to example, lines 123-128]

NumConts , TimeCaptEspontanea , TimeCaptHist , MinutoIniCapt , bCapturaInicial ,

Dir101 , DirEq , CON , (*)

(*) This repeats for each remote control counter. There will be as many as indicated under
NumConts. They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• TimeCaptEspontanea: Timeout (in min) of counter capture for spontaneous transfer. If
configured to 0, no counters will be sent spontaneously. Default value is 60 minutes.
• TimeCaptHist: Timeout (in min) of counter capture for counter history. if configured to 0,
no counter history will exist. Default value is 60 minutes.
• MinutoIniCapt: Minute of the hour when counters begin being captured. If not configured,
the default value is 1.
• bCapturaInicial: Indicates if the Central Unit sets an initial counter capture to (1) or not (0)
with all the counters to invalid. If not configured, the default value is 1. For Central Units
with IEC61850 CPUs, this parameter must be configured to 0, whereas for the rest of
Central Units (i.e. PROCOME, DNP3...) it must be configured to 1.
• Dir101: Address of the counter within protocol IEC-101.
• DirEq: Address of the equipment that the counter within the Central Unit database
belongs to.
• CON: Central Unit counter identifier.

Ex: 4,60,60,1,1,
25001,22,0,
25002,22,1,
25003,22,2,
25004,22,3,

M1CPTA2005I
B-55 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of IOA (Information Object Address) Ranges of the

Different Remote Control Points
Each remote control point is assigned a 101 address, IOA (Information Object Address). The
initial IOAs of the range corresponding to each different point (single, double signals,
measurements, taps, counters, commands...) will be configured in this point [refer to example,
line 134]

IOAIniEstSim , IOAIniEstSist , IOAIniEstDob , IOAIniMed , IOAIniTom , ...

... IOAIniCont , IOAIniOrdSim , IOAIniOrdDob , IOAIniOrdConsig , IOAIniOrdPaso ,

• IOAIniEstSim: Initial IOA for single signals. If not configured, the default value is 1.
• IOAIniEstSist: Initial IOA for system signals. If not configured, the default value is 60001.
• IOAIniEstDob: Initial IOA for double signals. If not configured, the default value is 10001.
• IOAIniMed: Initial IOA for analog measurements. If not configured, the default value is
15001.
• IOAIniTom: Initial IOA for taps. If not configured, the default value is 20001.
• IOAIniCont: Initial IOA for counters. If not configured, the default value is 25001.
• IOAIniOrdSim: Initial IOA for single commands. If not configured, the default value is
30001.
• IOAIniOrdDob: Initial IOA for double commands. If not configured, the default value is
35001.
• IOAIniOrdConsig: Initial IOA for set point change commands. If not configured, the default
value is 40001.
• IOAIniOrdPaso: Initial IOA for tap change commands. If not configured, the default value
is 45001.

Ej: 1,60001,10001,15001,20001,25001,30001,35001,40001,45001,

• Management Data for Activation/Deactivation of Signals Resulting From

Excessive Number of Changes
Data for the remote control to activate/deactivate signals resulting from excessive number of
changes are configured here. Since management can be carried out in CPUs (i.e. as is the case
for IEC61850), Central Unit kernel and remote control module, consideration must be given in
each case as from where the management should and should not be activated [refer to
example, line 140]

NCambDesact , NCambAct , TimeActDesact ,

• NCambDesact: Number of changes to deactivate a signal. To deactivate the managing

function for signal activation / deactivation in the remote control module, this parameter
will be configured to 0. If not configured, the default value is 0.
• NCambAct: Number of changes to activate a signal. If not configured, the default value is
0.
• TimeActDesact: Control period (in sec.) of the number of changes. If not configured, the
default value is 10.

M1CPTA2005I
1CPT: Substation Central Unit B-56
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Operation of signal activation/deactivation management:

- A signal deactivates when “NCambDesact” or more changes are produced in

“TimeActDesact” seconds. (NOTE: “NCambDesact” = 0, implies the function is
deactivated and, therefore, no signal will ever be deactivated).
- A deactivated signal activates again when no more than “NCambAct” changes are
produced in “TimeActDesact” seconds provided the number of changes is less than
“NCambDesact”.

Ex: 0,0,10,

The file becomes:

[1] # Configuration of RTU CEI101I Unbalanced (IBERDROLA)

[2] # Signal of communications failure with the control facility.
[3] 2,
[4] 0,1,0,0,0,1,
[5] 1,1,0,0,0,1,
[6] # Link address, ASDU address,
[7] 3,10007,
[8] # Port communications parameters
[9] 2,
[10] COM1,1200,e,8,1,1,
[11] COM2,1200,e,8,1,1,
[12] # TimeCDon,TimeCDoff,TimeRTSon,TimeRTSoff,SwCTS,SwCDTx,SwCDRx,
[13] # RTSAlwaysOn, TimeErrorTelem,TimePortNoActivo,NivelTraza,
[14] # TimeoutCambiosCommands(s),TimeoutSeleccion(s),TimeEntreConsignas(s),
[15] # RRLResetClase2,ToutEntreMsjTF(s),ToutTotalTF(s),MaxNumsecmPorSeccion,
[16] #TimeTomaACero,PermisoSincro,MaxReintSecc,MaxReintFich,ToutChar,PerfilPro
toc,
[1]0,500,500,11,1,1,1,0,60,5,0,10,10,22,0,60,2100,5,10,1,2,2,0,0,

[17] # TamColaClase1,TamColaClase2,TamColaComandos,TamColaOrdenes,
[18] 1000,1000,10,3,
[19] # CCGestionaST,CCNotificaST,AjusteSync,FuenteSincro(0=Proto,1=GPS),
[20] # TimeSincroKO(seg),TimeSincroOK(seg),DiffTimeParaLanzarSincroSNTP,
[21] 1,1,0,0,2100,5,0,
[22] # ------------------------------------------------------------
[23] # TYPE OF OBJECT | RANGE OF ADDRESSES
[24] # ------------------------------+------------------------------
[25] # Simple Dig. St. | 00001 – 10000
[26] # Double Dig. St. | 10001 – 15000
[27] # Analogical Measurements | 15001 – 20000
[28] # Collection position (taps) | 20001 – 25000
[29] # Int. Tot. Measure. (meters) | 25001 – 30000
[30] # Simple orders | 30001 – 35000
[31] # Double orders | 35001 – 40000
[32] # Analogical set point | 40001 – 45000
[33] # Collect. Reg. Commands (taps) | 45001 – 50000
[34] # System Information | 60001 - 65535
[35] # ------------------------------+------------------------------
[36] ###############################################
[37] # SIMPLE COMMANDS (ON=Pulse, OFF=Pulse) #
[38] ###############################################
[39] # NumOrdenes,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),OrdenConmutaFteSincro,
[40] 3,0,62501,

M1CPTA2005I
B-57 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[41] #
Add101,DIR,ISE,DCO,DIRon,ISCon,DIRoff,ISCoff,DIRdesc,ISCdesc,TimeEspInfo
Ret,
[42] 30001,22,12,2,22,0,22,1,22,9,5,
[43] 30251,12,0,2,12,78,12,76,12,9,10,
[44] 30252,12,1,2,12,79,12,77,12,9,15,
[45] ###################
[46] # COMANDOS DOBLES #
[47] ###################
[48] # NumOrdenes,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),
[49] 3,0,
[50] # Add101,DIR,ISEon,DCOon,ISEoff,DCOoff,DIRon,ISCon,DIRoff,ISCoff,
[51] # DIRdesc,ISCdesc,TimeEspInfoRet,
[52] 35001,12,0,2,1,2,12,80,12,0,12,4,5,
[53] 35002,12,6,2,7,2,12,81,12,0,12,4,10,
[54] 35003,12,8,2,9,2,12,82,12,0,12,4,15,
[55] ###################################
[56] # COMANDOS DE REGULACION DE TOMAS #
[57] ###################################
[58] # NumComandos,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),
[59] 2,0,
[60] # Add101,Dir,ISESubir,DCOsubir,ISEBajar,DCObajar,MEAToma,TimeEspInfoRet,
[61] 45001,17,4,2,5,2,1,15,
[62] 45002,21,4,2,5,2,1,20,
[63] ######################################
[64] # SET POINT REGULATION COMMANDS #
[65] ######################################
[66] #
NumComandosAutom,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),ASDU,NumComandosDir
ect,
[67] 2,0,50,2,
[68] #
Add101,DIR,ISESubir,DCOsubir,ISEBajar,DCObajar,MEAConsigna,Paso,TimeEspI
nfRet,
[69] 40001,17,2,2,3,2,0,205,30,
[70] 40002,21,2,2,3,2,0,205,35,
[71] # Add101,DIR,ISM,MEAConsigna,TimeEspInfRet,
[72] 40003,10,0,0,5,
[73] 40004,11,0,0,10,
[74] ###################
[75] # SIMPLE SIGNALS #
[76] ###################
[77] # Note: The address of the Overflow signal is 60001. After this signal
[78] # the rest of the info. Signals come from the system:
[79] # 60002 -> Queue full to x%.
[80] # 60003 -> Transf. Files active.
[81] # 60004 -> Periodic change.
[82] # 60005 -> RTU synchronized.
[83] # 60006 -> Source of synchronization.
[84] # NumSignals,AddSignalOverflow,%Lleno,%Vacio,TimeCambioPeriodico(s),
[85] 3,60001,70,30,1440,
[86] # Add101,DIR,ISC,Neg,
[87] 1,10,0,0,
[88] 2,10,1,0,
[89] 3,10,2,0,
[90] ##################
[91] # SENALES DOBLES #
[92] ##################
[93] # NumSenalesDobles,

M1CPTA2005I
1CPT: Substation Central Unit B-58
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[94] 3,
[95] # Add101,DIR,ISCoff,ISCon,ISCdesc,Neg,
[96] 10001,22,10,11,-1,0,
[97] 10002,22,12,13,0,0,
[98] 10003,22,14,15,0,0,
[99] #########
[100] # TOMAS #
[101] #########
[102] # NumTomas,
[103] 2,
[104] #
Add101,DIR,MEA,UCSVigilaEstInterm,UsaValorTomaErronea,ValorTomaErronea,
[105] 20001,17,1,0,0,0,// RTV IEC61850
[106] 20002,21,1,1,1,0,// RTN Procome
[107] ###########
[108] # MEDIDAS #
[109] ###########
[110] # NumMedidas,TimeCapturaMedidas(s),TipoASDU,PorcentajeOverflow,
[111] 4,2,13,1.0,
[112] #
Add101,DIR,MEA,Corr,Offset,Ope(6),VBA,PBA,Lmax,Lmin,Vmax,Vmin,FondoEscal
aSup,
[113] # FondoEscalaInf,UCSGestionaOverflow,
[114] 15001,22,0,0.009768,80.0,1,0,0,0,0,0,0.02,0,0,0,0,0,4095,0,0,//VCON
Procome
[115] 15002,23,1,0.032234,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,4095,-4095,0,//V
Procome
[116] 15005,24,2,1.0,0.0,1,0,0,0,0,0,0.008,0,0,0,0,0,7.0,0.0,0, //I float
[117] 15006,25,3,1.0,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,132.0,-132.0,0, //V float
[118] ##############
[119] # CONTADORES #
[120] ##############
[121] # NumCont,TiempoCapturaEspontanea(min),TiempoCapturaHistorico(min),
[122] # MinutoIniCapt,bCapturaInicial,
[123] 4,60,60,1,1,
[124] # Add101,DIR,CON
[125] 25001,22,0,
[126] 25002,22,1,
[127] 25003,22,2,
[128] 25004,22,3,
[129] ##############
[130] # IOAs RANGE#
[131] ##############
[132] # EstSim,EstSist,EstDob,Med,Toma,Cont,OrdSim,OrdDob,OrdConsig,OrdPaso,
[133] 1,60001,10001,15001,20001,25001,30001,35001,40001,45001,
[134] #
[135] ############################################
[136] # GESTIÓN ACTIVACIÓN/DESACTIVACIÓN SEÑALES #
[137] ############################################
[138] # NumCambDesact,NumCambAct,TimeActDesac(s),
[139] 0,5,5,

M1CPTA2005I
B-59 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.5 Gateway 104-101: GW104101.CFG

The emulation of IEC 870-5-104 protocol has been made by creating a task acting as Gateway
between said protocol and the IEC 870-5-101. As far as user data and 101 frames, the profile is
implemented through the corresponding IEC101 task. The GW104101 task is in charge of
translating FT1.2 message format into IEC-104 format and sending to the task which
implements the TCP/IP stack. On the other hand, it receives IEC-104 messages, converts them
into FT1.2 format and sends the same to IEC101 task. Therefore, to configure an IEC 870-5-
104 profile, two files: CEI101x.CFG and GW104101.CFG must be filled in.

In “gw104101.cfg” data related to IEC 870-5-104 and IEC 870-5-101 profile interfaces are
configured.
• Link Layer Configuration Data
GWLinkAdd , GWTamLinkAdd , GWTipoLinkAdd , MaxPrimaryRetries ,

PrimaryLinkLayerTi , GWFrameMaxLe , NivelMonitor , HabResetRemoto ,

meout nght

• GWLinkAdd: Address of link to communicate with 101 task.

• GWTamLinkAdd: Size of the link address field. It must be configured the same as for the
corresponding 101 profile. It can be 1 or 2.
• GWTipoLinkAdd: indicates if the link address field is non structured (1) or structured (2).
• MaxPrimaryRetries: Maximum number of retries with the IEC101 task.
• PrimaryLinkLayerTimeout: Timeout of communications with the IEC101 task.
• GWFrameMaxLenght: Maximum size of a IEC101 frame. Minimum value = 50; maximum
value = 255.
• NivelMonitor: Trace monitoring level.
• HabResetRemoto: Indicates if the remote communications reset function is enabled. 1
indicates it is enabled and 2 not enabled. Default value, 0: Not enabled. This function is
only valid in the 101 profile B.

EX: 128,2,1,1,100,255,0,0,

• ASDU Configuration Data

GWASDUAdd , GWTamCOT , GWTamComAddASDU ,

• GWASDUAdd: ASDU address to communicate with the IEC101 task.

• GWTamCOT: Size of the transmission cause field. It must be configured the same as for
the corresponding 101 profile. It can be 1 or 2.
• GWTamComAddASDU: Size of the ASDU address field. It must be configured the same
as for the corresponding 101 profile. It can be 1 or 2.

Ex: 128,2,2,

M1CPTA2005I
1CPT: Substation Central Unit B-60
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• APCI Data for Communications with SCADA using Single Socket Connection

Port104 , ApciK , ApciW , ApciT1 , ApciT2 , ApciT3 , SendTest ,

DirIP104 , IndexLAN ,

• Port104: IP port to communicate with SCADA using IEC 104 protocol. The set value is
2404.
• ApciK: Value of parameter k: maximum difference between sequence numbers to send a
status variable. The range is 1 to 32767.
• ApciW: Value of parameter w: Last acknowledgement after receiving type 1 w APDUs.
The range is 1 to 32767.
• ApciT1: Timeout for response to a SEND or TEST type APDU transmission. The range is
1 a 255 seconds.
• ApciT2:Timeout for confirmation in case of messages with no data. ApciT2 < ApciT1. The
range is 1 a 255 seconds
• ApciT3: Timeout to send type S frames in case of long inactive periods: ApciT3 > ApciT1.
The range is 1 a 255 seconds.
• SendTest: Indicates if a Test message must be sent to SCADA after ApciT3 times out
without receiving any message from the same. Value: 0 = No message sent; 1 =
Message sent. Default value is 0.

Data of the IP address of 104 interface:

• DirIP104: IP address to be configured in the communications interface within the Central

Unit to communicate with the 104 control facility. If the field is left blank, the IP address of
the Central Unit is taken (configured in TCP.CFG file). If a valid IP address is configured,
it will be used to communicate with the 104 master.
• IndexLAN: Index of the LAN port to be used for communications via TCP/IP. For CPT
relays, provided with two Ethernet ports, this will be 1 or 2. Default value is 1, associated
to LAN1.

Ex: 2404,20,8,15,10,20,1,
192.168.14.12,1,

• APCI Data for Communications with SCADA using Multiple Socket Connection

[MULTIPLE SOCKETS]
NumSockets , ChkIPDest ,
DirIPOrigen , Port104 , ApciK , ApciW , ApciT1 , ApciT2 , ApciT3 ,

DirIP104 , IndexLAN , MaskIP , (*)

(*) It repeats for each socket configured to communicate with SCADA.

• [MULTIPLE SOCKETS]: Label that identifies the configuration section of the APCI data
for communication with SCADA by means of multiple sockets.
• NumSockets: Number of sockets used for communication with SCADA. The maximum
number of sockets simultaneously connected to the Central Unit is limited to 8.

M1CPTA2005I
B-61 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• ChkIPDest: Parameter that indicates if the destination IP is checked before admitting a

connection from a 104 master. If the value is 0, only the source address is checked, that
is, DirIPOrigen must coincide with the master IP address. If the value is 1, the destination
address is also checked, that is, the address configured in the DirIP104 field of the
associated connection.
• DirIPOrigen: Is the IP address used by SCADA to establish the socket with Central Unit.
The Central Unit will check that the IP address used by SCADA to establish the socket
matches the one configured in this parameter, except when 255.255.255.255, has been
configured, in which case, the connection will be enabled from any IP address.
• Port104: Is the TCP port used for communicating with the SCADA using CEI 104
protocol. The set value is 2404.
• ApciK: Value of parameter k: maximum difference between sequence numbers to send a
status variable. The range is 1 a 32767.
• ApciW: Value of parameter w: Last acknowledgement after receiving type 1 w APDUs.
The range is 1 to 32767.
• ApciT1: Timeout for response to SEND or TEST type APDU transmission. The range is 1
to 255 seconds.
• ApciT2: Timeout for confirmation in case of messages with no data. ApciT2 < ApciT1.
The range is 1 to 255 seconds
• ApciT3: Timeout to send type S frames in case of long inactive periods: ApciT3 > ApciT1.
The range is 0 to 255 seconds. In case 0 is configured, test type messages will not under
any circumstance ever be sent to SCADA.
• DirIP104: IP address to be configured in the communications interface within the Central
Unit to communicate with the 104 control facility. If the field is left blank, the IP address of
the Central Unit is taken (configured in TCP.CFG file). If a valid IP address is configured,
it will be used to communicate with the 104 master.
• IndexLAN: Index of the LAN port to be used for communications via TCP/IP. For CPT
relays, provided with two Ethernet ports, this will be 1 or 2. Default value is 1, associated
to LAN1.
• MaskIP: Network mask to be associated to DirIP104. If this parameter is not configured,
the default value (255.255.0.0) is used.

Ex: 2,0,
10.27.67.102,2404,20,8,15,10,20,10.27.67.100,1,255.255.255.0,
255.255.255.255,2404,20,8,15,10,20,192.168.14.12,2,

The file becomes as follows for the case of communications with SCADA using a single socket:

[1] # Configuration of Gateway 104 101

[2] # Link layer data
[3] 128,2,1,100,255,0,
[4] # ASDU data
[5] 128,2,2,
[6] # APCI data
[7] 2404,20,8,15,10,20,1,
[8] # IP address data of 104 interface
[9] 192.168.14.12,1,

M1CPTA2005I
1CPT: Substation Central Unit B-62
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes as follows for the case of communications with SCADA using multiple
sockets:

[1] # Configuration of Gateway 104 101

[2] # Link layer data
[3] 128,2,1,100,255,0,
[4] # ASDU data
[5] 128,2,2,
[6] # APCI data
[7] [MULTIPLE SOCKETS]
[8] 8,0,
[9] 10.27.67.101,2404,20,8,15,10,20,10.27.67.100,1,
[10] 10.27.67.102,2404,20,8,15,10,20,10.27.67.100,1,
[11] 10.27.67.103,2404,20,8,15,10,20,10.27.67.100,1,
[12] 10.27.67.104,2404,20,8,15,10,20,10.27.67.100,1,255.255.255.0,
[13] 255.255.255.255,2404,20,8,15,10,20,192.168.14.12,2,
[14] 255.255.255.255,2404,20,8,15,10,20,192.168.14.12,2,
[15] 255.255.255.255,2404,20,8,15,10,20,192.168.14.12,2,
[16] 255.255.255.255,2404,20,8,15,10,20,192.168.14.12,2,

M1CPTA2005I
B-63 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.6 IEC60870-5-101 Balanced / IEC60870-5-104: C101104I.CFG

In this file, “c101104i.cfg”, the parameters of IEC60870-5-101balanced or IEC60870-5-104
remote control protocol are configured: general data, commands (single and double), tap and
set point commands, contact signals (single and double), tap positions, measurements and
counters. These orders, signals, measurements and counters are referenced with a IEC60870-
5-101/104 protocol address (Dir101). Each of these shall be associated a Central Unit
command, signal, measurement or counter. This profile uses the following sizes for variable
protocol parameters:

Parameter Size Format

Link address 2 Non structured
ASDU address 2 -
Information Object address 3 Non structured
Transmission Cause 1 -

If IEC60870-5-104 is used, file GW1041I.CFG described in section B.2.8 must also be

configured in accordance with the table above.

File format is practically identical to file CEI101I.CFG as follows:

• Configuration Data of Virtual Remote Control Signals
It will be made as described in section A.1. The two virtual Remote Control signals will be
configured:

- Signal 0: Indicates communications failure with the control facility of the Remote
Control.
- Signal 1: Indicates whether a point of the Remote Control is blocked, a
signal/measurement is blocked by oscillator,
- Signals 2,3,4 : Spare
- Signals 5-12: Indicate which Client is connected or disconnected. 8 Clients can be
connected as a maximum.
o Signal 5: Indicates that Client 1 is connected or disconnected.
o Signal 6: Indicates that Client 2 is connected or disconnected.
o Signal 7: Indicates that Client 3 is connected or disconnected.
o Signal 8: Indicates that Client 4 is connected or disconnected.
o Signal 9: Indicates that Client 5 is connected or disconnected.
o Signal 10: Indicates that Client 6 is connected or disconnected.
o Signal 11: Indicates that Client 7 is connected or disconnected.

Ex: 13,
0,1,0,0,0,1,
1,1,0,0,0,1,
2,1,0,0,0,1,
3,1,0,0,0,1,
4,1,0,0,0,1,
5,1,0,0,0,1,
6,1,0,0,0,1,
7,1,0,0,0,1,
8,1,0,0,0,1,
9,1,0,0,0,1,
10,1,0,0,0,1,
11,1,0,0,0,1,
12,1,0,0,0,1,

M1CPTA2005I
1CPT: Substation Central Unit B-64
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Address Data of the Central Unit (RTU): [refer to example, line 7]

DirEnlace , DirASDU , Interface104 ,

• DirEnlace: Link address of the Central Unit. Default setting is 1.

• DirASDU: ASDU address of the Central Unit. Default setting is 1.
• Interface104: Indicates whether IEC101 (0) or IEC104 (1) protocol is to be used. In this
case, file GW1041I.CFG is needed, and task GW41I is launched in run time. If not
configured, default value is 101.

Ex: 3,10007,1,

• Configuration Data of Port Communications: [refer to example, lines 9-

11]
NumPuertos ,
Puerto , Veloc , TipoPar , NumBits , NumStop , TamañoFIFO , (*)

(*) It repeats for each port. There will be as many ports as indicated under NumPuertos.

• NumPuertos: Number of ports to communicate with the control facility. Default setting is
2.
• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4 for
CPX relays. For CPX relays, possible values are COM1 and COM2. By default, they are
configured as COM1 and COM2.
• Veloc: Baud rate. It can take the values 600, 1200, 2400, 4800, 9600 and 19200 baud.
Default setting is 9600.
• TipoPar: Type of parity. It can take the following values:
 ‘N’ or ‘n’ = None.
 ‘O’, ‘o’, ‘I’ or ‘i’ = Odd.
 ‘E’, ‘e’, ‘P’ or ‘p’ = Even.
The default setting is even.
• NumBits: Number of bits. Possible values are 7 and 8 bits. Default setting is 8.
• NumStop: Number of stop bits. Possible values are 1 and 2. Default setting is 1.
• TamañoFIFO: Is the size of FIFO in bytes. Possible values are 1, 4, 8, 14 or 0 (FIFO not
used). Default value is 1.

Ex: 2,
COM1,1200,e,8,1,1,
COM2,1200,e,8,1,1,

Note: If the 104 interface is configured, these port data will be ignored by the application, since it works
through LAN.

M1CPTA2005I
B-65 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• General Data Related to Modem Line Control and various Times used by the
Central Unit: [refer to example, line 17]
TimeCDon , TimeCDoff , TimeRTSon , TimeRTSoff , SwCTS , SwCDTx , …

... SwCDRx , RTSAlwaysOn , TimeErrTelem , TimePortNoActivo , ...

... NivelTraza , TimeCambMando , TimeSel , TimeEntreConsig , ...

... RRLResetClase2 , TimeEntreMsjTF , TimeTotalTF , MaxSegmPorSeccion , ...

... TimeVigilaEstIntermToma , PermisoSincronizar , MaxNumReintSeccion , ...

... MaxNumReintFichero , ToutChar ,

• TimeCDon: Timeout (in msec.) for CD ON in order for data received to be deemed good.
Default value will be 0.
• TimeCDoff: Timeout (in msec.) waiting for transmission before CD sets to OFF. If
SwCDTx is 0, it will always wait. If SwCDTx is 1 and the time for CD to OFF times out, the
transmission will be aborted. Default value will bebe500.
• TimeRTSon: Timeout (in msec.) to start the transfer from the time RTS sets to ON. If
SwCTS is 0, it will always wait and, when it times out, the transmission begins. If SwCTS
is 1, this is the Timeout for CTS to set to ON. If this time times out, CTS remains OFF,
and the transmission is aborted. Default value will be 500.
• TimeRTSoff: Timeout (in msec.) for RTS to set to OFF after transmission. In case
RTSAlwaysOn is 1, it always waits, but at the end of transmission RTS will not be set to
OFF. Default value will be 11.
• SwCTS: Indicates whether the CTS line is checked (1) or not (0) before transmission.
Default value will be 1.
• SwCDTx: Indicates whether the CD line is checked (1) or not (0) for transmission. If
checked, CD must be set to OFF before transmission. Default value will be 1.
• SwCDRx: Indicates whether the CD line is checked (1) or not (0) for receiving. If checked,
the CD must be set to ON for TimeCDon milliseconds to start receiving data. Default
value will be1.
• RTSAlwaysOn: Indicates if the RTS always remains set to ON (1) or on the contrary it
sets to ON and to OFF before and after transmission respectively. Default value will be 0.
• TimeErrTelem: Timeout (in sec.) before issuing remote control communications error.
Default value will be 60.
• TimePortNoActivo: Timeout (in sec.) without receiving messages through one port to be
able to switch to the other communications port. By default is set to 10.
• NivelTraza: Trace monitoring level by the screen. The value 0 disables traces and this is
the value to be configured by default.
• TimeCambMando: Timeout (in sec.), from command completion, to label the associated
changes with non spontaneous cause. Default value will be 10.
• TimeSel: Timeout (in sec.) to automatically deselect a previously selected command. It
only has sense when commands are run with the SELECT AND EXECUTE method.
Default value is10 seconds.

M1CPTA2005I
1CPT: Substation Central Unit B-66
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TimeEntreConsig: Timeout (in msec) between two consecutive set point commands.
Default value is de 22 milliseconds.
• RRLResetClase2: Indicates if, after receiving a Reset Remote Link, class 2 data queues
must be reset (1) or not (0). By default is set to 1.
• TimeEntreMsjTF: Timeout (in sec.) between file transfer messages to abort the transfer.
By default is set to 60.
• TimeTotalTF: Timeout (in sec.) to abort a file transfer. By default is set to 300.
• MaxSegmPorSeccion: Maximum number of segments of each section that will be sent in
the file transfer. By default is set to 10.
• TimeVigilaEstIntermToma: Timeout (in sec.) for the Central Unit to monitor the
intermediate status of a capture (wrong value, namely, no capture or simultaneous
capture). When this times out with the capture to wrong value, it will be sent as invalid to
the control facility. If not configured, the default value is10 seconds.
• PermisoSincronizar: Indicates if the control facility is (1) or is not (0) enabled to
synchronize the Central Unit. Only one of those control facilities which will interrogate the
Central Unit may have this parameter set to 1. The rest of them will have it set to 0. If
more than one protocol is configured as possible synchronization source, the protocol
which started first in the Central Unit will be the only one to enable the corresponding
control facility synchronize the Central Unit. Default setting is 1.
• MaxNumReintSeccion: Maximum number of section send retries to abort file transfer.
They are retries, therefore one section will be sent “MaxNumReintSeccion” + 1 times. The
range is 1..100. If not configured, the default value is 2 retries.
• MaxNumReintFichero: Maximum number of file send retries to abort file transfer. They
are retries, therefore one file will be sent “MaxNumReintFichero” + 1 times. The range is
1..100. If not configured, the default value is 2 retries.
• ToutChar: Timeout between characters to reject a frame. If configured to 0, the timeout
between characters will be the one calculated internally by the Central Unit, adapted to
each baud rate. If not configured, the default value is 0.

Ex: 0,500,500,11,1,1,1,0,60,5,0,10,10,22,0,60,2100,5,10,1,2,2,0,

• Data on the Size of the Different Data Queues: [refer to example, line 19]
TamColaClase1 , TamColaClase2 , TamColaComandos , TamColaÓrdenes ,

• TamColaClase1: Size of class 1 data queue. Once class 1 data number has been
attained, a queue overflow will occur and data will not be stored until an application Reset
is received. Default setting is 1000.
• TamColaClase2: Size of each of class 2 data queues. Once the number of class 2 data
has been attained, data will not be stored until there is space in the queue for more data.
Default setting is 1000.
• TamColaCommands: Size of the command queue. This is the maximum number of
nonprocessed commands (data requests) that the Central Unit can store. Default setting
is 10.
• TamColaÓrdenes: Size of the command queue. It is the maximum number of commands
pending confirmation that the Central Unit is capable of processing. Default setting is 3.

Ex: 1000,1000,10,3,

M1CPTA2005I
B-67 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Time Synchronizing Configuration Data: [refer to example, Line 22]

GestionaST , NotificaST , TimeAjuste , Fuente , TimeSincro , TimeSincro , ...

Sincro Sincro KO OK

... DiffTimeParaLanzar ,
SincroSNTP

• GestionaST: Indicates if the control facility sends the updated date and hour with
summer/winter time change (1) or not (0). Default value will be 1.
• NotificaST: Indicates if the control facility sends the ST bit, indicating the summer/winter
time (1), or not (0). Default value will be 1.
• TimeAjusteSincro: Timeout (in msec) to adjust the time synchronization to compensate
for possible clock drift, channel delays, etc. Default value will be 0.
• FuenteSincro (CPX/CPP-A relays only): Indicates the default synchronizing source:
0=Protocol, 1=External clock. Default setting is 0.
• TimeSincroKO (CPX/CPP-A relays only): Timeout (in sec.) without receiving
synchronizations to deem the Central Unit NOT synchronized. Default setting is 2100.
• TimeSincroOK (CPX/CPP-A relays only): Timeout (in sec.) receiving correct
synchronizations from the external clock to deem the Central Unit synchronized. Default
setting is 3.
• DiffTimeParaLanzarSincroSNTP: Time difference (in msec.) between the time received
by protocol and the internal time of the Central Unit, under which a multicast/broadcast
SNTP synchronization is not sent when the Central Unit is synchronized by control
facility. This parameter has meaning only if the Central Unit is configured as SNTP
server. If not configured, the default value is 0.

Ex: 1,1,0,0,2100,5,0,

• Configuration Data of Remote Control Single Commands

Each remote control single command is associated to a Central Unit command. It is essential
to put Dir101s in ascending order: [refer to example, lines 41-45]

NumOrdenes , Ejec , OrdenConmutaFteSincro ,

Dir101 , DirEq , ISE , DCO , DirEqOn , ISCon , ...

... DirEqOff , ISCoff , DirEqDes , ISCdes , ... (*)

... TimeEsp ,
InfoRetorno

(*) It repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control single commands.

• Ejec: Indicates if these single commands are being run through the DIRECT EXECUTE
(0) (default value) or SELECT AND EXECUTE (1) method. Default value is 0.
• OrdenConmutaFteSincro: Address of the IEC-101 command protocol used to switch the
synchronizing source. Default address is 62501.

M1CPTA2005I
1CPT: Substation Central Unit B-68
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Dir101: Address of the single command within protocol IEC-101.

• DirEq: Address of the equipment (CPU) that the command belongs to within the Central
Unit database.
• ISE: Central Unit command identifier.
• DCO: DCO with which the ISE command of the DirEq equipment will be run. Default
value will be 2.
• DirEqOn: Address of the equipment (CPU) that the ISCon digital signal belongs to within
the Central Unit database.
• ISCon: Digital signal identifier that indicates the command activation. If this signal is not
to be used, it will be configured in this field with the value –1.
• DirEqOff: Address of the equipment (CPU) that the digital signal ISCoff belongs to within
the Central Unit database.
• ISCoff: Digital signal identifier that indicates the command deactivation. If this signal is
not to be used, this field will be configured as –1.
• DirEqDes: Address of the equipment (CPU) that the digital signal ISCdes belongs to
within the Central Unit database.
• ISCdes: Digital signal identifier that indicates lack of information on the status of the
command. If this signal is not to be used, this field will be configured as –1.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the
associated changes (signals On, Off and Des) with non spontaneous cause. If not
configured, the default setting is “TimeCambMando”.

Ex: 3,0,62501,
30001,22,12,2,22,0,22,1,22,9,5,
30251,12,0,2,12,78,12,76,12,9,10,
30252,12,1,2,12,79,12,77,12,9,15,

• Configuration Data of Remote Control Double Commands

Each remote control double command is associated to two Central Unit commands. It is
essential to put Dir101s in ascending order: [refer to example, lines 50-55]

NumOrdenes , Ejec ,
Dir101 , DirEq , ISEon , DCOon , ISEoff , DCOoff , ...

... DirEqOn , ISCon , DirEqOff , ISCoff , DirEqDes , ISCdes , ... (*)

... TimeEsp ,
InfoRetorno

(*) This repeats for each remote control double command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control double commands.

• Ejec: Indicates if the double commands are being run with DIRECT EXECUTE (0)
(default value) or SELECT AND EXECUTE (1) method. Default value is 0.
• Dir101: Address of the double command within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the commands to be associated to the
double command belong to, within the Central Unit database.
• ISEon: Central Unit command identifier corresponding to double command activation.

M1CPTA2005I
B-69 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DCOon: DCO with which the ISEon command of DirEq equipment (double command
activation) will be run. Default value will be 2.
• ISEoff: Central Unit command identifier corresponding to double command deactivation.
• DCOoff: DCO with which the ISEoff command of DirEq equipment (double command
deactivation) will be run. Default value will be 2.
• DirEqOn: Address of the equipment (CPU) that the ISCon digital signal belongs to within
the Central Unit database.
• ISCon: Digital signal identifier that indicates the double command activation (ISEon
command activation). If this signal is not to be used, this field will be configured as –1.
• DirEqOff: Address of the equipment (CPU) that the ISCoff digital signal belongs to, within
the Central Unit database.
• ISCoff: Digital signal identifier that indicates the double command deactivation (ISEoff
command activation). If this signal is not to be used, it will be configured in this field with
the value –1.
• DirEqDes: Address of the equipment (CPU) that the digital signal ISCdes belongs to,
within the Central Unit database.
• ISCdes: Digital signal identifier that indicates lack of information on the status of the
double command. If this signal is not to be used, this field will be configured as –1.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the
associated changes (signals On, Off and Des) with non spontaneous cause. If not
configured, the default setting is “TimeCambMando”.

Ex: 3,0,
35001,12,0,2,1,2,12,80,12,0,12,4,5,
35002,12,6,2,7,2,12,81,12,0,12,4,10,
35003,12,8,2,9,2,12,82,12,0,12,4,15,

• Configuration Data of Tap Change Commands

Each remote control tap change command is associated to two Central Unit commands (raise
and lower the tap) and one measurement from which the tap is read. It is essential to put
Dir101s in ascending order: [refer to example, lines 60-63]

NumComandos , Ejec ,
Dir101 , DirEq , ISEsubir , DCOsubir , ...

... ISEbajar , DCObajar , MEA , ... (*)

... TimeEsp ,
InfoRetorno

(*) This repeats for each remote control tap change command. There will be as many as
indicated under NumCommands. They will be arranged in ascending order of Dir101.

• NumCommands: Number of remote control tap change commands.

• Ejec: Indicates if the tap change commands are being run using DIRECT EXECUTE (0)
(default value) or SELECT AND EXECUTE (1). Default value is 0.
• Dir101: Address of command within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that Central Unit commands and measurement
belong to.
• ISEsubir: Central Unit command identifier to raise the tap.
• DCOsubir: DCO with which the ISEraise command of DirEq equipment (to raise the tap)
will be run. Default value will be 2.
• ISEbajar: Central Unit command identifier to lower the tap.

M1CPTA2005I
1CPT: Substation Central Unit B-70
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DCOlower: DCO with which the ISElower command of DirEq equipment (to lower the tap)
will be run. Default value will be 2.
• MEA: Measurement identifier of the Central Unit where the tap is read.
• TimeEspInfoRetorno: Timeout (in sec.), from command completion, to label the first tap
change with non spontaneous cause. If not configured, the default setting is
“TimeCambMando”.

Ex: 2,0,
45001,17,4,2,5,2,1,15,
45002,21,4,2,5,2,1,20,

• Configuration data of set point change commands

There are two types of set point commands:

- Set point command by raise/lower the set point control function: after receiving a set
point command, the Central Unit starts a control function to find out the number of times
to raise/lower the set point value to reach the desired value. This mode will be applied for
commands on CPUs that do not allow direct set point commands (only allow raise/lower
set point commands). Each set point command by control function is associated two
commands (raise and lower set point) and a measurement where the set point can be
read.
- Direct set point command: a direct command is run upon the CPU in order to set the set
point to a value. Each direct set point command is associated an analog output write in
order to write the set point value to the CPU and a measurement where the set point can
be read.

It is essential to put Dir101s in ascending order: [refer to example, lines 68-74]

NumComandos , Ejec , TipoASDU , NumComandos ,

Autom Direct
Dir101A , DirEqA , ISEsubir , DCOsubir , ...

... ISEbajar , DCObajar , MedA , Paso , ... (*)

... TimeEsp ,
InfoRetornoA

Dir101D , DirEqD , ISM , MedD , ...

(**)
... TimeEsp , UCSGestiona ,
InfoRetornoD CmndTerm

M1CPTA2005I
B-71 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

(*) It repeats for each set point command by raise/lower the set point control function. There
will be as many as indicated under NumCommandsAutom. They will be arranged in ascending
order of Dir101.
(**) It repeats for each direct set point command. There will be as many as indicated under
NumCommandsDirect. They will be arranged in ascending order of Dir101.

• NumCommandsAutom: Number of remote control set point change commands by

raise/lower the set point control function.
• Ejec: Indicates if the set point change commands are being run using DIRECT EXECUTE
(0) (default value) or SELECT AND EXECUTE (1). Default value is 0.
• TipoASDU: Indicates the type of ASDU used for remote control set point commands.
Possible values are: 48 (standard) and 50 (in floating point). If not configured, the default
value is 48 (standard).
IMPORTANT: If there are configured set points (whether by control function and/or direct)
and are floating point (TipoASDU=50), measurements cannot be standard (ASDU 9),
since the UCS will issue an error and the remote control will not start, as the
measurement full scale is needed to scale the set point.
• NumCommandsDirect: Number of remote control direct set point change commands. If
not configured, the default value is 0.
• Dir101A: Address of the command by control function within protocol IEC-101.
• DirEqA: Address of the equipment (CPU) that Central Unit commands and measurement
belong to.
• ISEsubir: Central Unit command identifier to raise the set point.
• DCOsubir: DCO with which the ISEraise command of DirEq equipment (to raise the set
point) is run. Default value will be 2.
• ISEbajar: Central Unit command identifier to lower the set point.
• DCObajar: DCO with which the ISElower command of DirEq equipment (to lower the set
point) is run. Default value will be 2.
• MedA: Measurement identifier of the Central Unit where the set point is read.
IMPORTANT: If set points are not standard (TipoASDU other than 48) or MedA
measurement is floating format (refer to FormatoMed parameter in “DBASE.CFG”), this
measurement must be configured in the measurements section(Configuration data of
remote control measurements) in order to know the full scale and correction factors and
so be able to scale the set point. If the measurement is not configured, the UCS will issue
an error and the remote control will not start.
• Paso: Allows calculating the number of times the raise or lower the set point command
must be run to reach the required set point value, as follows:

|Current_Value-Required_Value|
Number of command runs = ----------------------------------------------
Paso
Default value is 205.
• TimeEspInfoRetornoA: Timeout (in sec.) for the set point to reach the value requested
from the control facility. When this time times out, if the value is not reached, a failed
command completion will be reported to the control facility. If not configured, the default
value is 127.
• Dir101D: Address of the direct command within protocol IEC-101.
• DirEqD: Address of the equipment (CPU) the analog output write belongs to and the
measurement in the Central Unit database.

M1CPTA2005I
1CPT: Substation Central Unit B-72
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• ISM: Analog output write identifier of the Central Unit to write the set point value to the
CPU.
• MedD: Measurement identifier of the Central Unit where the set point is read.
IMPORTANT: If set points are not standard (TipoASDU other than 48) or MedA
measurement is floating format (refer to FormatoMed parameter in “DBASE.CFG”), this
measurement must be configured in the measurements section (Configuration data of
remote control measurements) in order to know the full scale and correction factors and
so be able to scale the set point. If the measurement is not configured, the UCS will issue
an error and the remote control will not start.
• TimeEspInfoRetornoD: Timeout (in sec.) to receive the command completion from the
CPU. When this time times out, if the command completion is not received from the CPU,
a failed command completion will be reported to the control facility. If not configured, the
default value is 127.
• UCSGestionaCmndTerm: Indicates whether the UCS monitors the value of the
measurement associated to the set point to generate a command completion (1) or,
conversely, the relay generates said command completion (0). With IEC61850 protocol,
the relay generates the command completion, but not with the rest of protocols. If not
configured, the default value is 0.

Ex: 2,0,50,2,
40001,17,2,2,3,2,0,205,30,
40001,21,2,2,3,2,0,205,35,
40001,10,0,0,5,0,
40002,11,0,0,10,0,

• Configuration Data of Single Contact Remote Control Signals

Each remote control signal of this type is associated a Central Unit digital signal. It is essential
to put Dir101s in ascending order: [refer to example, lines 86-90]

NumSD , DirSeñOverflow , X% , Y% , TimeCambioPeriodico ,

Dir101 , DirEq , ISC , Neg , (*)

(*) It repeats for each remote control single contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control single contact signals (excluding system information
signals).
• DirSeñOverflow: Address of the signal that indicates that class 1 queue is totally full (it
will be configured with the value 60001). The rest of system information signals will be
consecutive :
 60002: Queue X% full (half full) signal.
 60003: File transfer active signal.
 60004: Periodic and spontaneous change signal.
 60005: Central Unit (RTU) synchronized signal.
 60006: Synchronizing source signal.
• X%: % at which the X% full class 1 queue (queue half full) signal is activated. If wrongly
configured (valid limits range from 20% to 95%), the default value (70%) will be
configured.

M1CPTA2005I
B-73 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Y%: % at which the X% full class 1 queue (queue half empty) signal is deactivated. If
wrongly configured (valid limits range from 0% to 80%), the default value (30%) will be
configured.
• TimeCambioPeriodico: Indicates how often (in seconds) the periodic and spontaneous
change 60004 is generated. Default setting is 0.
• Dir101: Address of the single contact digital signal within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the associated digital signal belongs to,
within the Central Unit database.
• ISC: Central Unit digital signal identifier.
• Neg.:Indicates if the digital signal is negated (1) or not (0) to send it to the control facility.
If not configured, the default value is 0.

Ex: 3,60001,70,30,1440,
1,10,0,0,
2,10,1,0,
3,10,2,0,

• Configuration Data of Remote Control Double Contact Signals

Each remote control signal of this type is associated three Central Unit digital signals . It is
essential to put Dir101s in ascending order: [refer to example, lines 95-99]

NumSD , bGestion4Estados ,

• NumSD: Number of remote control double contact signals.

• bGestion4Estados: Defines whether there will be 3 or 4 status signals associated to
double signals. If set to 0 or if omitted, there will be 3 associated signals, whereas id set
to 1, 4 associated status signals must be defined. Default value is 3.

Case 1) If 3 single signals associated to the Double Signals are selected, they must be
configured as follows:

Dir101 , DirEq , ISCabierto , ISCcerrado , ISCdescono , Neg , (*)

(
(*) It repeats for each remote control double contact signal. There will be as many as
indicated under NumSD. They will be arranged in ascending order of Dir101.

• Dir101: Address of the double contact signal within protocol IEC-101.

• DirEq: Address of the equipment (CPU) that the associated digital signals belong to,
within the Central Unit database.
• ISCabierto: Central Unit digital signal identifier that indicates double contact signal open
status. If this signal is not used, it will be configured with the value –1.
• ISCcerrado: Central Unit digital signal identifier that indicates double contact signal
closed status. If this signal is not used, it will be configured with the value –1.
• ISCunknown: Central Unit digital signal identifier that indicates double contact signal
unknown status. If this signal is not used, it will be configured with the value –1.
• e.g.: Indicates if the double signal is negated (1) or not (0) to send it to the control facility.
If not configured, the default value is 0. Attention! It only runs for OFF (closed) and ON
(open) statuses.

M1CPTA2005I
1CPT: Substation Central Unit B-74
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Case 2) If 4 single signals associated to the Double Signals are selected, they must be
configured as follows:

Dir101 , DirEq , ISCDescInterm , ISC_ON , ISC_OFF , ISCDescError , Neg , (*)

(*) It repeats for each remote control double contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• Dir101: Address of the double contact signal within protocol IEC-101.

• DirEq: Address of the equipment (CPU) that the associated digital signals belong to,
within the Central Unit database.
• ISCDescInterm: Central Unit digital signal identifier that indicates the intermediate
unknown status (00) of the double contact signal. If this signal is not used, it will be
configured with the value –1.
• ISC_ON: Central Unit digital signal identifier that indicates the OFF status (01 = open) of
the double contact signal. If this signal is not used, it will be configured with the value –1.
• ISC_OFF: Central Unit digital signal identifier that indicates the ON status (10 = closed) of
the double contact signal. If this signal is not used, it will be configured with the value –1.
• ISCDescError: Central Unit digital signal identifier that indicates the unknown status error
(11) of the double contact signal. If this signal is not used, it will be configured with the
value –1.
• Neg.: Indicates if the double signal is negated (1) or not (0) to send it to the control
facility. If not configured, the default value is 0. Attention! It only runs for OFF (closed)
and ON (open) statuses.

Ej: 3,0, // ,3 single signals associated to double signals

10001, 22, 10,11,12, 0,
10002, 22, 13,14,-1, 0,
10003, 22, 15,16,-1, 0,

or

3,1, // ,4 single signals associated to double signals

10001, 22, 10,11,12,13, 0,
10002, 22, 14,15,16,17, 0,
10003, 22, 18,19,20,21, 0,

• Configuration Data of Remote Control Taps

Each remote control tap is associated a Central Unit measurement. It is essential to put
Dir101s in ascending order: [refer to example, lines 104-107]

NumTomas ,
Dir101 , DirEq , MEA , UCSVigilaE , UsaValor , Valor , bUCS , LimSupT , (*)
stInterm Toma Toma Gestiona oma
Erronea Erronea TomaOV OV

(*) It repeats for each remote control tap. There will be as many as indicated under
NumTomas. They will be arranged in ascending order of Dir101.

M1CPTA2005I
B-75 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumTomas: Number of remote control taps.

• Dir101: Address of the tap within protocol IEC-101.
• DirEq: Address of the equipment (CPU) that the associated measurement belongs to,
within the Central Unit database.
• MEA: Central Unit measurement identifier.
• UCSVigilaEstInterm: Indicates if the Central Unit must monitor the intermediate status of
the tap (1) or not (0). If not configured, the default value is 1. For CPUs that manage
intermediate tap statuses (i.e. IEC61850) this parameter will be configured to 0. When the
Central Unit monitors the intermediate status, it will use “TimeVigilaEstIntermToma” as
monitoring time.
• UsaValorTomaErronea: Indicates if the CPU uses “ValorTomaErronea” as wrong tap
value (no tap or simultaneous tap) (1) or instead, this value is not used and the last
known value with flag IV=1 is used as wrong tap value (0). If not configured, the default
value is 1, for compatibility with ZIV’s RTN regulator. For IEC61850 CPUs this parameter
is configured to 0.
• ValorTomaErronea: Value sent by the CPU when the tap is wrong (no tap or
simultaneous tap). It is only used when the previous parameter “UsaValorTomaErronea”
is 1. If not configured, the default value is 0, for compatibility with ZIV’s RTN regulator.
For IEC61850 CPUs this parameter is configured to 0.
• bUCSGestionaTomaOV: Indicates whether the Central Unit monitors the overflow of the
tap in question or not. If not configured, the default value is 0, and it will not be monitored.
• LimSupTomaOV: Value associated to the field above by which the specific value
associated to the overflow of the tap in question is defined. It is only used when the
above parameter “bUCSGestionaTomaOV” is 1. If not configured, the overflow control
function will be cancelled, regardless of whether the field above is active. Its value must
never exceed the maximum allowed as regards representation in the associated asdu,
which is 63, and in this case it is forced to this extreme value.

Ex: 2,
20001,17,1, 0,0,0,// RTV IEC61850
20002,21,1, 1,1,0, 1,23,// RTN PROCOME

• Configuration Data of Remote Control Measurements

Each remote control measurement is associated a Central Unit measurement. It is essential to
put Dir101s in ascending order. Measurement values in this protocol implementation can be
standard (ASDU 9) or floating point (ASDU 13): [refer to example, lines 112-118]

NumMedidas , TimeCapturasMedidas , TipoASDU , PorcentajeOverflow ,

Dir101 , Dir , Medida , Corr , Offset , Ope1 , Ope2 , ...

... Ope3 , Ope4 , Ope5 , Ope6 , VBA , PBA , ...

... LINF , LISUP , VMAX , VMIN , FondoEscalaSup , ...

... FondoEscalaInf , UCSGestionaOverflow , (*)

M1CPTA2005I
1CPT: Substation Central Unit B-76
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

(*) This repeats for each remote control measurement. There will be as many as indicated
under NumMedidas.

• NumMedidas: Number of remote control measurements.

• TimeCapturasMedidas: Timeout (in sec.) for exploring measurements. If not configured,
the default value is 1.
• TipoASDU: Indicates the ASDU with which measurements are sent. Possible values are
9 (standard) or 13 (floating point). If not configured, the default value is 9. IMPORTANT: If
these measurements are standard (TipoASDU=9) and there are configured set points
(whether by control function and/or direct) and they are floating point (ASDU 50) the UCS
will issue an error and the remote control will not start, since measurement full scales are
needed to scale the set point.
• PorcentajeOverflow: Rate per unit of the full scale to indicate overflow. It is only used for
measurement overflows managed by the Central Unit ( “UCSGestionaOverflow” to 1). If
not configured, the default value is 4090/4095. For CPUs that manage measurement
overflow (i.e. IEC61850), this value must be configured to 1.0.
• Dir101: Address of the measurement within protocol IEC-101.
• Dir: Address of the equipment (CPU) that the measurement in the Central Unit database
belongs to.
• Medida: Central Unit measurement identifier.
• Corr: Correction factor that enables the conversion of Central Unit database
measurement values into IEC-101 measurement values. Default value is 1.0.
• Offset: Offset that allows to convert Central Unit database measurement values into IEC-
101 measurement values. Default value is 0.0.

Value_Measurement_101 = Value_Measurement_BD_UCS * Corr + Offset

• Ope1: VBA parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 1.
• Ope2: PBA parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• Ope3: LINF parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• Ope4: LISUP parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to
0.
• Ope5: VMAX parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to
0.
• Ope6: VMIN parameter use indicator: 0 = Not in use; 1 = In use. It will be configured to 0.
• VBA: Band Value, indicates the minimum variation between two measurement values in
order for the new value to be sent to the control facility. It is configured in rate per unit (1
= 100%).
Iberdrola default values are:
- 0.1%: For voltage measurements (V), LV (VOLT).
- 0.2%: For active power (P), reactive power (Q), temperature (T), distance-to-fault
(DFAL) measurements.
- 0.8%: For current measurements (I).
- 2%: For set point voltage measurements (VCON).

M1CPTA2005I
B-77 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• PBA: Periodo de Banda, is the timeout to deem the measurement valid for transmission
(not used).
• LINF: Límite Bajo, is the value below which an alarm status is issued (not used).
• LISUP: Límite Alto, is the value above which an alarm status occurs (not used).
• VMAX: Valor Máximo, is the engineering value of the maximum value that the user
sensor can deliver to the capture card (not used).
• VMIN: Valor Mínimo, is the engineering value of the minimum value that the user sensor
can deliver to the capture card (not used).
• FondoEscalaSup: Upper equipment measurement full scale. Default value is 4095,
which is the upper full scale for our PROCOME CPUs.
Values to be configured for:
- PROCOME: 4095.
- DNP3: 32767.
- IEC61850: Maximum measurement value (attribute “rangeC$max”) (i.e. 7 A, 132
kV..).
• FondoEscalaInf: Lower equipment measurement full scale. If not configured, the default
value is 0.
Values to be configured for:
- PROCOME: 0 (for single pole measurement) or –4095 (for bipolar measurement).
- DNP3: 0 (for single pole measurement) or –32767 (for bipolar measurement).
- IEC61850: Minimum measurement value (attribute “rangeC$min”) (i.e. 0 A, -132
kV..).
IMPORTANT: FondoEscalaSup must be greater than FondoEscalaInf. If this is not
configured this way, the UCS will issue an error and the remote control will not start.
• UCSGestionaOverflow: Indicates whether the measurement overflow is managed by the
Central Unit (1) or the CPU (0) If not configured, the default value is 1 for compatibility
with our PROCOME CPUs. For CPUs that manage measurement overflows (i.e.
IEC61850) this parameter will be configured to 0.

This protocol implementation only uses the VBA (band value) parameter .

The Corr and Offset factors will be used for example to convert to floating point (ASDU 13) 16
bit whole measurements (i.e. PROCOME accounts):

- Ex: If a PROCOME measurement measures 0 to 7 amp (single pole measurement),

the units [0 to 4095] must be scaled to floating point format. For this, calculations
are as follows:

Corr = ABS(Vmax – Vmin) / (fesup – feinf) = ABS(7 – 0) / (4095 – 0) = 0.00171.

Offset = Vmin = 0

Since Value_Measurement_101 = ( Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 0 A.

Value_Measurement_BD_UCS = 1024 units  Value_Measurement_101 = 1.75 A.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 3.5 A.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 7 A.

M1CPTA2005I
1CPT: Substation Central Unit B-78
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

- Ex: If a PROCOME measurement measures 80 to 120 amp (single pole

measurement), the units [0 to 4095] must be scaled to floating point format. For this,
calculations are as follows:

Corr = ABS(Vmax – Vmin) / (fesup – feinf) = ABS(120 – 80) / (4095 – 0) = 0.00976801.

Offset = Vmin = 80

Since Value_Measurement_101 = ( Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 80 kV.

Value_Measurement_BD_UCS = 1024 units  Value_Measurement_101 = 90 kV.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 100 kV.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 120 kV.

- Ex: If a PROCOME measurement measures -132 to 132 kV (single pole

measurement), the units [-4095 to 4095] must be scaled to floating point format. For
this, calculations are as follows:

Corr = MAX[ABS(Vmax ),ABS(Vmin)] / (fesup) = 132 / 4095 = 0.032234

Offset = 0

Since Value_Measurement_101 = (Value_Measurement_BD_UCS * Corr ) + Offset

Value_Measurement_BD_UCS = -4095 units  Value_Measurement_101 = -132 kV.

Value_Measurement_BD_UCS = -2048 units  Value_Measurement_101 = -66 kV.
Value_Measurement_BD_UCS = 0 units  Value_Measurement_101 = 0 kV.
Value_Measurement_BD_UCS = 2048 units  Value_Measurement_101 = 66 kV.
Value_Measurement_BD_UCS = 4095 units  Value_Measurement_101 = 132 kV.

However, in case (ASDU 9) measurements must be standardized to floating point (i.e.

IEC61850), Corr and Offset are automatically calculated by the Central Unit (namely, the values
configured in the file for these parameters will be ignored), using the following criterion agreed
upon with Iberdrola:

- If the measurement is single pole, namely ABS(FondoEscalaSup) is other than

ABS(FondoEscalaInf) (asymmetric measurement), this floating point measurement will be
scaled between the standard values 0 and 32767.
- If the measurement is bipolar, namely ABS(FondoEscalaSup) is equal to
ABS(FondoEscalaInf) (symmetric measurement), this floating point measurement will be
scaled between the standard values -32767 and 32767.

Ex: 4,2,13,1.0,
15001,22,0,0.009768,80.0,1,0,0,0,0,0,0.02,0,0,0,0,0,4095,0,0,
15002,23,1,0.032234,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,4095,-4095,0,
15005,24,2,1.0,0.0,1,0,0,0,0,0,0.008,0,0,0,0,0,7.0,0.0,0,
15006,25,3,1.0,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,132.0,-132.0,0,

M1CPTA2005I
B-79 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Counters

Each remote control counter is associated a Central Unit counter. It is essential to put Dir101s
in ascending order: [refer to example, lines 123-128]

NumConts , TimeCaptEspontanea , TimeCaptHist , MinutoIniCapt , bCapturaInicial ,

Dir101 , DirEq , CON , (*)

(*) This repeats for each remote control counter. There will be as many as indicated under
NumConts. They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• TimeCaptEspontanea: Timeout (in min) of counter capture for spontaneous transfer. If
configured to 0, no counters will be sent spontaneously. Default value is 60 minutes.
• TimeCaptHist: Timeout (in min) of counter capture for counter history. if configured to 0,
no counter history will exist. Default value is 60 minutes.
• MinutoIniCapt: Minute of the hour when counters begin being captured. If not configured,
the default value is 1.
• bCapturaInicial: Indicates if the Central Unit sets an initial counter capture to (1) or not (0)
with all the counters to invalid. If not configured, the default value is 1. For Central Units
with IEC61850 CPUs, this parameter must be configured to 0, whereas for the rest of
Central Units (i.e. PROCOME, DNP3...) it must be configured to 1.
• Dir101: Address of the counter within protocol IEC-101.
• DirEq: Address of the equipment that the counter within the Central Unit database
belongs to.
• CON: Central Unit counter identifier.

Ex: 4,60,60,1,1,
25001,22,0,
25002,22,1,
25003,22,2,
25004,22,3,

• Configuration Data of IOA Ranges (Information Object Address) for the

Different Remote Control Points
Each remote control point is assigned a 101 address, IOA (Information Object Address). The
initial IOAs will be configured in this section, based on the range that corresponds to each of the
different types of points (single, double signals, measurements, taps, meters, commands, etc.)
[refer to example, line 134]

IOAIniEstSim , IOAIniEstSist , IOAIniEstDob , IOAIniMed , IOAIniTom , ...

... IOAIniCont , IOAIniOrdSim , IOAIniOrdDob , IOAIniOrdConsig , IOAIniOrdPaso ,

• IOAIniEstSim: Initial single signal IOA. If not configured, the default value is 1.
• IOAIniEstSist: Initial system signal IOA. If not configured, the default value is 60001.
• IOAIniEstDob: Initial double signal IOA. If not configured, the default value is 10001.
• IOAIniMed: Initial analog measurement IOA. If not configured, the default value is 15001.
• IOAIniTom: Initial tap IOA. If not configured, the default value is 20001.
• IOAIniCont: Initial counter IOA. If not configured, the default value is 25001.
• IOAIniOrdSim: Initial single command IOA. If not configured, the default value is 30001.
• IOAIniOrdDob: Initial double command IOA. If not configured, the default value is 35001.

M1CPTA2005I
1CPT: Substation Central Unit B-80
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• IOAIniOrdConsig: Initial set point change command IOA. If not configured, the default
value is 40001.
• IOAIniOrdPaso: Initial tap change command IOA. If not configured, the default value is
45001.

Ex: 1,60001,10001,15001,20001,25001,30001,35001,40001,45001,

• Management Data for Activation/Deactivation of Signals Resulting from

Excessive Number of Changes
Data for the remote control to activate/deactivate signals resulting from excessive number of
changes are configured here. Since management can be carried out in CPUs (i.e. as is the case
for IEC61850), Central Unit kernel and remote control module, consideration must be given in
each case as from where the management should and should not be activated [refer to
example, line 140]

NCambDesact , NCambAct , TimeActDesact ,

• NCambDesact: Number of changes to deactivate a signal. To deactivate the managing

function for signal activation / deactivation in the remote control module, this parameter
will be configured to 0. If not configured, the default value is 0.
• NCambAct: Number of changes to activate a signal. If not configured, the default value is
0.
• TimeActDesact: Control period (in sec.) of the number of changes. If not configured, the
default value is 10.

Operation of signal activation/deactivation management:

- A signal deactivates when “NCambDesact” or more changes are produced in

“TimeActDesact” seconds. (NOTE: “NCambDesact” = 0, implies the function is
deactivated and, therefore, no signal will ever be deactivated).
- A deactivated signal activates again when no more than “NCambAct” changes are
produced in “TimeActDesact” seconds provided the number of changes is less than
“NCambDesact”.
Ex: 0,0,10,

• Link Level Configuration Data

In this section the link level data are configured [refer to example, line 145]

TipoEnlace , DirTxFisica , NumReintN2 , TimeoutN2 ,

• TipoEnlace: Type of link level: 0=Balanced, 1=Unbalanced. By default, it is 1.

• DirTxFisica: Address of physical transmission. Equivalent to the DIR bit of the 101 frame
control byte: 1= Control facility->RTU, 0= RTU->Control facility. Default value is 0.
• NumReintN2: Maximum number of link level retries to issue a communications error with
the control facility. Default value is 3 retries. It is meaningless for the Unbalanced mode.
• TimeoutN2: Timeout between link level retries (in msec.). Default value is 1000
milliseconds (1 second).

Ex: 0,0,3,1000,

M1CPTA2005I
B-81 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # Configuration of RTU CEI101I Unbalanced (IBERDROLA)

[2] # Signal of communications failure with the control facility.
[3] 13,
[4] 0,1,0,0,0,1,
[5] 1,1,0,0,0,1,
[6] 2,1,0,0,0,1,
[7] 3,1,0,0,0,1,
[8] 4,1,0,0,0,1,
[9] 5,1,0,0,0,1,
[10] 6,1,0,0,0,1,
[11] 7,1,0,0,0,1,
[12] 8,1,0,0,0,1,
[13] 9,1,0,0,0,1,
[14] 10,1,0,0,0,1,
[15] 11,1,0,0,0,1,
[16] 12,1,0,0,0,1,# Link address, ASDU address,Interface104,
[17] 3,10007,1,
[18] # Port communications parameters
[19] 2,
[20] COM1,1200,e,8,1,1,
[21] COM2,1200,e,8,1,1,
[22] # TimeCDon,TimeCDoff,TimeRTSon,TimeRTSoff,SwCTS,SwCDTx,SwCDRx,
[23] # RTSAlwaysOn, TimeErrorTelem,TimePortNoActivo,NivelTraza,
[24] # TimeoutCambiosCommands(s),TimeoutSeleccion(s),TimeEntreConsignas(s),
[25] # RRLResetClase2,ToutEntreMsjTF(s),ToutTotalTF(s),MaxNumsecmPorSeccion,
[26] # TimeTomaACero,PermisoSincro,MaxReintSecc,MaxReintFich,ToutChar,
[27] 0,500,500,11,1,1,1,0,60,5,0,10,10,22,0,60,2100,5,10,1,2,2,0,
[28] # TamColaClase1,TamColaClase2,TamColaCommands,TamColaOrdenes,
[29] 1000,1000,10,3,
[30] # CCGestionaST,CCNotificaST,AjusteSync,FuenteSincro(0=Proto,1=GPS),
[31] # TimeSincroKO(sec),TimeSincroOK(sec),DiffTimeParaLanzarSincroSNTP,
[32] 1,1,0,0,2100,5,0,
[33] # ------------------------------------------------------------
[34] # TYPE OF OBJECT | ADDRESS RANGE
[35] # ------------------------------+------------------------------
[36] # Single Dig. St. | 00001 – 10000
[37] # Double Dig. St. | 10001 – 15000
[38] # Analog Measurements | 15001 – 20000
[39] # Tap position | 20001 – 25000
[40] # Int. Tot. Meas.(counters) | 25001 – 30000
[41] # Single commands | 30001 – 35000
[42] # double commands | 35001 – 40000
[43] # Analog set point | 40001 – 45000
[44] # Tap change commands | 45001 – 50000
[45] # System information | 60001 - 65535
[46] # ------------------------------+------------------------------
[47] ###############################################
[48] # SINGLE COMMANDS (ON=Pulse, OFF=Pulse) #
[49] ###############################################
[50] # NumOrdenes,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),OrdenConmutaFteSincro,
[51] 3,0,62501,
[52] #
Add101,DIR,ISE,DCO,DIRon,ISCon,DIRoff,ISCoff,DIRdesc,ISCdesc,TimeEspInfo
Ret,
[53] 30001,22,12,2,22,0,22,1,22,9,5,

M1CPTA2005I
1CPT: Substation Central Unit B-82
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[54] 30251,12,0,2,12,78,12,76,12,9,10,
[55] 30252,12,1,2,12,79,12,77,12,9,15,
[56] ###################
[57] # DOUBLE COMMANDS #
[58] ###################
[59] # NumOrdenes,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),
[60] 3,0,
[61] # Add101,DIR,ISEon,DCOon,ISEoff,DCOoff,DIRon,ISCon,DIRoff,ISCoff,
[62] # DIRdesc,ISCdesc,TimeEspInfoRet,
[63] 35001,12,0,2,1,2,12,80,12,0,12,4,5,
[64] 35002,12,6,2,7,2,12,81,12,0,12,4,10,
[65] 35003,12,8,2,9,2,12,82,12,0,12,4,15,
[66] ###################################
[67] # TAP CHANGE COMMANDS #
[68] ###################################
[69] # NumCommands,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),
[70] 2,0,
[71] # Add101,Dir,ISERaise,DCOraise,ISELower,DCOlower,MEAToma,TimeEspInfoRet,
[72] 45001,17,4,2,5,2,1,15,
[73] 45002,21,4,2,5,2,1,20,
[74] ######################################
[75] # SET POINT CHANGE COMMANDS #
[76] ######################################
[77] #NumCommandsAutom,TipoEjec(0=EJEC.DIRECTA,1=SEL+EJEC),ASDU,NumCommandsDir
ect,
[78] 2,0,50,2,
[79] #
Add101,DIR,ISERaise,DCOraise,ISELower,DCOlower,MEAConsigna,Paso,TimeEspIn
fRet,
[80] 40001,17,2,2,3,2,0,205,30,
[81] 40002,21,2,2,3,2,0,205,35,
[82] # Add101,DIR,ISM,MEAConsigna,TimeEspInfRet,UCSGestionaCmndTerm,
[83] 40003,10,0,0,5,0,
[84] 40004,11,0,0,10,0,
[85] ###################
[86] # SINGLE SIGNALS #
[87] ###################
[88] # NOTA: The address of the overflow signal is 60001. After this
[89] # comes the rest of system information signals:
[90] # 60002 -> Queue x% full.
[91] # 60003 -> File transfer active.
[92] # 60004 -> Periodic change.
[93] # 60005 -> RTU synchronized.
[94] # 60006 -> Synchronization source.
[95] # NumSignals,AddSignalOverflow,%Lleno,%Vacio,TimeCambioPeriodico(s),
[96] 3,60001,70,30,1440,
[97] # Add101,DIR,ISC,Neg,
[98] 1,10,0,0,
[99] 2,10,1,0,
[100]3,10,2,0,
[101]##################
[102]# DOUBLE SIGNALS #
[103]##################
[104]# NumSenalesDobles,
[105]3,1,
[106]# Add101,DIR,ISCoff,ISCon,ISCdesc,Neg,
[107]10001,22, 10,11,12,13, 0,
[108]10002,22, -1,14,15,-1, 0,

M1CPTA2005I
B-83 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[109]10003,22, 16,17,18,19, 0,
[110]#########
[111]# TAPS #
[112]#########
[113]# NumTomas,
[114]2,
[115]# Add101,DIR,MEA,UCSVigilaEstInterm,UsaValorTomaErronea,ValorTomaErronea,
[116]20001,17,1,0,0,0,// RTV IEC61850
[117]20002,21,1,1,1,0,1,63,// RTN Procome
[118]###########
[119]# MEASUREMENTS #
[120]###########
[121]# NumMeasurements,TimeCapturaMeasurements(s),TipoASDU,PorcentajeOverflow,
[122]4,2,13,1.0,
[123]#
Add101,DIR,MEA,Corr,Offset,Ope(6),VBA,PBA,Lmax,Lmin,Vmax,Vmin,FondoEscala
Sup,
[124]# FondoEscalaInf,UCSGestionaOverflow,
[125]15001,22,0,0.009768,80.0,1,0,0,0,0,0,0.02,0,0,0,0,0,4095,0,0,//VCON
Procome
[126]15002,23,1,0.032234,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,4095,-4095,0,//V
Procome
[127]15005,24,2,1.0,0.0,1,0,0,0,0,0,0.008,0,0,0,0,0,7.0,0.0,0, //I float
[128]15006,25,3,1.0,0.0,1,0,0,0,0,0,0.002,0,0,0,0,0,132.0,-132.0,0, //V float
[129]##############
[130]# COUNTERS #
[131]##############
[132]# NumCont,TiempoCapturaEspontanea(min),TiempoCapturaHistorico(min),
[133]# MinutoIniCapt,bCapturaInicial,
[134]4,60,60,1,1,
[135]# Add101,DIR,CON
[136]25001,22,0,
[137]25002,22,1,
[138]25003,22,2,
[139]25004,22,3,
[140]##############
[141]# IOAs RANGE #
[142]##############
[143]# EstSim,EstSist,EstDob,Med,Toma,Cont,OrdSim,OrdDob,OrdConsig,OrdPaso,
[144]1,60001,10001,15001,20001,25001,30001,35001,40001,45001,
[145]#
[146]############################################
[147]# SIGNAL ACTIVATION/DEACTIVATION MANAGEMENT #
[148]############################################
[149]# NumCambDesact,NumCambAct,TimeActDesac(s),
[150]0,5,5,
[151]####################
[152]# BALANCED DATA#
[153]####################
[154]# TipoEnlace(0=Bal;1=NoBal),DirTXFisica(0=A->B;1=B->A),ReintN2,TimeoutN2,
[155]0,0,3,1000,

M1CPTA2005I
1CPT: Substation Central Unit B-84
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.2.7 IEC101 Master Emulator Balanced/Unbalanced: M101B.CFG

In this file, “m101b.cfg”, data related to the balanced/ unbalanced IEC 870-5-101 emulator to
communicate with an RTU are configured: general data, commands (single and double),
contact type (single and double), measurements and counters. These commands, signals,
measurements and counters are referenced with a 101 protocol address (Dir101). Each of
these will be associated a command, signal, measurement or counter of the associated
equipment configured in dbase.cfg.

File format is as follows:

• Data of the RTU to Emulate
DirLINK , DirASDU , DirProcome , Reserva , TipoEnlace , NumReintentos ,

NivelTraza , DirEnlaceLength , DirAsduLength , DirObjLength , CotLength ,

• DirLINK: Link address of the RTU to emulate.

• DirASDU: Common ASDU address.
• DIrProcome: Procome address of the equipment. It must match the address of the
associated equipment, configured in dbase.cfg.
• Reserva: Old size of the link address field (TamLinkAdd): 1 or 2. Now It is configured
later. IT IS OBSOLETE: It is kept for compatibility with versions installed in the field.
• TipoEnlace: Indicates whether the link is Balanced (0) or Unbalanced (1). Default value is
Balanced.
• NumRetries: Number of retries of the messages sent to the RTU. The range is 1
onwards. If the values is 1 no retries occur. Default value is 3.
• NivelTraza: Value of the monitoring trace.
• DirEnlaceLength: Size in bytes of the link address (1 or 2).
• DirAsduLength: Size en bytes of the common ASDU address (1 or 2).
• DirObjLength: Size en bytes of the information Object address (1, 2 or 3).
• CotLength: Size in bytes of the transmission cause (1 or 2).

If nothing is configured, default values of the sizes above are:

Parameter Size
DirEnlaceLength 2
DirAsduLength 2
DirObjLength 3
CotLength 2

Ex: 111,111,126,0,0,3,0,2,2,3,2,

M1CPTA2005I
B-85 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Cyclic Procedure Timing Data

PeriodoSincro , PeriodoClass2 , PeriodoLectCont , TimeoutN7 , PeriodoRapidoClass ,

• PeriodoSincro: RTU synchronization period in seconds. By default: 0, meaning that

synchronizing messages are not sent.
• PeriodoClase2: Period for sending class 2 requests to the RTU, in seconds. It only has
meaning if TipoEnlace is Unbalanced. Possible values are -1, 0, 1..n. By default: 0.
• PeriodoLectCont: Period for reading RTU counters. It only has meaning if TipoEnlace is
Unbalanced. By default: 0.
• TimeoutN7: Timeout, in seconds, to send a RequestStatusLink as KeepAlive procedure
when the link level is idle. By default: 10 seconds.
• PeriodoRapidoClass: Fast period for sending class2 requests to the RTU, in milliseconds.
It only has meaning if TipoEnlace is Unbalanced. Possible values are -1,100..n. By
default: -1.

PeriodoClase2 and PeriodoRapidoClass parameters are related. They are only valid for
unbalanced mode. Both of them determine how often a Class2 request must be sent to the RTU
to collect the information available. The first is used to create a slow cycle, in seconds, in such a
way that the RTU does not become saturated. The second, on the contrary, is used when a
faster information updating cycle is required.

PeriodoClase2 is used for the first versions of the emulator and it predominates over the other.
If the value is set to 0, class2 requests are not sent (This value is not highly recommended
since remote control data will not be collected). If set to a value equal or greater than 1, it is
used as period to send class 2 requests to the RTU. An adequate value could be 1 or 2
seconds. If set to -1, it means this function is not used and the possibility of using the fast cycle
is open.

Si PeriodoClase2 is set to -1, PeriodoRapidoClass defines the class 2 request sending cycle to
the RTU. If set to -1, this function is not to be used. If a value equal or greater than 100 is set, it
is used as the period for sending class 2 requests to the RTU.

PeriodoClass2 PeriodoRapidoClass Ciclo

>0 x Slow cycle (seconds)
=0 x Class requests are not sent
-1 -1 Class requests are not sent
-1 >= 100 fast cycle (milliseconds)

Ex: 60,1,0,10,100,

M1CPTA2005I
1CPT: Substation Central Unit B-86
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Port Communications

Puerto , Veloc , TipoPar , NumBits , NumStop , TamañoFIFO ,

• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4.
• Veloc: Baud rate. It can take the values 600, 1200, 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can take the values ‘N’ or ‘n’ (none); ‘O’ or ‘o’, (odd number); ‘E’
or ‘e’, (even number).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. Possible values are 1 and 2.
• TamañoFIFO: Is the size of FIFO in bytes. Possible values are 1, 4, 8, 14 or 0 ( FIFO not
used). Default value is 1.

Ex: COM1,9600,e,8,1,1,

• General Time Data of Remote Control: [Line 13]

TimeWait , RTSon , RTSoff , CTS ,

• TimeWait: Delay time (in msec.) from the moment the transmission is due until RTS sets
to ON (provided RTSon is other than 0), or else, delay time (in msec.) from the moment
the transmission is due until the transmission begins (if RTSon is set to 0). Default value
is 0.
• RTSon: Delay time from the moment RTS sets to ON until transmission begins (in msec.).
Default value is 0, which means RTS will never set to ON and, therefore, the transmission
will start immediately after TimeWait times out.
WARNING: If the RTS control line is not to be used, setting this parameter to 0 is
mandatory.
• RTSoff: Delay time (in msec.) between the moment of transmission until RTS sets to
OFF. Default value is 0, which means the RTS line will not be used.
• CTS: Indicates whether the CTS line is checked (1) or not (0) before transmitting. Default
value is 0.

Ex: 0,0,0,0,

M1CPTA2005I
B-87 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Single Commands

Each protocol single command is associated two CPX/CPP commands. These commands will
be run through ASDU 45 (C_SC_NA_1: Single Command). It is essential to put Dir101s in
ascending order:

NumOrdenes , Ejec , ActTerm ,

Dir101 , ISEOn , ISEOff , (*)

(*) It repeats for each remote control single command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control single commands type ON=Pulse, OFF=Do

Nothing.
• Ejec: Indicates if these single commands (both ON=Pulse, OFF=Do Nothing and
ON=Pulse, OFF=Pulse) are to be run through DIRECT EXECUTE (0) or SELECT AND
EXECUTE (1) method. Default value is 1.
• ActTerm: Indicates whether COT ACTTERM must be received before the command can
be deemed completed. The value 1 indicates YES. The value 0 indicates NO. Value by
default, it is 0.
• Dir101: Address of 101 protocol single command.
• ISEOn: PROCOME label of the CPX/CPP On command.
• ISEOff: PROCOME label of the CPX/CPP Off command.

Ex: 2,1,0, // Num. Single commands, Ejec Type, ActTerm

33000,1,2,
33001,3,4,

• Configuration Data of Double Commands

Each protocol double command is associated two CPX/CPP commands. These commands will
be run through ASDU 46 (C_DC_NA_1: Double command). It is essential to put Dir101s in
ascending order:

NumOrdenes , Ejec , ActTerm ,

Dir101 , ISEOn , ISEOff , (*)

(*) This repeats for each remote control double command. There will be as many as indicated
under NumOrdenes. They will be arranged in ascending order of Dir101.

• NumOrdenes: Number of remote control double commands.

• Ejec: Indicates whether these double commands are to be run through DIRECT
EXECUTE (0) or SELECT AND EXECUTE (1) method. Default value is 1.
• ActTerm: Indicates whether COT ACTTERM must be received before the command can
be deemed completed. The value 1 indicates YES. The value 0 indicates NO. Value by
default, it is 0.
• Dir101: Address of 101 protocol double command.
• ISEon: PROCOME label of the CPX/CPP activation command of the double command
(close).
• ISEoff: PROCOME label of the CPX/CPP deactivation command of the double command
(open).

Ex: 1,1,0,//Num.ÓrdenesDobles,TipoEjec, ActTerm

30000,1,2,

M1CPTA2005I
1CPT: Substation Central Unit B-88
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Tap Commands

Presently these commands are not used and the number will be set to zero.

NumComandos ,

• NumComandos: Number of tap commands. It will be set to 0.

Ex: 0,//Num.ComandosRegulPaso,

• Configuration Data of Single Contact Signals

Each protocol signal of this type is associated a CPX/CPP digital signal. It is essential to put
Dir101s in ascending order:

NumSD , DirSeñalOV ,
Dir101 , ISC , Alr , (*)

(*) It repeats for each remote control single contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control single contact signals.

• DirSignalOV: Address of the signal that indicates that the data queue is full, namely,
overflow has occurred.
• Dir101: Address of 101 protocol single contact digital signal.
• ISC: PROCOME label of the CPX/CPP digital signal.
• Alr: Indicates if the signal is considered as alarm or not. In case it is an alarm, the slave
equipment will not send the change to zero, therefore it must be generated by the
CPX/CPP.

Ex: 2,0, // NumSD, Addr Signal Overflow,

1,1,0,
2,2,0,

• Configuration Data of Double Contact Signals

Each emulator signal of this type is associated three CPX/CPP digital signals. It is essential to
put Dir101s in ascending order:

NumSD ,
Dir101 , ISC_OFF , ISC_ON , ISCdesconocido , (*)

(*) It repeats for each remote control double contact signal. There will be as many as indicated
under NumSD. They will be arranged in ascending order of Dir101.

• NumSD: Number of remote control double contact signals.

• Dir101: Address of 101 protocol double contact signal.
• ISC_OFF: PROCOME label of the CPX/CPP digital signal indicating the OFF status
(open) of the double contact signal.
• ISC_ON: PROCOME label of the CPX/CPP digital signal indicating the ON status
(closed) of the double contact signal.
• ISCdesconocido: PROCOME label of the CPX/CPP digital signal that indicates double
contact signal unknown status.

Ex: 1, // NumSD
7000,16,17,18,

M1CPTA2005I
B-89 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Taps

Presently taps are not being used by the emulator and the number will be set to zero.

NumTomas ,

• NumTomas: Number of taps. It will be set to 0.

Ex: 0,

• Configuration Data of Measurements

Each protocol measurement is associated a CPX/CPP measurement. The CPX/CPP can
interpret the following types of measurements: Standard Measurement (ASDU 9:
M_ME_NA_1), Scaled Measurement (ASDU 11: M_ME_NB_1) and Floating Point
Measurement (ASDU 13: M_ME_NC_1). It is essential to put Dir101s in ascending order.

NumMeds ,
Dir101 , Med , Corrección , Offset , (*)

(*) It repeats for each protocol measurement. There will be as many as indicated under
NumMeds.

• NumMeds: Number of measurements. A maximum of 121 measurements can be

configured.
• Dir101: Address of 101 protocol measurement.
• Med: PROCOME label of CPX/CPP measurement.
• Corrección: Is the factor by which the measurement is multiplied to suit CPX/CPP internal
range. Default value is 1.0.
• Offset: Is the offset which must added to the measurement to suit CPX/CPP internal
range. Default value is 0.0.
Ex: 9, // Num. Measurements,
10000,0,1.0,0.0,
...
10008,8,1.0,0.0,

• Configuration Data of Set Point Change Commands

Presently set point commands are not used by the emulator and the number will be set to zero.

NumComandos ,

• NumComandos: Number of set point change commands. It will be set to 0.

Ex: 0,

M1CPTA2005I
1CPT: Substation Central Unit B-90
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Counters

Each protocol counter is associated a CPX/CPP counter. It is essential to put Dir101s in
ascending order.

NumConts , ModoLect , ModoFunc , PeriodoIntegCont ,

Dir101 , Med , Corrección , Offset , (*)

(*) It repeats for each protocol counter. There will be as many as indicated under NumConts.
They will be arranged in ascending order of Dir101.

• NumConts: Number of remote control counters.

• ModoLect: Counter read mode. Three methods can be used: Class_1 (1), Class_2 (2),
Counter interrogation request (3). Default value is 1 (Clase_1).
• ModoFunc: Indicates counter operating mode: With Reset (0) or without Reset (1).
Default value is 0 (With Reset).
• PeriodoIntegCounters: How often counters are integrated, namely, they are partially
accumulated. Value in minutes. By default it is set to 15.
• Dir101: Address of 101 protocol counter.
• CON: PROCOME label of CPX/CPP counter.
• Corrección: Is the factor by which the counter is multiplied to suit the CPX/CPP internal
range. Default value is 1.0.
• Offset: Is the offset which must added to the counter to suit CPX/CPP internal range.
Default value is 0.0.

Ex: 2,1,0,15, // Num. Counters

20000,0,1.0,0.0,
20001,1,1.0,0.0,

The table below shows ASDUs processed by the CPT.

ASDU Description
1 M_SP_NA_1: Single-point information without time tag
3 M_DP_NA_1: Double-point information without time tag
9 M_ME_NA_1: Measured value, normalized value
11 M_ME_NB_1: Measured value, scaled value
13 M_ME_NC_1: Measured value, short floating point number
15 M_IT_NA_1: Integrated totals
30 M_SP_TB_1:Single-point information with time tag CP56Time2a
31 M_DP_TB_1: Double-point information with time tag CP56Time2a
37 M_IT_TB_1: Integrated totals with time tag CP56Time2a
45 C_SC_NA_1: Single Command
46 C_DC_NA_1: Double Command
70 M_EI_NA_1: End of Initialization
100 M_IC_NA_1: Interrogation command
103 M_CS_NA_1: Clock synchronization command
199 M_LI_NA_1: Loss of information (private, AMPLA profile)

M1CPTA2005I
B-91 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # Configuration of RTU M101B

[2] # Address of RTU to emulate
[3] 111,111,126,2,0,3,0, // Link address, ASDU address,
FrameMaxLenght,
[4] # Cyclic procedure timing.
[5] 60,0,0,20,
[6] # Port communications parameters
[7] COM1,19200,e,8,1,1,
[8] # Time to set RTS to ON, time from RTS ON to tx (msec),
[9] # time from end of tx to set RTS to OFF (msec), Control CTS (on/off),
[10] 0,0,0,0,
[11] ####################
[12] # Single commands
[13] 2,1, // Num of single commands ON, Type of run,
[14] 33000,1,2,
[15] 33001,3,4,
[16] ####################
[17] 1,1, // Num. of double commands
[18] 30000,1,2,
[19] ####################
[20] # Tap change commands
[21] 0,
[22] ####################
[23] # Single signals
[24] 2,0,
[25] # Association of DIR101,ISC
[26] # it is essential to arrange DIR101
[27] # in ascending order
[28] 1,1,0,
[29] 2,2,0,
[30] ####################
[31] # Num. Nº Double CONTACT signals,
[32] 1,
[33] 7000,16,17,18,
[34] ####################
[35] # Taps
[36] # NumTomas,
[37] 0,
[38] ####################
[39] # NumMeasurements,
[40] 9,
[41] 10000,0,1.0,0.0,
[42] ...
[43] 10008,8,1.0,0.0,
[44] ####################
[45] # Set point change commands
[46] 0,
[47] ####################
[48] # Num. Counters, Freeze time in minutes, Time from freeze
[49] # to capture for sending, ResetCadaHora, ValorLimite, EnviaBitCY
[50] 2,1,0,15,
[51] # DIR 101 is the address of COUNTER type objects
[52] 20000,0,1.0,0.0,
[53] 20001,0,1.0,0.0,

M1CPTA2005I
1CPT: Substation Central Unit B-92
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.3 DNP3 Protocol: DNP3.CFG

In this file, called “dnp3.cfg” data related to the remote control is configured: general data,
orders, signals, measurements and meters. These orders, signals, measurements and meters
are referenced with one index. Each of the remote control’s orders, signals, measurements and
meters shall have an associated order, signal, measurement or meter from the CPX/CPP/CPT.
The file format is as follows:
• Configuration Data for Communications Failure Signal with the Remote
Control
This will be carried out as described under section A.1: [lines 3-4]. Nevertheless, two
communication failure signals are differentiated under this protocol:

- The first (ISC 0) will be communication failure at Application level.

- The second (ISC 1) will be communication failure at Link level.

This second signal is of high interest for communications via TCP/IP.

Ex: 2,
0,1,0,0,0, // Comm. Failure at Application level
1,1,0,0,0, // Comm. Failure at Link level

• Data regarding RTU Emulation: [Line 6]

DirRTUEm , DNP3TipoCom , DNP3PortTCPIP , DNP3KeepAlive , NumLAN ,
ul

NumTotInstanc , DNP3DirIp ,

• DirRTUEmul: Base Address of the RTU to be emulated.

• DNP3TipoCom: Type of Communication with Master. Three types of communications are
differentiated (series, TCP/IP and TCP/IP Multi-instanciable on the same address and
TCP port), but the last of these requires two different types of configurations, since one
single main instance must be compulsorily defined on the one hand, and none or various
secondary instances, on the other:
 0 = Coms. Serial Port. This will entail the communication via a COM port. It will be the
default value.
 1 = Coms. Via TCP/IP: This will entail communication via a local network, under
normal conditions, for a single DNP3 instance.
 2 = Coms. via Multi-instanciable TCP/IP, this being the only main instance. This will
be used when requiring various TCP simultaneous connections on a same address
and TCP port (which will be the TCP/IP address defined for the Central Unit under file
TCP.CFG).
There will only be one main instance, as against the possibility of many type 3
secondary instances.
Note: The name of this main DNP3 instance must be compulsorily “DNP3_2”.
 3 = Coms. via TCP/IP Multi-instanciable, this being one of the various secondary
instances possibilities.
This will also be used in the event that various TCP simultaneous connections on the
same address and TCP port, but, as against the main instance, various can be
defined of this kind.
The name of this secondary instance will be “DNP3_X”, where X will be a correlative
number as from number 3 (X=3, 4, 5...). This is advised in order to gain clarity, but it is
not compulsory, as against the name of the main instance.

M1CPTA2005I
B-93 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DNP3PortTCPIP: TCP/IP Port that is used for communications with the Master. As
regards DNP3 TCP/IP it has been defined with the value 20000. As IP address, the one
defined under file tcp.cfg is used.
• DNP3KeepAlive: This parameter indicates if the slave (CPX/CPP/CPT) forwards Keep
Alive type of messages (Request Link Status) to keep communication with Master active
after a period of inactivity with the same. The period of inactivity is determined by means
of parameter ErrorTel (defined further on). By default, it will be set to 0 (false), hence this
function will not be enabled.
• NumLAN: LAN number to be used for communication via TCP/IP. LAN addresses are
defined under file “TCP.CFG” and, for example, as regards CPT devices, which have two,
it will be 1 or else, 2. The default value is 1, associated to LAN1.
• NumTotInstanc: This field will only make sense when dealing with communications via
main TCP/IP multi-instanciable (in the case of DNP3TipoCom=2). This indicates the total
number of instances (both the main only one, and secondary) associated to this main
instance. In the rest of the cases, it must be configured to 0, as default value.
• DNP3DirIp: IP address of DNP3 slave. In the event that no address is configured, the IP
from the central unit (CPX) will be used, or that associated to the LAN adapter that has
been configured (CPT).

Ex. Coms Serie:4,0,20000,0,1,0,

Ex. Coms. TCPIP:4,1,20000,0,1,0, ,128.127.1.50,
Ex. Coms. TCPIP MultiInstancia Principal:4,2,20000,0,1,2,
Ex. Coms. TCPIP MultiInstancia Secundaria:4,3,20000,0,1,0,

• Configuration Data for Serial Communication with Master Station: [Line 8]

Although this must always be configured, it will only make sense if communication via serial port
is chosen subsequently.

Puerto , Veloc , TipoPar , NumBits , NumStop ,

This data shall always be configured, but it will only be used if communication is made through
serial port (TipoCom parameter).

• Puerto: Communication Port. Possible values are COM1, COM2 and COM3.
• Veloc: Baud rate. Possible values are 300, 600, 1200, 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can use values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number); ‘E’, ‘e’,
‘p’, ‘P’ (even number)..
• NumStop: Number of stop bits. Possible values are 1 and 2 bits.

Ex: COM1:4800,n,8,1,

M1CPTA2005I
1CPT: Substation Central Unit B-94
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Regarding Remote Control Timings: [Line 10]

RTSon , RTSoff , CDoff , ErrorTel , PermisoSincronizar ,

• RTSon: Timing that RTS is kept ON before transmitting (in msec.).

• RTSoff: Timing that RTS is kept OFF after transmitting (in msec.).
• CDoff: Waiting time for the activation of the carrier (in msec.).
• ErrorTel: Timing before issuing remote control error (in sec.).
• PermisoSincronizar (CPX/CPP-A/CPT model): Indicates if the control facility has permit
to synchronize with the Central Unit (1), or not (0). Only one control facility out of these
that are going to interrogate the Central Unit can set this parameter to 1. The rest will set
it to 0. If more than one protocol is configured as possible sources for synchronization,
the protocol that first starts-up at the Central Unit shall be the only one that will enable its
corresponding control facility to synchronize with the Central Unit.

Ex: 33,11,11,60,0,

• Data regarding the Address of the Master and the Level of Monitorization of
Traces: [Line 12]

DirMTU , NivelMonitor ,

• DirMTU: Address of the master.

• NivelMonitor: Level of monitorization of traces.

Ex: 1,0,

• Data regarding Retries at Link and Application Level: [Lines 14-16]

ReintentosN2? , NumReintentosN2 ,
ReintentosN7? , NumReintentosN7 ,

• ReintentosN2?: Bit that indicates if retries have been configured at link level (1) or not (0).
• NumReintentosN2: Number of retries at link level. This makes sense if the field
ReintentosN2? Is set to 1.
• ReintentosN7?: Bit that indicates if retries have been configured at application level (1) or
not (0).
• NumReintentosN7: Number of retries at application level. This makes sense if the field
ReintentosN7? Is set to 1.

Ex: 0,0,
1,3,

• Data regarding Confirmation Waiting Time: [Line 18]

TimeEspConfN2 , TimeEspConfN7 , TimeoutSelectMando , TimeoutSelect ,

EscrAna

• TimeEspConfN2: Maximum timing awaited for a confirmation at link level (in msec.).
• TimeEspConfN7: Maximum timing awaited for a confirmation at application level (in
msec.)
• TimeoutSelectMando: Timing that the selection of a command is kept before receiving
the activation message. After this time has lapsed, the command is deselected (in
seconds. Minimum value = 1 sec. Default value = 5 sec.).

M1CPTA2005I
B-95 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TimeoutSelectEscrAna: Timing that the analogical output write is maintained before

receiving the activation message. After this time has lapsed, the analogical output write is
deselected. (in seconds. Minimum value = 1 sec. Default value = 5 sec.).

Ex: 1000,1000,5,5,

• Configuration Data for Remote Control Orders

A CPX/CPP/CPT command is associated to each of the remote control orders: [lines 20-26]

NumOrdenes , MandosDobles ,

• NumOrdenes: Number of orders defined in the remote control.

• MandosDobles: If this parameter is set to 1, this indicates that the commands that are
going to be configured are double commands. If it is set to 0, they will be simple
commands. Parameters associated to each of the commands depend on this value and
are described below.

If the commands are simple commands (MandosDobles = 0):

Index , DirEq , EtiqISE , (*)

(*)This is repeated for each of the remote control orders. There will be as many as indicated
under NumOrdenes

• Index: Index of the remote control order.

• DirEq: Address of the device that the command belongs to within the Central Unit’s
database.
• EtiqISE: Identifier of the CPX/CPP/CPT command.

Ex: 52,0, // Num. commands

0,25,12,
1,25,9,
2,18,12,
...
51,13,9,

If commands are double commands (MandosDobles = 1):

Index , Doble Code1 , DirEq1 , EtiqISE1 , Dco1 ,

Code2 , DirEq2 , EtiqISE2 , Dco2 , (*)

This is repeated for each of the remote control orders. There will be as many as indicated under
NumOrdenes.

• Index: Index for the remote control orders.

• Doble: Indicates if it is a double command (1), i.e., if it admits activation and deactivation
codes, or, on the contrary, if it is a simple command (0), i.e., only admits one code:
activation or deactivation. In the first case, both commands must be configured, i.e. all the
parameters in the line. In the second, only those corresponding to the first command will
be configured.
• Code1: Code for the first command received by communication from the master.
• DirEq1: Address of the device that the first command within the database of the Central
Unit belongs to.

M1CPTA2005I
1CPT: Substation Central Unit B-96
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• EtiqISE1: Identifier of the first command from the CPX/CPP/CPT.

• Dco1: Code for the first command that is going to be forwarded to the device that is going
to carry out the same.
• Code2: Code for the second command received by communication from the master.
• DirEq2: Address of the device that the second command within the database of the
Central Unit belongs to.
• EtiqISE2: Identifier of the second command from the CPX/CPP/CPT.
• Dco2: Code for the second command that is going to be forwarded to the device that is
going to carry out the same.

If the command has been configured as double command (Double =1), when an order is
received from the master with the CODE=Code1 value, command DirEq1-EtiqISE1-Dco1 will be
implemented. If, on the contrary, an order with CODE=Code2 value is received, the other
command will be implemented: DirEq2-EtiqISE2-Dco2.

If the command is simple (double=0), the command DirEq1-EtiqISE1 will be implemented,

whatever the CODE value received from the master. In this case, there is a peculiarity, if the
Dco1=255 parameter is received, then the DCO that is forwarded to the relay is the value of the
CODE field received from the master by communication (the value depends on the DNP3
master configuration). If Dco1 parameter is other than 255, this value will be taken as DCO to
be forwarded to the relay.

Ex: 3,1, // Num. orders

0,0,1,25,12,2,
1,1,129,25,9,2,65,25,11,2,
2,1,129,18,12,2,65,18,17,2,

• Configuration Data for Remote Control’s Digital Signals

A digital signal from CPX/CPP/CPT is associated to each of the digital signals from the remote
control: [lines 28-34]

NumSeñales MaxCambISC ,
Index , DirEq , EtiqISC , (*)

(*) This is repeated for each signal from the remote control. There will be as many as
indicated under NumSeñales.

• NumSeñales: Number of digital signals defined in the remote control.

• MaxCambISC: Maximum number of digital signal changes. By omission, its default value
is 300.
• Index: Remote control’s signal index.
• DirEq: Address of the device that the signal within the Central Unit’s database belongs to.
• EtiqISC: Identifier of the CPX/CPP/CPT’s digital signal.

Ex: 608,300, // Num. Signals, MaxCambISC

0,25,65,
1,25,66,
2,25,40,
...
607,13,0,

M1CPTA2005I
B-97 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data on Remote Control Measurements

A measurement from the CPX/CPP/CPT will be associated to each of the remote control’s
measurements: [lines 36-42]

NumMedida , CfgSeg , Variation ,

s ScanMed Number
Index , DirEq , EtiqMEA , Banda , FactorA , FactorB , (*)

(*) This is repeated for each of the remote control’s measurements. There will be as many as
indicated under NumMedidas.

• NumMedidas: Number of measurements defined in the remote control.

• CfgSegScanMed: Number of seconds to undertake the measurement Scan.
• VariationNumber: Indicates the format in which measurement changes are sent to the
master. Possible values are: 2 = 16-bit without time; 4 = 16-bit with time. Default value is
4.
• Index: Index that represents the remote control’s measurement in question. These values
must start at zero and must be consecutive in ascending order, with no gaps and they
must not be repeated.
• DirEq: Address of the device that the measurement belongs to within the Central Unit’s
database.
• EtiqMEA: Identifier of this measurement from the CPX/CPP/CPT.
• Banda: Band value, when determining a change. Changes in measurement are only
forwarded if the change exceeds the value of the band.
• Factor A: Escalating factor A, when forwarding to the Remote Control.
• Factor B: Escalating factor B, when forwarding to the Remote Control.

Ex: 157,20, // Num. Measurement, acc. Measurement Scan

0,18,3,10,1.0,0.0,
1,18,4,12.3,25.34,0.0,
2,18,5,10,1.0,0.0,
...
156,13,2,10,2.0,0.0,

To configure the functionality of the forwarding of date and hour to the master, the data required
is described in the following table:

Data DirEq EtiqMEA

Year -257 0
Month -257 1
Day -257 2
Hour -257 3
Minute -257 4
Second -257 5

M1CPTA2005I
1CPT: Substation Central Unit B-98
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Base don a specific object (index) address, the above six elements will be configured, in the
same order and without leaving gaps. These values do not generate changes and are only
forwarded to the master when requested by the photo (Analog Inputs or Class 0), hence the
Band and ScaleFund parameters are not used.

Ex: 157, // Num. measurements

0,18,3,1.000000,0,
...
81,-257,0,4095,1,
82,-257,1,4095,1,
83,-257,2,4095,1,
84,-257,3,4095,1,
85,-257,4,4095,1,
86,-257,5,4095,1,
...
156,13,2,1.000000,0,

• Configuration Data for the Remote Control Meters

A meter from the CPX/CPP/CPT is associated to each of the remote control meters: [lines 44-
46]

NumConts ,
Index , DirEq , EtiqCON , (*)

(*)This is repeated for each of the remote control meters. There will be as many as
indicated under NumConts.

• NumConts: Number of meters defined for the remote control

• Index: Index that represents the remote control’s meter in question. These values must
start at zero and must be consecutive in ascending order, with no gaps and they must not
be repeated.
• DirEq: Address of the device that the meter belongs to within the Central Unit’s database.
• EtiqCON: Identifier of the CPX/CPP/CPT meter.

Ex: 1,// Num. Meters

0,16,17,

M1CPTA2005I
B-99 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Remote Control Data Associated to Sending Class 1 Changes

From 03.15 version (July 2012) certain parameters have been added that have substantially
modified the way to configure Changes by Class.

NumDatosClass1 , TipoDefC1 ,
Index , TipoC1 , (*)

(*) It repeats for each information associated to class 1. There will be as many as indicated
under NumInfoClase1.

• NumDatosClase1: Number of data associated to sending class 1 changes.

Notice: If set to 0, it means all digital signals will be sent to the remote control for
compatibility with old configurations, regardless of the set value of TipoDefC1.
• TipoDefC1: declaration of the type of data by default associated to Class 1.
1 = Digital signals
2 = Measurements
• Index: Index (DNP3 address) of the data in question associated to class 1.
• TipoC1: Type of the data in question associated to class 1.
1 = Digital signals.
2 = Measurements.

Important Note: DIFFERENT TYPES OF DATA MAY NOT BE MIXED IN THE SAME CLASS.

With these new parameters, there are different configuration options:

• Use the old configuration under which all the digital signals were sent for the sake of
compatibility.
Ex1: 0,1,// Class1: sending ALL digital signals

• Certain digital signals are sent, which must be configured.

Ex2: 4,1,// Class1: sending 4 specific digital signals
0,1,// ISC_DNP3_0, signal,
3,1,// ISC_DNP3_3, signal,
16,1,// ISC_DNP3_16, signal,
25,1,// ISC_DNP3_25, signal,

• Certain measurements are sent, which must be configured.

Ex3: 5,2,// Class1: sending 5 specific measurements
0,2,// MEA_DNP3_0, measurement,
3,2,// MEA_DNP3_3, measurement,
16,2,// MEA_DNP3_16, measurement,
25,2,// MEA_DNP3_25, measurement,
38,2,// MEA_DNP3_38, measurement,

M1CPTA2005I
1CPT: Substation Central Unit B-100
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Remote Control Data Associated to Sending Class 2 Changes

From the 03.15 version (July 2012) certain parameters have been added which have
substantially modified the way to configure Changes by Class.

NumDatosClass2 , TipoDefC2 ,
Index , TipoC2 , (*)

(*) It repeats for each information associated to class 2. There will be as many as indicated
under NumInfoClase2.

• NumDatosClase2: Number of data associated to sending class 2 changes.

Note: If set to 0 all measurements will be sent to the remote control, for compatibility with
old configurations, regardless the value assigned to TipoDefC2.
• TipoDefC2: Declaration of the type of data associated to Class2.
1 = Digital signals
2 = Measurements
• Index: Index (DNP3 address) of the data in question associated to class 2.
• TipoC1: Type of the data in question associated to class 2.
1 = Digital signals
2 = Measurements.

Important Note: DIFFERENT TYPES OF DATA MAY NOT BE MIXED IN THE SAME CLASS.

With these new parameters, there are different configuration options:

• Use the old configuration under which all the digital signals were sent for the sake of
compatibility.
Ex1: 0,2,// Class2: sending ALL the measurements

• Certain digital signals are sent, which must be configured.

Ex2: 4,1,// Class2: sending 4 specific digital signals
5,1,// ISC_DNP3_5, signal,
6,1,// ISC_DNP3_6, signal,
16,1,// ISC_DNP3_16, signal,
17,1,// ISC_DNP3_17, signal,

• Certain measurements are sent, which must be configured.

Ex3: 5,2,// Class1: sending 5 specific measurements
11,2,// MEA_DNP3_11, measurement,
12,2,// MEA_DNP3_12, measurement,
13,2,// MEA_DNP3_13, measurement,
21,2,// MEA_DNP3_21, measurement,
22,2,// MEA_DNP3_22, measurement,

M1CPTA2005I
B-101 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Remote Control Data Associated to Sending Class 3 Changes

From the 03.15 version (July 2012) certain parameters have been added which have
substantially modified the way to configure Changes by Class.

NumDatosClass3 , TipoDefC3 ,
Index , TipoC3 , (*)

(*) It repeats for each information associated to class 3. There will be as many as indicated
under NumInfoClass3.

• NumDatosClass3: Number of data associated to sending class 3 changes.

Note: If NumDatosClass3 is set to 0 and TipoDefC3 is set to 2 (measurements) all
measurements will be sent to the remote control. If TipoDefC3 were not set to 2, nothing
will be sent as is the case for old configurations.
• TipoDefC3: declaration of the type of data associated to class 3.
1 = Digital signals
2 = Measurements
• Index: Index (DNP3 address) of the data in question associated to class 3.
• TipoC3: Type of the data in question associated to class 3.
1 = Digital signals
2 = Measurements

Important note: DIFFERENT TYPES OF DATA MAY NOT BE MIXED IN THE SAME CLASS.

With these new parameters, there are different configuration options:

• Use the old configuration under which all the digital signals were sent for the sake of
compatibility.
Ex1: 0,2,// Class3: sending ALL the measurements

• Certain digital signals are sent, which must be configured.

Ex2: 4,1,// Class3: sending 4 specific digital signals
0,1,// ISC_DNP3_0, signal,
1,1,// ISC_DNP3_1, signal,
4,1,// ISC_DNP3_4, signal,
5,1,// ISC_DNP3_5, signal,

• Certain measurements are sent, which must be configured.

Ex3: 5,2,// Class3: sending 5 specific measurements
0,2,// MEA_DNP3_0, measurement,
1,2,// MEA_DNP3_1, measurement,
2,2,// MEA_DNP3_2, measurement,
8,2,// MEA_DNP3_8, measurement,
9,2,// MEA_DNP3_9, measurement,

M1CPTA2005I
1CPT: Substation Central Unit B-102
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Activation/Deactivation of the Remote Control based

on the Status of the other Remote
The other “remote” will inform as regards the status it is in and, based on a signal that
synthesizes this status, the decision will be made as to whether to activate or deactivate the
DNP3 task.

HabActivo , TimeElim , TimeEspEval , DirISC , IscISC , NegISC ,

Desact Cmb ISCAct Activ Activ Activ

• HabActivoDesact: Indicates if this function is enabled (1), or not (0). If it is not, the DNP3
task will always be active.
• TimeElimCmb: Timing in seconds that a change in the Temporary Pending Changes
must remain in the queue when the DNP3 task is in Inactive status.
• TimeEspEvalISCAct: Timeout for in seconds before starting the DNP3 task, in order to
“give time” to the other remote to start-up and have the status that the other remote is in
after the start-up, to be able to decide if this task must be started in active or inactive
mode.
• DirISCActiv: Address of the device that the indicative signal belongs to, which stipulates if
the remote must be commuted to the active status if it was not in the latter, or, which is
the same thing, that the “other remote” is inactive. This signal will be calculated in the
logia, based on other signals.
• IscISCActiv: Index of the signal that indicates that the remote has to be commuted to the
active status if it were not in the latter, or, which is the same thing, that the “other remote”
is inactive.
• NegISCActiv: Negation of the signal that indicates that the remote must be commuted to
the active status.

M1CPTA2005I
B-103 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Remote Control Analog Output Writes

Note: Analog output writes can only be configured for CPX-B and CPT relays from dnp3.dll version 03.07.

Each remote control analog output write is associated a CPX/CPT analog output write: [lines
56-61]

NumEscrsAna ,
Index , DirEq , EtiqISM , Pendiente , Origen , (*)

(*) This repeats for each remote control analog output write. There will be as many as
indicated under NumEscrsAna.

• NumEscrsAna: Number of
remote control remote
control analog output
writes.
• Index: Index of the remote
control analog output write.
• DirEq: Address of the
equipment that the
CPX/CPT analog output
write belongs to.
• EtiqISM: PROCOME label
of the CPX/CPT analog
output write.
• Pendiente (a): Slope of the
conversion line (by default
is 1). Refer to Figure B.1.
• Origen (b): Origin of the
conversion line (by default
is 0). Refer to Figure.
Figure B.2: Analog Output Write Conversion Line.

Engineering_Value = ( Value_Sent_Remote Control * Pendiente ) + Origin

Ex: 18, // Num. analog output writes

0,16,0,1.0,0.0,
1,18,14,1.5,-7.5,
2,18,15,0.5,10,
...
17,25,0,

M1CPTA2005I
1CPT: Substation Central Unit B-104
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # Configuration of RTU DNP3

[2] # Number of ISCs
[3] 2,
[4] 0,1,0,0,0,// Coms. failure at Application level
[5] 1,1,0,0,0,// Coms. failure at Link level
[6] # RTU address to be emulated
[7] 4,0,20000,0,1,0,
//DirRTU,TipoComs,PortTCPIP,KeepAlive,NumLAN,NumTotInstancSock
[8] # Communication parameters
[9] COM1,4800,n,8,1,
[10] # RTS on , RTS off,CD off , Remote Control Error
[11] 33,11,11,60,
[12] # MTU address, Monitorization Level
[13] 1,0,
[14] # Retries N2 (yes, no), Num of retries
[15] 0,0,
[16] # Retries N7 (yes, no), Num of retries
[17] 1,3,
[18] # Waiting time confirm N2,Idem N7 in ms.
[19] 1000,1000,5,5,
[20] # Orders
[21] 52, // Num. orders (commanmds)
[22] # Index assoc, DIR, ISE
[23] 0 ,25,12, // ORDER OPEN DJ-352 REMOTE CONTROL,
[24] 1 ,25,9, //ORDER CLOSE DJ-352 REMOTE CONTROL,
[25] 2 ,18,12, //ORDER OPEN DJ-222 REMOTE CONTROL,
[26] …
[27] 51 ,13,9, // ORDER CLOSE DJ-212 REMOTE CONTROL,
[28] # Signals
[29] 608,300,// Num. Señales, MaxCambISC
[30] # Index association to DIR, ISC
[31] 0 ,25,65, // 13 DISJUNCTOR COUPL. 3090
[32] 1 ,25,66, // 13 DISJUNCTOR COUPL. 3090
[33] 2 ,25,40, // 13 SECTIONALIZER COUPL. 3090ª
[34] …
[35] 607 ,13,0, // 13 TRAFO-2 BUSBAR VOLTAGE
[36] # Measurements
[37] 157,20, // Num. Measurements, CfgSegScanMedDNP3
[38] # Index association to DIR, MED, Scale Fund, band %,
[39] 0 ,18, 3,10,1.0,0.0, // CURRENT MEASUREMENT A
[40] 1 ,18, 4,20,1.0,0.0, // CURRENT MEASUREMENT B
[41] 2 ,18, 5,30,1.0,0.0, // CURRENT MEASUREMENT C
[42] …
[43] 156 ,13, 2,10,1.0,0.0, // VOLTAGE MEASUREMENT C
[44] # Meters
[45] 1, // Num. of meters
[46] # index to DIR,CON
[47] 0,16,17,
[48] # Class 1
[49] 3,1,// Class1: Sending 3 specific digital signals
[50] 4,1, // ISC_DNP3_4, signal,
[51] 7,1, // ISC_DNP3_7, signal,
[52] 16,1, // ISC_DNP3_16, signal,
[53] # class 2
[54] 5,2,// Class2: sending 5 specific measurements

M1CPTA2005I
B-105 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[55] 11,2, // MEA_DNP3_11, measurement,

[56] 12,2, // MEA_DNP3_12, measurement,
[57] 13,2, // MEA_DNP3_13, measurement,
[58] 21,2, // MEA_DNP3_21, measurement,
[59] 22,2, // MEA_DNP3_22, measurement,
[60] # class 3
[61] 0,2,// Class3: sending ALL the measurements
[62] #index,
[63] 1,5,60,256,5,0,
//HabActivDes,TimeElimCmb,TimeEspEvalISCAct,ISCActiv(dir,isc,neg)
[64] # Analog output writes
[65] 18, // Num. analog output writes
[66] 0,16, 0,1.0, 0.0,
[67] 1,18,14,1.5,-7.5,
[68] 2,18,15,0.5, 10,
[69] ...
[70] 17,25,0,
[71]

M1CPTA2005I
1CPT: Substation Central Unit B-106
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.4 DNP3 Protocol in Master Mode: DNP3MS.CFG

Common data regarding the interrogation of level 1 devices using protocol DNP3 is configured
under this file called “dnp3ms.cfg”: The file format is as follows:
• Master Data
DirMaestra , NivelMonitor ,

• DirRTUEmul: Address of the CPX/CPP/CPT as master.

• NivelMonitor: Level of monitorization of traces.

Ex: 100,1,

• Configuration Data for Communications with Level 1 Device

This data will only be used when Level 1 device is connected to one of the CPX/CPP/CPT‘s
serial ports. If devices are connected to optic fibre ports, the configuration parameters for these
ports will be configured under the puertos.cfg file. [line 4]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications port. Possible values are COM1 and COM2.

• Veloc: Baud rate. The following values can be applied: 300, 600, 1200, 2400, 4800, 9600,
19200 and 38400 baud.
• TipoPar: Type of parity. It can apply values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’, ‘e’, ‘p’, ‘P’ (even number).
• NumStop: Number of stop bits. Possible values are 1 and 2 bits.

Ex: COM2,4800,n,8,1,

• Communication Data for Timing with the Device

RTSon , RTSoff , CDoff ,

• RTSon: Timing that indicates that RTS is maintained ON before transmitting (in msec.).
• RTSoff: Timing that indicates that RTS is maintained OFF after transmitting (in msec.).
• CDoff: Waiting time for deactivation of the carrier (in msec.).

Ex: 66,11,11,

M1CPTA2005I
B-107 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Concerning Retries at Link and Application Level

ReintentosN2? , NumReintentosN2 ,
NumReintentosN7 , MaxTamBufTX MaxTamBufRX ,

• ReintentosN2?: Bit that indicates if retries are configured at link level (1) or not (0).
• NumReintentosN2: Number of retries at link level. It makes sense if the ReintentosN2?
field is set to 1.
• NumReintentosN7: Number of retries at application level.
• MaxTamBufTX: Size of the transmission buffer. This is the maximum number of
characters that can be transmitted in the application layer. The minimum value is 249 and
by default, it is 255. This parameter affects all the DNP3 master ports in the same
manner.
• MaxTamBufRX: Size of reception buffer. It is the maximum number of characters that can
be received in the application layer. The minimum value is 512, and by default, the value
is 2048. This parameter affects all the DNP3 master ports in the same manner.

Ex: 0,0,
1,255,2048,

• Data Regarding Waiting Times for Confirmation of Messages Forwarded

TimeEspConfN2 , TimeEspConfN7 ,

• TimeEspConfN2: Maximum timing that a response is awaited at link level (in msec.).
• TimeEspConfN7: Maximum timing that a response is awaited at application level. If
speed is slow and/or the device holds a lot of data, this timing will have to be increased
because the forwarding timing for all the data through the series line will have to be taken
into account. (in msec.).

Ex: 1000,4000,

• Data Regarding Various Timings

RetMsgBrdcst , IntervRefrescoSen , TipoSincro ,

• RetMsgBrdcst: Delay timing awaited after forwarding a broadcast message before

sending a new message (in msec.).
• IntervRefrescoSen: Period of time awarded for signal refresh requests (CLASS 0) to level
1 devices (in seconds).
• TipoSincro: If value is 0, synchronization is broadcast. If value is 1, synchronization is
specific for that device.

Ex: 50,60,1,

M1CPTA2005I
1CPT: Substation Central Unit B-108
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Regarding the Interrogation Procedure for each Port

NumPort ,
PortNum , InterC0 , InterC1 , InterC2 , InterC3 , InterBI , InterBIC ,

InterAI , InterAIC , HUSC1 , HUSC2 , HUSC3 ,

InterCounter , Sincro , (*)

(*) It will be repeated for each port that has DNP3 devices connected. There will be as many
lines as indicated under NumPort.

• NumPort: Number of ports with DNP3 devices connected. The desired interrogation
procedure must be defined for each of the ports.
• PortNum: Port number wherein the interrogation procedure defined by the rest of the
parameters in the line is going to be applied.
• InterC0: If value differs from 0, the type of interrogation is effected by means of CLASS0
message requesting data. If value is 0, this interrogation does not take place.
• InterC1: If value differs from 0, the type of interrogation is made through the CLASS1
message requesting data. If value is 0, this interrogation does not take place.
• InterC2: If value differs from 0, the type of interrogation is made through CLASS2 request
for data message. If value is 0, this interrogation does not take place.
• InterC3: If value differs from 0, the type of interrogation is made through CLASS3 request
for data message. If value is 0, this interrogation does not take place.
• InterBI: If value differs from 0, the type of interrogation is made through the message
requesting Binary Entries. If value is 0, this interrogation does not take place.
• InterBIC: If value differs from 0, the type of interrogation is made through a message
requesting changes in Binary Entries. If value is 0, this interrogation does not take place.
• InterAI: If value differs from 0, the type of interrogation is made through a message
requesting Analogical Entries. If value is 0, this interrogation does not take place.
• InterAIC: If value differs from 0, the type of interrogation is made through a message
requesting Changes in Analogical Entries. If value is 0, this interrogation does not take
place.
• HUSC1: If value is 1, the unsolicited messages are enabled for Class1 data. If value is 0,
this enabling does not take place.
• HUSC2: If value is 1, the unsolicited messages are enabled for Class2 data. If value is 0,
this enabling does not take place.
• HUSC3: If value is 1, the unsolicited messages are enabled for Class3. If value is 0, this
enabling does not take place.
• INterCounter: Indicates the way counter interrogation is made. If set to 0 it is through
Frozen Counter. If set to 1 it is through current values (Binary Counter). Default value: 0.
• Sincro: Indicates whether port synchronization is enabled (Value 0) or not (Value 1). If not
enabled, synchronizations are not sent to any of the port equipment. By default: Value 0.

Fields InterC0 to InterAIC (Inter#, in generic mode), support complex configuration to enable
different interrogation modes. The CPT has two periodic interrogation cycles: Refresh and
Changes. The period of the first can be configured through IntervRefrescoSen, and the second
is a continuous cycle. Each of the fields above control the request to be used in each cycle.
Depending on the values assigned to each of the fields, the request will be associated to one or
both cycles. These fields are construed as bit fields. The value 0 indicates the request is not
used.

M1CPTA2005I
B-109 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The DNP3 protocol enables, among other, two ways to interrogate the equipment: one generic
way by which the equipment associates individual data to generic data: CLASS0 for static data
and CLASS1, CLASS2 and CLASS3 for data changes and other way by which the master
interrogates for specific data: Binary Input (BI) and Analog Input (AI) for static data and Binary
Input Change (BIAC) and Analog Input Change (AIC) for data changes.

The CPT can associate each request to one or both cycles by allocating different values to
different fields. Three possibilities exist for the sake of compatibility with older equipment:
Standard Interrogation (INT_STANDARD=1), in the Refresh cycle (INT_REFRESCO=2) or in
the Changes cycle (INT_CHANGES=4). The setting value of the Inter# parameters above will
be given by the combination, through the OR function, of the selected interrogation cycles.

In the Standard mode, the Refresh cycle is associated the CLASS0 requests, Binary Input (BI)
and Analog Input (AI); and the Changes cycle is associated the CLASS1, CLASS2, CLASS3
requests, Binary Input Change (BIAC) and Analog Input Change (AIC). In order to be able to
activate these interrogation modes the applicable fields will be set to 1. This is the compatibility
mode with older equipment and the one to be used by default.

If requests are to be mixed in different cycles, another bit must be “activated” in this field. Thus
for example: if the master is to interrogate for Class 0 both in the Refresh cycle and changes
cycle, InterC0 must be set to 5 (INT_STANDARD | INT_CHANGES). If the master is to
interrogate for Binary Input Changes both in the Changes cycle and the refresh cycle, InterBIC
must be set to 3 ((INT_STANDARD | INT_REFRESCO).

Ex: 2,
1,1,1,1,0,0,0,0,0,0,0,0,0,0,
2,0,0,0,0,1,1,1,1,0,0,0,0,0,

In the example, there are two ports with DNP3 equipment connected. Ports are 1 and 2. An
interrogation procedure is defined for all the equipment in that port. Thus, port 1 is used to
interrogate for Class 0 for signal refresh and for Class1 and Class 2 for changes; port 2 is used
to interrogate for Read Binary Input (BI) and Analog Input (AI) for signal refresh and Read
Binary Input Change (BIC) and Analog Input Change (AIC) for changes.

Below is another example:

Ex: 2,
1,1,0,0,0,0,0,0,0,1,1,0,0,0,
2,1,1,1,0,5,1,5,1,0,0,0,0,0,

Port 1 is used to interrogate for Class 0 for signal refresh and Unsolicited Class 1 (HUSC1) and
Class 2 (HUSC2) are enabled for changes. Port 2 is used to request for Class0, BI and AI for
signal refresh and for Class1, Class2, BI, BIC, AI and AIC for Changes cycle.

M1CPTA2005I
1CPT: Substation Central Unit B-110
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on The Interrogation Procedure for Individual Equipment

NumEquip ,
DirEquipo , Obj_BI , Var_BI , Qual_BI , Obj_AI , Var_AI , Qual_AI ,

Obj_BIC , Var_BIC , Qual_BIC , Obj_AIC , Var_AIC ,

Qual_AIC , (*)

(*) This repeats for each Equipment whose individual cycle is to be configured. There will be
as many lines as indicated under NumEquip.
• NumEquip: Number of equipment whose interrogation cycle is to be configured. The
interrogation procedure must be defined for each equipment.
• DirEqupo: Address of the equipment to be configured. It must match an address
configured indbase.cfg.
• Obj_BI: Value of the object used for interrogation of Binary Inputs. Default value: 1
(BINARY_INPUT)
• Var_BI: Value of the variation used in for interrogation of Binary Inputs. Possible values
are:0 = VAR_ALL, 1 = VAR_SINGLE_BIT, 2 = VAR_WITH_STATUS. Default value is 0:
VAR_ALL.
• Qual_BI: Value of Qual field in the interrogation of Binary Inputs. Default value: 6
(QUAL_ALL).
• Obj_AI: Value of the object used for interrogation of Analog Inputs. Default value: 30
(ANALOG_INPUT).
• Var_AI: Value of the variation used in interrogation of Analog Inputs. Possible values are:
0 = VAR_ALL, 1 = VAR_ANALOG_32BITS, 2 = VAR_ANALOG_16BITS, 3 =
VAR_ANALOG_32B_WO_FLAG, 4 = VAR_ANALOG_16B_WO_FLAG. Default value is
0: VAR_ALL.
• Qual_AI: Value of the field Qual in the interrogation of Analog Inputs. Default value: 6
(QUAL_ALL).
• Obj_BIC: Value of the object used for interrogation of Binary Input Changes. Default
value: 2 (BINARY_CHANGE)
• Var_BIC: Value of the variation used for the interrogation of Binary Input Changes.
Possible values are: 0 = VAR_ALL, 1 = VAR_CHANGE_WITHOUT_TIME, 2 =
VAR_CHANGE_WITH_TIME, 3 = VAR_CHANGE_WITH_REL_TIME. Default value is 0:
VAR_ALL.
• Qual_BIC: Value of the field Qual in the interrogation of Binary Input Changes. Default
value: 6 (QUAL_ALL).
• Obj_AIC: Value of the object used for interrogation of Analog Input Changes. Default
value: 32 (ANALOG_CHANGE)
• Var_AIC: Value of the variation used for the interrogation of Analog Input Changes.
Possible values are: 0 = VAR_ALL, 1 = VAR_ANALOG_32B_WO_TIME, 2 =
VAR_ANALOG_16B_WO_TIME, 3 = VAR_ANALOG_32B_WITH_TIME, 4 =
VAR_ANALOG_16B_WITH_TIME. Default value is 0: VAR_ALL.
• Qual_AIC: Value of the field Qual in the interrogation of Analog Input Changes. Default
value: 6 (QUAL_ALL).

Ex: 2,
10,1,0,6,30,0,6,2,1,6,32,1,6,
20,1,1,6,30,1,6,2,1,6,32,0,6,

M1CPTA2005I
B-111 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The example below shows how the complete file looks like. The values configured here are
given only as an example and must not taken as reference for configuration. If in doubt, the
default values in the text above must be taken.

[1] # Central address as MTU

[2] 100,1,
[3] # Communications parameters
[4] COM2,4800,n,8,1,
[5] # RTS on , RTS off,CD off
[6] 60,11,11,
[7] # Retries N2 (yes, no),Num retries
[8] 0,0,
[9] # Num retries
[10] 1,255,2048,
[11] # Timeout confirmation N2,Idem N7 in ms
[12] 1000,4000,
[13] 50,60,1,
[14] 2,
[15] #NmPort,C0,C1,C2,C3,BI,BIC,AI,AIC,HUSC1,HUSC2,HUSC3,InterCounter, Sincro,
[16] 1,1,1,1,0,0,0,0,0,0,0,0,0,0,
[17] 2,0,0,0,0,1,1,1,1,0,0,0,0,0,
[18] # Config individual cycles of equipment
[19] 2,
[20] # DirEquipo,Obj_BI,Var_BI,Qual_BI,Obj_AI,Var_AI,Qual_
[21] # AI,Obj_BIC,Var_BIC,Qual_BIC,Obj_AIC,Var_AIC,Qual_AIC,
[22] 10,1,0,6,30,0,6,2,1,6,32,1,6,
[23] 20,1,1,6,30,1,6,2,1,6,32,0,6,

M1CPTA2005I
1CPT: Substation Central Unit B-112
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.5 Slave MODBUS Protocol: MODBUS.CFG

Configuration file for the slave MODBUS task. This file contains all parameters required to
communicate with a master via the MODBUS RTU protocol.

The file allows two configuration modes. They differ in the configuration of the own virtual
signals. In the old format, only one block of own digital signals is configured, with only one
signal. In the new format, other blocks of digital signals and measurements that can be updated
from SCADA through the applicable functions are configured.

These blocks refer to own signals of the virtual equipment MODBUS. Formerly, this equipment
had a digital signal associated to the master communications status (1= FAILURE; 0=OK) and
now more digital signals can be defined that are updated through function 15. The first signal
(index 0), is still reserved for master communications status.

Own MODBUS equipment analog signals can also be defined that are updated b SCADA
through function 16 (PresetMultipleRegister).

Both digital signals and measurements can be used as input signals in other tasks and
modules.

Below is the old format:

• [BLQ 1.0] Data to configure Own Slave MODBUS Task Signals (Master
Communications Failure Signal)

NumISCs ,
ISC , Alarma , F_activ , F_desactiv , Neg , Bocina , (*)

(*) It repeats for each device digital signal. There will be as many as shown in NumISCs.

• NumISCs: Number of digital signals of the device (1 in this case).

• ISC: PROCOME label of the signal in question.
• Alarma: Alarm bit that indicates whether the signal is considered alarm (1) or not (0).
• F_activ: Activation filter bit that indicates whether signal activation is considered an event
(0) or not (1).
• F_desac: Deactivation filter bit, that indicates whether signal deactivation is considered
an event (0) or not (1).
• Neg: Alarm negation bit that indicates whether to consider an alarm when the signal
takes the value of 1 (0) or when it takes the value 0 (1).
• Bocina: Horn bit that indicates whether the horn sounds (1) or not (0) upon signal
activation, provided it is considered as alarm (alarm bit set to 1). This bit will or will not
appear in the corresponding file depending on the version of the executable.

Ex: 1,
0,1,0,0,0,1,

M1CPTA2005I
B-113 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

New format is as follows:

• [BLQ 1.1] General Data of the Virtual Equipment In Question

N_ISC , N_ISE , N_ISS , N_MEA , N_CON ,

• N_ISC: Number of Digital signals (ISC) of the Modbus equipment.

• N_ISE: Number of Commands (ISE) of the Modbus equipment. This parameter must be
set to 0 (zero).
• N_ISS: Number of Output Writes (ISS) of the Modbus equipment. This parameter will be
configured to 0 (zero)
• N_MEA: Number of Measurements (MEA) of the Modbus equipment.
• N_CON: Number of Counters (CON) of the Modbus equipment. This parameter will be
configured to 0 (zero).

Ex: 9,0,0,2,0,// Number of each type of signal.

• [BLQ_1.2] Configuration data of Modbus Digital Signals

They are configured as described in section A.1:

Ej: 10,//Num. Signals

0,0,1,1,0,0,
1,0,1,1,0,0,
2,0,1,1,0,0,
…
9,0,0,0,0,0,

• [BLQ 1.3] Configuration data of Modbus Digital Outputs

A line will be configured with the value 0.

Ex: 0,//Num. Commands

• [BLQ 1.4] Configuration data of Modbus Digital Outputs

A line will be configured with the value 0.

Ex: 0,// Num. Digital outputs

• [BLQ 1.5] Configuration data of Modbus Measurements

They are configured as described in section A.1:

Ex: 2,//Num. Measurements

1.0,0.0,
1.0,0.0,

• [BLQ 1.6] Configuration data of Modbus Counters

A line will be configured with the value 0:

Ex: 0,//Num. Counters

M1CPTA2005I
1CPT: Substation Central Unit B-114
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on the Address of the Central Unit Slave: [Line 7]

DirEsclavo , TipoComModbus ,

• DirEsclavo: Address of the central unit slave. It is the address of the slave that must be
included in master requests transmitted to the central unit.
• TipoComModbus: Indicates the type of communication used to connect to the
RemoteControl: 0 = Serial, 1 = MODBUS TCP or 2 = MODBUS over TCP/IP. (Namely,
MODBUS RTU encapsulated in packets TCP/IP). The default value is 0, this is, via serial
port.

Ex: 14,0,//ModbSerie (by default)

or
14,1, //ModbusTCPIP
or
14,2, // ModbusSobreTCP

• [BLQ 3] Port Communications Data: Three Cases are distinguished: Serial

Port Communications, Modbus TCP Communications and Modbus over
TCP/IP Communications. [Line 9]
A. Serial Port Communications:

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Puerto: Communications port. Normal values are COM1 and COM2, but in case
communications are through the Terminal Server, the associated serial virtual port can be
defined here, beginning with the letter ‘V’ (e.g., V201,V202,…,V209). .
• Veloc: Baud rate. it can take the values 600, 1200, 2400, 4800, 9600, 19200 and 38400
bauds.
• TipoPar: Type of parity. It can use values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’,‘e’, ‘p’, ‘P’ (even number).NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. It can take the values 1 and 2.

Ex: # Data Serial Port Com

COM1,9600,n,8,1,
or
V201,19200,P,8,1,

B and C. Communications Modbus TCP or Communications over TCP/IP.

Puerto , DirIP , NumLAN , NetMask ,

In these two cases associated to a TCP/IP port, two new parameters will be defined instead of
the ones related to the serial communications port.

• Puerto: TCP port used to connect to the master. The default value is 502.
• DirIP: IP address of the interface to be used to communicate with the MODBUS master. If
this parameter is not configured, the IP address of the CPT will be used.
• NumLan: Number of the CPT’s LAN adapter used to communicate with the MODBUS
control facility. By default, the central default LAN adapter is selected.
• NetMask: Network mask applied to DirIP. If not configured, the default value is
255.255.0.0. [This parameter exists since emulator version 03.02]

M1CPTA2005I
B-115 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: # Datos Com. TCP/IP

502,128.127.60.1, 1,255.255.0.0,

• General Data to communicate with the Master: [Line 11]

TimeWait , RTSon , RTSoff , TimeoutComs , NivelMonitor ,

• TimeWait: Time elapsed (in msec.) from the moment the transmission is due until RTS
switches to ON (provided RTSon is other than–1), or time elapsed (in msec.) from the
moment the transmission is due until the transmission is started (if RTSon equals–1).
Default value is 0.
• RTSon: Time RTS keeps to ON before transmission (in msec.). Default value is –1,
which means RTS will not ever switch to ON so it will be transmitted immediately after
TimeWait times out.
ATTENTION: If the RTS control line is not to be used, this parameter must be set to
-1.
• RTSoff: Time elapsed (in msec.) from the transmission until RTS switches to OFF.
Default value is –1, which means that the RTS line will not be used. As a general rule it
is configured to –1 if RTS has been configured to –1, but this time can also be configured
to a value other than –1, RTSon having been configured to –1: it would be used to make
the salve wait this time RTSoff after transmitting (the RST would switch to OFF after this
time times out, status in which it already was after setting RTSon to -1).
ATTENTION: This parameter cannot be set to–1 if RTSon has been set to a value
other than –1, as the RTS will always be ON.
• TimeoutComs: Time (in sec.) the central unit must be without receiving a correct
message to issue a master communications error, that is, to generate the signal of
master communications failure configured in this same file. Default value is 60 seconds.
• NivelMonitor: Trace monitoring level. Default value is 0.

Ex: 0,-1,-
1,60,0,

• [BLQ 5] Data on Digital Signals by which the Master Interrogates the Central
Unit: Lines 13-17]

NumDigitales , OffsetValidacISCs , NegValidacISCs ,

DirModbusISC , Dir , ISC , NegISC , (*)

(*) It repeats for each digital signal handled by the master. There will be as many as shown in
NumISCs.

These signals must be read with MODBUS function 2 (READ INPUT STATUS).

• NumISCs: Number of digital signals to be handled by the master.

ATTENTION: In specific occasions this value must compulsorily be multiple of 16.
In this case, a number of signals are declared “extra” until the defined figure is
reached, said lines being declared as device signals –1, and ISC –1.
• OffsetValidacISCs: Offset to locate the addresses of validation of the ISC signals, as this
data is requested as if they were proper signals, through Modbus Function 02. This value
will be added to the address of the first defined ISC (DirModbusISC1), to locate the
address of the beginning of the first validation associated to the first ISC signal. From
now on validations will be correlative as with the ISCs that they are associated to.
For example: DirValidaciónISC1 = DirModbusISC1 + OffsetValidacISCs.

M1CPTA2005I
1CPT: Substation Central Unit B-116
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Offset default value is 0, in case the validations are not implemented through Function
02, but otherwise the same value as NumISCs is set, for said validations to go “behind”
the signals themselves, although this criterion is only for guidance.
ATTENTION: This value must be higher than the Modbus Address of the last ISC
signal, as otherwise signal overlapping will occur.
OffsetValidacISCs > DirModbusISC1 + NumISCs
• NegValidacISCs: Negation of ISC signal validation. In case the value is one, the value of
said validations is reversed at the time of sending via communications.
• DirModbusISC: MODBUS address of the digital signal (decimal).
ATTENTION: Signals must begin with zero, must be arranged in ascending order of
MODBUS address and be consecutive..
• Dir: Address of the device the digital signal belongs to.
• ISC: Label of the digital signal.
• NegISC: Negation of the specific ISC signal, for sending via communications.

Ex: 256,256,1, // NumISCs,OffsetValidacISCs,NegValidacISCs,

0,1,0,0, // DirModbusISC1,Dir1,Isc1,NegISC1,
1,2,0,0,
2,2,2,0,
3,2,3,0,
.....
255,19,9,0,

• [BLQ 6] Data on Master Commands: [Lines 19-21]

NumISEs ,
DirModbusISE , Dir , ISE , (*)

(*) It repeats for each master command. There will be as many as shown in NumISEs.

These commands will be executed with MODBUS function 5 (FORCE SINGLE COILS).

• NumISEs: Number of master commands. Default value is 0.

• DirModbusISE: MODBUS address of the command (decimal). 2 commands may have the
same MODBUS address. In this case, the first command will be executed with COIL to
ON (0xFF00) and the second with COIL to OFF (0x0000). In case there is only one
command with this address, this will be executed always with COIL to ON. In order to
clarify the COIL ON and OFF concepts, refer to “Modicon Modbus Protocol Reference
Guide”.
ATTENTION: Commands must be arranged in ASCENDING order of the MODBUS
address, with no need for said addresses to be consecutive.
• Dir: Address of the device that the command belongs to.
• ISE: Command label.

Ex: 2, // Num. Commands

512,1,0, // Command 1
513,1,1, // Command 2

M1CPTA2005I
B-117 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• [BLQ 7] Data on Measurements by which the Master can interrogate the

Central Unit: Lines 24-27]
NumMEAs , OffsetValidacMEAs , NegValidacMEAs , FuncEspPetMEAs ,
DirModbusMEA , Dir , MEA , FactorA , FactorB , (*)

(*)It repeats for each measurement handled by the master. There will be as many as shown in
NumMEAs.

These measurements can be read with the MODBUS function 4 (READ INPUT REGISTERS),
and function 3 (READ HOLDING REGISTERS). ATTENTION: If the same function is used to
request both measurements and counters, mixed information MAY NOT be sent. Namely,
measurement information and counter information may not be sent together in the same
packet.

• NumMEAs: Number of measurements to be handled by the master. Default value is 0.

ATTENTION: In specific occasions this value must compulsorily be multiple of 16.
In this case, excess measurements are declared until reaching the defined number.
Filler measurements will be declared as equipment –1 measurements, and MEA -1.
• OffsetValidacMEAs: Offset to locate the addresses of validation of the Measurements, as
this data is requested as if they were proper signals, through Modbus Function 02. This
value will be added to the address of the first defined ISC (DirModbusISC1), to locate the
address of the beginning of the first validation associated to the first measurement. From
now on validations will be correlative as with the MEAs they are associated to.
For example: DirValidaciónMEA1 = DirModbusISC1 + OffsetValidacMEAs.
Offset default value is 0, in case the validations are not implemented through Function
02.
ATTENTION: This value must be higher than the Modbus Address associated to the
validation of the Last ISC signal, as otherwise signal overlapping will occur.
(OffsetValidacMEAs > DirModbusISC1 + OffsetValidacISCs + NumISCs)
• NegValidacMEAs: Negation of the validation of MEAs Measurements. In case the value
is one, the value of said validations is reversed at the time of sending via
communications.
• FuncEspPetMEAs: Special Modbus Function to be used to request for Measurements.
By default or omission, it will be set to the standard value READ_ANALOG_INPUT(4).
• DirModbusMEA: MODBUS address of the measurement (decimal).
ATTENTION: Measurements must be arranged in ASCENDING order of the
MODBUS address, with no need for said addresses to be consecutive.
• Dir: Address of the device the measurement belongs to.
• MEA: Measurement label.
• FactorA: Multiplier factor to scale the measurement 1.0.
• FactorB: Additive value to scale the measurement converting it into the range expected
by the master. It is a floating point value that by default is set to 0.0.

Value_Sent_Remote Control = Internal_Value * FactorA + FactorB

M1CPTA2005I
1CPT: Substation Central Unit B-118
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 4,512,1,4, //
NumMEAs,OffsetValidacMEAs,NegValidacMEAs,FuncEspPetMEAs,
8192,1,0, 1.0,0.0,// DirModbusMEA1,Dir1,Mea1,Fa,Fb,
8193,1,1, 1.0,0.0,// Measurement 2
8194,2,0, 1.0,0.0,// Measurement 3
8195,2,1, 1.0,0.0,// Measurement 4

• [BLQ 8] Data on Counters by which the Master can interrogate the Central
Unit: Lines 29-33]

NumCONs , OffsetValidacCONs , NegValidacCONs , NumBytesCON , Func ,

EspPet
CONs
DirModbusCON , Dir , CON , (*)

(*) It repeats for each counter handled by the master. There will be as many as shown in
NumCONs.

These measurements can be read with the MODBUS function 4 (READ INPUT REGISTERS),
and function 3 (READ HOLDING REGISTERS). ATTENTION: If the same function is used to
request both measurements and counters, mixed information MAY NOT be sent. Namely,
measurement information and counter information may not be sent together in the same
packet

• NumCONs: Number of counters to be handled by the master. Default value is 0.

ATTENTION: In specific occasions this value must compulsorily be multiple of 16.
In this case, a number of counters are declared until the defined figure is reached,
these counters being declared as device counters –1, and CON –1.
• OffsetValidacCONs: Offset to locate the addresses of validation of the Counters, as this
data is requested as if they were proper signals, through Modbus Function 02. This value
must be added to the address of the first defined ISC (DirModbusISC1), to locate the
address of the beginning of the first validation associated to the first Counter. From now
on validations will be correlative as with the CONs they are associated to.
For example: DirValidaciónCON1 = DirModbusISC1 + OffsetValidacCONs.
Default value is 0.
ATTENTION: This value must be higher than the Modbus Address associated to the
validation of the Last MEA signal, as otherwise signal overlapping will occur.
(OffsetValidacCONs > DirModbusISC1 + OffsetValidacMEAs + NumMEAs)
• NegValidacCONs: Negation of the validation of CONs Counters. In case the value is one,
the value of said validations is reversed at the time of sending via communications.

M1CPTA2005I
B-119 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumBytesCON: Number of Bytes of the Counters. Two possible values are differentiated:
2 Byte Counters (Integer) and 4 Byte Counters (Long value). In the latter case, it must be
taken into account that as the Modbus protocol uses the integer as basic communication
unit, two Modbus addresses must be reserved to define a single counter. This is why, that
in this case, said Modbus Addresses would be all even or all odd (See Example 2
attached). Default value is 2 (See Example 1 attached).
• FuncEspPetCONs: Special Modbus function to be used for Counter request. By default
or omission it is set to the standard value READ_HOLDING_REGISTER(3).
• DirModbusCON: MODBUS address of counter (decimal).
ATTENTION: Counters must be arranged in ASCENDING order of the MODBUS
address, with no need for said addresses to be consecutive.
ATTENTION: In case NumBytesCON is 4, these addresses must be defined as all
even or all odd (See Example 2 attached).
• Dir: Address of the device that the counter belongs to.
• CON: Counter label.

Ex1: 4,3000,0,2,3,,
/NumCONs,OffsetValidacCONs,NegValidacCONs,NumBytesCON,
FunEspPetCONs

8320,1,0, // DirModbusCON1 (integer)

8321,1,1, // Integer Counter 2
8322,2,0, // Integer Counter 3
8323,2,1, // Integer Counter 4

For 4 byte counters.

Ex2: 4,3000,0,4,3

//NumCONs,OffsetValidacCONs,NegValidacCONs,NumBytesCON,FunEsp
PetCONs,
8320,1,0, // DirModbusCON1 (Long )
8322,1,1, // Counter Long 2
8324,2,0, // Counter Long 3
8326,2,1, // Counter Long 4

• [BLQ 9] Data on Analog Commands that can be Run by the Master

Analog output writes, or analog commands that can be carried out by the MODBUS master are
defined in this block. ISMs must belong to LEVEL 1 equipment.

NumISMs ,
DirModbusISM , Dir , ISM , (*)

(*) This repeats for each command run by the master. There will be as many as indicated
under NumISMs.

These commands are run with the MODBUS function 6 (PRESET SINGLE REGISTER).

M1CPTA2005I
1CPT: Substation Central Unit B-120
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumISMs: Number of analog commands that can be run by the master. By default is 0.
• DirModbusISM: MODBUS address of the analog command (decimal).
ATTENTION: Commands must be arranged in ascending order of the MODBUS
address.
• Dir: Address of the equipment that the command belongs to.
• ISM: Label of the analog command of the level 1 equipment.

Ex: 2, // Num. Commands

52,1,0, // Command 1
53,1,1, // Command 2

• [BLQ 10] Data on the digital signal status allocation block of virtual MODBUS
equipment
In this block the way to handle the digital signals of MODBUS equipment is defined.

DirIniModbus , NumSeñales , ISCIni ,

These signals are handled by 15 (FORCE MULTIPLE COILS) MODBUS signals.

• DirIniModbus: MODBUS address of the beginning of the digital signal block. These
addresses must be different from the ones defined in block [BLQ 5]
• NumSignals: Number of digital signals to be handled.
• ISCIni: Starting ISC of the virtual MODBUS equipment where digital signal statuses are to
be mapped. NOTE: Reserve at least the first digital signal for communications failure with
the master.

Ex: 1000,23,10,

• [BLQ 11] Data on the Digital Signal Value Allocation Block of Virtual
MODBUS Equipment
In this block the way to handle analog signals of the MODBUS equipment is defined.

DirIniModbus , NumSeñales , MEAIni ,

These signals are handled by 16 (PRESET MULTIPLE REGISTER) MODBUS signals.

• DirIniModbus: MODBUS address of the beginning of the analog signal block. These
addresses must be different from the ones defined in the block [BLQ 7].
• NumSignals: Number of digital signals to be handled.
• MEAIni: Starting MEA of the virtual MODBUS equipment where analog signal values are
to be mapped.

Ex: 2000,5,0,

M1CPTA2005I
B-121 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The complete file becomes as follows:

[1] # MODBUS.CFG file for the Configuration of the slave MODBUS task
[2] #
[3] # Signal data of virtual MODBUS equipment 20,0,0,10,0
[4] # Digital signals
[5] 20,
[6] 0,1,0,0,0,1,
[7] 1,0,0,0,0,0,
[8] 2,0,0,0,0,0,
[9] 3,0,0,0,0,0,
[10] 4,0,0,0,0,0,
[11] 5,0,0,0,0,0,
[12] 6,0,0,0,0,0,
[13] 7,0,0,0,0,0,
[14] 8,0,0,0,0,0,
[15] 9,0,0,0,0,0,
[16] 10,0,0,0,0,0,
[17] 11,0,0,0,0,0,
[18] 12,0,0,0,0,0,
[19] 13,0,0,0,0,0,
[20] 14,0,0,0,0,0,
[21] 15,0,0,0,0,0,
[22] 16,0,0,0,0,0,
[23] 17,0,0,0,0,0,
[24] 18,0,0,0,0,0,
[25] 19,0,0,0,0,0,
[26] # Commands
[27] 0,
[28] # output writes
[29] 0,
[30] # Measurements
[31] 10,
[32] 1.0,0.0,
[33] 1.0,0.0,
[34] 1.0,0.0,
[35] 1.0,0.0,
[36] 1.0,0.0,
[37] 1.0,0.0,
[38] 1.0,0.0,
[39] 1.0,0.0,
[40] 1.0,0.0,
[41] 1.0,0.0,
[42] # Counters
[43] 0
[44] # Central Unit slave address
[45] 14,
[46] # Communications data
[47] COM1,9600,n,8,1,
[48] # General data of master communications
[49] 0,-1,-1,60,0,
[50] # Digital signals
[51] 3,1000,1,// NumISCs, OffsetValidacISCs,NegValidacISCs
[52] 0,1,0,// Addr MODBUS, Addr, ISC
[53] 1,2,0,
[54] 2,2,2,
[55] # Commands
[56] 2, // Num. Commands
[57] 512,1,0,// Addr MODBUS, Addr, ISE

M1CPTA2005I
1CPT: Substation Central Unit B-122
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[58] 513,1,1,
[59] # Measurements
[60] 3,2000,1,// NumMEAs, OffsetValidacMEAs,NegValidacMEAs
[61] 8192,1,0,// Addr MODBUS, Addr , MEA
[62] 8193,1,1,
[63] 8194,2,0,
[64] # Counters
[65] 3,3000,1,2, // NumCONs, OffsetValidacCONs, NegValidacCONs,
NumBytesCON
[66] 8320,1,0,// Addr MODBUS, Addr, CON
[67] 8321,1,1,
[68] 8322,2,0,
[69] # Configuration of analog commands -
[70] 2,
[71] 52,1,0,
[72] 53,1,0,
[73] # Configuration of the digital signal handling block
[74] 1000,23,10,
[75] # Configuration of the analog signal handling block
[76] 2000,5,0,
[77]

M1CPTA2005I
B-123 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.6 Master MODBUS Protocol: MODBUSMS.CFG

Through this file, named “modbusms.cfg” master MODBUS data are configured: overall
parameters, ISCs, ISEs, MEAs and CONs of logic devices and digital inputs, digital outputs,
analog inputs and accumulator registers of the different modules to be mapped on said ISCs,
ISEs, MEAs and CONs respectively. The file has the following format:
• Port Communications Data
This section allows configuring the communications interface to be used in CPX/CPP/CPT to
establish the link with the slave device MODBUS, and thus the MODBUS protocol used in this
communication. Presently, two types of interface- MODBUS protocol can be configured:

- Serial channel with MODBUS serial protocol

- Ethernet channel with MODBUS - TCP protocol

For MODBUS-Serial communication, this section is configured through the following line of
parameters:

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications port. Possible values are:

- Serial ports: COM1, COM2, COM3 and COM4 (although COM3 and COM4 are only
valid for CPX relays).
- Fiber Optic ports: P1 and P2 (associated to CPT’S p3 and p4 ports respectively).
ATTENTION: In this case, port parameters are not defined here, but in the
PUERTOS.CFG file.
- Virtual Terminal Server Ports: V201,V202, …, V219.
• Veloc: Baud rate. Can take the values 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can take the values ‘N’ or ‘n’ (none), ‘O’ or ‘o’ (even), ‘E’ or ‘e’
(odd), ‘M’ or ‘m’ (mark) and ‘S’ or ‘s’ (space).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. It can take the values 1 and 2.

Ex: COM1,19200,I,8,1,
or P1,
or V201,19200,I,8,1,

In case of MODBUS-TCP communications this section is configured through the following

parameter line:

DirIPSlave , PortTCPSlave , NumLAN , IsMODBUSSobreTcpIP ,

• DirIPSlave: Is the TCP-IP address of the MODBUS-TCP slave the MODBUS-TCP master
is to be connected to.
• PortTCPSlave: TCP port available in the MODBUS-TCP slave for the Master to establish
the TCP/IP connection.
• NumLAN: LAN number to be used for the communications via TCP/IP. In case of CPT
devices two LAN ports are available identified by indexes 1 and 2, the default value being
index 1 associated to LAN1. For CPX devices, this parameter must be set to 1.
• IsMODBUSSobreTcpIp: Indicates whether the MODBUS protocol is MODBUS over
TCP/IP (1) or MODBUS TCP/IP (0). Default value is 0 (MODBUS TCP/IP).
Ex: 192.168.194.36,80,1,0,

M1CPTA2005I
1CPT: Substation Central Unit B-124
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• General Master Data

RTSon , RTSoff , TimeRX , NumReint , NivelMonitor ,

• RTSon: Time that RTS remains set to ON before transmitting (in msec.) in case of the
SERIAL MODBUS. This parameter will be used as timeout before sending a new
message to the MODBUS slave in case of the MODBUS-TCP.
• RTSoff: Time that RTS remains set to OFF after the transmission (in msec.) in case of the
SERIAL MODBUS. This parameter is used as timeout after sending each message to the
MODBUS slave in case of the MODBUS-TCP.
• TimeRX: RTU reception timeout (in msec.). Valid for all messages but broadcast
messages, in which case ToutSincroBroadcast is taken.
Note: For RFL equipment, a timeout of at least 200ms must be configured (recommended 300ms), in
case there is only one RFL equipment in the facility, or 700ms (recommended 1500ms), in case there are
two RFL equipment. If there are more RFL equipment connected, the minimum timeout value that
guarantees a correct communication must be determined.
• NumReint: Number of communication attempts with the device.
• NivelMonitor: Trace monitoring level.
Ex: 0,0,500,2,0,

• Master Time Data

TimeExplMed , TimeExplCon , TimePulso , TimeExpGenerico , …

… TimeSincro , TimeEsperaTrasReset , ToutSincroBroadcast , …
... TimeExpEntDig , HabPetPermMed ,

• TimeExplMed: Measurement exploration time (in sec.). It states how often measurement
exploration takes place.
• TimeExplCon: Counter exploration time (in sec.). It states how often counter exploration
takes place.
• TimePulso: Command pulse time (in msec.). In case of SEPAM, this value must be very
low, as it is the time between “Select” and “Operate” writes, and must be set only to 50
msec.
• TimeExpGenerico: This parameter is not used currently.
• TimeSincro: Device synchronisation time (in sec.). Incorporated in SEPAM devices.
Default value is 25 seconds.
• TimeEsperaTrasReset: Timeout after the loss of communications with SEPAM, NP-800
and AMS-7001 devices. It also applies to the start of CPX/CPP/CPT. This setting is
expressed in seconds. During this time, CPX/CPP/CPT keeps “keep-alive”
communications with the relay to guarantee that, when this time times out, relay DBs are
ready with actual device data. Default value is 60 seconds (1 minute).
• ToutSincroBroadcast: Timeout for the reception of synchronisation broadcast messages.
Default value is 22 msec.
• TimeExpEntDig: Digital input exploration time (in sec.). States how often digital signals
are explored in SEPAM, NP-800 and AMS-7001 devices.
• HabPetPermMed: This parameter allows enabling permanent measurement request to
the MODBUS slave, and also, it disables automatically periodic measurement requests.

Ex: 20,60,50,0,25,60,22,0,0,

M1CPTA2005I
B-125 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• RTU Data

DirPrimerEqLog ,
NumRTUs , TipoDeRTUs , ModoDeTransmisión ,

• DirPrimerEqLog: Address of the first equivalent logic device within the Central Unit
database.
• NumRTUs: Number of RTUs to be incorporated as devices.
• TipoDeRTUs: Type of RTU. Can be T-DAM(0), Generic(1), Micom(2), Sepam(3), NP-
800(4), CMS-7004(5), AMS-7001(6) or RFL(7). T-DAM by default.

RTU Type Configuration value

T_DAM 0
GENERICO 1
MICOM 2
SEPAM 3
NP-800 4
CMS-7004 5
AMS-7001 6
RFL 7

By default it will be set to 0, namely, T-DAM type.

• ModoDeTransmision: Transmission mode used. Possible values are RTU(0) or ASCII(1).

RTU by default.

Ex: 100,
4,0,0,

• Individual Equipment Configuration

Data of the equipment to be interrogated by the CPT/CPX are configured. There will be as
many blocks as indicated under NumRTUs.

For MODBUS equipment, two blocks must be configured. In the first block the parameters
related to the logic equipment to be incorporated into the database are configured. In the
second block, the parameters required to map MODBUS signals to database signals are
configured.

In view of the great variety of MODBUS equipment profiles existing in this signal mapping block,
it varies from another, so that different formats are established as a function of model /
manufacturer of the equipment. Some equipment can be configured on the basis of generic
profile whereas specific profiles have been defined for other equipment.

M1CPTA2005I
1CPT: Substation Central Unit B-126
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Logic Equipment Related Data

These parameters describe the logic equipment as well as other parameters specific to
MODBUS equipment.

Dir , N_ ISC , ISC Max , N_ ISE , ISE Max , N_ ISS , ISS Max , N_ MEA ,

N_ CON , DirEq , ISC , ISC Fail , Puerto , N_ISM ,

Remoto Remoto

TipoDe , FormatoM ,
RTU edidas

• Dir: RTU address. The address of the equivalent logic device will be (DirPrimerEqLog +
Dir).
• N_ISC: Number of RTU digital signals.
• ISCMax: Highest label of any ISC of the RTU in question.
• N_ISE: Number of RTU commands.
• ISEMax: Highest label of any ISE of the RTU in question.
• N_ISS: Number RTU output writes RTU.
• ISSMax: Highest label of any ISS of the RTU in question.
• N_MEA: Number of RTU measurements.
• N_CON: Number of RTU counters.
• DirEqRemoto: Address of the device of the ISC that states the RTU is in Remote Control
mode. It can be its own address or the address of other device, such as “logica” device.
• ISCRemoto: ISC of the device defined in the above column that defines whether the RTU
being configured is in remote control mode. This ISC [DirEqRemoto, ISCRemoto] must
be active for the execution of remote commands.
• ISCFail: Identifier of the command failure signal. In this case said ISC belongs to the RTU
that is being configured at this time.
• Puerto: Serial communications port used to communicate with the RTU. Possible values
are COM1 and COM2. In case no value is configured for this parameter, the port COM1
will be taken as default.
• Note: This parameter is not used in 32bit equipment (CPX and CPT). Nevertheless, it must be given a
value, recommended to be the same as for the previously configured serial port (e.g. COM1).
• N_ISM: Number of RTU analog output writes (only available for Generic type RTUs).
• TipoDeRTU: Type of RTU. In case the value is different from the previously read
TipoDeRTUs, the value of TipoDeRTU prevails.
NOTE: This parameter is only useful for CMS-7004 and AMS-7001 relays, since these are the only types
of equipment which are allowed to share the same serial port. In all other cases, all equipment
connected to the same serial port must be of the same type.
• FormatoMediddas: Indicates if these measurements will be dealt with at database level
as 16 bit integer values with sign (0) or as floating point values (1). By default is set to 0.
Depending on the format of equipment measurements, a conversion is made that may
result in loss of accuracy. For example, if the equipment sends 32 bit measurements that
are stored in a 16 bit register, information may be lost if the value of this measurement is
greater than 32637.

M1CPTA2005I
B-127 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex:Example1:
The ISC that determines whether the device is set to Remote Control mode is of its
own. Specifically ISC [1,21].1, 65,64, 16,15, 1,0, 6, 1, 1,21, 0, , 0, 0,
0,

Example2:
The ISC that determines whether the device is set to Remote Control mode is defined
in the “logica” device. Specifically ISC [256,504].
1, 65,64, 16,15, 1,0, 6, 1, 256,504, 0, , 0, 0, 0,
Settings must be configured for each signal group defined in the line above as has been
described in the CPT/CPX manual, Annex A, section 1.
• Data on RTU Digital Signals (ISCs)
They are configured as explained in section A.1. [lines 23-29]

Ex: 65,// Num. ISCs

00,0,1,1,0,0,
01,0,1,1,0,0,
…
64,0,1,1,0,0,

Table B-1:Note: For RFL relays, ISC numbers must match the applicable trip codes, which are:

Trip Code Trip Type

0 A phase trip
1 B phase trip
2 C phase trip
3 3I0 phase trip
4 A & B trip
5 A & C trip
6 A & 3I0 trip
7 B & C trip
8 B & 3I0 trip
9 C & 3I0 trip
10 A & B & 3I0 trip
11 B & C & 3I0 trip
12 A & C & 3I0 trip
13 ABC & 3I0 trip
14 A & B & C trip
16 DTT Received
17 DTT Transmitted

In RFL equipment, trips imply that the associated ISC switches to ‘1’, which later must return to the value ‘0’
through the LOGIC.

M1CPTA2005I
1CPT: Substation Central Unit B-128
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on RTU Commands

They are configured as explained in A.1. [lines 31-36]. In case of NP-800 and AMS-7001 this
parameter will be set to 0.

Ex: 16,// Num. ISEs

00,10,-1.500,0,10,-1,10,-1,0,0,
01,10,-1,500,0,10,-1,10,-1,0,0,
…
15,10,-1,500,0,10,-1,10,-1,0,0,

• Data on RTU Output Writes (ISSs)

They are configured as explained in A.1. [lines 38-40]. In case of SEPAM, NP-800 and AMS-
7001 this parameter will be set to 0.

Ex: 1,// Num. ISSs

00,10,-1,10000,0,0,

• Data on RTU Measurements (MEAs)

They are configured as explained in A.1. [lines 42-46]

Ex: 6,// Num. MEAs

1.0,0.0,
1.0,0.0,
…
1.0,0.0,

• Data on RTU Counters (CONs)

They are configured as explained in A.1. [lines 49-51]. In case of NP-800 and AMS-7001 this
value will be set to 0.

Ex: 1,// Num. CONs

1.0,0.0,

• Data on RTU Analog Output Writes (ISMs)

They will be configured as explained in section A.1., and will only be available for Generic type
RTUs; for other types of RTU this value will be set to 0. For CPX and CPP relays, in case the
number of ISMs is 0, this section may not appear in the configuration file for the sake of
compatibility with older versions of the dll.

Ex: 1,// Num. ISMs

00,10,-1,

M1CPTA2005I
B-129 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Signal Mapping Configuration of each Equipment

Fro now on it is configured individually as a function of the type of RTU defined in TipoDeRTUs:

CASE A) T-DAM type RTU: BCD Measurement (MeaBCD) is defined. In any case there will
only be one measurement per RTU. The first value must be TRUE or FALSE to specify whether
said measurement will exist or not.

NumM
ExisteB IscB IscBC IscB IscBC IscBCD IscBC IscBC IscBC
, eaBC , , , , , , , ,
CD CD0 D1 CD2 D3 4 D5 D6 D7
D

• ExisteBCD: TRUE or FALSE to specify whether BCD Measurements exist or not

• NumMeaBCD: MEA number (index), representing it.
• IscBCD0-8: the 8 ISCs making up the value of BCD measurement. In case one ISC does
not take part, its value will be –1.

Ex: 1,6,1,2,3,4,5,6,-1,-1,

• Data on RTU connected modules: [lines 56-66]

A.- For RTU type T_DAM:

NumModLog , Dir , Tipo , Dir , Tipo , … Dir , Tipo , (*)

DirModInp , NumInps , ISCini ,
DirModOutp , NumOutps , ISEini ,
DirModAnalog , NumAnalogs , MEAini ,
DirModCont , NumConts , CONini ,

(*) Only valid for T-DAM modules.

• NumModLog: Number of logic modules.

• Dir: Module address. As many times as there are
• Tipo: Type of module. logic modules (NumModLog).
For T-DAM modules, the following types of modules exist:
00: Bay without module.
01: Module type RMF-50 or 50 (7/8 digital inputs and 8 digital outputs).
02: Module type RMF-12 or 12 (1 analog input 16 bits).
03: Module types 11 and 13 (1 thermocouple analog input or RTD 16 bits).
04: Module type RMF-21 or 21 (1 analog output 12 bits).
05: Module type RMF-52 or 52 (8 digital inputs).
06: Module type RMF-60 or 60 (4 digital inputs and 4 digital outputs).
07: Module type RMF-51 (8 digital outputs).
08: Module type RMF-21 (1 analog output 12 bits and sign).
16: Module types 17 or 18 (8 analog inputs 16 bits) (input 1).
17: Virtual bay occupied by Module type 17 or 18 input 2.
18: Virtual bay occupied by Module type 17 or 18 input 3.
19: Virtual bay occupied by Module type 17 or 18 input 4.
20: Virtual bay occupied by Module type 17 or 18 input 5.
21: Virtual bay occupied by Module type 17 or 18 input 6.
22: Virtual bay occupied by Module type 17 or 18 input 7.
23: Virtual bay occupied by Module type 17 or 18 input 8.
• DirModInp: Starting address of modbus digital inputs.
For T-DAM it is figured out as follows:
[Nº Input (1 @ 8) - 1] + [Nº Module (1 @ 32) - 1] ∗ 8 or (0000 @ 00FF)H
[Nº Input (1 @ 8) - 1] + [Nº Module (1 @ 32) - 1] ∗ 8 + 20.480 (5000 @ 50FF)H

M1CPTA2005I
1CPT: Substation Central Unit B-130
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumInps: Number of Module digital inputs.

• ISCini: Identifier of the initial ISC of the logic device from which (including itself) modbus
digital inputs are mapped.
• DirModOutp: Starting address of modbus digital outputs.
For T-DAM it is figured out as follows:
[Nº Output (1 @ 8) - 1] + [Nº Module (1 @ 32) - 1] ∗ 8 + 512 or (0200 @ 02FF)H
[Nº Output (1 @ 8) - 1] + [Nº Module (1 @ 32) - 1] ∗ 8 + 20.992 (5200 @ 52FF)H
• NumOutps: Number of Module digital outputs.
• ISEini: Identifier of the initial ISE of the logic device from which (including itself) modbus
digital outputs M are mapped.
• DirModAnalog: Starting address of modbus analog inputs.
For T-DAM it is figured out as follows:
Modules with 1 analog input:
[Nº Module (1 @ 32) - 1] + 8.192 or (2000 @ 201F)H
[Nº Module (1 @ 32) - 1] + 20.480 (5000 @ 501F)H
Modules with 8 analog inputs:
[Nº Module (1 @ 32) - 1] + [Nº Input (1 @ 8) - 1] + 8.192 or (2040 @ 205F)H
[Nº Module (1 @ 32) - 1] + [Nº Input (1 @ 8) - 1] + 20.480 (5040 @ 505F)H
• NumAnalogs: Number of analog inputs of the module.
• MEAini: Identifier of the starting MEA of the logic device from which (including itself)
modbus analog inputs are mapped.
• DirModCont: Starting address of modbus accumulator registers.
For T-DAM it is figured out as follows:
[Nº Module (1 @ 32) - 1] + 8.256 or (2040 @ 205F)H
[Nº Module (1 @ 32) - 1] + 20.480 (5040 @ 505F)H
• NumConts: Number of accumulator registers of the Module.
• CONini: Identifier of the starting CON of the logic device from which (including itself)
ModBus accumulator registers are mapped.

Ex: Modules T-DAM:

16,1,5,2,5,3,5,4,5,5,5,6,5,7,5,8,5,10,7,11,7,…
… 20,2,21,2,22,2,23,2,24,2,25,2, (all in 1 line)
000,64,1,// Inputs
584,16,0,// Outputs
8211,6,0,// Analog inputs
8320,0,0,// Counters

B. GENERIC, MICOM, CMS-7004 or RFL type RTUs

The following blocks are configured for each of these types. Each of these sets up a rule for
mapping signals/ Modbus data to database signals. As many blocks as required can be defined
taking into account that each refers to a basic type of signals (digital, measurements, counters,
commands), mixing signals in the same block not being allowed.

NumModLog ,
DirModulo , Numero , Tipo , DirDatoIni , Funcion , Data , …
Num Orden Formato
… , , FactorEscalado , , (#)
Registros Registros Registros

(#) There will be as many rows as there are modules in the RTU. In case of Micom type RTUs
there will only be a single Module, so the value of NumModLog must always be 1.

M1CPTA2005I
B-131 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

• NumModLog: Number of Logic Modules.

• DirModulo: First MODBUS register of the register block to read.
• Numero: Number of registers to be read.
• Tipo: Type of module. Indicates the basic type of database signals the MODBUS
registers are being mapped to (2=Digital signals, 3=Counters, 4=Measurements, 5=
Digital Commands, 6=Analog Commands).
• DirDatoIni: Identifier of the starting signal, measurement, counter,....of the logic device
from which (including itself) they are mapped.
• Funcion: Number of the Function to be used for data acquisition of this MODBUS Module.
The function below are used by default.

Type Function
2 02, ReadInputRegister
3 03, ReadHoldingRegister
4 04, ReadAnalogRegister
5 05, WriteSingleCoil
6 06, WriteSingleReg
50 07, ReadHighSpeed8Bits

The table above is used as a reference for most of GENERIC MODBUS. The normal
function to read digital inputs of equipment is 2 (ReadInputRegister) although, some
equipment map digital signals to Holding Registers, so function 3 must be configured in
lieu of function 2. In this case, there exist a difference that must be taken into account:
the size of an Input Register is one bit whereas the Holding Register is 16. When defining
Numero, the number of digital signals to be read must be indicated in both cases. In case
of Input Registers, this will match the number of registers, whereas for Holding Registers
it will not. The CPT, when requesting the equipment for data, sets this value to the actual
number of MODBUS registers to be read.

For example. The table shows the way to configure reading the 16 digital signals to be
mapped to the first signals of the database. In the first case they will be read as Input
Register and in the second as Holding Register.

DirModulo Number Type DirDatoIni Function

100 16 2 0 02, ReadInputRegister
3745 16 2 0 03, ReadHoldingRegister

In the first case the equipment will be requested to read registers 100 to 116, whereas in
the second case it will only be requested to read register 3745.

• Data: For command modules, the code to be sent to the device will be configured: 0 =
Coil OFF and 65280=0xFF00 = Coil ON. Default value is 0.
• NumRegistros: Number of MODBUS registers (1 register = 2 bytes) that a measurement
or counter consists of. Possible values are 1 or 2 (by default 1). This parameter is only
considered for the case of measurements and counters.
Note: For CMS-7004 relays 5 registers (10 bytes) are always requested for each measurement,
regardless the value set for this parameter.

M1CPTA2005I
1CPT: Substation Central Unit B-132
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• OrdenRegistros: In case the number of registers in this module is 2, it indicates the order
in which registers are processed. It can take the values 0 or 1 (by default 0): 0 to indicate
that the most significant register (MSR) is received first, and 1 to indicate that the register
received first is the least significant register (LSR). As a rule, the order of the registers is
usually MSR-LSR, namely, this setting must be 0.
• Factorscalado: Scaling factor used for 2 register measurements. For all other cases, this
parameter is not taken into account. Measurement value are obtained by dividing the
value received from the RTU by the scaling factor. By default, is 1.0.
• FormatoRegistro: This parameter indicates the way read equipment registers are being
processed. The values are shown in the table below and is only applicable when Tipo is
set to 3 (Counters) or 4 (Measurements). Default values are indicated in bold type for
each type in the applicable tables. If an inadequate value is set for each type then the
default value indicated in the table is taken.

FormatoRegistro
Value Meaning Nº of Registers
0 32-bits WITH sign 2
1 32-bits Floating point 2
2 16-bits PROCOME 1
3 16-bits WITH sign 1
4 16-bits WITHOUT sign 1
5 32-bits WITHOUT sign 2
6 24-bits WITH sign 2
7 24-bits WITHOUT sign 2
8 32-bits MOD 10000 2

The 32-bit Modulo 10000 format is used to process some registers sent by SATEC model
PM172 equipment. The manual explains it as below:

The short energy registers 287-294, and 301-302 are transmitted in two contiguous 16-bit
registers in modulo 10000 format. The first (low order) register contains the value mod 10000,
and the second (high order) register contains the value/10000. To get the true energy reading,
the high order register value should be multiplied by 10,000 and added to the low order register.
[SATEC-PM172; page 12]

M1CPTA2005I
B-133 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The table below describes the possible values and their and their explanation for Tipo = 4
(measurements):

FormatoMedidas
NumRegistros FormatoRegistros
0 (Signed 16 bits) 1 (Short floating point)

2 (16-bits PROCOME) Conversion. The range Conversion. The range of

of values is -4096 … values is -4096.0 …
4095 4095.0
1 3 (16-bits WITH sign) No Conversion. Conversion. No loss.

4 (16-bits WITHOUT sign) Conversion. The value

received is divided by Conversion. No loss.
2.

0 (32-bits WITH sign) Conversion. It can be Conversion. It can be

loss of information. loss of accuracy.

1 (32-bits Short Floating Point) Conversion. It can be

No conversion
loss of information.

2 5 (32-bits WITHOUT sign) Conversion. It can be Conversion. It can be

loss of information. loss of accuracy.

6 (24-bits WITH sign) Conversion. It can be

Conversion.
loss of information.

7 (24-bits WITHOUT sign) Conversion. It can be Conversion.

loss of information.

The table below describes the possible values and their and their explanation for Tipo = 3
(counters):

NumRegistros FormatoRegistros Contadores

3 (16-bits WITH sign) Conversion to 32 bits without sign. No loss.

4 (16-bits WITHOUT sign) Conversion to 32 bits without sign. Negative values

1
are converted into very large values.

0 (32-bits WITH sign) Conversion to 32 bits without sign. Negative values

are converted into very large values.

1 (32-bits Short Floating Point) Conversion to 32 bits without sign. Loss of

accuracy. Negative values are converted into very
large values.
2
5 (32-bits WITHOUT sign) No conversion.

6 (24-bits WITH sign) Conversion to 32 bits without sign. Negative values

are converted into very large values.

7 (24-bits WITHOUT sign) Conversion to 32 bits without sign. No loss.

8 (32-bits MOD 10000) It is converted to 32 bits without sign.

M1CPTA2005I
1CPT: Substation Central Unit B-134
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: Generic modules:

4,
// DirModulo, Num, Tipo, DirDatoIni, Funcion,
0, 16,4, 0,4,0,1,0, 1,0,// Measurement,
20, 8,4,18,4,0,2,1,100,0,// Measurement
0, 5,3, 0,3,0,1,0, 1,0,// Counter
0, 3,2, 0,2,0,1,0, 1,0,// Digital Signals

Ex: Micom module:

1,
30016,10,3,0,1,0,1,0,// DirModBus,Num,Tipo,DirISCIni

C. SEPAM, NP-800 or AMS-7001 type RTUs:

In case of SEPAM, neither digital outputs (ISS) nor counters (CON) are defined. In case of NP-
800 and AMS-7001, apart from digital outputs (ISS) and counters (CON), commands (ISE) are
not defined either.
• Data on Inputs Connected to RTU: [Line 84]

NumBlqEntradas , DirIniMODBUS , Numero , ISCini , (#)

(#)There will be as many Input Blocks [DirInMODBUS, Numero, IscIni] as stated by

NumBlqEntradas.

• NumBlqEntradas: Number of Input Blocks. The Input blocks themselves are described
from this number.

The following are defined for each block:

• DirIniMODBUS: Starting MODBUS address of the first Digital Input.

• Numero: Number of Digital inputs defined in this block.
• ISCIni: Identifier of the starting ISC of the logic device from which (including itself)
modbus digital inputs are mapped.

Ex: # Input Groups

#NumBlqEntr,[DirIniModbus,Numero,IscProcoIniEquiv],[...],[...]
3 49408,41,0, 51440,122,41, 51662,29,163,

M1CPTA2005I
B-135 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on Commands to be Executed on the RTU: [Line 89]

Table B-2:Note: For SEPAM equipment only (not for NP-800 or AMS-7001)

Commands can be two types:

1. DO (Direct Operate): DirSelectISEIni must be set to 0.
2. SBO (Select Before Operate): In this case, DirSelectISEIni is other than 0. These
commands are carried out through two writes: first to the Select address and, after
“TimePulso” defined above, the write is checked for correctness through a read, and then
the final write is carried out to the Operate address.

DirSelectISEIni , DirOperateISEIni , Numero , IseProcoIniEquiv ,

• DirSelectISEIni: Starting MODBUS address of Select (0 for Direct Operate commands).

• DirOperateISEIni: Starting MODBUS address of Operate.
• Numero: Number of Commands defined consecutively.
• IseProcoIniEquiv: Identifier of the starting ISE of the logic device from which (including
itself) Modbus Commands are mapped.

Ex:# Commands SBO (Select Before Operate)

#DirSelectISEIni, DirOperateISEIni, Numero, IseProcoIniEquiv,
51312, 51376, 10, 0,

• Data on RTU Measurements: [Line 93]

NumBlqMedidas , DirIni , Numero , MeaIni , [TipoMea1,TipoMea2,..,TipoMeaN]** ,

MODBUS

* There will be as many Type of Measurement fields as indicated by the number of

measurements defined in the third field.
(#) There will be as many Measurement Blocks [DirInMODBUS, Number, MeaIni, TipoMea1,…]
as indicated by NumBlqMeasurements.

• NumBlqMedidas: Number of Measurement Blocks that follow. The following fields will be
defined per Block:
• DirIniMODBUS: Starting MODBUS address of the first measurement of a given block.
• Numero: Number of correlative Measurements in a given block.
• MEAIni: Identifier of the starting MEA of the logic device from which (including itself)
modbus measurements of a given block are mapped.
Note: TipoMeaN parameters are only used in SEPAM equipment (not in NP-800 or AMS-7001).
• TipoMeaN: From now on, the specific types of these N measurements pertaining to a
given block, are declared in sequential order as a function of the number of
measurements defined in the field “Numero”. The different types defined until now are:
- Type 16NS: It is defined with the value 4 in the configuration file. It is a 16 bit value
without sign. This poses a problem, as it is saved with sign in Dbase, and so it has
been decided to divide it by 2 in order to save it in the database. Then, for displaying it
on the HMI or sending it to any remote control, the saved value must be multiplied by
two to obtain the actual value. Currents and voltages are examples of these types of
measurements.
- Type 16O: It is defined with the value of 5 in the configuration file. It is a 16 bit value
with sign and 8000h range. This entails that the actual value –32768 is coded as
0000h. The actual value 0 is coded as 8000h. The actual value 32767 is coded as
FFFFh. Active power and reactive power are examples of this type of measurement.

M1CPTA2005I
1CPT: Substation Central Unit B-136
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: #NumBlqMedidas, DirIniModb, Num, MeaIni,

TipoMea1,TipoMea2,...,TipoMeaN,)
2, 64384,4,0, 4,4,5,5, 64285,1,4, 4,

The file for T-DAM type RTUs becomes:

[1] # MODBUSMS configuration

[2] # This is the PRUEBAS configuration
[3] # Parameters of COM1 communications Port
[4] ,9600,n,8,1,
[5] # Times of RTS ON (CS0T) and RTS OFF in msec, RX timeout with RTUs (ms),
[6] # num retries, monitor
[7] # For T-MOD modules RTS must not be used
[8] 0,0,500,2,0,
[9] # Exploration time(in sec) of measurement cycle, counter cycle, pulse
time,..
[10] 1,4,1000,1,
[11] # Address of first equivalent logic device within UCS’s DB
[12] 100,
[13] #Number of RTUs to explore (Max 10),Type of RTU
(0=T_DAM,1=Generic,2=Micom)
[14] 4,0,0,
[15] # These configurations are for FARELL´s Miniremote T-DAM
[16] #====================================================================
[17] #------------ LOGIC DEVICE [ACTUR - CD Nº 1, AREA 7]
[18] #====================================================================
[19] # RTU address, Nº ISCs, ISC max, Nº ISE, ISE max, Nº ISS, ISS max, Nº
Meas,
[20] Nº Con, ISC Local, ISC Failure,
[21] 1,65,64,16,15,1,0,6,1,0,21,0,COM1,0,0,0,
[22] # Number of ISCs
[23] 65,
[24] # ISC, alarm, f.activ, f.deactiv, alrm rising edge, horn,
[25] 00,0,1,1,0,0, // T-DAM’s COMs failure
[26] 01,0,1,1,0,0,
[27] 02,0,1,1,0,0,
[28] ...
[29] 64,0,1,1,0,0,
[30] # Number of ISEs
[31] 16,
[32] # ISE, Exec ON, Exc OFF, Time, Negada, OK, BAD, doble, n blqs, dir, isc,
neg,..,
[33] 00,10,-1,500,0,10,-1,10,-1,0,0,
[34] 01,10,-1,500,0,10,-1,10,-1,0,0,
[35] ...
[36] 15,10,-1,500,0,10,-1,10,-1,0,0,
[37] # Number of ISSs
[38] 1,
[39] ISS,DirEqEstado,ISCEstado,Time,Neg,Analog?
[40] 00,10,-1,10000,0,0,
[41] # Number of MEAs
[42] 6,
[43] # Factors a, b
[44] 1.0,0.0,
[45] 1.0,0.0,
[46] ...
[47] 1.0,0.0,

M1CPTA2005I
B-137 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[48] # Number of CONs

[49] 1,
[50] # Factors a, b
[51] 1.0,0.0
[52] # Measurement BCD:
[53] 1,6,1,2,3,4,5,6,-1,-1,
[54] # From here, MODBUSMS logic device is configured
[55] # with all its signals, commands, measurements and counters
[56] # First, the number of Modules and their type will be described
[57] # Nº logic Modules, addr, type, addr, type,......
[58] 16,1,5,2,5,3,5,4,5,5,5,6,5,7,5,8,5,10,7,11,7,20,2,21,2,22,2,23,2,24,2,25,
2,
[59] # Addr MODBUS Inputs, Num Inputs, starting ISC to map on modbus
addresses,
[60] # ISC 0 is reserved to state T-DAM’s COMs failure
[61] # Addr MODBUS Inputs, Num Inputs, starting ISC
[62] 000,64,1,
[63] # Addr MODBUS Outputs, Num Outputs, starting ISE,
[64] 584,16,0,
[65] # Addr MODBUS Inp Analog, Num Inp Analog, starting MEA,
[66] 8211,6,0,
[67] # Addr MODBUS Counters, Num Counters, starting CON
[68] 8320,0,0,
[69] #====================================================================
[70] #------------ LOGIC DEVICE [ACTUR CD Nº 2]
[71] #====================================================================
[72] # Address RTU, Nº ISCs, ISC max, Nº ISE, ISE max, Nº ISS, ISS max, Nº
Meas,
[73] Nº Con, ISC Local, ISC Failure,
[74] 2,65,64,24,23,0,0,8,0,20,0,
[75] ...

M1CPTA2005I
1CPT: Substation Central Unit B-138
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file for MICOM type RTUs becomes:

[1] # MODBUSMS configuration

[2] # This is PRUEBAS MODBUS MICOM configuration
[3] # Parameters of COM1 communications Port,9600,n,8,1,
[4] COM1,9600,n,8,1,
[5] # Times for RTS ON (CS0T) and RTS OFF in millisec, RX timeout with RTUs
(ms),
[6] # num retries,monitor
[7] # For T-MOD modules, RTS must not be used
[8] 0,0,500,3,0,
[9] # exploration time (in secs) of measurement cycle, counter cycle , pulse
time ,
[10] 1,4,1000,0,
[11] # Address of the first equivalent logic device within UCS´s DB
[12] 0,
[13] #Number of RTUs to be explored Max 10, Type of RTU(0=T-
DAM,1=Generic,2=MICOM)
[14] 1,2,0,
[15] #====================================================================
[16] #------------ LOGIC DEVICE [SANTA QUITERIA - Nº 1]
[17] #====================================================================
[18] # RTU address,Nº ISCs,ISC max,Nº ISE,ISE max,Nº ISS,ISS max,Nº Meas,Nº
con,Addr Local,ISC Local,ISC Failure,
[19] 1,32,31,0,0,0,0,0,0,0,0,0,COM1,0,2,0,
[20] # Numero de ISCs
[21] 32,
[22] #ISC,alarm,f.activ,f.deact,rising edge alrm, horn
[23] 00,0,1,1,0,0,
[24] 01,0,1,1,0,0,
[25] 02,0,1,1,0,0,
[26] 03,0,1,1,0,0,
[27] 04,0,1,1,0,0,
[28] 05,0,1,1,0,0,
[29] 06,0,1,1,0,0,
[30] 07,0,1,1,0,0,
[31] 08,0,1,1,0,0,
[32] 09,0,1,1,0,0,
[33] 10,0,1,1,0,0,
[34] 11,0,1,1,0,0,
[35] 12,0,1,1,0,0,
[36] 13,0,1,1,0,0,
[37] 14,0,1,1,0,0,
[38] 15,0,1,1,0,0,
[39] 16,0,1,1,0,0,
[40] 17,0,1,1,0,0,
[41] 18,0,1,1,0,0,
[42] 19,0,1,1,0,0,
[43] 20,0,1,1,0,0,
[44] 21,0,1,1,0,0,
[45] 22,0,1,1,0,0,
[46] 23,0,1,1,0,0,
[47] 24,0,1,1,0,0,
[48] 25,0,1,1,0,0,
[49] 26,0,1,1,0,0,
[50] 27,0,1,1,0,0,
[51] 28,0,1,1,0,0,
[52] 29,0,1,1,0,0,
[53] 30,0,1,1,0,0,

M1CPTA2005I
B-139 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[54] 31,0,1,1,0,0,
[55] # Numero de ISE
[56] 0,
[57] # Numero de ISS
[58] 0,
[59] # Numero de MEA
[60] 0,
[61] # Numero de CON
[62] 0,
[63] # Modules: NumModLog (Micom type)
[64] # DirIniModbus,Number of integers to be requested,Type of
Module,DirISCInicial
[65] 1,
[66] 3016,10,3,0,

The file for GENERIC type RTUs becomes:

[1] # MODBUSMS configuration

[2] # This is PRUEBAS MODBUS GENERIC configuration
[3] # Parameters of COM1 communications port
[4] ,9600,n,8,1,
[5] # Times of RTS ON (CS0T) and RTS OFF in millisec,RX timeout with RTUs
(ms),
[6] # num retries,monitor
[7] # For T-MOD modules, RTS must not be used
[8] 0,0,300,3,0,
[9] # exploration time (in secs) of measurement cycle,counter cycle,pulse
time,
[10] 1,4,1000,0,
[11] #Address of first equivalent logic device within UCS´s DB
[12] 0,
[13] #Number of RTUs to be explored Max 10, Type of RTU(0=T-DAM,1=
Generic,2=MICOM)
[14] 1,1,0,
[15] #====================================================================
[16] #------------ LOGIC DEVICE [P.E. MARVILA - Nº 1]
[17] #====================================================================
[18] # RTU address,Nº ISCs,ISC max,Nº ISE,ISE max,Nº ISS,ISS max,Nº Meas,Nº
con,Addr Local,ISC Local,ISC Failure,
[19] 1,32,31,0,0,0,0,0,0,0,0,0,COM1,0,1,0,
[20] # Number of ISCs
[21] 32,
[22] #ISC,alarm,f.activ,f.deact,alrm rising edge, horn
[23] 00,0,1,1,0,0,
[24] 01,0,1,1,0,0,
[25] 02,0,1,1,0,0,
[26] 03,0,1,1,0,0,
[27] 04,0,1,1,0,0,
[28] 05,0,1,1,0,0,
[29] 06,0,1,1,0,0,
[30] 07,0,1,1,0,0,
[31] 08,0,1,1,0,0,
[32] 09,0,1,1,0,0,
[33] 10,0,1,1,0,0,
[34] 11,0,1,1,0,0,
[35] 12,0,1,1,0,0,
[36] 13,0,1,1,0,0,

M1CPTA2005I
1CPT: Substation Central Unit B-140
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[37] 14,0,1,1,0,0,
[38] 15,0,1,1,0,0,
[39] 16,0,1,1,0,0,
[40] 17,0,1,1,0,0,
[41] 18,0,1,1,0,0,
[42] 19,0,1,1,0,0,
[43] 20,0,1,1,0,0,
[44] 21,0,1,1,0,0,
[45] 22,0,1,1,0,0,
[46] 23,0,1,1,0,0,
[47] 24,0,1,1,0,0,
[48] 25,0,1,1,0,0,
[49] 26,0,1,1,0,0,
[50] 27,0,1,1,0,0,
[51] 28,0,1,1,0,0,
[52] 29,0,1,1,0,0,
[53] 30,0,1,1,0,0,
[54] 31,0,1,1,0,0,
[55] # Number of ISE
[56] 0,
[57] # Number of ISS
[58] 0,
[59] # Number of MEA
[60] 0,
[61] # Number of CON
[62] 0,
[63] # Modules: NumModLog (Micom type)
[64] # DirIniModbus,Number of integers to ask,Type of Module,DirISCInicial
[65] 4,
[66] // DirModulo, Num, Tipo, DirDatoIni, Funcion,
[67] 0, 16,4, 0,4,0,1,0, 1,0,// Measurement,
[68] 20, 8,4,18,4,0,2,1,100,0,// Measurement
[69] 0, 5,3, 0,3,0,1,0, 1,0,// Counter
[70] 0, 3,2, 0,2,0,1,0, 1,0,// Digital Signals

M1CPTA2005I
B-141 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file for SEPAM type RTUs becomes:

[1] # MODBUSMS configuration

[2] # SUBESTACION ACTUR
[3] # MODBUSMS configuration
[4] # Parameters of COM3 communications port
[5] ,19200,I,8,1,
[6] # TimeRTSon(ms),timeRTSoff(ms),ToutRX(ms),NumReintentos,NivelMonitor,
[7] # NOTE: For modules T-MOD, RTS must not be used
[8] 0,0,66,3,0,
[9] #
TimeExpMedidas(sec),TimeExpCont(sec),TimePulso(sec),TimeExpGenerico(
sec), TimeExpSincro(sec),
[10] # TimeEsperaTrasReset(sec), ToutSincroBroadcast(msec),
[11] 20,0,50,0,25,60,22,
[12] # Address of the first equivalent logic device within UCS´s DB
[13] 32,
[14] # NumRTUs(Max 25),TipoDeRTUs(T-DAM(0),GENERICO(1),MICOM(2),SEPAM(3)),
[15] 1,3,0,
[16] #
[17] # SEPAM S81:
[18] #====================================================================
[19] #------- LOGIC DEVICE 1: ACTUR - BUSBAR 1 10KV (BUSBAR TYPE MT, B-MTC2-
SZ)
[20] #====================================================================
[21] #Dir,TotISCs,ISCMasAlta,TotISE,ISEMasAlta,TotISS,ISSMasAlta,TotMea,TotCon
,DirLocal,ISCLocal,ISCFallo
[22] 1, 22,21, 10,9, 0,0, 4, 0, 256,493, 86, COM3,0,3,0,
[23] # DirLocal= Addr. first equivalent logic device within UCS + DirRTU = 33
[24] ##
[25] # Number of ISCs
[26] 22,
[27] # ISC,alarm,f.activ,f.deact,alrm rising edge,horn,
[28] 0,0,1,1,0,0, // RESERVE 0 (Ox C100)
[29] 1,0,1,1,0,0, // RESERVE 1 (Ox C101)
[30] 2,0,0,0,0,0, // RESERVE 2 (Ox C102)
[31] 3,0,0,0,0,0, // RESERVE 3 (Ox C103)
[32] 4,0,1,1,0,0, // SECCIONADOR B1 POSICION CERRADO
[33] 5,0,1,1,0,0, // SECCIONADOR B1 POSICION ABIERTO
[34] 6,0,1,1,0,0, // RESERVE 6 (Ox C106)
[35] 7,0,1,1,0,0, // RESERVE 7 (Ox C107)
[36] 8,0,1,1,0,0, // RESERVE 8 (Ox C108)
[37] 9,0,1,1,0,0, // SECCIONADOR PAT POSICION CERRADO
[38] 10,0,1,1,0,0, // SECCIONADOR PAT POSICION ABIERTO
[39] 11,0,1,1,0,0, // RESERVE 11 (Ox C10B)
[40] 12,0,0,0,0,0, // CONTROL SIN MANDO
[41] 13,0,0,0,0,0, // CONTROL MANDO LOCAL
[42] 14,0,0,0,0,0, // RESERVE 14 (Ox C10E)
[43] 15,0,0,0,0,0, // RESERVE 15 (Ox C10F)
[44] 16,1,0,0,0,0, // UCP/S MAGNETO/S CC ABIERTO
[45] 17,1,0,0,0,0, // UCP/S FALTA CC or FALLO
[46] 18,1,0,0,0,0, // UCP FALLA CC SUPERVISION
[47] 19,1,0,0,0,0, // MAGNETO TENSIONES HOMOPOLARES
[48] 20,0,0,0,0,0, // RESERVE 20 (Ox C114)
[49] 21,0,0,0,0,0, // RESERVE 21 (Ox C115)
[50] ##
[51] # Number of ISEs
[52] 10,

M1CPTA2005I
1CPT: Substation Central Unit B-142
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[53] #
ISE,DirEqEst,ISCEst,Time,Negada,DirEqOK,IscOK,DirEqBAD,IscBAD,
doble, n blqs,dir,isc,neg,..,
[54] # DirEq=DirLocal=32+1
[55] 0,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- ABRIR INTOR DESDE REMOTO
[56] 1,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- CERRAR INTOR DESDE REMOTO
[57] 2,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- ABRIR SECC. B1 DESDE REMOTO
[58] 3,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- CERRAR SECC. B1 DESDE
REMOTO
[59] 4,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- ABRIR SECC. B2 DESDE REMOTO
[60] 5,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- CERRAR SECC. B2 DESDE
REMOTO
[61] 6,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- 79 FUERA DE SERVICIO DESDE
REMOTO
[62] 7,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- 79 EN SERVICIO DESDE REMOTO
[63] 8,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- COG. FUERA SERVICIO DESDE
REMOTO
[64] 9,33,-1,4000,0,33,-1,-1,-1,0,0,0,0,0, // O- COG. EN SERVICIO DESDE
REMOTO
[65] ##
[66] # Number of ISSs
[67] 0,
[68] ##
[69] # Number of MEAs
[70] 4,
[71] # Factors a,b
[72] 1.0000000,0.0000000, // MEASUREMENT DE INTENSIDAD (Tipo_16NS)
[73] 1.0000000,0.0000000, // MEASUREMENT DE TENSIÓN (10KV/110V) (Tipo_16NS)
[74] 1.0000000,0.0000000, // POTENCIA ACTIVA (Tipo_16O)
[75] 1.0000000,0.0000000, // POTENCIA REACTIVA (Tipo_16O)
[76] ##
[77] # Number of CONs (Factors a,b)
[78] 0,
[79] #1.0,0.0,
[80] ###################################################
[81] # MODELO SEPAM S81 LOGIC DEVICE 1:
[82] ## ISC
[83] # Nº groups, [Addr. memory(in decimal), Nº group signals, 1st ISC]
,[...],[...],...
[84] # 0xC100=49408, 0xC8F0=51440, 0xC9CE=51662
[85] 3, 49408,41,0, 51440,122,41, 51662,29,163,
[86] ## ISE
[87] # DirSelectISEIni, DirOperateISEIni, NumMandos, DirISEIni,
[88] # Addr. memory (in decimal), nº group signals, 1ª ISE,
[89] # DirSelect=0C870=51312 - DirOperate=0xC8B0=51376
[90] 51312,51376,10,0,
[91] ## MEA
[92] # DirModbusMEA (en decimal), NumMEAs, MEAProcoEquiv,
(TipoMea1,TipoMea2,...,TipoMeaN,)
[93] # 0xFB80=64384
[94] 2, 64384,4,0,4,4,5,5, 64285,1,4,4,

M1CPTA2005I
B-143 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The NP-800 RTUs file becomes:

[1] # MODBUSMS configuration

[2] # Port communications parameters
[3] COM1,9600,N,8,1,
[4] # TimeRTSon(ms),timeRTSoff(ms),ToutRX(ms),NumRetries,NivelMonitor,
[5] # NOTE: Do not use the RTS for modules T-MOD
[6] 0,0,200,3,0,
[7] #TimeExpMeasurements(sec),TimeExpCont(sec),TimePulso(sec),TimeExpGen
erico(sec),
TimeExpSincro(sec),TimeEsperaTrasReset(sec),ToutSincroBroadcast(msec
),
[8] 5,5,50,1,0,10,22,3,0,
[9] # Address of the UCS BD’s first equivalent logic equipment
[10] 0,
[11] # NumRTUs(Max 25),TipoDeRTUs(T-DAM(0),GENERICO(1),MICOM(2),SEPAM(3),
NP800(4),CMS7004(5),AMS7001(6)),
[12] 1,4,0,
[13] #
[14] #====================================================================
[15] #------- LOGIC EQUIPMENT 1: NPID-800 TRANSFORMER 1A K07
[16] #====================================================================
[17] #Dir,TotISCs,ISCMasAlta,TotISE,ISEMasAlta,TotISS,ISSMasAlta,TotMea,TotCon
,DirLocal,ISCLocal,ISCFallo
[18] 50, 48,47, 0,0, 0,0, 1, 0, 256, 0, 0, COM1,0,4,0,
[19] # DirLocal= Addr. first UCS’s equivalent logic equipment + DirRTU = 33
[20] ##
[21] # Number of ISCs
[22] 48,
[23] # ISC,alarm,f.activ,f.deactiv,edge alrm,horn,
[24] 0,1,0,1,0,0, // Trip 50 phase
[25] 1,1,0,1,0,0, //Trip 51-1
[26] 2,1,0,1,0,0, //Trip 50N
[27] 3,1,0,1,0,0, //Trip 51N
[28] 4,1,0,1,0,0, //Trip 51-2
[29] 5,0,1,1,0,0, //Spare
[30] 6,1,0,0,0,0, // Thermal image alarm (49)
[31] 7,1,0,0,0,0, // Minimum current
[32] 8,1,0,1,0,0, //I2/I1 time delayed
[33] 9,0,0,0,0,0, //Function 46
[34] 10,1,0,1,0,0, //I2/I1 instantaneous
[35] 11,0,1,1,0,0, //Spare
[36] 12,0,1,1,0,0, //Spare
[37] 13,0,1,1,0,0, //Spare
[38] 14,0,1,1,0,0, //Spare
[39] 15,0,1,1,0,0, //Spare
[40] 16,1,0,0,0,0, // Alarm nº trips breaker
[41] 17,1,0,0,0,0, //Alarm KA2
[42] 18,0,1,1,0,0, //Spare
[43] 19,0,1,1,0,0, //Spare
[44] 20,1,0,0,0,0, // Breaker defect
[45] 21,0,1,1,0,0, //Spare
[46] 22,0,1,1,0,0, //Spare
[47] 23,0,1,1,0,0, //Spare
[48] 24,0,0,0,0,0, // local/ distance mismatch
[49] 25,0,0,0,0,0, //Remote mode tap

M1CPTA2005I
1CPT: Substation Central Unit B-144
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[50] 26,0,1,1,0,0, //Spare

[51] 27,0,1,1,0,0, //Spare
[52] 28,0,1,1,0,0, //Spare
[53] 29,0,0,0,0,0, //74TC breaker coil
[54] 30,1,0,0,0,0, //Breaker failure (50BF)
[55] 31,0,1,1,0,0, //Spare
[56] 32,0,0,0,0,0, // Activation input 1
[57] 33,0,0,0,0,0, // Activation input 2
[58] 34,0,0,0,0,0, // Activation input 3
[59] 35,0,0,0,0,0, // Activation input 4
[60] 36,1,0,0,0,0, //Trip circuit failure
[61] 37,1,0,0,1,0, // Minimum voltage command and signalling
[62] 38,1,0,0,1,0, // Minimum voltage spring motor
[63] 39,1,0,0,0,0, //Loose springs
[64] 40,0,0,0,0,0, // Activation watchdog relay
[65] 41,0,0,0,0,0, // Activation relay A
[66] 42,0,0,0,0,0, // Activation relay B
[67] 43,0,0,0,0,0, // Activation relay C
[68] 44,0,0,0,0,0, // Activation relay D
[69] 45,0,0,0,0,0, // Activation relay E
[70] 46,0,0,0,0,0, // Activation relay F
[71] 47,0,0,0,0,0, // Activation relay G
[72] ##
[73] # Number of ISEs
[74] 0,
[75] ##
[76] # Number of ISSs
[77] 0,
[78] ##
[79] # Number of MEAs
[80] 1,
[81] # Factors a,b
[82] 1.0000000,0.0000000, // Measurement phase A current
[83] ##
[84] # Number of CONs (Factors a,b)
[85] 0,
[86] ##
[87] ## ISC
[88] # Nº groups, memory Addr.(decimal), Nº signals included in that group, 1st
ISC.....
[89] 2, 32784,40,0, 32832,8,40,
[90] ## MEA
[91] # Nº groups, DirModbusMEA (decimal), NumMEAs, MEAProcoEquiv, (TipoMea1,
TipoMea2,...TipoMeaN,)
[92] 1, 268,1,0,

M1CPTA2005I
B-145 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

CMS-7004 type RTU file becomes:

[1] # MODBUSMS configuration

[2] # Port communications parameters
[3] COM4,2400,N,8,1,
[4] # TimeRTSon(ms),timeRTSoff(ms),ToutRX(ms),NumRetries,NivelMonitor,
[5] # NOTA: Do not use the RTS for modules T-MOD
[6] 0,0,500,3,0,
[7] #TimeExpMeasurements(sec),TimeExpCont(sec),TimePulso(sec),TimeExpGen
erico(sec),
TimeExpSincro(sec),TimeEsperaTrasReset(sec),ToutSincroBroadcast(msec
),
[8] 0,5,50,1,0,10,22,900,0,
[9] # Address of the UCS BD’s first equivalent logic equipment
[10] 0,
[11] # NumRTUs(Max 25),TipoDeRTUs(T-DAM(0),GENERICO(1),MICOM(2),SEPAM(3),
NP800(4),CMS7004(5),AMS7001(6)),
[12] 1,5,0,
[13] #
[14] #====================================================================
[15] #------- LOGIC EQUIPMENT 1: NPID-800 TRANSFORMER 1A K07
[16] #====================================================================
[17] #Dir,TotISCs,ISCMasAlta,TotISE,ISEMasAlta,TotISS,ISSMasAlta,TotMea,TotCon
,DirLocal,ISCLocal,ISCFallo
[18] 52, 0,0, 0,0, 0,0, 13, 0, 256, 0, 0, COM4,0,5,0,
[19] # DirLocal= Addr. first UCS’s equivalent logic equipment + DirRTU = 33
[20] ##
[21] # Number of ISCs
[22] 0,
[23] ##
[24] # Number of ISEs
[25] 0,
[26] ##
[27] # Number of ISSs
[28] 0,
[29] ##
[30] # Number of MEAs
[31] 13,
[32] # Factors a,b
[33] 1.000000,0.0000000, //Measurement voltage phase A (VA)
[34] 1.000000,0.0000000, //Measurement voltage phase B (VB)
[35] 1.000000,0.0000000, //Measurement voltage phase C (VC)
[36] 1.000000,0.0000000, //Measurement voltage AB (VAB)
[37] 1.000000,0.0000000, //Measurement voltage BC (VBC)
[38] 1.000000,0.0000000, //Measurement voltage CA (VAC)
[39] 1.000000,0.0000000, //Measurement current phase A (IA)
[40] 1.000000,0.0000000, //Measurement current phase B (IB)
[41] 1.000000,0.0000000, //Measurement current phase C (IC)
[42] 1.000000,0.0000000, //Cos phi
[43] 1.000000,0.0000000, //Active Power
[44] 1.000000,0.0000000, //Reactive Power
[45] 1.000000,0.0000000, //Apparent Power
[46] ##
[47] # Number of CONs (Factors a,b)
[48] 0,

M1CPTA2005I
1CPT: Substation Central Unit B-146
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[49] ##
[50] # NumBlqGenericos
[51] 13,
[52] # DirIni, Number, Type, IdxProcome, Function, Data,
[53] 77,1,4,0,3,0,1,0,1,
[54] 86,1,4,1,3,0,1,0,1,
[55] 95,1,4,2,3,0,1,0,1,
[56] 107,1,4,3,3,0,1,0,1,
[57] 113,1,4,4,3,0,1,0,1,
[58] 122,1,4,5,3,0,1,0,1,
[59] 374,1,4,6,3,0,1,0,1,
[60] 383,1,4,7,3,0,1,0,1,
[61] 392,1,4,8,3,0,1,0,1,
[62] 617,1,4,9,3,0,1,0,1,
[63] 680,1,4,10,3,0,1,0,1,
[64] 743,1,4,11,3,0,1,0,1,
[65] 806,1,4,12,3,0,1,0,1,

AMS-7001 type RTU file becomes:

[1] # MODBUSMS configuration

[2] # Port communications parameters
[3] COM3,2400,N,8,1,
[4] # TimeRTSon(ms),timeRTSoff(ms),ToutRX(ms),NumRetries,NivelMonitor,
[5] # NOTA: Do not use the RTS for modules T-MOD
[6] 0,0,500,3,0,
[7] #TimeExpMeasurements(sec),TimeExpCont(sec),TimePulso(sec),TimeExpGen
erico(sec),
TimeExpSincro(sec),TimeEsperaTrasReset(sec),ToutSincroBroadcast(msec
),
[8] 0,5,50,1,0,10,22,900,0,
[9] # Address of the UCS BD’s first equivalent logic equipment
[10] 0,
[11] # NumRTUs(Max 25),TipoDeRTUs(T-DAM(0),GENERICO(1),MICOM(2),SEPAM(3),
NP800(4),CMS7004(5),AMS7001(6)),
[12] 1,6,0,
[13] #
[14] #====================================================================
[15] #------- AMS7001 BUSBAR CONTROL FUNCTION TO K09 EQUIPMENT 6 -------------
--------
[16] #====================================================================
[17] #Dir,TotISCs,ISCMasAlta,TotISE,ISEMasAlta,TotISS,ISSMasAlta,TotMea,TotCon
,DirLocal,ISCLocal,ISCFallo
[18] 72, 22,21, 0,0, 0,0, 0, 0, 256, 0, 0, COM3,0,6,0,
[19] # DirLocal= Addr. first UCS’s equivalent logic equipment + DirRTU = 33
[20] ##
[21] # Number of ISCs
[22] 22,
[23] # ISC, alarm, f.activ, f.deactiv, edge alrm, horn ,
[24] 0,0,0,0,0,0, //Supply switch B closed and inserted
[25] 1,0,0,0,0,0, //Transfer status B
[26] 2,0,0,1,0,0, // Switch in manual position
[27] 3,0,0,1,0,0, // Switch in automatic position
[28] 4,0,0,0,0,0, //Selector in position C
[29] 5,0,0,0,0,0, //Selector in position B
[30] 6,0,0,0,0,0, //Selector in position A
[31] 7,0,0,0,0,0, // Synchronism between both busbars

M1CPTA2005I
B-147 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[32] 8,0,0,0,0,0, //Coupling switch closed and inserted

[33] 9,0,0,0,0,0, // Side A ready
[34] 10,0,0,0,0,0, //Upstream switch closed and inserted
[35] 11,0,0,0,0,0, // Supply switch A closed and inserted
[36] 12,0,0,0,0,0, // Activation input 13
[37] 13,0,0,0,0,0, // Activation input 14
[38] 14,0,0,0,0,0, // Activation output 1
[39] 15,0,0,0,0,0, // Activation output 2
[40] 16,0,0,0,0,0, // Activation output 3
[41] 17,0,0,0,0,0, // Activation output 4
[42] 18,0,0,0,0,0, // Activation output 5
[43] 19,0,0,0,0,0, // Activation output 6
[44] 20,0,0,0,0,0, // Activation output 7
[45] 21,0,0,0,0,0, // Activation output 8
[46] ##
[47] # Number of ISEs
[48] 0,
[49] ##
[50] # Number of ISSs
[51] 0,
[52] ##
[53] # Number of MEAs
[54] 0,
[55] # Factors a,b
[56] ##
[57] # Number of CONs (Factors a,b)
[58] 0,
[59] ##
[60] ## ISC
[61] # Nº groups, memory Addr.(decimal), Nº signals included in that group,1st
ISC.....
[62] 3, 1408,8,0, 1424,6,8, 1440,8,14,
[63] ## MEA
[64] # Nº grupos, DirModbusMEA (en decimal), NumMEAs, MEAProcoEquiv,
(TipoMea1, TipoMea2,...TipoMeaN,)
[65] 0,

M1CPTA2005I
1CPT: Substation Central Unit B-148
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The RFL type RTU file becomes:

[66] # MODBUSMS configuration

[67] # Port communications parameters
[68] COM1,9600,N,8,1,
[69] # TimeRTSon(ms),timeRTSoff(ms),ToutRX(ms),NumRetries,NivelMonitor,
[70] # NOTA: Do not use the RTS for modules T-MOD
[71] 0,0,300,3,0,
[72] #TimeExpMeasurements(sec),TimeExpCont(sec),TimePulso(sec),TimeExpGen
erico(sec),
TimeExpSincro(sec),TimeEsperaTrasReset(sec),ToutSincroBroadcast(msec
),
[73] 0,5,50,1,0,10,22,900,0,
[74] # Address of the UCS BD’s first equivalent logic equipment
[75] 0,
[76] # NumRTUs(Max 25),TipoDeRTUs(T-DAM(0),GENERICO(1),MICOM(2),SEPAM(3),
NP800(4),CMS7004(5),AMS7001(6), RFL(7)),
[77] 1,7,0,
[78] #
[79] #====================================================================
[80] #------------------------------ RFL ---------------------------------
[81] #====================================================================
[82] #Dir,TotISCs,ISCMasAlta,TotISE,ISEMasAlta,TotISS,ISSMasAlta,TotMea,TotCon
,DirLocal,ISCLocal,ISCFallo
[83] 11,18,17, 0,0, 0,0, 0, 0, 256, 0, 0, COM1,0,7,0,
[84] # DirLocal= Addr. first UCS’s equivalent logic equipment + DirRTU = 33
[85] ##
[86] # Number of ISCs
[87] 18,
[88] # ISC,alarm, f.activ, f.deactiv, edge alrm, horn,
[89] 0,1,0,1,0,0,//A phase trip
[90] 1,1,0,1,0,0,//B phase trip
[91] 2,1,0,1,0,0,//C phase trip
[92] 3,1,0,1,0,0,//3I0 phase trip
[93] 4,1,0,1,0,0,//A&B trip
[94] 5,1,0,1,0,0,//A&C trip
[95] 6,1,0,1,0,0,//A&3I0 trip
[96] 7,1,0,1,0,0,//B&C trip
[97] 8,1,0,1,0,0,//B&3I0 trip
[98] 9,1,0,1,0,0,//C&3I0 trip
[99] 10,1,0,1,0,0,//A&B&3I0 trip
[100]11,1,0,1,0,0,//B&C&3I0 trip
[101]12,1,0,1,0,0,//A&C&3I0 trip
[102]13,1,0,1,0,0,//ABC&3I0 trip
[103]14,1,0,1,0,0,//A&B&C trip
[104]15,1,0,1,0,0,//Reserved
[105]16,1,0,1,0,0,//DTT received
[106]17,1,0,1,0,0,//DTT transmitted
[107]##
[108]# Number of ISEs
[109]0,
[110]##
[111]# Number of ISSs
[112]0,
[113]##
[114]# Number of MEAs
[115]0,

M1CPTA2005I
B-149 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[116]# Factors a,b

[117]##
[118]# Number of CONs (Factors a,b)
[119]0,
[120]# Number of ISMs
[121]0,
[122]##
[123]# NumBlqGenericos
[124]1,
[125]# DirIni, Number, Type, IdxProcome, Function, Data, NumRegistros,
OrdenRegistros, F.Escalado, FormatoRegistros,
[126]70,1,50,0,3,0,1,0,1,0,

M1CPTA2005I
1CPT: Substation Central Unit B-150
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.7 PID1 Protocol: PID1.CFG

Data related to the remote control is configured in this file called “pid1.cfg”: general data,
contacts, accumulators, measurements and commands. A signal, meter, measurement or
command from the CPX/CPP will be associated to each contact, accumulator, measurement
and command, respectively. A series of concepts described below will be used for this file:
• Contactos: Digital inputs with or without chronology.
• Acumuladores: Digital inputs that count pulses.
• Medidas: Analogical inputs.
• Mandos: Digital outputs for commands with relays.
• Salidas analógicas: Analogical outputs to send a value through the analogical output of a
device.
• Módulo: Is a group of logic type signals. Modules can be:
- Contact module = 128 contacts.
- Measurement module = 32 measurements.
- Accumulator module = 32 accumulators.
- Command module = 128 commands.
- Analogical output module = 32 measurements.
• Grupo: Basic association of input/output elements. This is a logical type of unit that may,
or may not, have physical correspondence, which will depend on implementation. Groups
can be:
- Group of contacts = 64 elements.
- Group of measurements = 8 elements.
- Group of accumulators = 4 elements.
- Group of commands = 64 elements.
- Group of analogical outputs = 8 elements.

The file format is as follows:

• Configuration Data for the Communications Failure Signal with the Remote
Control
This will be carried out as described under section A.1: [lines 2-3]

Ex: 1,
0,1,0,0,0,

• Data Related to General Adjustments for the Remote Terminal: [Line 5]

NumTR , NivelMonitor , PetCron , PetGenCamb , PID1TipoMaestro ,

• NumTR: Terminal number.

• NivelMonitor: Level of monitorization of traces.
• PetCron: Bit that indicates if records for chronological changes are activated (1) or not
(0). This value can be modified by communications from the master station.
• PetGenCamb: Bit that indicates if general request for changes is used: (0) it is used, and
(1), it is not used. This has been set out this way to ensure compatibility with old
configurations. This value can be modified by communications from the master station.
• PID1TipoMaestro: Indicates the type of communication with the remote control. Two
values can be applied: 0, indicates that communication is made through Master-Slave; 1,
indicates that the communication is between Master-Master. The default value is zero (0).

Ex: 66,0,1,0,0,

M1CPTA2005I
B-151 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Related to Timeouts from the Remote Terminal: [Line 6]

TC1 , TC2 , TC3 ,

• TC1: Waiting time between the last bit received from reception and the setting of the RTS
prior to transmission.
• TC2: Waiting time between the setting of the RTS up to the forwarding of the first
Transmission bit (timing for the activation of the PTT in communication via Radio).
• TC3: Timing that the RTS is maintained after Transmitting the last bit of the frame.

Ex: 250,200,200,

• Data Related to Parameters Belonging to the Remote Terminal: [Line 7]

CM1 , TFC , TSL1 , TM1 , TS3 , IntervSincro ,

DispersionPID1 , TS2 , Tac , TipoRTU ,

• CM1: Number of accounts for the handling of the value of a measurement as a change.
The default value is 7 accounts.
• TFC: Timing for communication failure (in minutes). The range of solid values is 1-200.
• TSL1: Timing for silence on line (in sec.), which is the time that has lapsed since a correct
message was received, even if not addressed to the same. The default value is 20
seconds.
• TM1: Maximum validity time for the selection of a command (in sec.). The default value is
30 seconds.
• TS3: Time employed by the Remote terminal to be progressively set as regards date/hour
sent by slow synchronization (in minutes). The default value is 1 minute.
• IntervSincro: Interval of time lapsed between two consecutive updates for the hour in a
slow synchronization process (in sec.). The TS3 value is divided between this value in
order to calculate the steps to be undertaken in this process. The default value is 15
seconds.
• DispersionPID1: Maximum time difference between the PID1 time and the GPS or UCS
time in order to begin to use the PID1 time instead of GPS. In Sec.
• TS2: Difference in time between the SCADA and the CPX/CPT time in order to admit
slow synchronization (in msec.). The default value is 120 msec.
• TipoRTU: Type of RTU that defines communication with SCADA (COSINOR=0 and
SIEMENS=1). The default value is 0.
• Tac: Timeout between characters to consider a different frame (in msec). This parameter
is only used in CPX-A. For CPX-B, this parameter is read but not in use (a timeout
between characters is used that is calculated automatically as a function of the serial port
baud rate).

Ex: 8,5,120,30,1,15,60,120,44,0,

M1CPTA2005I
1CPT: Substation Central Unit B-152
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Communications with the Master Station: [Line 8]

Puerto , Veloc , TipoPar , NumBits , NumStop , TamFIFO ,

• Puerto: Communication port. Possible values are COM1, COM2 and COM3 for CPX
models. For CPP models possible values are COM1 and COM2.
• Veloc: Baud rate. Possible values are 110, 150, 300, 600, 1200, 2400, 4800, 9600 baud.
• TipoPar: Type of parity. It can apply values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’, ‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 5,6,7 and 8 bits.
• NumStop: Number of stop bits. It can apply values 1 and 2.
• TamFIFO: Number of characters to be used to programme the UART’s FIFO. This
parameter is used to ensure that no characters are lost during excess workloads in the
CPX/CPP. Nevertheless, if TAC parameter is used, it must be adjusted to value 1
because, if this is not implemented, communication failures will take place.

Ex: COM1,600,I,8,2,1,

• Data Related to the Functionality of the Generation of Periodic, Spontaneous

Change: [Line 11]

Punto , Minuto ,

• Punto: Identification of the signal to be used. The point identification is used, which is a
consecutive number commencing from the first signal obtained from the first group of the
first module, consecutively numbered until the last contact. If the Point value is -1, this
functionality is disabled.
• Minuto: Number of interval minutes between two changes of signal. Each Minuto
generates a change in the signal identified as Punto. The status of the signal alternates
with each change. The range for this field is 1 ... 1440 minutes.

Ex: 3,60,

• Data Related to the Functionality of the Rebounce Filter in Digital Changes.

Depending on the values configured, when more NumCambios are received during the time set
by SegEspDesact, the changes from this signal are disabled until another configurable timing
lapses, SegEsperaAct, without receiving changes. Enabling/disabling is only effective for
changes forwarded to control facility, and does not affect internal changes in the CPX/CPP. [line
14]

Activado , SegEspDesact , SegEsperaAct , NumCambios ,

• Activado: If functionality is enabled (1) or disabled (0).

• SegEspDesact: Interval of reception time for NumCambios for the deactivation of the
signal. (10 ... 32767)
• SegEsperaAct: Interval of time that must lapse without receiving any change from a
specific signal in order to activate the same. (10 ... 32767)
• NumCambios: Maximum number of changes allowed within the timing SegEspDesact
before deactivating the signal (1... 32767).

Ex: 1,10,10,10,

M1CPTA2005I
B-153 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Related to the Number of Modules for each of the Timings included in the
Remote Control: [Line 16]

N_Mod_Cnt , N_Mod_Acu , N_Mod_Med , N_Mod_Man , N_Mod_Sal_Ana ,

• N_Mod_Cnt: Number of contact modules (maximum 8).

• N_Mod_Acu: Number of accumulator modules (maximum 1).
• N_Mod_Med: Number of measurement modules (maximum 3).
• N_Mod_Man: Number of command modules (maximum 4).
• N_Mod_Sal_Ana: Number of analogical output modules (maximum 3).

Ex: 2,1,1,1,1,

• Data Related to the Configuration of CONTACT Modules: [Lines 18-34]

NumModCnt ,
ModNum , NumGrps ,
GrpNum , NumCnts ,
DirEq , ISC , Neg , (*) (**) (***)

(*) This is repeated for each group contact. There will be as many as indicated under
NumCnts.
(**) This is repeated for each group from the corresponding to the contact module. There will
be as many as indicated under NumGrps.
(***) This is repeated for each of the remote control contact modules. There will be as many as
indicated under NumModCnt.

• NumModCnt: Number of contact modules (maximum 8).

• ModNum: Module number (i).
• NumGrps: Number of module contact groups (maximum 2).
• GrpNum: Group number (j).
• NumCnts: Number of contacts that belong to the group j (maximum 64).
• DirEq: Address of the device that the CPX/CPP signal belongs to, associated to the
contact in question.
• ISC: PROCOME label for the CPX/CPP signal.
• Neg: Negation bit for the CPX/CPP signal.

Ex: 2, // Num. of contact modules

# * FIRST MODULE
1,2, // ModNum, Num_Grp
# ---- Primer Grupo
0,64, // GrpNum, Num_Cnt
256,25,0,
256,0,0,
…
19,21,0,
# ---- Second Group
1,64, // GrpNum, Num_Cnt
19,25,0,
19,28,0,
…
11,100,0,
# * SECOND MODULE
…

M1CPTA2005I
1CPT: Substation Central Unit B-154
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for the ACCUMULATOR Modules: [Lines 36-48]

NumModAcu ,
ModNum , NumGrps ,
GrpNum , NumAcus , (***)
DirEq , CON , (*) (**)

(*) This is repeated for each accumulator of the group in question. There will be as many as
indicated under NumAcus.
(**) This is repeated for each group of the corresponding accumulator module. There will be
as many as indicated under NumGrps.
(***) This is repeated for each module of accumulators in the remote control. There will be as
many as indicated under NumModAcu.

• NumModAcu: Number of accumulator modules (maximum 1).

• ModNum: Module number (i).
• NumGrps: Number of accumulator groups in the module i (maximum 8).
• GrpNum: Group number (j).
• NumAcus: Number of accumulators that belong to group j (maximum 4).
• DirEq: Address of the device that the CPX/CPP meter associated to the accumulator in
question belongs to.
• CON: PROCOME label for the CPX/CPP meter.

Ej: 1, // Num. Of Accumulator modules

# * FIRST MODULE
1,2, // ModNum, Num_Grp
# ---- First Group
0,4, // GrpNum, Num_Acu
2,0, // 1
2,2, // 2
2,3, // 3
3,0, // 4
# ---- Second Group
1,2, // GrpNum, Num_Acu
3,2, // 1
3,3, // 2

• Configuration Data for Module MEASUREMENT: [Lines 52-68]

NumModMed ,
ModNum , NumGrps ,
GrpNum , NumMeds , (***)
DirEq , MEA , Correccion , Offset , (*) (**)

(*) This is repeated for each measurement of the group in question. There will be as many
as indicated under NumMeds.
(**) This is repeated for each group from the corresponding measurement module. There will
be as many as indicated under NumGrps.
(***) This is repeated for each module of the remote control measurements. There will be as
many as indicated under NumModMed.

• NumModMed: Number of measurement modules (maximum 3).

• ModNum: Module number (i).
• NumGrps: Number of measurement groups from module i (maximum 4).
• GrpNum: Group number (j).

M1CPTA2005I
B-155 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumMeds: Number of measurements that belong to group j (maximum 8).

• DirEq: Address of the device that the CPX/CPP measurement, associated to this remote
control measurement, belongs to.
• MEA: PROCOME label for the CPX/CPP measurement.
• Correccion: Multiplying correction factor that enables converting measurement values in
device accounts to PID1 protocol measurement values (normally set to 1.0).
• Offset: Displacement that enables conversion of measurement values in device
accounts to PID1 protocol measurement values (normally set to 0.0).

Correction and Offset factors are applied to measurement values in accounts forwarded by the
devices to the Central Unit, in order to obtain these values in PID1 protocol format and finally be
transmitted to the Control Centre.

Valor_Medida_PID1 = ( Valor_Medida_Equipo * Correccion ) + Offset

In addition, based on the values calculated under the PID1 protocol format, the PID1 emulator
from the Central Unit will obtain the difference between the current value and the previous value
for each measurement in order to compare the same against the value of the CM1 parameter
(number of accounts in the PID1 protocol format, for handling as a change in the value of a
measurement), which indicates if the measurement has changed the number of accounts
indicated by the parameter.

Since measures are coded in 12 bits (just the same as Procome protocol used for the
communication of control with level 1 devices) in the PID1 protocol profile implemented in the
Central Unit, values 1.0 and 0.0 are used as Correccion and Offset factors, respectively.

Ej: 1, // Num. Of Measurement modules

# * FIRST MODULE
1,3,// ModNum, Num_Grp
# ---- Primer Grupo
0,8, // GrpNum, Num_Med
1,0,1.0,0.0, // 1
1,1,1.0,0.0, // 2
…
7,2,409.6,0.0, // 8
# ---- Second Group
1,8, // GrpNum, Num_Med
7,1,0.956522,0.0, // 1
3,1,1.0,0.0, // 2
…
9,0,1.0,0.0, // 8
# ---- Third Group
…

M1CPTA2005I
1CPT: Substation Central Unit B-156
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for COMMAND Modules: [Lines 71-85]

NumModMan ,
ModNum , NumGrps ,
GrpNum , NumMans , (***)
DirEq , ISE , DirEqBlq , ISCBlq , NegBlq , (*) (**)

(*) This is repeated for each command from the group in question. There will be as many as
indicated underNumMans.
(**) This is repeated for each group from the corresponding command module. There will be as
many as indicated under NumGrps.
(***) This is repeated for each of the command modules from the remote control. There will be
as many as indicated under NumModMan.

• NumModMan: Number of command modules (maximum 4).

• ModNum: Module number (i).
• NumGrps: Number of command groups from module i (maximum 2).
• GrpNum: Group number (j).
• NumMans: Number of commands that belong to group j (maximum 64).
• DirEq: Address of the device that the CPX/CPP command belongs to, associated to the
remote control’s command.
• ISE: PROCOME label for the CPX/CPP command.
• DirEqBlq: Address of the device that the control blocking signal belongs to.
• ISCBlq: PROCOME label for the command blocking signal.
• NegBlq: Negation bit for the blocking signal.

Ej: 1, // Num. Of Command modules

# * FIRST MODULE
1,2, // ModNum, Num_Grp
# ---- First Group
0,64, // GrpNum, Num_Man
# 0,0,0,0,0,// 0 Reserve
1,8,0,0,0, // 1
1,5,0,0,0, // 2
…
16,3,0,0,0, // 64
# ---- Second Group
1,1, // GrpNum, Num_Man
16,5,0,0,0, // 1

• Configuration Data for the ANALOGICAL OUTPUT Modules

This function is used for modifying the value of analogical outputs for the devices connected to
the CPX/CPT from the control facility. The value associated to the analogical output, which must
be forwarded to the device, is received from the control facility by means of the corresponding
message: [lines 88-104]

NumModSal ,
ModNum , NumGrps ,
GrpNum , NumSal , (***)
DirEq , ISM , (*) (**)

(*) This is repeated for each measurement for the group in question. There will be as many as
indicated under NumSal.
(**) This is repeated for each group from the corresponding module of measurements. There
will be as many as indicated under NumGrps.

M1CPTA2005I
B-157 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

(***) This is repeated for each module of measurements from the remote control. There will be
as many as indicated under NumModSal.

• NumModSal: Number of modules for Analogical Outputs (maximum 3).

• ModNum: Module number (i).
• NumGrps: Number of output groups for module i (maximum 4).
• GrpNum: Group number (j).
• NumSal: Number of outputs that belong to group j (maximum 8).
• DirEq: Address of the device that the CPX/CPP analogical output belongs to, associated
to the analogical output of the remote control.
• ISM: PROCOME label for the CPX/CPP analogical output.

Ex: 1, // Number of Output modules

# * FIRST MODULE
1,3,// ModNum, Num_Grp
# ---- First Group
0,8, // GrpNum, NumSal
1,0,// 1
1,1,// 2
…
7,2, // 8
# ---- Second Group
1,8, // GrpNum, Num_Sal
7,1, // 1
3,1,// 2
…
9,0,// 8
# ---- Third Group
…

The file remains as follows:

[1] # CONFIGURATION OF THE ISCs
[2] 1,
[3] 0,1,0,0,0, // Communications Failure with the Remote Control
[4] # CONFIGURATION OF THE TR
[5] 66,0,1,0, // TR Number , NivMonitor, chronology, PetGenCamb
[6] 250,200,200,// TC1, TC2, TC3
[7] 8,5,120,30,1,15,60,120,66,0,
[8] COM1,600,I,8,2,1,// Coms. con EM
[9] # Spontaneous generation of periodic changes
[10] # Point, Interval
[11] 3,60,
[12] # Configuration of rebounds.
[13] # Act, SegEspDesact, SegEspAct, NumCambios,
[14] 1,10,10,10,
[15] # CONFIGURATION OF SIGNALS
[16] 2,1,1,1,1, // N_MOD_CNT, N_MOD_ACU, N_MOD_MED, N_MOD_MAN, N_MOD_SAL
[17] # **** CONTACT MODULES
[18] 2, // Number of contact modules
[19] # * FIRST MODULE
[20] 1,2, // ModNum, Num_Grp
[21] # ---- First Group
[22] 0,64, // GrpNum, Num_Cnt
[23] 256,25,0, // 1 ALL IN REMOTE CONTROL
[24] 256,0,0, // 2 SOME IN LOCAL

M1CPTA2005I
1CPT: Substation Central Unit B-158
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[25] …
[26] 19,21,0, // 64 T-2:ALARM BUCHHOLZ (TPP)
[27] # ---- Second Group
[28] 1,64, // GrpNum, Num_Cnt
[29] 19,25,0, // 65 T-2:A. OIL LEVEL (TPP)
[30] 19,28,0, // 66 T-2:REGUL. ANOMALY (TPP)
[31] …
[32] 11,100,0, // 128 L-4 13:LOW GAS PRESSURE
[33] # * SECOND MODULE
[34] …
[35] # **** ACCUMULATOR MODULES
[36] 1, // Number of Accumulator modules
[37] # * FIRST MODULE
[38] 1,2, // ModNum, Num_Grp
[39] # ---- First Group
[40] 0,4, // GrpNum, Num_Acu
[41] 2,0, // P ENTRANTE T-1
[42] 2,2, // Q INCOMING T-1
[43] 2,3, // Q OUTGOING T-1
[44] 3,0, // P INCOMING T-2
[45] # ---- Second Group
[46] 1,2, // GrpNum, Num_Acu
[47] 3,2, // Q INCOMING T-2
[48] 3,3, // Q OUTGOING T-2
[49] #
[50] #
[51] # **** MEASUREMENT MODULES
[52] 1, // Number of Measurement modules
[53] # * FIRST MODULE
[54] 1,3,// ModNum, Num_Grp
[55] # ---- First Group
[56] 0,8, // GrpNum, Num_Med
[57] 1,0,1.0,0.0, // V LINEA 1 30kV
[58] 1,1,1.0,0.0, // V LINEA 2 30kV
[59] …
[60] 7,2,409.6,0.0, // TAP T-2 (max 9--4096/10=409.6)
[61] # ---- Second Group
[62] 1,8, // GrpNum, Num_Med
[63] 7,1,0.956522,0.0, // SET POINT VOLTAGE T-2
[64] 3,1,1.0,0.0, // ACTIVE POWER T-2
[65] …
[66] 9,0,1.0,0.0, // INTENSITY L-2
[67] # ---- Third Group
[68] …
[69] #
[70] # **** COMMAND MODULES
[71] 1, // Number of Command modules
[72] # * FIRST MODULE
[73] 1,2, // ModNum, Num_Grp
[74] # ---- First Group
[75] 0,64, // GrpNum, Num_Man
[76] # DirEq, ISE, BLQ: EqIsc, BLQ: ISC, Neg
[77] # 0,0,0,0,0,// 0 Reserve for remote control reasons
[78] 1,8,0,0,0, // 1 OPEN 52-1 30kV
[79] 1,5,0,0,0, // 2 CLOSE 52-1 30kV
[80] …
[81] 16,3,0,0,0, // 64 L-9:TRANSITION TO AUTOMATIC
[82] # ---- Second Group

M1CPTA2005I
B-159 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[83] 1,1, // GrpNum, Num_Man

[84] # DirEq, ISE, BLQ: EqIsc, BLQ: ISC, Neg
[85] 16,5,0,0,0, // 65 L-9:TRANSITION TO MANUAL
[86] #
[87] # **** MODULES FOR ANALOGICAL OUTPUTS
[88] 1, // Number of Output modules
[89] # * FIRST MODULE
[90] 1,3,// ModNum, Num_Grp
[91] # ---- First Group
[92] 0,8, // GrpNum, Num_Sal
[93] 1,0,// V LINEA 1 30kV
[94] 1,1,// V LINEA 2 30kV
[95] …
[96] 7,2, // TOMA T-2
[97] # ---- Second Group
[98] 1,8, // GrpNum, Num_Sal
[99] 7,1, // VOLTAGE SET POINT T-2
[100]3,1,// ACTIVE POWER T-2
[101]…
[102]9,0,// INTENSITY L-2
[103]# ---- Third Group
[104]…

M1CPTA2005I
1CPT: Substation Central Unit B-160
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.8 SEVCO 6802 Protocol: SEVCO.CFG

Data related to the remote control is configured in this file called “sevco.cfg”: general data,
digital inputs, meters, measurements and commands. A signal, meter, measurement or
command from the CPX/CPP will be associated to each digital input, meter, measurement and
order for each module, respectively. A series of concepts described below will be used for this
file:

• Entradas Digitales: Digital inputs with or without chronology.

• Contadores: Digital inputs that count pulses.
• Medidas: Analogical inputs.
• Órdenes: Digital outputs for commands with relays.
• Módulo: Is a group of logic type signals. Modules can be:
- Digital input module = 128 signals.
- Measurement module = 16 measurements.
- Meter module = 32 meters.
- Command module = 16 commands.

The file format is as follows:

• Configuration Data for the Communications Failure Signal with the Remote
Control
This will be carried out as described under section A.1: [lines 2-3]

Ex: 1,
0,1,0,0,0,

• Data Related to General Adjustments in the Remote Terminal: [Line 5]

NumTR ,

• NumTR: Terminal number.

Ex: 55,

• Configuration Data for Communications with the Master Station: [Line 6]

Puerto , Veloc , TipoPar , NumBits , NumStop NumPorts ,

• Puerto: Communication port. Possible values are COM1, COM2 and COM3 for the CPX
models. For CPP model possible values are COM1 and COM2..
• Veloc: Baud rate. Possible values are 110, 150, 300, 600, 1200, 2400, 4800, and 9600
baud.
• TipoPar: Type of parity. It can apply values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’, ‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 5,6,7 and 8 bits.
• NumStop: Number of stop bits. It can apply values 1 and 2.
• NumPorts: Number of ports used for communications with the control room. Default value
= 2. Value 1 will be assigned FOR THE CPP. If there are 2 ports, only the first one will be
indicated, COM1; the other one is assigned internally to COM2.

Ex: COM1,600,N,8,2,2,

M1CPTA2005I
B-161 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Regarding Timeouts from the Remote Terminal: [Line 13]

TimeRTS_CTS , TimeCTS_TD , TimeTD_RTS , NumCaractFF ,

• TimeRTS_CTS: Waiting time as from the onset of the RTS up to the onset of the CTS (in
msec.).
• TimeCTS_TD: Waiting time as from the onset of the CTS until the first Transmission bit is
forwarded (in msec.).
• TimeTD_RTS: Maintenance time for the RTS after transmitting the last bit from the frame
(in msec.).
• NumCaractFF: Number of FF characters to be added to the queue of the message.

Ex: 60,60,60,2,

• Data Related to the Number of Modules for each of the Timings Set Up in the
Remote Control: [Line 14]

N_Mod_ED , N_Mod_Med , N_Mod_Man , N_Mod_Con , N_Reg_Crono ,

• N_Mod_ED: Number of modules for digital inputs (maximum 15).

• N_Mod_Med: Number of modules for measurements (maximum 15).
• N_Mod_Man: Number of modules for commands (maximum 15).
• N_Mod_Con: Number of modules for meters (maximum 15).
• N_Reg_Crono: Number of chronological registers.

Ex: 2,2,1,1,100,

• Data Related to the Configuration of DIGITAL INPUT modules:

[Lines 16-30]

NumModED ,
ModNum , NumEDs ,
DirEq , ISC , (*) (**)

(*) This is repeated for each digital entry in the module. There will be as many as indicated
under NumEDs.
(**) This is repeated for each digital input module. There will be as many as indicated under
NumModED.

• NumModED: Number of digital input modules (maximum 15).

• ModNum: Module number.
• NumEDs: Number of digital inputs related to the module in question (maximum 128).
• DirEq: Address of the device that belongs to the CPX/CPP signal associated to the
module’s digital input.
• ISC: PROCOME label for the CPX/CPP signal.

M1CPTA2005I
1CPT: Substation Central Unit B-162
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ej: 2, // Number of modules for Digital Inputs

# * FIRST MODULE
0,128, // ModNum, Num_ED
0,0,
0,0,
10,16,
10,17,
…
11,10,
# * SECOND MODULE
1,64, // ModNum, Num_ED
12,8,
256,8,
…
0,0,

• Configuration Data for METER Modules: [Lines 32-37]

NumModCon ,
ModNum , NumCons ,
DirEq , CON , (*) (**)

(*) This is repeated for each meter from the corresponding module. There will be as many as
indicated under NumCons.
(**) This is repeated for each of the remote control’s meter modules. There will be as many as
indicated under NumModCon.

• NumModCon: Number of meter modules (maximum 15).

• ModNum: Module number.
• NumCons: Number of meters related to the module in question (maximum 16).
• DirEq: Address of the device related to the CPX/CPP meter that is associated to the
remote control’s meter.
• CON: PROCOME label of the CPX/CPP meter.

Ej: 1, // Num. Of Meter modules

# * FIRST MODULE
0,3,// ModNum, Num_Cons
10,3,
10,4,
10,5,

• Data Related to the Configuration of MEASUREMENT Modules: [Lines 39-51]

NumModMed ,
ModNum , NumMeds ,
DirEq , MEA , Factor_a , Factor_b , (*) (**)

(*) This is repeated for each measurement from the corresponding module. There will be as
many as indicated under NumMeds.
(**) This is repeated for each measurement module. There will be as many as indicated under
NumModMed.

• NumModMed: Number of measurement modules (maximum 15).

• ModNum: Module number.

M1CPTA2005I
B-163 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumMeds: Number of measurements related to the corresponding module (maximum

16).
• DirEq: Address of the device related to the CPX/CPP measurement associated to the
remote control’s measurement.
• MEA: PROCOME label for the CPX/CPP measurement.
• Factor_a: Slope of the measurement conversion line.
• Factor_b: Origin of the measurement conversion line.

The ratio for converting the 12 bit digital values forwarded by the relays is obtained through
parameters Factor_a and Factor_b (range –4096 to +4095) to the engineering values handled
by the SEVCO remote control profile.

Valor_Medida_SEVCO = [ ( Valor_Medida_Equipo * Factor_a ) + Factor_b ] / 2

Since measurements from this remote control profile are forwarded as digital values coded with
an 11 bit length word, parameters Factor_a and Factor_b will have to be configured with values
1.0 and 0.0 respectively. Thus, and by means of an internal processing undertaken within the
Central Unit, the 12 bit measurements forwarded by relays are only transferred to an 11 bit
coding to obtain measurement values within the range of the SEVCO remote control profile
(range -2048 to +2047).

Ej: 2, // Num. Of Measurement modules

# * FIRST MODULE
0,16, // ModNum, Num_Meds
0,0,1,0,
0,0,1,0,
…
0,0,1,0,
# * SECOND MODULE
1,5, // ModNum, Num_Meds
0,0,1,0,
18,1,1,0,
…
0,0,1,0,

• Data Related to the Configuration of COMMAND Modules: [Lines 53-62]

NumModMan ,
ModNum , NumMans ,
DirEqAb , ISEAb , DirEqCe , ISCCe , DCOAb , DCOCe , (*) (**)

(*) This is repeated for each command from the corresponding module. There will be as many
as indicated under NumMans.
(**) This is repeated for each of the remote control’s command module. There will be as many
as indicated under NumModMan.

• NumModMan: Number of command modules (maximum 15).

• ModNum: Module number.
• NumMans: Number of commands related to the corresponding module (maximum 16).
• DirEqAb: Address of the device related to the CPX/CPP command to open.
• ISEAb: PROCOME label from the CPX/CPP command to open.
• DirEqCe: Address of the device related to the CPX/CPP command to close.
• ISCCe: PROCOME label for the CPX/CPP command to close.

M1CPTA2005I
1CPT: Substation Central Unit B-164
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DCOAb: Operation code to be forwarded to the device so that it will open the switch. This
code depends on the destination device for the command. Value 2 will be used for
PROCOME devices. For other devices, this will depend on the specific device.
• DCOCe: Operation code that must be forwarded to the device so that it will close the
switch. This code depends on the destination device for the command. Value 2 will be
used for PROCOME devices. For other devices, this will depend on the specific device.

Ej: 1, // Num. Of Command modules

# * FIRST MODULE
0,16, // ModNum, Num_Mans
# ---- First Group
0,0,0,0,
10,12,10,9,2,2,
12,12,12,9,2,2,
…
0,0,0,0,

The file remains as follows:

[1] # CONFIGURATION OF ISCs

[2] 1,
[3] 0,1,0,0,0, // Communication failure with Remote Control
[4] # CONFIGURATION OF THE TR
[5] 55, // TR Number
[6] COM1,600,N,8,2, // Coms. con EM
[7] # Command timing for the RTS
[8] # a,b,c,d
[9] # a: waiting time from the moment that the RTS is activated until the CTS
is activated
[10] # b:time from the moment that the RTS is activated until it begins to
transmit.
[11] # c:time that the RTS remains active after transmitting the last
character
[12] # d: FF nº to be added to the message queue
[13] 60,60,60,2, // RTS Timings
[14] 2,2,1,1,100, // N_MOD_ED, N_MOD_EA, N_MOD_SD, N_MOD_CON, N_REG_CRON
[15] # **** DIGITAL INPUT MODULES
[16] 2, // Number of Digital Input modules
[17] # * FIRST MODULE
[18] 0,128, // ModNum, Num_DE
[19] 0,0,//reserve
[20] 0,0, //reserve
[21] 10,16,//D01 int open
[22] 10,17,//D01 int closed
[23] …
[24] 11,10, //D01 directional ground trip
[25] # * SECOND MODULE
[25] 1,64, // ModNum, Num_DE
[26] 12,8,//D03 blocking by CMB
[27] 256,8,//D03 maintenance switch
[28] …
[29] 0,0, //reserve
[30] # **** METER MODULES
[31] 1, // Number of Meter modules
[32] # * FIRST MODULE
[33] 0,3,

M1CPTA2005I
B-165 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[34] 10,3,
[35] 10,4,
[36] 10,5,
[37] # **** MEASUREMENT MODULES
[38] 2, // Number of Measurement modules
[39] # * FIRST MODULE
[40] 0,16,// ModNum, Num_Med
[41] 0,0,1,0,
[42] 0,0,1,0,
[43] …
[44] 0,0,1,0,
[45] # * SECOND MODULE
[46] 1,5, // ModNum, Num_Grp
[47] 0,0,1,0,
[48] 18,1,1,0,
[49] …
[50] 0,0,1,0,
[51] # **** COMMAND MODULES
[52] 1, // Number of Command modules
[53] # * FIRST MODULE
[54] 0,16, // ModNum, Num_Man
[55] # ---- First Group
[56] # DirEqAb, ISEAb, DirEqCe, ISECe
[57] 0,0,0,0,
[58] 10,12,10,9,//D01
[59] 12,12,12,9,//D03
[60] …
[61] 0,0,0,0,

M1CPTA2005I
1CPT: Substation Central Unit B-166
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.9 Protocolo Wisp+.: WISP.CFG

The configuration file for Extended Wisp + (Wisp.cfg) Protocol consists of five different parts.
The first counts on generic data, both internal for the Central Unit and communication
parameters that identify Wisp+ (configuration of the communication port, RTU number, etc.).
The other four identify the relationship between CPX/CPP-Wisp+ as regards commands, digital
signals, analogical measurements and meters.

Lines that are preceded in the configuration file by a '#' symbol and the information presented in
each line after a '//' symbol, are comments whose only objective is that of clarifying the meaning
of each group of parameters. In fact, the file should always be self-explanatory.

Due to system requirements, parameters for each section must be configured by placing Wisp+
in ascending order and its numbers (i.e. first 1,1,; and after 1,2, etc.).

A comma must be placed after each parameter (even after the last parameter on each line).

The file format is as follows:

• Configuration Data for the Communications Failure Signal with the Remote
Control
This will be carried out as described under section A.1: [lines 2-3]

Ex: 1,
0,1,0,0,0,

• Data for RTU Emulation: [Line 5]

DirRTUEmul , SistPert , Max_Replay , Broadcast ,

• DirRTUEmul: Base RTU address to be emulated.

• SistPert. System that it belongs to.
• Max_Replay. Maximum length of package in bytes.
• Broadcast. Group that it belongs to.

Ex: 24,0,200,0,

M1CPTA2005I
B-167 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Port Communications: [Line 7]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications Port. Possible values are COM1, COM2, COM3 and COM4 for
CPX models.
• Veloc: Baud rate. Possible values are 2400, 4800, 9600 and 19200 baud.
• TipoPar: Type of parity. It can apply values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’, ‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. It can apply values 1 and 2.

Ej: COM1,1200,e,8,1,

• General Data on Remote Control Timing: [Line 10]

RTSon , RTSoff , ErrorTel , DespachoSincroST ,

• RTSon: Timing that the RTS is maintained ON before transmitting (in msec.).
• RTSoff: Timing that the RTS is maintained OFF after transmitting (in msec.).
• ErrorTel: Timing before an error message is issued from the remote control (in sec.).
• DespachoSincroST: Indicates if the control facility synchronizes with the Central Unit with
summer/winter time (1), or with the standard time (0). It will be configured to 1 for the new
control facility (SAC), but it will be configured to 0 if the control facility is the old one
(WESDAC). If it is not configured, the default value applied by the Central Unit will be 0.

Ex: 22,22,90,1,

• Configuration Data for Remote Control Orders

A command from the CPX/CPP is associated to each of the remote control orders. It is
essential to put DirWisp (Seg + Nsal) in ascending order: [lines 16-23]

NumOrdenes , TimeOut
Seg , NSal , Pulso , DirEq , ISE , DCO , (*)

(*) This is repeated for every remote control order. There will be as many as indicated under
NumOrdenes. They will be displayed in ascending order under DirWisp. As commands are
double, there will be two lines per pulse (ON / OFF)

• NumOrdenes: Number of remote control orders.

• TimeOut: Time Out for the commands in seconds.
• Seg: Segment within Wisp+ protocol.
• Nsal: Output within the segment.
• Pulso: Pattern for differentiating ON / OFF in each of the double commands.
• DirEq: Address of the device related to the CPX/CPP.
• ISE: PROCOME label for the device’s command.
• DCO: DCO used for the implementation of the command (default value =2).

Ex: 2,10,// Num. Orders,TimeOut

1,2,5,30,3,2,
1,2,6,30,2,2,

M1CPTA2005I
1CPT: Substation Central Unit B-168
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

This example indicates that there are 2 commands configured with a timeout of 10 seconds for
the orders. In this case, these commands correspond to segment 1 and output 2 of the Wisp+,
the first with a type 5 input pulse, and the second with a type 6 input pulse. The final values for
each line are those that correspond to the internal command of the Central Unit.
• Configuration data for simple contact type signals from the remote control
A digital signal from the CPX/CPP is associated to each signal of this type from the remote
control. It is essential to put DirWisp (Seg + Sal) in ascending order: [lines 25-41]

Ngrupo , (*)
Seg , Sal , Prio ,
DirEq , ISC , Neg , (**)

(*) Indicates how many groups (Seg,Sal,Prio) there are.

(**) There will be 8 lines (Seg,Sal,Prio) for each group.

• NGrupo: Number of configured groups of signals.

• Seg: Segment within Wisp+ protocol.
• Sal: Output within the segment.
• Prio: Priority.
• DirEq: Address of the device related to the CPX/CPP’s digital signal. If it does not have a
signal (-1).
• ISC: PROCOME label for the digital signal of the device. If it does not have a signal (-1).
• Neg: Value 0 or 1. If the signal is negated, it would be (1).

Ej: 1,// Number of groups of signals

1,1,0, // Segment, output, priority
37,4,0,
37,0,0,
-1,-1,0,
258,0,0,
-1,-1,0,
37,31,0,
37,11,0,
-1,-1,0,

• Configuration Data for Remote Control Measurements

A CPX/CPP measurement is associated to each of the measures from the remote control: [lines
43-48]

NumMeds ,
DirSeg , NMTel , Dir , Med , Tasa , Alis , Prio , Escala , ...

... Offset , Bipolar , (*)

(*) This is repeated for each of the measurements undertaken with the remote control. There
will be as many as indicated under NumMeds.

• NumMeds: Number of remote control measurements.

• DirSeg: Segment of the measurement within the Wisp+ protocol.
• NMTel: Number of the measurement within the segment.
• Dir: Address of the device related to the CPX/CPP measurement.
• Med: PROCOME label for the measurement of the device.
• Tasa: Periodic value in seconds to acquire the measurement.

M1CPTA2005I
B-169 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Alis: Minimum amount that the value must vary in order to be deemed as being
significant. This value is indicated under PROCOME accounts.
• Prio: Priority.
• Escala: Escalating factor which multiplies the value of the measurement in the accounts.
• Offset: Escalating factor that is added to the above value. The default value is 0.
Ex:
MEATEL = MEAUCS * Escala + Offset
• Bipolar: Indicates if measurement is bipolar (1) (takes positive or negative values) or
unipolar (0) (which only takes positive values). The default value is 0.

Ex: 2, // Num. medidas

1,1,30,3,20,30,0,1,0,0,
2,2,30,6,20,30,0,1,0,1,

• Configuration Data for the Remote Control Meters

A CPX/CPP meter is associated to each of the remote control meters. It is essential to put
DirWisp (Seg + N_Cont) in ascending order: [lines 50-56]

NumConts , P_Cong ,
Seg , N_Cont , Dir CON , Prio , (*)

(*) It will be repeated for each of the remote control meters. There will be as many as
indicated under NumConts. They will be placed in ascending order of DirWisp.

• NumConts: Number of remote control meters.

• P_Cont: Freezing period.
• Seg: Segment of the meter within the Wisp+ protocol.
• N_Cont: meter number within the segment.
• Dir: Address of the device related to the CPX/CPP meter.
• CON: PROCOME label for the device’s meter.
• Prio: Priority.

Ej: 2,30// Num.Meters,per. Freezing in minutes

1,1,27,1,0,
1,2,28,9,0,

The file remains as follows:

[1] # RTU CEI101 configuration.

[2] 1,
[3] 0,1,0,0,0,
[4] # RTU address to be emulated
[5] 24,0,200,0, // Base
[6] # Port communications parameters
[7] COM1,1200,e,8,1,
[8] # RTS ON (CS0T) and RTS OFF timings in milliseconds, remote control error
in
[9] # seconds, DespachoSincroST
[10] 22,22,90,1,
[11] #
[12] #
[13] #
[14] #

M1CPTA2005I
1CPT: Substation Central Unit B-170
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[15] #
[16] # Orders
[17] 2,10, // Num. Of orders, Timeout of the commands in seconds
[18] # Association of Wisp Segment, Wisp Output, Pulse (i.e.:
5=00000101)DIR,ISE
[19] #It is essential to place DIR Wisp
[20] # in ascending order
[21] # Segment, output number,Pulse ,DIR procome, Num command, DCO,
[22] 1,2,5,30,3,2,
[23] 1,2,6,30,2,2,
[24] #
[25] # Nº of signal groups
[26] 1,
[27] # Association of CISP Segment, Wisp output number, Priority
[28] # It is essential to put DirWisp in ascending order.
[29] #y in groups.
[30] Group 1 , each group must be followed by 8 lines with the corresponding
DIR, ISC
[31] #trio (otherwise, you must set –1) and negated yes (1) or no (0)
[32] # DIR,ISC are the PROCOME address and the signal from the 7IRD where the
contact
[33] # is located
[34] 1,1,0,
[35] 37,4,0,
[36] 37,0,0,
[37] -1,-1,0,
[38] 258,0,0,
[39] -1,-1,0,
[40] 37,31,0
[41] 37,11,0
[42] #
[43] # Measurements
[44] 2, // Number of measurements
[45] # DIR Segment,Num remote control Measurement,DIR Procom,Num MED
Central,Rate (in seconds)
[46] #,Dejagging,Priority, Conversion Factor, Offset, Bipolar
[47] 1,1,30,3,20,30,0,1,0,0,
[48] 1,2,30,6,20,30,0,1,0,1,
[49] #
[50] # Meters
[51] 2,30,// Num. Meters, freezing period in minutes
[52] # Segment Association, Meter number, DIR, ISC, Priority
[53] # It is essential to put DIRWisp
[54] # in ascending order
[55] 1,1,27,1,0,
[56] 1,2,28,9,0

M1CPTA2005I
B-171 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.10 Communications with SIEMENS SIMATIC PLCs

The following communications files are going to be described in this section:

• COMSINEC.CFG: Configuration file for communications between CPX/CPP/CPT and the

PLC and the SCD.
• COM3964R.CFG: Configuration file for the COM3964R task.
• COMPLC.CFG: Configuration file for the COMPLC task.
• COMSCD.CFG: Configuration file for the COMSCD task.
• MODBMSPLC.CFG: Configuration file for the MODBMSPLC task.

B.10.1 SINEC H1 Protocol: COMSINEC.CFG (only CPD)

Communications between the CPD and the PLC and SCD to forward and send DBs towards
and from the PLC and SCD are configured in this file. The name of the file is “comsinec.cfg”.
The file format is as follows:
• Data Related to Communications from the CPD with the PLC and SCD: [Lines
2-12]

TimeReconex ,
dd1PLC , dd2PLC , dd3PLC dd4PLC , dd5PLC , dd6PLC ,
dd1SCD , dd2SCD , dd3SCD , dd4SCD , dd5SCD , dd6SCD ,
TSAPlocPLC_r ,
TSAPlocPLC_w ,
TSAPremPLC_r ,
TSAPremPLC_w ,
TSAPlocSCD_r ,
TSAPlocSCD_w ,
TSAPremSCD_r ,
TSAPremSCD_w ,

• TimeReconex: Reconnection time (in sec.).

• dd1PLC
• dd2PLC
• dd3PLC Ethernet Address
• dd4PLC of the PLC
• dd5PLC
• dd6PLC

• dd1SCD
• dd2SCD
• dd3SCD Ethernet Address
• dd4SCD of the SCD
• dd5SCD
• dd6SCD

• TSAPlocPLC_r: Local TSAP for connection with the PLC (read).

• TSAPlocPLC_w: Local TSAP for connection with the PLC (write).
• TSAPremPLC_r: Remote TSAP for connection with the PLC (read).
• TSAPremPLC_w: Remote TSAP for connection with the PLC (write).
• TSAPlocSCD_r: Local TSAP for connection with the SCD (read).
• TSAPlocSCD_w: Local TSAP for connection with the SCD (write).

M1CPTA2005I
1CPT: Substation Central Unit B-172
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• TSAPremSCD_r: Remote TSAP for connection with the SCD (read).

• TSAPremSCD_w: Remote TSAP for connection with the SCD (write).

Ex: 1,
08,00,06,01,00,21,
08,00,06,01,00,16,
8 1,
____8__2,
16, 1,
___16__2,
SCDRLOC_,
SCDWLOC_,
SCDRREM_,
SCDWREM_,

• DBs Data: [Lines 14-19]

NumDBs ,
DBNum , DwIni , DwFin , Tipo , AvisoPLC , AvisoSCD , Nodo , (*)

(*) This is repeated for each DB. There will be as many as indicated under NumDBs.

• NumDBs: Maximum number of DBs with 256 Data Words each.

• DBNum: DB number.
• DwIni: Initial DB Data Word.
• DwFin: Final DB Data Word.
• Tipo: Type of DB (0 = Read; 1 = Write).
• AvisoPLC: Indicates if COMPLC task must be warned if there is a change in the DB in
question.
• AvisoSCD: Indicates if COMSCD task must be warned if there is a change in the DB in
question.
• Nodo: Indicates if the DB in question belongs to the PLC (0), or to the SCD (1).

Ex: 4,// Num. DBs

100,0,254,1,0,0,0,
44, 0,254,0,1,0,0,
70, 0,254,1,0,0,1,
72, 0, 20,0,0,1,1,

M1CPTA2005I
B-173 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file remains as follows:

[1] # COMMUNICATION DATA WITH THE PLC AND THE SCD

[2] 1,// Reconnection time
[3] 08,00,06,01,00,21, // PLC Ethernet Address
[4] 08,00,06,01,00,16, // SCD Ethernet Address
[5] 8 1, // PLC’s local TSAP
[6] ____8__2, // PLC’s local TSAP
[7] 16 1, // PLC’s Remote TSAP
[8] ___16__2, // PLC’s Remote TSAP
[9] SCDRLOC_, // SCD’s Local TSAP
[10] SCDWLOC_, // SCD’s Local TSAP
[11] SCDRREM_, // SCD’s Remote TSAP
[12] SCDWREM_, // SCD’s Remote TSAP
[13] # DB DATA
[14] 4, // Number of DBs
[15] # DBNr,DwInic,DwFin,Tipo(R/W),Aviso_COMPLC,Aviso_COMSCD,Nodo (0 - PLC) (1
- SCD),
[16] 100,0,254,1,0,0,0, // CPD --> PLC
[17] 44, 0,254,0,1,0,0, // PLC --> CPD
[18] 70, 0,254,1,0,0,1, // CPX --> SCD
[19] 72, 0, 20,0,0,1,1, // SCD --> CPD

B.10.2 RK512/3964R Protocol: COM3964R.CFG

This file contains the necessary data to configure the COM3964R task. The name of the file is
“com3964r.cfg”. The format of the file is as follows:
• Data related to Reconnection Time: [Line 2]

TimeReconex , PlcRedun , IdxDbChk , NumReint ,

• TimeReconex: Reconnection time (in msec.).

• PlcRedun: Indicates if the CPX/CPT is redundant (1) or not (0). If it is redundant, the
status is checked (active/passive), before commencing to interrogate the PLC. It can only
be interrogated if the CPX/CPT is active.
• IdxDbChk: DB Index used to check the performance of the CPU on the PLC. The first
Data Word of this DB is used as a meter and is monitored in the CPX/CPT. If its value is
not modified during five cycles, the CPU will be deemed as being at a standstill, even if
communications are working, because they are handled by the CP and not by the CPU.
• NumReintentos: Number of retries before deeming the procedure in process as having
failed. Default value: 6.

Ex: 5000,0,2,6,

M1CPTA2005I
1CPT: Substation Central Unit B-174
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Communications with the PLC: [Line 3]

Puerto , Veloc , TipoPar , NumBits , NumStop , TamFIFO ,

• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4.
• Veloc: Baud rate. Possible values are 110, 150, 300, 600, 1200, 2400, 4800, 9600 and
19200 baud.
• TipoPar: Type of parity. It can apply values ‘N’ or ‘n’ (none), ‘O’ or ‘o’ (even number), ‘E’
or ‘e’ (odd number)‘M’ or ‘m’ (mark) and ‘S’ or ‘s’ (space).
• NumBits: Number of bits. Possible values are 5,6,7 and 8 bits.
• NumStop: Number of stop bits. It can apply values 1 and 2.
• TamFIFO: Size of the FIFO for the communications UART. It must be configured as
size 1 FIFO.

Ex: COM1,9600,P,8,1,1,

• DBs Data: [Lines 4-6]

NumDBs ,
DBNum , DwIni , DwFin , Tipo , AvisoPLC , Sincro , (*)

(*) .This is repeated for each DB. There will be as many as indicated under NumDBs.

• NumDBs: Maximum number of DBs with 256 Data Words each.

• DBNum: DB number.
• DwIni: Initial DB Data Word.
• DwFin: Final DB Data Word.
• Tipo: Type of DB (0 = Read; 1 = Write).
• AvisoPLC: Indicates if COMPLC task must be warned if there is a change in the DB in
question.
• Sincro: Indicates if the DB in question is used for synchronizing the PLC with the
CPX/CPT date and hour. If the value is 1, it will be used for synchronizing the PLC. The
date and time format is displayed in the following table. It will be considered as index 0
(zero) as from the initial DW configured under the field DwIni, i.e., DW0 will be DWIni.

DW Description
0 1
1 Julian Day Calendar as from the 01/01/1990
2
Milliseconds in the day as from 00:00
3

Ex: 1,// Num. DBs

110,0,170,1,1,0,

The file remains as follows:

[1] # CONFIGURATION OF TASK COM3964R

[2] 5000,0,2,6,// Reconnect time
[3] COM1,9600,P,8,1,1,// Communications parameters
[4] 1,// Maximum number of DBs
[5] # DB Number, DwIni, DwFin, Type(R/W), AvisoCOMPLC, Node
[6] 110,0,170,1,1,0,// First DB

M1CPTA2005I
B-175 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.10.3 Configuration file for COMPLC Task: COMPLC.CFG

A series of data corresponding to the PLC are configured in this file called “complc.cfg”:

• PLC digital signals, commands and measurements.

• Digital signals, commands and measurements generated through the PLC’s DBs.
• CPX/CPP/CPT signals and commands to be forwarded to the PLC.

The file has the following format:

• Data on the Total Number of PLC Digital Signals, Commands and
Measurements, and Type of Communications Protocol to be Used: [Line 1]

N_ISCs , N_ISEs , N_MEAs , N_CONs , TipoProtocPLC ,

• N_ISCs: Total number of PLC digital signals.

• N_ISEs: Total number of PLC commands.
• N_MEAs: Total number of PLC measurements.
• N_CONs: Total number of PLC meters.
• TipoProtocPLC: Indicates the type of communications protocol to be used. Allowed
values are 0 for COM3964R and 1 for MODBUS_PLC. The default value is 0.

Ex: 488,60,6,4,0, //com.3964r

• Configuration Data for PLC Digital Signals

This is configured as described under section A.1: [lines 3-8]

Ex: 488, // Num. signals

0,0,0,0,0,
1,0,0,0,0,
2,0,0,0,0,
…
487,0,1,1,0,

• Configuration Data for PLC Commands

This is configured as described under section A.1: [lines 10-15]

Ex: 60,// Num. commands

0,266,-1,1000,0,266,-1,266,-1,0,0,
1,266,-1,1000,0,266,-1,266,-1,0,0,
2,266,-1,1000,0,266,-1,266,-1,0,0,
…
59,266,-1,1000,0,266,-1,266,-1,0,0,

M1CPTA2005I
1CPT: Substation Central Unit B-176
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for PLC Measurements

This is configured as described under section A.1: [lines 17-22]

Ex: 6,// Num. measurements

1.0,0.0,
1.0,0.0,
1.0,0.0,
…
1.0,0.0,

• Configuration Data for PLC Meters

This is configured as described under section A.1: [lines 24-28]

Ej: 4,// Num. meters

1.0,0.0,
1.0,0.0,
1.0,0.0,
1.0,0.0,

• Configuration Data for ISCs to be generated when Changes take place in

Specific DBs in the PLC
A mapping is made between a DB bit of one Data Word from the PLC and an ISC signal. When
a change takes place in the bit contained in that Data Word from the DB in the PLC, the ISC
signal will be generated: [lines 30-36]

N_ISCs ,
DB , DW , Bit , ISC , (*)

(*) This is repeated for each of the ISCs to be generated. There will be as many as indicated
under N_ISCs.

• N_ISCs: Number of ISCs to be generated.

• DB: PLC’s DB.
• DW: Data Word from the PLC.
• Bit: Bit from the DW Data Word from the PLC’s DB whose change in value prompts the
generation of the ISC signal.
• ISC: PROCOME label for the digital signal that is generated when a change takes place
in the DW Bit belonging to the DB.

As can be observed from the second line of the following example, a change in the 0 bit in the
Data Word 0 of the DB 44 in the PLC will prompt the generation of the ISC 1.

Ex: 487,// Num. signals

44,0,0,1,
44,0,1,2,
44,0,2,3,
…
44,39,15,487,

M1CPTA2005I
B-177 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for the DBs to be updated when changes are detected in
the ISCs associated to the CPX/CPP/CPT
A mapping is made between the ISC from the CPX/CPP/CPT and a one Data Word bit from a
DB in the PLC. All changes that take place in the ISC of the CPX/CPP/CPT will be reflected in
this bit contained in that Data Word from the DB in the PLC: [lines 38-44]

N_DBs ,
DirEq , ISC , DB , DW , Bit , (*)

(*) This is repeated for each DB of the PLC where changes are generated. There will be as
many as indicated under N_DBs.

• N_DBs: Number of DBs of the PLC wherein changes are generated when the associated
ISCs of the CPS change.
• DirEq: Address of the device related to the CPX/CPP/CPT ISC that generates changes in
the PLC.
• ISC: PROCOME label from the CPX/CPP/CPT ISCs that generate changes in the PLC.
• DB: PLC’s DB which displays the changes that have taken place in the CPX/CPP/CPT
ISC signal.
• DW: Data Word that belongs to the PLC’s DB which displays the changes that have
taken place in the CPX/CPP/CPT ISC signal.
• Bit: Bit from the DW Data Word that belongs to the PLC’s DB which displays the changes
that have taken place in the CPX/CPP/CPT ISC signal

As can be observed from the second line of the following example, a change in the ISC 21 from
device 43 will be reflected in the bit 0 of Data Word 0 of the PLC’s DB 100.

Ex: 1589,// Num. DBs

43,21,100,0,0,
43,22,100,0,1,
43,4,100,0,3,
…
256,1,100,199,15,

• Configuration Data for the CPX/CPP/CPT’s ISES that are generated by

Indication from the PLC’s DBs
A mapping is made between the CPX/CPP/CPT’s ISEs and one Data Word bit from a DB in the
PLC. When a change takes place in this PLC bit, the ISE command is generated from the
CPX/CPP/CPT: [lines46-52]

N_ISEs ,
DB , DW , Bit , DirEq , ISE , DCO , (*)

(*) This is repeated for each ISE to be generated. There will be as many as indicated under
N_ISEs.

• N_ISEs: Number of commands that are generated from the CPX/CPP/CPT.

• DB: PLC’s DB that prompts the generation of the ISE command from the CPX/CPP/CPT.
• DW: Data Word that belongs to the PLC’s DB which prompts the generation of the ISE
command from the CPX/CPP/CPT.
• Bit: Bit from the DW Data Word that belongs to the PLC’s DB, which prompts the
generation of the CPX/CPP/CPT ISE command.
• DirEq: Address of the device related to the command that is generated from the
CPX/CPP/CPT.

M1CPTA2005I
1CPT: Substation Central Unit B-178
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• ISE: PROCOME label for the generated command.

• DCO: DCO of the command generated by the CPX/CPP/CPT.

As can be observed from the second line of the following example, a change in the 0 bit of
Data Word 100 from the PLC’s DB 44 will generate ISE 1 in device 43 with the DCO 2.
Commands can be associated to any of the configured equipment, namely, they need not
belong to the own COMPLC logic equipment.

Ex: 144,// Num. commands

44,100,00,43,1,2, //db,dw,bit, dir,ise,dco,
44,100,01,43,0,2,
44,100,02,62,1,2,
…
44,108,15,195,0,2,

• Configuration Data from the CPX/CPP/CPT’s ISES to be forwarded to PLC

A mapping is made between the CPX/CPP/CPT’s ISE and one Data Word bit from a DB in the
PLC: [lines 54-60]

N_ISEs ,
DirEq , ISE , DB , DW , Bit , (*)

(*) This is repeated for each of the ISEs to be implemented by the PLC. There will be as many
as indicated under N_ISEs..

• N_ISEs: Number of CPX/CPP/CPT’s ISEs to be implemented in the PLC.

• DirEq: Address of the device related to the ISE command from the CPX/CPP/CPT.
• ISE: PROCOME label for the ISE command from the CPX/CPP/CPT.
• DB: PLC’s DB associated to CPX/CPP/CPT’s ISE.
• DW: Data Word related to the PLC’s DB associated to the CPX/CPP/CPT’s ISE
command .
• Bit: Bit for the PLC’s DW Data Word associated to the CPX/CPP/CPT’s ISE command.

As can be seen in the second line of the example below, running the command 00 of the
COMPLC 266 logic equipment generates the activation of DW 200 bit 00 [00->15] of DB 100.
This bit activation bit will be on for 5 seconds in order for the PLC to be aware and operate
accordingly. Obviously, the commands to be configured in this section must COMPULSORILY
be from the COMPLC logic equipment (equipment 266, 267 268.. if there were different
COMPLC instances with this number of equipment defined in the PROTASK.CFG), since
otherwise, said tasks will not be running them.

Ex: 61,// Num. commands

266,00, 100,200,00,// dir,ise, db,dw,bit,
266,01, 100,200,01,
…
266,60, 100,203,12,

M1CPTA2005I
B-179 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for the PLC’s DBs that generate measurements

A mapping is made between the PLC’S DB Data Word and the generated MEA. Any change
that takes place in this PLC Data Word will be reflected in the generated MEA: [lines 63-68]

N_MEAs ,
DB , DW , MEA , FuncConvMea , Fa Fb (*)

(*) This is repeated for each PLC’s DB that generates any measurement. There will be as
many as indicated under N_MEAs.

• N N_MEAs: Number of measurements generated by changes in the DB associated to the

PLC.
• DB: PLC’s DB whose change generates the MEA measurement.
• DW: Data Word related to the PLC’s DB whose change generates the MEA
measurement.
• MEA: PROCOME label for the MEA measurement generated by the changes that have
taken place in the DW Data Word of the PLC’s DB.
• FuncConvMea: Conversion function of the received measurement (from DB.DW to MEA),
such that the following values are accepted:
- Conversion Value 0 or 1: the received value (in word format) is saved as such into
MEA. This is the function to be used by default, thus existing old substation
configuration files remain compatible.
- Conversion value 2 (scaled): in this case the formula y = fa*x+fb will be used, by which
the value obtained can be scaled as required by using the two parameters below.
• Fa: Conversion Factor a (multiplier) when the scaled conversion function is selected (y =
fa*x+fb). Default value is 1.0.
• Fb: Conversion Factor b (offset) when the scaled conversion function is selected (y =
fa*x+fb). DEfault value is 0.0.

As can be observed from the second line of the following example, a change in Data Word 40 of
the PLC’s DB 44 will generate MEA 0.

Ex: 6,// Num. measurements (DB:DW->MEA)

44,40, 0,0,
44,41, 1,1,
44,42, 2,2,0.125,0.0,// MEA2 divides the value received into 8
…
44,45, 5,2,1.0,-9.0, // MEA6 subtracts 9 from the value
received

• Configuration Data for the DBs to be updated when changes in the associated
CPX/CPP/CPT MEAs are detecte
A mapping is made between the CPX/CPP/CPT’s MEA and a Data Word from a PLC's DB.
Every change that takes place in the CPX/CPP/CPT's MEA will be reflected in the PLC's DB's
Data Word.: [lines 70-76]

N_DBs ,
DirEq , MEA , DB , DW , FuncConvMea , Fa , Fb , (*)

(*) This is repeated for each of the PLC’s DBs that generate measurements. There will be as
many as indicated under N_DBs.

M1CPTA2005I
1CPT: Substation Central Unit B-180
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• N_DBs: Number of DBs in the PLC wherein changes are generated when the associated
CPX/CPP/CPT’s MEAs change.
• DirEq: Address of the device related to the CPX/CPP/CPT’s MEA which generate
changes in the PLC.
• MEA: PROCOME label of the MEA measurement of the CPX/CPP/CPT that generates
changes in the PLC.
• DB: DB of the PLC which reflects the changes that have taken place in the
CPX/CPP/CPT’s MEA measurement.
• DW: Data Word belonging to the PLC’s DB which reflects the changes that have taken
place in the CPX/CPP/CPT’s MEA measurement.
• FuncConvMea: Conversion Function of the measurement to be sent (from MEA to
DB.DW) such that the values below are accepted:
- Conversion value 0 or 1: the value (in word format) is sent divided by 2, since while
values are saved into the database as 12 bit, they are saved as 11 bit in the PLC, so
that this Conversion is necessary. This is so in order to keep compatibility with the
older software where the Conversion function was fixed. This will be the function to be
used by default, thus existing old substation configuration files remain compatible.
- Conversion Value 2 (scaled): in this case the formula y = fa*x+fb, by which the value
to be sent can be scaled as required, by using the two parameters below. For
example, the measurement value of the old SCD used in old CPDs, was multiplied by
8 before the value was sent.
• Fa: Conversion Factor a (multiplier) when the scaled conversion function is selected (y =
fa*x+fb). Default value is 1.0.
• Fb: Conversion Factor b (offset) when the scaled conversion function is selected (y =
fa*x+fb). Default value is 0.0.

C As can be observed from the second line of the following example, a change in MEA 0 in
device 43 will be reflected in Data Word 128 of the PLC’s DB 110.

Ex: 11,// Num. DBs (MEA->DB:DW)

43,0, 110,128,0, // from 12 to 11 bits (divided into 2)
43,1, 110,129,1, // from 12 to 11 bits (divided into 2)
43,2, 110,130,2,3.0,0.0, // forwards triple the value in BD
…
43,10, 110,131,2,1.0,-6.0, //6 units less will be forwarded

• Configuration Data for the PLC’s DBs that generate Meters

A mapping is made of the PLC’s DB Data Word and CON generated. Any change that takes
place in this PLC Data Word will be reflected in the generated CON: [lines 78-83]

N_CONs , N_DWsCON ,
DB , DW , CON , FuncConv , (*)

(*) This is repeated for each of the PLC’s DBs that generate a meter. There will be as many as
indicated under N_CONs.
• N_CONs: Number of meters generated by changes in the PLC’s associated DB.
• N_DWsCON: Number of PLC DWs mapped to a UCS counter. Possible values are 1
or 2, the default value being 1.
• DB: PLC’s DB whose change is generated by the CON meter.

M1CPTA2005I
B-181 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• DW: PLC’s DB word the change of which generates the CON counter. In case the CON
counter is mapped to 2 PLC’s DWs, this parameter indicates the lower DW.
• CON: PROCOME label of the CON meter generated by the changes produced in the DW
Data Word of the PLC’s DB.
• FuncConv: Conversion function for the meter (from DB.DW to CON).

As can be observed from the second line of the following example, a change in the Data Word
50 of the PLC’s DB 44 will generate CON 0.

Ex: 4,1,// Num. Meters, NumDWsCON

44,50,0,1,
44,51,1,1,
44,52,2,1,
44,55,5,1,

The file remains as follows:

[1] 488,60,6,4,0,// Number of ISCs, ISEs, MEAs, CONs, TipoProtocPLC,

[2] # CONFIGURATION OF PLC’s ISCs
[3] 488, // Number of ISCs
[4] 0,0,0,0,0,
[5] 1,0,0,0,0,
[6] 2,0,0,0,0,
[7] …
[8] 487,0,1,1,0,
[9] # CONFIGURATION OF PLC’s ISE
[10] 60, // Number of ISEs
[11] 0,266,-1, 1000, 0,266,-1,266, -1, 0, 0,
[12] 1,266,-1, 1000, 0,266,-1,266, -1, 0, 0,
[13] 2,266,-1, 1000, 0,266,-1,266, -1, 0, 0,
[14] …
[15] 59,266,-1, 1000, 0,266,-1,266, -1, 0, 0,
[16] # CONFIGURATION OF PLC’s MEA
[17] 6, // Number of MEAs
[18] 1.0,0.0,
[19] 1.0,0.0,
[20] 1.0,0.0,
[21] …
[22] 1.0,0.0,
[23] # CONFIGURATION WITH PLC’s CON
[24] 4, // Number of CONs
[25] 1.0,0.0,
[26] 1.0,0.0,
[27] 1.0,0.0,
[28] 1.0,0.0,
[29] # ISCs TO BE GENERATED AS COMPLC CHANGES
[30] 487,// Number of ISCs
[31] # db,dw,bit,isc,
[32] 44, 0, 0, 1,
[33] 44, 0, 1, 2,
[34] 44, 0, 2, 3,
[35] …
[36] 44,39,15,487,
[37] # ISCs TO BE UPDATED IN DB AND DW FOR THE PLC
[38] 1589,// Number of DBs

M1CPTA2005I
1CPT: Substation Central Unit B-182
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[39] # DIR, ISC, DB, DW, BIT

[40] 43,21,100, 0, 0,
[41] 43,22,100, 0, 1,
[42] 43, 4,100, 0, 3,
[43] …
[44] 256,1,100,199,15,
[45] # ISEs TO BE IMPLEMENTED BY THE CPX/CPT on the devices
[46] 144,// Number of ISEs
[47] # db,dw,bit, dir,ise,dco
[48] 44,100,00, 43,1,2,
[49] 44,100,01, 43,0,2,
[50] 44,100,02, 62,1,2,
[51] …
[52] 44,108,15,195,0,2,
[53] # ISEs TO BE IMPLEMENTED BY THE PLC
[54] 61,// Number of ISEs
[55] # dir,ise, db,dw,bit
[56] 266,00, 100,200,00,
[57] 266,01, 100,200,01,
[58] 266,02, 100,200,02,
[59] …
[60] 266,60, 100,203,12,
[61] # Measurements forwarded by the PLC
[62] # db, dw, MEA, Func. Convers.
[63] 6,// Number of MEAs (DB:DW->MEA)
[64] 44,40, 0, 0,
[65] 44,41, 1, 1,
[66] 44,42, 2, 2,0.125,0.0, // MEA2 divides the value received into 8
[67] …
[68] 44,45, 5, 2,1.0,-9.0, // MEA6 subtracts 9 from the value received
[69] MEAs TO BE UPDATED IN DB AND DW FOR THE PLC
[70] 11,// Number of DBs (MEA->DB:DW)
[71] # DIR, MEA, DB, DW, Func. Convers.
[72] 43,0, 110,128,0,// goes from 12 to 11 bits (divided into 2)
[73] 43,1, 110,129,1,// goes from 12 to 11 bits (divided into 2)
[74] 43,2, 110,130,2,3.0,0.0,// forwards triple the value in BD
[75] …
[76] 43,10, 110,131,2,1.0,-6.0,// forwards 6 units less than BD
[77] # Meters forwarded by the PLC
[78] 4,1,// Number of CONs, NumDWsCON
[79] # db, dw, CON, Func. Convers.
[80] 44,50, 0, 1,
[81] 44,51, 1, 1,
[82] 44,52, 2, 1,
[83] 44,55, 5, 1,

M1CPTA2005I
B-183 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.10.4 Configuration File for COMSCD Task: COMSCD.CFG (only CPD)

A mapping of signals and measurements of the CPD and the PLC is undertaken in this file
called “comscd.cfg”, with DBs from SCD, as follows:

• ISC from the CPD.......................................... One Data Word bit from a DB from the SCD.
• One Data Word bit from a PLC’s DB............. One Data Word bit from a DB from the SCD.
• MEA from the CPD ........................................ Data Word from a DB from the SCD.
• Data Word (measurement) of a PLC’s DB. . Data Word from a DB from the SCD.

The file has the following format:

• Configuration Data for the CPDs ISCs to be forwarded to the SCD
A mapping between the CPDs ISC and a bit (Bit) from a Data Word (DW) belonging to a DB
(DB) of the SCD will be carried out. Any change that takes place in the CPDs ISC will be
reflected in the bit of the DB Data Word that has been assigned to the same: [lines 3-9]

N_ISCs ,
DirEq , ISC , DB , DW , Bit , Neg , (*)

(*) This is repeated for each ISC. There will be as many as indicated under N_ISCs.

• N_ISCs: Number of ISCs from the CPD to be forwarded to the SCD.

• DirEq: Address of the device related to the CPDs ISC.
• ISC: PROCOME label of the CPDs ISC.
• DB: DB assigned to the CPDs ISC.
• DW: Data Word that belongs to the DB assigned to the CPDs ISC.
• Bit: Bit for the DW Data Word belonging to the DB assigned to the CPDs ISC.
• Neg: Negation Bit for the ISC.

As can be observed from the second line of the following example, a change in the signal 50 of
device 256 will be reflected in bit 6 of the Data Word 100 of DB 70 in the SCD.

Ex: 134,// Num. signals

256,50,70,100,6,0,
256,51,70,100,8,0,
43,0,70,100,9,0,
…
220,3,70,131,11,0,

• Configuration Data for the PLC’s DBs to be forwarded to SCD

A bit (BitSCD) from a Data Word (DWSCD) belonging to a DB (DBSCD) from the SCD is
assigned to each bit (BitPLC) from a Data Word (DWPLC) belonging to a DB (DBPLC) of the
PLC. Every change that takes place in this bit from the PLC will be reflected in the
corresponding bit that has been assigned in the SCD: [lines 11-17]

N_DBs ,
DBPLC , DWPLC , BitPLC , DBSCD , DWSCD , BitSCD , (*)

(*) This is repeated for each of the DBs from the PLC. There will be as many as indicated
under N_DBs.

M1CPTA2005I
1CPT: Substation Central Unit B-184
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• N_DBs: Number of DBs from the PLC to be forwarded to the SCD.

• DBPLC: PLC’s DB that generates changes.
• DWPLC: Data Word from the DB DBPLC that generates changes.
• BitPLC: Bit from the Data Word DWPLC of the DB DBPLC that generates changes.
• DBSCD: DB from the SCD on which changes are generated.
• DWSCD: Data Word from the DB DBSCD on which changes are generated.
• BitSCD: Bit from the Data Word DWSCD belonging to the DB DBSCD on which changes
are generated.

As can be observed from the second line of the following example, a change in bit 11 of the
Data Word 54 of DB 44 of the PLC will be reflected in bit 0 of Data Word 100 of DB 70 of the
SCD.

Ex: 41,// Num. DBs

44,54,11,70,100,0,
44,54,13,70,100,4,
44,55,7,70,101,0,
…
44,26,13,70,123,10,

• Configuration Data for CPD Measurements to be forwarded to the SCD

One Data Word (DW) bit (Bit) will be assigned to a MEA from the CPD belonging to a DB (DB)
from the SCD. A change in the CPDs MEA will be reflected in the bit assigned from the SCD:
[lines 21-25]

N_MEAs ,
DirEq , MEA , DB , DW , FuncConv , (*)

(*) This is repeated for each of the MEAs. There will be as many as indicated under N_MEAs.

• N_MEAs: Number of MEAs from the CPD to be forwarded to the SCD.

• DirEq: Address of the device related to the CPDs MEA.
• MEA: PROCOME label for the CPDs MEA.
• DB: DB that is going to reflect the changes that have taken place in the CPDs MEA.
• DW: Data Word belonging to the DB where the changes in the CPDS MEA are going to
be reflected.
• FuncConv: Conversion factor for the MEA. It is not used (always set to 0)

As can be observed from the second line of the following example, a change in measurement 0
of device 43 will be reflected in Data Word 1 of DB 70 of the SCD.

Ex: 70,// Num. mesurements

43,0,70,1,0,
43,3,70,2,0,
266,0,70,3,0,
…
156,0,70,81,0,

M1CPTA2005I
B-185 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Measurements (DBs) from the PLC to be forwarded to

the SCD
One Data Word (DWSCD) belonging to the SCD’s DB (DBSCD) will be assigned to each Data
Word (DWPLC) belonging to a DB (DBPLC) from The PLC. All changes that take place in this
Data Word from the PLC will be reflected in the corresponding Data Word that has been
assigned in the SCD: [lines 27-33]

N_DBs ,
DBPLC , DWPLC , DBSCD , DWSCD , FuncConv , (*)

(*) This is repeated for each measurement DB defined from the PLC. There will be as many
as indicated under N_DBs.

• N_DBs: Number of measurement DBs from the PLC to be forwarded to the SCD.
• DBPLC: PLC’s DB that generates changes.
• DWPLC: Data Word from DB DBPLC that generates changes.
• DBSCD: DB from the SCD on which changes are generated.
• DWSCD: Data Word from the DB DBSCD on which changes are generated.
• FuncConv: Conversion function for measurement. Not used (always set to 0).

As can be observed from the second line of the following example, a change in the Data Word 3
of the PLC’s DB 44 will be reflected in Data Word 82 of the DB 70 of the SCD.

Ex: 5,// Num. DBs

44,3,70,82,0,
44,3,70,83,0,
44,0,70,84,0,
44,0,70,85,0,
44,5,70,86,0,

The file remains as follows:

[1] # File: COMSCD.CFG

[2] # NUMBER OF ISCs TO BE FORWARDED TO SCD
[3] 134,
[4] # DIR, ISC, DB, DW, BIT
[5] 256,50,70,100,6,0,
[6] 256,51,70,100,8,0,
[7] 43,0,70,100,9,0,
[8] …
[9] 220,3,70,131,11,0,
[10] # NUMBER OF SIGNALS FROM THE PLC TO THE SCD
[11] 41,
[12] # (PLC)DB, DW, BIT, (SCD)DB, DW, BIT
[13] 44,54,11,70,100,0,
[14] 44,54,13,70,100,4,
[15] 44,55,7,70,101,0,
[16] …
[17] 44,26,13,70,123,10,
[18] # NUMBER OF MEAs TO BE FORWARDED TO THE SCD
[19] 70,
[20] # DIR, MEA, DB, DW, FUNC CONV
[21] 43,0,70,1,0,
[22] 43,3,70,2,0,
[23] 266,0,70,3,0,

M1CPTA2005I
1CPT: Substation Central Unit B-186
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[24] …
[25] 156,0,70,81,0,
[26] # NUMBER OF MEASUREMENTS TO BE FORWARDED TO THE SCD FROM THE PLC
[27] 5,
[28] # DB, DW, DB, DW, FUNC CONV
[29] 44,3,70,82,0,
[30] 44,3,70,83,0,
[31] 44,0,70,84,0,
[32] 44,0,70,85,0,
[33] 44,5,70,86,0,

B.10.5 MODBUS PLC Protocol: MODBMSPLC.CFG

This file contains necessary data to configure the MODBMSPLC task. The name of the file is
“modbmsplc.cfg”. File format is as follows:
• Data on the reconnection time: [line 2]
DirEquipo , ToutResp , TimeWaitEntreMsj , NivelTraza ,

• DirEquipo: Equipment address. This field is meaningless when communications are via
TCP/IP, but it is kept in case serial communications are used, the software of which is not
implemented as yet.
• ToutResp: PLC response time (in msec).
• TimeWaitEntreMsj: Timeout between messages (in msec). When this time is activated
messages idle to give the PLC enough time to deal with requests. Default value is 0,
namely, disabled.
• NivelTraza: Task tracing level. Default value is 0.

Ex: 1,1000,100,0,

• Configuration data of PLC communications: [line 4]

DirIP , PuertoIP ,

• DirIP: IP address of the PLC.

• PuertoIP: IP port of the PLC. The MODBUS port is usually 502, but it can be any other if
the PLC supports it.

Ex: 192.168.20.2,502,

• Data on MODBUS registers that are being dealt with: [lines 6-10]
NumBlqRegsMO ,
DBUS
DBNum , DwIni , NumRegs , DirRegIni Tipo , Func , AvisoP , (*
MODBUS MODBUS LC

(*) This repeats for each Register Block. There will be as many as indicated under
NumBlqRegsMODBUS.

The MODBMSPLC task is created by the COMPLC task, data being transferred through a
common memory area, so that at the time of configuring it, the contents of the COMPLC.CFG
configuration file must be taken into account. On the one hand, the MODBMSPLC task reads a
number of registers from the PLC whose information is placed into the common area for later
treatment by the COMPLC task, and on the other hand, writes to the PLC the data placed in
that common area by the COMPLC task.

M1CPTA2005I
B-187 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Each MODBUS register block represents every operation to carry out in PLC communications.
Each block associates to a pair [DB, DW], (DataBase number and DataWord number) which
has to be previously defined in the configuration file of its associated COMPLC task.

• NumBlqRegsMODBUS: Number of MODBUS blocks to be requested from the PLC.

• DBNum: Number of DataBase associated to the Block in question.
• DwIni: First word (DataWord) of the DB.
• NumRegs: Number of registers of the block in question.
• DirRegIniMODBUS: Block starting MODBUS address in the PLC
• Tipo: Type of operation (0 = Read; 1 = Write).
• FuncMODBUS: MODBUS function to be used. (03 = Read Holding Register, 04 = Read
Input Register, 16 = Write Multiple Register)
• AvisoPLC: Indicates whether to notify the COMPLC task if a change occurs in the DB in
question. It will be set to 1 in case of reading PLC data.

Ex: 3,// NumBlqRegsMODBUS

044, 0,109, 200,0,03,1, // Lectura 109 regs Dir.0x0200
110, 0,100, 400,1,16,0, // Escritura 100 regs Dir 0x0400
110,100,115, 500,1,16,0, // Escritura 115 regs Dir 0x0500

The file becomes:

[1] # CONFIGURATION OF MODBMSPLC TASK

[2] 1,1000,100,0,
[3] # Parameters of TCP/IP Communications with the PLC
[4] 192.168.20.2,502,
[5] # Data on MODBUS registers to request
[6] 3,// Number of Blocks of MODBUS registers
[7] # Number DB, DwIni, DwFin, Tipo (R/W), AvisoCOMPLC, Node
[8] 044, 0,109, 200,0,3,1,// Read 109 regs. of DirMODBUS 0x0200
[9] 110, 0,100, 400,1,16,0,// Write 100 regs. of DirMODBUS 0x0400
[10] 110,100,115, 500,1,16,0,// Write 115 regs. of DirMODBUS 0x0500

M1CPTA2005I
1CPT: Substation Central Unit B-188
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.11 GESTEL Protocol: GESTEL.CFG

Data related to the remote control is configured in this file, called “GESTEL.CFG”, as follows:
general data, digital inputs (ED), digital outputs (SD), analogical inputs (EA) and meter inputs
(EC).

The above-mentioned data is grouped into modules. The CPX/CPP/CPT can have a maximum
of 128 modules, numbered from 0 to 127. Each module can be one of the types mentioned
above: ED, SD, EA, and EC. Each module can have a maximum of 16 signals, called channels,
all of which are of the same type. A signal, meter, measurement or command shall be assigned
to each channel from the CPX/CPP/CPT, depending on the type of channel in question.

The configured modules do not have to be consecutive and different types can be inserted.

The file format is as follows:

• Configuration Data for the Communications Failure signal with the Remote
Control
This will be carried out as described under section A.1: [lines 4 and 5]

Ex: 1,
0,1,0,0,0,

• Data regarding general adjustments for the Remote Terminal: [Line 7]

NumTR , PeriodCont , NDecHistCont , PetAlGrupo , NivelMonitor , SwPetAlGrupo ,

• NumTR: Remote terminal number.

• PeriodCont: Period for meter integration. This parameter is expressed in minutes. Its
default value will be 15 minutes.
• NdecHistCont: Number of decimals for the values that are stored in the history record
meter registers. The forwarding format for these values is carried out in physical units in
Full-Exponent format and, hence, the exponent value must be defined (this, as it is used
in negative value, tallies with the number of decimals displayed by the meter value).
• PetAlCamb: Bit that indicates if the group alarm request is used (general request for
changes to all remote facilities). Its value can be: (1) It is used and (0), it is not used. This
value can be modified by communication from the central control facility.
• NivelMonitor: Level of monitorization of traces.
• SwPetAlGrupo: This field indicates if, during the start-up, a reply will be made to the
Group Alarm request messages, if set to 1, or if it is not going to be replied, when it is set
to 0. The default value is 0.

Ex: 66,15,2,1,0,0,

M1CPTA2005I
B-189 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data for Communications with Master Station: [Line 8]

Puerto , Veloc , TipoPar , NumBits , NumStop , TamFIFO ,

• Puerto: Communications port. Possible values are COM1, COM2 and COM3 for CPX
models. For CPP and CPT models possible values are COM1 and COM2..
• Veloc: Baud rate. Possible values are 110, 150, 300, 600, 1200, 2400, 4800, 9600,
19200 baud.
• TipoPar: Type of parity. It can accept values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd number);
‘E’, ‘e’, ‘p’, ‘P’ (even number).
• NumBits: Number of bits. Possible values are 5, 6, 7 and 8 bits.
• NumStop: Number of stop bits. It can accept values 1 and 2.
• TamFIFO: Size in bytes of the UART’s FIFO. Possible values are: 0,1,4,8 and 14. When
the value is 0, the FIFO is not used.

Ex: COM1,9600,i,8,1,0,

• Data regarding Timeouts in the Remote Terminal: [Line 9]

RTSOn , RTS Off , CD Off , Sw CD , Sw CTS , ErrTeleman ,

• RTS On: Waiting time from the setting of the RTS up to the forwarding of the first
Transmission bit (timing to activate the PTT in Radio communications). (In ms).
• RTS Off: Maintenance time for the RTS after transmitting the last bit of the frame. (In ms)
• CD Off: Maximum waiting time between the moment that the CPX/CPP/CPT decides to
forward a message and the setting of the RTS prior to transmission (In ms.). If during this
waiting time the CD signal is deactivated, then the next step must be undertaken. If this
parameter has been set to 0, no waiting time is required, nor is the CD signal controlled.
• SwCD: Bit that indicates if the CD control is used or not. 0 or 1. If it is activated, a control
will be carried out on the CD signal, in such a way that if it is active, no transmission will
be made. Channels with a continuous carrier must be configured with a zero value (0).
• SwCTS: Bit that indicates if the CTS is used or if it is done by timing. 0 or 1. If it is
activated, a control is carried out on the CTS signal in such a way that when the
CPX/CPP/CPT activates the RTS signal, if the CTS signal is not activated, no forwarding
is made. On the other hand, when it is transmitting, if the CTS signal is deactivated, it
stops transmitting.
• ErrTeleman: Timing awaited without receiving anything from the control facility for this
remote station, before generating the communications failure signal with the Remote
Control. (In Sec.: 300).

Ex: 33,11,11,0,0,300,

M1CPTA2005I
1CPT: Substation Central Unit B-190
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The procedure for transmitting a message would be as represented below in the signals’
flowchart:

RX

CD

TX

RTS

CTS

CDOff RTSOn RTSOff

• Data regarding Modules for Remote Terminal

Now the data for each of the modules must be configured. As mentioned above, each module is
a specific type of module, and modules can be interspersed of each timing. In the first place, the
number of modules available for this remote terminal must be indicated. [line 11]

NumModulos ,

• NumModulos: Total number of modules available for this configuration. All modules must
be included notwithstanding the type of module in question. Values for this field range
between 0 and 128.

Ex: 4,

Data related to each of the modules indicated above will be configured. Due to the fact that
there could be various models of the same type and that these could be interspersed, we will
indicate how to configure the data for each of the types of modules that can be configured. One
of the following blocks must be included for each of the modules.
• General Data for each Module [Lines 13, 21, 27, 33]

ModNum , Tipo , Modo ,

• ModNum: Module number. The value ranges between 0 and 127.

• Tipo: The type of module is indicated in this field: ED  1, EA  2, EC  3, SD  4.
• Modo: Indicates the mode used for interrogating through this module. The values that it
can use are: CAMB_MED  0, CAMBIOS  1, MEDIDAS  2.

Ex: 4,1,0,

M1CPTA2005I
B-191 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding Modules for Digital Inputs (ED) [Lines 14-19]

NumCanales ,
CanalNum , Doble , DirEqOn , IscOn , Neg ,

DirEqOff , IscOff , Neg , DirEqDesc , IscDesc , Neg , (*)

(*) This line is repeated as many times as indicated under the field NCanales.

• NumCanales: Number of module channels.

• CanalNum: Channel number that the data refers to. This value ranges between 0 and 15.
The channels must be configured in order commencing from the lowest (channel 0), and
there must not be any gaps between two channels. If a channel does not physically exist,
it will be configured as reserve with all the data related to the devices and signals by
setting the value -1.
• Doble: Indicates if the channel is double or simple. Simple channels can only set two
status, 1 (one) and 0 (zero). Double channels can set more values than the above and,
thus, they physically occupy two consecutive channels. Data from all the necessary
signals is configured in the first, and the Double field is configured in the second, setting
the value to -1 and the rest of the fields are not configured.

The following fields will only be included if the channel has been configured as simple (0), or as
double (1). If it has been configured as the second channel of a double channel (-1), the
CPX/CPP/CPT program will not read the same.

• DirEqOn: Address of the device related to the status signal On.

• IscOn: PROCOME label of the status signal On.
• Neg: Indicates if the previous signal uses the negated value (1), or not (0).

The following signals will only be included if the signal is double. If the signal has been
configured as simple, the CPX/CPP/CPT program will not read the same.

• DirEqOff: Address of the device related to the Off status signal.

• IscOff: PROCOME label for the status signal Off.
• Neg: Indicates if the previous signal is used negated (1), or not (0).
• DirEqDesc: Address of the device related to the status signal Unknown.
• IscDesc: PROCOME label of the status signal Unknown.
• Neg: Indicates if the previous signal is used negated (1) or not (0).

Ex: 5,
0,0,1,52,0,
1,0,1,48,0,
2,0,-1,-1,0,
3,1,1,37,0,1,38,0,1,39,0,
4,-1,

M1CPTA2005I
1CPT: Substation Central Unit B-192
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Regarding the Modules for Analogical Inputs (EA) [Lines 22-25]

NumCanales ,
CanalNum , DirEq , Mea , Banda , FactorA , FactorB , (*)

(*)This line is repeated as many times as indicated under the field NumCanales.

• NumCanales: Number of module channels.

• CanalNum: Channel number that the data refers to. This value ranges between 0 and 15.
The channels must be configured in order beginning from the lowest (channel 0) and
there must not be any gaps between two channels. If a channel does not physically exist,
it will be configured as reserve, with all the data related to the devices and signals, by
setting the value -1.
• DirEq: Address of the device related to the measurement.
• Mea: PROCOME label for the measurement.
• Banda: Value of the band used for deeming that a change has taken place in the value of
the measurement as a change in the channel. It is a full value. It can range between 0
and 4095.
• FactorA: Slope of the measurement conversion line. It is a real value (floating comma).
• FactorB: Offset of the measurement conversion straight line. It is a real value (floating
comma).

Ex: 3,
0,1,0,30,1.0,0.0,
1,1,1,40,1.0,0.0,
2,1,2,30,1.0,0.0,

• Data regarding Input Modules from the Meter (EC) [Lines 28-31]

NumCanales ,
CanalNum , DirEq , Con , FactorA , FactorB , Hist , (*)

(*) This line is repeated as many times as indicated under the field NumCanales.

• NumCanales: Number of module channels.

• CanalNum: Channel number related to the data. This value ranges between 0 and 15.
Channels must be configured in order, commencing from the lowest (channel 0) and
there must not be any gaps between two channels. If a channel does not physically exist,
it will be configured as reserve with all the data related to the devices and signals by
setting the value to -1.
• DirEq: Address of the device related to the measurement.
• Con: PROCOME label for the meter.
• FactorA: Slope of the measurement conversion line. It is a real value (floating comma).
• FactorB: Offset of the measurement conversion straight line. It is a real value (floating
comma).
• Hist: This parameter indicates if a history record of this channel’s meters will be carried
out. 0  NO, 1  YES, a history record is carried out.

Ex: 3,
0,1,0,1.0,0.0,0,
1,1,1,1.0,0.0,1,
2,1,2,1.0,0.0,0,

M1CPTA2005I
B-193 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data Regarding the Digital Output Modules (SD) [Lines 34-38]

NumCanales ,
CanalNum , Vigilancia , Doble , DirEqAct , IseAct ,

DirEqRep , IseRep , (*)

(*) This line is repeated as many times as indicated under the field NumCanales.

• NumCanales: Number of module channels.

• CanalNum: Number of Channels related to the data. This value ranges between 0 and
15. The channels must be configured in order commencing from the lowest (channel 0)
and there must not be any gaps between two channels. If a channel does not physically
exist, it will be configured as reserve introducing the value zero (0) in the double field and
-1 in the fields DirEqAct and IseAct.
• Vigilancia: This field indicates if the implementation of the command must be monitored.
If it is activated (1), the CPX/CPP/CPT waits during a configurable timing, to find out if the
command has been correctly undertaken, or, on the contrary, if it has failed. Should this
implementation fail, an event is generated which is incorporated to the change queue and
the SCADA indicates that this command has failed. During this period, no other command
received from SCADA is accepted. In order to carry out this monitoring, the signals
associated to these commands must be adequately configured in the file dbase.cfg:
status signal, OK signal and failure signal.
• Doble: Indicates if the channel is double or simple. For simple channels, only the
Activation command is necessary. Both commands are used for double channels; in this
case, a double channel physically occupies two consecutive channels. Data from all the
necessary signals is configured in the first (Activation and Replacement commands), and
the second field is configured with value -1, and the rest of the fields are not configured.
• DirEqAct: Address of the device related to the Activation command.
• IseAct: PROCOME label for the Activation command.
• DirEqRep: Address of the device related to the Replacement.
• IseRep: PROCOME label for the Replacement command.

Ex: 4,
0,0, 0, 1, 0,
1,1, 0, 1, 1,
2,1, 1, 2, 0, 2, 1,
3,0,-1,

M1CPTA2005I
1CPT: Substation Central Unit B-194
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file remains as follows:

[1]# TEST SUBSTATION

[2]#
[3]# ISCs’ CONFIGURATION
[4]1,
[5]0,1,0,0,0, // Communications Failure with the Remote Control
[6]# TR CONFIGURATION
[7]66,15,2,1,0, // TR Num. , Period cont, NumDecContHist,PetAlGrupo, Niv
Monitor
[8]COM1,9600,i,8,1,0,// Coms. con EM
[9]33,11,11,0,0,300,// RTSOn, RTSOff, CDOff, SwCD, SwCTS, ErrTeleman
[10]# MODULE CONFIGURATION
[11]4, // Total number of the module
[12]# CONFIGURATION OF THE FIRST MODULE
[13]3,1,0,// ModNum, Tipo ED, Modo CAMB_MED,
[14]5, // Number of channels
[15]0,0,1,52,0,// 0, Simple, DirEqOn, IscOn
[16]1,0,1,48,0,// 1, Simple, DirEqOn, IscOn
[17]2,0,-1,-1,0,// 2, Reserve,
[18]3,1,1,37,0,1,38,0,1,39,0,
[19]4,-1,//3, Second double channel
[20]# CONFIGURATION OF THE SECOND MODULE
[21]4,2,0,// ModNum, Tipo EA, Modo CAMB_MED,
[22]3, // Number of channels
[23]0,1,0,30,1.0,0.0,// 0,DirEq,Mea,Banda, FactoA, FactorB
[24]1,1,1,40,1.0,0.0,// 1,
[25]2,1,3,30,1.0,0.0,// 2,
[26]# CONFIGURATION OF THE THIRD MODULE
[27]6,3,0,// ModNum, Tipo EC, Modo CAMB_MED,
[28]3, // Number of channels
[29]0,1,0,1.0,0.0,0,
[30]1,1,1,1.0,0.0,1,
[31]2,1,2,1.0,0.0,0,
[32]# CONFIGURATION OF THE FOURTH MODULE
[33]7,3,0,// ModNum, Typo SD, Mode CAMB_MED,
[34]4, // Number of channels
[35]0,0, 0, 1, 0,// 0,No Monitoring, Simple,
[36]1,1, 0, 1, 1, // 1,Monitoring, Simple,
[37]2,1, 1, 2, 0, 2, 1, // 2,Monitoring, Double,
[38]3,0,-1, // 3,Double (Second command),
[39]

M1CPTA2005I
B-195 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.12 SPABUS Master Protocol: SPABUSMS.CFG and

MODULSPA.CFG
The SPABUS master protocol emulator incorporates two configuration files from
CPX/CPP/CPT; one of these will enable emulating each SPA protection device, as if it were a
Procome virtual device (file SPABUSMS.CFG), while the other file (MODULSPA.CFG), will
include the description of each of the SPA protection and control modules that the
CPX/CPP/CPT must communicate with through this emulator.

B.12.1 Device Emulation File: SPABUSMS.CFG

Data from the SPABUS master module is configured in this file, called “spabusms.cfg”:
general master, ISCs, ISEs, MEAs and CONs for each of the PROCOME logic devices on
which the ISCs, ISEs, MEAs and CONs of the real SPA devices will be mapped.
Note: the SPABUS master emulator must be previously registered in the Central Unit, and to this avail, the
following line: 0,SPABUSMS,SPABUSMS,2048,-1, must be added to the CPX/CPP/CPT’s PROTASK.CFG
configuration file.

File format is as follows:

• Port Communication Data: [Line 4]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications port. Possible values are

- Serial port: COM1, COM2, COM3 and COM4 for CPX relays. For CPP and CPT
relays, possible values are COM1 and COM2.
- Virtual Port Terminal Server: only used in the CPT. Possible values are V201..V209
(ports of the first Terminal Server) and V211..V219 (ports of the second Terminal
Server). These virtual ports are declared in TSComs.cfg file.
• Veloc: Baud rate. It can use values 2400, 4800, 9600 and 19200 baud.
• TipoPar: Parity type. It can take the values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd); ‘E’, ‘e’, ‘p’,
‘P’ (even).NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumPuerto: Number of the port where SPABUS equipment are connected. 0=Serial port
above; 1-6= TL176 port. In case of CPT, it can take the values 0 or 1 (0= first fiber optic
port, 1= second port). All SPABUS equipments are connected to the same port. Default
value is 0.

Ex: COM2,9600,E,7,1,

• General Master Data: [Line 7]

TimeLineIdle , RTSon , RTSoff , NumReint ,

EnableChecksum , NivelMonitor ,

• TimeLineIdle: Idle Line timing that is added before each transmission (in msec.).
• RTSon: Timing that RTS is maintained ON before transmitting (in msec.).
• RTSoff: Timing that RTS is kept OFF after transmitting (in msec.).
• NumReint: Number of communication retries with the device.
• EnableChecksum: Calculation of checksum in messages SPA-bus (0: Checksum not
calculated, 1: Checksum is calculated).
• NivelMonitor: Level of monitorization of traces.

Ex: 22,0,0,1,1,0,

M1CPTA2005I
1CPT: Substation Central Unit B-196
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Timing Data for the Master: [Line 12]

TimeExplMed , TimeExplCon , TimeSincMsg , TimeSincDate ,

• TimeExplMed: Exploration timing in measurements (in sec.). Expresses how often

measurement explorations are carried out.
• TimeExplCon: Exploration timing in meters (in sec.). Expresses how often meter
explorations are carried out.
• TimeSincMsg: Synchronization period of milliseconds for SPA devices (in sec.).
• TimeSincDate: Synchronization period for the date and full hour for SPA devices (in sec.).

Ex: 5,10,1,60,

• Data regarding Logic Procome Devices over which Physical SPA Devices are
going to be mapped: [Line 16]

NumEqLogicos , NumPuerto ,

• NumEqLogicos: Number of full SPA devices to be incorporated as Procome logic

equipment in the Central Unit (limited to 60 devices).
• NumPuertos: Port number where SPABUS devices are going to be connected. 0=Serial
port indicated above; 1-6= TL176 Port. All SPABUS devices are connected in the same
port. The default value is 0.

Ex: 52,1,
Note: The parameter NumEqLogicos must be updated in configuration file DBASE.CFG of the Central Unit,
specifically under the section "General substation data”, in such a way that this data will be added to the
parameter value NumEqLogicos which appears in this section.

Data regarding all logic PROCOME devices is listed below (one after the other one), to be
incorporated as devices that emulate the physical SPA devices, on the real time database of the
CPX/CPP/CPT. The following data will be provided for each of the devices:
• General Data regarding the Logic Procome Device that Emulates the SPA
Device: [Line 26]

Dir , TimeOut , N_ISC , ISC Max , N_ ISE , ISE Max ,

N_ ISS , ISS Max , N_ MEA , N_CON , ISCRem ,

• Dir: Procome address of the logic device that is associated to a complete physical SPA
device.
• TimeOut: Timeout for communication errors (in msec.).
• N_ISC: Number of digital signals for the logic device.
• ISCMax: Highest label that can be applied to any ISC from the logic device.
• N_ISE: Number of commands for the logic device.
• ISEMax: Highest label that can be applied to any ISE from the logic device.
• N_ISS: Number of output writes from the logic device.
• ISSMax: Highest label that can be applied to any ISS from the logic device.
• N_MEA: Number of measurements from the logic device.
• N_CON: Number of meters for the logic device.
• ISCRem: PROCOME label for the signal that determines if the logic device is in the
Remote Control, in which case, it will enable the implementation of commands.

M1CPTA2005I
B-197 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Note for the programmer: within the code, it will be named as ISCLocal, but its true significance is as described
above.

Ex: 1,500,108,107,17,16,0,0,8,0,0,

• Data regarding SPA Protection and Control Modules that make up the SPA
Physical Device Emulated by the Procome Logic Device: [lines 28-67]

NumModulos ,
ModuloSPA , DirFisicaSPA , (*)

(*) This is repeated for each module that makes up the SPA device. There will be as many as
indicated under NumModulos.
• NumModulos: Number of SPA protection and control modules that make up the physical
SPA device.
• ModuloSPA: Identification of the SPA module. Maximum 15 characters.
• DirFisicaSPA: Physical address of the SPA module.

Ej: 3, // Num. SPA Modules

SPTO6D3,113, // CONTROL Module
SPCU3C14,114,// OVER AND UNDER-VOLTAGE PROTECTION Module
SPCU1C6,115, // RESIDUAL VOLTAGE PROTECTION Module

• Data regarding Digital Signals (ISCs) from the Logic Device

This is configured as described under section A.1. [lines 35-41]

Ex: 108,// Num. ISCs

00,0,0,0,0,0,
01,0,0,1,0,0,
…
107,1,0,1,0,1,

• Data regarding Commands (ISEs) from the Logic Device

These are configured as described under section A.1. [lines 43-50]

Ex: 17,// Num. ISEs

00,1,36,10000,0,1,36,1,78,0,2,1,71,0,256,15,0,
01,1,37,10000,0,1,37,1,78,0,2,1,71,0,256,15,0,
…
16,1,1,10000,0,1,1,1,-1,0,0,

• Data regarding Output Writes (ISSs) from the Logic Device

This is configured as described under section A.1. [line 52]

Ex: 0,// Num. ISSs

Note: output writes have not yet been used with physical SPA devices.

M1CPTA2005I
1CPT: Substation Central Unit B-198
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding Measurements (MEAs) for the Logic Device

This is configured as described under section A.1. [lines 55-62]

Ex: 8,// Num. MEAs

0.46886447,0.0,
0.46886447,0.0,
…
0.03516484,0.0,

• Data regarding Meters (CONs) for the Logic Device

This is configured as described under section A.1. [line 64]

Ex: 0,// Num. CONs

Note: meters are handled as analogical measurements in SPA physical devices.

The file remains as follows:

[1] # SPABUSMS Configuration.

[2] # This is a TEST configuration
[3] # Communication parameters for the serial port
[4] COM2,9600,E,7,1,
[5] # Idle Line Times,RTS ON,RTS OFF in millisec,Nº Retries,Checksum,Monitor
[6] # RTS must not be used for ABB’s SPA bus
[7] 22,0,0,1,1,0,
[8] # Exploration timings:
[9] # Measurement cycle (sec), Meter cycle (sec),
[10] # Synchronization periods for devices (sec): Synchro Milisec, Synchro
Date and
[11] #Hour,
[12] 5,10,1,60,
[13] # Nº of full ABB SPA Devices (Control Module + Protection Modules)
[14] # connected to ABB's SPA bus.
[15] # Each full SPA Device is equivalent to a logic Procome Device
[16] 52,1,
[17] #
[18] # These configurations are for ABB Devices connected to the SPA bus
[19] #=====================================================================
[20] # LOGIC DEVICE Nº 1 (SPAC-534C4 LINE PITUAÇU 69kV 02J6)
[21] #=====================================================================
[22] # PROCOME Address for the logic Procome device associated to a full SPA
Device from
[23] # ABB,
[24] # TimeOut RX (ms), Nº ISCs, ISC Máx, Nº ISEs, ISE Máx, Nº ISSs, ISS Max,
[25] # Nº MEAs, Nº CONs, ISC Local,
[26] 1,500,108,107,17,16,0,0,8,0,0,
[27] # Nº of modules (Control and/or Protection) that make up ABB’s SPA
Device
[28] 3,
[29] # Identification of SPA Module, Physical address of SPA Module,
[30] SPTO6D3,113,
[31] SPCU3C14,114,
[32] SPCU1C6,115,

M1CPTA2005I
B-199 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[33] # Configuration of digital signals

[34] # Number of ISCs
[35] 108,
[36] # digital signal, alarm, filter activ., filter deact., alarm ,rising
edge alarmº
[37] 0,0,0,0,0,0,
[38] 1,0,0,1,0,0,
[39] 2,0,0,1,0,0,
[40] ...
[41] 107,1,0,1,0,1,
[42] # ISE
[43] 17,
[44] # command,isc status(device, signal nº),timing, negated,isc
ok(device,signal nº),isc
[45] #failure(device, signal nº),double,nº jams, (device,dig. signal) by
jamming
[46] 0,1,36,10000,0,1,36,1,78,0,2,1,71,0,256,15,0,
[47] 1,1,37,10000,0,1,37,1,78,0,2,1,71,0,256,15,0,
[48] 2,1,39,10000,0,1,39,1,-1,0,2,1,72,0,256,15,0,
[49] ...
[50] 16,1,1,10000,0,1,1,1,-1,0,0,
[51] # ISS
[52] 0,
[53] # ISS,Dir,Isc,time,neg,Analog ?
[54] # MEA
[55] 8,
[56] # MEA * conversion factor = Real Value
[57] # a,b where a=(max-min)/4095 and b=min
[58] 0.46886447,0,
[59] 0.46886447,0,
[60] 0.46886447,0,
[61] ...
[62] 0.03516484,0,
[63] # CON
[64] 0,
[65] # CONT * conversion FACTOR = REAL VALUE
[66] # a,b where a=(max-min)/4095 and b=min
[67] #
[68] #=======================================================================
=
[69] # LOGIC DEVICE Nº 2 (SPAC-538C DIRECTIONAL RELAY LINE PITUAÇU 69kV 02J6)
[70] #=======================================================================
=
[71] # PROCOME address for Procome logic device associated to a full SPA
Device for
[72] # ABB,
[73] # TimeOut RX (ms), Nº ISCs, ISC Max, Nº ISEs, ISE Max, Nº ISSs, ISS Max,
[74] # Nº MEAs, Nº CONs, Local ISC,
[75] 2,500,31,30,0,0,0,0,0,0,0,
[76] # Nº of modules (Control and/or Protection) that make up ABB’s SPA
Device,
[77] 3,
[78] # Identification of SPA Module, Physical address of SPA Module,
[79] SPCS4D1F,111, // PROTECTION OF TWO-PHASE SPCS 4D11 DIRECTIONAL OVER-
VOLTAGE
[80] SPCS3C4,112, // PROTECTION OF NEUTRAL SPCS 3C4 DIRECTIONAL OVER-VOLTAGE
[81] SPCS4D1F,130, // PROTECTION OF TWO-PHASE DIRECTIONAL SPCS 4D12 OVER-
VOLTAGE
[82] ...

M1CPTA2005I
1CPT: Substation Central Unit B-200
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.12.2 Device Description File: MODULSPA.CFG

The individualized description of each of the SPA protection and control modules will be
included in this file, called “modulspa.cfg”, as well as the connection that each of these has
with the equivalent PROCOME configuration. These modules will be referenced from the file
SPABUSMS.CFG in the configuration of each of the logic Procome devices over which the SPA
physical devices are going to be mapped. The file has the following format:
• Data regarding the Number of SPA Protection and Control Modules Described
under this File: [Line 21]

NmodulosSPA ,

• NmodulosSPA: Number of SPA modules.

Ex: 9,

The data for the different SPA protection and control modules is listed below (one after the
other). The following data will be provided for each of the SPA modules:
• General Data for the SPA Module: [Line 27]

Identificacion , N_ISC , N_ ISE , N_ ISS , N_MEA , N_CON , TIPO ,

• Identificacion: Name that identifies the SPA module. Maximum 15 characters.

• N_ISC: Number of digital signals for the SPA module.
• N_ISE: Number of commands for the SPA module.
• N_ISS: Number of output writes for the SPA module.
• N_MEA: Number of analogical measurements for the SPA module.
• N_CON: Number of meters for the SPA module.
• TIPO: Indicates the type of SPA module (0:Control, 1:Protection).

Ex: SPTO6D3,100,17,0,8,0,0,

Note: Information regarding digital inputs, analogical measurements, digital outputs, etc., within a SPA module,
is classified into logic groups called channels.

Note: References to ISCs MEAs, CONs, ISSs and ISEs Procome labels configured in each SPA module within
the file MODULSPA.CFG, will be relative and not absolute references within each of the logic Procome devices
that emulate a physical SPA device. This is so because each SPA module is defined only once within this file
with its set of ISCs, MEAs, CONs, ISSs and ISEs to carry out its mapping of different logic Procome devices
within the Central Unit. Hence, if a SPA physical device has various SPA protection and control modules, the
Procome logic device associated to the same in the configuration file SPABUSMS.CFG, will comprise the same
modules which will have been previously defined under file MODULSPA.CFG, in such a way that the number of
ISCs, MEAs, CONs, ISSs and ISEs for this Procome logic device will be the combination of ISCs, MEAs, CONs,
ISSs and ISEs from each of the SPA modules that have been referenced for the device under file
SPABUSMS.CFG, and the labelled order for this information will be determined by the order in which the SPA
modules have been referenced in the declaration of the Procome logic device.

M1CPTA2005I
B-201 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding BINARY DIGITAL INPUTS for the SPA Module: “I” data
Category within the SPABUS Protocol: [Lines 37-42]
Binary digital inputs for a SPA module are going to be configured by forming
CORRESPONDING binary digital inputs associated to consecutive channels.
CORRESPONDING binary digital inputs are those that have the same code (full value), but
belong to different channels within a SPA module and only apply two statuses (0 or 1). Hence,
CORRESPONDING binary digital inputs are going to be configured by forming consecutive
groups of channels within the SPA module.

NumBinDigInputs ,
Input , CanalIni , CanalFin , IscIni , (*)

(*) This is repeated for each group of CORRESPONDING binary digital inputs to be requested
from the SPA module. There will be as many as indicated under NumBinDigInputs.
• NumBinDigInputs: Nº of CORRESPONDING binary digital input groups for the SPA
Module.
• Input: Binary SPA digital Input Code.
• CanalIni: Initial group Channel.
• CanalFin: Final group channel.
• IscIni: PROCOME label for the initial ISC of the logic device, from which (including the
same) the group’s SPA Binary Digital Inputs are mapped.

Ex: 1, // Nº of CORRESPONDING binary digital input

groups
1,8,17,85,

• Data regarding SPA Module MULTIBIT DIGITAL INPUTS: “I” Data Category
within SPABUS Protocol: [Lines 52-58]
Multibit digital inputs for a SPA module are going to be configured by forming
CORRESPONDING multibit digital inputs associated to consecutive channels. Multibit
CORRESPONDING digital inputs are those that have the same code, but belong to different
channels within the SPA Module, and can apply more than two statuses (0, 1, 2, 3,...). Hence,
CORRESPONDING multibit digital inputs are going to be configured by forming groups of
channels that are consecutive within the SPA Module.

NumMultiDigInputs ,
Input , CanalIni , CanalFin , NumEstados ,

NumIscsEstados , IscIni , Estado , PosIsc , (*)

(**)

(*) This is repeated for each group of CORRESPONDING multibit digital inputs that are
going to be requested from the SPA module. There will be as many as indicated under
NumMultiDigInputs.
(**) This is repeated for each status that can be applied by the digital multibit inputs. There
will be as many as indicated under NumIscsEstado.

M1CPTA2005I
1CPT: Substation Central Unit B-202
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• NumMultiDigInputs: Nº of CORRESPONDING multibit digital inputs in the SPA Module.

• Input: Multibit digital Input Code.
• CanalIni: Initial group channel.
• CanalFin: Final group channel.
• NumEstados: Number of Statuses for the Multibit Digital Input.
• NumIscsEstados: Number of ISCs used by the Multibit Digital Input Status (one ISC can
be associated to various statuses for a multibit digital input).
• IscIni: PROCOME label for the initial ISC logic device, from which (including the same),
the SPA Multibit Digital Inputs for the group are mapped.
• Estado: Status of the Multibit Digital Input.
• PosIsc: Relative position (as regards the ISC IscIni) of the ISC associated to the Multibit
Digital Input Status.

Ej: 1, // Nº of CORRESPONDING multibit digital input

groups
1,1,7,4,3,36,0,3,1,2,2,1,3,3,

• Data regarding SPA Module BINARY DIGITAL OUTPUTS : 'O' Data Category
within the SPABUS Protocol: [Lines 65-67]
Binary digital outputs for a SPA module are going to be configured by forming adjoining binary
digital output groups within the same channel. Binary digital outputs only apply two statuses (0
or 1).

NumBinDigOutputs ,
Canal , OutputIni , OutputFin , IscIni , (*)

(*) This is repeated for each group of binary digital outputs that is going to be requested from
the SPA module. There will be as many as indicated under NumBinDigOutputs.
• NumBinDigOutputs: Nº of binary digital outputs within the SPA Module.
• Canal: Nº of group channel.
• OutputIni: Code for the Initial Binary Digital Output for the group.
• OutputFin: Code for the Final Binary Digital Output for the group.
• IscIni: Initial ISC PROCOME label for the logic device, from which (including the same)
the SPA Binary Digital Outputs are mapped for the group.

Ex: 1, // Nº of binary digital output groups

0,1,8,0,

M1CPTA2005I
B-203 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding MULTIBIT DIGITAL OUTPUTS for the SPA Module: ‘O’ Data
Category within the SPABUS Protocol: [Lines 77-83]
Multibit digital outputs for a SPA Module will be configured by forming CORRESPONDING
multibit digital output groups associated to consecutive channels. CORRESPONDING multibit
digital outputs are those that have the same code, but belong to different channels within the
SPA Module, and can apply more than two statuses (0,1,2,3,...). Hence, CORRESPONDING
multibit digital outputs are going to be configured forming groups of channels that are
consecutive within the SPA Module.

NumMultiDigOutputs ,
Output , CanalIni , CanalFin , NumEstados ,

NumIscsEstados , IscIni , Estado , PosIsc , (*)

(**)

(*) This is repeated for each group of CORRESPONDING multibit digital outputs that are
going to be requested from the SPA module. There will be as many as indicated under
NumMultiDigOutputs.
(**) This is repeated for each of the statuses that can be applied by the multibit digital outputs.
There will be as many as indicated under NumIscsEstados.

• NumMultiDigOutputs: Nº of CORRESPONDING multibit digital outputs in the SPA

Module.
• Output: Multibit digital output code.
• CanalIni: Initial group channel.
• CanalFin: Final group channel.
• NumEstados: Number of Statuses for the Multibit Digital Output.
• NumIscsEstados: Number of ISCs used by the N Digital Multibit Output (one ISC can be
associated to various statuses for a digital multibit output).
• IscIni: PROCOME label for the initial ISC logic device, based on which (including the
same) the SPA Multibit Digital Outputs for the group will be mapped.
• Estado: Multibit Digital Output Status.
• PosIsc: Relative position (as regards the ISC IscIni) of the ISC associated to the Status of
the Multibit Digital Output.

Ex: 1, // Nº of CORRESPONDING multibit digital output

groups
10,0,0,5,5,5,1,1,2,6,3,11,4,16,5,21,

M1CPTA2005I
1CPT: Substation Central Unit B-204
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding DIGITAL INTERNAL VARIABLES for the SPA Module: ‘V’ Data
Category within the SPABUS Protocol: [Lines 90-93]
Digital internal variables for a SPA Module will be configured by forming groups of adjacent
digital internal variables within the same channel. Digital internal variables only apply two
statuses (0 or 1).

NumIntDigVars ,
Canal , VarIni , VarFin , IscIni , (*)

(*) This is repeated for each group of digital internal variables to be requested from the SPA
module. There will be as many as indicated under NumIntDigVars.
• NumIntDigVars: Nº of digital internal variable groups within the SPA Module.
• Canal: Nº of the group channel.
• VarIni: Code for the group’s Initial Digital Internal Variable.
• VarFin: Code for the group’s Final Digital Internal Variable.
• IscIni: Initial logic device ISC PROCOME label, based on which (including the same) the
group’s SPA Digital Internal Variables are mapped.

Ex: 1, // Nº of digital internal variable groups

0,6,6,0,

• Data regarding SPA Module’s MULTIBIT INTERNAL VARIABLES: ‘V’ Data

Category within the SPABUS Protocol: [Lines 52-58]
The multibit internal variables for a SPA module are going to be configured by forming
CORRESPONDING multibit internal variable groups associated to consecutive channels. The
CORRESPONDING multibit internal variables are those that have the same code but belong to
different channels within the SPA Module and can apply more than two statuses (0,1,2,3,...).
Hence, CORRESPONDING multibit internal variables are going to be configured by forming
groups of consecutive channels within the SPA Module.

NumMultiDigVarInts ,
VarInt , CanalIni , CanalFin , NumEstados ,

NumIscsEstados , IscIni , Estado , PosIsc , (*)

(**)

(*) This is repeated for each group of CORRESPONDING multibit digital inputs to be
requested from the SPA module. There will be as many as indicated under NumMultiDigInputs.
(**) This is repeated for each status that can be applied to the multibit digital inputs. There will
be as many as indicated under NumIscsEstados.

• NumMultiDigVarInts: Nº of CORRESPONDING multibit internal variable groups in the

SPA Module.
• VarInt: Code for the multibit Internal Variable.
• CanalIni: Initial group channel.
• CanalFin: Final group channel.
• NumEstados: Number of Multibit Internal Variable Statuses.
• NumIscsEstados: Number of ISCs used by the N Multibit Internal Variable Status (one
ISC can be associated to various statuses in a multibit internal variable).
• IscIni: Initial ISC PROCOME label for the logic device, based on which (including the
same) the group’s SPA Multibit Internal Variables are mapped.

M1CPTA2005I
B-205 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Estado: Status of the Multibit Internal Variable.

• PosIsc: Relative position (as regard ISC IscIni) of the ISC associated to the Multibit
Internal Variable Status.

Ex: 1, // Nº of CORRESPONDING Multibit Internal

Variable groups
1, 1,7, 4, 3, 36, 0,3, 1,2, 2,1, 3,3,

• Data regarding SPA Module’s BINARY DIGITAL SETTINGS: ‘S’ Data Category
within SPABUS Protocol: [Lines 100-103]
The SPA Module’s binary digital settings are going to be configured by forming adjacent digital
adjustment groups within the same channel. Binary digital settings only apply two statuses (0 or
1).

NumBinDigAjs ,
Canal , AjsIni , AjsFin , IscIni , (*)

(*) It is repeated for each group of binary digital settings that are going to be requested from
the SPA module. There will be as many as indicated under NumBinDigAjs.
• NumBinDigAjs: Nº of binary digital adjustment groups within the SPA Module.
• Canal: Nº of group channel.
• AjsIni: Code for the group’s Initial Binary Digital Adjustment.
• AjsFin: Code for the group’s Final Binary Digital Adjustment.
• IscIni: PROCOME Label for the initial ISC of the logic device, based on which (including
the same) the group’s SPA Binary Digital Settings are mapped.

Ex: 2, // Nº of binary digital adjustment groups

0,5,6,97,
0,78,78,99,

• NumIscsEstados: Number of ISCs used by the N Status of the Multibit Internal Variable
(one ISC can be associated to various status in a multibit internal variable).
• IscIni: PROCOME label for the logic device’s initial ISC, based on which (including the
same) the group’s SPA Multibit Internal Variables are mapped.
• Estado: Status of the Multibit Internal Variable.
• PosIsc: Relative position (as regards ISC IscIni) of the ISC associated to the Multibit
Internal Variable Status.

Ex: 1, // Nº of CORRESPONDING Multibit Internal

Variable groups
1, 1,7, 4, 3, 36, 0,3, 1,2, 2,1, 3,3,

M1CPTA2005I
1CPT: Substation Central Unit B-206
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding the SPA Module’s ANALOGICAL INPUTS: Data Category ‘I’
within the SPABUS Protocol: [Lines 109-112]
Analogical inputs for a SPA Module are going to be configured by forming adjacent analogical
input groups within the same channel.

NumAnalogInputs ,
Canal , InputIni , InputFin , MeaIni , (*)

(*) This is repeated for each analogical input group that is going to be requested from the
SPA module. There will be as many as indicated under NumAnalogInputs.
• NumAnalogInputs: Nº of analogical input groups within the SPA Module.
• Canal: Nº of group’s channel.
• InputIni: Group’s Initial Analogical Input Code.
• InputFin: Group’s Final Analogical Input Code.
• MeaIni: PROCOME label for the initial MEA’s logic device, based on which (including the
same), the group’s Analogical Inputs are mapped.

Ej: 1, // Nº of analogical input groups

0,11,16,0,

• Data regarding the SPA Module’s ANALOGICAL INTERNAL VARIABLES: ‘V’

Data Category within the SPABUS Protocol: [Lines 119-122]
The SPA module’s analogical internal values will be configured by forming groups of adjacent
analogical internal variables within the same channel.

NumAnalogIntVars ,
Canal , VarIni , VarFin , MeaIni , (*)

(*) This is repeated for each group of analogical internal variables that is going to be
requested from the SPA module. There will be as many as indicated under
NumAnalogIntVars.
• NumAnalogIntVars: Nº of analogical internal variable groups within the SPA Module.
• Canal: Group’s channel Nº.
• VarIni: Group’s Initial Analogical Internal Variable Code.
• VarFin: Group’s Final Analogical Internal Variable Code.
• MeaIni: PROCOME label for the initial MEA’s logic device, based on which (including the
same), the group’s SPA Analogical Internal Variables are mapped.

Ex: 1, // Nº of analogical internal variable groups

0,3,4,6,

M1CPTA2005I
B-207 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding the SPA Module’s INTERNAL METERS: ‘V’ Data Category
within SPABUS Protocol: [Line 128]
SPA Module’s Internal meters are going to be configured by forming adjacent internal meter
groups within the same channel

NumIntContadores ,
Canal , ConIntIni , ConIntFin , ConIni , (*)

(*) This is repeated for each group of internal meters to be requested from the SPA module.
There will be as many as indicated under NumIntContadores.
• NumIntContadores: Nº of internal meter groups within the SPA Module.
• Canal: Group channel Nº.
• ConIntIni: Group’s Initial Internal Meter Code.
• ConIntFin: Group’s Final Internal Meter Code.
• ConIni: PROCOME label for the initial CON of the logic device, based on which (including
the same), the group’s Internal SPA Meters are mapped.

Ex: 0, // Nº of internal meter groups

• Data regarding the SPA Module’s EXTERNAL METERS: ‘I’ Data Category
within SPABUS Protocol: [Line 136]
SPA Module's external meters are going to be configured by forming adjacent external meter
groups within the same channel.

NumExtContadores ,
Canal , ConExtIni , ConExtFin , ConIni , (*)

(*) This is repeated for each group of external meters to be requested from the SPA module.
There will be as many as indicated under NumExtContadores.
• NumExtContadores: Nº of external meter groups within the SPA Module.
• Canal: Group’s channel Nº.
• ConExtIni: Group’s Initial External Meter Code.
• ConExtFin: Group’s Final External Meter Code.
• ConIni: PROCOME label for the initial CON of the logic device, based on which (including
the same), the group’s External SPA Meters are mapped

Ex: 0, // Nº of external meter groups

M1CPTA2005I
1CPT: Substation Central Unit B-208
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding METERS AND BCD MEASUREMENTS CALCULATED by the

CPX/CPP/CPT based on the Data provided by the SPA Module
This does not correspond with any data Category within the SPABUS protocol as this is
calculated internally by the Central Unit: [lines 154-163]

The meters that are calculated are not generated by a SPA Module, but, rather, are calculated
by the Central Unit based on a group of meters generated by a SPA Module. These type of
calculated meters are used to obtain total Energy values based on GWh, MWh and KWh.

Calculated BCD measurements are measurements that are calculated by the Central Unit
based on a group of bits that make up the digits for each BCD measurement handled by the
SPA module for the device. The value of a BCD measurement will be available from the Central
Unit through two channels:

- Via Refresh: through direct reading of SPA data associated to the bits that make up the
BCD measurement digits.
- Via Changes: through the collection of the activation and deactivation events associated
to each of the bits.

These BCD measurements from the SPA module are finally converted to accounts in MEA’s
Procome, associated to the logic PROCOME device that emulates ABB’s physical device.

NumCalcContadores , NumCalcMedBCD ,
ConGiga , ConMega , ConKilo , Contador , (*)

(*) This is repeated for each meter to be calculated within the Central Unit based on partial
meters provided by the SPA Module. There will be as many as indicated under
NumCalcContadores.

• NumCalcContadores: Nº of meters calculated by the UCS.

• NumCalcMedBCD: Nº of BCD measurements calculated by the UCS.
• ConGiga: PROCOME label for the CON associated to the SPA Meter for GWh or GVarh.
• ConMega: PROCOME label for the CON associated to the SPA Meter for MWh or
MVarh.
• ConKilo: PROCOME label for the CON associated to the SPA Meter for KWh or KVarh.
• Contador: PROCOME label for the CON associated to the Calculated Meter.

Mea , CategDatoSPA , NumDigitosBCD , (*)

Canal_Est_Bit , Dato_Est_Bit , (**)
Canal_Bit_ON , Evento_Bit_ON , Canal_Bit_OFF , Evento_Bit_OFF , (**)

(*) This is repeated for each BCD Measurement to be calculated within the Central Unit based
on the bits provided by the SPA Module. There will be as many as indicated under
NumCalcMedBCD.
(**) This is repeated for each of the bits that make up the BCD measurement to be calculated
within the Central Unit. There will be as many as indicated by the expression (4 *
NumDigitosBCD).

M1CPTA2005I
B-209 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Mea: PROCOME label for the MEA associated to the calculated BCD SPA measurement.
• CategDatoSPA: Category of SPA data associated to the bits that make up the BCD
measurement (I: Inputs, O: Outputs).
• NumDigitosBCD: Nº of BCD digits that make up the SPA measurement (each BCD digit
has 4 bits).
• Canal_Est_Bit: Channel Nº for SPA data that stores the current status of the bit (Bit LSB ,
…, Bit MSB).
• Dato_Est_Bit: Code for the SPA data that stores the current status of the bit (Bit LSB , …,
Bit MSB).
• Canal_Bit_ON: Event channel Nº that sets the bit to 1 (Bit LSB , …, Bit MSB).
• Evento_Bit_ON: Event Code that sets the bit to 1 (Bit LSB , …, Bit MSB).
• Canal_Bit_OFF: Event Channel Nº that sets the bit to 0 (Bit LSB , …, Bit MSB).
• Evento_Bit_OFF: Event Code that sets the bit to 0 (Bit LSB , …, Bit MSB).

Ex: 0,1, // Nº of calculated meters, Nº of calculated BCD

measurements
0,O,2,
5,861,5,862,5,863,5,864,5,866,5,867,5,868,5,869,
24,E51,24,E50,24,E49,24,E48,24,E47,24,E46,24,E45,24,E44,
24,E43,24,E42,24,E41,24,E40,24,E39,24,E38,24,E37,24,E36,

• Data regarding SPA Module’s COMMANDS FOR OBJECTS (Switches, Circuit-

Breakers, etc.). ‘O’ Data Category within the SPABUS Protocol: [Lines 167-
173]

NumMandos ,
Mando , Canal , Dco , Ise , (*)

(*) This is repeated for each command from the SPA module. There will be as many as
indicated under NumMandos.
• NumMandos: Nº of commands in the SPA Module.
• Mando: Command Code for the SPA Device.
• Canal: Nº of logic channel, within the SPA module, that the command is associated to.
• Dco: Final Status for the Output governed by the command within the SPA module.
• Ise: PROCOME label for the ISE associated to the SPA Command.

Ex: 14, // Nº of commands in the SPA Module

1,1,0,0,
1,1,1,1,
1,2,0,2,
...
1,7,1,13,

M1CPTA2005I
1CPT: Substation Central Unit B-210
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding SPA Module COMMANDS FOR MODIFICATION OF SETTINGS:

‘S’ Data Category within the SPABUS Protocol: [Lines 177-181]

NumEscrAjs ,
Mando , Canal , Dco , Ise , (*)

(*) This is repeated for each command from the SPA module. There will be as many as
indicated under NumEscrAjs.
• NumEscrAjs: Nº of commands from the SPA Module.
• Mando: Command Code in SPA device.
• Canal: Logic channel Nº, within the SPA module, that the command is linked to.
• Dco: Final status of Adjustment, governed by the command within the SPA module.
• Ise: PROCOME label for the ISE associated to the SPA Command.

Ex: 3, // Nº of commands in SPA Module

78,0,1,14,
78,0,0,15,
79,0,1,16,

• Data on SPA Module COMMANDS FOR WRITING INTERNAL MULTIBIT

VARIABLES: ‘V’ Data Category within the SPABUS Protocol: [Lines 182-186]

NumEscrVarIntMulti ,
Mando , Canal , Dco , Ise , (*)

(*) This is repeated for each command from the SPA module. There will be as many as
indicated under NumEscrAjs.
• NumEscrVarIntMulti: Nº of commands in the SPA Module.
• Mando: Command Code in the SPA Device.
• Canal: Logic channel Nº, within the SPA module, that the command is linked to.
• Dco: Final status of the Adjustment governed by the command within the SPA module.
• Ise: PROCOME label for the ISE linked to the SPA Command.

Ex: 3, // Nº of commands in the SPA Module

150,0,6,17,
151,0,7,18,
152,0,6,19,

M1CPTA2005I
B-211 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding the Configuration of EVENTS required for Collection from the
SPA Module: Data Category ‘E’ within the SPABUS Protocol: [Lines 191-198]
The events stemming from a SPA Module will be configured one by one, in such a way that the
generation of each event can be enabled or disabled by means of an event mask.

Generally speaking, and within the Central Unit, a SPA event will entail the
activation/deactivation of a main Procome ISC associated to the Event, and, at the same time,
the activation/deactivation of a series of secondary Procome ISCs related to the former.

NumEventos ,
Canal , Evento , Mascara , HabilEvento , Isc , Cambio ,

NumCambiosSec , IscSec , CambioIscSec , (*)

(**)

(*) This is repeated for each Event from the SPA module. There will be as many as indicated
under NumEventos.
(**) This is repeated for each of the secondary Procome ISCs related to the SPA Event. There
will be as many as indicated under NumCambiosSec.

• NumEventos: Nº of Events in the SPA Module that generate changes in ISC's Procome.
• Canal: Nº of the logic channel, within the SPA module, that the Event is linked to.
• Evento: SPA Event Code.
• Mascara: Mask for enabling/disabling the generation of the SPA Event.
• HabilEvento: Value that enables the generation of the SPA Event.
• Isc: PROCOME label for the main ISC linked to the SPA Event.
• Cambio: Change generated by the Event on the linked Procome ISC.
• NumCambiosSec: Nº of secondary Procome ISCs linked to the SPA Event.
• IscSec: PROCOME label for another ISC linked to the SPA Event.
• CambioIscSec: Change provoked by the SPA Event on said Procome ISC.

Ex: 82, // Nº of Events in SPA Module

0,1,155,1,0,0,0,
0,2,155,2,0,1,0,
0,5,155,16,97,0,0,
...
7,10,155,512,84,1,1,84,0,

M1CPTA2005I
1CPT: Substation Central Unit B-212
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data regarding SPA Module EVENT MASKS: ‘V’ Data Category within the
SPABUS Protocol: [Lines 203-209]
The event masks will be configured one by one in a SPA module, and will enable the SPABUS
master emulator to enable/disable, via serial communication, the generation of an associated
event within the SPA module.

NumMascaras ,
Canal , Mascara , (*)

(*) This is repeated for each event mask in the SPA module. There will be as many as
indicated under NumMascaras.

• NumMascaras: Nº of event masks in the SPA Module.

• Canal: Logic channel Nº, within the SPA module, associated to the event mask.
• Mascara: Mask associated to the SPA Event.

Ex: 21, // Nº of event masks in the SPA Module

0,155,
0,156,
0,157,
...
17,155,

• Data required for Modification of Settings on the SPA Module’s EEPROM

Memory: ‘V’ Data Category within the SPABUS Protocol: [Line 213]
This section defines, on the one hand, the code associated to the updating Operation of the
SPA module’s EEPROM memory, and, on the other hand, the Password will be configured in
order to update the EEPROM memory in the SPA module.

StoreEEPROM , PasswordSPA ,

• StoreEEPROM: Updating operation of the SPA module’s EEPROM memory.

• PasswordSPA: Password to enable updating of the SPA module’s EEPROM memory (0:
Password not required).

Ex: 151,0, // Access to EEPROM, Password (0:No Password)

M1CPTA2005I
B-213 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file remains as follows:

[1] #/***********************************************************************
*******/
[2] # The different types of SPA modules are configured in this file (Control
and/or
[3] # Protection) that make up ABB's SPA physical Devices.
[4] # All its digital signals, commands, measurements, will be specified for
each module,
[5] # and meters.
[6] #
[7] # "SPTO6D3" SPA Module: CONTROL SPTO 6D3
[8] # "SPTO1D2" SPA Module: CONTROL SPTO 1D2
[9] # "SPCJ4D29" SPA Module: OVERCURRENT PROTECTION SPCJ 4D29
[10] # "SPCU3C14" SPA Module: OVER AND UNDER VOLTAGE PROTECTION SPCU 3C14
[11] # "SPCU1C6" SPA Module: RESIDUAL VOLTAGE PROTECTION SPCU 1C6
[12] # "SPCS3C4" SPA Module: DIRECTIONAL OVERCURRENT GROUND PROTECTION
[13] # SPCS 3C4
[14] # "SPCS4D1F" SPA Module: DIRECTIONAL OVERCURRENT BIPHASIC PROTECTION
[15] # SPCS 4D11
[16] # "SPCD3D53" SPA Module: TRIPHASIC DIFFERENTIAL PROTECTION
[17] # "SACO16D1" SPA Module: ANNOUNCER OR ALARM
[18] #
[19] # -----------------------------------------------------------------------
--------
[20] # Number of SPA modules (Control and/or Protection) described in this
file
[21] 9,
[22] #
[23] # -----------------------------------------------------------------------
--------
[24] # SPA Module: CONTROL SPTO 6D3
[25] # SPA Module Identification , Nº ISCs, Nº ISEs, Nº ISSs, Nº MEAs, Nº
CONs,
[26] # Type(Control=0, Prot=1)
[27] SPTO6D3,100,17,0,8,0,0,
[28] # -----------------------------------------------------------------------
--------
[29] # BINARY DIGITAL INPUTS (Data Category 'I')
[30] # Binary digital inputs for a SPA Module will be configured by forming
[31] # groups of CORRESPONDING binary digital inputs associated to consecutive
[32] # channels.
[33] # CORRESPONDING binary digital inputs are those that have the same code,
[34] # but belong to different channels within the SPA Module, and only apply
two
[35] # status (0 or 1).
[36] # Nº of CORRESPONDING binary digital inputs in the SPA Module
[37] 1,
[38] # CORRESPONDING binary digital inputs will be configured by forming
groups
[39] # of consecutive channels in the SPA Module.
[40] # Code for binary digital Input, Initial Channel, Final Channel, initial
ISC
[41] # associated to Input group
[42] 1,8,17,85,
[43] # -----------------------------------------------------------------------
--------
[44] # MULTIBIT DIGITAL INPUTS (Data category 'I')

M1CPTA2005I
1CPT: Substation Central Unit B-214
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[45] # SPA Module Multibit digital inputs will be configured by forming

[46] # CORRESPONDING groups of digital multibit inputs associated to
consecutive
[47] # channels.
[48] # CORRESPONDING multibit digital inputs are those that have the same
code,
[49] # but belong to different channels within the SPA Module, and can apply
more
[50] # than two statuses (0,1,2,3,...).
[51] # Nº of CORRESPONDING multibit digital input groups in the SPA Module
[52] 1,
[53] # CORRESPONDING multibit digital inputs are going to be configured by
forming groups
[54] # of channels that are consecutive in the SPA Module.
[55] # Multibit digital Input Code, Initial Channel, Final Channel, Nº of
Values
[56] # for the Input, Nº of ISCs used by the N values, Initial ISC, Value 1,
Pos.
[57] # ISC, ..., Value n, Pos. ISC
[58] 1,1,7,4,3,36,0,3,1,2,2,1,3,3,
[59] # ----------------------------------------------------------------------
---------
[60] # BINARY DIGITAL OUTPUTS ('O' data category)
[61] # SPA Module binary digital outputs will be configured by forming
[62] # groups of adjacent binary digital outputs within the same channel.
[63] # Binary digital outputs only apply two statuses (0 or 1).
[64] # Nº of binary digital outputs in the SPA Module
[65] 1,
[66] # Channel, Initial Output, Final Output, Initial ISC associated to the
group of outputs
[67] 0,1,8,0,
[68] # ----------------------------------------------------------------------
---------
[69] # MULTIBIT DIGITAL OUTPUTS ('O' data category)
[70] # Multibit digital outputs for a SPA Module are going to be configured
by forming
[71] # groups of CORRESPONDING multibit digital outputs associated to
consecutive
[72] # channels.
[73] # CORRESPONDING multibit digital outputs are those that have the same
code,
[74] # but belong to different channels within the SPA Module, and can apply
more than
[75] # two statuses (0,1,2,3,...).
[76] # Nº of CORRESPONDING multibit digital output groups in the SPA Module
[77] 1,
[78] # CORRESPONDING multibit digital outputs are going to be configured by
forming groups
[79] # of consecutive channels in the SPA Module.
[80] # Code for multibit digital Output, Initial Channel, Final Channel, Nº
of Values for
[81] # the Output, Nº of ISCs used by N values, Initial ISC, Value 1, Pos.
ISC,
[82] # ..., Value n, ISC Pos.
[83] 10,0,0,5,5,5,1,1,2,6,3,11,4,16,5,21,
[84] # ----------------------------------------------------------------------
---------
[85] # DIGITAL INTERNAL VARIABLES ('V' data category)
[86] # Digital internal variables for a SPA Module will be configured by
forming

M1CPTA2005I
B-215 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[87] # groups of adjacent digital internal variables within the same channel.
[88] # Digital internal variables only apply two statuses (0 or 1).
[89] # Nº of digital internal variable groups in the SPA Module
[90] 1,
[91] # Channel, Initial Internal Variable, Final Internal Variable, initial
ISC associated to
[92] # the group of Variables
[93] 0,6,6,0,
[94] # ----------------------------------------------------------------------
---------
[95] # MULTIBIT DIGITAL INTERNAL VARIABLES ('V' data category)
[96] # Multibit internal variables for a SPA Module will be configured by
forming
[97] # groups of CORRESPONDING multibit internal variables associated to
consecutive
[98] # channels.
[99] # CORRESPONDING multibit internal variables have the same code,
[100] # but belong to different channels within the SPA Module, and can apply
more
[101] # than two statuses (0,1,2,3,...)
[102] 1,
[103] 1, 1,7, 4, 3, 36, 0,3, 1,2, 2,1, 3,3,
[104] # ----------------------------------------------------------------------
--------
[105] # DIGITAL SETTINGS ('S' data category)
[106] # Digital settings for a SPA Module will be configured by forming
[107] # groups of adjacent digital settings within the same channel.
[108] # Digital settings only apply two statuses (0 or 1).
[109] # Nº of digital settings groups in the SPA Module
[110] 2,
[111] # Channel, Initial Setting, Final Setting, initial ISC associated to the
group of Settings
[112] 0,5,6,97,
[113] 0,78,78,99,
[114] # ----------------------------------------------------------------------
--------
[115] # ANALOGICAL INPUTS ('I' data category)
[116] # Analogical inputs for a SPA Module will be configured by forming
[117] # groups of adjacent analogical inputs within a same channel.
[118] # Nº of analogical input groups in the SPA Module
[119] 1,
[120] # Channel, Initial Analogical Input, Final Analogical Input, initial MEA
[121] # associated to the Input group
[122] 0,11,16,0,
[123] # ----------------------------------------------------------------------
--------
[124] # ANALOGICAL INTERNAL VARIABLES ('V' data category)
[125] # Analogical internal variables for a SPA Module will be configured by
[126] # forming groups of adjacent analogical internal variables within the
same
[127] # channel.
[128] # Nº of analogical internal variables for the SPA Module
[129] 1,
[130] # Channel, Initial Internal Variable, Final Internal Variable,
associated initial MEA
[131] # for the group of Variables
[132] 0,3,4,6,
[133] # ----------------------------------------------------------------------
--------

M1CPTA2005I
1CPT: Substation Central Unit B-216
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[134] # INTERNAL METERS ('V' data category)

[135] # Internal meters for a SPA Module will be configured by forming
[136] # groups of adjacent internal meters within the same channel.
[137] # Nº of internal meter groups in the SPA Module
[138] 0,
[139] # Channel, Initial Internal Meter, Final Internal Meter, initial CON
associated
[140] # to the group of Meters
[141] # ----------------------------------------------------------------------
--------
[142] # EXTERNAL METERS ('I' data category)
[143] # External meters for a SPA Module will be configured by forming
[144] # groups of adjacent external meters within the same channel.
[145] # Nº of external meter groups in the SPA Module
[146] 0,
[147] # Channel, Initial External Meter, Final External Meter, initial CON
associated
[148] # to the group of Meters
[149] # ----------------------------------------------------------------------
--------
[150] # METERS AND BCD MEASUREMENTS CALCULATED BY THE UCS (Data category:
None)
[151] # Calculated meters are meters that are not generated by a SPA Module,
[152] # but are calculated by the UCS based on a group of meters that
[153] # are generated by a SPA Module. These type of calculated meters are
[154] # used for obtaining total Energy values based on GWh, MWh
[155] # and KWh fractions.
[156] # Calculated BCD measurements are measurements calculated by the UCS
based on a
[157] # group of bits which make up the BCD digits from each BCD measurement
[158] # handled by the SPA Module, whose value reaches the UCS through the
[159] # activation and deactivation events associated to each of the bits.
These
[160] # BCD measurements from the SPA Module are finally converted into
accounts in MEA's
[161] # Procome.
[162] # Nº of meters calculated by the UCS, Nº of BCD measurements calculated
by the
[163] # UCS
[164] 0,1,
[165] # SPA meter for GWh or GVarh, SPA meter for MWh or MVarh, SPA meter for
KWh
[166] # or KVarh, CON associated to group of Meters
[167] # MEA associated to the BCD SPA measurement, Category_Med_BCD_SPA, Nº of
BCD digits,
[168] # Channel, DatoSPA BIT_0, ...
[169] # Channel, BIT_0 Activation Event, Channel, BIT_0 Deactivation Event,
...
[170] # Measurement of Percentage of distance to the Fault (Locator)
[171] 0,O,2,
[172] 5,861,5,862,5,863,5,864,5,866,5,867,5,868,5,869,
[173] 24,E51,24,E50,24,E49,24,E48,24,E47,24,E46,24,E45,24,E44,24,E43,24,E42,24
,E41,24,E40,24,E39,24,E38,24,E37,24,E36,
[174] # ----------------------------------------------------------------------
--------
[175] # COMMANDS FOR OBJECTS ('O' data category)
[176] # Nº of commands in the SPA Module
[177] 14,
[178] # Command Code, Channel, DCO, ISE associated to the Command
[179] 1,1,0,0,

M1CPTA2005I
B-217 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[180] 1,1,1,1,
[181] 1,2,0,2,
[182] ...
[183] 1,7,1,13,
[184] # ----------------------------------------------------------------------
--------
[185] # COMMANDS FOR MODIFICATION OF SETTINGS ('S' data category)
[186] # Nº of commands in the SPA Module
[187] 3,
[188] # Code for Command, Channel, DCO, ISE associated to the Command
[189] 78,0,1,14,
[190] 78,0,0,15,
[191] 79,0,1,16,
[192] # ----------------------------------------------------------------------
--------
[193] # COMMANDS FOR WRITING INTERNAL VARIABLES ('V' data category)
[194] # Nº of commands in the SPA Module
[195] 3,
[196] # Command Code, Channel, DCO, ISE associated to the Command
[197] 150,0,6,17,
[198] 151,0,7,18,
[199] 152,0,6,19,
[200] # ----------------------------------------------------------------------
--------
[201] # EVENTS ('E' data category)
[202] # Events for a SPA Module will be configured one by one, in such a way
that
[203] # the generation of each event may be enabled or disabled by means of an
[204] # event mask.
[205] # As a general principle, and within the Central Unit, an event will
entail the
[206] # activation of an ISC associated to the Event, and the deactivation of
a series of
[207] # ISCs related to the former.
[208] # Nº of Events in the SPA Module
[209] 82,
[210] # Channel, Event, Mask, Mask Value, ISC, Change, Nº of ISCs, ISC1,
Change 1,
[211] # ..., ISCn, Change n
[212] 0,1,155,1,0,0,0,
[213] 0,2,155,2,0,1,0,
[214] 0,5,155,16,97,0,0,
[215] ...
[216] 7,10,155,512,84,1,1,84,0,
[217] # ----------------------------------------------------------------------
--------
[218] # EVENT MASKS ('V' data category)
[219] # Event masks in a SPA Module will be configured one by one.
[220] # Nº of event masks in the SPA Module
[221] 21,
[222] # Channel, Mask
[223] 0,155,
[224] 0,156,
[225] 0,157,
[226] ...
[227] 17,155,
[228] # ----------------------------------------------------------------------
--------

M1CPTA2005I
1CPT: Substation Central Unit B-218
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[229] # Information required to undertake changes in the configuration of a

SPA Device
[230] # Access to EEPROM, Password (0:No Password)
[231] 151,0,
[232] #
[233] # ----------------------------------------------------------------------
--------
[234] # SPA Module: CONTROL SPTO 1D2
[235] # Identification of SPA Module, Nº ISCs, Nº ISEs, Nº ISSs, Nº MEAs, Nº
CONs,
[236] # Type(Control=0, Prot=1)
[237] SPTO1D2,35,6,0,5,0,0,
[238] ...

M1CPTA2005I
B-219 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.13 PROCOSLV Protocol: PROCOSLV.CFG

This file, “procoslv.cfg” configures remote control data: general data, commands, signals,
measurements and counters. Each remote control command, signal, measurement and counter
will be associated a CPX/CPT command, signal, measurement or counter. File formal is as
follows:
• Data to configure Remote Control Communications Failure Signal
They are configured as explained in section A.1:

Ex: 1,
0,1,0,0,0,0,

• Data on RTU Emulation

DirRTUEmul , NivelTraza , TimeCDoff , TimeRTSon , TimeRTSoff , ..

.. TipoComs , TimeErrComs , HabSincro ,

• DirRTUEmul: Base address of the RTU to emulate.

• NivelTraza: Trace monitoring level (0,1,2, or 3)..
• TimeCDoff: Time elapsed from the moment the last frame character is received to the
moment when RTS activates
• TimeRTSon: Time that RTS remains set to ON before transmitting (in msec.).
• TimeRTSoff: Time that RTS remains set to OFF after the transmission (in msec.).
• TipoComs: States the type of communication with master. Possible values are 0 (serial
communications) and 1 (TCP/IP communications).
• TimeErrComs: Time (in seconds) the CPX/CPP/CPT remains without receiving requests
from the master to issue a communications error. If it is set to 0, it means
communications failures are not managed and CPX/CPP/CPT communications errors will
never be stated.
• HabSincro: Indicates whether the synchronisation function from the master will be
enabled (1) or not (0). Default value is (0), namely, synchronisation from the master is not
allowed.

Ex: 13,8,0,33,0,0,60,0,

M1CPTA2005I
1CPT: Substation Central Unit B-220
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data to configure Port Communications:

Then serial port or TCP/IP port data are to be configured as a function of the parameter
TipoComs.
If TipoComs is set to 0 (SERIAL communications)

Puerto , Veloc , TipoPar , NumBits , NumStop , TamañoFIFO ,

• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4.
COM3 and COM4 are only valid for CPX. Virtual Ports (VXXX), associated to the
Terminal Server, declared in configuration file TSComs.cfg (V201,V202,V203,…), may
also be defined here.
• Veloc: Baud rate. It can take the values 600, 1200, 2400, 4800, 9600 and 19200 baud.
• TipoPar: Parity type. It can take the values ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd); ‘E’, ‘e’, ‘p’,
‘P’ (even).NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. Possible values are 1 and 2.
• TamañoFIFO: Size of FIFO in bytes. Possible values are 1, 4, 8, 14 or 0 (FIFO not used).
Default value is 1.

Ex: COM1,19200,p,8,1,1,

If TipoComs is 1 (TCP/IP communications)

PuertoTCP , DirIP NumLAN

• PuertoTCP: TCP/IP communications port.

• DirIP: IP address of PROCOSLV slave. In case no address is configured, the central IP
will be taken.
• NumLAN: Number of the LAN to be used for TCP/IP communications. LAN addresses
are defined in file “TCP.CFG” and, for example, in case of CPT equipment that have two,
it will be 1 or 2. Default value is 1, associated to LAN1.

Ex: 123,128.127.170,171,1,

• Data to configure Remote Control Digital Signals

Each remote control digital signal is associated a CPX/CPP/CPT signal:

NumSeñales ,
DirEq , EtiqISC , (*)

(*) It repeats for each remote control signal. It will be as many as shown in NumSeñales.

• NumSeñales: Number of signals defined in the remote control.

• DirEq: Address of the device the CPX/CPP/CPT signal belongs to.
• EtiqISC: PROCOME label of the CPX/CPP/CPT digital signal.

Ex: 40, // Num. signals

6,2,
6,3,
6,4,
...
257,4,

M1CPTA2005I
B-221 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data to configure Remote Control Measurements

Each remote control measurement is associated a CPX/CPP/CPT measurement:

NumMedidas ,
DirEq , EtiqMEA , (*)

(*) It repeats for each remote control measurement. It will be as many as shown in
NumMeasurements.

• NumMeasurements: Number of measurements defined in the remote control.

• DirEq: Address of the device the CPX/CPP/CPT measurement belongs to.
• EtiqMEA: PROCOME label of said CPX/CPP/CPT measurement.
Ex: 18, // Num. measurements
100,0,
100,1,
100,2,
...
4,1,

• Data to configure Remote Control Counters

Each remote control counter is associated a CPX/CPP/CPT counter:

NumContadores ,
DirEq , EtiqCON , (*)

(*) It repeats for each remote control counter. It will be as many as shown in NumContadores.

• NumContadores: Number of counters defined in the remote control.

• DirEq: Address of the device the CPX/CPP/CPT counter belongs to.
• EtiqCON: PROCOME label of said CPX/CPP/CPT counter.

Ex: 16, // Num. Counters

100,0,
100,1,
100,2,
...
4,3,

M1CPTA2005I
1CPT: Substation Central Unit B-222
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data to configure Remote Control Commands

Each remote control command is associated one or two CPX/CPP/CPT commands, as a
function of whether it is double or single:

NumOrdenes ,
IseProcoslv , Doble , DirEq1 , Ise1 , Dco1 , DirEq2 , Ise2 , Dco2 , (*)

(*) It repeats for each remote control command. It will be as many as shown in NumOrdenes.

• NumOrdenes: Number of commands defined in the remote control.

• IseProcoslv: Number of the remote control command.
• Doble: Indicates whether the command is double or not.
• DirEq1: Address of the device the first CPX/CPP/CPT command belongs to.
• ISE1: PROCOME label of the CPX/CPP/CPT command.
• Dco1: Dco of command 1 execution.
• Only for double command, the fields below will be added; they are not read for single
command.
• DirEq2: Address of the device the CPX/CPP/CPT second command belongs to.
• ISE2: PROCOME label of CPX/CPP/CPT command.
• Dco2: Dco of command 2 execution.

Ex: 7, //Num. Commans(ISE)

0, 0, 100,0,2,
1, 0, 100,1,2,
2, 1, 100,2,2, 100,2,1,
...
6, 0, 100,27,2,

The file becomes:

[1] # Configuration file of PROCOME Slave emulator

[2] # SE CARRASQUILLO - CONFIGURATION FOR DEVICE 100 TESTS
[3] # ASO 21/05/2004
[4] 1,
[5] 0,1,0,0,0,0,
[6] #DirRTU,Trazado,TimeEspCdOff,TimeRtsOn,TimeRtsOff,TipoComs,TimeErrComs,H
abSincro,
[7] 13,8,0,33,0,0,1,
[8] # COM1 communications parameters
[9] ,19200,p,8,1,1,
[10] # Signals
[11] 40, // Number of signals
[12] # Index association to DIR,ISC
[13] 6,2, // 0
[14] 6,3, // 1
[15] 6,7, // 2
[16] 6,8, // 3
[17] 6,60, // 4
[18] 257,6, // 5
[19] 256,0, // 6
[20] 256,0, // 7
[21] 100,8, // 8 Local
[22] 100,9, // 9 Panel
[23] 100,10, //10 XXX
[24] 100,11, //11 XXX

M1CPTA2005I
B-223 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[25] 100,12, //12 XXX

[26] 100,13, //13 XXX
[27] 100,14,//14 XXX
[28] 100,15, //15 XXX
[29] 257,17, //16
[30] 100,17, //17 Remote control
[31] 256,0, //18
[32] 256,0, //19
[33] 44,89, //20
[34] 44,90, //21
[35] 44,110, //22
[36] 44,111, //23
[37] 257,44, //24
[38] 256,0, //25
[39] 256,0, //26
[40] 256,0, //27
[41] 256,0, //28
[42] 256,0, //29
[43] 4,2, //30
[44] 4,3, //31
[45] 4,97, //32
[46] 4,98, //33
[47] 4,94, //34
[48] 4,95, //35
[49] 4,100, //36
[50] 4,101, //37
[51] 4,152, //38
[52] 257,4, //39
[53] # Measurements
[54] 18, // Number of measurements
[55] # Index association to DIR,MEA,
[56] 100,0, // 0 ACTIVE POWER T1
[57] 100,1, // 1 ACTIVE POWER T1
[58] 100,2, // 2 BUSBAR VOLTAGE 220kV (T1)
[59] 17,4, // 3 RESERVE
[60] 17,5, // 4 RESERVE
[61] 17,6, // 5 ACTIVE POWER T2
[62] 17,7, // 6 REACTIVE POWER T2
[63] 6,0, // 7 RESERVE
[64] 6,0, // 8 RESERVE
[65] 6,0, // 9 RESERVE
[66] 44,6, //10 ACTIVE POWER T3
[67] 44,7, //11 REACTIVE POWER T3
[68] 6,0, //12 RESERVE
[69] 6,0, //13 RESERVE
[70] 6,0, //14 RESERVE
[71] 4,6, //15 ACTIVE POWER L. VALLEJERA
[72] 4,7, //16 REACTIVE POWER L. VALLEJERA
[73] 4,1, //17 LINE VOLTAGE VALLEJERA 220kV
[74] # Meters
[75] 16, // Num. Meters
[76] # index to DIR,CON
[77] 100,0, //0 METER INPUT ACTIVE ENERGY T1
[78] 100,1, //1 METER OUTPUT ACTIVE ENERGY T1
[79] 100,2, //2 METER INPUT REACTIVE ENERGY T1
[80] 100,3, //3 METER OUTPUT REACTIVE ENERGY T1

M1CPTA2005I
1CPT: Substation Central Unit B-224
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[81] 17,0, //4 METER INPUT ACTIVE ENERGY T2

[82] 17,1, //5 METER OUTPUT ACTIVE ENERGY T2
[83] 17,2, //6 METER INPUT REACTIVE ENERGY T2
[84] 17,3, //7 METER OUTPUT REACTIVE ENERGY T2
[85] 44,0, //8 METER INPUT ACTIVE ENERGY T3
[86] 44,1, //9 METER OUTPUT ACTIVE ENERGY T3
[87] 44,2, //10 METER INPUT REACTIVE ENERGY T3
[88] 44,3, //11 METER OUTPUT REACTIVE ENERGY T3
[89] 4,0, //12 METER INPUT ACTIVE ENERGY L. VALLEJERA
[90] 4,1, //13 METER OUTPUT ACTIVE ENERGY L. VALLEJERA
[91] 4,2, //14 METER INPUT REACTIVE ENERGY L. VALLEJERA
[92] 4,3, //15 METER OUTPUT REACTIVE ENERGY L. VALLEJERA
[93] # Commands
[94] 7,
[95] # ISEProcoslv, Doble ,ISC1(dir1,isc1,dco1),ISC2(dir2,isc2,dco)
[96] 0, 0, 100,0,2,
[97] 1, 0, 100,1,2,
[98] 2, 1, 100,0,2, 100,1,2,
[99] 3, 0, 100,2,2,
[100] 4, 0, 100,3,2,
[101] 5, 1, 100,2,2, 100,3,2,
[102] 6, 0, 100,27,2,

M1CPTA2005I
B-225 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.14 SEVCO Master Protocol: SEVCOMS.CFG

This file “sevcoms.cfg” configures common data related to the interrogation of level 1 devices
using the SEVCO protocol: The number of signals of each type and the parameters associated
to each one are configured in dbase.cfg, as any other device. File format is as follows
• Master Data: [Line 2]

DirRTUEmul ,

• DirRTUEmul: CPX/CPP/CPT address as master.

Ex: 100,

• Data to configure Communications with Level 1 Devices

Serial port configuration parameters. [line 4]

Puerto , Veloc , TipoPar , NumBits , NumStop ,

• Puerto: Communications port. Possible values are COM1 and COM2.

• Veloc: Baud rate. Possible values are 110, 150, 300, 600, 1200, 2400, 4800, 9600 and
19200 baud.
• TipoPar: Parity type. Possible values are ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd); ‘E’, ‘e’, ‘p’,
‘P’ (even).
• NumBits: Number of bits. Possible values are 5, 6, 7 and 8 bits.
• NumStop: Number of stop bits. Possible values are 1 and 2 bits.
Ex: COM2:4800,n,8,1,

• Data on Device Communication Time: [Line 6]

SwRTS SwCTS SwCD RTSon , RTSoff , CDoff ,

• SwRTS: Indicates whether the RTS line will be activated before transmitting. 0 = NO; 1 =
YES. Default value = 0.
• SwCTS: Indicates whether the CTS line will be used. 0 = NO; 1 = YES. Default value = 0.
• SwCD: Indicates whether the CD line will be used. 0 = NO, 1 = YES. Default value= 0.
• RTSon: Time RTS remains set to ON before the transmission (in msec.).
• RTSoff: Time RTS remains set to OFF after the transmission (in msec.).
• CDoff: Carrier deactivation timeout (in msec.).

Ex: 1,1,1,66,11,11,

M1CPTA2005I
1CPT: Substation Central Unit B-226
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on Other Times: [Line 8]

NumReinten , RetMsgBrdcst , IntervRefrescoSen ,

• NumReinten: Number of retries made before a communications failure with the RTU is
issued. Default value = 2.
• RetMsgBrdcst: Time delay after sending a broadcast message to send a new message
(in msec.). Minimum value is 50 msec.
• IntervRefrescoSen: Period of time for signal refreshing requests to level 1 devices (in
seconds). Minimum value = 10 s.

Ex: 50,60,1,

• Data on configured Signal Blocks: [Line 10]

NumBlqED , NumBlqEA , NumBlqEC , NumBlqSD ,

• NumBlqED: Number of configured Digital Signal blocks. It must match the dbase
configured signals. Each block consists of a maximum of 128 signals.
• NumBlqEA: Number of configured Analog Signal blocks. It must match the dbase
configured signals. Each block consists of a maximum of 16 signals.
• NumBlqEC: Number of configured Counter Input blocks. It must match the dbase
configured signals. Each block consists of a maximum of 16 signals.
• NumBlqSD: Number of configured Digital Output blocks. It must match the dbase
configured signals. Each block consists of a maximum of 32 signals.

Ex: 3,1,1,2,

The file becomes:

[1] # Central address as MTU

[2] 100,
[3] # Communications parameters
[4] COM2,4800,n,8,1,
[5] # SwRTS, SwCTS, SwCD, RTSon , RTSoff,CDoff
[6] 1,1,1,60,11,11,
[7] # Retries, ToutBradcast, TimeRefSeñales
[8] 2,50,60,
[9] #NumBlqED, NumBlqEA, NumBlqEC, NumBlqSD,
[10] 3,1,1,2,

M1CPTA2005I
B-227 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.15 Communications with CGC. COMSCGC.CFG

This file “comscgc.cfg” configures data concerning the metering data communications
manager CGC. Meters are configured in dbase.cfg as any other device, stating that the control
protocol is metering type (5) and the port is –1. This file will indicate communications
parameters and the mapping of meter addresses with dbase addresses.

File format is as follows:

• Communications Data: [Lines 2-3]
This line indicates the parameters required for communications between the CGC and
CPX/CPP/CPT.

DirIPCGC , PortCGC ,
CGCToutSocket , IntervMed , CGCIntervCont ,

• DirIPCGC: IP address of the CGC.

• PortCGC: Communications port number of socket CGC.
• CGCToutSocket: Timeout for the response to a CPX/CPP/CPT request. In seconds.
• IntervMed: Measurement request transmission period to the CGC. In seconds.
• CGCIntervCont: Meter request transmission period to the CGC. In seconds.

Ex: 128.127.60.26,32010
4,2,30,

• Meter Address Mapping Data

Configuration parameters for mapping meter addresses to dbase addresses. These data are
needed because meter addresses are in the range 0 to 65535 whereas the addresses of dbase
devices are in the range 0 to 254. [lines 5-9]

NumEqCGC ,
DirEqCGC , DirEqCPX , (*)

(*) It repeats for each meter configured in the CGC. There will be as many as shown in
NumEqCGC.

• NumEqCGC: Number of devices connected to the CGC configured in dbase.

• DirEqCGC: Number indicating the communications address of the meter.
• DirEqCPX: Address of the metering device assigned in dbase.

Ex: 4,
5432, 20,
45645, 21,
32458, 40,
60321, 44,

M1CPTA2005I
1CPT: Substation Central Unit B-228
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # Communications parameters.

[2] 128.127.60.26, 32010,
[3] 4,2,30,
[4] # Address mapping data
[5] 4,
[6] 5432,20,
[7] 45645,21,
[8] 32458,40,
[9] 60321,44,
[10]

M1CPTA2005I
B-229 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.16 Wisp+ Master Protocol: WISPMS.CFG

The Wisp+ Master protocol configuration file (wispms.cfg) consists of five distinct parts. The
first part contains generic data, both internal for the Central Unit and communications
parameters and Wisp+ Master identifiers (configuration of the communications port, RTU
number etc.). The other four parts identify the connections between the CPX/CPP and the
Wisp+ device regarding digital signals, commands, analog measurements and meters.

Due to system requirements, section parameters must be configured placing in ascending order
Wisp+ Master segments and numbers (namely, first the 1,1,; then the 1,2, etc.). All parameters
must be followed by one comma (even the last of a line).

File format is as follows:

• General Data of Master on RTU: [Line 3]

nRTUcfg , flgExtWisp , tPoll , tSync , TCountFreeze , NivelTraza , TimerDelay , ToutRxCabMsg , SincroST ,

• nRTUcfg: Number of RTUs configured.

• FlgExtWisp: Wisp+ Extended flag. Default setting is 1, namely, extended.
• TPoll: Poll time in milliseconds.
• TSync: Synchronisation time in seconds.
• TCountFreeze: Time of Meter Freeze in Minutes. If the number of minutes configured
does not divide exactly one day, the default value is taken (30 minutes).
• NivelTraza: Screen Tracing level.
• TimerDelay: Intermessage gap time FOR TESTS in milliseconds.
• TimeoutRxCabMsg: Timeout for error when receiving the header of a message.
• SincroST: This parameter indicates whether the RTU must be synchronised with summer
/ winter time or standard time (with no change to summer and winter). Default value is
FALSE.
Ej: 1,0,100,30,1,0,50,100,0,

• Configuration Data of Port Communications: [Line 5]

Puerto , Veloc , TipoPar , NumBits , NumStop , TamanoFIFO ,

• Puerto: Communications port. Possible values are COM1, COM2, COM3 and COM4 for
CPX models. Possible values for CPP models are COM1 and COM2.
• Veloc: Baud rate. Possible values are 2400, 4800, 9600 and 19200 baud.
• TipoPar: Parity type. Possible values are ‘N’ or ‘n’ (none); ‘O’, ‘o’, ’i’, ‘I’ (odd); ‘E’, ‘e’, ‘p’,
‘P’ (even).
• NumBits: Number of bits. Possible values are 7 and 8 bits.
• NumStop: Number of stop bits. Possible values are 1 and 2.
• TamanoFIFO: Size of FIFO.
Ex: COM2,9600,N,8,1,1,

M1CPTA2005I
1CPT: Substation Central Unit B-230
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• General Data of Device Configuration: [Line 10]

DirRTU , SistRTU , NumSegISCs , NumBytesISCs , NumSegISEs , NumSalISEs , …

... NumSegMEAs , NumMEAs , NumSegCONs , NumCONs , DirProcoEq ,

• DirRTU: RTU address.

• SistRTU: System the RTU belongs to, in case “FlgExtWisp” has been configured as
Wisp+ Extended.
• NumSegISCs: Number of segments of the ISCs.
• NumBytesISCs: Number of bytes of the ISCs.
• NumSegISEs: Number of segments of the ISEs.
• NumSalISEs: Number of Outputs of the ISEs.
• NumSegMEAs: Number of segments of the MEAs.
• NumMEAs: Number of MEAs.
• NumSegCONs: Number of segments of the CONs.
• NumCONs: Number of CONs.
• DirProcoEq: Address of the equivalent PROCOME device.
Ex: 1,0, 4,13, 5,13, 3,12, 2,7, 43,

• Configuration Data of Single Contact type Signals of the Device

Each remote control signal of this type is associated a CPX/CPP digital signal. It is essential
that DirWisp (Seg + Sal) are in ascending order: [lines 25-41]

Seg , Byte , ISCini , Prioridad ,

• Seg: Segment number.

• Byte: Number of Bytes.
• ISCini: Starting ISC associated to the first of 8 bits associated to each Byte.
• Prioridad: Priority Level. The ranking is from less to more priority [1->3]. In case of signals
the intermediate value, 2, is normally set reserving the maximum priority for response to
control and messages with specific data.

Ex: 1,1, 0, 2, // Segmento,Byte, ISCini, Prioridad

1,2, 8, 2,
1,3, 16, 2,
1,4, 24, 2,
2,1, 128, 2,
2,2, 136, 2,
2,3, 144, 2,
2,4, 152, 2,
3,1, 256, 2,
3,2, 264, 2,
3,3, 272, 2,
3,4, 280, 2,
13,1, 320, 2,

M1CPTA2005I
B-231 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Device Commands

Each device command is associated a CPX/CPP command. It is essential that DirWisp (Seg +
Nsal) are in ascending order: [lines 16-23]

Seg , Salida , ISEon , ISEoff , Tipo ,

• Seg: Number of remote control commands.

• Salida: Output number within each Segment.
• ISEon: Activation Command.
• ISEoff: Deactivation Command.
• Tipo: Command type. (CON_SEGURO or 6= SALIDA_RELE).

Ex: 1,1, 0,1, 4,//Seg,Salida(1Seg=16Sal=32mando),ISEon,ISEoff,Tipo,

1,2, 2,3, 4,
1,3, 4,5, 4,
2,1, 32,33, 4,
2,2, 34,35, 4,
2,3, 36,37, 4,
3,1, 64,65, 4,
3,2, 66,67, 4,
3,3, 68,69, 4,
4,1, 96,97, 4,
4,2, 98,99, 4,
4,3, 100,101, 4,
17,2, 124,125, 6, // Local/Remote command in logic segment 17
// that does not exist physically. Command type=6.

• Configuration Data of Device Measurements.

Each device measurement is associated a CPX/CPP measurement: [lines 43-48]

Seg , Medida , MEA , Tasa , Alisado , Prioridad ,

• Seg: Segment Number.

• Medida: Number of Measurements within said segment.
• MEA: Associated Measurement Number.
• Tasa: Measuring period in seconds. Range [0->255].
• Alisado: Dejagging level. It is the minimum amount the value must vary to be considered
significant. This value comes in PROCOME accounts. The range is [0->255].
• Prioridad: Priority Level. The ranking goes from less to more priority [1->3]. In case of
measurements and meters it is normally set to the minimum value, 1.

M1CPTA2005I
1CPT: Substation Central Unit B-232
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ej: 1,1, 0, 10,10,1, //Seg,Medida,MEA,Tasa,Alisado,Prioridad,

1,2, 1, 10,10,1,
1,3, 2, 10,10,1,
1,4, 3, 10,10,1,
2,1, 4, 10,10,1,
2,2, 5, 10,10,1,
2,3, 6, 10,10,1,
2,4, 7, 10,10,1,
3,1, 8, 10,10,1,
3,2, 9, 10,10,1,
3,3, 10, 10,10,1,
3,4, 11, 10,10,1,

• Configuration Data of Device Meters

Each device meter is associated a CPX/CPP meter. It is essential that DirWisp (Seg + N_Cont)
are in ascending order: [lines 50-56]

Seg , Cont , CON Prioridad ,

• Seg: Segment Number.

• Cont: Meter number in said segment.
• CON: Procome label of device Meter.
• Prioridad: Priority Level. The ranking goes from less to more priority [1->3]. In case of
measurements and meters it is normally set to the minimum value

Ej: 1,1, 0, 1,// Seg,Cont,CON, Priority,

1,2, 1, 1,
1,3, 2, 1,
1,4, 3, 1,
2,1, 4, 1,
2,2, 5, 1,
2,3, 6, 1,

The file becomes:

[1] # Configuration of RTUs with Extended WISP+ protocol

[2] # nRTUscfg,flgExtWisp,tPoll,Tsync,TCountFreeze,NivelTraza,
[3] # TimerDelay,ToutRxCabMsg,SincroST,
[4] 1,0,100,30,1,0,50,100,0,
[5] # Communications parameters of the port
[6] COM2,9600,N,8,1,1,
[7] # General configuration data of devices
[8] ##############################################
[9] # EQUIPO WISP 1 (Addr.Procome 43)
[10] ##############################################
[11] # DirRTU,SistRTU, NumSegISCs,NumBytesISCs, NumSegISEs,NumSalISEs,
[12] # NumSegMEAs,NumMEAs, NumSegCONs,NumCONs,DirProcoEq,
[13] # 1,0, 4,13, 5,13, 3,12, 2,7, 43,
[14] #################
[15] # ISCs: Segment,Byte,ISCini,Priority,
[16] 1,1, 0, 2,
[17] 1,2, 8, 2,

M1CPTA2005I
B-233 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[18] 1,3, 16, 2,

[19] 1,4, 24, 2,
[20] 2,1, 128, 2,
[21] 2,2, 136, 2,
[22] 2,3, 144, 2,
[23] 2,4, 152, 2,
[24] 3,1, 256, 2,
[25] 3,2, 264, 2,
[26] 3,3, 272, 2,
[27] 3,4, 280, 2,
[28] 13,1, 320, 2,
[29] #################
[30] # ISEs: Seg,Output(1Seg=16Out=32comm) ,ISEon,ISEoff, Type,
[31] 1,1, 0,1, 4,
[32] 1,2, 2,3, 4,
[33] 1,3, 4,5, 4,
[34] 2,1, 32,33, 4,
[35] 2,2, 34,35, 4
[36] 2,3, 36,37, 4,
[37] 3,1, 64,65, 4,
[38] 3,2, 66,67, 4,
[39] 3,3, 68,69, 4,
[40] 4,1, 96,97, 4,
[41] 4,2, 98,99, 4,
[42] 4,3, 100,101, 4,
[43] #################
[44] # MEAs: //Seg,Measur, MEA, Rate,Dejagging,Priority,
[45] 1,1, 0, 10,10,1,
[46] 1,2, 1, 10,10,1,
[47] 1,3, 2, 10,10,1,
[48] 1,4, 3, 10,10,1,
[49] 2,1, 4, 10,10,1,
[50] 2,2, 5, 10,10,1,
[51] 2,3, 6, 10,10,1,
[52] 2,4, 7, 10,10,1,
[53] 3,1, 8, 10,10,1,
[54] 3,2, 9, 10,10,1,
[55] 3,3, 10, 10,10,1,
[56] 3,4, 11, 10,10,1,
[57] #################
[58] # CONs: Seg,Meter, CON, Priority,
[59] 1,1, 0, 1,
[60] 1,2, 1, 1,
[61] 1,3, 2, 1,
[62] 1,4, 3, 1,
[63] 2,1, 4, 1,
[64] 2,2, 5, 1,
[65] 2,3, 6, 1,

M1CPTA2005I
1CPT: Substation Central Unit B-234
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.17 IEC-61850 Module (1CPT Models)

This chapter describes the configuration files of the IEC-61850 module integrated into the CPT,
which comprises the following components:

• Configuration of IEC-61850 Client

• Configuration of 61850 IEDs to be connected to the CPT.
• Configuration of IEC-61850 Server

Activation of the CPT’s IEC61850 module is carried out by including the following line in the
PROTASK.CFG configuration file of the CPT:

0, IEC61850, IEC61850, 2048, 288,

The above Configuration line specifies the address (288) of the logic device that represents the
IEC61850 server module of the CPT within its real time database.

B.17.1 Configuration of IEC-61850 Client: 61850CLI.CFG

This file “61850cli.cfg” lists the different compatible IEC-61850 relays that the IEC-61850
Client of the CPT is to be connected to. Each relay will be referenced in the file by its IEDName
and so it will be mapped to a virtual device within the CPT’s real time Database.

Communication with IEC-61850 relays will be available by one of the two LAN ports (LAN1 or
LAN2) of the CPT, and the selection of the network port will be determined by parameter
IndexLANCentral (index of the network adapter to be used by the Central Unit application)
configured in file TCP.CFG.

The file “61850cli.cfg” can also configure a number of general parameters of the CPT’s IEC-
61850 Client.

File format is as follows:

• Data on the Number of IEC-61850 Devices: [Line 4]

NumIEDs , NivelMonitorCliente , NivelMonitorMMS ,

• NumIEDs: Number of IEC-61850 IEDs connected to the CPT.

• NivelMonitorCliente: General trace monitoring level of the IEC-61850 Client.
• NivelMonitorMMS: Trace monitoring level of MMS protocol.

Ej: 48,0,0,

M1CPTA2005I
B-235 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of OSI 1 Readdressing associated to IEC-61850 Client :

[Line 6]
These data contain the OSI selectors that the CPT’s IEC-61850 Client will use in the
connections with IEC-61850 IEDs. [line 4]

osi_tsel , osi_ssel , osi_psel ,

• osi_tsel: OSI transport selector.

• osi_ssel: OSI session selector.
• osi_psel: OSI presentation selector.

Ex: 0001,01,0001,

• Configuration Data of Common Times for all IED’s: [Line 13]

IEDConnectingTi , ServerShort , ServerLong , MMSKeepA MMSKeep , ReportsCheck ,

meout IdleTime IdleTime liveTime AliveInterval Period

OldBufReports , OldBufReports , EntryID , ConfigRev , BRCBs ,

CollectBRCBTime CollectIEDTime StoreInterval CheckPeriod DisabledTime

SCLOperationPeriod ,

• IEDConnectingTimeout: Maximum time in sec. used during the phase of implementation

of the association with an IED, before a communications failure with the IED is issued in
case the connection with the IED is not achieved. Minimum value is 20, which matches
the default value.
• ServerShortIdleTime: Short time in sec. during which the IEC-61850 Client temporarily
switches a failed ‘relevant’ IED communication to inactive status, before a retry. Minimum
value is 10, which matches the default value.
• ServerLongIdleTime: during which the IEC-61850 Client temporarily switches a failed
‘non relevant’ IED communication to inactive status, before a retry. Minimum value is 60,
which matches the default value.
• MMSKeepAliveTime: Time in sec. used as MMS 2 protocol Keep-Alive time, such that if
this time times out before the IEC-61850 Client receives IED data, the IED status is
requested through the MMS protocol Status service. Minimum value is 360, which
matches the default value.
• MMSKeepAliveInterval: Time in seconds used between retries of IED status request at
MMS protocol level, after the previous status request has failed. Minimum value is 10,
which matches the default value. The number of retries is limited to 5 (for any MMS
communications service) before IED communication failure is issued.
• ReportsCheckPeriod: Time in seconds to request the enable status of the IED Report
Control Blocks linked to the CPT, in case no Report is received during the configured
time interval. The minimum value of 300 matches the default value.

Table B-1:1 OSI: Open Systems Interconnection

Table B-2:2 MMS: Manufacturing Message Specification (ISO 9506)

M1CPTA2005I
1CPT: Substation Central Unit B-236
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• OldBufReportsCollectBRCBTime: Stand alone timeout in seconds for each ‘Buffered’

type IED Report Control Block, before a request of a general refresh of the ‘Buffered’ type
IED Report Control Block on the part of the CPT’s IEC-61850 Client takes place. The
purpose of this time window is retrieving those Reports generated by the IED before
establishing the new link from the CPT’s IEC-61850 Client and therefore not received
previously by the CPT. This window will reset whenever an IED Report is received before
the time window times out. Default value is 1.
• OldBufReportsCollectIEDTime: IED time window in seconds, the function of which is to
limit constant resets of the time windows associated to each ‘Buffered’ IED Report
Control Block that come before the request on the part of the CPT’s IEC-61850 Client for
general refresh of the ‘Buffered’ IED Report-Control-Blocks. Therefore this window will
never reset, such that should it time out, the individual window for every ‘Buffered’ IED
Report-Control-Block will disable, then requesting a general refresh of said Report-
Control-Blocks on the part of the CPT’s IEC-61850 Client. Default value is 60.
• EntryIDStoreInterval: Time in sec. that indicates the frequency used by the CPT’s IEC-
61850 Client to write non volatile ‘EntryID’ attributes associated to received ‘Buffered’
type Reports. Default value is 1.
• ConfigRevCheckPeriod: Time in seconds used by the CPT’s IEC-61850 Client to check
whether an IED configuration or parameterisation has been changed. Minimum value is
20, which matches the default value.
• BRCBsDisabledTime: Time in seconds used to keep a ‘Buffered’ IED Report-Control-
Block temporarily disabled, after the CPT’s IEC-61850 Client has detected a ‘Buffer
Overflow’ in said Report-Control-Block. Minimum value is 10, which matches the default
value.
• SCLOperationPeriod: Time in seconds used for the periodic check of the status of the
validation operation for an IED CID file, after having been initiated from the Central Unit
IEC-61850 Client. The minimum allowable value for the periodic check of the status of the
validation operation for an IED CID file is 5, which matches the default value.

Ex: 20,10,60,360,10,300,1,60,1,20,10,5,

M1CPTA2005I
B-237 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on IEC-61850 Devices: [Lines 16-42]

IEDname , (*)

(*) It repeats for each IEC-61850 device to be connected to the CPT’s IEC-61850 Client.

• IEDName: Name of the IEC-61850 IED.

Ej: # IED nº 1
COND_SSAA, // AUXILIARY SERVICES, ZIV 6MCV
# IED nº 2
CONDEQ01I01,// LINE 1 132 kV, ZIV 7IRV
# IED nº 3
CONDEQ01I02,// LINE 1 132 kV, REL670
. . . . . .

# IED nº 13
CONDEQ05I03,// TRANSFORMER 2 VOLTAGE REGULATOR, ZIV 6RTV
# IED nº 14
CONDEQ05I04,// TRANSFORMER 2 DIFFERENTIAL, ZIV 8IDV

The file becomes:

[1] # File 61850CLI.cfg

[2] # IEC-61850 Client file for CPT
[3] # SUBSTATION: CONDOMINA
[4] 14,0,0,// Nº of IEDs, Client Monitor Level, MMS Monitor Level
[5] # Configuration of OSI addressing associated to IEC-61850 Client
[6] 0001,01,0001,// osi_tsel, osi_ssel, osi_psel
[7] # Configuration of common times for all IEDs:
[8] # IEDConnectingTimeout, ServerShortIdleTime, ServerLongIdleTime,
[9] # MMSKeepAliveTime, MMSKeepAliveInterval, ReportsCheckPeriod,
[10] # OldBufReportsCollectBRCBTime, OldBufReportsCollectIEDTime,
[11] # EntryIDStoreInterval,ConfigRevCheckPeriod, BRCBsDisabledTime,
[12] # SCLOperationPeriod
[13] 20,10,60,360,10,300,1,60,1,20,10,5,
[14] #
[15] # IED nº 1
[16] COND_SSAA, // AUXILIARY SERVICES, ZIV 6MCV
[17] # IED nº 2
[18] CONDEQ01I01,// LINE 1 132 kV, ZIV 7IRV
[19] # IED nº 3
[20] CONDEQ01I02,// LINE 1 132 kV, REL670
[21] # IED nº 4
[22] CONDEQ02I01,// LINE 2 132 kV, ZIV 7IRV
[23] # IED nº 5
[24] CONDEQ02I02,// LINE 2 132 kV, REL670
[25] # IED nº 6
[26] CONDEQ03I01,// TRANSFORMER 1 132 kV, ZIV 7IRV
[27] # IED nº 7
[28] CONDEQ03I02,// TRANSFORMER 1 SPECIFIC POINTS, GE F650
[29] # IED nº 8
[30] CONDEQ03I03,// TRANSFORMER 1 VOLTAGE REGULATOR, ZIV 6RTV
[31] # IED nº 9
[32] CONDEQ03I04,// TRANSFORMER 1 DIFFERENTIAL, ZIV 8IDV
[33] # IED nº 10
[34] CONDEQ04I01,// CONNECTION 132 kV, ZIV 7IRV

M1CPTA2005I
1CPT: Substation Central Unit B-238
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[35] # IED nº 11
[36] CONDEQ05I01,// TRANSFORMER 2 132 kV, ZIV 7IRV
[37] # IED nº 12
[38] CONDEQ05I02,// TRANSFORMER 2 SPECIFIC POINTS, GE F650
[39] # IED nº 13
[40] CONDEQ05I03,// TRANSFORMER 2 VOLTAGE REGULATOR, ZIV 6RTV
[41] # IED nº 14
[42] CONDEQ05I04,// TRANSFORMER 2 DIFFERENTIAL, ZIV 8IDV

B.17.2 Configuration of 61850 IEDs in the CPT

Unit real time database, from its CID File that describes the IED Configuration. For this task, the
ZIV Central Unit configuration program or Zivergraph© will be used that includes the option to
integrate IEC-61850 into the CPT.

Zivergraph© incorporates a component for processing IED CID Files, such that after the
Configuration Engineer has selected IEC-61850 commands and IED ‘Report-Control-Blocks’
reserved for the CPT that is being configured, necessary data for the Zivergraph© to add a new
protection and control device in the Central Unit is generated.

Then the configuration engineer may modify the different attributes associated to digital signals,
measurements, meters and commands generated by the Zivergraph© for the new 61850
protection and control device that is being integrated into the Central Unit.

Upon completion of the 61850 IED configuration through the Zivergraph©, a new logic device
will appear in file DBASE.CFG of the Central Unit (with IEC-61850 communications protocol)
with the digital signals, measurements, meters and commands associated to the IED. Also, an
exclusive IED CFG file, identified with the IED name, which contains the mapping of the IEC-
61850 IED data to the CPT’s real time Database is generated.

Then, the different sections of a mapping file of a 61850 IED in the Central Unit are described.
• IED General Data: [Line 17]

IEDName , DirEqLog , NivelMonitorIED ,

LDName_1 , LDName_2 , ... LDName_i ,

(*)
(*) There will be as many as logic devices in the CID file of the IED.

• IEDName: name of the IED IEC-6185.

• DirEqLog: logic device address which contains the mapping of the IED in the Central Unit
data base.
• NivelMonitorIED: Trace monitoring level of communications between the CPT and the
IEC-61850 IED.
• LDName_i: Name of an IED Logic Device.

Ex: CONDEQ01I01,5,0,LD1,

M1CPTA2005I
B-239 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Parameters to Establish IED Communications: [Lines 19-24]

DirIP , Subred , Gateway , osi_tsel , osi_ssel , osi_psel ,

LocalDetail , ServicesCalling , ServicesCalled , NestLevel , VersNumber ,
ServicesSup , ParamCBBs , TransportType , MMSStackType , Reserva ,
AUTH_enabled , AUTH_mechanism , AUTH_password ,

• DirIP: TCP-IP address of the IED.

• Subred: Subnet mask that the IED belongs to.
• Gateway: TCP-IP address of the Gateway to the IED.
• osi_tsel: OSI transport selector used by the IED.
• osi_ssel: OSI session selector used by the IED.
• osi_psel: OSI presentation selector used by the IED.
• LocalDetail: Maximum size of the PDU for the MMS protocol proposed by the Central Unit
in the MMS connection process to the IED. Default value is 8192.
• ServicesCalling: Maximum number of MMS transactions initiated by the MMS client
proposed by the Central Unit, in the MMS connection process to the IED, to be
simultaneously supported in the IED. Default value is 6.
• ServicesCalled: Maximum number of MMS transactions transmitted to the MMS client
proposed by the Central Unit, in the MMS connection process to the IED, to be
simultaneously supported in the IED. Default value is 6.
• NestLevel: Maximum nesting level supported by the Central Unit in the structure of data
interchanged with the IED. Default value is 6.
• VersNumber: Version of ISO 9506 (MMS) proposed by the Central Unit, in the MMS
connection process to the IED, for IED communications. Version 1 is available at the
Central Unit, and will be the default value.
• ServicesSup: Parameter defining MMS protocol services, proposed by the Central Unit, in
the MMS connection process to the IED, for IED communications. A value 0 for this
parameter implies using the default value: (status | getNameList | identify | read | write |
getVarAccessAttr | defineNamedVarList | getNamedVarListAttr | deleteNamedVarList |
getDomainAttr | readJournal | writeJournal | initializeJournal | reportJournalStatus |
getCapList | fileOpen | fileRead | fileClose | fileDelete | fileDirectory | unsolicitedStatus |
informationReport | conclude | cancel).
• ParamCBBs: Parameter defining MMS protocol “Conformance Building Blocks” (or
CBB’s), proposed by the Central Unit, in the MMS connection process to the IED, for IED
communications. A value 0 for this parameter implies using the default value: (str1 | str2 |
vnam | valt | vlis).
• TransportType: Type of transport stack used by the Central Unit, possible options being:
"tcp" and "osi".
• MMSStackType: Type of communications stack used at MMS protocol level, possible
options being: “short”, “full” and “fastbyte”.
• Reserva: Parameter not available, and the value is 0.
• AUTH_enabled: Enables establishing the IED communication using authentication at
MMS level.
• AUTH_mechanism: Authentication method used during the IED communication.
• AUTH_password: Password used by the Central Unit for authenticated IED
communication.

M1CPTA2005I
1CPT: Substation Central Unit B-240
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: CONDEQ01I01,5,0,LD1,
# Configuracion del IED:
# Nombre IED, Dir. Equipo en BD UCS, NivelTraza,NombresLDs(,..,),
CONDEQ01I01,5,0,LD1,
# Dir IP, Subred, Gateway, osi_tsel, osi_ssel, osi_psel
10.193.60.5,255.255.255.0,172.16.1.254,0001,0001,00000001,
# LocalDetail, ServicesCalling, ServicesCalled, NestLevel,
VersNumber
32717,6,6,5,1,
# ServicesSup, ParamCBBs, TransportType, MMSStackType, Reserva
7738001c2000000080f71800,8700,tcp,full,0,
false,520301,ziv,// AUTH_enabled,AUTH_mechanism, AUTH_password

• Configuration of IED Buffered Report-Control-Blocks: [Lines 27-228]

In this section of the IED mapping file, the IED Buffered Report-Control-Blocks the IED makes
available to the Central Unit IEC-61850 Client are configured.

NumBRCBs ,
BRCBRef , BRCBRef_2 ,
SeqNumber , ReportTimeStamp , ReasonForInclusion , DatasetName , …

… DataRef , BufferOverflow , EntryID , ConfRevision ,

DataChange , QualityChange , DataUpdate , Integrity ,

(*
BufferTime , IntegrityPeriod , bRefrescoCiclico ,
DatSetRef , NumTotDSMembers ,
NumMappedDSMembers ,
IndexDataSetMember , MemberRef , NumPrimitiveDAs ,

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , … (**)

… P , MappingType , Param_1 , Param_2 , … Param_i , (***)

(*) It repeats for each Buffered Report-Control-Block the IED makes available to the
Central Unit IEC-61850 Client. There will be as many as shown in NumBRCBs.
(**) It repeats for each mapped dataset member associated to a Report-Control-Block.
There will be as many as shown in NumMappedDSMembers.
(***) It repeats for each primitive attribute of the dataset member being mapped. There will
be as many lines as shown in NumPrimitiveDAs.

M1CPTA2005I
B-241 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

• NumBRCBs: Number of Buffered Report-Control-Blocks the IED makes available to the

Central Unit IEC-61850 Client.
• BRCBRef: IEC-61850 reference of the Report-Control-Block (including the Logic Device).
• BRCBRef_2: Is the IEC-61850 reference of the Report-Control-Block (including the Logic
Device) to be used in Hot-Hot Redundancy to check the connection status of the other
CPT. (Only used for Hot-Hot redundancy).
• Both CPT must have different configuration for BRCBRef and BRCBRef_2 fields, but
must be complementary. For example, if the main CPT has the following configuration:
LD1/LLN0.brcb01,LD1/LLN0.brcb02, the secondary CPT will have this one:
LD1/LLN0.brcb01,LD1/LLN0.brcb02.
• SeqNumber: Allows enable (value 1) or disable (value 0) the inclusion of the sequence
number (attribute SqNum or SubSqNum) in the IED generated Reports for the Report-
Control-Block.
• ReportTimeStamp: Allows enable (value 1) or disable (value 0) the inclusion in the
Reports of the time and date at which every IED generated Report is created (attribute
TimeOfEntry) for the Report-Control-Block.
• ReasonForInclusion: Allows enable (value 1) or disable (value 0) the inclusion in the
Reports of the cause (attribute ReasonCode) whereby all data constituting the IED
generated Reports for the Report-Control-Block are included.
• DatasetName: Allows enable (value 1) or disable (value 0) the inclusion of the name of
the dataset in the IED generated Reports for the Report-Control-Block.
• DataRef: Allows enable (value 1) or disable (value 0) the inclusion of the MMS reference
of all data constituting the IED generated Reports for the Report-Control-Block.
• BufferOverflow: Allows enable (value 1) or disable (value 0) the inclusion in the IED
generated Reports for the Report-Control-Block, of the attribute serving as fill indicator of
the buffer assigned to the Report-Control-Block in the IED.
• EntryID: Allows enable (value 1) or disable (value 0) the inclusion in the Reports of the
identifier of each IED generated Reports for the Report-Control-Block.
• ConfRevision: Allows enable (value 1) or disable (value 0) the inclusion in the Reports of
the attribute containing the number of times the Configuration of the dataset associated to
the IED Report-Control-Block has been changed.
• DataChange: Allows enable (value 1) checking the changes of data constituting the
dataset associated to the Report-Control-Block, as a requirement for generating Reports.
The value 0 will not change in the IED the Requirement for generating Reports by data-
change for the Report-Control-Block.
Note: The Central Unit IEC-61850 Client automatically activates the Requirement for
generating Reports by general-interrogation for the Report-Control-Block.
• QualityChange: Allows enable (value 1) checking the changes of the quality of data
constituting the dataset associated to the Report-Control-Block, as a requirement for
generating Reports. The value 0 will not change in the IED the requirement for generating
Reports by quality-change for the Report-Control-Block.
• DataUpdate: Allows enable (value 1) checking the updating of data constituting the
dataset associated to Report-Control-Block, as requirement for generating Reports. The
value 0 will not change in the IED the requirement for generating Reports by data-update
for the Report-Control-Block.
• Integrity: Allows enable (value 1) checking in the IED the end of a refresh period of data
constituting the dataset associated to the Report-Control-Block, as a requirement for
generating Reports. The value 0 will not change in the IED the requirement for generating
Reports by integrity for the Report-Control-Block.
Note: The value 0 for the set of the four parameters DataChange, QualityChange,
DataUpdate e Integrity implies not to change the value of the attribute TrgOps in
the IED Report-Control-Block

M1CPTA2005I
1CPT: Substation Central Unit B-242
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• BufferTime: Value (in millisec.) to be configured in the Report-Control-Block to establish

the duration of the time interval elapsed from the instant the first requirement for
generating new Reports is detected until this is finally sent by the IED. The value 0
implies the value of the attribute BufTm in the IED Report-Control-Block is not modified.
• IntegrityPeriod: Value (in millisec.) to be configured in the Report-Control-Block as time
interval for generating Reports periodically, for which it will be necessary that the Report-
Control-Block has the requirement for generating Reports by integrity activated. The
minimum configurable value in the Central Unit for this parameter will be 1500
milliseconds. The value 0 implies not to modify the value of the attribute IntgPd in the IED
Report-Control-Block.
• bRefrescoCiclico: Enables the Central Unit function for general cyclic interrogation of the
IED Report-Control-Block (when the associated dataset contains measurements or
meters), the period of Reports request by general-interrogation being the value
configured for parameter PerioLectMed in file CENTRAL.CFG (chapter A.2 in the CPT
manual).
• DatSetRef: IEC-61850 reference of the dataset associated to the Report-Control-Block
that appears in the IED CID file (including the Logic Device). The Central Unit IEC-61850
Client, upon establishing the association with the IED, checks the match between the
dataset configured in the IED and the dataset configured in the CID for the same Report-
Control-Block.
• NumTotDSMembers: Total number of members constituting the dataset associated to the
Report-Control-Block (mapped and not mapped to the Central Unit real time database)
appearing in IED CID file. The Central Unit IEC-61850 Client, upon establishing the
association with the IED, checks this data in the dataset configured in the IED matches
the same data in the dataset configured in the CID for the same Report-Control-Block.
• NumMappedDSMembers: Number of members of the dataset associated to the Report-
Control-Block to be finally mapped to Central Unit real time database.
• IndexDatasetMember: Index (starting at zero) within the dataset of the member to be
mapped to the Central Unit real time database.
• MemberRef: Is the IEC-61850 reference of the dataset member (including the Logic
Device).
• NumPrimitiveDAs: Number of primitive attributes (they match basic IEC-61850 data)
constituting the dataset member to be mapped to the Central Unit real time database.
• IdxDataInNestingLevel_i: Index sequence (starting at zero from the nesting level
immediately under the data specified in the dataset) of the components within each
nesting level of the structure of the dataset member IEC-61850 data, which set up the
path (applying the functional constraint filter associated to the dataset member data)
within the data structure to reach the primitive attribute (basic data) that is to be mapped
to the Central Unit real time database. The end of the index sequence of a data primitive
attribute will be tagged with character ‘P’.
• P: Character ‘P’ that indicates the end of the sequence of indices that set up the path to
reach the primitive attribute of the dataset member data.
• MappingType: Type of mapping assigned to the primitive attribute of the dataset member
data, to be included within the Central Unit real time database.
• Param_i: Sequence of parameters that define completely the mapping of the primitive
attribute of the dataset member data, within the Central Unit real time database.

M1CPTA2005I
B-243 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

As mentioned above, for each dataset member associated to the Report-Control-Block the
required data must be configured for its mapping within the Central Unit internal database. The
mapping data to be included, for each dataset member, will depend on the type of IEC-61850
data to map and more specifically on the primitive attributes (they match with the type of basic
IEC-61850 data) that constitute it, as these are the objects that will actually be mapped to the
different types of similar data available in the Central Unit real time database.

The Zivergraph© software, through the built-in component for processing IED CID files, can
generate for the Central Unit the mapping information of the IEC-61850 data constituting the
dataset, from preset criteria that define the primitive attributes, within each type of IEC-61850
data relevant for the Central Unit that will finally be mapped to similar data within the Central
Unit database.

As above mentioned, in the context of a dataset member IEC-61850 data, for each primitive
attribute finally mapped by the Zivergraph© to an object of the Central Unit database, a
configuration line will appear that will include the sequence of component indices
IdxDataInNestingLevel_i, ending in the character ‘P’, followed by the information on the
mapping assigned by the Zivergraph© for the primitive attribute, within the Central Unit internal
database. Mapping data will depend on the type of IEC-61850 data to map.

Mapping an IEC-61850 primitive attribute may require one or more data within the Central Unit
database. Types of mapping available are:

• Types ‘S’ and ‘ST’: the IEC-61850 primitive attribute being mapped is Boolean type and
so it is mapped only to a single digital signal. In case the primitive attribute is Transient
type, ‘ST’ mapping will be used, signifying that the deactivation of the single digital signal
associated in the Central Unit database will be forced from inside the CPT itself.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , EtiqISC ,

• MappingType: Type of mapping ‘S’ and ‘ST’.

• EtiqISC: Identifier of the single digital signal used for mapping the IEC-61850 primitive
attribute, in the Central Unit database.

Ex: # general
0,P,ST,241,

M1CPTA2005I
1CPT: Substation Central Unit B-244
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

- Type ‘MS’: the IEC-61850 primitive attribute being mapped represents a tag that can take
more than two states, thus it is mapped to several single digital signals (one digital signal
for each state that may tag the primitive attribute to be mapped in the Central Unit
database).

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , NumISCs , ...

… Valor61850_1 , EtiqISC_1 , ... Valor61850_i , EtiqISC_i ,

(*)
(*) It repeats for each state that can tag the IEC-61850 primitive attribute to be mapped in the
Central Unit database. There will be as many as shown in NumISCs.

• MappingType: Type of mapping ‘MS’.

• NumISCs: Number of Central Unit database single digital signals used for mapping the
possible states of the IEC-61850 primitive attribute being mapped.
• Valor61850_i: Value of a possible state of the IEC-61850 primitive attribute.
• EtiqISC_i: Identifier of the single digital signal used for mapping the value Valor61850_i of
the IEC-61850 primitive attribute.

Ex: # stVal
0,P,MS,4,0,238,1,239,2,240,3,238,

- Types ‘O’ and ‘OT’: the IEC-61850 primitive attribute being mapped represents the
component orCat of the attribute origin (Originator type in IEC-61850) of a composite
data (also including other primitive attributes affected by the origin attribute data), that is
mapped to five single digital signals (one digital signal for each of the following categories
of the origin of a change in an IEC-61850 data : bay-control, station-control, remote-
control, automatic-bay and automatic-station). In case a Transient type primitive attribute
related to the attribute origin has been mapped to the IEC-61850 compound data, ‘OT’
type mapping will be used, meaning that the deactivation of the associated single digital
signals within the Central Unit database will be forced from within the CPT itself.

M1CPTA2005I
B-245 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , ...

… EtiqISCAtribPrimValue , NumCatOrigin , ...

(*)
… ValorOrigin_1 , EtiqISC_1 , ... ValorOrigin _i , EtiqISC_i ,

(**)

(*) It repeats for each value of the IEC-61850 primitive attributes (that is also part of the IEC-
61850 composite data that includes the attribute origin) that have been previously mapped and
are affected by the attribute origin whose orCat component is being mapped. The mapping of
the origin of change in IEC-61850 data for a maximum of 20 values of various IEC-61850
primitive attributes is allowed.
(**) It repeats for each category of the origin of change in IEC-61850 data that is to be mapped
to the Central Unit database. There will be as many as shown in NumCatOrigin.

• MappingType: Type of mapping ‘O’ and ‘OT’.

• EtiqISCAtribPrimValue: Identifier of the single digital signal previously used for mapping
(to the Central Unit database) the value of an IEC-61850 primitive attribute, part of the
same IEC-61850 composite data that includes the attribute origin being mapped and thus
affected by the same.
• NumCatOrigin: Number of categories of the origin of change in IEC-61850 data being
mapped to the Central Unit database, for the value of a previously mapped IEC-61850
primitive attribute.
• ValorOrigin_i: Value of a possible category of origin of change in the value of the IEC-
61850 primitive attribute, previously mapped by digital signal EtiqISCAtribPrimValue.
• EtiqISC_i: Identifier of the single digital signal used for mapping the value ValorOrigin_i of
the category of origin of change in the value of the IEC-61850 primitive attribute,
previously mapped by digital signal EtiqISCAtribPrimValue.

Ex: # origin.orCat
3,0,P,OT,241,4,1,242,2,243,3,244,4,245,

M1CPTA2005I
1CPT: Substation Central Unit B-246
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

- Type ‘M’: the IEC-61850 primitive attribute being mapped represents an analog value and
thus is mapped in floating point.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , EtiqMEA , IEDUnits , ScaleFactor , ClientUnits , ...

Multiplier Multiplier

… Data61850Ref [ConfAttrib61850Names] ,

(*)

(*) This field will only be configured when the IEC-61850 composite data containing the IEC-
61850 analog type primitive attribute being mapped, also contains the configuration attribute of
the scale range (IEC-61850 attribute named rangeC), or configuration attribute of the units of
said analog attribute (IEC-61850 attribute named units), or both.

• MappingType: Type of mapping ‘M’.

• EtiqMEA: Identifier of the measurement, within the Central Unit database, used for
mapping the IEC-61850 analog type primitive attribute.
• IEDUnitsMultiplier: Scale value (expressed as exponent in the power of 10) used by the
61850 IED to express the units of the IEC-61850 analog type primitive attribute.
• ScaleFactor: Scale factor by which the values of the IEC-61850 analog type primitive
attribute are to be divided, within the Central Unit.
• ClientUnitsMultiplier: Scale value (expressed as exponent in the power of 10) used by the
Central Unit real time database, to express the units of the IEC-61850 analog type
primitive attribute.
• Data61850Ref[ConfAttrib61850Names]: Parameter composed of the 61850 reference of
the IEC-61850 composite data (including the Logic Device name) that contains the IEC-
61850 analog type primitive attribute being mapped. Next, it will also include between
brackets and separated by the character |, the names of the IEC-61850 scale range
configuration attributes (IEC-61850 attribute named rangeC) and the units of said analog
attribute in the IED (IEC-61850 attribute named units). As these two attributes are
optional in the IED, only the name of the attribute available in the IED will be configured.
In case neither of the two latter attributes are available in the IED, this parameter will not
appear in the configuration line for mapping the IEC-61850 analog type primitive attribute.

Ex: # phsA.cVal.mag.f
0,1,0,0,P,M,6,3,1.0,3,LD1/IRVAMMXU1.PhV.phsA[units|rangeC],

M1CPTA2005I
B-247 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

- Type ‘C’: the IEC-61850 primitive attribute being mapped represents a binary counter,
and hence it is mapped to 32 bit counter in the Central Unit.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , EtiqCON , IEDUnits , ScaleFactor , ClientUnits , ...

Multiplier Multiplier

… Data61850Ref [ConfAttrib61850Names] ,

(*)

(*) This field will always contain at least the pulse value configuration attribute (IEC-61850
attribute named pulsQty) as it is compulsory and will contain the configuration attribute of the
units of said counter attribute (IEC-61850 attribute named units), when the IEC-61850
composite data that contains the IEC-61850 counter type primitive attribute being mapped
includes it in the IED.

• MappingType: Mapping type ‘C’.

• EtiqCON: Identifier of the counter, within the Central Unit database, used for mapping the
IEC-61850 counter type primitive attribute.
• IEDUnitsMultiplier: Scale value (expressed as exponent in the power of 10) used by the
61850 IED to express the units of IEC-61850 counter type primitive attribute.
• ScaleFactor: Scale factor by which the values of the IEC-61850 counter type primitive
attribute are to be divided, within the Central Unit.
• ClientUnitsMultiplier: Scale value (expressed as exponent in the power of 10) used by the
Central Unit real time database, to express the units of the IEC-61850 counter type
primitive attribute.
• Data61850Ref[ConfAttrib61850Names]: Parameter composed of the 61850 reference of
the IEC-61850 composite data (including the Logic Device name) that contains the IEC-
61850 counter type primitive attribute being mapped. Next, it will also include between
brackets and separated by the character |, the names of the IEC-61850 pulse value
configuration attributes (IEC-61850 attribute named pulsQty) and the units of said
counter attribute in the IED (IEC-61850 attribute named units). The name of attribute
units will only be configured when it is available in the IED.

Ex: # actVal
0,P,C,11,3,1.0,6,LD1/INTMMTR1.DmdVArh[units|pulsQty],

M1CPTA2005I
1CPT: Substation Central Unit B-248
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

- Type ‘Q’: the IEC-61850 primitive attribute being mapped represents attribute q (Quality
type in IEC-61850) of an IEC-61850 composite data, hence it is mapped to the quality
data of Central Unit data resulting from the mapping of the IEC-61850 data primitive
attributes affected by attribute q.

Four subtypes are differentiated in the mapping of the primitive attribute q to the Central
Unit database as follows:

- Subtype ‘S’: the IEC-61850 primitive attribute being mapped represents the attribute q
of other Boolean type primitive attribute within the same IEC-61850 composite data.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , EtiqISC ,

• MappingType: Type of mapping ‘Q’.

• MappingSubType: Type of mapping ‘S’.
• EtiqISC: Identifier of the single digital signal used for mapping the IEC-61850
primitive attribute affected by attribute q, in the Central Unit database.

Ex: # q
1,P,Q,S,3,

- Subtype ‘MS’: the IEC-61850 primitive attribute being mapped represents the attribute
q of other primitive attribute that can take more than two states (previously mapped to
various single digital signals), belonging to the same IEC-61850 composite data. The
configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , NumISCs , ...

… EtiqISC_1 , EtiqISC_2 , ... EtiqISC_i ,

(*)

(*) It repeats for each of the single digital signals used for mapping, in the Central
Unit database, the possible states that can take the IEC-61850 primitive attribute
affected by attribute q. There will be as many as shown in NumISCs.

• MappingType: Type of mapping ‘Q’.

• MappingSubType: Type of mapping ‘MS’.
• NumISCs: Number of Central Unit database single digital signals used for mapping
the possible states of the IEC-61850 primitive attribute affected by attribute q.
• EtiqISC_i: Identifier of the single digital signal used for mapping one of the possible
states that can take the IEC-61850 primitive attribute affected by attribute q, within
the Central Unit database.

Ex: # q
1,P,Q,MS,5,241,242,243,244,245,

M1CPTA2005I
B-249 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

- Subtype ‘M’: the IEC-61850 primitive attribute being mapped represents the attribute q
of other analog type primitive attribute within the same IEC-61850 composite data.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , EtiqMEA ,

• MappingType: Type of mapping ‘Q’.

• MappingSubType: Type of mapping ‘M’.
• EtiqMEA: Identifier of the measurement used for mapping the IEC-61850 primitive
attribute affected by attribute q, within the Central Unit database.

Ex: # phsA.q
0,3,P,Q,M,10,

- Subtype ‘C’: the IEC-61850 primitive attribute being mapped represents the attribute q
of other Boolean type primitive attribute within the same IEC-61850 composite data.

The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , EtiqCON ,

• MappingType: Type of mapping ‘Q’.

• MappingSubType: Type of mapping ‘C’.
• EtiqCON: Identifier of the counter used for mapping the IEC-61850 primitive
attribute affected by attribute q, within the Central Unit database.

Ex: # q
1,P,Q,C,11,

• Type ‘T’: the IEC-61850 primitive attribute being mapped represents the attribute t
(TimeStamp type in IEC-61850) of an IEC-61850 composite data, hence, it is mapped to
the date and time of change data of the Central Unit data resulting from the mapping of
the IEC-61850 data primitive attributes affected by attribute t.

The mapping of the primitive attribute t, to the Central Unit database, two mapping
subtypes are differentiated:

- Subtype ‘S’: the IEC-61850 primitive attribute being mapped represents the attribute t
of other Boolean type primitive attribute within the same IEC-61850 composite data.
The configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , EtiqISC ,

M1CPTA2005I
1CPT: Substation Central Unit B-250
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• MappingType: Type of mapping ‘T’.

• MappingSubType: Type of mapping ‘S’.
• EtiqISC: Identifier of the single digital signal used for mapping the IEC-61850
primitive attribute affected by attribute t, within the Central Unit database.

Ex: # t
2,P,T,S,3,

- Subtype ‘MS’: the IEC-61850 primitive attribute being mapped represents the attribute
t of other primitive attribute that can take more than two states (previously mapped to
several single digital signals), belonging to the same IEC-61850 composite data. The
configuration line for this type of mapping is as follows:

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , …

… P , MappingType , MappingSubType , NumISCs , ...

… EtiqISC_1 , EtiqISC_2 , ... EtiqISC_i ,

(*)

(*) It repeats for each of the single digital signals used for mapping, in the Central
Unit database, the possible states that can take the IEC-61850 primitive attribute
affected by attribute t. There will be as many as shown in NumISCs.

• MappingType: Type of mapping ‘T’.

• MappingSubType: Type of mapping ‘MS’.
• NumISCs: Number of Central Unit database single digital signals used for mapping
the possible states of the IEC-61850 primitive attribute affected by attribute t.
• EtiqISC_i: Identifier of the single digital signal used for mapping one of the possible
states that can take the IEC-61850 primitive attribute affected by attribute t, within
the Central Unit database.

Ej: # t
2,P,T,MS,5,241,242,243,244,245,

M1CPTA2005I
B-251 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

Ex: # Configuration of the BUFFERED-REPORT-CONTROL-BLOCKS (BRCBs)

1,// Nº of BRCBs
# BRCB nº 1
# BRCB reference(from the LD)
LD1/LLN0.brcbUCS,
# seqNumber, ReportTimeStamp, ReasonforIncl, data-set-name,
# data-reference, DATA OVERFLOW, ENTRYID, conf-revision
1,1,1,0,0,1,1,0,
# TriggerOptions: datachg, qualitychg, dataupdate, Integrity
0,0,0,0,
# Buffer Time, Integrity Period, GI Enable,
0,0,0,+
# Ref. DataSet (from the LD), Total Nº of Dataset members
# (mapped and not mapped to Procome objects)
LD1/LLN0.dsUCS,26,
# Configuration of the FCDs/FCDAs constituting the Dataset and
# also mapped to Procome objects.
16,
#
# FCD/FCDA nº 1
# LD1/GENGGIO1.Alm03[ST] // Trip coil supervision Bd1
2,LD1/GENGGIO1.Alm03,3,
# stVal
0,P,S,2,
# q
1,P,Q,S,2,
# t
2,P,T,S,2,
# FCD/FCDA nº 2
# LD1/GENGGIO1.Alm04[ST] // Trip coil supervision Bd1
3,LD1/GENGGIO1.Alm04,3,
# stVal
0,P,S,3,
# q
1,P,Q,S,3,
# t
2,P,T,S,3,
. . . . . .
. . . . . .
# FCD/FCDA nº 20
# LD1/INTMMTR1.DmdVArh[ST] // INCOMING REACTIVE ENERGY
337,LD1/INTMMTR1.DmdVArh,3,
# actVal

0,P,C,11,3,1.0,6,LD1/INTMMTR1.DmdVArh[units|pulsQty],
# q
1,P,Q,C,11,
# t
2,P,T,C,11,

M1CPTA2005I
1CPT: Substation Central Unit B-252
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration of Unbuffered IED Report-Control-Blocks: [Lines 231-335]

In this section of the IED mapping file, the IED Unbuffered Report-Control-Blocks the IED
makes available to the Central Unit IEC-61850 Client are configured.

NumURCBs ,
URCBRef ,
SeqNumber , ReportTimeStamp , ReasonForInclusion , DatasetName , …

… DataRef , ConfRevision ,

DataChange , QualityChange , DataUpdate , Integrity ,

(*
BufferTime , IntegrityPeriod , bRefrescoCiclico ,
DatSetRef , NumTotDSMembers ,
NumMappedDSMembers ,
IndexDataSetMember , MemberRef , NumPrimitiveDAs ,

IdxDataInNestingLevel_1 , IdxDataInNestingLevel_2 , … IdxDataInNestingLevel_i , … (**)

… P , MappingType , Param_1 , Param_2 , … Param_i , (***)

(*) It repeats for each Unbuffered Report-Control-Block the IED makes available to the Central
Unit IEC-61850 Client. There will be as many as shown in NumURCBs.
(**) It repeats for each mapped dataset member associated to a Report-Control-Block. There
will be as many as shown in NumMappedDSMembers.
(***)It repeats for each primitive attribute of the dataset member being mapped. There will be as
many lines as shown in NumPrimitiveDAs.

• NumURCBs: Number of Unbuffered Report-Control-Blocks the IED makes available to

the Central Unit IEC-61850 Client.
• URCBRef: IEC-61850 reference of the Report-Control-Block (including the Logic Device).
• SeqNumber: Allows enable (value 1) or disable (value 0) the inclusion of the sequence
number (attribute SqNum or SubSqNum) in the IED generated Reports for the Report-
Control-Block.
• ReportTimeStamp: Allows enable (value 1) or disable (value 0) the inclusion in the
Reports of the time and date at which every IED generated Report is created (attribute
TimeOfEntry) for the Report-Control-Block.
• ReasonForInclusion: Allows enable (value 1) or disable (value 0) the inclusion in the
Reports of the cause (attribute ReasonCode) whereby all data constituting the IED
generated Reports for the Report-Control-Block are included.
• DatasetName: Allows enable (value 1) or disable (value 0) the inclusion of the name of
the dataset in the IED generated Reports for the Report-Control-Block.
• DataRef: Allows enable (value 1) or disable (value 0) the inclusion of the MMS reference
of all data constituting the IED generated Reports for the Report-Control-Block.
• ConfRevision: Allows enable (value 1) or disable (value 0) the inclusion in the Reports of
the attribute that contains the number of times the configuration of the dataset associated
to the IED Report-Control-Block has been modified.
• DataChange: Allows enable (value 1) checking the changes of data constituting the
dataset associated to the Report-Control-Block, as a requirement for generating Reports.
The value 0 will not change in the IED the requirement for generating Reports by data-
change for the Report-Control-Block.
Note: The Central Unit IEC-61850 Client automatically activates the Requirement for
generating Reports by general-interrogation for the Report-Control-Block.

M1CPTA2005I
B-253 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

• QualityChange: Allows enable (value 1) checking the changes of the quality of data
constituting the dataset associated to the Report-Control-Block, as a requirement for
generating Reports. The value 0 will not change in the IED the requirement for generating
Reports by quality-change for the Report-Control-Block.
• DataUpdate: Allows enable (value 1) checking the updating of data constituting the
dataset associated to Report-Control-Block, as requirement for generating Reports. The
value 0 will not change in the IED the requirement for generating Reports by data-update
for the Report-Control-Block.
• Integrity: Allows enable (value 1) checking in the IED the end of a refresh period of data
constituting the dataset associated to the Report-Control-Block, as a requirement for
generating Reports. The value 0 will not change in the IED the requirement for generating
Reports by integrity for the Report-Control-Block.
Note: The value 0 for the set of the four parameters DataChange, QualityChange,
DataUpdate e Integrity implies not to change the value of the attribute TrgOps in
the IED Report-Control-Block.
• BufferTime: Value (in millisec.) to be configured in the Report-Control-Block to establish
the duration of the time interval elapsed from the instant the first requirement for
generating new Reports is detected until this is finally sent by the IED. The value 0
implies the value of the attribute BufTm in the IED Report-Control-Block is not modified.
• IntegrityPeriod: Value (in millisec.) to be configured in the Report-Control-Block as time
interval for generating Reports periodically, for which it will be necessary that the Report-
Control-Block has the requirement for generating Reports by integrity activated. The
minimum configurable value in the Central Unit for this parameter will be 1500
milliseconds. The value 0 implies not to modify the value of the attribute IntgPd in the IED
Report-Control-Block.
• bRefrescoCiclico: Enables the Central Unit function for general cyclic interrogation of the
IED Report-Control-Block (when the associated dataset contains measurements or
meters), the period of Reports request by general-interrogation being the value
configured for parameter PerioLectMed in file CENTRAL.CFG (chapter A.2 in the CPT
manual).
• DatSetRef: IEC-61850 reference of the dataset associated to the Report-Control-Block
that appears in the IED CID file (including the Logic Device). The Central Unit IEC-61850
Client, upon establishing the association with the IED, checks the match between the
dataset configured in the IED and the dataset configured in the CID for the same Report-
Control-Block.
• NumTotDSMembers: Total number of members constituting the dataset associated to the
Report-Control-Block (mapped and not mapped to the Central Unit real time database)
appearing in IED CID file. The Central Unit IEC-61850 Client, upon establishing the
association with the IED, checks this data in the dataset configured in the IED matches
the same data in the dataset configured in the CID for the same Report-Control-Block.
• NumMappedDSMembers: Index (starting at zero) within the dataset of the member to be
mapped to the Central Unit real time database.
• IndexDatasetMember: Index (starting at zero) within the dataset of the member to be
mapped to the Central Unit real time database.
• MemberRef: Is the IEC-61850 reference of the dataset member (including the Logic
Device).
• NumPrimitiveDAs: Number of primitive attributes (they match basic IEC-61850 data)
constituting the dataset member to be mapped to the Central Unit real time database.

M1CPTA2005I
1CPT: Substation Central Unit B-254
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• IdxDataInNestingLevel_i: Index sequence (starting at zero from the nesting level

immediately under the data specified in the dataset) of the components within each
nesting level of the structure of the dataset member IEC-61850 data, which set up the
path (applying the functional constraint filter associated to the dataset member data)
within the data structure to reach the primitive attribute (basic data) that is to be mapped
to the Central Unit real time database. The end of the index sequence of a data primitive
attribute will be tagged with character ‘P’.
• P: Character ‘P’ that indicates the end of the sequence of indices that set up the path to
reach the primitive attribute of the dataset member data.
• MappingType: Type of mapping assigned to the primitive attribute of the dataset member
data, to be included within the Central Unit real time database.
• Param_i: Sequence of parameters that define completely the mapping of the primitive
attribute of the dataset member data, within the Central Unit real time database.

As mentioned above, for each dataset member associated to the Report-Control-Block the
required data must be configured for its mapping within the Central Unit internal database. The
mapping data to be included, for each dataset member, is described in the previous section
dedicated to Buffered type Report-Control-Blocks.

M1CPTA2005I
B-255 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

Ex: # Configuration of the UNBUFFERED-REPORT-CONTROL-BLOCKS

(URCBs)
1, // Nº of URCBs
# URCB nº 1
# URCB reference(from the LD)
LD1/LLN0.urcbUCS_ME,
# seqNumber, ReportTimeStamp, ReasonforInclusion, DatasetName,
# data-reference, conf-revision
1,1,1,0,0,0,
# TriggerOptions: datachg, qualitychg, dataupdate, Integrity
0,0,0,0,
# Buffer Time, Integrity Period, GI Enable,
0,0,0,
# Dataset reference(from the LD), Nº of Dataset members
# mapped and not mapped to Procome objects)
LD1/LLN0.dsUCSmeasurements,8,
# Configuration of the FCDs/FCDAs constituting the Dataset and
# also mapped to Procome objects.
8,
#
# FCD/FCDA nº 1
# LD1/TGOGGIO1.AnIn1[MX] // Active power 132 kV
0,LD1/TGOGGIO1.AnIn1,2,
# mag.f
1,0,P,M,0,-3,1.0,0,LD1/TGOGGIO1.AnIn1[units|rangeC],
# q
3,P,Q,M,0,
# FCD/FCDA nº 2
# LD1/TGOGGIO1.AnIn2[MX] // Reactive power 132 kV
1,LD1/TGOGGIO1.AnIn2,2,
# mag.f
1,0,P,M,1,-3,1.0,0,LD1/TGOGGIO1.AnIn2[units|rangeC],
# q
3,P,Q,M,1,
. . . . . .
. . . . . .
# FCD/FCDA nº 8
# LD1/IRVRFLO1.FltDiskm[MX] // DISTANCE TO FAULT (IN KM)
7,LD1/IRVRFLO1.FltDiskm,2,
# mag.f
1,0,P,M,14,3,1.0,0,LD1/IRVRFLO1.FltDiskm[units|rangeC],
# q
3,P,Q,M,14,

M1CPTA2005I
1CPT: Substation Central Unit B-256
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration of Commands to IEDs: [Lines 338-363]

The configuration section of commands to IED executed from the Central Unit, starts with a line
in which the number of commands to the IED to be configured is specified.
Then, a configuration line for each controllable IEC-61850 data of the IED to be controlled from
the Central Unit will be included that allows its mapping to commands of the logic device that
represents said 61850 IED within the Central Unit internal database. For each controllable
IEC-61850 data, up to three pairs of equivalent commands (activation command and
deactivation command) can be assigned, within the Central Unit, so that each command pair
will be associated to a different IEC-61850 origin for command execution.

NumControlData ,
ControlDataRef , ControlDataClass , ControlService , HMI_MandoOFF , HMI_MandoON ,

Telem_MandoOFF , Telem_MandoON , Autom_MandoOFF , Autom_MandoON ,

Check , ControlModel , sboTimeout , sboClass , (*)

(*) It repeats for each controllable IEC-61850 data of the IED that must be controlled from the
Central Unit. There will be as many as shown in NumControlData.

• NumControlData: Number of controllable IEC-61850 data of the IED to be mapped to

internal commands within the Central Unit database.
• ControlDataRef: Is the IEC-61850 reference of the controllable data (including the Logic
Device).
• ControlDataClass: IEC-61850 Common Data Class from which the controllable data is
derived. The following classes of controllable IEC-61850 data are supported by the
Central Unit: SPC, DPC, BSC and APC.
• ControlService: Type of IEC-61850 control service to be used to execute the command to
the IED controllable data. Presently, only the service Operate (type 1) is supported by the
Central Unit.
• HMI_MandoOFF: Index of the Central Unit database command linked to the deactivation
(switch to OFF) of the controllable IEC-61850 data of the IED from the Local Operation
HMI (IEC-61850 origin station-control). The value –1 will be used when Central Unit
command is not to be associated.
• HMI_MandoON: Index of the Central Unit database command linked to the activation
(switch to ON) of the controllable IEC-61850 data of the IED from the Local Operation
HMI (IEC-61850 origin station-control). The value –1 will be used when Central Unit
command is not to be associated.
• Telem_MandoOFF: Index of the Central Unit database command linked to the
deactivation (switch to OFF) of the controllable IEC-61850 data of the IED from the
Remote Control (IEC-61850 origin remote-control). The value –1 will be used when
Central Unit command is not to be associated.
• Telem_MandoON: Index of the Central Unit database command linked to the activation
(switch to ON) of the controllable IEC-61850 data of the IED from the Remote Control
(IEC-61850 origin remote-control). The value –1 will be used when Central Unit command
is not to be associated.
• Autom_MandoOFF: Index of the Central Unit database command linked to the
deactivation (switch to OFF) of the controllable IEC-61850 data of the IED from a CPT
Control Function (IEC-61850 origin automatic-station). The value –1 will be used when
Central Unit command is not to be associated.
• Autom_MandoON: Index of the Central Unit database command linked to the activation
(switch to ON) of the controllable IEC-61850 data of the IED from a CPT Control Function
(IEC-61850 origin automatic-station). The value –1 will be used when Central Unit
command is not to be associated.

M1CPTA2005I
B-257 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Check: Specifies the requirements for the controllable IEC-61850 data check by the IED
prior to the execution of the command received. Accepted values are:
o 0: no check requirements are applied.
o 1: Synchronism requirement is checked (synchrocheck).
o 2: Interlock requirement is checked (interlock-check).
• ControlModel: Type of control mode used for IED controllable IEC-61850 data. Accepted
values are:
o 1: Direct control with normal security
o 3: Direct control with enhanced security
• SboTimeout: Maximum time (in msec.) the selected controllable IEC-61850 data will
remain after the IED receives the Select service (not yet available for 1CPT models).
• SboClass: Allows select the type of execution of the Select-Before-Operate control
service (not yet available for CPT models). Accepted values are:
o 0: Operate-once
o 1: Operate-many

Note: In case of commands for raising or lowering taps and set points (BSC class controllable IEC-61850 data)
activation commands (HMI_MandoON, Telem_MandoON and Autom_MandoON) will allow raising the tap and
the set point. Deactivation commands (HMI_MandoOFF, Telem_MandoOFF and Autom_MandoOFF) will allow
lowering the tap and the set point.
Note: Analog commands (APC class controllable IEC-61850 data) will be mapped to analog output writes within
the Central Unit database, so that it will only be necessary to configure the parameters for activation
commands (HMI_MandoON, Telem_MandoON and Autom_MandoON).

Ex: # Configuration of DATA-CONTROL

# Nº of Commands
12,
# Controllable object,CDC ...
# OPEN / CLOSE BREAKER FROM PANEL/REMOTE CONTROL
LD1/CSWI1.Pos,DPC,1,02,05,03,06,-1,-1,0,3,0,0,
# REMOVE/SET LOCKOUT/TAGOUT FROM PANEL
LD1/CSWI2.Pos,DPC,1,08,09,-1,-1,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-1 FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI3.Pos,DPC,1,14,17,15,18,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-1T FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI4.Pos,DPC,1,20,23,21,24,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-2 FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI5.Pos,DPC,1,26,29,27,30,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-2T FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI6.Pos,DPC,1,32,35,33,36,-1,-1,0,3,0,0,
# SET TO AUTOMATIC/MANUAL FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI7.Pos,DPC,1,10,12,11,13,-1,-1,0,3,0,0,
# SWITCH TO LOCAL/SWITCH TO REMOTE CONTROL FROM PANEL
LD1/CSWI8.Pos,DPC,1,00,01,-1,-1,58,59,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-3 FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI9.Pos,DPC,1,38,41,39,42,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-3T FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI10.Pos,DPC,1,44,47,45,48,-1,-1,0,3,0,0,
# OPEN/CLOSE SECTIONALIZER 89-1-4T FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI11.Pos,DPC,1,50,53,51,54,-1,-1,0,3,0,0,
# RESET CONTROL FUNCTION RFTL FROM PANEL/FROM REMOTE CONTROL
LD1/CSWI12.Pos,DPC,1,55,-1,56,-1,-1,-1,0,3,0,0,

M1CPTA2005I
1CPT: Substation Central Unit B-258
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # File CONDEQ01I01_r03.cid

[2] # Client file for UCS
[3] # SUBSTATION: CONDOMINA
[4] ########################################################################
###
[5] #
#
[6] # 61850 DEVICE CONDEQ01I01 ; ZIV MCAD
#
[7] #
#
[8] # ISCs=473 MEAs=15 CONs=12
#
[9] #
#
[10] # version="2" revision="7"
#
[11] #
#
[12] # LD="LD1" configRev="2007.03.21.15:00:00"
paramRev="2007.03.21.15:00:00" #
[13] #
#
[14] ########################################################################
###
[15] # IED configuration:
[16] # IED Name, Device address in BD UCS, NivelTraza, NombresLDs(,..,),
[17] CONDEQ01I01,5,0,LD1,
[18] # IP address, Subnet, Gateway, osi_tsel, osi_ssel, osi_psel
[19] 10.193.60.5,255.255.255.0,172.16.1.254,0001,0001,00000001,
[20] # LocalDetail, ServicesCalling, ServicesCalled, NestLevel, VersNumber
[21] 32717,6,6,5,1,
[22] # ServicesSup, ParamCBBs, TransportType, MMSStackType,
BitClockNotSynchEnable
[23] 7738001c2000000080f71800,8700,tcp,full,0,
[24] false,520301,ziv,// AUTH_enabled, AUTH_mechanism, AUTH_password
[25] #
[26] # Configuration of BUFFERED-REPORT-CONTROL-BLOCKS (BRCBs)
[27] 1,// Nº of BRCBs
[28] # BRCB nº 1
[29] # BRCB reference (from the LD)
[30] LD1/LLN0.brcbUCS,
[31] # sequence-number, report-time-stamp, reason-for-inclusion, data-set-
name,
[32] # data-reference, DATA OVERFLOW, ENTRYID, conf-revision
[33] 1,1,1,0,0,1,1,0,
[34] # Trigger Options: data-change, quality-change, data-update, Integrity
[35] 0,0,0,0,
[36] # Buffer Time, Integrity Period, GI Enable,
[37] 0,0,0,+
[38] # Dataset reference (from the LD), Total Nº of Dataset members
[39] # (mapped and not mapped to Procome objects)
[40] LD1/LLN0.dsUCS,26,
[41] # Configuration of the FCDs/FCDAs constituting the Dataset and
furthermore
[42] # mapped to Procome objects.

M1CPTA2005I
B-259 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[43] 16,
[44] #
[45] # FCD/FCDA nº 1
[46] # LD1/GENGGIO1.Alm03[ST] // Trip coil supervision Bd1
[47] 2,LD1/GENGGIO1.Alm03,3,
[48] # stVal
[49] 0,P,S,2,
[50] # q
[51] 1,P,Q,S,2,
[52] # t
[53] 2,P,T,S,2,
[54] # FCD/FCDA nº 2
[55] # LD1/GENGGIO1.Alm04[ST] // Trip coil supervision Bd1
[56] 3,LD1/GENGGIO1.Alm04,3,
[57] # stVal
[58] 0,P,S,3,
[59] # q
[60] 1,P,Q,S,3,
[61] # t
[62] 2,P,T,S,3,
[63] # FCD/FCDA nº 3
[64] # LD1/GENGGIO1.Alm09[ST] // Breaker 52-1 closed
[65] 8,LD1/GENGGIO1.Alm09,3,
[66] # stVal
[67] 0,P,S,8,
[68] # q
[69] 1,P,Q,S,8,
[70] # t
[71] 2,P,T,S,8,
[72] # FCD/FCDA nº 4
[73] # LD1/GENGGIO1.Alm10[ST] // Breaker 52-1 open
[74] 9,LD1/GENGGIO1.Alm10,3,
[75] # stVal
[76] 0,P,S,9,
[77] # q
[78] 1,P,Q,S,9,
[79] # t
[80] 2,P,T,S,9,
[81] # FCD/FCDA nº 5
[82] # LD1/TGOGGIO1.SPCSO09[ST] // Open command 52-1 Bd1
[83] 10,LD1/TGOGGIO1.SPCSO09,3,
[84] # stVal
[85] 0,P,S,88,
[86] # q
[87] 1,P,Q,S,88,
[88] # t
[89] 2,P,T,S,88,
[90] # FCD/FCDA nº 6
[91] # LD1/TGOGGIO1.SPCSO10[ST] // Close command 52-1
[92] 11,LD1/TGOGGIO1.SPCSO10,3,
[93] # stVal
[94] 0,P,S,89,
[95] # q
[96] 1,P,Q,S,89,
[97] # t
[98] 2,P,T,S,89,
[99] # FCD/FCDA nº 7
[100] # LD1/CSWI1.OKOpn[ST] // OPEN COMMAND EXECUTED NO/YES

M1CPTA2005I
1CPT: Substation Central Unit B-260
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[101] 12,LD1/CSWI1.OKOpn,3,
[102] # general
[103] 0,P,ST,234,
[104] # q
[105] 1,P,Q,S,234,
[106] # t
[107] 2,P,T,S,234,
[108] # FCD/FCDA nº 8
[109] # LD1/CSWI1.OKCls[ST] // CLOSE COMMAND EXECUTED NO/YES
[110] 13,LD1/CSWI1.OKCls,3,
[111] # general
[112] 0,P,ST,235,
[113] # q
[114] 1,P,Q,S,235,
[115] # t
[116] 2,P,T,S,235,
[117] # FCD/FCDA nº 9
[118] # LD1/CSWI1.FailOpn[ST] // OPEN COMMAND FAILURE NORMAL/ALARM
[119] 14,LD1/CSWI1.FailOpn,3,
[120] # general
[121] 0,P,ST,236,
[122] # q
[123] 1,P,Q,S,236,
[124] # t
[125] 2,P,T,S,236,
[126] # FCD/FCDA nº 10
[127] # LD1/CSWI1.FailCls[ST] // CLOSE COMMAND FAILURE NORMAL/ALARM
[128] 15,LD1/CSWI1.FailCls,3,
[129] # general
[130] 0,P,ST,237,
[131] # q
[132] 1,P,Q,S,237,
[133] # t
[134] 2,P,T,S,237,
[135] # FCD/FCDA nº 11
[136] # LD1/CSWI2.Pos[ST] // BREAKER WITHOUT LO-TO/WITH LO-TO
[137] 16,LD1/CSWI2.Pos,3,
[138] # stVal
[139] 0,P,MS,4,0,238,1,239,2,240,3,238,
[140] # q
[141] 1,P,Q,MS,3,238,239,240,
[142] # t
[143] 2,P,T,MS,3,238,239,240,
[144] # FCD/FCDA nº 12
[145] # LD1/CSWI2.OpOpnOr[ST] // COMMAND TO REMOVE LO-TO
[146] 17,LD1/CSWI2.OpOpnOr,4,
[147] # general
[148] 0,P,ST,241,
[149] # q
[150] 1,P,Q,MS,5,241,242,243,244,245,
[151] # t
[152] 2,P,T,MS,5,241,242,243,244,245,
[153] # origin.orCat
[154] 3,0,P,OT,241,4,1,242,2,243,3,244,4,245,
[155] # FCD/FCDA nº 13
[156] # LD1/CSWI2.OpClsOr[ST] // COMMAND TO SET LO-TO
[157] 18,LD1/CSWI2.OpClsOr,4,

M1CPTA2005I
B-261 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[158] # general
[159] 0,P,ST,246,
[160] # q
[161] 1,P,Q,MS,5,246,247,248,249,250,
[162] # t
[163] 2,P,T,MS,5,246,247,248,249,250,
[164] # origin.orCat
[165] 3,0,P,OT,246,4,1,247,2,248,3,249,4,250,
[166] # FCD/FCDA nº 14
[167] # LD1/CSWI2.OKCls[ST] // COMMAND TO SET LO-TO EXECUTED NO/YES
[168] 19,LD1/CSWI2.OKCls,3,
[169] # general
[170] 0,P,ST,251,
[171] # q
[172] 1,P,Q,S,251,
[173] # t
[174] 2,P,T,S,251,
[175] # FCD/FCDA nº 15
[176] # LD1/CSWI2.OKOpn[ST] // COMMAND TO REMOVE LO-TO EXECUTED NO/YES
[177] 20,LD1/CSWI2.OKOpn,3,
[178] # general
[179] 0,P,ST,252,
[180] # q
[181] 1,P,Q,S,252,
[182] # t
[183] 2,P,T,S,252,
[184] # FCD/FCDA nº 16
[185] # LD1/CSWI2.FailCls[ST] // FAILED COMMAND TO SET LO-TO NORMAL/ALARM
[186] 21,LD1/CSWI2.FailCls,3,
[187] # general
[188] 0,P,ST,253,
[189] # q
[190] 1,P,Q,S,253,
[191] # t
[192] 2,P,T,S,253,
[193] # FCD/FCDA nº 17
[194] # LD1/INTMMTR1.SupWh[ST] // OUTGOING ACTIVE ENERGY
[195] 22,LD1/INTMMTR1.SupWh,3,
[196] # actVal
[197] 0,P,C,8,3,1.0,6,LD1/INTMMTR1.SupWh[units|pulsQty],
[198] # q
[199] 1,P,Q,C,8,
[200] # t
[201] 2,P,T,C,8,
[202] # FCD/FCDA nº 18
[203] # LD1/INTMMTR1.SupVArh[ST] // OUTGOING REACTIVE ENERGY
[204] 23,LD1/INTMMTR1.SupVArh,3,
[205] # actVal
[206] 0,P,C,9,3,1.0,6,LD1/INTMMTR1.SupVArh[units|pulsQty],
[207] # q
[208] 1,P,Q,C,9,
[209] # t
[210] 2,P,T,C,9,
[211] # FCD/FCDA nº 19
[212] # LD1/INTMMTR1.DmdWh[ST] // INCOMING ACTIVE ENERGY
[213] 24,LD1/INTMMTR1.DmdWh,3,
[214] # actVal
[215] 0,P,C,10,3,1.0,6,LD1/INTMMTR1.DmdWh[units|pulsQty],

M1CPTA2005I
1CPT: Substation Central Unit B-262
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[216] # q
[217] 1,P,Q,C,10,
[218] # t
[219] 2,P,T,C,10,
[220] # FCD/FCDA nº 20
[221] # LD1/INTMMTR1.DmdVArh[ST] // INCOMING REACTIVE ENERGY
[222] 337,LD1/INTMMTR1.DmdVArh,3,
[223] # actVal
[224] 0,P,C,11,3,1.0,6,LD1/INTMMTR1.DmdVArh[units|pulsQty],
[225] # q
[226] 1,P,Q,C,11,
[227] # t
[228] 2,P,T,C,11,
[229] #
[230] # Configuration of the UNBUFFERED-REPORT-CONTROL-BLOCKS (URCBs)
[231] 1,// Nº de URCBs
[232] # URCB nº 1
[233] # URCB reference(from the LD)
[234] LD1/LLN0.urcbUCS_ME,
[235] # sequence-number, report-time-stamp, reason-for-inclusion, data-set-
name,
[236] # data-reference, conf-revision
[237] 1,1,1,0,0,0,
[238] # Trigger Options: data-change, quality-change, data-update, Integrity
[239] 0,0,0,0,
[240] # Buffer Time, Integrity Period, GI Enable,
[241] 0,0,0,
[242] # Dataset reference (from the LD), Total Nº of Dataset members
[243] # (mapped and not mapped to Procome objects)
[244] LD1/LLN0.dsUCSmeasurements,8,
[245] # Configuration of the FCDs/FCDAs constituting the Dataset and
furthermore
[246] # mapped to a Procome objects.
[247] 8,
[248] # Nº Data in DATASET, Type of mapping, Index MEA Procome,
UnitsMultiplier,
[249] # scaleFactor, Offset,
[250] #
[251] #
[252] # FCD/FCDA nº 1
[253] # LD1/TGOGGIO1.AnIn1[MX] // Active power 132 kV
[254] 0,LD1/TGOGGIO1.AnIn1,2,
[255] # mag.f
[256] 1,0,P,M,0,-3,1.0,0,LD1/TGOGGIO1.AnIn1[units|rangeC],
[257] # q
[258] 3,P,Q,M,0,
[259] # FCD/FCDA nº 2
[260] # LD1/TGOGGIO1.AnIn2[MX] // Reactive power 132 kV
[261] 1,LD1/TGOGGIO1.AnIn2,2,
[262] # mag.f
[263] 1,0,P,M,1,-3,1.0,0,LD1/TGOGGIO1.AnIn2[units|rangeC],
[264] # q
[265] 3,P,Q,M,1,
[266] # FCD/FCDA nº 3
[267] # LD1/IRVAMMXU1.TotVAr[MX] // MEASUREMENT OF REACTIVE POWER (Q)
[268] 2,LD1/IRVAMMXU1.TotVAr,2,
[269] # mag.f
[270] 1,0,P,M,2,6,1.0,6,LD1/IRVAMMXU1.TotVAr[units|rangeC],

M1CPTA2005I
B-263 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[271] # q
[272] 3,P,Q,M,2,
[273] # FCD/FCDA nº 4
[274] # LD1/IRVAMMXU1.PPV[MX]
[275] 3,LD1/IRVAMMXU1.PPV,6,
[276] # phsAB.cVal.mag.f
[277] 0,1,0,0,P,M,3,3,1.0,3,LD1/IRVAMMXU1.PPV.phsAB[units|rangeC],
[278] # phsAB.q
[279] 0,3,P,Q,M,3,
[280] # phsBC.cVal.mag.f
[281] 1,1,0,0,P,M,4,3,1.0,3,LD1/IRVAMMXU1.PPV.phsBC[units|rangeC],
[282] # phsBC.q
[283] 1,3,P,Q,M,4,
[284] # phsCA.cVal.mag.f
[285] 2,1,0,0,P,M,5,3,1.0,3,LD1/IRVAMMXU1.PPV.phsCA[units|rangeC],
[286] # phsCA.q
[287] 2,3,P,Q,M,5,
[288] # FCD/FCDA nº 5
[289] # LD1/IRVAMMXU1.PhV[MX]
[290] 4,LD1/IRVAMMXU1.PhV,8,
[291] # phsA.cVal.mag.f
[292] 0,1,0,0,P,M,6,3,1.0,3,LD1/IRVAMMXU1.PhV.phsA[units|rangeC],
[293] # phsA.q
[294] 0,3,P,Q,M,6,
[295] # phsB.cVal.mag.f
[296] 1,1,0,0,P,M,7,3,1.0,3,LD1/IRVAMMXU1.PhV.phsB[units|rangeC],
[297] # phsB.q
[298] 1,3,P,Q,M,7,
[299] # phsC.cVal.mag.f
[300] 2,1,0,0,P,M,8,3,1.0,3,LD1/IRVAMMXU1.PhV.phsC[units|rangeC],
[301] # phsC.q
[302] 2,3,P,Q,M,8,
[303] # neut.cVal.mag.f
[304] 3,1,0,0,P,M,9,0,1.0,3,LD1/IRVAMMXU1.PhV.neut[units|rangeC],
[305] # neut.q
[306] 3,3,P,Q,M,9,
[307] # FCD/FCDA nº 6
[308] # LD1/IRVAMMXU1.A[MX]
[309] 5,LD1/IRVAMMXU1.A,6,
[310] # phsA.cVal.mag.f
[311] 0,1,0,0,P,M,10,0,1.0,0,LD1/IRVAMMXU1.A.phsA[units|rangeC],
[312] # phsA.q
[313] 0,3,P,Q,M,10,
[314] # phsB.cVal.mag.f
[315] 1,1,0,0,P,M,11,0,1.0,0,LD1/IRVAMMXU1.A.phsB[units|rangeC],
[316] # phsB.q
[317] 1,3,P,Q,M,11,
[318] # phsC.cVal.mag.f
[319] 2,1,0,0,P,M,12,0,1.0,0,LD1/IRVAMMXU1.A.phsC[units|rangeC],
[320] # phsC.q
[321] 2,3,P,Q,M,12,
[322] # FCD/FCDA nº 7
[323] # LD1/IRVRFLO1.FltDispct[MX] // MEASUREMENT OF DISTANCE TO FAULT (IN %)
[324] 6,LD1/IRVRFLO1.FltDispct,2,
[325] # mag.f
[326] 1,0,P,M,13,0,1.0,0,LD1/IRVRFLO1.FltDispct[units|rangeC],
[327] # q
[328] 3,P,Q,M,13,

M1CPTA2005I
1CPT: Substation Central Unit B-264
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[329] # FCD/FCDA nº 8
[330] # LD1/IRVRFLO1.FltDiskm[MX] // MEASUREMENT OF DISTANCE TO FAULT (IN KM)
[331] 7,LD1/IRVRFLO1.FltDiskm,2,
[332] # mag.f
[333] 1,0,P,M,14,3,1.0,0,LD1/IRVRFLO1.FltDiskm[units|rangeC],
[334] # q
[335] 3,P,Q,M,14,
[336] # Configuration of the DATA-CONTROL
[337] # Nº of Commands
[338] 12,
[339] # Controllable object,CDC ...
[340] # OPEN/CLOSE BREAKER FROM PANEL/FROM REMOTE CONTROL
[341] LD1/CSWI1.Pos,DPC,1,02,05,03,06,-1,-1,0,3,0,0,
[342] # REMOVE/SET BREAKER LO-TO FROM PANEL
[343] LD1/CSWI2.Pos,DPC,1,08,09,-1,-1,-1,-1,0,3,0,0,
[344] # OPEN/CLOSE SECTIONALIZER 89-1-1 FROM PANEL/FROM REMOTE CONTROL
[345] LD1/CSWI3.Pos,DPC,1,14,17,15,18,-1,-1,0,3,0,0,
[346] # OPEN/CLOSE SECTIONALIZER 89-1-1T FROM PANEL/FROM REMOTE CONTROL
[347] LD1/CSWI4.Pos,DPC,1,20,23,21,24,-1,-1,0,3,0,0,
[348] # OPEN/CLOSE SECTIONALIZER 89-1-2 FROM PANEL/FROM REMOTE CONTROL
[349] LD1/CSWI5.Pos,DPC,1,26,29,27,30,-1,-1,0,3,0,0,
[350] # OPEN/CLOSE SECTIONALIZER 89-1-2T FROM PANEL/FROM REMOTE CONTROL
[351] LD1/CSWI6.Pos,DPC,1,32,35,33,36,-1,-1,0,3,0,0,
[352] # SET TO AUTOMATIC/MANUAL FROM PANEL/FROM REMOTE CONTROL
[353] LD1/CSWI7.Pos,DPC,1,10,12,11,13,-1,-1,0,3,0,0,
[354] # SWITCH TO LOCAL/SWITCH TO REMOTE CONTROL FROM PANEL
[355] LD1/CSWI8.Pos,DPC,1,00,01,-1,-1,58,59,0,3,0,0,
[356] # OPEN/CLOSE SECTIONALIZER 89-1-3 FROM PANEL/FROM REMOTE CONTROL
[357] LD1/CSWI9.Pos,DPC,1,38,41,39,42,-1,-1,0,3,0,0,
[358] # OPEN/CLOSE SECTIONALIZER 89-1-3T FROM PANEL/FROM REMOTE CONTROL
[359] LD1/CSWI10.Pos,DPC,1,44,47,45,48,-1,-1,0,3,0,0,
[360] # OPEN/CLOSE SECTIONALIZER 89-1-4T FROM PANEL/FROM REMOTE CONTROL
[361] LD1/CSWI11.Pos,DPC,1,50,53,51,54,-1,-1,0,3,0,0,
[362] # RESET CONTROL FUNCTION RFTL FROM PANEL/FROM REMOTE CONTROL
[363] LD1/CSWI12.Pos,DPC,1,55,-1,56,-1,-1,-1,0,3,0,0,

M1CPTA2005I
B-265 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.17.3 Configuration of Central Unit IEC-61850 Server

The Central Unit can operate as IEC-61850 server, and the server configuration file (file
“61850SRV.CFG”) must exist to activate this function, so that if the CPT does not incorporate
this file, the Central Unit IEC-61850 server will remain disabled.

Presently, the IEC-61850 server function implemented by the Central Unit is limited to the
following aspects:

- It consists of a single Logic Device (LD = Logical Device).

- It includes the following IEC-61850 elements:

 Logic node instances (LN = Logical Node):

o Instance GENGGIO1 of logic node GENGGIO (general instructions).
o Instance TGO3GGIO1 of logic node TGO3GGIO (contains data to be
transmitted by the outgoing GOOSE).
 Buffered type Report-Control-Blocks:
o brcbCLI: Associated with dataset dsUCS1.
o brcbCLI2: Associated with dataset dsUCS1.
 UnBuffered type Report-Control-Blocks:
o urcbCLI: Associated with dataset dsUCS1.
o urcbCLI2: Associated with dataset dsUCS1.
 Goose-Control-Blocks:
o gcGOOSE1: Associated with dataset dsGOOSE1.
o gcGOOSE2: Associated with dataset dsGOOSE2 t.
o gcGOOSE3: Associated with dataset dsGOOSE3.
 Datasets:
o dsUCS1: Consists of 32 alarms (Alm01 to Alm32) and 32 indications of
node GENGGIO1 (Ind01 to Ind32).
o dsGOOSE1: Consists of 16 indications of node TGO3GGIO1 (Ind01 to
Ind16).
o dsGOOSE2: Consists of 8 indications of node TGO3GGIO1 (Ind01 to
Ind08).
o dsGOOSE3: Consists of 32 indications of node TGO3GGIO1 (Ind01 to
Ind32).

- It can handle GOOSE messages, the configuration of which is recorded in file

“IECGOOSE.INI”:

 It can generate three output GOOSE messages that will be associated to Goose-
Control-Block gcGOOSE1, gcGOOSE2 and gcGOOSE3. data sent by these
output GOOSE are pairs of IEC-61850 attributes stVal (status) and q (quality)
corresponding to data Ind01 to Ind16 for gcGOOSE1, data Ind01 to Ind08 for
gcGOOSE2 and data Ind01 to Ind32 for gcGOOSE3 of the logic node
TGO3GGIO1, which are single digital indications (Boolean type). The allocation of
data Ind01 to Ind32 to digital signals of the real time database of the Central Unit is
carried out in the “61850SRV.CFG” configuration file.

M1CPTA2005I
1CPT: Substation Central Unit B-266
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

 It can process a maximum of 10 Incoming GOOSE messages of other IEC-61850

IEDs. The Central Unit may only process data contained in the Incoming GOOSE
messages that are pairs of attributes stVal (state) and q (quality), corresponding to
indications of single digital states (Boolean type). Data of each Incoming GOOSE
message to be processed will be mapped, in file “61850SRV.CFG”, to single
digital signals of the logic device that represents the Central Unit IEC-61850
server module, whose address in the Central Unit database is 288 (as reflected in
file “PROTASK.CFG” for the activation of the Central Unit function modules).

The first 10 digital signals (0 to 9) of the logic device that represents the Central
Unit IEC-61850 server module, are reserved to indicate whether the Incoming
GOOSE messages configured (from 1 to 10) are being received correctly (signal
value 1) or not (signal value 0). The order in which each of the Incoming GOOSEs
are identified is determined by the order in which they have been registered in the
configuration file “IECGOOSE.INI”. The digital signal 0 will indicate whether the
first GOOSE input configured in file “IECGOOSE.INI” is being received correctly
(value 1) or not (value 0), the digital signal 1 will indicate the same of the second
GOOSE input configured in file “IECGOOSE.INI”, and so on.

Pairs of attributes stVal (Boolean state) and q (quality) contained in Incoming

GOOSE messages that are of interest to the Central Unit will be mapped from
digital signal 10 of the logic device that represents the Central Unit IEC-61850
server module.

B.17.3.a GOOSEs Configuration File: IECGOOSE.INI

Data corresponding to Incoming and outgoing GOOSEs to be handled by the Central Unit are
configured in file “IECGOOSE.INI”.

The file is configured in sections labelled with a heading, and is segregated into two sections:

- Section for Outgoing GOOSEs configuration, identified by label [GOOSE_OUT].

- Section for Incoming GOOSEs configuration, identified by label [GOOSE_IN].
• Section for Outgoing GOOSE Configuration: [Lines 7-9]
Labelled with heading [GOOSE_OUT].

EtiqSeccGoOut
NumGoOut ,
GoRef , GoID , MACAddr , VID , AppID , Priority , ...
(*)
... ConfRev , FirstInterval , Multiplier , MaxInterval ,

(*) It repeats for each Outgoing GOOSE. There will be as many as shown in NumGoOut.

• EtiqSeccGoOut: Heading label of section for Central Unit Outgoing GOOSE

configuration. It takes the value [GOOSE_OUT].
• NumGoOut: Number of Central Unit Outgoing GOOSEs. Maximum allowable value for
this parameter is 3.
• GoRef: Complete MMS reference of Goose-Control-Block (including the IED name),
namely, the Goose-Control-Block attribute GoCBRef.

M1CPTA2005I
B-267 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• GoID: Name that will uniquely identify the GOOSE. It corresponds to Goose-Control-
Block attribute GoCBName.
• MACAddr: MAC multicast GOOSE destination address.
• VID: VLAN (Virtual LAN) identifier with which the GOOSE will be sent. It is a number
between 0 and 4095 (both included).
• AppID: Integer identifying the application (Logic Device) that sends the GOOSE. It is a
number from 0 and 16383 (both included).
• Priority: Integer indicating the priority within the VLAN to send the GOOSE. It is a number
between 0 y 7 (both included).
• ConfRev: Integer representing the number of times the configuration of the dataset
associated to Goose-Control-Block has changed.
• FirstInterval: First interval (in msec.) of GOOSE message retransmission. Each time a
new GOOSE message is transmitted due to a change in any of its data, this is the time
value of its attribute timeAllowedToLive. Attribute timeAllowedToLive indicates the
devices receiving a GOOSE message, the maximum time in which they must receive a
retransmission of the same GOOSE.
• Multiplier: Integer by which the last retransmission interval must be multiplied each time a
GOOSE is sent by retransmission. Each GOOSE retransmitted will have the attribute
timeAllowedToLive updated with the value used for this attribute in the previous
retransmission, but multiplied by the parameter Multiplier.
• MaxInterval: Maximum interval (in msec.) of GOOSE retransmission. This will be the
maximum value that a retransmitted GOOSE will have for attribute timeAllowedToLive.
According to IEC-61850, this value must not exceed 60 seconds

Note: The set formed by parameters: FirstInterval, Multiplier and MaxInterval constitute what is known
as GOOSE message retransmission strategy that in this case it is of arithmetic type

Ex: [GOOSE_OUT]
2,
COND_UCSLD1/LLN0$GO$gcGOOSE1,GOOSE_UCS1,010CCD01002C,0,1001,4,1,10
0,2,10000,
COND_UCSLD1/LLN0$GO$gcGOOSE3,GOOSE_UCS2,010CCD01002E,0,1002,4,1,100,2,
10000,

• Section for Incoming GOOSE Configuration: [Lines 25-28]

Labelled with heading [GOOSE_IN].

EtiqSeccGoIn
NumGoIn ,
GoID , MACAddr , GoRef , AppID , MaskGoIn , MaskMap , (*)

(*) It repeats for each Incoming GOOSE. There will be as many as shown in NumGoIn.

• EtiqSeccGoIn: Heading label of section for Central Unit Incoming GOOSE configuration.
It takes the value [GOOSE_IN].
• NumGoIn: Number of Incoming GOOSEs processed by the Central Unit. Maximum
allowable value for this parameter is 10.
• GoID: Name that will uniquely identify the GOOSE. It corresponds to Goose-Control-
Block attribute GoCBName.
• MACAddr: MAC multicast Incoming GOOSE destination address.
• GoRef: Complete MMS reference of Goose-Control-Block (including the IED name).
Matches the Goose-Control-Block attribute GoCBRef.

M1CPTA2005I
1CPT: Substation Central Unit B-268
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• AppID: Integer identifying the application (Logic Device) that sends the GOOSE. It is a
number from 0 and 16383 (both included).
• MaskGoIn: Mask of Incoming GOOSE data, used to select the elements of the Incoming
GOOSE to be processed by the Central Unit to be mapped to digital signals of the logic
device that represents the Central Unit IEC-61850 server (device with internal address
288).
The Central Unit may only process Incoming GOOSEs if the data they contain are
consecutive pairs composed by a Boolean state (stVal) and its associated quality (q),
namely, GOOSE messages with data of the type [stVal1, q1, stVal2, q2, ..., stValN, qN]
or [q1, stVal1, q2, stVal2, ..., qN, stValN]. The mask indicates which elements (pairs of
attributes stVal and q) of the GOOSE message received are of interest for the Central
Unit, for which two bits for each GOOSE (one bit will act as filter for attribute stVal and
the other bit will act as filter for attribute q) will be reserved within the mask. GOOSE
elements whose position in the mask corresponds to a value of 0 will be discarded by the
Central Unit, and only GOOSE elements associated to positions with a value of 1 within
the mask will be processed, hence updating their values over the digital signals of the
logic device representing the Central Unit IEC-61850 server. In the example, for the
GOOSE_SEL1 (110011), the first data and the third data of all data contained in the
GOOSE message received will be processed.
• MaskMap: Bit mask that allows selecting the digital signals of the logic device
representing the Central Unit IEC-61850 server (device with internal address 288), that
will be used for mapping Incoming GOOSE data previously selected with parameter
MaskGoIn. As the first 10 digital signals (0-9) of the Central Unit IEC-61850 logic device
are reserved, the first signal available for mapping Incoming GOOSE data will be digital
signal number 10.

The first bit of the mask corresponds to signal 10, the second to 11 and so on. The
Central Unit will only process the values ‘0’ and ‘1’ within this mask, so that separator
characters ‘|’ and blank spaces will not be taken into account. The value ‘1’ in this mask
indicates that the associated digital signal will be used for mapping one element of the
Incoming GOOSE (one pair of attributes stVal and q).

The first pair (11) selected in the mask MaskGoIn will correspond to the first ‘1’ in this
mask, this second pair (11) selected in MaskGoIn will correspond to the second ‘1’ in this
mask and so on. In the example, for GOOSE_SEL1 (| 1 0 1 |), the first data (pair 11 of
MaskGoIn) will be mapped to the digital signal number 10 of the Central Unit IEC-61850
logic device, and the third data (pair 11 of MaskGoIn) to the digital signal number 12.

Ej: [GOOSE_IN]
2,
GOOSE_SEL1,010CCD010004,Sel/GcRef1,0,110011,| 1 0 1 |,
GOOSE_SEL2,010CCD010005,Sel/GcRef1,1,001100,| 0 1 0 |,

M1CPTA2005I
B-269 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] # [GOOSE_OUT]
[2] # Number of Outgoing GOOSEs,
[3] #
GoRef,GoID,MAC,VID,AppID,Priority,ConfRev,FirstInterval(msec),Multiplier,
[4] # MaxInterval(msec),
[5] #
[6] [GOOSE_OUT]
[7] 1,
[8] COND_UCSLD1/LLN0$GO$gcGOOSE1,GOOSE_UCS,010CCD01002C,0,1001,4,1,100,2,1000
0,
[9] #[GOOSE_IN]
[10] # Number of Incoming GOOSEs,
[11] # GoID,MAC,GoRef,PRIORITY,AppID,MascaraGoose,MascaraMapeoSeñalesSRV61850,
[12] #
[13] # In the example from the 6 data of GOOSE_SEL1 only 4 (the two first and
the two last) will be mapped:
[14] # - the two first ("stVal"/"q" or "q"/"stVal") are mapped to signal
[288,10].
[15] # - the two next (idem) are NOT mapped (they are not activated in the
mask).
[16] # - the two last (idem) are mapped to signal [288,12].
[17] # In the example from the 6 data of GOOSE_SEL2 only 2 (the 2
[18] # in the middle) are mapped:
[19] # - the two first ("stVal"/"q" or "q"/"stVal") are NOT mapped.
[20] # - the two next (idem) are mapped to signal [288,11].
[21] # - the two last (idem) are NOT mapped.
[22] #
[23] [GOOSE_IN]
[24] 2, //Virtual IEC61850 signal: 10 11 12 13 14 15 ...
[25] GOOSE_SEL1,010CCD010004,Sel/GcRef1,0,110011,| 1 0 1 |,
[26] GOOSE_SEL2,010CCD010005,Sel/GcRef1,1,001100,| 0 1 0 |,

B.17.3.b IEC-61850 Server Configuration File: 61850SRV.CFG

Is the file “61850SRV.CFG” that contains the Central Unit IEC-61850 server configuration data.
The file is segregated into two parts:

- Configuration of digital signals of the logic device representing the Central Unit IEC-
61850 server (device with internal address 288), used for mapping the pairs of IEC-61850
attributes stVal (digital Boolean state) and q contained in the Incoming GOOSE
messages.
- Configuration of the different logic devices (LDs) that comprise the Central Unit. For each
Logic Device:
o Configuration of Logic Device descriptions.
o Configuration of logic nodes (LNs). For each logic node:
• Configuration of general data of the logic node.
• Configuration of single digital indications of the logic node. Allocation of single
digital signals available in the Central Unit real time database, to the single digital
indications of the logic node.
• Configuration of single commands of the logic node.
Each controllable IEC-61850 data within the logic node is allocated a pair of single
commands of the Central Unit. When the Central Unit receives the IEC-61850
command with the control attribute ctlVal set to TRUE (on), this will execute the
first associated command. When the IEC-61850 command is received with the
control attribute ctlVal set to FALSE (off), the Central Unit will execute the second
associated command.

M1CPTA2005I
1CPT: Substation Central Unit B-270
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

File format is as follows:

• Configuration Data of Signals for Mapping Incoming GOOSEs: [lines 5-18]
It will be carried out as explained in chapter A.1.

Central Unit Incoming GOOSEs are mapped to digital signals of the IEC-61850 logic device (its
internal address will be the associated to the IEC-61850 module in the Central Unit module
activation file “PROTASK.CFG”) with the following criterion:

- The Central Unit accepts a maximum of 10 Incoming GOOSEs.

- Digital signals 0 to 9 (both included) are reserved to tag whether the Incoming GOOSE 1
to 10, respectively, is received correctly (value 1) or not (value 0). The order of the
Incoming GOOSEs will be the order of registration in the configuration file
“IECGOOSE.INI”. Namely, digital signal number 4 will indicate if the fifth Incoming
GOOSE configured in file “IECGOOSE.INI” is received correctly (digital signal number 4
with value 1) or not (digital signal number 4 with value 0).
- These 10 first signals must be included in the total number of signals configured in this
section. If the Central Unit is not to receive Incoming GOOSEs (they have not been
defined in “IECGOOSE.INI”), no signal will be configured in this section.
- It will be from digital signal number 10 (inclusive) that data of the different Incoming
GOOSEs could be mapped.
- When the GOOSE is not being received correctly, the GOOSE digital signals will be
tagged as invalid in the Central Unit real time database. In the example:
o If GOOSE 1 is not being received, digital signals 10 and 12 will become invalid (also,
digital signal 0 will switch to state 0).
o If GOOSE 2 is not being received, digital signal 11 will become invalid (also, digital
signal 1 will switch to state 0).

Ex:13,
00,1,0,0,0,1, // GOOSE 1 received OK (1) or not (0)
01,1,0,0,0,1, // GOOSE 2 received OK (1) or not (0)
02,1,0,0,0,1, // GOOSE 3 received OK (1) or not (0)
03,1,0,0,0,1, // GOOSE 4 received OK (1) or not (0)
04,1,0,0,0,1, // GOOSE 5 received OK (1) or not (0)
05,1,0,0,0,1, // GOOSE 6 received OK (1) or not (0)
06,1,0,0,0,1, // GOOSE 7 received OK (1) or not (0)
07,1,0,0,0,1, // GOOSE 8 received OK (1) or not (0)
08,1,0,0,0,1, // GOOSE 9 received OK (1) or not (0)
09,1,0,0,0,1, // GOOSE 10 received OK (1) or not (0)
10,1,0,0,0,1, // Signal 1 of GOOSE 1
11,1,0,0,0,1, // Signal 1 of GOOSE 2
12,1,0,0,0,1, // Signal 2 of GOOSE 1

M1CPTA2005I
B-271 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Central Unit Logic Devices (LD): [Lines 24-67]

The only Logic Device (LD) that comprise the Central Unit will be configured in this section.

The configuration of the Logic Device will have a first part dedicated to the configuration of a
number of descriptive texts that identify the same. Logic nodes (LN) that comprise the Logic
Device will be configured next.

In turn, each logic node will have a first part of descriptive text configuration. Then, the Central
Unit digital signals to be mapped to IEC-61850 logic node data (e.g. for Outgoing GOOSEs,
Reports, ...) will be configured. Finally, single controllable IEC-61850 logic node data to be
mapped to single commands of the Central Unit (e.g. logic module commands) will be
configured

NumLDs ,
DomainName ,
Mod ,
Beh ,
Health ,
Vendor ,
LLN0_d ,
SerNum ,
Location ,
NumLNs ,
LNName , LN_d , (*)
NumSeñSimp ,
Señal61850 , Dir , Isc , Descrip , (***) (**)
NumManSimp ,
Mando61850 , DirOn , IseOn , DcoOn , …
(****)
… DirOff , IseOff , DcoOff , DescripMan ,

(*) It repeats for each LD. There will be as many as shown in NumLDs.
(**) It repeats for each LN belonging to the LD. There will be as many as shown in NumLNs.
(***) It repeats for each single IEC-61850 digital indication belonging to the LN. There will be
as many as shown in NumSeñSimp.
(****) It repeats for each single controllable IEC-61850 data belonging to the LN. There will be
as many as shown in NumManSimp.

• NumLDs: Number of logic devices (LD) that comprise the Central Unit, although presently
it consists only of one LD. The maximum allowable value for this parameter is 5 LDs.
• DomainName: Name of domain MMS, namely, the name of the IED linked to the LD
name. For instance, if the name of the IED is “COND_UCS” and the name of the LD is
“LD1”, this parameter will take the value “COND_UCSLD1”. The maximum allowable
number of characters for this parameter is 64.
• Mod: Description of the IEC-61850 data Mod (mode) of the logic node zero (LLN0) and of
every logic nodes configured later on (as many as specified by parameter NumLNs). With
this parameter the Central Unit will configure the IEC-61850attribute “LLN0$Mod$d” and
attributes “LNName$Mod$d” (where LNName is the name of each logic node configured
later on in this same section). The default value to be configured for this parameter will be
“Operating mode” (in the applicable language). The maximum allowable number of
characters for this parameter is 255.

M1CPTA2005I
1CPT: Substation Central Unit B-272
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Beh: Description of the IEC-61850 data Beh (performance) of the logic node zero (LLN0)
and of every logic nodes configured later on (as many as specified by parameter
NumLNs). With this parameter the Central Unit will configure the attribute “LLN0$Beh$d”
and attributes “LNName$Beh$d” (where LNName is the name of each logic node
configured later on in this same section). The default value to be configured for this
parameter will be “Performance” (in the applicable language). The maximum allowable
number of characters for this parameter is 255.
• Health: Description of the IEC-61850 data Health (health) of the logic node zero (LLN0)
and of every logic nodes configured later on (as many as specified by parameter
NumLNs). With this parameter the Central Unit will configure the attribute
“LLN0$Health$d” and attributes “LNName$Health$d” (where LNName is the name of
each logic node configured later on in this same section). The default value to be
configured for this parameter will be “Health” (in the applicable language). The maximum
allowable number of characters for this parameter is 255.
• Vendor: Value of the IEC-61850 attribute vendor (manufacturer name) of the logic node
zero (LLN0), physical node (LPHD1) and of every logic nodes configured later on (as
many as specified by parameter NumLNs). With this parameter the Central Unit will
configure the attribute “LLN0$NamPlt$vendor”, attribute “LPHD1$PhyNam$vendor” and
attributes “LNName$NamPlt$vendor” (where LNName is the name of each logic node
configured later on in this same section). The default value to be configured for this
parameter will be “ZIV Aplicaciones y Tecnologia S.A.”. The maximum allowable
number of characters for this parameter is 255.
• LLN0_d: Description of the logic node zero (LLN0) of the Logic Device. With this
parameter the Central Unit will configure the attribute “LLN0$NamPlt$d”. The default
value to be configured for this parameter will be “Logic Node 0” (in the applicable
language). The maximum allowable number of characters for this parameter is 255.
• SerNum: Value of the IEC-61850 attribute serNum (serial number) of the Logic Device
physical node (LPHD1). With this parameter the Central Unit will configure the attribute
“LPHD1$PhyNam$serNum”. In this parameter the serial number of the Central Unit will
be configured (displayed in the nameplate on the device front). The maximum allowable
number of characters for this parameter is 255.
• Location: Value of the IEC-61850 attribute location (location) of the Logic Device physical
node (LPHD1). With this parameter the Central Unit will configure the attribute
“LPHD1$PhyName$location”. The default value to be configured for this parameter will
be “Substation Central Unit” (in the applicable language). The maximum allowable
number of characters for this parameter is 255.
• NumLNs: Number of logic nodes (LN) of the Logic Device. The maximum allowable
number for this parameter is 100 LNs.
• LNName: Name of the logic node. The maximum allowable number of characters for this
parameter is 32.
• LN_d: Description of the logic node. With this parameter the Central Unit will configure
the attribute “LNName$NamPlt$d” (where LNName is the name of the logic node). The
maximum allowable number of characters for this parameter is 255.
• NumSeñSimp: Number of single digital signals of the Central Unit to be mapped to single
IEC-61850 digital indications of the logic node. The maximum allowable value for this
parameter is de 999 signals.
• Señal61850: Single IEC-61850 digital indication (only the data name) to which the state
(in attribute “LNName$ST$Señal61850$stVal”), the validity (in attribute
“LNName$ST$Señal61850$q”) and the time tag (in attribute
“LNName$ST$Señal61850$t”) of a single digital signal [Dir,Isc] of the Central Unit real
time database is to be mapped.
• Dir: Address of the device (within the Central Unit real time database) that the single
digital signal to be mapped to the IEC-61850 data specified by parameter Señal61850
belongs to.

M1CPTA2005I
B-273 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

• Isc: Identifier of the single digital signal used for mapping to IEC-61850 data specified by
the parameter Señal61850.
• Descrip: Description of IEC-61850 data specified by the parameter Señal61850. With this
parameter the Central Unit will configure the attribute “LNName$DC$Señal61850$d”. The
maximum allowable number of characters for this parameter is 255.
• NumManSimp: Number of single controllable IEC-61850 data of the logic node to be
mapped to pairs of single commands of the Central Unit. The maximum allowable value
for this parameter is 99 commands.
• Mando61850: Single controllable IEC-61850 data (only the data name) to be mapped to
two single commands of the Central Unit. When the Central Unit receives a command for
the controllable IEC-61850 data (specified by parameter Mando61850) with the control
attribute ctlVal set to TRUE (on), this will execute the single command [DirOn,IseOn] with
DCO=DcoOn. When a command is received for the controllable IEC-61850 data
Mando61850 with the control attribute ctlVal set to FALSE (off), the Central Unit will
execute the single command [DirOff,IseOff] with DCO=DcoOff.
• DirOn: Address of the device (within the Central Unit real time database) to which the
single command the Central Unit will execute when receiving a command for the
controllable IEC-61850 data Mando61850 with ctlVal set to TRUE (on) belongs.
• IseOn: Identifier of the single command the Central Unit will execute when a command
for the controllable IEC-61850 data Mando61850 with ctlVal set to TRUE (on) is received.
• DcoOn: DCO with which the Central Unit will execute the single command [DirOn,IseOn]
when receiving a command for the controllable IEC-61850 data Mando61850 with ctlVal
set to TRUE (on).
• DirOff: Address of the device (within the Central Unit real time database) that the single
command the Central Unit will execute when receiving a command for the controllable
IEC-61850 data Mando61850 with ctlVal set to FALSE (off) belongs to.
• IseOff: Identifier of the single command the Central Unit will execute when receiving a
command for the controllable IEC-61850 data Mando61850 with ctlVal set to FALSE (off).
• DcoOff: DCO with which the Central Unit will execute the single command [DirOff,IseOff]
when receiving a command for the controllable IEC-61850 data Mando61850 with ctlVal
set to FALSE(off).
• DescripMan: Description of the controllable IEC-61850 data specified by parameter
Mando61850. With this parameter the Central Unit will configure the attribute
“LNName$DC$Mando61850$d”. The maximum allowable number of characters for this
parameter is 255

M1CPTA2005I
1CPT: Substation Central Unit B-274
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 1, // NumLDs
COND_UCSLD1, // DomainName
Operating mode, // Mod
Performance, // Beh
Health, // Health
ZIV Aplicaciones y Tecnologia S.A., // vendor
Logic Node 0, // d
61044, // serNum
Substation Central Unit, // location
2, // NumLNs,
# First LN
TGO3GGIO1,OUTGOING GOOSES, // LNName,Descr,
4, // NumSenSimp,
Ind01,256,100,BLOCK COUPL. OPEN. BY 89 COUPL,
Ind02,256,101, SOME BAY COUPLED TO BUSBARS 1,
Ind03,256,102, SOME BAY COUPLED TO BUSBARS 2,
Ind04,256,103,20 COUPLED SECTIONALIZERS,
1, // NumManSimp,
SPCS001,256,0,2,256,1,2,LOGIC: Command 0,
# Second LN
GENGGIO1,GENERAL INDICATIONS, // LNName,Descr,
0, // NumSenSimp,
0, // NumManSimp,

The file becomes:

[1] #############################################################
[2] ## 61850 SERVER CONFIGURATION FILE (61850SRV.CFG) ##
[3] #############################################################
[4] # Signals of virtual IEC61850 device (for mapping the Incoming GOOSE)
[5] 13,
[6] 00,1,0,0,0,1,// GOOSE 1 received OK (1) or KO (0)
[7] 01,1,0,0,0,1,// GOOSE 2 received OK (1) or KO (0)
[8] 02,1,0,0,0,1,// GOOSE 3 received OK (1) or KO (0)
[9] 03,1,0,0,0,1,// GOOSE 4 received OK (1) or KO (0)
[10] 04,1,0,0,0,1,// GOOSE 5 received OK (1) or KO (0)
[11] 05,1,0,0,0,1,// GOOSE 6 received OK (1) or KO (0)
[12] 06,1,0,0,0,1,// GOOSE 7 received OK (1) or KO (0)
[13] 07,1,0,0,0,1,// GOOSE 8 received OK (1) or KO (0)
[14] 08,1,0,0,0,1,// GOOSE 9 received OK (1) or KO (0)
[15] 09,1,0,0,0,1,// GOOSE 10 received OK (1) or KO (0)
[16] 10,1,0,0,0,1,// Signal 1 of GOOSE 1
[17] 11,1,0,0,0,1,// Signal 1 of GOOSE 2
[18] 12,1,0,0,0,1,// Signal 2 of GOOSE 1
[19] #
[20] ########################
[21] # Configuration of LDs #
[22] ########################
[23] # Number of LDs
[24] 1,
[25] ################## Primer LD #################
[26] # Domain name (IED name + LD name),
[27] COND_UCSLD1,
[28] #### Description data of LD ####
[29] # Mod (LLN0)
[30] Operating mode,
[31] # Beh (LLN0)

M1CPTA2005I
B-275 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[32] Performance,
[33] # Health (LLN0)
[34] Health,
[35] # vendor (LLN0$NamPlt + LPHD1$PhyNam + Nodos$NamPlt)
[36] ZIV Aplicaciones y Tecnologia S.A.,
[37] # d (LLN0)
[38] Logic Node 0,
[39] # serNum (LPHD1$PhyNam)
[40] 61044,
[41] # location (LPHD1$PhyNam)
[42] Substation Central Unit,
[43] #### Number of LD1 nodes ####
[44] 2,
[45] ########## Node 1 ##########
[46] # Node name, Node description (NamPlt$d),
[47] TGO3GGIO1,OUTGOING GOOSES,
[48] # Number of single signals of the node TGO3GGIO1,
[49] 4,
[50] # Dato61850,Dir,ISC,Descripción,
[51] Ind01,256,100,BLQ. OPEN COUPL BY 89 COUPL, // Signal 1 of the
Outgoing GOOSE
[52] Ind02,256,101, SOME BAY COUPLED TO BUSBARS 1, // Signal 2 of the
Outgoing GOOSE
[53] Ind03,256,102, SOME BAY COUPLED TO BUSBARS 2, // Signal 3 of the
Outgoing GOOSE
[54] Ind04,256,103,20 COUPLED SECTIONALIZERS, // Signal 4 of the Outgoing
GOOSE
[55] # Number of single commands of node TGO3GGIO1,
[56] 1,
[57] # Dato61850,DirOn,IseOn,DcoOn,DirOff,IseOff,DcoOff,Descripción,
[58] # The first command (DirOn,IseOn) with DcoOn will be executed when
"ctlVal" is ON.
[59] # The second command (DirOff,IseOff) with DcoOff will be executed when
"ctlVal" is OFF.
[60] SPCS001,256,0,2,256,1,2,LÓGIC: Command 0,
[61] ########## Node 2 ##########
[62] # Node name, Node description (NamPlt$d),
[63] GENGGIO1,GENERAL INDICATIONS,
[64] # Number of single signals of node GENGGIO1,
[65] 0,
[66] # Number of single commands of node GENGGIO1,
[67] 0,

B.17.4 Configuration File of IEC-61850 Communications: RFC1006.CFG

[Lines 1-9]
In this file the settings of the interface between the IEC-61850 module of the Central Unit and ISO
transport layer used in the MMS communication between the Central Unit and the rest of the 61850
IEDs are configured.

local_tsap
max_tsdu_size
buff_segment_size
num_buffers
num_connections
num_queue_pool_entries
max_input_queue_len
max_output_queue_len
use_listen

M1CPTA2005I
1CPT: Substation Central Unit B-276
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• local_tsap: Access point to the local transport layer service (SAP).

• max_tsdu_size: Maximum size in bytes for the data unit handled by the local transport
layer.
• buff_segment_size: Size in bytes of each of the buffers available in the list of buffers
reserved for communications through MMS protocol.
• num_buffers: Number of buffers available in the list of buffers reserved for
communications through MMS protocol.
• num_connections: Maximum number of MMS connections accepted by the Central Unit
IEC-61850 server.
• num_queue_pool_entries: Number of registers reserved for saving the messages
interchanged between the MMS layer and the transport layer.
• max_input_queue_len: Maximum number of registers reserved for saving messages
received by the MMS layer from the transport layer.
• max_output_queue_len: Maximum number of registers reserved for saving messages to
be sent from the MMS layer to the transport layer.
• use_listen: This parameter configures the transport layer of the Central Unit in order to
accept MMS client connections (value 1), or to accept no connections (value FALSE).
However, no matter the value of this parameter, when the Central Unit IEC-61850 server
has been configured through file “61850SRV.CFG”, the Central Unit transport layer will
be automatically enabled to accept MMS client connections; and it will be disabled
otherwise.

Ex: local_tsap 0001

max_tsdu_size 65535
buff_segment_size 1024
num_buffers 100
num_connections 5
num_queue_pool_entries 100
max_input_queue_len 65
max_output_queue_len 65
use_listen 1

The file becomes:

[1] local_tsap 0001

[2] max_tsdu_size 65535
[3] buff_segment_size 1024
[4] num_buffers 100
[5] num_connections 5
[6] num_queue_pool_entries 100
[7] max_input_queue_len 65
[8] max_output_queue_len 65
[9] use_listen 1

M1CPTA2005I
B-277 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.18 IEC103 Protocol: IEC103MS.CFG

The configuration required for IEC103 equipment communications is carried out in two files:
dbase.cfg and iec103ms.cfg. In the first file, signals are configured the same as for PROCOME
equipments. In file “iec103ms.cfg” the parameters that associate specific protocol data to
signals configured in dbase.cfg are configured

File format is as follows:

• Protocol General Data

NumEquipos , MaxReint , RepCiclos IG , Retardo , PeriodoSincro ,

Traza , MaxReintNakMandos , MaxReintNakGI ,

• NumEquipos: Number 103 equipment.

• MaxReint: Maximum number of retries before a communications failure is issued. It is a
value between 0 and 100. Default value is 3.
• RepCiclosIG: Consecutive attempts during the general interrogation cycle. The General
Interrogation may be too long, so it may be convenient segregating it into parts among all
equipment. The number of requests sent to an equipment in each part is given by this
parameter, the value of which varies from 2 to 100, the default value being 6. In case it is
configured to -1, the general interrogation will be completely executed for an equipment
before going to the next, except otherwise stated by parameter MaxReintNakGI.
Note: For devices other than Siemens, it is recommended to configure this parameter to -1.
• Retardo: Delay time between two consecutive messages sent to the same device. This
parameter is expressed in ms and varies from 0 to 5000, the default value being 60.
• PeriodoSincro: Device synchronization period in units of 500ms. This parameter varies
from 20 (10 s) to 2000 (1000 s). The default value is 60 (30 s).
• Traza: Value of the screen tracing mask.
• MaxReintNakCommands: After sending a command, the device usually takes some time
to send the answer, during which it responds with NAK messages. This parameter
indicates the number of times the NAK message is accepted before the command
procedure is deemed failed. Values vary from 3 to 200, the default value being 5. For
AREVA P132 devices, this parameter must be configured with a high value: 30.
• MaxReintNakGI: This parameter has a meaning similar to the above, but it is used in the
General Interrogation procedure. If this maximum number of NAKs is reached during a
General Interrogation, next device will be interrogated, but next cycle the outstanding GI
for the relay in progress will be taken again. Values vary from 3 to 200, taking 5 as default
value. In case it is configured to -1, next device will not be interrogated until the General
Interrogation of the current device is completed, except otherwise stated by parameter
• RepCiclosIG.

Ex: 2,4,3,0,300,0,30,5,

Data of the different devices are listed below in sequential order. The following data are shown
for each of the NumEquipos devices:

M1CPTA2005I
1CPT: Substation Central Unit B-278
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• General Data of the Device in Question: [line 6]

Dir , TipoReset , TipoReintento , TipoCiclo , TipoRecuperaError ,

• Dir: IEC103 and PROCOME address of the equipment. This address is used to
communicate with the device and to associate it with the signals configured in
DBASE.CFG.
• TipoReset: It indicates the type of RESET message sent to the device: 0=ResetCU and
1=ResetFCB (Endesa). Default value is 0.
• TipoReintento: It indicates the way to carry out attempts on communications failure:
0=Consecutive attempts, 1=Attempts per cycle (Endesa). Default value is 0.
• TipoCiclo: It indicates the type of cycle to be used to retrieve device data:
0=RequestDataClass2, 1=RequestDataClass1 (Endesa). Default value is 0.
• TipoRecuperaError: It indicates the method used to recover the device from error status.
Value 0 indicates that the interrogation is repeated the number of times configured, every
cycle in turn. Value 1 (Endesa) indicates that, in case the communication with the device
fails, the interrogation cycle is cancelled for one minute, after which its recovery is
attempted. This procedure is carried out because SIEMENS devices take one minute to
recover after a cold start.

Ex: 10,1,1,1,1,

• Configuration Data ff Digital Signals

In this section, the associations between device ISCs and IEC103 signals received from the
device are configured. These are described by a two-parameter set: FunctionType and
InformationNumber.

NumISC ,
ISC , FuncNum , FuncType , InfNum , ASDU , BitDoble , (*)

(*) It repeats for each signal. There will be as many lines as shown in NumISC.

• NumISC: Number of the device ISC. This parameter must have the same value as its
counterpart in dbase.
• ISC: Index of the ISC to which the IEC103 parameters are associated. Signals must be
configured consecutively in ascending order without gaps.
• FuncNum: Associated function number. It is an information parameter not used in the
protocol that can be set to 0 if its value is unknown. It has no effect on communications.
• FuncType: Function Type. (See next parameter)
• InfNum: Information Number. In IEC103 protocol, every signal is identified,
unmistakeably, by the pair of values FuncType-InfNum.
• ASDU: Number of the ASDU with which the information is received. This is an information
parameter.
• BitDoble: Indicates whether the signal is single (0) or double. In the latter case the signal
state must be associated to the ISC: 1=OFF; 2=ON. In general, two ISC signals must be
defined for each double IEC103 signal, one with BitDoble set to 1 and another set to 2.

M1CPTA2005I
B-279 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 4,
0,1764,100,1,1,0,
1,1763,100,2,1,0,
2,352,240,160,1,1,
3,352,240,160,1,2,

• Configuration Data of Commands

In this section, the associations between commands defined in the device dbase.cfg and the
IEC103 commands to be sent to the device. These are described by a set of three parameters:
ASDU, FunctionType and InformationNumber. If IEC103 device commands are to be integrated
in other UCS modules (logic, screens, remote controls, etc.) it must be taken into account that
these devices have double commands and DCO values must be configured adequately.

NumISE ,
ISE , FuncNum , FuncType , InfNum , ASDU , BitDoble , (*)

(*)It repeats for each signal. There will be as many lines as shown in NumISE.

• NumISE: Number of device commands. This parameter must have the same value as its
counterpart in dbase.
• ISE: Index of the ISE to which the IEC103 parameters are associated. Commands must
be configured consecutively in ascending order without gaps.
• FuncNum: Associated function number. It is an information parameter not used in the
protocol that can be set to 0 if its value is unknown. It has no effect on communications.
• FuncType: Function Type. (See next parameter).
• InfNum: Information Number. In IEC103 protocol, every command is identified,
unmistakeably, by the pair of values FuncType-InfNum.
• ASDU: Number of ASDU to be used to carry out the command. Possible values are
three: 20, 46 and 232.
• BitDoble: Field for compatibility purposes. Not in use. Always set to zero.

Ex: 4,
0,3003,240,160,20,0,
1,3007,253,17,20,0,
2,3007,253,27,46,0,
3,3004,253,51,232,0,

M1CPTA2005I
1CPT: Substation Central Unit B-280
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Configuration Data of Measurements

In this section, the associations between measurements defined in the equipment dbase.cfg
and IEC103 measurements received from the device are configured. These are described by a
four-parameter set: ASDU, FunctionType, InformationNumber and measurement position in
ASDU.

NumMEA ,
MEA , Posicion , FuncType , InfNum , ASDU , BitDoble , (*)

(*) It repeats for each measurement. There will be as many lines as shown in NumMEA.

• NumMEA: Number of device measurements. This parameter must have the same value
as its counterpart in dbase.
• MEA: Index of the MEA to which the IEC103 parameters are associated. Measurements
must be configured consecutively in ascending order without gaps.
• Posicion: Position of the measurement in the applicable ASDU.
• FuncType: Function Type. (See next parameter)
• InfNum: Information Number. In IEC103 protocol, every information is identified,
unmistakeably, by the pair of values FuncType-InfNum.
• ASDU: Number of the ASDU with which measurement values are received. Possible
values are: 3 and 9.
• BitDoble: Field for compatibility purposes. Not in use. Always set to zero.

Ex: 4,
0,0, 160,145,3,0,
1,5, 134,137,9,0,
2,10,134,137,9,0,
3,11,134,137,9,0,

The file becomes:

[1] # Protocol general data

[2] 2,4,3,0,300,0,30,5,
[3] # Equipment 1: General data
[4] 10,1,1,1,1,
[5] # Configuration data digital signals
[6] 4,
[7] 0,1764,100,1,1,0,
[8] 1,1763,100,2,1,0,
[9] 2,352,240,160,1,1,
[10] 3,352,240,160,1,2,
[11] # Configuration data of commands.
[12] 4,
[13] 0,3003,240,160,20,0,
[14] 1,3007,253,17,20,0,
[15] 2,3007,253,27,46,0,
[16] 3,3004,253,51,232,0,
[17] # Configuration data of measurements
[18] 4,
[19] 0,0, 160,145,3,0,
[20] 1,5, 134,137,9,0,
[21] 2,10,134,137,9,0,
[22] 3,11,134,137,9,0,
[23] # Equipment 2: General data.

M1CPTA2005I
B-281 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[24] 10,1,1,1,1,
[25] # Configuration data of digital signals
[26] 4,
[27] 0,1764,100,1,1,0,
[28] 1,1763,100,2,1,0,
[29] 2,352,240,160,1,1,
[30] 3,352,240,160,1,2,
[31] # Configuration data of commands.
[32] 4,
[33] 0,3003,240,160,20,0,
[34] 1,3007,253,17,20,0,
[35] 2,3007,253,27,46,0,
[36] 3,3004,253,51,232,0,
[37] # Configuration data of measurements
[38] 4,
[39] 0,0, 160,145,3,0,
[40] 1,5, 134,137,9,0,
[41] 2,10,134,137,9,0,
[42] 3,11,134,137,9,0,

M1CPTA2005I
1CPT: Substation Central Unit B-282
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.19 SNMP Client Module: SRVSNMP.CFG and

SNMPCLI.CFG Files (1CPT Models)
The SNMP client module of the CPT is supported in turn by two modules (SRVSNMP and
SNMPCLI) which cooperate with each other to provide the SNMP client function, so that SNMP
variables can be read from SNMP devices (mapped to CPT database data: signals,
measurements or counters) or written to SNMP devices (mapped to digital or analog
commands).

SRVSNMP is a CPT thread to read/write SNMP variables from/to the various SNMP devices,
using the “Net-SNMP“ library for that purpose. The configuration file of this module is
SRVSNMP.CFG and houses both SNMP device communications data and the names and
types of the different SNMP variables that are read / written from/to each device.

SNMPCLI is a CPT task (fibre) responsible for launching the SRVSNMP thread that makes
possible the read/write of SNMP variables and the mapping of SNMP variables concerning data
(signals, measurements, counters, digital commands and analog commands) of the CPT
database virtual equipment. Therefore, this SNMPCLI task is the task to be configured in the list
of task to be run in the CPT (PROTASK.CFG file). The configuration file of this module is
SNMPCLI.CFG that houses the definition of the database virtual equipment with its signals,
digital and analog commands, measurements and counters that the various SNMP device
variables described in SRVSNMP.CFG file will be mapped to.

The SNMPCLI module of the CPT will be activated by including the following line in the
PROTASK.CFG configuration file of the CPT:

1, SNMPCLI,SNMPCLI.DLL,2048,-1,

B.19.1 SRVSNMP Module: SRVSNMP.CFG File

File format is as follows:
• SNMP Device Data: [lines 3-21]

NumEqSNMP ,
Nombre_IP , Password , Retries , Timeout , Vers ,
NumOIDs , (*)
NombreOID , TipoOID , (**)

(*) It repeats for each SNMP device. There will be as many as indicated by NumEqSNMP.
(**) It repeats for each SNMP device data (OID). There will be as many as indicated by
NumOIDs.

• Nombre_IP: Name or IP address of the SNMP device.

• Password: Password used for the SNMP connection with that device.
• Retries: Number of connection retries or data request/transmission (Timeout milliseconds
apart) before a timeout with the SNMP device is issued, namely, the number of retries will
be (Retries+1). If it is set to –1 the Net-SNMP library default value is taken (1 retry).

M1CPTA2005I
B-283 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Timeout: Timeout (in milliseconds) for each connection retry or data

request/transmission. If it is set to –1 the Net-SNMP library default value is taken (1
second). Timeout*(Retries+1) milliseconds will elapse from the first communications retry
until a timeout with the device is issued.
• Vers: SNTP version used; possible values are 1 or 2 (equivalent to SNMP version 2c).
• NumOIDs: Number of SNMP device variables (OIDs) concerned.
• NombreOID: Name of the SNMP variable.
• TipoOID: Type of SNMP variable. Available types are (ASN1 notation): 2
(ASN_INTEGER, integer), 3 (ASN_BIT_STR, bit-string), 4 (ASN_OCTET_STR, octet-
string), 120 (ASN_OPAQUE_FLOAT, float) and 121 (ASN_OPAQUE_DOUBLE, double).

Ex: 2,
128.127.170.233,user,-1,-1,2,
157,
.1.3.6.1.4.1.4576.4.6.1.1.1.0,2,
.1.3.6.1.4.1.4576.4.6.1.1.2.0,2,
...
.1.3.6.1.4.1.4576.4.6.1.2.51.0,2,
128.127.170.36,gestion,0,2000,1,
2,
.1.3.6.1.2.1.4.2.0,2,
.1.3.6.1.2.1.4.13.0,2,

The file becomes:

[95] # SNMP Devices Configuration

[96] # SNMP Devices Number
[97] 2,
[98] # ********** DEVICE 1 ***************
[99] # Nombre_IP,Password,retries,timeout,versión,
[100]128.127.170.233,user,-1,-1,1,
[101]# OIDs Number,
[102]157,
[103]# NombreOID,TipoOID,
[104].1.3.6.1.4.1.4576.4.6.1.1.1.0,2,
[105].1.3.6.1.4.1.4576.4.6.1.1.2.0,2,
[106]...
[107].1.3.6.1.4.1.4576.4.6.1.2.51.0,2,
[108]# ********** DEVICE 2 ***************
[109]# Nombre_IP,Password,retries,timeout,versión,
[110]128.127.170.36,gestion,0,2000,2,
[111]# OIDs Number,
[112]2,
[113]# NombreOID,TipoOID,
[114].1.3.6.1.2.1.4.2.0,2,
[115].1.3.6.1.2.1.4.13.0,2,

M1CPTA2005I
1CPT: Substation Central Unit B-284
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.19.2 SNMPCLI Module: SNMPCLI.CFG File

File format is as follows:
• General Data: [Line 3]

TimeRefresh , NivelTraza ,

• TimeRefresh: Time (in milliseconds) from the time the SNMP device interrogation cycle
ends until the beginning of the next cycle. The lower configurable limit is 200
milliseconds.
• NivelTraza: Trace monitoring level of the SNMPCLI task.

Ex: 1000,0,

• Data of Database SNMP Virtual Equipment: [Line 5]

NumEqBD ,

• NumEqBD: Number of database SNMP virtual equipment that the SNMP variables of the
various SNMP devices will be mapped to.

Ex: 2,

Below are the data of all virtual equipment that the SNMP variables of the various SNMP
devices will be mapped to (in sequence, one after another). The following data will be given for
each equipment:
• General Equipment Data: [line 9]

Dir , N_ ISC , ISC Max , N_ ISE , ISE Max , N_ ISS , ISS Max , N_ MEA , N_ CON ,

… N_ISM , ISCFail , FormatoMEAs , Nombre_IP ,

• Dir: Equipment address.

• N_ISC: Number of digital signals (ISC).
• ISCMax: Highest label of any ISC of the equipment in question.
• N_ISE: Number of digital commands (ISE).
• ISEMax: Highest label of any ISE of the equipment in question.
• N_ISS: Number of output writes (ISS).
• ISSMax: Highest label of any ISS of the equipment in question.
• N_MEA: Number of measurements (MEA).
• N_CON: Number of counters (CON).
• N_ISM: Number of analog output writes (ISM).
• ISCFail: Identifier of command failure signal, of course, belonging to the equipment being
configured at that time. If set to –1 no signal will be issued upon a command failure. If a
valid signal is configured, a signal pulse will be generated upon a command failure [Dir,
ISCFail].
• FormatoMEAs: Indicates whether database measurements are dealt with in 16 bit
INTEGER format (0) or FLOAT format (1).
• Nombre_IP: Name or IP address of the SNMP device associated to the virtual equipment.
This parameter must match the Nombre_IP of the associated SNMP device of the
SRVSNMP.CFG file, as it is the connecting link of both files.
Ex:100,50,49,3,2,1,110,20,2,49,1,128.127.170.233,

M1CPTA2005I
B-285 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on Equipment Digital Signals (ISCs)

They are configured as explained in section A.1. [lines 11-16]

Ex: 50,// Num. ISCs

0,0,1,1,0,0,
1,0,1,1,0,0,
...
49,0,1,1,0,0,

• Data on Equipment Digital Commands (ISE)

They are configured as explained in section A.1. [lines 18-22]

Ex: 3,// Num. ISEs

0,100,-1,500,0,100,-1,100,-1,0,0,
1,100,-1,500,0,100,-1,100,-1,0,0,
2,100,-1,500,0,100,-1,100,-1,0,0,

• Data on Equipment Output Writes (ISS)

They are configured as explained in section A.1. [lines 24-26]. No ISSs have been implemented
by the time being, therefore this value will be set to 0.

Ex: 1,// Num. ISSs

0,100,-1,10000,0,0

• Data on Equipment Measurements (MEA)

They are configured as explained in section A.1. [lines 28-33]

Ex: 110,// Num. MEAs

1.0,0.0,
1.0,0.0,
...
1.0,0.0,

• Data on Equipment Counters (CON)

They are configured as explained in section A.1. [lines 35-40]

Ex: 20,// Num. CONs

1.0,0.0,
...
1.0,0.0,

• Data on Equipment Analog Output Writes (ISM)

They are configured as explained in section A.1. [lines 42-45]

Ex: 2,// Num. ISMs

0,100,-1,
1,100,-1,

M1CPTA2005I
1CPT: Substation Central Unit B-286
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Data on Mapping SNMP Variables to Equipment Database Data: [Lines 50-60]

NumOIDs ,
NombreOID , TipoLect , IdxLect , TipoEscr , IdxEscrOn , IdxEscrOff , ... (*)
… ValorOn , ValorOff , DcoOn , DcoOff ,
(*) It repeats for each SNMP device variable (OID). There will be as many as indicated
by NumOIDs.

• NumOIDs: Number of SNMP device variables (OIDs) to be mapped to database data.

• NombreOID: Name of the SNMP variable. This parameter must match NombreOID of the
corresponding variable of SRVSNMP.CFG file.
• TipoLect: Type of database data that the SNMP variable is mapped to. Available types
are: 1 (signal), 2 (counter), 4 (measurement) and -1 (not used). The value –1 is reserved
for when the read of that SNMP variable is not to be mapped to any database data (e.g.
because the SNMP variable corresponds to a digital or analog command that is not to be
read).
• IdxLect: Signal, measurement or counter label that the SNMP variable is mapped to. For
write only data, it is set to –1.
• TipoEscr: Type of database data where the write of the SNMP variable is mapped.
Available types are: 5 (digital command), 7 (analog command) and -1 (not used). The
value –1 is reserved for when no database data is to be mapped to the write of that
SNMP variable (e.g. because the SNMP variable corresponds to signals, measurements
and counters on which no action may be taken through digital or analog commands).
• IdxEscrOn: Label of the digital command corresponding to the ON option (activation) or
label of the analog command. For read only data, it will be set to –1.
• IdxEscrOff: Label of the digital command corresponding to the OFF option (deactivation).
For analog commands and read only data, it will be set to –1.
• ValorOn: Value of the SNMP variable corresponding to the ON option, both for read
(signals) and write (digital commands). For measurements, counters and analog
commands, it will be set to –1.
• ValorOff: Value of the SNMP variable corresponding to the OFF option, both for read
(signals) and write (digital commands). For measurements, counters and analog
commands, it will be set to –1.
• DcoOn: Value of the DCO of the digital command corresponding to the ON option. For
signals, measurements, counters and analog commands, it will be set to –1.
• DcoOff: Value of the DCO of the digital command corresponding to the OFF option. For
signals, measurements, counters and analog commands, it will be set to –1.

IMPORTANT:
For signals:
- When the associated SNMP variable NombreOID takes the value ValorOn, signal
[Dir,IdxLect] will change to ON status (E=1).
- When the associated SNMP variable NombreOID takes the value ValorOff, signal
[Dir,IdxLect] will change to OFF status (E=0).
- When the associated SNMP variable NombreOID takes neither the value ValorOn nor the
value ValorOff, signal [Dir,IdxLect] will change to OFF status (E=0) and invalid (V=1).
For digital commands:
- When the [Dir,IdxEscrOn] command is run with DcoOn the value ValorOn will be written
to the associated SNMP variable NombreOID.
- When the [Dir,IdxEscrOff] command is run with DcoOff the value ValorOff will be written
to associated SNMP variable NombreOID.

M1CPTA2005I
B-287 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Ex: 157,
.1.3.6.1.4.1.4576.4.6.1.1.1.0, 4, 0,-1,-1,-1,-1,-1,-1,-1,
.1.3.6.1.4.1.4576.4.6.1.1.2.0, 4, 1,-1,-1,-1,-1,-1,-1,-1,
...
.1.3.6.1.4.1.4576.4.6.1.1.28.0, 2, 0,-1,-1,-1,-1,-1,-1,-1,
...
.1.3.6.1.4.1.4576.4.6.1.2.6.0, 4,59, 7, 0,-1,-1,-1,-1,-1,
...
.1.3.6.1.4.1.4576.4.6.1.2.21.0, 1,41, 5, 0, 1, 3, 2, 2, 2,

The file becomes:

[1] # SNMPCLI Configuration

[2] # TimeRefresh,NivelTraza,
[3] 1000,8,
[4] # Number of equipments,
[5] 2,
[6] # *********** Device 1 **************
[7] #
Dir,NºISCs,ISCmax,NºISE,ISEmax,NºISS,ISSmax,NºMEA,NºCON,NºISM,ISCFallo,
[8] # FormatoMEAs,NombreIP,
[9] 100,50,49,3,2,1,0,110,20,2,49,1,128.127.170.233,
[10] # ISCs Number
[11] 50,
[12] # ISC, alarme, f.activa, f.desact, flanco alrm, bocina,
[13] 0,0,1,1,0,0,
[14] 1,0,1,1,0,0,
[15] ...
[16] 49,0,1,1,0,0,// ISC Fail
[17] # ISEs Number
[18] 3,
[19] # ISE,DirExec,ISCExec,Time,Negada,OK,BAD,doble,n blqs,dir,isc,neg,..,
[20] 0,100,-1,500,0,100,-1,100,-1,0,0,
[21] 1,100,-1,500,0,100,-1,100,-1,0,0,
[22] 2,100,-1,500,0,100,-1,100,-1,0,0,
[23] # ISSs Number
[24] 1,
[25] ISS,DirEqEstado,ISCEstado,Time,Neg,Analog?
[26] 0,100,-1,10000,0,0,
[27] # MEAs Number
[27] 110,
[28] # a, b Factors
[29] 1.0,0.0,
[30] 1.0,0.0,
[31] ...
[32] 1.0,0.0,
[33] # CONs Number
[34] 20,
[35] # a, b Factors
[36] 1.0,0.0
[37] 1.0,0.0,
[38] ...
[39] 1.0,0.0,
[40] # ISMs Number
[41] 2,
[42] # ISM,DirEqEstado,MEAEstado,
[43] 0,100,-1,
[44] 1,100,-1,

M1CPTA2005I
1CPT: Substation Central Unit B-288
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

[45] #
[46] # Mapping SNMP Variables
[47] #
[48] # NumOIDs,
[49] 157,
[50] #
NombreOID,TipoLect,IdxLect,TipoEscr,IdxEscrOn,IdxEscrOff,ValorOn,ValorOf
f,
[51] # DcoOn,DcoOff,
[52] .1.3.6.1.4.1.4576.4.6.1.1.1.0, 4, 0,-1,-1,-1,-1,-1,-1,-1,
[53] .1.3.6.1.4.1.4576.4.6.1.1.2.0, 4, 1,-1,-1,-1,-1,-1,-1,-1,
[54] ...
[55] .1.3.6.1.4.1.4576.4.6.1.1.28.0, 2, 0,-1,-1,-1,-1,-1,-1,-1,
[56] ...
[57] .1.3.6.1.4.1.4576.4.6.1.2.6.0, 4,59, 7, 0,-1,-1,-1,-1,-1,
[58] ...
[59] .1.3.6.1.4.1.4576.4.6.1.2.21.0, 1,41, 5, 0, 1, 3, 2, 2, 2,
[60] # *********** DEVICE 2 **************
[61] #
Dir,NºISCs,ISCmax,NºISE,ISEmax,NºISS,ISSmax,NºMEA,NºCON,NºISM,ISCFallo,
[62] # FormatoMEAs,NombreIP,
[63] 101,1,0,0,0,0,0,1,0,0,-1,1,128.127.170.36,
[64] # ISCs Number
[65] 1,
[66] # ISC, alarme, f.activa, f.desact, flanco alrm, bocina,
[67] 0,0,1,1,0,0,
[68] # ISEs Number
[69] 0,
[70] # ISSs Number
[71] 0,
[72] # MEAs Number
[73] 1,
[74] # a, b Factors
[75] 1.0,0.0,
[76] # CONs Number
[77] 0,
[78] # ISMs Number
[79] 0,
[80] #
[81] # Mapping SNMP Variables
[82] #
[83] # NumOIDs,
[84] 2,
[85] #
NombreOID,TipoLect,IdxLect,TipoEscr,IdxEscrOn,IdxEscrOff,ValorOn,ValorOf
f,
[86] # DcoOn,DcoOff,
[87] .1.3.6.1.4.1.4.1.2.0, 4, 0,-1,-1,-1,-1,-1,-1,-1,
[88] .1.3.6.1.4.1.4.1.13.0, 1, 0,-1,-1,-1, 1, 0,-1,-1,

M1CPTA2005I
B-289 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

B.20 Configuration of Substation configuration Server: File

UCSCONEC.INI (1CPT Models)
CPT’s UCSConf module is supported by two sub-modules which cooperate with each other to
offer the function of IEC61850 substation configuration server. One of these sub-modules is part
of the Central Unit application itself and thus resides in the CPT equipment, but the other sub-
module resides in the PC acting as substation WorkStation.

The UCSConf sub-module that resides in the CPT checks through the IEC61850 substation bus
the parameters that keep the parameterization and configuration revisions of each of the
substation IEDs, and also provides the functions to validate and activate a new CID file
previously loaded into the IED. The activation of this CPT sub-module is carried out by including
the line below into the CPT’s PROTASK.CFG configuration file:

0, CONFUCS, CONFUCS, 2048, -1,

Meanwhile, the sub-module of UCSConf (program UCS-Conf.exe) residing outside the CPT will
manage the UCSConf database, and will handle the substation configuration files (SCD file) and
the configuration files of every IED (CID file). Also, it will keep a centralised database in the PC
Workstation with the latest revisions of the substation SCD and CID files.

This sub-module will communicate on the one hand with the sub-module residing in the CPT to
receive in real time parameterisation and configuration data revisions of each IED connected to
the CPT, it will communicate with the UCSConf’s WEB interface attending operator requests
and sending updated data of the UCSConf database, and will connect to IEDs to send or
receive CID configuration files via FTP protocol.

This sub-module uses UCSCONEC.INI configuration file that is segregated into three sections:

• Conexion: this section contains the configuration parameters for the communication
between the two submodules in which the UCSConf is divided, namely, between the
submodule that resides in the CPT and the submodule that resides in the substation
WorkStation.
• BDSCL: this section gathers database parameters of UCSConf CID and SCD files.
• PATH: section that includes the different routes used by the UCSConf.

M1CPTA2005I
1CPT: Substation Central Unit B-290
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

Listed below are the different file parameters:

[Conexion]
Iplocal
Ipremote
Portlocal
Portremote
Timetolive
Log
[BDSCL]
NumMaxCID
NumMaxSCD
UncompressSCD
UncompressCID
[PATH]
Base
Log
UCSConf
XSD
BDSCL
FTP

• [Conexión]: Indicates the beginning of the section that r contains the configuration
parameters for the communication between the UCSConf submodule that resides in the
CPT and the submodule that resides in the substation WorkStation.
• Iplocal: Is the IP address of the WorkStation device where the UCSConf database
manager submodule is installed. If no value is configured for this parameter, the
UCSConf itself will automatically obtain the IP address of the WorkStation.
• Ipremote: Is the IP address of the CPT in which the other UCSConf submodule resides.
• Portlocal: Local TCP port of the WorkStation device used by UCSConf to establish the
TCP-IP connection with the CPT.
• Portremote: TCP port within the CPT that the UCSConf submodule that resides in the
WorkStation is to be connected to.
• Timetolive: Maximum time (in sec.) of inactivity in message exchange between the
UCSConf submodule that resides in the substation WorkStation and the submodule that
resides in the CPT. This time is also applied to the message interchange between the
UCSConf submodule that resides in the substation WorkStation and the UCSConf Web
client.
• Log: Monitoring level of the UCSConf application. There are three levels:0- Without log,
1- Only errors and 2- Errors and general information.
• [BDSCL]: Indicates the beginning of the section that gathers database parameters of
UCSConf CID and SCD files.
• NumMaxCID: Maximum number of CID files that will be saved in the UCSConf database
per IED.
• NumMaxSCD: Maximum number of SCD files that will be saved in the UCSConf
database.
• UncompressSCD: Maximum number of unzipped SCD files in the UCSConf database.
• UncompressCID: Maximum number of unzipped CID files in the UCSConf database per
IED.
• [PATH]: Indicates the beginning of the section that includes the different routes used by
the UCSConf.
• Base: Complete route of the UCSConf database manager base directory.

M1CPTA2005I
B-291 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

• Log: Relative route (to the Base directory) of the directory where Log files generated by
the UCSConf are saved.
• UCSConf: Complete route of the directory the programme UCS-Conf.exe and its
configuration file UCSCONEC.INI belong to.
• XSD: Relative route (to the Base directory) of the directory the diagrams used to validate
SCD and CID files belong to. Hangs from the base.
• BDSCL: Relative route (to the Base directory) of the directory the configuration file
database kept by UCSConf belongs to.
• FTP: Complete route of the base directory of the WorkStation device FTP server.

Ex: [Conexion]
iplocal = 128.127.50.72
ipremote = 128.127.170.28
portlocal = 32005
portremote = 32004
timetolive = 30
Log = 1

[BDSCL]
NumMaxCID = 7
NumMaxSCD = 7
UncompressSCD=3
UncompressCID=3

[PATH]
Base=c:\ucsconf
Log=\log
UCSConf=c:\ucsconf\bin
XSD=\xsd
BDSCL=\bdscl
FTP=c:\DirFTP

M1CPTA2005I
1CPT: Substation Central Unit B-292
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex B. Configuration of Protocol Emulators

The file becomes:

[1] [Conexion]
[2] iplocal = 128.127.50.72
[3] ipremote = 128.127.170.28
[4] portlocal = 32005
[5] portremote = 32004
[6] timetolive = 30
[7] Log = 1
[8]
[9] [BDSCL]
[10] NumMaxCID = 7
[11] NumMaxSCD = 7
[12] UncompressSCD=3
[13] UncompressCID=3
[14]
[15] [PATH]
[16] Base=c:\ucsconf
[17] Log=\log
[18] UCSConf=c:\ucsconf\bin
[19] XSD=\xsd
[20] BDSCL=\bdscl
[21] FTP=c:\DirFTP

M1CPTA2005I
B-293 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex B. Configuration of Protocol Emulators

M1CPTA2005I
1CPT: Substation Central Unit B-294
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
C. Schemes and Drawings

Dimension and Drill Hole Schemes

1CPT (2U x 1 rack) >>4BF0100/0011

External Connection Schemes

1CPT >>3RX0188/0002 (generic)

D. List of Illustrations and Tables
 Annex D. List of Illustrations and Tables

D.1 List of Figures

4. Physical Architecture ........................................................................................ 4-1

Figure 4.1: Front View of a 1CPT. ......................................................................................... 4-2
Figure 4.2: Rear View of a 1CPT. .......................................................................................... 4-3
Figure 4.3: Digital Inputs of the 1CPT. .................................................................................. 4-4
Figure 4.4: Power Supply and Digital Outputs of the 1CPT. ................................................. 4-4

6. Description of Operation .................................................................................. 6-3

Figure 6.1 Device Interrogation Procedure......................................................................... 6-13
Figure 6.2 Example of CIC Integration with the rest of the Substation Devices................. 6-17
Figure 6.3 Values of 1CPT Logic Parameters. ................................................................... 6-18
Figure 6.4 Serial Port Table. ............................................................................................... 6-19
Figure 6.5 Network Interface Configuration Screen. .......................................................... 6-20
Figure 6.6 Connection Configuration Screen. .................................................................... 6-21
Figure 6.7 Control Function Status Flow Chart. ................................................................. 6-36
Figure 6.8 Voltage Presence / Absence Control Function. ................................................ 6-41
Figure 6.9 Control Function for the Definition of High Voltage Statuses. ........................... 6-43
Figure 6.10 Execution of Sequences.................................................................................... 6-48
Figure 6.11 Manoeuvre Execution Procedure. ..................................................................... 6-49
Figure 6.12 Sequence of Medium Voltage Manoeuvres. ..................................................... 6-50
Figure 6.13 Sequence of Switching because of Protection Tripping. ................................... 6-53
Figure 6.14 Voltage Presence / Absence Control Function. ................................................ 6-59
Figure 6.15 Control Function for the Definition of High Voltage Statuses. ........................... 6-61
Figure 6.16 Command Execution. ........................................................................................ 6-68
Figure 6.17 Switching due to Protection Tripping Sequence. .............................................. 6-75
Figure 6.18 Y Control Function. ............................................................................................ 6-79
Figure 6.19 TERAS4 Control Function. ................................................................................ 6-94
Figure 6.20 Operation of the MANDO Logical Operation. .................................................. 6-103
Figure 6.21 Operation of the ESC Logical Operation. ........................................................ 6-104
Figure 6.22 Operation of the Timer. ................................................................................... 6-104
Figure 6.23 Operation of the Range Evaluator. .................................................................. 6-104
Figure 6.24 Command Logic (Example). ............................................................................ 6-108
Figure 6.25 Home Screen of the Web Report Application. ................................................ 6-111
Figure 6.26 Connection Menu. ........................................................................................... 6-112
Figure 6.27 Connection Attempt Error Message. ............................................................... 6-112
Figure 6.28 Correct Connection Message. ......................................................................... 6-112
Figure 6.29 Consultation Date Range Selection. ............................................................... 6-113
Figure 6.30 Message for no Consultation Range Data. ..................................................... 6-113
Figure 6.31 Unloading 1CPT Data. .................................................................................... 6-113
Figure 6.32 Graphic Type Report Configuration Screen. ................................................... 6-114
Figure 6.33 Report Attributes Menu ................................................................................... 6-115
Figure 6.34 Configuring the Elements of the Graphic Type Report. .................................. 6-115
Figure 6.35 Curve Display with no Interpolation. ................................................................ 6-116
Figure 6.36 Curve Display with Interpolation. ..................................................................... 6-117
Figure 6.37 Print Configuration. .......................................................................................... 6-117
Figure 6.38 Acceptance of the Report to be Printed. ......................................................... 6-118
Figure 6.39 Display of the Final Report. ............................................................................. 6-118
Figure 6.40 Configuration of the Chart Type Report. ......................................................... 6-119
Figure 6.41 Chart Type Display of the Measurements Recorded in the 1CPT. ................. 6-119
Figure 6.42 Chart Type Report File Menu. ......................................................................... 6-120
Figure 6.43 Excel Format Export Configuration. ................................................................ 6-120
Figure 6.44 PDF Format Export Configuration. .................................................................. 6-120
Figure 6.45 Export of Chart Type Report to Excel Format. ................................................ 6-121

M1CPTA2005I
1CPT: Substation Central Unit D-2
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex D. List of Illustrations and Tables

Figure 6.46 Export of Chart Type Report to PDF Format. ................................................. 6-121
Figure 6.47 File Menu Options in the Main Tool Bar.......................................................... 6-122
Figure 6.48 Confirm Deletion of the Database. .................................................................. 6-122
Figure 6.49 Confirm Disconnection. ................................................................................... 6-122
Figure 6.50 Hot Standby Redundant System Architecture with IEC61850 Devices. ......... 6-125
Figure 6.51 Assembly Architecture with Level 1 Star Topology. ........................................ 6-126
Figure 6.52 Assembly Architecture with Level 1 Star Topology using CIC. ....................... 6-127
Figure 6.53 Connection through Digital Inputs / Outputs. .................................................. 6-129
Figure 6.54 Primary 1CPT Status Diagram. ....................................................................... 6-132
Figure 6.55 Secondary 1CPT Status Diagram. .................................................................. 6-133

7. Alphanumeric Keypad and Display ................................................................. 7-1

Figure 7.1: Alphanumeric Display. ........................................................................................ 7-2
Figure 7.2: Keypad. ............................................................................................................... 7-2

M1CPTA2005I
D-3 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex D. List of Illustrations and Tables

D.2 List of Tables

6. Description of Operation .................................................................................. 6-3

Table 6-1: Range of Signals of the Virtual Units .................................................................. 6-6
Table 6-2: Frame Format ...................................................................................................... 6-8
Table 6-3: Interrogation Cycle Parameters......................................................................... 6-25
Table 6-4: Data supported by the 1CPT ............................................................................. 6-28
Table 6-5: Resistive Ground Contact Inputs....................................................................... 6-35
Table 6-6: Resistive Ground Contact Inputs....................................................................... 6-35
Table 6-7: Resistive Ground Settings ................................................................................. 6-35
Table 6-8: Resistive Ground Signals .................................................................................. 6-38
Table 6-9: H Control Function Operating Preferences ....................................................... 6-39
Table 6-10: Voltage Presence / Absence Control Functions Measuring Inputs and Logic
Outputs .............................................................................................................. 6-40
Table 6-11: Voltage Presence / Absence Control Functions Settings Margins.................... 6-40
Table 6-12: Definition of High Voltage Status Control Function Inputs ................................ 6-42
Table 6-13: Definition of High Voltage Status Control Function Settings ............................. 6-42
Table 6-14: Definition of High Voltage Status Control Function Outputs ............................. 6-42
Table 6-15: High Voltage Manoeuvres Control Function Inputs........................................... 6-44
Table 6-16: High Voltage Manoeuvres Control Function Sequence Selection .................... 6-46
Table 6-17: Operations of each Sequence ........................................................................... 6-47
Table 6-18: High Voltage Manoeuvres Control Function Settings ....................................... 6-48
Table 6-19: Medium Voltage Manoeuvres Control Function Inputs ..................................... 6-49
Table 6-20: Medium Voltage Manoeuvres Control Function Settings .................................. 6-49
Table 6-21: Medium Voltage Manoeuvres Control Function Sequence Selection ............... 6-51
Table 6-22: Switching due to Protection Tripping Control Function Inputs .......................... 6-52
Table 6-23: Switching due to Protection Tripping Control Function Maneouvre Selection .. 6-52
Table 6-24: H Control Function Digital Signals..................................................................... 6-54
Table 6-25: H Control Function Commands ......................................................................... 6-55
Table 6-26: H Control Function External Signals ................................................................. 6-56
Table 6-27: H2 Control Function Operating Preferences ..................................................... 6-57
Table 6-28: Voltage Presence / Absence Control Functions Measuring Inputs and Logic
Outputs .............................................................................................................. 6-58
Table 6-29: Voltage Presence / Absence Control Functions Settings Margins.................... 6-58
Table 6-30: Definition of High Voltage Status Control Function Inputs ................................ 6-60
Table 6-31: Definition of High Voltage Status Control Function Settings ............................. 6-60
Table 6-32: Definition of High Voltage Status Control Function Outputs ............................. 6-60
Table 6-33: High Voltage Manoeuvres Control Function Inputs........................................... 6-62
Table 6-34: High Voltage Manoeuvres Control Function Sequence Selection .................... 6-64
Table 6-35: Type of Commands ........................................................................................... 6-66
Table 6-36: High Voltage Manoeuvres Control Function Settings ....................................... 6-67
Table 6-37: Input Signals of the Protection Trip Switching Control Function ....................... 6-70
Table 6-38: Protection Trip Switching Control Function Command Selection ..................... 6-71
Table 6-39: H Control Function Digital Signals..................................................................... 6-76
Table 6-40: H Control Function Commands ......................................................................... 6-77
Table 6-41: H Control Function External Signals ................................................................. 6-77
Table 6-42: Y Control Function Inputs Signals (I)................................................................. 6-79
Table 6-43: Y Control Function Sequence Selection (I) ....................................................... 6-80
Table 6-44: Y Control Function Operations .......................................................................... 6-81
Table 6-45: Y Control Function Inputs Signals (II) ............................................................... 6-81
Table 6-46: Y Control Function Sequence Selection (II) ...................................................... 6-81
Table 6-47: Switching Due to Protection Tripping Control Function Input Signals............... 6-82
Table 6-48: Switching Due to Protection Tripping Control Function Sequence Selection ... 6-82
Table 6-49: UCERAS1 Statuses .......................................................................................... 6-83
Table 6-50: UCERAS1 Contact Inputs ................................................................................. 6-83

M1CPTA2005I
1CPT: Substation Central Unit D-4
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 Annex D. List of Illustrations and Tables

Table 6-51: UCERAS1 Contact Outputs .............................................................................. 6-83

Table 6-52: UCERAS1 Commands ...................................................................................... 6-84
Table 6-53: UCERAS1 Flow Chart ....................................................................................... 6-84
Table 6-54: UCERAS2 Statuses .......................................................................................... 6-84
Table 6-54: UCERAS2 Statuses .............................................................................................. 6-85
Table 6-55: UCERAS2 Contact Inputs ................................................................................. 6-85
Table 6-56: UCERAS2 Contact Outputs .............................................................................. 6-85
Table 6-57: UCERAS2 Commands ...................................................................................... 6-85
Table 6-58: UCERAS2 Settings ........................................................................................... 6-86
Table 6-59: UCERAS2 Flow Chart ....................................................................................... 6-86
Table 6-60: UCERAS3 Statuses .......................................................................................... 6-87
Table 6-61: UCERAS3 Contact Inputs ................................................................................. 6-87
Table 6-62: UCERAS3 Contact Outputs .............................................................................. 6-87
Table 6-63: UCERAS3 Commands ...................................................................................... 6-87
Table 6-64: UCERAS3 Settings ........................................................................................... 6-87
Table 6-65: UCERAS3 Flow Chart ....................................................................................... 6-87
Table 6-66: TERAS1 Statuses ............................................................................................. 6-88
Table 6-67: TERAS1 Contact Inputs .................................................................................... 6-88
Table 6-68: TERAS1 Contact Outputs ................................................................................. 6-88
Table 6-69: TERAS1 Commands ......................................................................................... 6-88
Table 6-70: TERAS2 Statuses ............................................................................................. 6-89
Table 6-71: TERAS2 Contact Inputs .................................................................................... 6-89
Table 6-72: TERAS2 Contact Outputs ................................................................................. 6-90
Table 6-73: TERAS2 other signals used .............................................................................. 6-90
Table 6-74: TERAS2 Commands issued by the terminal..................................................... 6-90
Table 6-75: TERAS2 Commands received by the terminal ................................................. 6-90
Table 6-76: TERAS2 Settings .............................................................................................. 6-91
Table 6-77: TERAS2 Flow Chart .......................................................................................... 6-91
Table 6-78: TERAS3 Statuses ............................................................................................. 6-92
Table 6-79: TERAS3 Contact Inputs .................................................................................... 6-92
Table 6-80: TERAS3 Contact Outputs ................................................................................. 6-92
Table 6-81: TERAS4 Statuses ............................................................................................. 6-93
Table 6-82: TERAS4 Contact Inputs .................................................................................... 6-93
Table 6-83: TERAS4 Contact Outputs ................................................................................. 6-93
Table 6-84: ERAS Own Signals ........................................................................................... 6-94
Table 6-85: Signals for each terminal................................................................................... 6-95
Table 6-86: ERAS Commands ............................................................................................. 6-96
Table 6-87: ERAS External Signals ..................................................................................... 6-96
Table 6-88: Virtual Central Equipment Digital Signals ......................................................... 6-97
Table 6-89: Virtual Central Equipment Commands .............................................................. 6-99
Table 6-90: Virtual Central Equipment Output Writes ........................................................ 6-100
Table 6-91: Input and Output Variables for Logical Operations ......................................... 6-100
Table 6-92: OR Truth Table ............................................................................................... 6-101
Table 6-93: AND Truth Table ............................................................................................. 6-102
Table 6-94: XOR Truth Table ............................................................................................. 6-102
Table 6-95: NOT Truth Table ............................................................................................. 6-102
Table 6-96: CABLE Truth Table ......................................................................................... 6-102
Table 6-97: FFRS Truth Table ........................................................................................... 6-102
Table 6-98: FFJK Truth Table ............................................................................................ 6-103
Table 6-99: DEACT Truth Table (Particular Case of 3 Inputs)........................................... 6-105
Table 6-100: CONT Truth Table........................................................................................... 6-105

M1CPTA2005I
D-5 1CPT: Substation Central Unit
© ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
Annex D. List of Illustrations and Tables

M1CPTA2005I
1CPT: Substation Central Unit D-6
 ZIV APLICACIONES Y TECNOLOGÍA, S.L.U. Zamudio, 2020
 License agreement for Software Embedded in Equipment

ZIV APLICACIONES Y TECNOLOGÍA, S.L.

End-User Software License Agreement

THE EQUIPMENT YOU HAVE PURCHASED INCLUDES EMBEDDED SOFTWARE

PROGRAM(S). THE PROGRAM IS COPYRIGHTED AND IS BEING LICENSED TO
YOU (NOT SOLD) FOR USE WITH THE EQUIPMENT.

THIS IS A LEGAL AGREEMENT BETWEEN US (AS “LICENSEE) AND ZIV

APLICACIONES Y TECNOLOGIA, S.L. (AS “LICENSOR”) FOR THE SOFTWARE
PROGRAM INCLUDED WITH THE EQUIPMENT. PLEASE READ THE TERMS AND
CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE USING THE
EQUIPMENT.

IF YOU INSTALL OR USE THE EQUIPMENT, 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 EQUIPMENT UNUSED TO YOUR SELLER, AND
YOU WILL RECEIVE A REFUND OF YOUR MONEY.

Terms and Conditions of License

1. License Grant. Licensor hereby grants to you, and your accept, a nonexclusive and non-
transferable license to use the embedded programs and the accompanying documentation, if any
(collectively referred to as the “Software”), only as authorized in this License Agreement.
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. No Assignment. This License is intended for your exclusive use with the purchased equipment.
You agree that you will not assign, sublicense, transfer, pledge, lease, rent or share your rights
under this License Agreement.
4. Licensor’s Rights. You acknowledge and agree that the Software is the proprietary product of
Licensor protected under U.S. copyright law and international 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 ownership interest in or to the Software, but only a
limited right of use revocable in accordance with the terms of this License Agreement.
5. 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. For the
purposes of this clause, sub-contract staff, employed or retained by the Licensee to perform
computer systems development work, shall not be deemed to be third parties provided such staff
are subject to the disclosure restrictions set forth above. In no event, except with a prior written
authorization duly signed by an officer of Licensor, may you disclose any such confidential
information, even for subcontracted jobs, to persons or entities that may be considered to be
direct competitors of Licensor.
6. Term. The License Agreement is effective upon delivery of the equipment to you and shall
continue until terminated. You may terminate this License Agreement at any time by returning
the equipment to Licensor, or by destroying the equipment. Licensor may terminate this License
Agreement upon your breach of any term hereof. Upon such termination by Licensor, you agree
to return the equipment to Licensor.
7. Warranty and Disclaimer. Licensor warrants, for your benefit only, that the Software, when
and as delivered to you, will conform to the specifications described in the instruction manuals
for the equipment purchased, or any specifications agreed to in writing by Licensor with a
particular customer. This warranty does not cover any minor errors or deviations from the
specifications that do not affect the proper functioning of the equipment. EXCEPT FOR THE
WARRANTIES SET FORTH ABOVE, THE SOFTWARE IS LICENSED “AS IS”, AND
LICENSOR DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER
EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
8. Licensee’s Remedy. You sole and exclusive remedy for any breach of Licensor’s warranty
shall be the repair or replacement, at Licensor’s sole option, of any Software that does not
conform to stated specifications. Licensor shall not be responsible for any failure arising from
inadequate or improper use of the Software.
9. Limitation of Liability. Licensor’s cumulative liability to you or any other party for any loss or
damages resulting from any claims, demands, or actions arising out of or relating to this
Agreement shall not exceed the purchase price paid to Licensor for the equipment. 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. All ZIV trademarks (including ZIVERCOM, ZIVERLOG and ZIVERSYS) are
common law trademarks of Licensor. No right, license or interest to such trademarks 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 the State of Illinois, U.S.A.
13. No Waiver. The failure of either party to enforce any rights granted 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 signed by an
officer of Licensor.

ZIV Aplicaciones y Tecnología, S.L.

Parque Tecnológico, 2089
48016 Zamudio (Bizkaia)
48080 Bilbao
Spain