Ume Ingepac Ef CD Eng

CONTROL AND MEASUREMENT DEVICES
INGEPAC EF-CD
User Manual
UME_INGEPAC_CD_eng Rev. I (11/19)
© All rights reserved. No part of this publication

may be reproduced, by whatever means, without
the prior written permission of Ingeteam
Technology.
Ingeteam Power Technology reserves the right to

make changes without prior notice.
INDEX 
1. GENERAL DESCRIPTION ............................................................................................................................ 9

1.1 FUNCTIONAL DESCRIPTION ...................................................................................................................................... 9
1.2 MODEL ENCODING ................................................................................................................................................ 10
1.3 USER INTERFACE .................................................................................................................................................... 12
1.4 INTERCONNECTIONS .............................................................................................................................................. 12
1.4.1 CPU ...................................................................................................................................................................... 12
1.4.2 Power supply ....................................................................................................................................................... 13
1.4.3 Input/output cards .............................................................................................................................................. 13
1.4.4 Analogue inputs .................................................................................................................................................. 16
2. HARDWARE...................................................................................................................................... 27
2.1 CONSTRUCTION FEATURES .................................................................................................................................... 27
2.1.1 Half chassis (½ 19”) ............................................................................................................................................. 27
2.1.2 19” chassis ........................................................................................................................................................... 28
2.2 REAR TERMINALS................................................................................................................................................... 28
2.2.1 Configuration options ......................................................................................................................................... 28
2.2.2 Half chassis (½ 19”) ............................................................................................................................................. 28
2.2.3 19” chassis ........................................................................................................................................................... 29
2.2.1 Closed Terminals ................................................................................................................................................. 31
2.2.2 Wire section ........................................................................................................................................................ 31
2.3 FRONT INTERFACE ................................................................................................................................................. 31
2.3.1 Half chassis (½ 19”) ............................................................................................................................................. 31
2.3.2 19” chassis ........................................................................................................................................................... 32
2.4 TECHNICAL CHARACTERISTICS ............................................................................................................................... 33
2.4.1 Power supply voltage .......................................................................................................................................... 33
2.4.2 Digital outputs ..................................................................................................................................................... 33
2.4.3 Digital inputs ....................................................................................................................................................... 34
2.4.4 IRIG-B input and PPS ........................................................................................................................................... 35
2.4.5 Analogue ouputs ................................................................................................................................................. 35
2.4.6 RTD Inputs ........................................................................................................................................................... 36
2.4.7 Current and voltage circuits ................................................................................................................................ 36
2.4.8 Front communication .......................................................................................................................................... 37
2.4.9 Rear communications ......................................................................................................................................... 37
2.5 ENVIRONMENTAL CONDITIONS ............................................................................................................................. 39
2.5.1 Tropicalized ......................................................................................................................................................... 39
2.6 TESTS ..................................................................................................................................................................... 39
2.6.1 Climatic test ........................................................................................................................................................ 39
2.6.2 Insulation and electrical safety tests ................................................................................................................... 39
2.6.3 Mechanical tests ................................................................................................................................................. 39
2.6.4 Electromagnetic tests.......................................................................................................................................... 40
3. MEASUREMENT ............................................................................................................................... 41
3.1 38BMeasurements depending on wiring procedures ............................................................................................ 45
3.1.1 Connection Type A .............................................................................................................................................. 45
3.1.2 Connection Type B .............................................................................................................................................. 45
3.1.3 Connection Type D .............................................................................................................................................. 46
3.1.4 Connection Type E .............................................................................................................................................. 46
3.1.5 Connection Type F ............................................................................................................................................... 47
3.1.6 Connection Type G .............................................................................................................................................. 48
3.2 16BEnergy counterS .............................................................................................................................................. 48
4. AUTOMATISMS ................................................................................................................................ 49
4.1 SYNCHRONISM ...................................................................................................................................................... 49
4.1.1 Undervoltage permission .................................................................................................................................... 51
Ingeteam Power Technology S.A.

User Manual III
INDEX 
4.1.2 Synchronism permission ..................................................................................................................................... 51

5. MONITORING ................................................................................................................................... 56
5.1 EXTERNAL POWER SUPPLY MONITORING .............................................................................................................. 56
5.2 TEMPERATURE MONITORING ................................................................................................................................ 57
5.3 DIS BLOCKING BY LACK OF VAUX ........................................................................................................................... 58
5.4 INTERNAL BATTERY FAILURE MONITORING ........................................................................................................... 58
5.5 UNIT CHECKS ......................................................................................................................................................... 59
6. CONFIGURATION .............................................................................................................................. 62
6.1 CID ......................................................................................................................................................................... 62
6.1.1 Data Storage ........................................................................................................................................................ 62
6.1.2 Updating CID ....................................................................................................................................................... 62
6.2 GENERAL................................................................................................................................................................ 62
6.3 FRECUENCY, MEASUREMENT AND TRANSFORMERS .............................................................................................. 64
6.3.1 Current ................................................................................................................................................................ 64
6.3.2 Frequency and voltage ........................................................................................................................................ 64
6.3.3 Power and energy ............................................................................................................................................... 65
6.4 INPUTS/OUTPUTS .................................................................................................................................................. 65
6.4.1 Inputs .................................................................................................................................................................. 65
6.4.2 Outputs ............................................................................................................................................................... 66
6.4.3 Treatment of digital input flicker ........................................................................................................................ 67
6.5 LEDS....................................................................................................................................................................... 67
6.5.1 Via GEN/IHMI node ............................................................................................................................................. 67
6.5.2 Via CTRL/IHMI node ............................................................................................................................................ 68
6.6 CONFIGURATION WITH INREF ............................................................................................................................... 68
6.7 GENERIC COMMAND ............................................................................................................................................. 68
6.8 NAMES .................................................................................................................................................................. 69
6.9 IPRV nodes configuration ...................................................................................................................................... 69
6.9.1 General IPRV settings .......................................................................................................................................... 69
6.9.2 IEC 61850 clients IPRV settings ........................................................................................................................... 70
6.10 Measurement’s range automatic configuration ................................................................................................... 71
7. SYNCHRONIZATION .......................................................................................................................... 73
7.1 GENERAL SETTINGS................................................................................................................................................ 73
7.2 IEEE 1588v2 ........................................................................................................................................................... 75
7.2.1 Settings ................................................................................................................................................................ 75
7.3 IRIG-B .................................................................................................................................................................... 75
7.4 SNTP ...................................................................................................................................................................... 75
7.4.1 Settings ................................................................................................................................................................ 76
7.5 QUALITY FLAGS IEC 61850 ..................................................................................................................................... 79
8. DATA ACQUISITION FUNCTIONS ....................................................................................................... 80
8.1 STATUS REPORT ..................................................................................................................................................... 80
8.2 PRIMARY MEASUREMENTS REPORT ...................................................................................................................... 81
8.3 INCIDENT REPORT .................................................................................................................................................. 83
8.4 HISTORICAL MEASUREMENT REPORT .................................................................................................................... 84
8.5 MAXIMETER/MINIMETER REPORT ......................................................................................................................... 85
8.6 OSCILLOGRAPHY .................................................................................................................................................... 86
8.7 DISPLAY ................................................................................................................................................................. 89
9. USB ACCESS...................................................................................................................................... 93
9.1 DOWNLOADING REPORTS ..................................................................................................................................... 93
9.2 LOADING CID ......................................................................................................................................................... 94
9.3 LOADING FIREWALL CONFIGURATION ................................................................................................................... 94

User Manual IV
INDEX 
9.4 FIRMWARE UPDATE............................................................................................................................................... 94

9.5 USB ENABLING ....................................................................................................................................................... 95
10. FTP ACCESS ...................................................................................................................................... 96
10.1 ACCESS CONTROL ................................................................................................................................................ 97
11. MAPPING THE UNIT’S SIGNALS, MEASUREMENTS AND METERS ........................................................ 98
11.1 SIGNALS ............................................................................................................................................................... 98
11.1.1 Type A signals .................................................................................................................................................... 98
11.1.2 Type B signals .................................................................................................................................................... 99
11.1.3 Type C signals .................................................................................................................................................. 100
11.1.4 Type D signals .................................................................................................................................................. 101
11.2 MEASUREMENTS ............................................................................................................................................... 102
11.3 COUNTERS ......................................................................................................................................................... 104
12. LOGICS ........................................................................................................................................... 105
12.1 CONTROL LOGICS ............................................................................................................................................... 105
12.2 PROTECTION LOGICS .......................................................................................................................................... 106
12.3 DATABASE SIGNALS ........................................................................................................................................... 107
12.4 output data upon power-up .............................................................................................................................. 107
13. IEC 61850 COMMANDS.............................................................................................................. 110
13.1 RUNNING IEC 61850 COMMANDS ............................................................................................................. 110
13.1.1 DIRECT_WITH_NORMAL_SECURITY (1) .......................................................................................................... 113
13.1.2 SBO_WITH_NORMAL_SECURITY (2) ............................................................................................................... 113
13.1.3 DIRECT_WITH_ENHANCED_SECURITY (3) ....................................................................................................... 114
13.1.4 SBO_WITH_ENHANCED_SECURITY (4) ............................................................................................................ 114
13.2 COMMAND BLOCKS .................................................................................................................................... 116
13.2.1 Command blocks by inconsistent parameters ........................................................................................ 116
13.2.2 Command blocks by switching hierarchy ................................................................................................ 116
13.2.3 Command 1 of n blocks.............................................................................................................................. 121
13.2.4 Command blocks by mode (Mod/Beh) ..................................................................................................... 121
13.2.5 Command blocks by Heatlh ....................................................................................................................... 122
13.2.6 Command blocks by Interlocking .............................................................................................................. 122
13.2.7 Commands blocks due to invalid/reached position ................................................................................ 122
13.3 COMMANDs for other positions ................................................................................................................. 123
13.4 COMMAND SADDRESS ............................................................................................................................... 123
14. RIO MODULES ................................................................................................................................ 125
14.1 CONFIGURATION ............................................................................................................................................... 125
14.2 OPERATION ....................................................................................................................................................... 125
15. CHANGES REQUIRING THE REBOOTING OF THE DEVICE ................................................................... 127
16. RECEPTION GOOSES ....................................................................................................................... 128
16.1 GOOSE SUBSCRIPTION .............................................................................................................................. 128
16.2 GOOSE SIMULATION .......................................................................................................................................... 129
16.3 TEST MODE ................................................................................................................................................... 131
16.3.1 Logical devices management hierarchy .................................................................................................. 131
16.4 SERVICE TRACKING .................................................................................................................................... 132
16.5 SUBSTITUTION MODEL ............................................................................................................................... 135
16.6 FILE TRANSFER ................................................................................................................................................... 136
16.7 EDITION1 SUBSCRIPTION. LGOS MODEL. ........................................................................................................... 136
16.7.1 Configuration values ....................................................................................................................................... 137
16.7.2 Supervision values ........................................................................................................................................... 138
16.7.3 Checked values ................................................................................................................................................ 138

User Manual V
INDEX 
17. TCP/IP NEWORK CONFIGURATION .................................................................................................. 139

17.1 DESCRIPTION ..................................................................................................................................................... 139
17.2 COMMUNICATIONS REDUNDANCY .................................................................................................................... 140
17.2.1 PARALLEL REDUNDANCY PROTOCOL (PRP) ..................................................................................................... 140
17.2.2 HIGH-AVAILABILITY SEAMLESS REDUNDANCY (HSR) ...................................................................................... 140
17.2.3 SWITCH MODE ................................................................................................................................................ 141
17.2.4 LINK FAILOVER REDUNDANCY ......................................................................................................................... 141
17.3 GENERAL CONSIDERATIONS ABOUT NETWORK CONFIGURATION ..................................................................... 141
17.4 GOOSES ............................................................................................................................................................. 142
17.5 FIREWALL ........................................................................................................................................................... 142
18. KEYBOARD AND GRAPHIC DISPLAY ................................................................................................. 143
18.1 GENERAL OPERATION ........................................................................................................................................ 143
18.1.1 Display structure ............................................................................................................................................. 143
18.1.2 Organization of the pages ............................................................................................................................... 143
18.1.3 Treatment of the functional keys .................................................................................................................... 144
18.1.4 Graphics pages ................................................................................................................................................ 146
18.1.5 I/O pages ......................................................................................................................................................... 148
18.1.6 Event pages ..................................................................................................................................................... 149
18.1.7 Protection event pages ................................................................................................................................... 150
18.1.8 Alarm pages .................................................................................................................................................... 151
18.1.9 Device status pages ......................................................................................................................................... 152
18.1.10 Fault pages .................................................................................................................................................... 156
18.1.11 Measurement pages ..................................................................................................................................... 160
18.1.12 Menu to other screens page ......................................................................................................................... 162
18.1.13 Shortcut menu page ...................................................................................................................................... 163
18.2 CONTROL AND PROTECTION MENUS PAGES ...................................................................................................... 164
18.2.1 Operation of the menus .................................................................................................................................. 164
18.2.2 Password management ................................................................................................................................... 169
18.3 NETWORK CONFIGURATION .............................................................................................................................. 171
18.3.1 Ethernet Configuration ................................................................................................................................... 171
18.3.2 Gateway Configuration ................................................................................................................................... 175
18.4 OTHER SCREENS ................................................................................................................................................. 177
18.4.1 Contrast setting ............................................................................................................................................... 177
18.4.2 USB treatment................................................................................................................................................. 177
18.4.3 System Information ......................................................................................................................................... 178
18.4.4 CID validation .................................................................................................................................................. 179
18.4.5 Security Logs ................................................................................................................................................... 179
18.4.6 Test Screens .................................................................................................................................................... 179
18.4.7 Other Communications Menu Screens ........................................................................................................... 180
19. WEB APPLICATION ......................................................................................................................... 181
19.1 Introduction....................................................................................................................................................... 181
19.2 WEB application login ........................................................................................................................................ 181
19.2.1 Login ................................................................................................................................................................ 181
19.3 Tabs ................................................................................................................................................................... 182
19.3.1 Reports ............................................................................................................................................................ 182
19.3.2 Settings............................................................................................................................................................ 185
19.3.3 Maintenance ................................................................................................................................................... 186
19.3.4 SW/Configuration ........................................................................................................................................... 187
19.3.5 Logout ............................................................................................................................................................. 188
20. DNP PROTOCOL.............................................................................................................................. 189
20.1 INTRODUCTION ................................................................................................................................................. 189

User Manual VI
INDEX 
20.2 CONFIGURATION SETTINGS ............................................................................................................................... 189

20.3 TABLES ............................................................................................................................................................... 194
20.3.1 Digital status table .......................................................................................................................................... 194
20.3.2 Analog values table ......................................................................................................................................... 194
20.3.3 Counters table ................................................................................................................................................. 195
20.3.4 Commands table ............................................................................................................................................. 195
20.4 DEVICE PROFILE ................................................................................................................................................. 197
20.4.1 OBJECT TABLE.................................................................................................................................................. 198
21. IEC 60870-5-103 PROTOCOL ............................................................................................................ 200
21.1 INTRODUCTION ................................................................................................................................................. 200
21.3 Tables ................................................................................................................................................................ 203
21.3.1 Digital signals table ......................................................................................................................................... 203
21.3.2 Measurements table ....................................................................................................................................... 204
21.3.3 Commands table ............................................................................................................................................. 204
22. SLAVE PROCOME PROTOCOL .......................................................................................................... 205
22.1 INTRODUCTION ................................................................................................................................................. 205
22.3 TABLES ............................................................................................................................................................... 207
22.3.1 Digital status table .......................................................................................................................................... 207
22.3.2 Analog values table ......................................................................................................................................... 207
22.3.3 Counters table ................................................................................................................................................. 208
22.3.4 Commands table ............................................................................................................................................. 208
23. MODBUS MASTER PROTOCOL ........................................................................................................ 209
23.1 INTRODUCTION ................................................................................................................................................. 209
23.3 DATA TYPES ....................................................................................................................................................... 211
23.3.1 Digital signals .................................................................................................................................................. 211
23.3.2 Measurements ................................................................................................................................................ 211
23.3.3 Counters .......................................................................................................................................................... 212
23.3.4 Commands ...................................................................................................................................................... 212
23.3.5 Request of events to Ingeteam Power Technology devices ........................................................................... 212
23.3.6 Synchronization ............................................................................................................................................... 212
23.4 IMPLEMENTED FUNCTIONS ............................................................................................................................... 213
23.5 RTU TYPES ......................................................................................................................................................... 213
23.6 SW CONFIGURATION TOOL ................................................................................................................................ 214
23.6.1 Fields to be configured .................................................................................................................................... 214
23.6.2 Configuration example .................................................................................................................................... 221
23.7 SERIAL MESSAGES .............................................................................................................................................. 224
23.7.1 Format ............................................................................................................................................................. 224
23.7.2 Examples ......................................................................................................................................................... 225
24. MODBUS SLAVE PROTOCOL ............................................................................................................ 229
24.1 INTRODUCTION ................................................................................................................................................. 229
24.3 PROTOCOL PROFILE ........................................................................................................................................... 232
24.3.1 Implemented functions in Modbus RTU ......................................................................................................... 232
24.3.2 Implemented functions in Modbus TCP/IP ..................................................................................................... 232
24.3.3 Exception codes .............................................................................................................................................. 233
24.4 CONTROL PROCESSES ........................................................................................................................................ 233
24.4.1 Request for equipment status ........................................................................................................................ 233
24.4.2 Request for digital signals ............................................................................................................................... 233

User Manual VII
INDEX 
24.4.3 Request for measurements and counters....................................................................................................... 233

24.4.4 Request for digital signal changes ................................................................................................................... 234
24.4.5 Requesting data via memory map .................................................................................................................. 235
24.4.6 Synchronization ............................................................................................................................................... 236
24.4.7 Command execution ....................................................................................................................................... 236
24.5 EQUIPMENT ADDRESS MAP ............................................................................................................................... 236
24.6 DATA FORMAT ................................................................................................................................................... 238
24.7 CONFIGURATION SOFTWARE TOOL ................................................................................................................... 239
24.7.1 Fields to be configured .................................................................................................................................... 239
24.7.2 Configuration example .................................................................................................................................... 242
24.8 SERIAL MESSAGES .............................................................................................................................................. 244
24.8.1 Format ............................................................................................................................................................. 244
24.8.2 Examples ......................................................................................................................................................... 245
24.9 TCP/IP MESSAGES .............................................................................................................................................. 249
24.9.1 Format ............................................................................................................................................................. 249
24.9.2 Examples ......................................................................................................................................................... 250
25. MEASUREMENT LIST....................................................................................................................... 251
26. PREVENTIVE MAINTENANCE ........................................................................................................... 256
26.1 ERROR DETECTION ............................................................................................................................................. 257
26.2 ERROR HANDLING PROCEDURE ......................................................................................................................... 258
27. PROTECTION DEVICES WITH SAMPLED VALUES ............................................................................... 259
27.1 DEVICE MODELS................................................................................................................................................. 260
27.2 PUBLISHERS DECLARATION ................................................................................................................................ 260
27.3 SAMPLED VALUES SUBSCRIPTION ...................................................................................................................... 260
27.3.1 Configuration .................................................................................................................................................. 260
27.3.2 ADD-IN of subscription .................................................................................................................................... 261
27.3.3 Monitoring ...................................................................................................................................................... 263
27.4 CONFIGURABLE LOCAL MEASURES .................................................................................................................... 265
27.5 SAMPLED VALUES SIMULATION ......................................................................................................................... 265
27.6 TEST MODE FOR SAMPLED VALUES ................................................................................................................... 266
27.7 BEHAVIOUR WITH LOSS OF SYNCHRONIZATION ................................................................................................ 266

User Manual VIII
GENERAL DESCRIPTION 
1. GENERAL DESCRIPTION
1.1 FUNCTIONAL DESCRIPTION
Table 1 shows the features and measurements available.
Table 1 Functions
Functions and measurements

Frequency
Line phase voltages (phase and mean)
Line to line voltages (combination of phase and mean)
Current sequences
Harmonic distortion (phase THD and mean THD)
Neutral line-phase current
Neutral harmonic distortion
Active power (signed)
Reactive power (signed)
Apparent power
Active energy counter (positive and negative)
Active energy counter (positive and negative)
Power factor (signed)
Maximum and minimum counters
Oscillography
Historical reports
Phase currents and voltages are measured with 0.2 class precision (by IEC688:1992). Reference conditions for this class are:
V (measured) VN  2%
F FN 0,1 %
Waveform Sinusoidal, distortion factor  0,2
Power factor 1,0.........0,8 inductive o capacitive
Temperature 23ºC  2ºC
V supply  1%
Influence of environmental conditions:
Magnitude Tolerance Variation in % referred to the class

Temperature - 10ºC/55ºC 100%
Frecuency FN  10% 100%
Voltage VN  20% 50%
Power factor +0,5...1...+0,5 50%
Waveform distortion factor 0,2 200%

User Manual 9
1.2 MODEL ENCODING
COM1
COM2
COM3
COM4
COM5
COM6
ETH1
ETH2
I/O 1
I/O 2
I/O 3
I/O 4
I/O 5
I/O 6
I/O 7
I/O 8
INGEPAC EF CD MODEL C D B - - -
MODEL
Control 0
Control + Measurement 1
Control + Measurement + Synchronism 2
HOUSING
1/2 chassis 19" 5U with configurable keyboard A
1/2 chassis 19" 5U with predefined keyboard B
Chassis 19" 4U with configurable keyboard C
Chassis 19" 4U with predefined keyboard D
POWER SUPPLY MODULE

Single PS 85-300 Vdc+ 6DI 125 Vdc + 4DO A
Single PS 85-300 Vdc+ 6DI 220 Vdc + 4DO B
Single PS 18-60 Vdc+ 6DI 24 Vdc + 4DO C
Single PS 18-60 Vdc+ 6DI 48 Vdc + 4DO D
Redundant PS 48 Vcc / 48Vcc F
Redundant PS 125 Vcc / 125Vcc G
REAR SERIAL COMMUNICATION PORT

A GFO COM-1
B PFO COM-2
C RS232C COM-3
D RS485 COM-4
X No port COM-5
COM-6
REAR ETHERNET COMMUNICATION PORT

E GFO ETH-1
F RJ45 ETH-2
I GFO (Link failover redundancy) Note 7
J RJ45 (Link failover redundancy) Note 7
K LC (Link failover redundancy) Note 7
L LC
O LC (ETH with PRP/HSR/Switch) Note 8
P RJ45 (ETH with PRP/HSR/Switch) Note 8
X No port
TERMINALS
Pin type standard terminals A
Closed terminals Note 1 B
Closed terminals for analog inputs and pin type terminals for the rest C
I/O BOARD CONFIGURATION

BOARD SELECTION (Note 2)
-A No board Board 2
-B 11 DI (24Vdc) + 9 DO Board 3
-C 11 DI (48Vdc) +9 DO Board 4 (Note 3)
-D 11 DI (125 Vdc) + 9 DO Board 5 (Note 4)
-E 11 DI (220 Vdc) + 9 DO Board 6 (Note 4)
-F 32 DI (24Vdc) Note 9 Board 7 (Note 4)
-G 32 DI (48Vdc) Note 9 Board 8 (Note 5)
-H 32 DI (125 Vdc) Note 9
-I 32 DI (220 Vdc) Note 9
-J 16 DI (24Vdc)-8 independent DO
-K 16 DI (48Vdc)-8 independent DO
-L 16 DI (125 Vdc)-8 independent DO
-M 16 DI (220 Vdc)-8 independent DO
-N 16 DI (24 Vdc)- 16 DO
-O 16 DI (48Vdc)- 16 DO
-P 16 DI (125 Vdc)- 16 DO
-Q 16 DI (220 Vdc)- 16 DO
-R 16 DI (24Vdc)-8 AI Note 6
-S 16 DI (48Vdc)-8 AI Note 6
-T 16 DI (125 Vdc)-8 AI Note 6
-U 16 DI (220 Vdc)-8 AI Note 6
-V 16 DI (24 Vdc)- 8 AI (4 isolated) Note 6
-W 16 DI (48Vdc)- 8 AI (4 isolated) Note 6
-X 16 DI (125 Vdc)- 8 AI (4 isolated) Note 6
-Y 16 DI (220 Vcc)- 8 AI (4 isolated) Note 6
-0 8DI (24Vcc) + 4DO (h.b.c.o.) + 4DO
-1 8DI (48Vcc) + 4DO (h.b.c.o.) + 4DO
-2 8DI (125Vcc) + 4DO (h.b.c.o.) + 4DO
-3 8DI (220Vcc) + 4DO (h.b.c.o.) + 4DO
-4 8DI (24Vcc) + 8DO
-5 8DI (48Vcc) + 8DO
-6 8DI (125Vcc) + 8DO
-7 8DI (220Vcc) + 8DO
-8 11 RTD + 4 AO Note 11
ZB 8DI (24Vcc) + 4DO (fast+h.b.c.o.) + 4DO Note 10
ZC 8DI (48Vcc) + 4DO (fast+h.b.c.o.) + 4DO Note 10
ZD 8DI (125Vcc) + 4DO (fast+h.b.c.o.) + 4DO Note 10
ZE 8DI (220Vcc) + 4DO (fast+h.b.c.o.) + 4DO Note 10
ZF 8ED (24Vcc) + 8SD (h.b.c.o.)
ZG 8ED (48Vcc) + 8SD (h.b.c.o.)
ZH 8ED (125Vcc) + 8SD (h.b.c.o.)
ZI 8ED (220Vcc) + 8SD (h.b.c.o.)
- Reservado
- Reservado
- Reservado
Note 1: The terminals for the power supply inputs are pyn type standard terminals.
Note 2: To know the order of the boards in the rack, consult the number of the terminals on the rear views of each chassis.
Note 3: Available only for 1/2 19" chassis without measurement and 19" chassis.
Note 4: Available only for 19" chassis.
Note 5: Available only for 19" chassis without measurement.
Note 6: Standard analogue inputs configuration: +/-5mA, +/-5mA, +/-2.5mA, +/-2.5mA, +/-2.5mA, +/-2.5mA, +/-20mA, +/-20mA. Consult other configurations.
Note 7:This option requires selecting both ETH1 as ETH2 and supports any combination of options I , J and K.
Note 8: If there is only one card with these options it should be placed in ETH-1. This options replace options G, H, M, N. To use replaced options consult Ingeteam.
Note 9: If REAR ETHERNET COMMUNICATION PORT is "O" or "P", not available on board I/O 2 (4U housing) neither on board I/O 3 (5U housing).
Note 10: Not available on board I/O 7. If REAR ETHERNET COMMUNICATION PORT is "O" or "P", not available on board I/O 2 (4U housing) neither on board I/O 3 (5U housing).
Note 11: The maximun number of RTD board in the device are 2 .
It´s available an external accessory (FC2910) to allow BNC connection with coaxial cable in Irig-B and PPS input.
The following figures show the board position acording to model encoding.

User Manual 10
Figure 1 CD1 and CD2: ½ 19” chassis Figure 2 CD1 and CD2: 19” chassis
Figure 3 CD0 ½ 19” chassis Figure 4 CD0 19” chassis
Figure 5 Redundant power supply Figure 6 Redundant power supply
Figure 7 PRP Redundancy (2LC) Figure 8 PRP Redundancy (2RJ45 + 2LC)

User Manual 11
1.3 USER INTERFACE
The front board is equipped with:
❑ 10-digit numerical keyboard with decimal point, plus R key

❑ 4 scroll keys:  (Up),  (Down),  (Left), → (Right)
❑ 3 general keys  (Enter), ESC (Escape), MENU
❑ Function keys depending on the model:
 5 function keys (I, O, DES, SEL, INF)
 7 function keys (I, O, F1...F5)
 12 function keys (I, O, DES, SEL, INF, F1…F7)
 16 function keys (I, O, F1…F14)
❑ 19 fully assignable LEDs
❑ 1 unit operation LED
❑ USB 2.0 front port for downloading reports and loading CID
❑ Front RJ45 port for communications
Dispone de un interface trasero con comunicaciones:
The rear communications could be:
❑ Ethernet. Up to two Ethernet port (IEC8802-3) with options of RJ45, GFO or LC. Redundant ports are optional.
❑ Serial. Up to 6 ports with options: RS232, RS485, GFO and PFO.
1.4 INTERCONNECTIONS
Interconnections depend on the modules selected. The connections associated with each of the modules are indicated, and thus the
diagram will depend on the modules installed.
1.4.1 CPU
Figure 9 3-contact relay and IRIG-B Figure 10 With BNC accessory

User Manual 12
1.4.2 Power supply

The two options are a redundant power supply and a simple power supply with inputs/outputs.
Figure 11 Simple power supply
Figure 12 Double power supply
1.4.3 Input/output cards

The I/O modules available are:
❑ Module 1 (Figure 13): Equipped with 11 digital inputs and 9 digital outputs grouped as follows:
 Inputs: 4 independent + 3 with a common point + 4 with a common point.
 Outputs: 5 independent + 3 with a common point + 1 switched (3 contacts).
Figure 13 Module 11 digital inputs and 9 digital outputs
 Inputs: 16 with a common point.
 Outputs: 16 with a common point.
 Outputs: 8 independent.

User Manual 13
❑ Module 4 (Figure 16): Equipped with 32 digital inputs grouped as follows:

 Inputs: 16 with a common point + 16 with a common point.
Figure 16 Module 32 inputs
❑ Module 5 (Figure 17): Equipped with 16 digital inputs and 8 analogue inputs grouped as follows:
 Analogue: 8 independent. The analogue inputs have standard configuration, that could be changed among the
options: ±1mA, ±2.5mA, ±5mA, ±20mA, ±5V, ±10V
Standard configuration of analogue inputs
Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Input 8

+/- 5mA +/- 5mA +/- 2.5mA +/- 2.5mA +/- 2.5mA +/- 2.5mA +/- 20mA +/- 20mA
Figure 17 Module with 16 digital inputs and 8 analogue inputs
❑ Module 6 (Figure 18): Equipped with 16 digital inputs and 8 analogue inputs (4 isolated) grouped as follows:
 Analogue: 8 independent, 4 of them are isolated and 4 have a common point. The analogue inputs have
standard configuration, that could be changed among the options: ±1mA, ±2.5mA, ±5mA, ±20mA, ±5V, ±10V
Standard configuration of analogue inputs
Input 5 Input 6 Input 7 Input 8

Input 1 Input 2 Input 3 Input 4
(isolated) (isolated) (isolated) (isolated)
+/- 5mA +/- 5mA +/- 2.5mA +/- 2.5mA +/- 2.5mA +/- 2.5mA +/- 20mA +/- 20mA
Figure 18 Module with 16 digital inputs and 8 analogue inputs (4 isolated)

User Manual 14
❑ Module 7 (Figure 19): Equipped with 8 digital inputs, 4 high breaking capacity outputs (hbco) and 4 digital outputs
grouped as follows:
 Inputs: 8 independent.
 Outputs: 8 independent: the 4 hbco outputs are 1 to 4 (pins 1 to 8) and the 4 standard outputs are 5 to 8 (pins
10 a 17).
Figure 19 Módule 8 inputs, 4 outputs (hbco) and 4 digital outputs
❑ Module 8 (Figure 20): Equipped with 8 digital inputs, 8 digital outputs grouped as follows:
 Outputs: 8 independent.
Figure 20 Módule 8 inputs, 8 outputs
❑ Module 9 (Figure 21): Equipped with 8 digital inputs, 4 fast and high breaking capacity outputs (hbco) and 4 digital outputs
grouped as follows:
 Outputs: 8 independent: the 4 fast and hbco outputs are 1 to 4 (pins 1 to 8) and the 4 standard outputs are 5
to 8 (pins 10 a 17).
Figure 21 Module 8 inputs, 4 outputs (fast and hbco) and 4 digital outputs
❑ Module 10 (Figure 20): Equipped with 8 digital inputs, 8 high breaking capacity outputs (hbco) grouped as follows:
 Outputs: 8 hbco independent outputs..
Figure 22 Module 8 inputs, 8 outputs (hbco)

User Manual 15
❑ Module 11 (Figure 23): Equipped with 11 RTD inputs and 4 analogue outputs grouped as follows:
 RTD Inputs: 11 RTD.
 Analogue outputs: 4 independent. The analogue outputs can be configured with the options 0-1mA, 0-20mA,
4-20mA.
Figure 23 Module 11 RTD and 11 analog outputs
1.4.4 Analogue inputs

The following diagram shows the configuration of the analogue inputs:

User Manual 16
1.4.4.1 Wiring diagrams

The following figures show different interconnection options for the analogue inputs, in accordance with the available inputs.
Figure 24 Connection A. 3 wires connection: 3TT and 3TC

User Manual 17
Figure 25 Connection A. 4 wires connection : 3TT and 3TC

User Manual 18
Figure 26 Connection A. 3 wires connection: 3TT, Vneutral and 3TC

User Manual 19
Figure 27 Connection B.Delta 3 wires: 2TT and 3TC

User Manual 20
Figure 28 Connection B.Delta 3 wires: 2TT and 2TC

User Manual 21
Figure 29 Connection D. Delta 3 wires: 2TT and 1TC (balanced load)

User Manual 22
Figure 30 Connection E.4 wires: 1TT and 1TC (balanced load)

User Manual 23
Figure 31 Connection F.3 delta wires: 1TT and 1TC (balanced load)

User Manual 24
Figure 32 Connection G.4 Y wires: 2TT and 3TC

User Manual 25
Figure 33 Connection A with synchronism (model CD2)

User Manual 26
HARDWARE 
2. HARDWARE
EF devices can be used as autonomous devices or as part of a protection and control system. The devices are implemented based on a
microprocessor and a DSP linked through shared RAM and communication lines.
The digital processing is done by a high accuracy 16 bit converter. Each signal reaches this converter after being conditioned, filtered and
amplified. A high frequency sampling is done at 144 samples per cycle (at 8640 Hz for 60 Hz systems or at 7200Hz for 50 Hz systems). This
sampling is transformed into 24 samples per cycle through a digital process before reaching the protection functions.
INGEPAC EF devices have non-volatile flash memory where the user settings, configurations and application are stored. This kind of
memory allows software updates and modifications without needing to manipulate the device hardware.
2.1 CONSTRUCTION FEATURES
Two options can be selected:
❑ Half chassis ½ 19” and 5U

❑ Chassis 19” and 4U
2.1.1 Half chassis (½ 19”)

User Manual 27
HARDWARE 
2.1.2 19” chassis
2.2 REAR TERMINALS
The rear section will vary in accordance with the options selected for the unit. The following figures show various possible
configurations.
2.2.1 Configuration options

The rear section options may vary depending on the options selected:
❑ Power supply unit. There are two options available:

 Simple with inputs/outputs. Equipped with a 3-contact terminal with power supply with screw and a 17-
contact terminal with screw (Figure 34).
 Redundant. Equipped with two 3-contact terminals for each of the power supplies.
❑ Inputs/outputs cards. All the input/output modules have two 17-contact terminals with screw.
❑ CPU. Equipped with a 6-contact terminal with screw for the digital output of 3 contacts and the IRIG-B inputs
(Figure 9). Equipped with different Ethernet and standard communications module options.
❑ Analogue. Equipped with two 12-contact terminals with screw.
❑ Communications. To choose between:
 Ethernet: RJ45 and G.F.O.
 Standard: RS232, RS485, G.F.O. and P.F.O.
Pin type or closed type terminals may be chosen for the analogue and input/output terminals.

Different options which modify the view of the rear section may be selected (from top to bottom):
❑ Simple/redundant power supply

User Manual 28
HARDWARE 
❑ 1 or 2 I/O modules
❑ Communication ports in the CPU
❑ Choose between analogue card, I/O module or nothing
Figure 34 shows rear section with the options:
❑ Simple power source with inputs/outputs

❑ 2 input/output cards
❑ CPU with communication ports:
 Ethernet GFO + RJ45
 Standard RS232+RS485+GFO+PFO
❑ Analogue card with up to 12 transformers
Figure 34 Rear section with analogue and simple source
Figure 35 Rear section without analogue and simple source
2.2.3 19” chassis

Different options which modify the view of the rear section may be selected (from top to bottom and left to right):
❑ Simple/redundant power supply

❑ 1 or no I/O modules

User Manual 29
HARDWARE 
❑ Communication ports in the CPU

❑ Choose between analogue card, I/O module or nothing
❑ Number of I/O modules
In Figure 36 the next options can be seen:
❑ Simple power source with inputs/outputs

❑ 5 input/output cards
❑ CPU with communication ports:
 Ethernet GFO + RJ45
 Standard with 3 RS232 + 2 GFO + PFO
❑ Analogue card with up to 12 transformers
Figure 36 Rear section with analogue and simple source
Figure 1 Rear section without analogue and simple source

User Manual 30
HARDWARE 
2.2.1 Closed Terminals

The next figures show the closed terminals used in the digital I/O boards (Figure 37) and the transformer inputs (V/I) (Figure 38).
Figure 37 Closed Terminals I/O boards
Figure 38 Closed Terminals transformer inputs (V/I)
2.2.2 Wire section

The wires for the terminals should be copper with a section:
❑ Supply terminals:
Wire section AWG 16 to 12 (1.5 to 2.5 mm2)
❑ I/O terminals:
Wire section AWG 16 to 12 (1.5 to 2.5 mm2)
❑ Current and voltage terminals:

Wire section AWG 10 (4 mm2)
2.3 FRONT INTERFACE

There are two half-chassis front options (½ 19” and 5U):
❑ Configurable functional keys (Figure 39)

❑ Fixed functional keys (Figure 40).
The front interfaces are equipped with:
❑ Graphic display
❑ 19 general use LEDs with interchangeable labels
❑ 1 2-colour unit status LED
❑ Numeric keypad
❑ 7 operational keys
❑ Ethernet communication
❑ Master USB communication
❑ Depending on the model, the following are available:

User Manual 31
HARDWARE 
 5 functional keys for selecting with interchangeable labels + 2 operational keys

 3 fixed function keys + 2 operational keys.
Figure 39 Configurable functional keys Figure 40 Fixed functional keys
2.3.2 19” chassis

There are two 19” and 4U chassis front options:
❑ Configurable functional keys (Figure 41)

❑ Fixed functional keys (Figure 42)
The front interfaces are equipped with:
❑ Graphic display
❑ 19 general use LEDs with interchangeable labels
❑ 1 2-colour unit status LED
❑ Numeric keypad
❑ 7 operational keys
❑ Ethernet communication
❑ Master USB communication
❑ Depending on the model, the following are available:
 14 functional keys for selecting with interchangeable labels + 2 operational keys
 3 fixed function keys + 2 operational keys + 7 functional keys with interchangeable labels for selecting.
Figure 41 Configurable functional keys

User Manual 32
HARDWARE 
Figure 42 Fixed functional keys
2.4 TECHNICAL CHARACTERISTICS
2.4.1 Power supply voltage

Single power supply 125/220 Vdc models: 110Vdc-20% up to 250Vac + 10%:
❑ Operating range:
 Direct: 88Vdc up to 300Vdc
 Alternating: 85Vac up to 265Vac
Single power supply 24/48 Vdc models: 24Vdc-20% up to 48Vdc + 20%:
Redundant power supply 125Vdc models:
Redundant power supply 24/48 Vdc models:
Burden. Depends on the cards connected.
❑ 20W + 0,5W for each relay activated

Battery failure signal. Minimum voltage to activate the signal
Power supply 24Vcc 48Vcc 125Vcc 220Vcc

Activation level 16V 37V 86V 170V
The wires for the terminals should be copper with a section AWG 16 to 12 (1.5 to 2.5 mm2).
2.4.2 Digital outputs

The wires for the I/O terminals should be copper with a section AWG 16 to 12 (1.5 to 2.5 mm2).
Independent standard and trip outputs:
The characteristics of the independent contact outputs are as follows:
❑ Permanent current: 8 A at 25ºC

❑ Make: 30 A 1sec
❑ Connection capacity 2500W at 250Vdc

User Manual 33
HARDWARE 
❑ Open or break capacity:

200Vdc 125Vdc 48Vdc
With resistive load 1.0A 1.5A 2.0A
With inductive load L/R=40ms 0.7A 1.0A 1.5A
❑ Operating time: 5ms activation and 8ms deactivation

Signal outputs:
The characteristics of the 3-contact switched, common point signal outputs are:

❑ Make:
 30 A ½ sec.
 20 A 1 sec.
200Vdc 125Vdc 48Vdc
With resistive load 0.2A 0.4A 1.0A
With inductive load L/R=40ms 0.1A 0.2A 0.5A
❑ Operating time: 8ms activation and deactivation

The compliance of the common point outputs is the same as that of the independent outputs. However, due to sharing a common
point, only 2 relays can be activated simultaneously.
High break contact outputs (h.b.c.o) and Fast + high break contact outputs (fast + h.b.c.o):
The characteristics of the independent contact outputs are the same except the activation times:

❑ Make: 30 A 1sec
❑ Connection capacity 2500W at 250Vdc
200Vdc 125Vdc 48Vdc
With resistive load 10A 10A 10A
With inductive load 10A L/R=20ms 10A L/R=40ms 10A L/R=40ms
❑ Cyclic capacity: 4 cycles in 1 second, 2 minutes waiting for thermal dissipation

❑ Operating time:
 h.b.c.o outputs
 5ms activation and 5ms deactivation with resistive load
 5ms activation and 14ms deactivation with L/R = 40ms
 Fast + h.b.c.o outputs
 3µs activation and 8ms deactivation with resistive load
2.4.3 Digital inputs

The input burden is lower than 3mA at nominal voltage.
The inputs do not have polarity.
The wires for the I/O terminals should be copper with a section AWG 16 to 12 (1.5 to 2.5 mm2).
They have a fixed range with 4 nominal voltage options:

User Manual 34
HARDWARE 
Rated V Characteristics
Not activated below 9 Vdc.
24Vdc Activated above 12 Vdc.
Maximum voltage 72 Vdc
125Vdc They are activated above 87 Vdc.
2.4.4 IRIG-B input and PPS

Equipped with an input for synchronization by GPS, using IRIG-B time codes (Figure 43) and a pulse per second (PPS) input for
synchronization with:
❑ Demodulated input (TTL levels).

❑ Cable type: 2-wire, shielded
❑ Insulation: 2000 V
The input circuit is a 440 ohm serial resistance with an opto-isolator; for a 5 V signal, the approximate burden is 10 mA.
The number of units that can be connected in parallel to a generator depends on the output current supply capacity; a typical value
is 70 mA, which would enable the connection of 6 units (although the length and the type of cable can also influence). The cable
must be shielded and twisted.
According to configuration, it synchronizes with frames B002 , B003 , B006 , B007 type . It also synchronizes with IEE1344.
Optionally, with an external adapter inputs IRIG- B and PPS can be BNC type. The connection must use a 50 Ω coaxial cable with a
male BNC connector.
Figure 43 Connection example
2.4.5 Analogue ouputs

There is a I/O board with 4 continuous analogue outputs.
❑ Range can be selected by settings: 0 at 1 mA, 4 at 20mA and 0 at 20mA

❑ Accuracy: ± 1 % of full scale
❑ Maximum load:: 1200 Ohms
❑ Isolation:: 1 kV

User Manual 35
HARDWARE 
2.4.6 RTD Inputs

There is a I/O board with 11 isolated RTDs suitable by setting for the following probes:
❑ 100Ω Platinum
❑ 100Ω Nickel
❑ 120Ω Nickel
❑ 10Ω Copper
Measurement range: -50ºC to +250ºC
Accuracy ±2ºC
The wire must be shielded and twisted.
2.4.7 Current and voltage circuits

Phases, neutral current. Single rated current 1/5 A.
❑ Measurement range: 0,001A to 7,5A.

❑ Thermal capacity:
 Permanent 20 A
 Short duration 50 A (10 sec.)
500 A (1 sec.)
❑ Burden at In= 5 A <0.2VA

❑ Burden at In= 1 A <0.02VA
Voltage:
❑ Measurement range: 1V to 200V.

❑ Rated voltages: Configurable 40Vac to 140Vac
❑ Thermal capacity
 Permanent 2 Un
 Short duration 5 Un (1 sec.)
3.5 Un (1 min)
❑ Burden at 63.5 V <0.015 VA

❑ Burden at 100 V <0.03 VA
The wires should be copper with a section AWG 10 (4 mm2).
2.4.7.1 Accuracy
Apply control and measurement devices: models CD1 and CD2
❑ Current
 Measurement range (0 to 1.5*In)
 With In = 1A / 5A: class 0.2
❑ Voltage
 Measurement range (0 to 1.5*Vn)
 With Vn=63,5/120 Vac class 0.2
❑ Dephase angle
 Accuracy  1º

User Manual 36
HARDWARE 
❑ Power
 Measurement range (0 to 1,5xIn x 1,5xVn)
 With In = 1A/5A: class 0,5
❑ Frequency: ±10MHz
2.4.8 Front communication

Ethernet (IEC8802-3) via RJ45 cable
❑ RJ45 connector (female)

❑ Cable type: Shielded
❑ Cable length: 100 m maximum
❑ Baud rate: 10/100 Mb.
❑ Insulation 500V
USB
❑ USB 2.0 compatible version

❑ Master operating mode
❑ Speed: 480Mbps (high-speed), 12Mbps (full-speed) or 1.5Mbps (low-speed)
❑ Insulation 500V
2.4.9 Rear communications
2.4.9.1 Ethernet communication

The device has two Ethernet port (IEC8802-3) with options of RJ45 or optical fiber.
Ethernet via RJ45 cable
❑ RJ45 connector (female)

❑ Baud rate: 10/100 Mb.
❑ Insulation 500V
Ethernet via glass optical fiber (ST and LC)
❑ Connector
 ST
 LC
❑ Wavelength: 1310nm
❑ Multimode glass optical fiber: 62.5 /125 µm and 50/125 µm
❑ Permitted attenuation
 8 db with 50/125 µm
 11 db with 62.5/125 µm
❑ Typical transmitter optical power: -20dBm to -14dBm
❑ Receiver optical sensitivity: -31dBm
❑ Baud rate: 100 Mb.
❑ Maximum distance: 2 km

User Manual 37
HARDWARE 
2.4.9.2 Serial communications

Glass optical fiber
❑ ST connector
❑ Multimode glass optical fiber: 62.5 /125 µm and 50/125 µm
❑ Permitted attenuation
 9 db with 50/125 µm
 11 db with 62.5/125 µm
❑ Typical transmitter optical power: -17dBm to -11dBm
❑ Maximum distance: 2 km
Plastic optical fiber
❑ V-Pin connector (HP standard)

❑ Multimode optical fiber HCS (silica) with 200 µm and plastic with 1mm
❑ Permitted attenuation:
 24.7db with 1mm plastic cable
 22db with 200 µm silica cable
❑ Typical transmitter optical power
 -17dBm to -8dBm with 1mm plastic cable
 -13,5dBm to -4,5dBm with 200 µm silica cable
❑ Maximum distance: 115m with 1mm plastic cable and 1.9km with 200 µm silica cable
RS232
❑ DTE 9 pin female D type

❑ Insulation 500V
RS485
❑ DTE 9 pin female D type

❑ Cable type: Shielded crossed pair
❑ Cable length: 1.000 m maximum.
❑ Insulation 500V
The serial ports pinout is shown in the table:
Pin RS232 RS485

1 CD D+
2 Rx D+
3 Tx D-
4 9 Vcc D-
5 GND GND
6 DSR
7 RTS
8 CTS
9

User Manual 38
HARDWARE 
2.5 ENVIRONMENTAL CONDITIONS
Operating temperature:
❑ Continuous: -25°C a +60 ºC

❑ <96h: -25°C a +70 °C
❑ <16h: -40°C a +85ºC
❑ HMI and MTBF may be affected outside the continuous operating temperature range
❑ The maximum operation temperature for LC communication ports is +70º
Storage temperature: -40 to 85 ºC
Relative humidity: Up to 95% without condensation
2.5.1 Tropicalized
Printed circuit boards are lacquered to protect against corrosion and biological factors in humid environments. Depending on the
type of card different methods are used, dipping or selective varnishing and different varnishes. It is a treatment that deposits a
layer of low surface energy that repels moisture and some types of dirt. This procedure is made by demand, in the order.
2.6 TESTS
2.6.1 Climatic test

Climatic test Standard
Cold IEC -60068-2-1 -40°C, 16 hours
Dry Heat IEC -60068-2-2 +85°C, 16 hours
Damp heat steady state IEC -60068-2-78 +40°C/93%RH, 96 hours
Damp heat cyclic IEC -60068-2-30 55ºC / 95% HR 6 cycles of 12+12 hours
Rapid change of temperature IEC -60068-2-14 -20ºC/+70ºC 5 cycles of 3+3 hours
External protection level IEC60529 IP30
2.6.2 Insulation and electrical safety tests

Insulation and electrical safety test Standard
Dielectric test IEC 60255-27 2 kVac
Insulation resistance test IEC 60255-27 > 100 MΩ at 500Vdc.
±5kV CM
Impulse voltage test IEC 60255-27
±1kV DM
2.6.3 Mechanical tests

Mechanical test Standard
Vibration (sinusoidal): Response IEC 60255-21-1 Class 2
Vibration (sinusoidal): Endurance IEC 60255-21-1 Class 1
Shocks and bumps IEC 60255-21-2 Class 1
Seismic IEC 60255-21-3 Class 2

User Manual 39
HARDWARE 
2.6.4 Electromagnetic tests

Electromagnetic test Standard
IEC 60255-26
Measurements of radiated disturbance field strength EN 55022 A Class
CISPR 11, 32
IEC 60255-26
A Class PS
Measurements of conducted radioelectric disturbances EN 55022
B class: Ethernet port
CISPR 11, 32
IEC 60255-26 ±2.8kV CM
Damped oscillatory waves immunity test
IEC 61000-4-18 ±1kV DM
IEC 60255-26
Electrostatic discharge immunity test ±8kV/±15kV
IEC 61000-4-2
IEC 60255-26
Electrical Fast transients immunity test ±4kV,5kHz
IEC 61000-4-4
IEC 60255-26 ±4kV CM
Surge immunity test IEC 61000-4-5 ±2kV DM
IEC 60255-26 100% 130 ms
DC power supply interruptions, dips and variations immunity test IEC 61000-4-29 60% 200 ms
IEC 61000-4-11 30% 5s
IEC 60255-26
Ripple immunity test 15% (50 and 100 Hz)
IEC 61000-4-17
IEC 60255-26
Power frequency immunity test IEC6100-4.16 300 V CM/ 150 V DM
IEC 60255-22-7
IEC 60255-26
Radiated radiofrequency electromagnetic field immunity test 10V/m
IEC 61000-4-3
IEC 60255-26
Conducted disturbances induced by radiofrequency fields immunity test 10Vrms
IEC 61000-4-6
IEC 60255-26
50 Hz magnetic fields immunity test 100 A/m 1000 A/m (2 s)
IEC 61000-4-8
IEC 60255-26
Pulse magnetic fields immunity test 1000 A/m
IEC 61000-4-9
Damped oscillatory magnetic fields immunity test IEC 61000-4-10 100 A/m
Radiated Electromagnetic Interference from Transceivers IEEE 37.90.2 35 V/m

User Manual 40
MEASUREMENT
3. MEASUREMENT
The measurements corresponding to 4 current trafos and 4 voltage trafos are calculated over these models, based on those calculated
by the powers and energies.
T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12

I phase A I phase B I phase C I neutral -- -- -- -- V neutral V phase A V phase B V phase C
There are rms and fundamental frequency measurements.
The measurements measured and/or calculated by the unit are:
❑ Voltage measurements. There are rms and fundamental frequency measurements. See Table 1.
 Phase A simple voltage  Vab compound voltages

 Angle V phase A  Vbc compoundvoltajes
 Phase B simple voltage  Vca compoundvoltages
 Angle V phase B  Average compound voltages
 Phase B simple voltage  Voltage unbalance
 Angle V phase B  Harmonic distortion in Va, Vb, Vc and average (%)
 Average simple voltage  Frequency
 Neutral voltage
 Angle V neutral
❑ Measurements of currents. There are rms and fundamental frequency measurements. VerTable 2.
 Phase A current (Amperes)  Neutral current

 Angle I phase A  Angle i neutral
 Phase B current (Amperes)  Harmonic distortion in Ia, Ib, Ic and average (%)
 Angle I phase B  Current unbalance
 Phase C current (Amperes)
 Angle I phase C
 Phase average current
❑ Measurements of power and energy. There are rms and fundamental frequency measurements. VerTable 3.
 Active power(kW)  Active energy counter (positive)

 Reactive power(kVAR)  Active energy counter (negative)
 Aparent power (kVA)  Reactive energy counter (positive)
 Power factor phase A, B, C and average  Reactive energy counter (negative)

User Manual 41
MEASUREMENT
Table 1 Voltage measurements
Measurement Description Node Data Atribute

V phase A rms (module and angle) VA MMXU PhV phsA
V phase B rms (module and angle) VB MMXU PhV phsB
V phase C rms (module and angle) VC MMXU PhV phsC
Phase Average voltage rms (module) AVERAGE V MMXU PhV net
V neutral rms (module and angle) VN MMXU PhV neut
V phase A fundamental (modulo y argumento) VA (fundamental) FUNMMXU FunPhV phsA
V phase B fundamental (module and angle) VB (fundamental) FUNMMXU FunPhV phsB
V phase C fundamental (module and angle) VC (fundamental) FUNMMXU FunPhV phsC
V neutral fundamental (module and angle) VN (fundamental) FUNMMXU FunPhV neut
V compound AB VAB MMXU PPV phsAB
V compound BC VBC MMXU PPV phsBC
V compound CA VCA MMXU PPV phsCA
V compound average AVERAGE U MMXU PPV (PPVm in Ed2) net
THD voltage phase A THD phase A Voltage MHAI ThdPhV phsA
THD voltage phaseB THD phase B Voltage MHAI ThdPhV phsB
THD voltage phaseC THD phase C Voltage MHAI ThdPhV phsC
THD voltage average THD Average Voltage MHAI ThdPhV net
THD neutral voltage THD Neutral Voltage MHAI ThdPhV neut
Sequence V0 (module and angle) V0 MSQI SeqV c1
Frequency Frequency MMXU Hz net
Table 2 Current measurements

I phase A rms (module and angle) IA MMXU A phsA
I phase B rms (module and angle) IB MMXU A phsB
I phase C rms (module and angle) IC MMXU A phsC
Phase Average currentrms (module) AVERAGE I MMXU A net
I neutral rms (module and angle) IN MMXU A neut
I phase A fundamental (module and angle) IA (fundamental) FUNMMXU FunA phsA
I phase B fundamental (module and angle) IB (fundamental) FUNMMXU FunA phsB
I phase C fundamental (module and angle) IC (fundamental) FUNMMXU FunA phsC
I neutral fundamental (module and angle) IN (fundamental) FUNMMXU FunA neut
THD current phase A THD phase A current MHAI ThdA phsA
THD current phase B THD phase B current MHAI ThdA phsB
THD current phase C THD phase C current MHAI ThdA phsC
THD current average THD Average current MHAI ThdA net
THD neutral current THD Neutral current MHAI ThdA neut
Sequence I0 (module and angle) I0 MSQI SeqA c1

User Manual 42
MEASUREMENT
Table 3 Power measurements

Total active power ACTIVE POWER P MMXU TotW net
Total reactive power REACTIVE POWER Q MMXU TotVAr net
Average apparent power POWER S MMXU TotVA net
Phase A active power Phase A Active Power MMXU W phsA
Phase A reactive power Phase A Reactive Power MMXU VAr phsA
Phase A apparent power Phase A S Power MMXU VA phsA
Phase B active power Phase B Active Power MMXU W phsB
Phase B reactive power Phase B Reactive Power MMXU VAr phsB
Phase B apparent power Phase B S Power MMXU VA phsB
Phase C active power Phase C Active Power MMXU W phsC
Phase C reactive power Phase C Reactive Power MMXU VAr phsC
Phase C apparent power Phase C S Power MMXU VA phsC
Phase A power factor Cosine phi rms phase A MMXU PF phsA
Phase B power factor Cosine phi rms phase B MMXU PF phsB
Phase C power factor Cosine phi rms phase C MMXU PF phsC
Average power factor Cosine phi rmsaverage MMXU PF net
Total active power (fundamental) Active power P (fund) FUNMMXU FunTotW net
Total reactive power (fundamental) Reactive power Q (fund) FUNMMXU FunTotVAr net
Average apparent power (fundamental) Power S (fund) FUNMMXU FunTotVA net
Phase A active power (fundamental) Phase A Active Power (fund) FUNMMXU FunW phsA
Phase A reactive power (fundamental) Phase A Reactive Power (fund) FUNMMXU FunVAr phsA
Phase A apparent power (fundamental) Phase A S Power (fund) FUNMMXU FunVA phsA
Phase B active power (fundamental) Phase B Active Power (fund) FUNMMXU FunW phsB
Phase B reactive power (fundamental) Phase B Reactive Power (fund) FUNMMXU FunVAr phsB
Phase B apparent power (fundamental) Phase B S Power (fund) FUNMMXU FunVA phsB
Phase C active power (fundamental) Phase C Active Power (fund) FUNMMXU FunW phsC
Phase C reactive power (fundamental) Phase C Reactive Power (fund) FUNMMXU FunVAr phsC
Phase C apparent power (fundamental) Phase C S Power (fund) FUNMMXU FunVA phsC
Phase A power factor (fundamental) Cosine phi rms phase A (fund) FUNMMXU FunPF phsA
Phase B power factor (fundamental) Cosine phi rms phase B (fund) FUNMMXU FunPF phsB
Phase C power factor (fundamental) Cosine phi rms phase C (fund) FUNMMXU FunPF phsC
Average power factor (fundamental) Cosine phi rms average (fund) FUNMMXU FunPF net
The available measurements depend on the connection type:

❑ A Connection. The simple currents (Ia, Ib, Ic) and neutral and voltages (Va, Vb, Vc) and neutral are directly measured, and
the rest of the measurements are calculated on the basis of these
❑ B Connection. The simple currents (Ia, Ib, Ic) and neutral and compound voltages (Vab, Vbc, Vca) are directly measured,
and the rest of the measurements are calculated on the basis of these. Simple voltages are not available.
❑ D Connection. The simple current Ia and compound voltages (Vab, Vbc, Vca) are directly measured. The rest of the
measurements are calculated on the basis of these. Simple voltages are not available. The currents Ib and Ic are calculated
from Ia because the load is balanced
❑ E Connection. The simple current of phase A (Ia)and simple voltage of phase A (Va)are directly measured, and the rest of
the measurements are calculated on the basis of theseThe voltage Vb and Vc are calculated from Va and the currents Ib
and Ic are calculated from Ia because the load is balanced.
❑ F Connection. The simple current of phase C (Ic)and compound voltage of phases AB (Vab)are directly measured.The
voltage Vbc and Vca are calculated from Vab and the currents Ia and Ib are calculated from Ia because the load is
balanced. Simple voltages are not available.
❑ G Connection. The simple currents (Ia, Ib, Ic) and neutral and voltages (Va, Vc) are directly measured. The rest of the
measurements are calculated on the basis of these. The simple voltage Vb is calculated from the other voltages (balanced
load).
The power measurements are calculated with the meausured voltajes and currents. Depending on the connection type, phase
and/or total power are available.
Depending on the connection type, phase and/or average power factor are available.
There are four Energy counters: positive active, negative active, positive reactive, negative reactive.

User Manual 43
MEASUREMENT
Table 4 Available measurements with connection type
Measurement A B D E F G
Voltage phase A (module)   
Voltage phase B (module)   
Voltage phase C (module)   
AverageV simple (module)   
V neutral (module) 
Voltage phase A (angle)   
Voltage phase B (angle)   
Voltage phase C (angle)   
Voltage neutral (angle) 
Voltage phases AB (module)      
Voltage phases BC (module)      
Voltage phases CA (module)      
Average V compound (module)      
Current phase A (module)      
Current phase B (module)      
Current phase C (module)      
Average current (module)      
I neutral (module)   
Current phase A (angle)      
Current phase B (angle)      
Current phase C (angle)      
Current neutral (angle)   
THD Voltage phaseA   
THD Voltage phaseB   
THD Voltage phaseC   
THD voltaje average   
THD V neutral   
THD Voltage phasesAB   
THD Voltage phasesBC   
THD Voltage phasesCA   
THD voltaje compoundaverage   
THD Current phaseA      
THD Current phaseB      99
THD Current phaseC      
THD Current average      
THD I neutral     
Sequence V0   
Sequence I0      
Sequence V1      
Sequence I1      
Sequence V2      
Sequence I2      
Active Power      
Reactive Power      
Apparent Power      
Active Power phase A   
Reactive Power phase A   
Apparent Power phase A   
Active Power phase B   
Reactive Power phase B   
Apparent Power phase B   
Active Power phase C   
Reactive Power phase C   
Apparent Power phase C   
Power Factor phase A   
Power Factor phase B   
Power Factor phase C   
Power Factor average      

User Manual 44
MEASUREMENT
3.1 MEASUREMENTS DEPENDING ON WIRING PROCEDURES

38B
The available measurements on each connection type are showed in Table 4.
3.1.1 Connection Type A

The simple currents and voltages are directly measured, and the rest of the measurements are calculated on the basis of these.
Each phase power is calculated with Equation1.
Equation1. Phase Power

 
Pi = Re{Vi  I i )
 
Qi = Im{Vi  I i )
S i = Vi  I i
(beingieach phase A, B and C).
Total power is calculated with Equation 2:
Equation 2. Total Power
PT = PA + PB + PC
QT = Q A + QB + QC
ST = S A + S B + SC
The power factor uses Equation 3 for each phase andEquation 4 for total power.
Equation 3.Power factor for each phase
Pi
cos  i =
Si
Equation 4. Total Power Factor
PT
cos  T =
ST
Direct, inverse and zero sequences of currents and voltages are available (Equation 5).
Equation 5. Currents and voltages Sequences
 1     1   
V0 =  (Va + Vb + Vc ) I 0 =  ( Ia + Ib + Ic )
3 3
 1     1   
V1 =  (Va + a • Vb + a 2 • Vc ) I1 =  ( Ia + a • Ib + a 2 • Ic )
3 3
 1     1   
V2 =  (Va + a 2 • Vb + a • Vc ) I 2 =  ( Ia + a 2 • Ib + a • Ic )
3 3
where a=1|120º
3.1.2 Connection Type B

The simple currents and compound voltages are directly measured.

User Manual 45
MEASUREMENT
There are not measurements of simple voltages, power for each phase (P, Q, S and power factor) and zero sequence. All of them
are marked as invalid.
Total active power (P), reactive power (Q) and apparent power (S) are calculated using Equation 6 and average power factor using
Equation 4.
PT = I b  Vbc − I a  Vca
In the connections, where compound voltages are measured, the voltage zero sequence is not available and the direct and inverse
sequences are calculated with the compound voltaje as:
Equation 7. Sequences calculation

j 330
 1    e 180
V1 =  (Vab + a • Vb c + a 2 • Vc a) 
3 3

j 330
 1    e 180
V2 =  (Vab + a 2 • Vb c + a • Vc a) 
3 3
where a=1|120º
This wiring type may be connected with only two current trafos, while the measurement of the third current is carried out as the
sum of the other two (see Equation 7).
3.1.3 Connection Type D

In this case, the compound voltages and phase A current are directly measured.
The other two currents, as they are for balanced load, are the same in module as the measured current, but dephased 120º and –
120º respectively. As the load is balanced, zero and inverse sequences are zero
From this point on, the compound voltages and phase currents are available, and the rest of the measurements are calculated on
the basis of these.
Total active power (P), reactive power (Q) and apparent power (S) are calculated using Equation 8 and average power factor using
Equation 4.
The voltage zero sequence is not available. The direct and inverse sequences are calculated with the compound voltaje using
Equation 7.
Equation 8. Total Power calculation
PT = 3  ( I a  Vbc )
3.1.4 Connection Type E

In this case, only one measurement voltage and one measurement current are available.
The other two voltages are the same in module as the measured current, but dephased 120º and –120º respectively, because the
load is balanced.
The other two currents are the same in module as the measured current, but dephased 120º and –120º respectively, because the
load is balanced.

User Manual 46
MEASUREMENT
As the load is balanced, zero and inverse sequences of current and voltage are zero.
The power of each phase is the same and it is enough to calculate one of them (Equation 9) and the total power as three times the
calculated phase (Equation 10).
Equation 9.Power for phase A
(
 
PA = Re V A  I A )
(
 
Q A = Im V A  I A )
S A = VA  I A
PT = 3  PA
QT = 3  Q A
ST = 3  S A
The total and phase power factors are also the same and it is enough with calculating phase A.
Equation 11. Power factor
PA
cos  A =
SA
3.1.5 Connection Type F

In this case, only a measured compound voltage (Vab) and measured current (Ic) are available.
The other two voltages are the same in module as the measured current, but dephased 120º and –120º respectively, because the
load is balanced.
The other two currents are the same in module as the measured current, but dephased 120º and –120º respectively, because the
load is balanced.
As the load is balanced, zero and inverse sequences of current and voltage are zero.
The total power is calculated starting from measured compound voltage and simple current (Equation 12).
Equation 12. Total Power factor

 
V pot = VAB· j
( )
 
PT = 3·Re V pot  I C
( )
 
QT = 3· Im V pot  I C
ST = 3·V pot  I C
Only the average power factor is available (Equation 13).
Equation 13. Power factor
PT
cos T =
ST

User Manual 47
MEASUREMENT
3.1.6 Connection Type G

In this case, the three phase currents and simple voltages of phase A and C are directly measured.
As the load is balanced, phase B voltage is calculated with Equation 14.
From this point on, the simple voltages and phase currents are available, and the rest of the measurements are calculated on the
basis of these.
The equations are the same as A connection.
Equation 14. Vb Voltage calculation
V B = −(V A + VC )
3.2 ENERGY COUNTERS

16B
They correspond to the primary of the measurement transformers, so there are parameters that indicate transformatio ratio of the
voltage and current trafos.
The measurement is given as the number of pulses. There is a programmable parameter that indicates the number of kWh/pulse for
the active energy counters, and another kVARh / pulse for the reactive energy counters.
So, the settings related to the energy counters are:
❑ Voltage trafo ratio

❑ Current trafo ratio
❑ Active Energy counter (kWh)
❑ Reactive Energy counter (kVARh)
Application example:
A 1500kWh burden measurement will read 1500 pulses for an active energy constant of 1 kWh primary / pulse. The Reading will be 300
pulses for an active energy constant of 5 kWh primary / pulse.
Table 5 Energy counters
Name Node Data Atribute

Positive active Energy counter Active Energy Out MMTR SupWh actVal
Negative active Energy counter Active Energy In MMTR DmdWh actVal
Positive reactive Energy counter Reactive Energy Out MMTR SupVArh actVal
Negative reactive Energy counter Reactive Energy In MMTR DmdVArh actVal

User Manual 48
AUTOMATISMS 
4. AUTOMATISMS
Only in models CD2.
4.1 SYNCHRONISM
The synchronism function or “synchrocheck” waits for the appropriate conditions established in the settings, to determine breaker
closure, both manual and automatic.
Two voltage signals from the two sides of the breaker, which we will call side A and side B, are compared.
Side A corresponds to the voltage input selected with the setting “Side A Phase Select”. This setting selects the analogue input used.
The selection between ground to phase and phase to phase voltages is made with the connection type. With this setting a
compensation factor is applied to equalize the module and the angle of the two voltages compared (side A and side B).
Side B corresponds to the analogue voltage input connected to the synchronism voltage terminals.
Table 2 shows the settings of this function for undervoltage and synchronism:
❑ Enabled. Indicates whether the function is enabled or not. When enabled, the function tests the synchronism conditions. When
disabled, manual closure permission is granted, but automatic permission is refused.
❑ Side A phase Select: selectable between A/AB, B/BC or C/CA, corresponding to the measurement of the selected voltage
transformer. A/AB for transformer 10, B/BC for transformer 11 and C/CA for transformer 12.
❑ Compensation factor (Vs1): the factor by which the module is multiplied in order to equalize the voltages.
❑ Compensation angle (Vs1): the factor to be added to the angle in order to equalize the voltages.
❑ A-Side Voltage presence (V): the voltage measured in side A must exceed this value in order to consider that there is voltage on
that side of the breaker.
❑ A-Side Lack of Voltage (V): the voltage measured in side A must be lower than this value in order to consider that there is an
absence of voltage on that side of the breaker. It must be at least 5% less than Voltage presence.
❑ B-Side Voltage presence (V): the voltage measured in side B must exceed this value in order to consider that there is voltage on that
side of the breaker.
❑ B-Side Lack of Voltage (V): the voltage measured in side B must be lower than this value in order to consider that there is an
absence of voltage on that side of the breaker. It must be at least 5% less than Voltage presence.
❑ Autoreclose condition. Indicates the conditions for granting reclosing permission with undervoltage:
 Without permission: under no circumstances will the function grant undervoltage permission
 Not A and Yes B: there must be an absence of voltage on side A and presence of voltage on side B in order for the function to
grant undervoltage permission.
 Yes A and Not B: there must be an absence of voltage on side B and presence of voltage on side A in order for the function to
 Not A and Not B: there must be an absence of voltage on both sides of the breaker in order for the function to grant
undervoltage permission.
 Not A or Not B: there must be an absence of voltage on one of the sides of the breaker in order for the function to grant
 A xor B: there must be voltage presence on one side of the breaker and an absence on the other in order for the function to
 Not A: there must be an absence of voltage on side A in order for the function to grant undervoltage permission.
 Not B: there must be an absence of voltage on side B in order for the function to grant undervoltage permission.
❑ Manual closing condition. Indicates the conditions for granting manual closing permission with undervoltage:
 Without permission: under no circumstances will the function grant undervoltage permission
 Not A and Yes B: there must be an absence of voltage on side A and presence of voltage on side B in order for the function to

User Manual 49
AUTOMATISMS 
 Yes A and Not B: there must be an absence of voltage on side B and presence of voltage on side A in order for the function to
 Not A and Not B: there must be an absence of voltage on both sides of the breaker in order for the function to grant
 Not A or Not B: there must be an absence of voltage on one of the sides of the breaker in order for the function to grant
 A xor B: there must be voltage presence on one side of the breaker and an absence on the other in order for the function to
 Not A: there must be an absence of voltage on side A in order for the function to grant undervoltage permission.
 Not B: there must be an absence of voltage on side B in order for the function to grant undervoltage permission.
❑ Enabling of synchrocheck with reclosure:
 None: under no circumstances will the function grant synchronism permission.
 No compensation: comparisons between angles, modules and frequencies are taken into account to grant permission if the set
conditions are met during the programmed time
 With compensation1: in addition to the module and frequency comparisons, breaker close time is taken into account. See
Figure 44.
 Zero compensation1: a specific case of enabling with compensation and also taking into account that closure permission will be
granted when the angle difference is 0°. See Figure 44.
 Always.2 The function grants synchronism permission with present of voltage on both sides of the breaker.
❑ Enabling of synchrocheck with manual closure:
 None: under no circumstances will the function grant synchronism permission.
 No compensation: comparisons between angles, modules and frequencies are taken into account to grant permission if the set
conditions are met during the programmed time
 With compensation1: in addition to the module and frequency comparisons, breaker close time is taken into account. See
Figure 44.
 Zero compensation1: a specific case of enabling with compensation and also taking into account that closure permission will be
granted when the angle difference is 0°. See Figure 44.
 Always.2 The function grants synchronism permission with present of voltage on both sides of the breaker.
❑ Breaker close time (s): taken into account when calculating the angle difference and providing that the enabling "with
compensation" has been programmed. In this case, the frequency slip is taken into account to compensate for this time.
❑ Voltage difference (V): the difference between the voltage modules on side A and side B must be less than this value in order for
permission to be granted.
❑ Frequency difference (Hz): the difference between the frequencies on side A and side B must be less than this value in order for
❑ Angle difference (º): the difference between the voltage angles on side A and side B must be less than this value in order for
❑ Slip threshold (Hz): if the difference between the frequencies in side A and side B is greater than this value there is frequency slip.
Otherwise, it is not considered frequency slip.1
❑ Sync.Time Man.closing(ms): the time during which the conditions for the granting of permission for closure must be met.
❑ Sync. Time Autoreclose(ms): the time during which the conditions for the granting of permission for reclosure must be
met.Blocking input: logic input which, when active, blocks the function. When blocked, manual closure permission is granted, but
automatic permission is refused.
❑ Close blocking: logic input which, when active, blocks the breaker close permission (manual and automatic).
❑ A-Side Maximum V. (V) 3. To fulfill the synchronism, the side A voltage must be greater than the “A-Side Voltage presence (V)”
setting and below the "A-Side Maximum V" setting. If they are set to the same value, the "A-Side Maximum V" is considered 200V.
1
Available since firmware version 5.17.15.2 and ICD 6.1.13.27
2
3

User Manual 50
AUTOMATISMS 
❑ B-Side Maximum V. (V) 3. To fulfill the synchronism, the side B voltage must be greater than the “B-Side Voltage presence (V)”
setting and below the "B-Side Maximum V" setting. If they are set to the same value, the "B-Side Maximum V" is considered 200V.
The synchronism function can be disabled by means of a setting (“NO”). By means of a “fuse failure” or a “breaker closure permission
block” digital input both manual and automatic permission are refused.
When disabled, manual closure permission is granted but not automatic closure permission. In order to give closure permission when
enabled, the function contemplates the conditions that grant undervoltage permission or synchronism permission. If any of then grants
permission, closure permission is granted. Manual and automatic closure permissions are analysed independently.
❑ Undervoltage:
 When disabled undervoltage permission is refused.
 When enabled, undervoltage conditions are analised. If undervoltage permission is granted, closure permission is granted,
independently of synchronism conditions.
❑ Synchronism: when undervoltage permission is not granted, synchronism conditions are analised
 When disabled synchronism permission is refused.
 When enabled, synchronism conditions are analised. .
4.1.1 Undervoltage permission

Permission is granted if there is voltage on one or on both sides of the breaker. In order to verify whether there is no voltage
present on one side of the breaker, the voltage measured is checked to see whether it is lower than the programmed value (see
Table 2).
The detection of the presence or the absence of voltage is always done in all the phases. However, the analysis of the conditions for
granting or refusing breaker close permission is only carried out if the function is enabled.
4.1.2 Synchronism permission

Synchronism permission is given when following conditions indicated by the corresponding setting are simultaneously fulfilled
during a programmable time. These conditions are based on the comparison of voltage modules, phases and frequency on both
sides of the breaker. The analysis is performed whenever there is voltage on both sides of the breaker and it is below the maximum
voltage setting.
Figure 44 Synchronism check with compensation
If “Sync. Enabled” is selected “with compensation”, the frequency slip is used to compensate the breaker closing time:
ϕUB (with compensation) =ϕUB + ωslip·TCB
∆ϕ with compensation =ϕUB (with compensation) -ϕUA
In which:

User Manual 51
AUTOMATISMS 
Frequency slip ∆f=fB-fA (Hz)
Slip speed ωslip=∆f·360º (º/s)
Breaker closure time TCB (s)
To consider the slip frequency difference must exceed the "Slip threshold (Hz)" setting.
If this angle difference decreases when the “Sync. Enabled” is set with compensation and closure in 0º, the condition for granting
permission will be:
|∆ϕ with compensation|=0
If the angle difference is increasing, the following must be met:
|∆ϕ with compensation|<angle difference setting
When the “Sync. Enabled” is set with compensation, in order for permission to be granted the difference must be around 0º, the
following must be met:
|∆ϕ with compensation|<angle difference setting
Synchronism function measurements available in the unit status:
❑ Module, angle, frequency of the voltage on side A.

❑ Module, angle, frequency of the voltage on side B.
❑ The difference between the module, angle, frequency of the voltage on side A and side B. They are only available when
the voltage presence conditions are met on both sides.
The function has independent settings, commands and outputs:
❑ Node: PROT/RSYN1
❑ Settings and logical inputs: There are 6 settings tables. See Table 2.
❑ Commands:
 DOrdSyBlk1: Function block and unblocking. Only acts when the function is enabled.
 DOrdPeBlk1: Close permission block and unblock. Only acts when the function is enabled.
❑ Outputs: Table 3 shows the function’s output data.
Synchrocheck function signals (see Table 3).
❑ Enable Synchro Breaker 1: Indicates whether the function is enabled or not.

❑ V presence Va/Vab side A: indicates if the voltage on the phase A/AB of side A is greater than the setting “A-Side Voltage
presence (V)”.
❑ V presence Vb/Vbc side A: indicates if the voltage on the phase B/BC of side A is greater than the setting “A-Side Voltage
presence (V)”.
❑ V presence Vc/Vca side A: indicates if the voltage on the phase C/CA of side A is greater than the setting “A-Side Voltage
presence (V)”.
❑ V presence ABC side A: indicates if the voltage of the three phases of side A is greater than the setting “A-Side Voltage
presence (V)”.
❑ V presence side B B1: indicates if the voltage on the side B is greater than the setting “B-Side Voltage presence (V)”.
❑ No Voltage Va/Vab side B: indicates if the voltage on the phase A/AB of side A is less than the setting “A-Side Voltage
presence (V)”.
❑ No Voltage Vb/Vbc side B: indicates if the voltage on the phase B/BC of side A is greater than the setting “A-Side Voltage
presence (V)”.
❑ No Voltage Vc/Vca side B: indicates if the voltage on the phase C/CA of side A is greater than the setting “A-Side Voltage
presence (V)”.

User Manual 52
AUTOMATISMS 
❑ No Voltage ABC side A: indicates if the voltage of the three phases of side A is less than the setting “A-Side Voltage
presence (V)”.
❑ No Voltage side B B1: indicates if the voltage on the side B is less than the setting “B-Side Voltage presence (V)”.
❑ A Side Maximun V exceeded 3: It indicates that the voltage on the A side is geater than the setting “A-Side Maximum V.
(V)”.
❑ B Side I1 Maximun V exceeded3: It indicates that the voltage on the B side is geater than the setting “B-Side Maximum V.
(V)”.
For the following signals, it is necessary that voltage presence is detected on both sides of the breaker:
❑ Positive slip Breaker 1: it is active if the frequency on the side B is also greater than that on side A by more than the
setting.
❑ Negative slip Breaker 1: it is active if the frequency on the side A is also greater than that on side B by more than the
setting.
❑ Underfrequency side B B1: it is active if the frequency difference of both sides exceeds the setting value and the
frequency on side A is greater than that on side B.
❑ Overfrequency side B B1: it is active if the frequency difference of both sides exceeds the setting value and the frequency
on side B is greater than that on side A.
❑ Delay without comp. side B 1: when the difference between the angles exceeds the setting value and is greater on side A
than on side B.
❑ Adv. without comp.side B B1: when the difference between the angles exceeds the setting value and is greater on side B
than on side A.
❑ Delay with comp. side B 1: when the difference between the angles, calculated by taking into account breaker closure
time, exceeds the setting value and is greater on side A than on side B.
❑ Advance with comp. side B 1: when the difference between the angles, calculated by taking into account breaker closure
time, exceeds the setting value and is greater on side B than on side A.
❑ Over Module side B B1: when the voltage difference is greater than the programmed setting and the voltage in B is
greater than in A.
❑ Under Module side B B1: when the voltage difference is greater than the programmed setting and the voltage in A is
greater than in B.
❑ Perm. without comp. B1: indicates that differences in voltage, angle and frequencies are lower than the corresponding
settings.
❑ Perm. with comp. B1: when the necessary conditions related to the voltage, angle argument and frequencies differences
are given, taking into account the breaker closure time for calculating the angle argument difference.
❑ Perm. Manual Close V B1: Manual closure permission for voltage checks. It´s active when the undervoltage conditions are
met.
❑ Permission Recloser V B1: Reclosure permission for voltage checks. It´s active when the undervoltage conditions are met.
❑ Perm. Manual Close B1: closure permission for undervoltage or for synchronism. It is active, due to compliance with the
undervoltage conditions or the synchronism conditions. If the function is disabled, manual closure permission will also be
signalled.
❑ Perm. Reclose Br 1: reclosure permission for undervoltage or synchronism, so that the recloser decides on the automatic
closure of the breaker. It is actived, due to compliance with the undervoltage conditions or the synchronism conditions.

User Manual 53
AUTOMATISMS 
Table 2 Synchronism settings
Data Setting Minimum Maximum Step Remarks Type

SynEna Enabled NO/YES enum
SiASel Side A Phase Select A/AB, B/BC, C/CA enum
CoModVs1 Compensation factor (Vs1) 0.1 3 0.01 float
CoArgVs1 Compensation angle (Vs1) 0 330 30 float
PrVSiA A-Side Voltage presence (V) 10 200 0.1 float
AbVSiA A-Side Lack of Voltage (V) 10 200 0.1 float
BrClTmms1 Closing time (ms) 0 100000 10 float
None
No compensation
SyWReEna1 Sync. Enabled (AR) Zero compensation enum
With compensation
Always
None
No compensation
SyWMaClEna1 Sync. Enabled (Close) Zero compensation enum
With compensation
Always
SyDifV1 Voltage difference (V) 0 90 0.1 float
SyDifF1 Frequency difference(Hz) 0.01 5 0.01 float
SyDifA1 Angle difference (º) 0 360 1 float
SlThr Slip threshold (Hz) 0.01 0.1 0.01
ReTmms1 Sync. Time (Autoreclose) 0 100000 10 float
MaClTmms1 Sync.Time (Man.closing) 0 100000 10 float
PrVSiB1 B-Side Voltage presence (V) 10 200 0.1 float
AbVSiB1 B-Side Lack of Voltage (V) 10 200 0.1 float
Without permission
Not A and Yes B
Yes A and Not B
Not A and Not B
ClCond1 Manual closing condition enum
Not A or Not B
A xor B
Not A
Not B
Without permission
Not A and Yes B
Yes A and Not B
Not A and Not B
ReCond1 Autoreclose condition enum
Not A or Not B
A xor B
Not A
Not B
LogInBlSy1 Blocking input Int32
LogInBlCl1 Close blocking Int32
LogInRFF Fuse failure signal Int32
MaskEna Enable Events Record NO/YES Boolean
MaxVSiA3 A-Side Maximum V. (V) 10 200 0.1 float
MaxVSiB3 B-Side Maximum V. (V) 10 200 0.1 float

User Manual 54
AUTOMATISMS 
Table 3 Synchronism function outputs for breaker 1
Signal Data Atribute

Positive Slip Breaker 1 PosSlipBr1 stVal
Negative Slip Breaker 1 NegSlipBr1 stVal
Underfrequency side B B1 UFSideBBr1 stVal
Overfrequency side B B1 OFSideBBr1 stVal
Delay without comp. side B 1 DBNSlipBr1 stVal
Adv. without comp.side B B1 ABNSlipBr1 stVal
Delay with comp. side B B1 DBSlipBr1 stVal
Advance with comp. side B 1 ABSlipBr1 stVal
Over Module side B B1 OAbsBBr1 stVal
Under Module side B B1 UAbsBBr1 stVal
Perm. without comp. B1 PNoSlipBr1 stVal
Perm. with comp. B1 PSlip0Br1 stVal
Perm. Manual Close B1 PMCBr1 stVal
Perm. Close Recloser Br 1 PRecBr1 stVal
Perm. Manual Close V B1 PMClVChBr1 stVal
Permission Recloser V B1 PRecVChBr1 stVal
Permission with compens. 1 PSlipBr1 stVal
Enable Synchro Breaker 1 EnaBr1 stVal
V presence Va/Vab side A SAVPres phsA
V presence Vb/Vbc side A SAVPres phsB
V presence Vc/Vca side A SAVPres phsC
V presence ABC side A SAVPres general
No Voltage Va/Vab side A SAVAbs phsA
No Voltage Vb/Vbc side A SAVAbs phsB
No Voltage Vc/Vca side A SAVAbs phsC
No Voltage ABC side A SAVAbs general
Voltage presence side A SAPres stVal
No Voltage side A SAAbs stVal
V presence side B B1 SBVPresBr1 stVal
No Voltage side B B1 SBVAbsBr1 stVal
A Side Maximun V exceeded3 SAVExc stVal
B Side I1 Maximun V exceeded3 SBVExcBr1 stVal

User Manual 55
MONITORING 
5. MONITORING
5.1 EXTERNAL POWER SUPPLY MONITORING
This function checks if the external supply voltage is within the set range. It generates two signals:
❑ Auxiliary power supply greater than maximum threshold. If the supply voltage exceeds the set maximum threshold.
❑ Auxiliary power supply lower than minimum threshold. If the supply voltage is below the set minimum threshold.
The settings for configuring the external power supply monitoring (Table 4):
❑ Enabled: Enables the external power supply monitoring function.

❑ Minimum threshold. Indicates the minimum power supply voltage threshold, below which an alarm is issued.
❑ Maximum threshold. Indicates the maximum power supply voltage threshold, above which an alarm is issued.
❑ Enable Events record. Allows the generation of protection events associated to the function. If set to “NO”, the function’s
protection events are not generated. If set to “YES”, the function’s specific mask is contemplated.
Table 4 External power supply monitoring settings

SupSpvEna Enabled NO (0) / YES (1) enum
LoSuppV Minimum threshold 10 280 1 float
HiSuppV Maximum threshold 10 280 1 float
MaskEna Enable Events record NO (0) / YES (1) Boolean
There are two independent functions with settings, commands and outputs:
❑ Node:
 PROT/CESS1 for power supply 1
 PROT/CESS2 for power supply 2 (only in devices with redundant power supply)
❑ Settings. There are 6 settings tables. For details see Table 4.
❑ There are no logical inputs or commands
 Vcc Supervision Status. It is active when enabled and not blocked.
 HH Infeed. Indicates that the power supply has exceeded the maximum threshold.
 LL Infeed. Indicates that the power supply is below the minimum threshold.
❑ Measurement. The external power supply values are available in the node GEN/LLN0 (see Table 6)
Table 5 Power supply monitoring outputs
Signal (CESS1) Signal (CESS2: redundant power supply) Data Attribute

Vcc Supervision Status Vcc 2 Supervision Status StEna stVal
HH Infeed HH Infeed 2 OverVcc general
LL Infeed LL Infeed 2 UnderVcc general

User Manual 56
MONITORING 
Table 6 Power supply measurement
Measurement Data Attribute

Power supply Psup net
Power supply2 Psup2 net
5.2 TEMPERATURE MONITORING
This function checks if the temperature is within the set range. It generates two signals:
❑ Temperature greater than maximum threshold. If the temperature exceeds the set maximum threshold.
❑ Temperature lower than minimum threshold. If the temperature is below the set minimum threshold.
The settings for configuring the external power supply monitoring (Table 4):
❑ Enabled: Enables the temperature monitoring function.

❑ Minimum temperature (ºC). Indicates the minimum temperature threshold, below which an alarm is issued.
❑ Maximum temperature (ºC). Indicates the maximum temperature threshold, above which an alarm is issued.
Table 7 Temperature monitoring settings

TmpSpvEna Enabled NO (0) / YES (1) enum
LoTmpVal Minimum temperature (ºC) -40 0 1 float
HiTmpVal Maximum temperature (ºC) 50 100 1 float
It has independent settings, commands and outputs:
❑ PROT/CTSU1 node
❑ Settings. There are 6 settings tables. For details see Table 7.
❑ Outputs: Measurement. The temperature value is available (see Table 9)
❑ Table 8 shows the function’s output data.
 Enabled. It is active when enabled and not blocked.
 Temperature greater than maximum threshold. Indicates that the temperature has exceeded the maximum threshold.
 Temperature lower than minimum threshold. Indicates that the temperature is below the minimum threshold.
❑ Measurement. The temperature value is available (see Table 9)
Table 8 Temperature monitoring outputs
Signal Data Attribute

Enabled StEna stVal
Power supply greater than maximum OverTemp general
Power supply lower than minimum UnderTemp general
Table 9 Temperature measurement

Temperature Temp net

User Manual 57
MONITORING 
5.3 DIS BLOCKING BY LACK OF VAUX
If enabled, it checks that the external power supply exceeds the battery failure threshold, generating an alarm signal when it is below
the threshold.
In devices with redundant power supply, every power supply generates an independent DFFA signal. With the setting "Power Supply" a
general DFFA signal in generated.
The settings for configuring the battery failure monitoring (Table 10)
❑ Enabled: Enables the battery failure monitoring function.

❑ Power Supply: In devices with redundant power supply, selects which power supply generates the DFFA signal:
 PS1. Only Power supply 1 generates DFFA
 PS2. Only Power supply 2 generates DFFA
 PS1 or PS2. Weak Infeed DFFA1 or DFF2 indicates DFFA
 PS1 and PS2. Both power supplies must indicate DFFA.
Table 10 Battery failure monitoring settings

SupSpvEna Enabled NO (0) / YES (1) enum
PS1
PS2
SrcSpv Power Supply enum
PS1 or PS2
PS1 and PS2
There are independent settings and outputs:
❑ PROT/CSUS1 node
❑ Settings. There are 6 settings tables. See Table 10.
 Enabled. It is active when enabled and not blocked.
 Weak Infeed DFFA. Indicates that the external power supply is below the minimum threshold as indicated in the
setting "Power supply".
 Weak Infeed DFFA1. Indicates that the external power supply 1 is below the minimum threshold.
 Weak Infeed DFFA2. Indicates that the external power supply 2 is below the minimum threshold.
Table 11 Battery failure monitoring outputs

Enabled StEna stVal
Weak Infeed DFFA DFFA general
Weak Infeed DFFA1 DFFA1 general
Weak Infeed DFFA2 DFFA2 general
5.4 INTERNAL BATTERY FAILURE MONITORING
The internal battery used for data maintenance is checked to ensure that it does not fall below a security level.
There are independent outputs:

User Manual 58
MONITORING 
❑ GEN/LPHD1 node
❑ It does not use settings.
❑ There are no logical inputs or commands.
 Internal battery failure. Indicates that the internal battery level is below the minimum threshold.
❑ Measurement. The battery value is available (see Table 13)
Table 12 Internal battery failure outputs

Battery failure BatAlm general
Table 13 Internal battery measurement

internal battery IntBat net
5.5 UNIT CHECKS
The unit continually checks the various incorporated elements and cards. If an error is detected in any of the elements or cards, an
alarm is generated. If the error affects the unit’s operation, a critical error is generated, which in addition to the signal acts on :
❑ Colour front LED. Non-configurable status LED, which indicates the unit’s general status. If the LED is green, it indicates
that everything is correct, while if it is red it indicates a critical error in the unit.
❑ CPU Relay. Non-configurable 3-contact relay, which indicates the unit’s general status. If the LED is active (common
terminal – NO), it indicates that everything is correct, while if it is deactivated (common terminal– NC) it indicates a critical
error in the unit. If the unit is switched off, the relay is deactivated.
❑ The unit's alarm signals are to be found in the LPHD node. The available signals indicate faults in the card check, in the
communications between the cards, in the unit’s configuration, etc.:
❑ Critical hardware error. Indicates that a critical error has been produced. In addition to this signal, the cause that produced
the signal will be indicated.
❑ CPU error. Indicates that the check has detected an error in the CPU. It generates critical error signal.
❑ Analogue error. Indicates an error in transformers card. It generates critical error signal.
❑ I/O micro error. Indicates an error in the I/O cards’ micro.
❑ Analogue connection error. Indicates that a fault has been produced in the communications between the CPU and the
transformers card. It generates critical error signal.
❑ I/O connection error. Indicates that a fault has been produced in the communication between the CPU and an I/O card. It
generates critical error signal. Additionally, it will indicate the card which has suffered the failure:
 Error card address x. Indicates that there is a communication error with the card with the address x.
❑ Front connection error. Indicates that a fault has been produced in the communications between the CPU and the unit’s
front card. It generates critical error signal.
❑ Shared analogue memory error. Indicates that a fault has been produced in the Data exchange memory between the CPU
and the transformers card. It generates critical error signal.
❑ Error shared I/O memory. Indicates that a fault has been produced in the Data exchange memory between the CPU and
the I/O cards. It generates critical error signal.
❑ RTC clock error. Indicates that the check has detected an error in the real time clock.
❑ Continuous component monitoring alarm. Indicates that an error in the continuous measurement monitoring has been
detected in the transformers card.

User Manual 59
MONITORING 
❑ Alarm settings. Indicates that errors have been detected in the storage of the unit’s settings. It generates critical error
signal.
❑ FW Alarm. Indicates that the relay firmware versions are incompatible.
❑ Memory check alarm. Indicates that errors have been detected in the checking of the unit’s memory. It generates critical
error signal.
❑ Converter check alarm. Indicates that errors have been detected in the transformers card AD converter. It generates
critical error signal.
❑ Converter voltage level alarm. Indicates that errors have been detected in the transformers card reference voltages. It
generates critical error signal.
❑ Relay activation alarm. Indicates that an error has been detected in the activation of at least one of the I/O cards’ relays. It
generates critical error signal.
❑ I/O configuration error. Indicates that the configuration of the I/O cards does not coincide with the unit’s correct
configuration. It generates critical error signal.
❑ General Vdc error. Indicates a failure in the internal power supply levels. It generates critical error signal.
❑ Frequency configuration error. This is not a unit failure, but rather a configuration failure. Indicates that the frequency
measurement of the signals being injected into the unit do not match the set measurement, that is, the unit is configured
as 50Hz and the signals which are being injected are greater than 55Hz; or that the unit is configured as 60 Hz and the
signals being injected are less than 55 Hz.
❑ Internal battery failure. Indicates that the data storage battery is below the security levels and that the data may be lost at
shutdown.
❑ Version compatibility error. Indicates that the versions of the unit's firmware are not correct.
❑ Time setting configuration alarm. Indicates that there is an error in the configuration of the unit’s time setting.
❑ For each I/O card there is are 5 signals, indicating:
 Status OK. Indicates that the card is configured correctly and without errors.
 Configured & No_detected. Indicates that the card is configured by the user, but not detected in the unit. This may be
because it is not assembled or because it has an error. Equivalent to the current communication error.
 Different configuration. The type indicated by the user and the type detected by the unit do not coincide.
 No_configured & detected. Indicates that card that has not been configured by the user has been detected in an
address.
 Internal card error. A card check error has been received (includes relay check).
❑ ICD error. Indicates the last ICD received by the device was wrong and it was refused by the device. Once activated, this
signal is deactivated when a correct ICD is received.
❑ Power supply 1 OFF. Indicates that the power supply 1 is turned off. It is only available in devices with redundant power
supply.
❑ Power supply 2 OFF. Indicates that the power supply 2 is turned off. It is only available in devices with redundant power
supply.
❑ SV Board Error. Indicates that there is an error in the sampled values board.

User Manual 60
MONITORING 
Table 14 Checking signals

Critical hardware error HwCrAlm stVal
CPU error CPUAlm stVal
Analogue error AnaAlm stVal
I/O micro error ESAlm stVal
Analogue connection error AnaComAlm stVal
I/O connection error ESComAlm stVal
Front connection error MMIComAlm stVal
Shared analogue memory error AnDPMAlm stVal
Shared I/O memory error ESDPMAlm stVal
RTC clock error RTCAlm stVal
Continuous component monitoring alarm Harm0Alm stVal
Alarm settings SettingAlm stVal
Firmware alarm FwAlm stVal
Memory check alarm MemAlm stVal
Converter check alarm ADCAlm stVal
Converter voltage level alarm VRefAlm stVal
Relay activation alarm DOAlm stVal
I/O configuration error IOCnfError stVal
Card address error 1 GGIO1Alm stVal
Same as rest of I/O up to 8
Card address error x (x from 2 to 8) GGIOxAlm stVal
General Vdc error VccError stVal
Frequency configuration error FrConfAl stVal
Internal battery failure BatAlm stVal
Version compatibility error VerAlm stVal
Time setting configuration alarm HSetAlm stVal
ICD error FailICD stVal
Card 1 ok GGIO1Ok stVal
Card 1 ConfiguredYNo_detected GGIO1Nodet stVal
Card 1 Different configuration GGIO1Dif stVal
Card 1 No_configured Y Detected GGIO1NConf stVal
Card 1 Internal card error GGIO1HwErr stVal
Same as rest of I/O up to 8
Front ok FRONTOk stVal
Front Configured Y No_detected FRONTNodet stVal
Different front configuration FRONTDif stVal
Front No_configured Y Detected FRONTNConf stVal
Front Internal card error FRONTHwErr stVal
Power supply 1 OFF FailSup1 stVal
Power supply 2 OFF FailSup2 stVal
SV Board Error SVError stVal

User Manual 61
CONFIGURATION 
6. CONFIGURATION
6.1 CID
6.1.1 Data Storage

The unit has a CID file that follows the format defined in section 6 of the IEC 61850 standard. It is available via the following path by
FTP “SCL/validated”, in which all the unit’s configuration information is saved, either structured in nodes that follow the IEC 61850
format or in private parts.
6.1.2 Updating CID

There are different ways to change the settings. They are listed below:
❑ Using MMS in IEC 61850

❑ Using local display
❑ Using the pacFactory (PC tool)
❑ By sending the CID by FTP to the “SCL/notvalidated” directory
Independently of the form used from among those listed above, the changes to the affected setting are stored in the unit’s CID file.
CONFIGURATIONS USING ED1:

On devices with IEC61850 Edition 1 configurations, when any setting is changed, the paramRev field in the node in which the
new setting has been written, as well as the LLN0 node of the Logical Device to which the node belongs, are updated in the CID
file.
The format of the paramRev data is as follows:
XXX year.month.day.time.minute.second [paramRev origin text]
❑ Where “XXX” is an integer counter that is incremented each time paramRev is updated by a setting change.
❑ "paramRev origin text“depends on the origin of the setting change:
Origin of settings change paramRev text origin

MMS IEC 61850 client BROWSER IP
Local display USER DISPLAY
pacFactory USER TOOL
New CID CID UPDATE
In the case of “New CID”, only those settings in the CID sent to the unit and which are out of range will be updated in
paramRev.
6.2 GENERAL
Two nodes are used for the general configuration of the unit
❑ GEN/LLN0. Includes the unit’s generic configuration settings

User Manual 62
CONFIGURATION 
The settings available in the GEN/LLN0 node are shown in protection events mask enablind. Allows the generation of protection events
associated to the function. If set to "NO", the function's protection events are not generated. If set to "YES", the function's specific
mask is contemplated:
❑ Language. Indicates the unit’s language. Affects the display, reports, etc.
❑ Functional key block. It allows the functional key to be blocked. When blocked commands with functional key are not
allowed.
❑ Functional keys (remote). It allows key commands with the device in remote mode.
❑ Leds Blocking. Allows the activation of the LEDs to be blocked.
❑ Blocking allowed by command. It allows blocking the reception of block/unblock protection commands.
❑ Reset Digital Output. Indicates the logic input that, when activated, reset all the digital outputs.
❑ The supported IRIG-B formats are B002, B003, B006, B007 and IEEE1344. It select whether the year is taken into account in
the synchronization by IRIG. The options are:
 “UTC without year”. The year is not taken into account and all the formats are admitted.
 “UTC with year”. With formats B006, B007 and IEE1344 the year is not taken into account. It cannot be used with
formats B002 and B003 because they set the year to zero value.
 “Local without year”. The year is not taken into account. All the formats are admitted.
 “Local with year”. With formats B006, B007 and IEE1344 the year is not taken into account. It cannot be used with
formats B002 and B003 because they set the year to zero value.
❑ Local/remote selection. Indicates the logic input that, when activated,changes the device between local/remote.
❑ Erase records. Indicates the logic input that, when activated, deletes the unit’s report queues. Affects protection events,
faults, disturbance reports, historical measurement reports, etc.
❑ Remote/ Local type. It indicates how the unit will behave when it has to block the commands it is sent. See 13.2.1
❑ Flicker Enable. Enables the digital inputs’ swing supervising function.See 6.4.3
❑ Block full records. When set to "NO", queues are circular, when the maximun number of registers is fullfiled, the oldest
one is erased. If sets to "YES", when the maximun number of registers is fullfiled, the queue is blocked and no more
registers are stored. It affects protection events, faults, disturbance reports, historical measurement reports.
Table 15 General settings

Lang Language Spanish (0) / English (1) Boolean
BlkFKeys Functional keys blocking NO (0) / YES (1) Boolean
FKeysRem Functional keys (remote) Boolean
BlkFrCom Leds Blocking NO (0) / YES (1) Boolean
LogInReDO Blocking allowed by command Int32
BlkComm Reset Digital Outputs Boolean
UTC without year /
UTC with year /
IrgType IRIG-B002 format enum
Local without year /
Local with year
LogInLR Local/remote selection Int32
LogInDelRe Erase records Int32
Not treated (0)
Iberdrola (1)
LRmode Remote/Local Type 0 3 1 enum
Exclusive (2)
No HMI (3)
FlickerEna Flicker Enabled 0 1 1 NO (0) / YES (1) enum
MaskEna Enable Events Record NO (0) / YES (1) Boolean
BlkFRec Block full records NO (0) / SI (1) Boolean

User Manual 63
CONFIGURATION 
6.3 FRECUENCY, MEASUREMENT AND TRANSFORMERS
The current and voltage transformers are configured in independent nodes, in which the units’ rated values, transformation ratios and
frequencies are indicated.
6.3.1 Current
Two GEN/TCTR nodes are used for the transformation ratios and GEN/TCIN for rated currents.
The settings used for the configuration of the current transformers ratios, which are used to provide primary measurements, are
(see Table 16):
❑ Phase current ratio. Indicates the phase current transformation ratio.

❑ Neutral current ratio. Indicates the neutral current transformation ratio.
The settings used for configuring the rated currents are (see Table 17):
❑ I rated phases. Selects the value of the rated phase current.

❑ I rated neutral. Selects the value of the rated neutral current.
Table 16 Current transformation ratios

PhsRat Phase current ratio 1 10000 0.1 float
GndRat Neutral current ratio 1 10000 0.1 float
Table 17 Rated currents

PhsInom I rated phases 1A (1)/ 5A (2) enum
GndInom I rated neutral 1A (1)/ 5A (2) enum
6.3.2 Frequency and voltage

The GEN/TVTR node is used for the voltage and rated voltage transformation ratios (see Table 18).
❑ Phase transformation ratio. Indicates the phase voltage transformation ratio.

❑ Rated phase-earth V (V sec). Selects the rated voltage.
❑ Frequency. Selects the unit’s rated operating frequency 50Hz or 60Hz
❑ Ground voltage ratio (VN). Indicates the neutral voltage transformer ratio.
❑ Ground Rated Voltage. Selects the rated ground voltage
❑ Connection Type. Selects the connection used.
❑ Synchro voltage ratio. Indicates synchronism 1 voltage transformer ratio.
Table 18 Voltage characteristics

VRat Phase transformation ratio 1 10000 0.1 float
VRtg Rated phase-earth V (V sec) 40 200 0.1 float
HzRtg (HzVal in Ed2) Frequency 50Hz (0) /60Hz (1) enum
VNRat Ground voltage ratio (VN) 1 10000 0.1 float
A(0), B(1), D(2),
ConTyp Connection Type enum
E(3), F(4), G(5)
VsRat1 Synchro voltage ratio 1 10000 0.1 float

User Manual 64
CONFIGURATION 
6.3.3 Power and energy

The GEN/MPWE node, which indicates the conditions for the power calculation, is used (see Table 19):
❑ Real energy constant. Indicates the real energy impulse factor, i.e., the number of kWh by virtue of which the
counter is incremented by one unit.
❑ Reactive energy constant. Indicates the reactive energy impulse factor, i.e., the number of kWh by virtue of which
the counter is incremented by one unit.
The energy counters value is available in the PROT/MMTR node, with the data:
❑ Positive real energy counter: SupWh.

❑ Negative real energy counter: DmdWh.
❑ Positive reactive energy counter: SupVArh.
❑ Negative reactive energy counter: DmdVArh.
Table 19 Power characteristics

CorWh Constant real power (kWh) 1 1000 1 enum
CorVArh Constant reactive power 1 1000 1 enum
6.4 INPUTS/OUTPUTS
The unit can host a variable number of input-output cards variable (from 1 to 7). Each card is configured with an internal address from
2 to 7. The power supply is assigned address 1, which is not configurable.
Each card is represented in the IEC 61850 data model as an instance of the GGIO node in the Logical Device called “GEN”. Each GGIO
has the internal address of the physical card as an instance. Thus, for example, if a unit has two input-output cards with internal
addresses 1 and 4, the GEN/GGIO1 and GEN/GGIO4 nodes will exist in the data model.
The number of digital input settings and signals present in each GGIO depends on the type of card used. Continuing the example, if the
card with the internal address 1 has 6 digital inputs and 4 digital outputs, the GGIO1 node will have 6 digital input signals and 4 digital
output signals, as well as the settings corresponding to each digital input and output available.
The data model associated to the GGIOs is common to all and has 32 digital inputs and 16 digital outputs. Nevertheless, in each card
only the data associated with its own inputs and outputs are updated.
For each GGIO there is a boolean setting called MaskEna (event record enabled). If set to “YES”, the activation/deactivation of the
digital inputs and outputs will generate protection events. To the contrary, they will not be stored as event records.
6.4.1 Inputs
There are 2 settings available for each digital input:
❑ DIxTmms: Digital input time x (ms). This is a software filter for the activation/deactivation of digital inputs. It
indicates the milliseconds (range 0 to 100 ms4) which a digital input must be seen to be active in order to be
considered active. In order to calculate an input's total activation time, the input’s hardware filter delay – which is
approximately 1ms – must be added to this time.
❑ DIxType: Digital input type x. Defines whether the input is to be interpreted as active when it is seen as closed (NO)
or when it is seen as open (NC)
Each digital input has an associated digital signal indicating its status (see Table 20). Each GGIO indicates the status of all its digital
inputs (up to 32).
4
From firmware version 5.20.15.8 and ICD version 6.3.0.0. In previous versions the maximun was 20ms

User Manual 65
CONFIGURATION 
Table 20 Digital input signals

Digital input 1 Ind1 stVal
Remaining inputs
6.4.2 Outputs
There are 3 settings available for each digital output:
❑ DOxSig: Assignment digital output x. Assigns the activation of the digital output. There are several assignment
possibilities:
 Signals: They can be signals generated by the unit (trips, logics, hw check, digital inputs and outputs)
 Commands: All of the commands available in the unit can be directly programmed to a physical output
❑ DOxTmms: Digital output time x (ms). The output activation time defines the minimum operational time of each
physical output following activation (in milliseconds). The range is 0.05 to 5000 ms. The output remains active in
accordance with this time setting or the duration of the associated signal, whichever is greater.
❑ DOxTyp: Digital output type. Each output’s type is defined from among the options:
 “Not”. The output follows the assigned signal, i.e., the output is activate when the signal is active. When the
signal is deactivated, the output will deactivate if the digital output time has elapsed. To the contrary, the
output will remain active until this time elapses.
 “Stored”. Once activated, the output remains active until the relay deactivation command is issued, with the
signal assigned to the output deactivated. The command can be issued by the action of a digital input
programmed as “Local reset”, a command or by keyboard/display.
Each digital input has an associated digital signal indicating its status (see Table 22Table 22). Each GGIO indicates the status of all its
digital outputs (up to 16).
Table 21 Input/output settings

OscTms Input oscillation time (s) 1 60 1 Int32
Nchanges Number of changes 0 255 1 Int32
DI1Tmms Digital Input Time 1 (ms) 0 100 1 Int32
DI1Type Digital Input Type 1 NO (0) / NC (1) enum
DI2Tmms Digital Input Time 2 (ms) 0 100 1 Int32
DI2Type Digital Input Type 2 NO (0) / NC (1) enum
Remaining inputs DI3x, DI4x..
DO1Sig Digital Output Assignment 1 Int32
DO1Tmms Minimum Output Time 1 (ms) 0 5000 1 Int32
DO1Ty Digital Output Type 1 enum
DO2Sig Digital Output Assignment 2 enum
DO2Tmms Minimum Output Time 2 (ms) 0 5000 1 enum
DO2Ty Digital Output Type 2 Int32
Remaining inputs DI3x, DI4x..
Table 22 Digital output signals

Digital output 1 SPCSO1 stVal
Remaining outputs

User Manual 66
CONFIGURATION 
6.4.3 Treatment of digital input flicker

Flicker consists of a fast and continuous change of a digital input, usually associated with a failure in the input’s contact. The
function allows a control to be performed to disable the flickering digital inputs or signals in order to prevent them from interfering
with the control system, as a disabled digital does not generate status changes.
The supervising of the swing in the digital inputs or the supervising of the flicker is conducted in accordance with certain user-
configurable settings.
On the one hand, there is a general setting that allows this function to be enabled or disabled. If this setting is disabled, not flicker
treatment is performed.
General setting for the configuration of the flicker treatment (Table 23):
❑ FlickerEna: Enables the digital inputs’ swing supervising function.
Table 23 General flicker treatment setting

FlickerEna Flicker enabled 0 1 1 NO (0) / YES (1) enum
❑ GEN/LLN0 node
Once the general flicker setting has been enabled (Table 23), there are two more setting per card for treating the swing.
They are “OscTms” and “Nchanges” which can be seen in Table 21:
❑ OscTms: The time between changes in the same direction in order for a signal to be deemed to be swinging. When a signal
is swinging a swinging signal is produced. The unit is seconds.
❑ Nchanges: The number of changes that must be produced in a swinging signal in order for the signal to become invalid and
cease from sending changes. If this setting is set to zero, it disables the swing treatment for this card, i.e., the flicker
treatment is not performed for this card.
❑ GEN/GGIOx node, in which x depends on the card’s internal address (see section 6.4)
Once a signal has been detected as swinging, it becomes questionable and oscillatory.
If this situation continues and the number of set changes (“Nchanges” setting) is exceed, the signal becomes invalid and oscillatory.
It ceases to send the changes and sends the signal's last known valid status.
When the time difference between two changes is greater than the inputs’ swing time (“OscTms” setting), the signal changes to
valid.
6.5 LEDS
6.5.1 Via GEN/IHMI node

The LEDs are programmed within the IHMI node located in the “GEN” Logical Device. There are 2 settings available for each LED:
❑ LexSig: Assignment led x. Assigns the activation of LED x using any of the signals generated by the unit
❑ LExTyp: LED type x. It can be programmed as “not” and “stored”. In the first case, the activation of the LED follows
the activation of the signal programmed in the setting described above. If it is programmed as “stored”, the LED’s
activation will remain even if the signal that provoked its activation drops out, until the signal programmed in the
LogInReLed setting available in the IHMI node is activated.
There is a general setting for all the LEDs that indicates the logic signal used to switch of the LEDs:
❑ LED reset. Selects the signal which, when active, switches off the LEDs.
The LEDs are updated every 200ms. Thus, for the correct activation of the LEDs, the assigned signal must remain active for at least
150 ms. To the contrary, the LED cannot be activated.

User Manual 67
CONFIGURATION 
Table 24 LED settings

LogInReLed LED reset Int32
Le1Sig Led 1 assignment 0 20 1 Int32
Le1Ty Led 1 type Not (0) /Stored (1) enum
Le2Sig Led 2 assignment 0 20 1 Int32
Le2Ty Led 2 type Not (0) /Stored (1) enum
Remaining LEDs up to 19
6.5.2 Via CTRL/IHMI node

If the unit, in addition to the “GEN” Logical Device’s IHMI node defined in the previous section, has an IHMI node located in “CTRL”
Logical Device, the unit’s treatment in relation to the configuration of the LEDs differs as follows:
❑ The parameterization of the assignment of LEDs is carried out by the settings present in the CTRL/IHMI node.
❑ The parameterization of the LEDs type is carried out by the settings present in the CTRL/IHMI node.
The settings present in this node are detailed below

InRef1 Led 1 assignment - - - InRef
LEDSe1 Led 1 type Not (0) /Stored (1) enum
InRef2 Led 2 assignment - - - InRef
LEDSe2 Led 2 type Not (0) /Stored (1) enum
Remaining LEDs up to 19
There are 2 settings available for each LED:
❑ InRefx: Assignment led x. Assings the activation of LED x using any of the signals generated by the unit. The
assignment is carried out by means of a character string (see next section “Configuration with InRef”)
❑ LEDSex: LED type x. It can be programmed as “not” and “stored”. In the first case, the activation of the LED follows
the activation of the signal programmed in the setting described above. If it is programmed as “stored”, the LED’s
activation will remain even if the signal that provoked its activation drops out, until the signal programmed in the
LogInReLed setting available in the GEN/IHMI node (defined in the previous section) is activated.
6.6 CONFIGURATION WITH INREF
The InRef type settings are programmed by a string of characters in which the reference of the IEC 61850 object containing the value to
be employed as an input is indicated. The following format, as defined in the part 7.2 of the IEC 61850 standard, is employed:
LDName/LNName.DataObjectName[.SubDataObjectName[. ...]].DataAttributeName
For example,
❑ In order to program InRef1 with the GGIO1 input signal 1, the reference to be written in the InRef is:
GEN/GGIO1.Ind1.stVal
6.7 GENERIC COMMAND
Generic commands are available within the Logical Device "GEN" on the ordGGIO1 node, which will be active for 100msg.
The commnad are the following:
❑ SPCS01, Generic command 1


User Manual 68
CONFIGURATION 
❑ ………..
Are available signals associated with these generic commands, which will be available in logic, output, etc.

Generic command 1 activation Ind1 stVal
--------- stVal
Generic command 1 desactivation Ind17 stVal
--------- stVal
6.8 NAMES
The PROT/LPHD node is used for the general configuration of the units’ names and the installation.
Short names are used for the generation of the disturbance recorder and fault file names.
The settings for this node are shown in Table 25:
❑ Installation name: Full name of the installation.

❑ Short name of the installation. Short name of the installation. Limited to 10 characters, this is used in the generation of
disturbance recorder and fault files. Neither spaces nor commas are permitted in the name.
❑ Relay name. Full name of the relay.
❑ Short relay name. Short name of the installation. Limited to 10 characters, this is used in the generation of disturbance
recorder and fault files. Neither spaces nor commas are permitted in the name.
❑ Name of breaker 1. Full name of breaker 1.
❑ Name of breaker 2. Full name of breaker 1.
Table 25 Name settings

InstNam Installation name String
InstShNam Short name of the installation 10 characters String
RelNam Relay name. String
RelShNam Short relay name 10 characters String
BkrNam1 Name of breaker 1 String
BkrNam2 Name of breaker 2 String
6.9 IPRV NODES CONFIGURATION
6.9.1 General IPRV settings

The device has several settings (included in the GEN/genIPRV logical node) to set certain operating modes.
These settings are considered special and they are configurable via an IEC 61850 connection or sending the CID file after editing the
values from pacFactory tool (menu Settings -> IPRV). They do not appear in the display or section pacFactory protection settings.
The settings included in this logical node are:

User Manual 69
CONFIGURATION 
❑ LocalTim: Allows to force sending local time in IEC 61850 timestamps. It is important to know that this is not normative
because IEC 61850 standard defines that the timestamps must be sent in UTC format. However, with this option the device
is adapted to systems that only use local time. The default value is 0, which indicates the use of UTC. The value 1 indicates
the use of local time.
❑ MaxConn: Sets the maximum number of IEC 61850 connections that are accepted. Limited to a maximum value of 16.
❑ AplicTms: Defines the disconnection timeout at the application level. After this time (in seconds) without receiving any IEC
61850 messages the server automatically closes the connection.
❑ TipoServ: Defines some operation modes of the device.
 Value 0: Default operation mode.
 Value 1: Special operation mode that includes:
 Enable IP checking to validate a new ICD/CID file. If the IP address indicated in the communications section of
the ICD/CID file does not match the address of the device the file is not validated. If the IP address of the
device is changed once the file has been validated, the IEC 61850 server is disabled and waits for the change of
the IP address of the device with the one in the file or to receive a new CID file with the correct IP.
 When a command is received, the value that the device saves in "orIdent" attribute is the IP address from
which the command was sent, regardless of the value that the client sent in the message.
❑ AuthReq: Allows activating the password authentication in the establishment of IEC 61850 connection. The password
received is checked against the one assigned to the user “user61850”.
 The default password for this user is: user61850.
❑ DevGoose: Selects the Ethernet port for GOOSE messages. Any online change of this value requires the reset of the device
and therefore the signal ResetDev is activated.
 Eth1: GOOSE publication and reception enabled on interface ETH1.
 Eth2: GOOSE publication and reception enabled on interface ETH2.
 Both (Eth1): Reception on both interfaces (ETH1 and ETH2). Publication is sent by only one configurable
interface for each GOOSE. By default port ETH1.
 Both (Eth2): Reception on both interfaces (ETH1 and ETH2). Publication is sent by only one configurable
interface for each GOOSE. By default port ETH2.
❑ NoGsVlan: Defines the use of the VLAN tag in GOOSE messages. Any change in this value causes the activation of the signal
ResetDev. Default value is 0.
 Value 0: GOOSE messages are sent with VLAN TAG and are received with or without VLAN TAG.
 Value 1: GOOSE messages are sent and received only without VLAN TAG.
❑ IprvMod: Sets the access level to reports, commands and logs from the different IP addresses configured in the IPRV logical
nodes defined in the following paragraph:
 Permissive: By default all IP addresses not configured in the IPRV logical nodes have access to reports,
commands and logs. The IP addresses included in the IPRV logical nodes will have the configured access level.
 Restrictive: Only IP addresses configured in the IPRV logical nodes have access to reports, commands and logs.
The access level is configured individually for each IP address. Other IP addresses do not have access.
❑ IprvConn: The value 1 limits the IEC 61850 connections only to IP addresses configured on IPRV logical nodes and any
connection from other IP address will be rejected. The value 0 allows the connection from any IP address.
Only the settings that indicate the activation of the signal ResetDev require a restart of the device to be effective.
6.9.2 IEC 61850 clients IPRV settings

There are 8 instances of this logical node (GEN/IPRVx) to configure the level access to reports, commands and logs of up to 8 IEC
61850 clients. Each client is identify by its IP address. The available settings for each logical node are:
❑ Addr: IP address of the client.

❑ EnaRpt: Enumerated value to configure the access level to reports from the defined IP address.
 [0] All: Allows access to all reports.
 [1] Yes: Allows access only to the reports defined in RptNam fields.

User Manual 70
CONFIGURATION 
 [2] No: Not allowed access to any report.

❑ CmdEna: Boolean setting that with value 1 allows the execution of commands from the defined IP address.
❑ EnaLog: Enumerated value to configure the access level to logs from the defined IP address.
 [0] Read only: Only read access to the logs.
 [1] Read/write: Read and write access to the logs.
The signal GEN/IPRVx.St.stVal indicates whether the address configured on that node is in communication with the device. In case
of multiple connections from the same IP, the signal is 0 when all are closed.
These settings are considered special and they are configurable via an IEC 61850 connection or sending the CID file after editing the
values from pacFactory tool (menu Settings -> IPRV). They do not appear in the display or section pacFactory protection settings.
6.10 MEASUREMENT’S RANGE AUTOMATIC CONFIGURATION
Measures logical nodes which have the AdRanMea setting have the possibility of the automatic configuration of the measures
ranges (with value 1 in the AdRanMea setting).
AdRanMea settings in different logical nodes are independent. Each logical node can be configured independently.
Only de ranges of measures with a sAddress value are calculated.
If the value of AdRanMea setting is 1, the range configuration cannot be modified via IEC 61850 protocol.
The values that are automatically calculated are:
Measures:
❑ rangeC.hhLim.f
❑ rangeC.hLim.f
❑ rangeC.lLim.f
❑ rangeC.llLim.f
❑ rangeC.min.f
❑ rangeC.max.f
Angles:
❑ rangeAngC.hhLim.f
❑ rangeAngC.hLim.f
❑ rangeAngC.lLim.f
❑ rangeAngC.llLim.f
❑ rangeAngC.min.f
❑ rangeAngC.max.f
The calculation is made based on the values of scale range and transformation ratio of each measure as follows:
❑ Signed measures:
❑ max: scale range * transformation ratio
❑ min: - (scale range * transformation ratio)

User Manual 71
CONFIGURATION 
❑ Unsigned measures
❑ max: scale range * transformation ratio
❑ min: 0
And the value of the factor configured in the multiplier attribute is applied:
❑ If multiplier > 0 it is divided by 10 multiplier

❑ If multiplier < 0 it is multiplied by 10 multiplier
In both cases the limits are configured as:
❑ hLim = max
❑ hhLim = max
❑ lLim = max * 4 / 5
❑ llLim = max * 4 / 5
The rest of the configuration values of each measurement (db, SIUnits, multiplier, dbAng, limDb) are not modified.

User Manual 72
SYNCHRONIZATION 
7. SYNCHRONIZATION
Several synchronization sources are permitted, with the following priority:
❑ IEEE1588v25
❑ IRIG-B
❑ SNTP
❑ Communication protocols
❑ pacFactory (see specific user manual)
❑ Local display
In case of active synchronization with any of the sources, the sources of lower priority are blocked. Some examples:
❑ If there is synchronization by IEEE1588v2, synchronization for any other cause is not permitted. In order to consider the absence of
IEEE1588v2 synchronization and to allow other sources, 1.5 minutes must elapse without synchronization:
 When disabled by setting
 When you lose IEEE 1588v2 communication through the port (synchronization does not arrive)
 When it loses traceability or precision (the master is not synchronized)
❑ If there is synchronization by IRIG, synchronization for any other cause is not permitted. In order to consider the absence of IRIG
synchronization and to allow other sources, 1.5 minutes must elapse without the reception of correct IRIG frames.
❑ If there SNTP synchronization, the synchronization of protocols is not permitted, nor pacFactory nor display. However, if IRIG
synchronization is received, the SNTP is blocked and IRIG is synchronized.
❑ Synchronization by pacFactory and by display have the same priority and can be run simultaneously.
7.1 GENERAL SETTINGS
The unit’s data model has a GEN/LTIM node for the configuring the summer/winter time change. The node has the following settings
(see Table 26):
❑ Offset Local Time-UTC (min): Offset Local Time-UTC (min). A setting that indicates the number of minutes by which the time setting
must be put forward/put back when changing between summer/winter time. Range between -720 and 720 minutes (-12 to + 12
hours)
❑ Summer-winter time change enabled: Time change enabled. A boolean setting that allows the time setting to be changed
❑ Summer Calendar Pattern: Summer Calendar Pattern. Three selectable values:
 Last of month: Last week, refers to the weekday set in WkDayD
 First of month: First week, refers to the weekday set in WkDayD
 Second of month: Second week, refers to the weekday set in WkDayD
 Third of month: Third week, refers to the weekday set in WkDayD
 Fourth of month: Fourth week, refers to the weekday set in WkDayD
 Day of month: Selects the day of the month indicated in DayD
❑ Day Week Summer: Indicates the day of the week for the change to summer time (Monday.. Sunday)
❑ Month Summer: Indicates the month in which the change to summer time occurs (January.. December)
❑ Day Summer: Indicates the day in which the change to summer time occurs (1.. 31)
❑ Time Summer: Indicates the time at which the time changes to summer time
❑ Minute Summer: Indicates the minute (within the time set on HrD) when the time changes to summer time
❑ Winter Calendar Pattern: Winter Calendar Pattern. Equivalent to OccD but from winter to summer
5
Available from firmware version 6.0.18.0
User Manual 73
SYNCHRONIZATION 
❑ Day Week Winter: Indicates the day of the week for the change to winter time (Monday.. Sunday)
❑ Month Winter: Indicates the month in which the change to winter time occurs (January.. December)
❑ Day Winter: Indicates the day in which the change to winter time occurs (1.. 31)
❑ Time Winter: Indicates the time at which the time changes to winter time
❑ Minute Winter: Indicates the minute (within the time set on HrS) when the time changes to winter time
❑ Not Synchro Time (min): Timeout to activate synchronization alarm.
Table 26 Synchronization settings

TmOfsTmm Offset Local Time-UTC (min) -720 720 1 Int32
TmUseDT Summer-winter time change enabled NO (0) / YES (1) Boolean
OccD Summer Calendar Pattern 0 2 1 enum
WkDayD Day Week Summer 0 6 1 enum
MthD Month Summer 1 12 1 enum
DayD Day Summer 1 31 1 Int32
HrD Time Summer 0 23 1 Int32
MnD Minute Summer 0 59 1 Int32
OccS Winter Calendar Pattern 0 2 1 enum
WkDayS Day Week Winter 0 6 1 enum
Mths Month Winter 1 12 1 enum
DayS Day Winter 1 31 1 Int32
HrS Time Winter 0 23 1 Int32
MnS Minute Winter 0 59 1 Int32
SyncAlmTm Not Synchro Time (min) 1 1440 1 Int32
There are signals indicating the synchronization source (Table 27):
❑ Synchronization by IEEE1588: Active when the device is synchronized by IEEE1588. It is maintained activated for 90 seconds after
an IEEE1588 synchronization.
❑ Synchronization by IRIG-B: Active when the device is synchronized by IRIG-B. It is maintained activated for 90 seconds after an IRIG-
B synchronization.
❑ SNTP synchronization: Active when the device is synchronized by SNTP. It is maintained activated the period defined by not synchro
timeout SNTP setting (ValTm) after an SNTP synchronization.
❑ Synchronization by protocols: Active if the last synchronization was been received by communications protocols.
❑ Synchronization by display: Active if the last synchronization was been received by the front keyboard.
❑ Synchronization by console: Active if the last synchronization has been received from the PacFactory console.
❑ Device not synchronized: Synchronization alarm. Active if a valid synchronization (IRIG-B, SNTP or protocols) has not been received
during the timeout configured by the not synchro time setting (SyncAlmTm).
❑ Daylight saving time: Active if the local time has summer correction.
Table 27 Synchronization source

Synchronization by IEEE1588 SyncPTP stVal
Synchronization by IRIG-B SyncIRIGB stVal
Synchronization by SNTP SyncSNTP stVal
Synchronization by protocols SyncProt stVal
Synchronization by display SyncDispl stVal
Synchronization by console SyncCons stVal
Device not synchronized SyncAlm stVal
Daylight saving time TmDT stVal

User Manual 74
SYNCHRONIZATION 
7.2 IEEE 1588V2
The IEEE Std. 1588-2008, also known as IEEE 1588v2 or PTPv2, offers a good solution for clock synchronization in distributed systems
with high accuracy requirements. It works through Ethernet networks and achieves accuracy in the submicrosecond range.
Ingepac EF IEDs support IEEE 1588v2 and specifically the IEC 61850-9-3:2016 Ed1, also nown as Power Utility Profile (PUP), which allows
compliance with the highest synchronization classes of IEC 61850-5 and IEC 61869-9.
Following the IEC 61850-9-3:2016 Ed1 profile:
❑ The PTP over IEEE 802.3 transport mapping, specified in Annex F of IEEE 1588v2, shall be the only transport mechanism used.
❑ The peer delay request mechanism specified in Chapter 11.4 and Annex J.4 of IEEE 1588v2 shall be the only path delay
measurement mechanism in operation.
Ingepac EF IEDs support IEEE 62439-3:2016 Ed 3 Annex A when 1588 synchronization over PRP or HSR is needed.
7.2.1 Settings
There are 3 settings to set up IEEE 1588v2. They all belong to the GEN/LTMS logical node described in 1.4.1.
❑ Main Time Source: The string “1588” must be set up in this setting in order to enable 1588v2.
❑ PTP interface: This setting specifies the interface in which the IED will listen to IEEE 1588v2 messages.
❑ PTP delay mechanism: The Mechanism used peer to peer (P2P).
7.3 IRIG-B
The device is equipped with an input for synchronization by GPS, using IRIG-B time codes (consult chapter 2 for more details about the
input).
The supported IRIG-B formats are B002, B003, B006, B007 and IEEE1344. The configuration is with the IrgType setting in the GEN\LLN0
logical node (General configuration). The different options are (depending on whether the GPS send UTC or local time):
❑ “UTC without year”. The year is not taken into account and all the formats are admitted.
❑ “UTC with year”. With formats B006, B007 and IEE1344 the year is not taken into account. It cannot be used with formats
B002 and B003 because they set the year to zero value.
❑ “Local without year”. The year is not taken into account. All the formats are admitted.
❑ “Local with year”. With formats B006, B007 and IEE1344 the year is not taken into account. It cannot be used with formats
B002 and B003 because they set the year to zero value.
7.4 SNTP
The available implementation of the SNTP (Simple Network Time Protocol) is based on the points described in RFC5905. To improve the
accuracy of the synchronization and to take into account the possible delays introduced by the network, the "On-Wire" protocol, which
is described within the RFC itself, is used.
This correction algorithm uses four timestamps numbered from T1 to T4, with the timestamp of sending or receiving each message, to
calculate the offset that is required to apply to the time of the equipment after sending each synchronization request.

User Manual 75
SYNCHRONIZATION 
The following image shows in a general way the synchronization scheme:
The time offset obtained using this calculation is the deviation to be applied in the SNTP client clock to obtain the time of the SNTP
server that synchronizes it. It is a valid method for both LAN networks as well as for WAN networks that have higher response times.
The SNTP settings are included in the LTMS logical node.
Note: There is an optional configuration mode with the SNTP-IP value in the communications section of the ICD file, which is
maintained for backward compatibility with previous configuration files. The IED only uses that option if no configuration is included in
the LTMS node. Nevertheless, the recommended configuration option is through the LTMS node settings.
7.4.1 Settings
The SNTP settings are in the GEN/LTMS logical node:
❑ Main Time Source: IP address of the main NTP server. Broadcast addresses are not allowed. Value 0.0.0.0 disables the
main source.
❑ Secondary Time Source: IP address of the secondary NTP server. Broadcast addresses are not allowed. Value 0.0.0.0
disables the secondary source.
❑ Not Synchro time SNTP (min): Elapsed time in which it has not been received any correct SNTP response (the checked
fields are detailed below) from any of the sources configured for SNTP synchronization to consider the SNTP as not
synchronized. Range value is 1 to 1440 min.
❑ SNTP Polling Time (seg): Time interval between synchronization requests to the NTP servers. Range value is 10 to 3600
seconds. If the configured time is less than the real polling communication process (requests and retries in case of failure)
the synchronization active request will finish normally and a new polling timer will be started.
❑ SNTP Time delay Unicast message (seg): Waiting time for the response to an unicast synchronization request. If no
response is received in that time interval a unicast request retry cycle will be started. Range value is 1 to 60 seg.
❑ Retry number: Number of unicast request retries in case there is no response from the NTP server to a request. If the
configured number of retries finishes without response with the main source the device tries to synchronize with the
secondary source. If the configured number of retries finishes without response with the secondary source that
synchronization process is finished and the device waits the polling period to send a new request. Range value is 0 to 9.
❑ PTP interface: This setting specifies the interface in which the IED will listen to IEEE 1588v2 messages.
❑ PTP delay mechanism: This settings specifies which delay Mechanism to use: peer to peer (P2P) or end to end (E2E) delay
mechanism.
(*) Available from firmware version 6.3.20.0, the necessary settings to enable and configure symmetric key authentication in SNTP
requests:
❑ SNTP authentication: This setting enables the authentication in SNTP messages based on the keys file configured.
❑ SNTP key: The number of the key used for the authentication. It shall match with the value configured in the SNTP server
used as synchronization source.

User Manual 76
SYNCHRONIZATION 
Table 28 SNTP settings LTMS node

TmSrcSet1 Main Time Source IP address VisString255
TmSrcSet2 Secondary Time Source IP address VisString255
ValTm Not Synchro timeout SNTP (min) 1 1440 1 Int32
PollTms SNTP Polling Time (seg) 10 3600 1 Int32
EspTms SNTP Time delay Unicast message (seg) 1 60 1 Int32
NRetry Retry number 0 9 1 Int32
PTPIface PTP Interface 1 2 1 Eth1/Eth2 enum
PTPDelM PTP delay mechanism 0 1 1 P2P / E2P enum
SNTPAuth SNTP authentication (*) NO / YES Boolean
TrustedKey SNTP key (*) 1 65535 1 Int32
The keys file is configurable from the website6, and it shall be shared between the IED and the SNTP server. The following key types are
supported by the IED:
❑ MD5
❑ SHA
❑ SHA1
❑ RIPEMD160
To provide additional information, a digital signal and a counter have been added with data about the status of the SNTP
authentication:
❑ AuthCfgErr: Configuration error boolean signal. Indicates that there is some type of error in the configuration of the keys
file or in the selected settings. In this case, the IED sends SNTP requests without authentication so it can be synchronized.
❑ AuthRspErr: Counter with the number of not authenticated responses or with authentication failure. When this occurs, the
response obtained is discarded and the device is not synchronized. This counter is increased in case of:
 The SNTP server rejected the request (because the key was not configured or the expected signed value did
not match).
 The received authentication is not considered valid (the calculated signed value does not match the expected
one).
The following diagram details the synchronization process:
6
Available from firmware version 6.5.22.0

User Manual 77
SYNCHRONIZATION 
The following values are checked in the synchronization responses to consider them valid and apply the time to the internal clock:
❑ Message length.
❑ Flags mode: Server.
❑ Flags version number: NTP version 4.
❑ Flags leap indicator: Different from 3.
From the following firmware versions of Ingepac EF these checks are also available:
 Ingepac EF version 6.1.18.5:

❑ Flags version number: NTP version 3 or 4.
❑ Valid stratum value: Between 1 and 15.
❑
 Ingepac EF version 6.3.20.0:
❑ The origin timestamp received in the response packet must match with the transmitted timestamp on the request.

User Manual 78
SYNCHRONIZATION 
7.5 QUALITY FLAGS IEC 61850
In the IEC 61850 data there are quality flags which detail the validity of the time in a timestamp sent by communications. These are the
used quality flags:
❑ Clock Not Synchronized: Active jointly with the synchronization failure alarm.
❑ Leap Second: It is activated if the synchronization source provides this data. Active for SNTP, IRIG-B and 1588.
❑ Clock Failure: Active jointly with the failure of the internal RTC clock.

User Manual 79
DATA ACQUISITION FUNCTIONS 
8. DATA ACQUISITION FUNCTIONS

The information generated by the unit is stored in xml format files, except the format the oscillograph, which is stored in comtrade format.
8.1 STATUS REPORT
The status report indicates the current status of the protection, showing instantaneous values. This report is updated approximately
every 1 second.
The information available in the status message is:
❑ Version. Indicates the unit version:

 CPU: Shows the CPU’s main firmware version
 CPU2: Shows the firmware version of the FPGA and interface with I/O modules
 OTHER: Shows the analogue card's firmware and I/O modules
 Only in models with sampled values reception modules:
 SV: Shows the module main firmware version
 SV-FPGA: Shows the firmware version of the FPGA.
❑ General. Displays the unit’s general data:
 Relay date and time. Within the <Date> tag, the date (Date) and time (Time) are shown
❑ Measurements: Within the Measurements tag, the unit’s measurements are shown. The measurements correspond to
the fundamental frequency.
 <Analog>: Type, module and angle of each of the unit’s 12 transformers.
 <Sequence>: Direct, inverse and zero sequences of currents and voltages (module and angle).
 <Power>: Total real, reactive and apparent power.
 <Frequency>. Frequency value.
 <Battery> External power supply battery voltage.
 <InternalBattery> Internal battery voltage for maintenance of Data.
 <Maximeter>. Indicates the maximeter value for each current and voltage phase. It has a “Reset” button.
 <Temperature> Indicates the unit’s temperature.
❑ Input and output status. The status of the digital inputs and outputs is indicated in each of the cards available in the unit.
Each card is distinguished by its address, indicated in GGIO1 to GGIO8.
 Digital inputs. Ind1.stVal to Ind32.stVal indicate “Y” if enabled and “N” if not. There are as many values as there are
inputs in the card.
 Digital outputs. SPCSO1.stVal to SPCSO16.stVal indicate “Y” if enabled and “N” if not. There are as many values as
there are outputs in the card.
❑ General status. Indicated in LLN0 with the “GEN” data, in which the following is indicated:
 Unit hw status. Indicating if there is failure "Y" or "N".
 Local/remote mode. Indicating if it is local, "Y" or "N".
 Events pending dispatch. Indicating if there is an event pending dispatch, "Y" or "N".
 Failure in IRIG synchronization. Indicating if there is failure, "Y" or "N".
 V2 and Vn voltage monitoring. Indicating if there is failure, "Y" or "N".
 Check on internal communication between cards. Indicating if there is failure, "Y" or "N".
❑ Monitoring units.
 CCTS1. CT monitoring. There is function enabled data (StEna.stVal) and CT monitoring activation data (CTSpv.general)

User Manual 80
 CTSU1. Temperature monitoring. There is a function enabling data (StEna.stVal) and an indication of the temperature
above (OverTemp) and below (UnderTemp) the threshold.
 CESS1. External power supply monitoring. Indication of external power supply above (OverVcc) or below (UnderVcc)
the threshold. Also indicates whether the function is enabled or not (StEna.stVal).
 CSUS1. Indicates battery failure status (DFFA), if it is activated “Y" or deactivated “N”.
The status data are displayed on the PacFactory console and in the unit's display:
❑ PacFactory. All the status message information is displayed, grouped in tabs according to the information:
 General. The date, active table, versions and measurements are displayed.
 I/O. The digital inputs and outputs are displayed.
 Check. The results of the various checks that are carried out in the unit are displayed.
❑ Display. Grouped into several screens and displaying:
 General: Date and active table
 Transformer measurements and configuration
 Current and voltage maximeters
 I/O. The digital inputs and outputs are displayed.
Figure 45 PacFactory status screen
8.2 PRIMARY MEASUREMENTS REPORT
This report indicates the measurement transformers’ primary measurements, applying the transformer ratio. The maximeter
information is used for the maximeter reports.
The information available in the measurements message is:
❑ Distance. In the <Distance> tag, indicating the distance of the last fault.
❑ Currents. Within the <Currents> tag, showing the rms current measurements in primary:

User Manual 81
 Earth-phase.
 The module and angle of each phase, neutral and sensitive neutral.
 The average current module of the three phases.
 THD of each phase, neutral and sensitive neutral.
 Sequences <Sequence>. Current sequences module (I0, I1, I2)
❑ Voltages Within the <Voltage> tag, showing the rms voltage measurements in primary:
 Earth-phase.
 The module and angle of each phase and neutral.
 The average voltage module of the three phases.
 THD of each phase and neutral.
 Phase-phase <Phase>.
 Phase pair module (AB, BC and CA) and average.
❑ Sequences. Voltage sequences module (V0, V1, V2)
❑ Frequency. Frequency value.
❑ Powers. Within the <Power> tag, showing the rms measurements for each phase and total:
❑ Real power. Per phase and total.
❑ Reactive power. Per phase and total.
❑ Apparent power. Per phase and total.
❑ Power factor <Power Factor>. Per phase and average.
❑ Energy counters <Energy>. There is a reset button for the energy counters.
 Last reset command date
 Positive and negative real energy counter value
 Positive and negative reactive energy counter value
❑ Maximeters. Shows the maximum value and the date on which it was produced. There is a reset button for the
maximeter.
 Current. For each phase.
 Voltage. For each phase.
 Real power. For phase and total.
 Reactive power. For phase and total.
 Apparent power. For phase and total.

User Manual 82
Figure 46 PacFactory measurements screen
8.3 INCIDENT REPORT
In CD2 models.
The unit stores in a queue of 1000 non-simultaneous protection events in a non-volatile memory. Each protection event is recorded
with its date and time, as well as the current and voltage measurements of all the transformers and the frequency.
The protection events can be masked individually, so that only protection events configured by the user are generated. These enablings
are available in the GEN/RSUC node.
The information available in each record is:
❑ Date: With a resolution of one millisecond.

❑ Information. Within the <Inf> tag the protection event signal number and its status 0 (Deactivation) / 1 (Activation) are
indicated. Each protection event record can have up to 16 simultaneous signals.
❑ Measurements. The trafo measurements at the time of the protection event (module and angle) and frequency
measurement are shown for each of the unit’s transformers.
Figure 47 Example of protection event record
<Reg Fecha="15-06-10 21:50:38:792">

<Inf Sen="8426" Status="1"/>
<Inf Sen="8433" Status="0"/>
<Med>
<T1 Mod="0.00" Arg="0.00"/>
<T2 Mod="0.00" Arg="0.00"/>
<T3 Mod="0.00" Arg="0.00"/>
<T4 Mod="0.00" Arg="0.00"/>
<T5 Mod="0.00" Arg="0.00"/>
<T6 Mod="0.00" Arg="38.10"/>
<T7 Mod="31.68" Arg="58.53"/>
<T8 Mod="99.94" Arg="-62.01"/>
<T9 Mod="99.95" Arg="178.00"/>
<T10 Mod="31.67" Arg="58.54"/>
<T11 Mod="99.98" Arg="-62.02"/>
<T12 Mod="99.94" Arg="178.00"/>
<FRE Hz="50.00"/>
</Med>
</Reg>

User Manual 83
Figure 48 PacFactory protection event screen
8.4 HISTORICAL MEASUREMENT REPORT
The unit saves a queue of historical measurement reports in the non-volatile memory. Depending on the registered measurements,
4000 or 1000 registers are available.
Each record includes the maximum, minimum and average currents of each measurement, calculated within a programmable time
window, detected during a programmable recording period. The measurements are secondary.
The historical measurement report is grouped into records in which the first corresponds to the oldest and the last to most recent, so
that when the file is opened, the first item we see is the oldest.
The format of this file for each record is:
❑ Record number
❑ Date: With second precision: Day and Time
❑ Measurements: Maximum/minimum/average magnitude values:
The settings employed by this unit are in the PROT/MHRE node:
❑ Sample time window. Indicates the time in minutes during which the average is calculated
❑ Record interval. Indicates the time in minutes in which each record is created
❑ Start time. Indicates the time after which the historical measurement record is started
❑ End time. Indicating the time up to which the historical measurements record is carried out
❑ Calendar mask. Indicates whether the historical measurements record is created every day (YES) or if it is only created on
the days indicated in the day selection mask.
❑ Day selection. It indicated, for each day of the week, whether the record was created.
❑ Register mode7. Selects between standard or extended:
7
Available from firmware version 5.19.15.7 and ICD version 6.3.0.0. Previous versions is fixed “Standard”.

User Manual 84
 Standard. It saves 4000 registers, with máximum, mínimum and average of the mean currents and voltages, real,
reactive and apparent power, frequency and external power supply.
 Extended. Extended number of measures. It saves 1000 registers, with máximum, mínimum and average of the phase
and neutral currents, phase voltages, current and voltage sequences, real, reactive and apparent power, power factor
and the result of 10 measurements data logics AutGGIO.AnIn.
The units of the measurements are:
❑ Current. The units are secondary amps.

❑ Voltage. The units are secondary volts.
❑ Real power. The units are secondary watts.
❑ Reactive power. The units are secondary VAR.
❑ Apparent power. The units are secondary VA.
❑ Frequency. Units are Hz.
❑ External power supply. The units are volts.
Table 29 Historical measurement settings
Data Setting Min. Max Step Remarks Type

SmTmm Sample time window 1 15 1 minutes uint32
RegIntTmm Record interval 1 1440 minutes uint32
StH Start time 0 23 1 uint32
EndH End time 0 23 1 uint32
DayEna Calendar mask YES/NO Boolean
SunEna Selection Sunday YES/NO Boolean
MonEna Selection Monday YES/NO Boolean
TueEna Selection Tuesday YES/NO Boolean
WedEna Selection Wednesday YES/NO Boolean
ThuEna Selection Thursday YES/NO Boolean
FriEna Selection Friday YES/NO Boolean
SatEna Selection Saturday YES/NO Boolean
RegType Register mode Standard / Extended Boolean
Figure 49 Example of records
<REG Num="0" Day="18/04/10" Time="00:00:37">
<I_A Max="0.000" Min="0.000" Media="0.000"/>
<V_V Max="0.000" Min="0.000" Media="0.000"/>
<P_W Max="0.00" Min="0.00" Media="0.00"/>
<Q_VAR Max="0.00" Min="0.00" Media="0.00"/>
<S_VA Max="0.00" Min="0.00" Media="0.00"/>
<f_Hz Max="0.000" Min="0.000" Media="0.000"/>
<Batery_V Max="120.51" Min="120.51" Media="120.51"/>
</REG>
8.5 MAXIMETER/MINIMETER REPORT
Displays the maximum and minimum values integrated in the time. It has buttons to individually reset the maximeters and/or
minimeters.
The Data displayed are:

User Manual 85
❑ Each phase’s current

❑ Each phase’s voltage
❑ Real power per phase and total
❑ Reactive power per phase and total
❑ Apparent power per phase and total
❑ Frequency
❑ External battery measurement
Figure 50 PacFactory maximeter/minimeter screen
8.6 OSCILLOGRAPHY
The oscillography is stored in binary comtrade format. There is a CFG config file and a DAT data file for each.
For additional information see on “IEEE Standard Common Format for Transient Data Exchange (COMTRADE) for Power Systems”.
It allows 16 analogue signals:
❑ 12 analogue inputs from the transformers (current and voltages)

❑ 4 frequency measurements8 (V phase B, V synchronism, frequency 2Va-Vb-Vc, V synchronism 28)
❑ External battery used as the power supply of the equipment
It allows up to 100 digital signals, selected among all the signal of the equipment.
The trigger signals are selected among the registered signals, when the set “Trigger Signal” is set to “YES”. If it is set to “NO”, that signal
is registered but does not start the oscillography.
The length is set in cycles (Total Duration), from 20 up to 420 cycles (8,4 seconds for 50Hz and 7 seconds for 60Hz).
8
Available since firmware version 6.0.18.2 and ICD 8.2.0.0. Up to that version there are 100 digital signals and 3 frequencies

User Manual 86
Pre-fault duration (cycles) indicates the pre-fault cycles that are stored in each disturbance recorder prior to the trigger, being able to
vary between 1 and 415 cycles.
The number of samples can be selected among the options of the following table. Depending on the device and ICD used, the number
of the samples per cycle is different to adapt to the different devices. The relationship between them is shown in the following table
Table 30 Options of samples per cycle
Equivalent Conventional Sampled values Sampled values

Setting9
setting Devices 80/cycle 96/cycle
Full 144 144 80 96
1 de 2 72 72 40 48
1 de 3 48 48 40 32
1 de 4 36 36 20 24
1 de 6 24 24 20 16
1 de 9 16 16 20 16
The continuous mode allows to increase the length if at the end of the register, there is a trigger signal activated. In that case, the
register continues the number of cycles set in the “Total Duration”, checking again the trigger signals at the end of the new register.
The total register is limited to 5Mb or 3 times the setting “Total Duration” (the most restrictive of both).
To increase the length, the trigger signal has to change the status, that is, it has to pass from deactivated to activated. If one trigger
signal is continuously activated, it does not start, nor extend the oscillography register.
The digital signals set to “NO” are displayed, but do not start, nor extend the oscillography register.
The oscillography allows to display signals that do not start the register. For example, the protection trip signal can inicialize an
oscillography register, where the start signals are displayed. Table 31 shows an example of an oscillography configuration, with 11
digital signals registered but only three signals start the register (GGIO1Digital input 1, GGIO1Digital input 4 and GGIO2Digital input 1).
At the end of the register, if one of these three signal, continues activated, the oscillography is extended the cycles set in “Total
Duration”; otherwise the oscillography is finished.
10Mb of non volatile memory is available to store oscillography registers. The total number of registers depends on the settings. Table
32 shows some examples of the capacity (with the continuous mode set to “NO”), where the most influential settings are the length
and the number of samples.
Table 31 Oscillography configuration example
Ajustes Valor
Recorded signal 01 GGIO1Digital input 1
Trigger Signal 01 YES
Trigger Signal 02 NO
Señal registrada oscilo 05 GGIO1Digital output 1
Recorded signal 06 GGIO1Digital output 2
9
Available since ICD version 8.1.0.18

User Manual 87
Table 32 Oscillography capacity
Total Duration
Number of samples/cycle Number of digital signals Number of oscillography
(cycles)
420 144 100 3
420 144 32 3
420 36 100 13
420 36 32 15
50 144 100 27
50 144 32 32
50 36 100 98
50 36 32 121
20 144 100 34
20 144 32 78
20 36 100 206
20 36 32 271
20 16 100 350
20 16 32 499
The settings employed by this unit are in the GEN/RDRE node:
❑ Total Duration (cycles). Indicates the total duration of disturbance recorder (in cycles).
❑ Pre-fault duration (cycles). Indicates the pre-fault cycles that are stored in each disturbance recorder
❑ Number of samples/cycle. Indicates the samples per cycle stored in the disturbance recorder.
❑ Recorded signal X. Indicates the signal that is stored in record position X. If programmed as -1, no signals are recorded.
❑ Trigger X signal. If the signal is configured, it indicates whether it provokes a disturbance recorder pick up (1) or not (0). If
set to “No”, it is only displayed.
The trigger and recorded signals are repeated up to 100 possible signals.
Table 33 Oscillography settings
Data Setting Min. Max Step Remarks Type

OscCyc Total Duration (cycles) 20 420 1 cycles Int32
PreCyc Prefault duration (cycles) 1 415 1 cycles Int32
NuSaCy Number of samples/cycle enum
OscReg1 Recorded signal 1 Int32
OscTrg1 Trigger 1 signal 0 1 1 YES/NO Boolean
OscReg2 Recorded signal 2 Int32
OscTrg2 Trigger 2 signal 0 1 1 YES/NO Boolean
Recorded signal and trigger up to 100 0 1 1 YES/NO Boolean
The disturbance record configuration file (CFG) contains the general disturbance recorder information (Figure 51):
❑ Total number of analogue and digital channels available in the disturbance recorder
❑ Analogue channel data: bay, identification, measurements scaled and limits
❑ Digital input data: bay and identification
❑ Sample data: signal frequency, sampling frequency, number of the last sample
❑ Disturbance recorder start and end dates.
❑ Data file format
The disturbance recorder data file (DAT) includes the information captured in the disturbance recorder, with the following available for
each sample:
❑ Sample number
❑ Sample time
❑ Analogue samples values
❑ Digital signals values

User Manual 88
Figure 51 Configuration file
The name of the file uses the standard IEEE C37.232-2007, using the fields:
Start Date, Start Time, Time Code, Station Identifier, Device Identifier, Company Name
For example, “20100626, 46702262,+2h30t,Substation,Rele1,Ingeteam”, which means:
❑ Start Date: Trip date with a 4-character format for the year, the month and the day. For example, 26/june/2010 would be
20100626.
❑ Start Time: Indicates the milliseconds since 00:00 of the day, that is, milliseconds since midnight.
❑ Time Code: Indicates the time zone amplitude sign, and can indicate minutes if necessary. For example, “t +2” indicates
time zone 2, while “+2 h30t” indicates that the time zone is 2 hours 30 minutes.
❑ Station Identifier. Indicates the substation name. The installation’s short name (InsShNam) from the “PROT/LPHD1” node
is used".
❑ Device Identifier. Indicates the unit’s name. The relay’s short name (RelShNam) from the “PROT/LPHD1” node is used".
❑ Company Name. Indicates the name of unit’s manufacturer, in this case, Ingeteam.
8.7 DISPLAY
In the display available on the equipment, it's possible to see measurements, in different screens. Measurements not available are
shown with "--".
❑ Screenshot 1. Shows rms voltages and currents inputs measurements.

❑ Screenshot 2. Sequences. Sequences values from voltage and current and frequency.
❑ Screenshot 3. Power and power factor.
❑ Screenshot 4. Total power, mean power factor and energy counter.
❑ Screenshot 5. Harmonic distortion.

User Manual 89
Nombre A B D E F G
Ia: A phase current      
Ib: B phase current      
Ic: C phase current      
In: Neutral current   
I average: Mean current      
Va: A phase voltage   
Vb: B phase voltage   
Vc: C phase voltage   
Vn: Neutral voltage 
Vmedia: Mean voltage   
Vab: AB phase voltage      
Vbc: BC phase voltage      
Vca: CA phase voltage      
Vc average: mean ph-ph voltage      
Nombre A B D E F G
I0: Zero sequence current      
I1: Possitive sequence current      
I2: Negative sequence current      
V0: Zero sequence current   
V1: Possitive sequence voltage      
V2: Negative sequence voltage      
F: Frequency      

User Manual 90
Nombre A B D E F G
Pa: Potencia activa fase A   
Pb: Potencia activa fase B   
Pc: Potencia activa fase C   
Qa: Potencia reactiva fase A   
Qb: Potencia reactiva fase B   
Qc: Potencia reactiva fase C   
Sa: Potencia aparente fase A   
Sb: Potencia aparente fase B   
Sc: Potencia aparente fase C   
Cosa: Factor Potencia fase A   
Cosb: Factor Potencia fase B   
Cosc: Factor Potencia fase C   
Nombre A B D E F G
P: total active power      
Q: total reactive power      
S: total apparent power      
Cos: mean power factor      
E. Activa+: positive active energy      
E. Activa-: negative active energy      
E. Reactiva+: positive reactive energy      
E. Reactiva-: negative reactive energy      

User Manual 91
Nombre A B D E F G
Ia: A phase current      
Ib: B phase current      
Ic: C phase current      
I average: Mean current      
Va: A phase voltage   
Vb: B phase voltage   
Vc: C phase voltage   
V average: Mean voltage   
B, D and F Connection bus shows total distortion.
Nombre A B D E F G
Vab: AB phase voltage   
Vbc: BC phase voltage   
Vca: CA phase voltage   
Vc average: Ph-Ph mean voltage   

User Manual 92
USB ACCESS 
9. USB ACCESS
The unit can be accessed via the front USB to retrieve reports and CID from the device and to load a new CID or a firmware update.
The USB port can be configured from the local HMI (Menu: Password -> USB Configuration).
The configuration options are:
❑ Without password: No password is needed.

❑ With password: The local HMI password must be entered before any USB operation.
❑ Disabled: The USB port is disabled.
9.1 DOWNLOADING REPORTS
When a pendrive is inserted, the following appears in the front above the current screen, indicating that the device has been detected:
USB Detected
The unit’s reports are automatically dumped onto the pendrive.
While the data is being downloaded, the following appears in the front above the current screen:
USB Detected
Downloading data
Just in case there is a CID, an ICD or and IID in the pendrive, the user will be asked for a confirmation to load this file into the unit.
WANT TO START
THE CID UPDATE
CANCEL
ACCEPT
PRESS ENTER: RUN OPTION
If accepted, the following appears on the screen:
USB Detected
Downloading data
If canceled, downloading is assumed to be complete, and the following appears on the screen for 5 seconds:
REMOVE THE
USB DEVICE
As of this moment, the pendrive can be removed.
Only the reports existent in the unit at the time of the download will appear in the pendrive, with the data structure:
User Manual 93
USB ACCESS 
❑ Root with the short installation and relay name (PROT/LPHD node), and the iedName, separated by “_”·, i.e.,
“Instalacion_Rele_iedName”
❑ COMTRADE. This directory contains the disturbance recorders generated in the unit
❑ FAULT RECORDS. This directory contains the fault records generated in the unit.
❑ The rest of the unit’s reports are dependent on the root:
 Maximetro.xml
 Sucesos.xml
 Informe_Estadisticos.xml
 Registro.xml
 CID
For detailed information about these reports, see Chapter 10, “DATA ACQUISITION FUNCTIONS
”.
Figure 52 USB Tree
9.2 LOADING CID
When a pendrive is inserted into the front USB port, a check is run to see if an ICD exists. If there is an ICD, it is copied into the directory
“public/SCL/notvalidated” in order that it may be operative in the unit.
During the search for the ICD, the existence of a file with an ICD, icd, CID, cid, IID or iid extension is checked. There is not a established
filename as only the extension is checked.
If there is more than one file with one of the indicated extensions, the ICD is considered invalid and not ICD is captured.
9.3 LOADING FIREWALL CONFIGURATION
When a pendrive is inserted into the front USB port, a check is run to see if a firewall configuration file exists. In that case, it is copied
into the directory “public/SCL/notvalidated” in order that it may be operative in the unit.
During the search, the existence of a file with “fwc” extension is checked. There is not a established filename as only the extension is
checked.
If there is more than one file with one of the indicated extensions, the file is considered invalid and not captured.
9.4 FIRMWARE UPDATE
For firmware update via USB, a USB flash drive must be inserted in the front USB port, with a "FW" directory with a valid firmware file.

User Manual 94
USB ACCESS 
In the local display, the user will be prompted for a confirmation to start the update. It is very important that during the process of
updating firmware the device is not turned off since in that case the device could become unusable.
After the update the device will restart automatically and the result of the update can be consulted either in the device versions screen
or in the latest updates screen (consult display section).
9.5 USB ENABLING
To increase the security of the device, the USB port can be disabled, preventing access to the device via USB. With the USB disabled,
ICD and firmware loading and data download of the equipment are not allowed.
USB enable / disable can only be performed from the display (consult display section). It is done from the Password screen. The setting
will have 3 possible values:
❑ Disabled: USB is not available.

❑ With Password: USB processing is available but you need to enter the password of the settings menu.
❑ Without Password: USB processing is available without the need to enter a password.

User Manual 95
FTP ACCESS 
10. FTP ACCESS

The public user for FTP access is as follows:
❑ User: ftpuser
❑ Password: ftpuser
Available from firmware version 5.25.16.1, the device implements a sFTP access for secure connections as follows:
❑ User: sftpuser
❑ Password: sftpuser
The passwords can be modified from the local display or from the software tool pacFactory.
The key modification meets the criteria defined by the IEEE1686 standard (available from firmware version 6.3.20.0):
 Minimum length of 8 characters.

 At least one character of each type: uppercase, lowercase, numeric and special (not alphanumeric).
In addition to some own criteria to provide additional security:
 It is not allowed to reuse the previous key: including modifying only uppercase / lowercase. It is required a minimum of 4
characters modified with respect to the previous string.
 Palindromes are not accepted.
These user profiles allows direct access to the following directorys and files:
Config directory:
❑ config/SYSTEM_LOG: Text files with system information.

❑ CIDupdates.log: Log of events of the CID files received.
❑ swupdates.log: Log of events of the firmware upddates.
❑ System.log: Los of system information events.
❑ Versions.log: Versions of the device.
❑ ftp.log: Log of events of the FTP access (available from firmware version 5.25.16.1)
❑ config/VALIDATION_TRACES: Text files with the received CIDs validation information.

❑ log_lib850.log: Log of events related with the IEC 61850 parser.
❑ validation_traces.log: Los of events of general parser.
LD directory:
❑ LD/PROT/COMTRADE: Oscilografy files in Comtrade format.

❑ LD/PROT/FAULT_RECORDS: Fault report files.
❑ LD/PROT/FAULT_SETTINGS: Settings files associated with fault reports.
SCL directory:
❑ SCL/NotValidated: Directory to copy the new CID file to configure the device.
❑ SCL/Validated: Directory with the active CID configuracion file (read only).
The user for ftp firmware update is as follows:
❑ User: ftpUpdat

User Manual 96
FTP ACCESS 
❑ Password: ftpUpdat
With this user you can access the directory "downloads" where a valid firmware file should be copied. Once the file is copied the update
will start automatically.
It is very important that during the process of updating firmware the device is not turned off since in that case the device could become
unusable.
After the update the device will restart automatically and the result of the update can be consulted either in the device versions screen or
in the latest updates screen (consult display section).
10.1 ACCESS CONTROL
Available from firmware version 5.25.16.1: The device incorporates a management of failed accesses which after 5 consecutive
attempts to establish a connection using a wrong password, the access to that user is blocked for 10 minutes. From this moment, any
failed attempt blocks the user 10 more minutes. While a user is blocked the correct password is also not accepted to access.
The goal is to harden the system to avoid "brute-force attacks" to recover a key by trying all possible combinations until finding the one
that gains access.
There is a signal on GEN/LLN0 indicating the activation of this block for some user.
 AccAlm: Access alarm. Active when access control is blocking a user.
In addition, all FTP accesses are registered in a log file located in /config/SYSTEM_LOG folder called ftp.log.
In this file, the accesses of any FTP client are recorded, indicating the source IP address and the date and time. Any uploads or
downloads of files are also recorded.

User Manual 97
MAPPING THE UNIT’S SIGNALS, MEASUREMENTS AND METERS
11. MAPPING THE UNIT’S SIGNALS, MEASUREMENTS AND METERS

The binding of the IED internal data to the IEC 61850 data model is configured in the short address (sAddress) attribute.
The sAddr attribute allows the allocation of a short address to DO attributes. According to the IEC 61850 standard short addresses can be
used as IED internal identification for the attribute. In this scope the format of the content is private to the IED and any tool that process
the ICD/CID file shall preserve imported contents in exported SCL files.
All the signals (trips, logics, hw check, digital inputs-outputs, etc.), measurements and meters that are generated in the unit are identified
by a number that appears in the sAddress of each of these elements.
In the factory ICD configuration file, all the internal data is preconfigured, and the user cannot modified them apart from the description
texts.
For new data created at engineering phase, as control logics output data, the software configuration tool allows the creation of sAddress
values.
11.1 SIGNALS
The distribution of the unit’s signals is effected using four numbers as a base: 0, 8192, 16384, 24576. All the unit’s signals are divided
into four types, taking these four digits as references:
11.1.1 Type A signals

This type of signal refers to all those signals with sAddress identification numbers between digits 0 and 8191.
These signals include digital inputs and Goose signals.
❑ Digital Inputs
 Identification number between 0 and 287.
Example: sAddr="S,0,5,0;TX1:GGIO1.Digital input 6,TX2:GGIO1.Digital Input 6,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of digital input number six from the first card in the ICD
sAddress.
 GEN/GGIO node
❑ Goose Signals
 In turn, the Goose signals are divided into RIO modules and LGOS nodes.
 RIO modules
Example: sAddr="GS,0,288,0;TX1:RIO1.St,TX2:RIO1.St,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of the first signal from the first RIO module in the ICD
sAddress.
 GEN/RIO node
❑ LGOS nodes
Example: sAddr="GS,0,608,0;TX1:LGOS1.St,TX2:LGOS1.St,AC:1.2,ED:1.1,AD:0.1"
In the example, we can see the identification number of the first signal from the first LGOS node in the ICD
sAddress.
 GEN/LGOS node
Therefore, the distribution of these signals based on their identification number is as follows:

User Manual 98
Table 34 Type A signal mapping
DIGITAL
INPUTS
(0 - 287)
GOOSE
SIGNALS
(288 - 1695)
The number of this type of signal reserved in the unit is 1696.
11.1.2 Type B signals

This type of signal includes type B protection signals, fast protection logic signals and fast control logic signals.
❑ Type B protection signals

Example: sAddr="S,0,9091,0;TX1:TOC1 Phase trip,TX2:TOC1 Phase Trip,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of a type B protection signal in the ICD sAddress.
 Additional type B protection signals: Identification number between 9472 and 10399
 PROT node
❑ Fast protection logics
Example: sAddr="PS,0,9216,0;TX1:Protection logic 1,TX2:Protection logic 1,AC:1.2,ED:1.1,AD:0.0"
 In the example, we can see the identification number of the first protection logic in the ICD sAddress.
 GEN/pGGIO node
❑ Fast control logics
Example: sAddr="LS,0,9344,0;TX1:Fst logic 1,TX2:Fast logic 1,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of the first fast control logic in the ICD sAddress.
 CTRL/AutGGIO2 node

User Manual 99
Table 35.Type B signal mapping
PROTECTION SIGNALS
TYPE B
(8192 - 9215)
FAST PROTECTION LOGIC

SIGNALS
(9216 - 9343)
FAST CONTROL LOGIC

SIGNALS
(9344 - 9471)
ADDITIONAL
PROTECTION SIGNALS
TYPE B
(9472 -10399)
11.1.3 Type C signals

These signals include the type C protection signals.
❑ Type C protection signals

Example: sAddr="S,0,16384,0;TX1:Recloser in service,TX2:,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of the first type C protection signal in the ICD sAddress.
 PROT node

User Manual 100
Table 36.Type C signal mapping
TYPE C PROTECTION
SIGNALS
(16384 - 16831)
11.1.4 Type D signals

This type of signal refers to all those signals with sAddress identification numbers between digits 24576 and higher.
This type of signal includes the type D protection signals, the communication failure signals for all the bays that are connected to
the unit, the slow logic control signals, signals resulting from orders and Loc and LocSta signals (for more information about these
signals go to 1.2.1 Command blocks by command hierarchies, in IEC 61850 commands)
❑ Type D protection signals

Example: sAddr="S,0,24576,0;TX1:Relay in service,TX2:OnLine,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of the first type D protection signal in the ICD sAddress.
 Additional protection signals: Identification number between 27936 and 27967
 PROT node
❑ Communication failure control signals
❑ Slow control logics
Example: sAddr="LS,0,25120,0;TX1:Slow logic 1,TX2:Slow logic 1,AC:1.2,ED:1.1,AD:0.0"
In the example, we can see the identification number of the first slow control logic in the ICD sAddress.
❑ Signals resulting from orders
 Example: sAddr=" RS,0,26908,4;TX1:CSWI4 opClsOr,TX2:,AC:3.7.8.4,ED:1.1.1.1,AD:0.0.0.0"
❑ Loc signals
 Example: sAddr=" S,0,27424,0;TX1:GEN.LLN0.Loc,TX2:GEN.LLN0.Loc,AC:1.2,ED:0.0,AD:0.0"
❑ LocSta signals
 Example: sAddr="S,0,27680,0;TX1:GEN.RIOGGIO1.LocSta,TX2:GEN.RIOGGIO1.LocSta,AC:1.2,ED:0.0,AD:0.0"

User Manual 101
Table 37 Type D signal mapping
TYPE D PROTECTION SIGNALS

(24576 - 24991)
CONTROL SIGNALS (COM FAILURE)

(24992 - 25119)
SLOW LOGIC CONTROL SIGNALS

(25120 - 26399)
SIGNALS RESULTING FROM

ORDERS
(26400 - 27423)
LOC SIGNALS
(27424 - 27679)
LOCSTA SIGNALS
(27680 – 27935)
ADDITIONAL
PROTECTION SIGNALS
(27936 - 27967)
11.2 MEASUREMENTS
All the unit's measurements are divided into four types:
❑ Protection measurements.
Example: sAddr="M,0,124,1;TX1:I average,TX2: AVERAGE I"
In the example, we can see the identification number of a protection measurement in the ICD sAddress.
 Additional measurements: Identification number between 744 – 948 and 979 - 1266.
 PROT node
❑ Goose Measurements
Example: sAddr="GM,0,300,0"
In the example, we can see the identification number of the first Goose measurement in the ICD sAddress.
 GEN/LGOS node

User Manual 102
❑ Measurements resulting from logics

Example: sAddr="LM,0,556,0;TX1:Logic measurement 1,TX2:Logic analog 1"
In the example, we can see the identification number of the first logic measurement in the ICD sAddress.
❑ Measurements resulting from analogical input boards
Example: sAddr="M,0,688,0;TX1:Measure 1,TX2:Measure 1"
In the example, we can see the identification number of the first measurement in the ICD sAddress.
 GEN/GGIO node
❑ RTD boards measurements
Example: sAddr="M,0,949,0;TX1:Temperatura 1,TX2:Temperature 1"
 GEN/RTD
Therefore, the distribution of these measurements based on their identification number is as follows:
Table 38 Measurement mapping
PROTECTION MEASUREMENTS
(0 - 299)
GOOSE MEASUREMENTS
(300 - 555)
MEASUREMENTS RESULTING FROM CONTROL LOGICS

(556 - 687)
MEASUREMENTS RESULTING FROM ANALOGICAL

INPUT BOARDS
(688 - 743)
ADDITIONAL
(744 - 948)
RTD BOARDS MEASUREMENTS

(949 - 978)
ADDITIONAL
(979 - 1266)
The number of measurements reserved in the unit is 1267.

User Manual 103
11.3 COUNTERS
All the unit's counters are divided into two types:
❑ Protection counters
Example: sAddr="C,0,0;TX1:Active energy out,TX2:Active Energy Out"
In the example, we can see the identification number of the first protection counter in the ICD sAddress.
 Additional protection counters: Identification number between 150 and 192.
 GEN and PROT node
❑ Counters resulting from logics
Example: sAddr="LC,0,32;TX1:Logic counter 1,TX2:Logic counter 1"
In the example, we can see the identification number of the first logic counter in the ICD sAddress.
Therefore, the distribution of these counters based on their identification number is as follows:
Table 39 Counter mapping
PROTECTION COUNTERS
(0 - 31)
COUNTERS RESULTING FROM CONTROL LOGICS

(32 - 149)
ADDITIONAL
PROTECTION COUNTERS
(150 - 192)
The number of counters reserved in the unit is 193.

User Manual 104
LOGICS
12. LOGICS
This document explains the operating mode of the logics generation tool of logic devices.
The EF family’s logics are fragments of executable code generated by the user using a PC tool, both in text and graphic formats. These
logics can be defined in an IED’s data model (using iedFactory) or in a particular instance (using substationFactory or the pacFactory
settings tool).
There are two different types of logics: control logics and protection logics.
In this chapter the device logics are defined and an introduction to the configuration options is presented. For more details about the logics
configuration consult the user manual of the software configuration tool (pacFactory / energyFactorySuite).
12.1 CONTROL LOGICS
The logics can be used to customize the behaviour of an IED. For example, automatism can be added or calculations between different
magnitudes can be carried out.
The logics are run in two different tasks, each with different priorities: one for fast logics and one for slow logics.
The running time for the fast logics is 2 milliseconds. The running time for the slow logics is approximately 10 milliseconds, although
given that this is a lower priority task it may occasionally be affected by other higher priority tasks.
Each configured logic must be included in one of these two tasks, in accordance with the manner in which they are to be run – fast
logics or slow logics.
To edit a control logic from substationFactory, the user must select the corresponding IED and click on the editor icon. To edit the
control logic from pacFactory, click on the "Logics" option in the “Configuration” menu or in the side menu.
The logics are defined in program blocks called POU (program organization unit). Two of the languages defined in the IEC-61131-3
standard are offered for the creation of each POU: one textual (ST) and one graphic (FBD).
There are three types of POU, as defined in the IEC-61131-3 standard: PROGRAM, FUNCTION_BLOCK and FUNCTION. The programs are
the senior hierarchy POUs, with each one corresponding to a task to be run on the device. Each PROGRAM can refer to several
FUNCTION_BLOCK and FUNCTION. In turn, a FUNCTION_BLOCK can refer to one or more FUNCTION.
At the IED level, two PROGRAM corresponding to the two above tasks are automatically defined: one for the fast logics (FastLog) and
the other for the slow logics (SlowLog). These PROGRAM cannot be deleted nor can their names be modified. New PROGRAM cannot
be created at any level, either.
All the new signals, measurements and counters that are created in the data model must be assigned a number that appears in the
sAddress of each of these elements.
The range values are:
❑ Fast control logics signals: Value between 9344 and 9471.

❑ Slow control logics signals: Value between 25120 and 26399.
❑ Measurements: Value between 556 and 687.
❑ Counters: Value between 32 and 149.

User Manual 105
LOGICS
12.2 PROTECTION LOGICS
The various protection functions can be configured by means of settings associated to the unit’s internal signals, vg enablings or blocks.
The protection functions treat these signals as inputs, although they do not modify their value. In order to assign them a value, the
protection logics are used.
The protection logics have two main differences in relation to the control logics:
❑ The result of a protection logic is always a Boolean value, to be assigned in one of the protection function's settings.
❑ The protection logic editor has been simplified to facilitate the programming of this type of logic.
The number of available logics is defined by the unit’s data model.
Each logic signal has a value obtained from an associated logic. These logics are fragments of code created in one of the two possible
languages - ST (text) or FBD (graphic). The corresponding language must be selected when a logic corresponding to a signal is edited for
the first time.
Each protection logic is independent from the rest and need not be included in a POU in order to be run. When a protection logic is
saved in the editor, an attempt is made to compile the information. If no error is found, a call to the logic in question is automatically
generated so that the logic is run when a CID (configured IED description) message is sent to the device or sent from pacFactory.
The protection logics are run every 2 milliseconds, as are the fast control logics.
To edit a protection logic from substationFactory, the user must select the corresponding logic signal and click on the editor icon. This
icon has three statuses to indicate the status of the corresponding logic:
Icon Logic statuses:

No logic has been edited for this signal. The value of the signal will be 0 (false).
Logic edited and ready to be run.
Logic edited, but with errors. Logic will not be run.
The following image shows a detail of the expander with four signals with logic signals of different statuses:
Details of the expander with protection logic signals
To edit a protection logic from pacFactory, click on the "Protection Logics" option in the “Configuration” menu or in the side menu.
A screen with a list of the available protection logic signals, along with the logic’s status icon and an access button for each logic’s
editor, will be shown.

User Manual 106
LOGICS
Details of the protection logics list in pacFactory
12.3 DATABASE SIGNALS
All of the IED’s database signals, measurements, meters and commands can be accessed as readings from the logics (the data model’s
basic data with valid sAddress). There is a set of data within this database that can be modified from the control logics:
Signal type Description

Critical signals Digital signals that can be modified from the fast task (FastLog)
Non-critical signals Digital signals that can be modified from the slow task (SlowLog)
Measurements Floating point data that can be modified from both tasks
Meters Whole numbers that can modified from both tasks
Commands Commands can only be generated from the slow task (SlowLog)
Both the data’s value and its quality can be accessed. If data is modifiable from the logic, the same will apply to the value and the
quality.
The data that can be modified from the logic may be preset in the unit's data model or they can be configured in the engineering
phase.
Only the status of the signal to which the logic in question is associated can be modified from the protection logics.
12.4 OUTPUT DATA UPON POWER-UP
Output data can maintain its value after the device is powered off and on.
In the logics, user can define variables of type RETAIN, which have the property of remaining with the value that they had before the
power off of the device.

User Manual 107
LOGICS
The maximum size allowed for all the logics of each group (protection and control) is 96 bytes. This means that if the variables that we
define with this property are of type BOOL (that is, the type associated to the logical signals) we can define a maximum of 96 RETAIN
variables.
Example of using variables in the logics:
There are global variables belonging to the model that can be used in the logic. For example all the signals like Trips or Starts of
protection functions. In the protection logics, each logic has a variable associated with it that is the output of that logic. That output is
also visible as a signal and can be sent in reports or GOOSES, assign it to a digital output, etc.
Each logic can also have internal variables. Once inside the logic editor, click on the "Show interface editor" option to see and / or add
internal variables to the logic (select the VAR tab).
A new variable can be created in 2 ways:
1.- When a non-recognized text is written in the algorithm, an assistant appears asking if you want to add it as a variable.
2.- Writing directly in the cell (if in tabular mode), as shown in next figure.
An internal variable to the logic can be made permanent selecting the RETAIN option in the Retain column.

User Manual 108
LOGICS
The initial value is optional. If it is assigned, it is the value it takes the first time the logic is executed. In the case of the variables not
marked as Retain each time the device is started, the variable is restarted with that value. In the case of Retain variables, it is only
started when the logic has been created or changed. Of course, it is highly recommended to initialize the variables.
When a "Function Block" is used in a logic, it is also considered a variable. If one of the predefined "Function Block" in the editor's right-
hand tab is dragged into the editing window, such as a SR flip-flop (SetReset), an SR1 variable of type SR is added. By activating the
option "Show interface editor" we can see how it is in the list of variables (next figure). In this case, if we want to store the internal
states of this block, we must also select the corresponding RETAIN option.
In the case of the "Function Blocks" with RETAIN option, the size in bytes used depends on the number of internal variables of that
block. In the case of the SR they are 3 bytes.
The example (previous figure) is a simple logic in graphic language to demonstrate how to make permanent the internal state of a SR
flip-flop.

User Manual 109
IEC 61850 COMMANDS
13. IEC 61850 COMMANDS
13.1 RUNNING IEC 61850 COMMANDS
Commands can be issued for controllable elements (elements whose functional constraint is “CO”) that may
belong to different Data classes (detailed in IEC 61850-7-3). Control class model implemented by the IED are:
❑ Controllable single point (SPC)

❑ Controllable double point (DPC)
❑ Controllable enumerated status (ENC)
The device implements the following services defined by IEC 61850 standard:
❑ Select (Sel) / SelectWithValue (SelVal)

❑ Cancel
❑ Operate (Oper)
❑ CommandTermination (CmdTerm)
The structure required to operate the command has the following fields:
❑ CtlVal. Command value. The type will be different, in accordance with element’s the CDC (Common
Data Class).
❑ Origin. It includes information about the origin of the command, divided into two fields:
 orCat. Origin category. Indicates the type of origin that issues the command (local, substation,
remote command, etc.)
 orIdent. Octect string that allows the identification of the command origin.
❑ CtlNum. It is the sequence number of the command.
❑ T: The timestamp when the command was generated.
❑ Test: It defines whether the control service request is going to be used with test purposes or not.
❑ Check: Delimits the kind of checkup that must be performed to the command before running it.
Because the Ingepac EF device implements edition 2 of the IEC61850 standard but maintains compatibility with the existing
configurations of edition 1, the differences in the data used to track orders are explained below:
In addition to informing of the changes in the status signals of the elements on which the commands are to be run,
the reports also provide information on the changes in the status of the two data associated with the command
process itself: OpOpnOr and OpClsOr.
These data have four possible statuses:
Table 40 OpOpnOr and OpClsOr statuses
Value Explanation enum

STANDBY Command in standby 0
IN PROGRESS Command in process 1
SUCCESSFUL Command run successfully 2
UNSUCCESSFUL Failure in running of command 3
For opening commands in general, OpClsOr remains in STANDBY, the sequence for OpOpnOr would be STANDBY -
IN PROGRESS - SUCCESSFUL / UNSUCCESSFUL – STANDBY. In the case of a closure command, OpOpnOr would
remain in standby and OpClsOr would continue the complete sequence. If the command’s CtlModel indicates that

User Manual 110
the command has normal security, no return information is available from the device and, therefore, the sequence
would be STANDBY - IN PROGRESS – STANDY.
CONFIGURACIONES USING ED2:
In the second edition of IEC61850 standard, three new data elements are defined in order to follow the command
process: opOk, OpRcvd and tOpOk. These new elements have a new functional constraint, “OR”.
OpRcvd is activated upon the reception of a command and deactivated about 10 milliseconds later.
OpOk is activated at the same time as the command pulse (the pulse that will afterwards be transmitted to a digital
output, for example) and tOpOk shows the timestamp when opOk was activated.
OpOk and OpRcvd may be set as RS signals, editing their sAddr in the CID using the configuration tool. In this way,
their values will be refreshed in the internal database and will be available for internal logics.
In addition to these elements, it is also possible to generate a series of indications, through signals from the
database, to provide complementary information on the return of the orders.
In the logical nodes where it is necessary to have this return information of the controls, the normative class has
been extended defining the following data objects with CDC = "ACT", which in turn includes the optional data
"originSrc".
❑ OpOpnPrg / OpClsPrg: Execution of opening and closing controls (order in progress).

❑ OpOpnFail / OpClsFail: Failure of opening and closing controls (command failure).
The configuration for the use of these return signals is done through the configuration tool, through the sAddr field
of the command itself. However, the return signals have an RS type sAddr.
In both configurations, upon completion of an order execution, part 7-2 of the IEC 61850 standard defines the possible
reasons for termination. The following table lists the AddCause values used by the device:

User Manual 111
Table 41 AddCause considered
Value Cause Explanation enum

Unknown Unknown cause Command not successful due to unknown causes 0
Not-Supported Not configured 1
Blocked-by-switching- Not successful since one of the downstream Loc switches like in CSWI has
Blocked by hierarchy 2
hierarchy the value TRUE
Select-failed Selection failure Cancelled due to an unsuccessful selection (select service) 3
Control action is aborted due to invalid switch position (Pos in XCBR or
Invalid-position Invalid position 4
XSWI) or the switch reaches an invalid position.
Position-reached Position reached Switch is already in the intended position (Pos in XCBR or XSWI) 5
Parameter-change-in- Parameter change in
Control action is blocked due to running parameter change 6
execution execution
Control action is blocked, because the LN (CSWI or XCBR/XSWI) is in a
Blocked-by-Mode 8
mode (Mod) which does not allow any switching
Blocked-by- Block signal Control action is blocked due to interlocking of switching devices (in CILO
10
interlocking activated attribute EnaOpn.stVal=“FALSE” or EnaCls.stVal=“FALSE”
Command-already-in- Command in Control service or cancel is rejected, because control action is already
12
execution execution running
Health signal Control action is blocked due to some internal event that prevents a
Blocked-by-health 13
activated successful operation (Health)
Control action is blocked, because another control action in a domain (for
1-of-n-control 1 of n block example, substation) is already running (in any XCBR or XSWI, the 14
DPC.stSeld=“TRUE”).
Abortion-by-cancel Command cancelled Control action is aborted due to cancel service 15
Time-limit-over Time exceeded Control action is terminated due to exceed of some time limit 16
Object not selected Object not selected Control action is rejected, since object is not selected 18
Object-already- Object already Select action is not executed, because the addressed object is already
19
selected selected selected
Abortion-by- Abortion by Control action is aborted due to the loss of connection with the client that
23
communication-loss communication loss issued the control
None Command accepted Control action successfully executed 25
Inconsistent- Inconsistent
The parameters between successive control services are not consistent 26
parameters parameters
Locked-by-other- Locked by other
Another client has already reserved the objet 27
client client
On the other hand, the operating mode of a specific command is defined by the ctlModel configuration parameter
associated with that command, according to the following table:
Table 42 Possible ctlModel
Value Explanation enum

The object is not controllable, only the services that apply to a status object are supported. The
status-only 0
attribute ctlVal does not exist.
direct-with-normal-
Direct control with normal security according to IEC 61850-7-2. 1
security
sbo-with-normal-security SBO control with normal security according to IEC 61850-7-2. 2
direct-with-enhanced-
Direct control with enhanced security according to IEC 61850-7-2. 3
security
sbo-with-enhanced-
SBO control with enhanced security according to IEC 61850-7-2. 4
security
Other configuration parameters that determine the progress of the command are:
❑ PulseConfig. This data structure defines the command’s output pulse type (pulse, duration, pulse
train). The command is not terminated until the last pulse ends.
❑ OperTimeOut. Maximum switching time, after which, failure occurs if the command has not been
successfully executed.
❑ sboTimeout. The time during which the command selection remains activated.
In the following sections, the operation process of a command depending on the ctlModel is described in detail.

User Manual 112
13.1.1 DIRECT_WITH_NORMAL_SECURITY (1)
If the command’s ctlModel is DIRECT_WITH_NORMAL_SECURITY (1), the process to follow will be as shown in
the following figure:
Figure 53 Direct command process with normal security
IEC 61850 Client IEC 61850 Server Process
Operate
Checkup for
operation
Origin, blocks…
Operate
Response
Upon receiving a request to run a command by an Operate Request, the device analyses the validity of the
request, checking the client’s authorization and any possible blocks, and responds positively or negatively by an
Operate Response to the client. If the response is positive, the command is sent to the device.
13.1.2 SBO_WITH_NORMAL_SECURITY (2)
If the command’s ctlModel is SBO_WITH_NORMAL_SECURITY (2), the process is similar, but including a
selection prior to execution:
Figure 54 Command process with select before operate and normal security
Select
Checkup for
selection
Origin,
selection…
Select
Response
Operate Checkup for

operation
Origin, blocks…
Operate
Response

User Manual 113
In this case, after receiving a selection request the selection's permission is checked and, when applicable, a
positive response is sent. At that moment a timer starts. This timer will cancel the selection after the sboTimeOut
timeout ends. If an operate request is received before the conclusion of the timeout, the same process as
described for the direct commands with normal security is followed.
If the selection is not accepted, the response will be negative and the process is concluded.
13.1.3 DIRECT_WITH_ENHANCED_SECURITY (3)

When the command’s ctlModel is DIRECT_WITH_ENHANCED_SECURITY (3), the process starts exactly as the
direct commands with normal security, as shown in the diagram below:
Figure 55 Direct command process with enhanced security
Operate
Checkup for
operation
Origin, blocks…
Operate
Response
Command
Termination
After sending the operate request to the device, the return information of the element on which the command is
executed is expected, so that the device can inform the client throught a Command Termination if the operation
has been successfully executed.
If the device’s return information is received before the conclusion of the operTimeout (the maximum execution
time) and the position requested has been reached, the IED then sends to the client a positive Command
Termination.
If the operTimeout time is exceeded without having received the information from the device, or if it is received but
the position requested has not been reached, the Command Termination will be negative. In this case, the cause
of the failure of the command will be included in the AddCause field.
13.1.4 SBO_WITH_ENHANCED_SECURITY (4)
The ctlModel SBO_WITH_ENHANCED_SECURITY (4) includes, in addition to the enhanced security process of
the commands modelled as DIRECT_WITH_ENHANCED_SECURITY, the SelectWithValue service in order to
select the command before operate. In this way, it is verified that the value sent in the selection process is the
same as the one sent during the execution. The scheme to be followed is:

User Manual 114
Figure 56 Command process with select before operate and enhanced security
IEC 61850 Client 61850 Server Process

Select
Checkup for
selection
Origin,
Select selection…
Response
Operate
Checkup for
operation
Operate Origin, blocks…
Response
Command
Terminationn
Similarly to direct orders with enhanced security, if the order fails, the cause of the failure is reported in the
AddCause field.

User Manual 115
13.2 COMMAND BLOCKS
The commands sent to the device can be blocked for different reasons in which the execution cannot be allowed.
In part 7-2, of the IEC 61850 standard, the possible reasons for failure of a command are detailed.
The following subsections describe the different blocks implemented by the device.
IMPORTANT NOTE: The order of these sections matches exactly with the order of blocking verification
that the IED follows. So once a block is applied, the command will not prosper and next blocks will not be
checked.
13.2.1 Command blocks by inconsistent parameters

The parameters of the command are checked to ensure that there have been no changes to them.
This block only affects commands with ctlModel SBO_WITH_ENHANCED_SECURITY (4) that are performed
through the SelectWithValue service.
The reason for command failure when this block is generated is "inconsistent parameters" (AddCause = 26).
13.2.2 Command blocks by switching hierarchy

The next possible cause of locking a command is switching hierarchy blocking (AddCause = 2). The IED
implements a hierarchy of commands that implies the blocking of the orders according to their origin and the
configuration of the device.
In the standard IEC 61850, part 7-3, it is defined the possible origins of a command that are affected by
blockages due to the switching hierarchy.
 "not-supported": Only accepted in the mode that the order hierarchy is not handled.
 "remote-control": corresponds to a remote origin.
 "station-control" or "maintenance": corresponds to a console.
 "bay-control": corresponds to a console at bay / local level or to the display.
 "automatic-bay", "automatic-static" or "automatic-remote". By default, orders sent by
IEC61850 with these origins are allowed, except for the modes that strictly check the local
origin of the order (LRMode, Edition 2 and Exclusive Edition 2).
Under the section "Command blocks by interlocking" it is explained the particular operation
for these origins in H automation architectures.
 "process": Commands with this origin are not accepted in any case. The process source is
reserved for changes in the state of control elements that do not come from commands. If
there is a change in a signal associated with a command but the change of state has not
been a consequence of an order, but a spontaneous change, the order orCat will be written
to "PROCESS".
The "Remote/Local Type" setting determines how the device will behave at the moment of blocking the
commands by hierarchy. It is found in the data model as "GEN/LLN0.LRmode" or in the display under
"General configuration: Remote / Local Type". The following values are available:
Table 43. Available values for LRMode
LRmode Numeric Value

Not treated 0
Iberdrola 1
Exclusive 2
No HMI 3
ExclusiveBR 4
Edition2 5
ExclusiveEd2 6

User Manual 116

Depending on the mode selected, it can be taken into account the status of the signals GEN/LLN0.RemCtlBlk
(remote control signal status) and GEN/LLN0.Lockey (HMI signal status).
To interpret the tables in the next sections with edition 1 configurations, it is necessary to consider the first columns
according to the following relation:
❑ Loc = RemCtlBlk
❑ LocSta = Lockey
In any case, for these configurations, as the data model specific to ICD Ed2 is required, any LRMode associated with
Edition 2 is not available.

Depending on the mode selected, the MltLev setting of the LLN0 of the logical device GEN can be taken into
account, as well as the status of the Loc and LocSta signals.
MltLev is a boolean setting that can be found in the data model in "GEN/LLN0.MltLev", and indicates if more than
one level (Originator) has the switching authority. This setting only applies to Edition2 and ExclusiveEd2 modes.
Loc is a boolean status signal ("GEN/LLN0.Loc.stVal"). It shows the local status, which is unique for the device, so all
the Loc signals show always the same status (the standard defines this signal in several nodes with configured
commands). To be able to modify this state, we have two options:
 Sending a command on the RemCtlBlk ("GEN/LLN0.RemCltBlk") element. This way, every Loc signal
will be set to the same value as "GEN/LLN0.RemCltBlk.stVal".
 Configuring the LogInLR setting ("GEN/LLN0.LogInLR") to a valid signal reference, so that this signal
status stablishes the value of every Loc. It is important to note that this setting predominates over
sending the command to the RemCtlBlk element explained in the previous point. Therefore, when
this setting is configured the command over the RemCtlBlk element is not allowed.
LocSta is a boolean status signal ("GEN/LLN0.LocSta.stVal"). Its status shows if station or remote origins are
accepted, and as in the case of Loc, it is unique for the device although it may exist in several logical nodes. To
modify the status of LocSta, a command on the controllable LocSta element "GEN/LLN0.LocSta" can be issued. Every
LocSta element in the device will show the same status value.
The operating characteristics of each of the LRmode values are detailed in the following points:
❑ LRMode: Not treated
No switching hierarchy blocking on commands is applied. It is the only mode that allows commands
from the "not-supported" origin.
❑ LRMode: Iberdrola
The status of Loc and LocSta signals is taken into account. The following tables show for each
combination whether the order is blocked or allowed, depending on the origin of the order.
Table 44. Command blocks by switching hierarchy on mode "Iberdrola"
Loc LocSta Bay Station Remote

(1) (1) allowed blocked blocked
(1) (0) allowed allowed blocked
(0) (1) blocked blocked allowed

User Manual 117
Table 45. Command blocks by switching hierarchy for RemCtlBlk on mode "Iberdrola"

Table 46. Command blocks by switching hierarchy for LocSta on mode "Iberdrola"

(0) (1) blocked blocked blocked
❑ LRMode: Exclusive
This mode of operation implies that when activating the status of the RemCtlBlk (associated with Loc),
the activation of the value of the LocSta signal is automatically generated. Deactivation is independent.
The status of Loc and LocSta signals is taken into account in this mode.
Because the activation of the RemCtlBlk signal triggers the activation of the LocSta, in the "Exclusive"
LRMode, it is not possible to reach the Loc = 1 and LocSta = 0 state from the table’s origins. It is only
possible to reach this value after a LRMode change or using "automatic" origin, however, the behavior
is exactly the same as for Loc = 1 and LocSta = 1.
Table 47. Command blocks by switching hierarchy on mode "Exclusive"

(0) (0) blocked allowed blocked
Table 48. Command blocks by switching hierarchy for RemCtlBlk on mode "Exclusive"

Table 49. Command blocks by switching hierarchy for LocSta on mode "Exclusive"

❑ LRMode: No HMI

User Manual 118
Only the status of the Loc signal is taken into account. The following table shows for each combination
whether the command is blocked or allowed, depending on the origin.
Table 50. Command blocks by switching hierarchy on mode "No HMI"
Loc Bay Station Remote

(1) allowed blocked blocked
(0) blocked allowed allowed
Table 51. Command blocks by switching hierarchy for RemCtlBlk on mode "No HMI"
Loc Bay Station Remote

* The LocSta table has not been included because is not used in this mode. The command blocks
applied will be those of RemCtlBlk.
❑ LRMode: ExclusiveBR
This is a particular case of the "Exclusive" LRMode mode. This LRMode differs in that the LocSta
variable is not activated automatically when the RemCtlBlk is activated and it is possible to modify the
LocSta if the equipment is in local mode (Loc = 1) from the same origin (bay-control).
The following tables show for each combination whether the order is blocked or allowed, depending on
the origin of the order.
Table 52. Command blocks by switching hierarchy on mode "ExclusiveBR"

Table 53. Command blocks by switching hierarchy for RemCtlBlk on mode "ExclusiveBR"

Table 54. Command blocks by switching hierarchy for LocSta on mode "ExclusiveBR"

❑ LRMode: Edition2
Only for Edition 2 configurations. If LRMode is "Edition2", the normative hierarchies of commands
described in Part 7-4 of Edition 2 of IEC61850 standard (Annex B) apply.

User Manual 119
This implies that the local origin of the command is considered strictly, so that if Loc = 1, no command
(nor selection) from IEC61850 communications is accepted regardless of what is indicated in the origin
field (even if it is a bay-level console and commands with 'bay-control' origin). Therefore, when the
equipment is in local mode (Loc = 1) only commands sent from display or logic are accepted.
In this mode, the MltLev setting of the LLN0 of the logical device GEN, as well as the status of Loc and
LocSta signals, is used to determine if a command is required to be blocked by switching hierarchy.
The following table shows for each combination whether the command is blocked or allowed,
depending on the origin. This table affects all orders, including RemCtlBlk and LocSta.
Table 55. Command blocks by switching hierarchy on mode "Edition2"
MltLev Loc LocSta Bay Station Remote

(0) (1) (1) allowed* blocked blocked
(0) (1) (0) allowed* blocked blocked
(0) (0) (1) blocked allowed blocked
(0) (0) (0) blocked blocked allowed
(1) (1) (1) allowed blocked blocked

(1) (1) (0) allowed blocked blocked
(1) (0) (1) allowed allowed blocked
(1) (0) (0) allowed allowed allowed
* The local origin is checked strictly: Only display or logics.
❑ LRMode: ExclusiveEd2
Only for Edition 2 configurations. If the LRMode is set to "ExclusiveEd2", the command switching
hierarchy blocks are the same as in the "Edition2" case, except for the commands over the LocSta and
RemCtlBlk.
When operating a command on these two elements, the verification of the local origin is not strict, that
is, commands received from IEC61850 communications with origin 'bay-control' or 'automatic' sources
are allowed.
The following tables show the behavior of the switching hierarchy blocks on these two orders:
Table 56. Command blocks by switching hierarchy for RemCtlBlk on mode "ExclusiveEd2"

NOTE: MtlLev is not included as it does not modify the table.
Table 57. Command blocks by switching hierarchy for LocSta on mode "ExclusiveEd2"
MltLev Loc LocSta Bay Station Remote

(0) (1) (1) blocked blocked blocked

For all other commands, the local origin check remains strict, as detailed in the LRMode "Edition2"
mode.
User Manual 120
13.2.2.1 Exceptions to switching hierarchy blocks

Any order sent from the logics or from the pacFactory tool is not affected by switching hierarchy blocks.
In protection commands, hierarchy locks are the same as those in control commands, with the exception
of the following commands, that are never blocked by switching hierarchy.
 Reset commands for statistical data

 Reset commands for maximeter and minimeters
 Reset commands for energy counters
 Reset commands for queues
 Reset commands for LEDs and relays
 Battery connection/disconnection commands
In the LLN0 node of the logical device GEN the FKeysRem setting is defined. When is set to '1', it allows any
order given from the device’s display without any hierarchical blocking.
Additionally, with the configuration tool it is possible to set (in the sAddress), for each command of type SPC
and DPC, if the switching hierarchy blocks shall be avoided. It can be choosen whether this affects the
opening command, the closing command, or both.
13.2.3 Command 1 of n blocks

It ensures that multiple orders are not executed simultaneously. If a second command is received before the first
command is completed, the error is indicated as "1 of n" block (AddCause = 14).
13.2.4 Command blocks by mode (Mod/Beh)

This block is performed depending on whether the test bit of the received command is activated or not, and based on the
Beh status of the logic node. It has to be taken into account that the mode block is not checked in the case of making
commands over the Mod element. In case of blocking, the order is rejected with "blocked by mode" reason (AddCause =
8).
Table 58. Blocks by mode (Mod/Beh)
Command Test Bit Beh=On(1) Beh=Test(3) Beh=Off(5)

0 Allowed BLOCKED_BY_MODE BLOCKED_BY_MODE
1 BLOCKED_BY_MODE Allowed BLOCKED_BY_MODE
The IED contemplates 3 possible Beh / Mod values: 1: ON / 3: TEST / 5: OFF.
When the Beh is Off this block also applies to the selection of the command. As the test bit is not sent in the selection
request, it can not be checked in the other cases. The value Off is only defined in those logical nodes that it makes sense
to disable the node (for example protection functions).
Only with Edition2 configurations, to determine the Beh status of the logical node on which the command is executed,
different levels of hierarchy are defined:
❑ Mod of the own logical node.

❑ Mod of the LLN0 of the logical device to which the logical node belongs.
❑ Mod of the LLN0 of the logical device defined in the GrRef.
The GrRef setting is defined in the Edition2 of the standard and allows to relate a logical device to depend on a higher
hierarchy logical device. Its data type is objRef and it is found in the LLN0. The format to be used is the own logical
device concatenated to the IEDname of the installation.
The following table details the calculation of Beh of a logical node according to the different levels of hierarchy. The
GrRef can have an empty value and therefore considered unconfigured (NC):

User Manual 121
Table 59. Calculation of Beh according to hierarchy
GrRef LD LDMode LNMode LNBeh

➔
LLN0.Mod LLN0.Mod LN.Mod LN.Beh
On / NC On On ➔ On
On / NC On Test ➔ Test
On / NC On Off ➔ Off
On / NC Test On ➔ Test
On / NC Test Test ➔ Test
On / NC Test Off ➔ Off
Test On On ➔ Test
Test On Test ➔ Test
Test On Off ➔ Off
Test Test On ➔ Test
Test Test Test ➔ Test
Test Test Off ➔ Off
NOTE: Mod / Beh to Off is not accepted in LLN0 nodes.
13.2.5 Command blocks by Heatlh

The possibility of blocking commands based on a selectable alarm signal via the configuration tool (in a sAddress field) is
available. If this alarm signal is activated, the command will be blocked by "Blocked by Health" reason (AddCause = 13).
It is possible to set a different configuration for each command.
13.2.6 Command blocks by Interlocking

In IEC61850 Edition 2 configurations, the blocks by interlocking (EnaOpn/EnaCls) are only checked if the command is
issued with the “interlock-check” bit activated. If not, the command will not be checked against this blocking conditions.
On the other hand, in edition 1 configurations or other protocols different than IEC61850, the block by interlocking is
always checked.
The standard defines that the signals of the CILO logical nodes shall be used, but using the configuration tool it is
allowed to select these or any other signal in a generic way to perform the interlocking block. Signals can be set for both
the opening and closing blocks. The reason for the failure associated with this type of block is the "blocked by
Interlocking" (AddCause = 10).
In addition, within interlocking blocks, there is a check for installations in H automation architectures. This configuration is
performed using the configuration tool (automation signal sAddress field). When this signal is configured, the following
logic is followed:
❑ Automation signal activated:

 Only commands whose origin is "automatic" are accepted.
❑ Automation signal deactivated:
 Commands whose origin is "automatic" will be blocked.
For this section it is important to take into account the order followed to check the blocks, so that for example, with
LRMode configured to Edition2, and with the IED in local mode, automatic orders will be blocked by switching hierarchy
before reaching this kind of block.
13.2.7 Commands blocks due to invalid/reached position

The IED allows configuring blocks on commands based on the status of the item on which the order is intended and
taking into account whether an opening or closing is sent.

User Manual 122
These blocks are configured through the configuration tool (in a sAddress field) indicating the desired operating mode for
each command.
The commands will be blocked in accordance with the following table:

Table 60 Blocks in accordance with the command mode
Estado invalido /
Open status Close status
desconocido
Open Close Open Close Open Close
Command Mode 0 / -1 ALLOWED ALLOWED ALLOWED ALLOWED ALLOWED ALLOWED
Command Mode 1 BLOCK (1) ALLOWED ALLOWED BLOCK (1) BLOCK (2) BLOCK (2)
Command Mode 2 BLOCK (1) ALLOWED ALLOWED BLOCK (1) ALLOWED BLOCK (2)
Command Mode 3 ALLOWED ALLOWED ALLOWED BLOCK (1) ALLOWED BLOCK (2)
Thus, the blocks marked with (1) are blocks by "position reached" (AddCause = 5) and those marked with (2) are by
"invalid position" (AddCause = 4).
13.3 COMMANDS FOR OTHER POSITIONS
The configuration of these commands is related to the protocol by which they are propagated.
When the command is configured as a command of another device or UCL, the order will be sent to the corresponding
device behaving as a direct order with normal security (ctlModel = 1). The check of return information, pulseConfig, timeouts
and blocks must be performed on the device to which the order belongs.
13.4 COMMAND SADDRESS
Through the sAddress fields of each command the behavior explained in some of the previous sections can be modified.
The method for modifying the sAddress fields must always be the configuration tool. Manually changing these values can
cause errors and malfunction of the associated command.
Indicatively, the sAddress of a command has the following format:
sAddr = " a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s;TX1:Language 1 text,TX2: Language 2 text "
❑ a:= O (letter corresponding to the command) / LO (Letters corresponding to the command logics)
❑ b:= Command UCL number. Maximum 4 characters.
Value 0 is used to select internal Ucl.
❑ c:= Command number. Maximum 4 characters.

Number of the first associated internal command. Each control element has two internal commands associated.
The first corresponds to the “ON” command (ctlVal = 1) and the second to the “OFF” command (ctlVal = 0). The
sAddress value has to be configured always as the number of the first command, which corresponds to the “ON”.
❑ d:= Enabling off/aperture signal number (EnaOpn). Maximum 5 characters.

Only if configured: It is the number of the signal that allows or blocks the OFF/aperture command, in case of it is
activated or deactivated respectively.
❑ e:= Enabling on/close signal number (EnaCls). Maximum 5 characters.

Only if configured: It is the number of the signal that allows or blocks the ON/close command, in case of it is
activated or deactivated respectively.
❑ f:= Expected status inverted. (1 character)

When set to 1 indicates that the expected status of the signal associated with the command is inverted.

User Manual 123
❑ g:= Health signal number. Maximum 5 characters.

Only if configured: It is the number of the alarm signal that is used to block the order. If the alarm signal is not
active, the remaining locks are checked.
❑ h:= Command Mode. It accepts four possible values (0-3)

Depending on this field, the commands will be blocked for "invalid position" or "position reached". The absence of
this field or a -1 value, assumes the same operation as that corresponds to a 0 value.
The table with the explanation of each mode can be found in the corresponding blocks section.
❑ i:= H automation signal number. Maximum 5 characters.

Only if configured: If it is a valid signal number, the status of the signal is checked to know if the equipment is in
automatic or not:
 If signal value is '1', H automation is activated, so command requests over this element from any
origin that is not “automatic” will be blocked
 If signal value is '0', H automation is not activated, so command requests over this element from any
“automatic” origin will be blocked
❑ j:= UCL number of the enabling off/aperture signal (field d). Maximum 4 characters.
The value 0 is used to refer to internal ucl. If it is empty the ucl number of the command is used.
❑ k:= UCL number of the enabling on/close signal (field e). Maximum 4 characters.
❑ l:= UCL number of the H automation signal (field i). Maximum 4 characters.
❑ m:= Disable block by switching hierarchy (ON/close). 1 character.

Setting this field to value 1 disables blocks per switching hierarchy for the ON command.
❑ n:= Disable block by switching hierarchy (OFF/aperture). 1 character.

Setting this field to value 1 disables blocks per switching hierarchy for the OFF command.
❑ o:= UCL number of the H automation signal (field i). Maximum 4 characters.
❑ p: RS signal associated with return of command (only Ed2): opOpnPrg. Maximum 5 characters.
❑ q: RS signal associated with return of command (only Ed2): opClsPrg. Maximum 5 characters.
❑ r: RS signal associated with return of command (only Ed2): opOpnFail. Maximum 5 characters.
❑ s: RS signal associated with return of command (only Ed2): opClsFail. Maximum 5 characters.
The UCL associated to the four return signals of commands Ed2 is the UCL of the command itself.
❑ TX1:= Command text language1. Maximum 16 characters.
❑ TX2:= Command text language2. Maximum 16 characters.

User Manual 124
RIO MODULES
14. RIO MODULES
14.1 CONFIGURATION
The RIO modules are configured using the RIOGGIO logic nodes A maximum of 8 nodes of this type is contemplated.
Each node has series of attributes that allow us to select the RIO modules with which we are to communicate and to configure the
outputs to be published:
Table 61 RIO module configuration attributes in Edition 1
ATTRIBUTE DESCRIPTION
The RIO number to which we want to associate the current node. It is a configurable value
NumRIO.setVal
between 0 and 99.
The RIO module to which we want to associate. It can accept the 1 (12 inputs / 4 outputs) or 2
TypeRIO.setVal
(8 inputs / 2 outputs). The value 0 is reserved to indicate that the node is not configured.
InRef1.setRef IEC 61850 reference to the RIO module’s first output.
InRef2.setRef IEC 61850 reference to the RIO module’s second output.
InRef3.setRef IEC 61850 reference to the RIO module’s third output.
InRef4.setRef IEC 61850 reference to the RIO module’s fourth output.
Table 62 RIO module configuration attributes in Edition 2
The RIO number to which we want to associate the current node. It is a configurable value
NumRIO.setVal
between 0 and 99.
The RIO module to which we want to associate. It can accept the 1 (12 inputs / 4 outputs) or 2
TypeRIO.setVal
(8 inputs / 2 outputs). The value 0 is reserved to indicate that the node is not configured.
InRef1.setSrcRef IEC 61850 reference to the RIO module’s first output.
InRef2.setSrcRef IEC 61850 reference to the RIO module’s second output.
InRef3.setSrcRef IEC 61850 reference to the RIO module’s third output.
InRef4.setSrcRef IEC 61850 reference to the RIO module’s fourth output.
14.2 OPERATION
When we have configured a RIOGGIO logical node correctly, the expected performance in the different attributes is as follows:

User Manual 125
RIO MODULES
Table 63 Operation of RIO module attributes
Status of the communication with the associated RIO module. The value 1 indicates that it is
St.stVal
correct.
Indicates that the configured RIO type does not match that which is being received. This value
CfgErr.stVal
is only displayed in IEC 61850, it has no associated signal in the internal data base.
Ind[1..17].stVal The values received from the RIO module.
The values sent to the RIO module. The value always coincides with the signals configured in
SPSCO[1..4].stVal
the InRefs in the same index.
Both the elements received and the communication status has associated signals with fixed position in the internal database. The
signals are distributed as follows:
Table 64 Internal signals associated with RIO modules
LOGICAL NODE ELEMENT ASSOCIATED INTERNAL SIGNALS
Communication status 288

RIOGGIO1
Values received in command From 289 to 305.

RIOGGIO2

RIOGGIO3

RIOGGIO4

RIOGGIO5

RIOGGIO6

RIOGGIO7

RIOGGIO8

User Manual 126
CHANGES REQUIRING THE REBOOTING OF THE DEVICE
15. CHANGES REQUIRING THE REBOOTING OF THE DEVICE

The modification of the value of certain attributes requires the resetting of the device in order for the modification to have effect. In order
to inform of the need to manually reset of the device, the ResetDev.stVal signal has been defined within the GEN node’s LLN0. In some
cases, it is enough to send a new ICD / CID file.
For standard IEC61850 Ed1 configurations only, after a change on LGOS logical node subscription settings, the server does not require a
reset only if the LGOS was completely configured when the server started. In other case, the change of any of the settings will activate the
reset required signal.
The following table details the possible causes to activate this signal:
Table 65 Setting changes that require the manual reset of the device
LOGICAL NODE ATTRIBUTE DESCRIPTION DEACTIVATION WITH ICD FILE

The multicast reception MAC associated to
MAC.setVal YES
the goose
GoCBRef.setRef Goose control block reference YES
LGOS – Applies only on

IEC61850 Ed1 GoDatSetRef.setRef Dataset reference YES
configurations.
(Only if not completely GoID.setVal Goose identifier YES

configured at start-up)
ConfRev.setVal Configuration revision YES
LGOS data attribute assigned to one goose

InRef_.intAddr YES
data value
RIO module Type. Involves modifying the

RIOGGIO TypeRIO.setVal YES
structure of the goose.
Network interface associated to the Goose

genIPRV DevGoose.setVal YES
messages.
genIPRV NoGsVlan.setVal VLAN use in Goose messages YES
YES, it is also deactivated after the

LLN0 IRMod.setVal InRefs mode
modification of an InRef data
Change of the I/O cards configuration from
- Commercial code the local HMI (change in the commercial NO
code)

User Manual 127
RECEPTION GOOSES
16. RECEPTION GOOSES

The IEC 61850 server is conforming to IEC 61850 Edition 2.
For the details of the IEC 61850 interface implementation consult the following documents for the Ingepac EF family:
❑ PICS: Protocol Implementation Conformance Statement for the IEC 61850 interface
❑ PIXIT: Protocol Implementation eXtra Information for Testing for the IEC 61850 interface
❑ TICS: Technical Issues Implementation Conformance Statement
The Ingepac EF family maintains compatibility with the existing ICDs developed following Edition 1. The last point of this section
describes the GOOSEs subscription for that case. The remaining points refer to functionalities associated with Edition 2
configurations.
16.1 GOOSE SUBSCRIPTION
According to IEC 61850 Edition 2 the GOOSE subscription is configured using the Inputs-ExtRef elements in the CID file.
The Inputs section defines all external signals that will be received via GOOSE messages from other IEDs. In this section,
each ExtRef element references to one external item and the intAddr element makes the binding of the external signal to an
IED internal configured data.
The CID file of an IED with configured GOOSE subscriptions contains several IED sections. The IED section of the server device itself and
IED sections from each of the IEDs sending GOOSE messages to which the device is subscribed.
These external IED sections only contain the data model needed for the subscription to reduce the size of the CID file.
LGOS logical node is used to monitor GOOSE subscriptions. There are 32 instances of LGOS logical node, which allow
monitoring up to 32 GOOSE subscriptions.
The only configuration value in the LGOS logical node is the GoCBRef (Reference to the subscribed GOOSE control block).
The monitored values are:
❑ NdsCom: Subscription needs commissioning. When true, the received GOOSE message does not conform the current
subscription configuration; either the dataSetRef is wrong, the data set members, the configuration revision number, ...
❑ St:If true, the GOOSE subscription is active, other is inactive
❑ SimSt: If true, subscribed GOOSE messages with the simulation bit set are being received and accepted
❑ LastStNum: Last state number received
❑ ConfRevNum: Expected configuration revision number of the GOOSE messages
❑ RxConfRevNum: Configuration revision number of the received GOOSE messages
The St and SimSt data are mapped to the internal database to be used in for example logics or local display. The other
values are only available through the IEC 61850 communication.
The factory CID file contains 2 logical nodes (GOOGGIO1 and GOOGGIO2) with available data for the internal binding of
the received values.
Each of these logical nodes contains:

User Manual 128
RECEPTION GOOSES
❑ 32 boolean signals (Ind1 to Ind32 data)

❑ 4 dbpos signals (DPSInd1 to DPSInd4 data)
❑ 4 float values (AnIn1 to AnIn4 data)
In models with the "Extended control" option the IED data model can be extended with more logical nodes in the control
logical device for internal binding of the data received in GOOSE messages.
Extension capacity:
❑ Signals: Up to a total of 1024 internal signals (including the 2 GOOGGIO nodes) and taking into account that the dbpos
signals occupy 4 internal signals.
❑ Measures: Up to a total of 256 measures (float values).
As established in Edition 2 of the standard, it is possible to subscribe to both data attributes and data objects. The recommendation
following criteria of efficiency and response time is to use data attributes in GOOSE messages. In any case, the device supports the
subscription to data objects of the following CDCs:
❑ Status: SPS, DPS, ENS, ACT, ACD.

❑ Measured: MV, CMV, WYE, DEL, SEQ, DEL y SEQ.
❑ Controllable: SPC, DPC, ENC.
For more information about the GOOSE subscription configuration process consult the software tool manual
(energyFactorySuite/pacFactory).
16.2 GOOSE SIMULATION
The device implements the GOOSE simulation mode defined in the IEC 61850 Edition 2.
This mode allows the simulation of any GOOSE that is present in the communication network so that two GOOSES with the same
information data will be present at the same moment, the real one without the simulation bit active and the simulated one with the
simulation bit active. If the subscriber is in simulation mode, once it has received the first simulation GOOSE its values will be used
instead of the values of the original GOOSE.
Therefore, if the device is in simulation mode, it still accepts 'original' GOOSE messages, and only discards the 'original' GOOSE
messages for those GOOSEs which are simulated.
Simulation mode is enabled with the controllable data "Sim" included in the LPHD logical node in the GEN logical device.
In each LGOS logical node, used to monitor GOOSE subscription, the SimSt status shows with TRUE value that subscribed GOOSE
messages with the simulation bit set are being received and accepted.
When the subscriber is not in simulation mode (GEN/LPHD.Sim.stVal=false) the simulated GOOSEs are ignored. The device keep on
using the "real" GOOSE messages.
When the subscriber is in simulation mode (GEN/LPHD.Sim.stVal=true) the simulated GOOSEs are used for operational purposes. The
device ignore the "real" GOOSE messages after a first simulated one has been received. The corresponding LGOS.SimSt is set when the
first simulated message is received and only cleared when LPHD.Sim.stVal is set to false.
Once the device has received a simulated message for one of the subscribed GOOSE messages, it will not process the real one until the
simulation mode of the device (LPHD.Sim.stVal) is set to false.

User Manual 129
RECEPTION GOOSES
The following state machine, from IEC 61850 TISSUES data base (num. 1151), displays the different states and illustrates the
supervision of GOOSE subscription with regards to LGOS.St and LGOS.SimSt
stm LGOS
[LPHD.Sim.stVal==FALSE]
Initial
LPHD.Sim.stVal
== TRUE
[y] [n]
subscription normal
goose as long as no
[LPHD.Sim.stVal == TRUE] subscribtion normal [normal GOOSE message received] w ait for normal GOOSE
w ait for normal or [TAL expired] simulated GOOSE
goose
simulated GOOSE receiv ed
[LPHD.Sim.stVal == FALSE] [TAL expired] SimSt.stVal = FALSE
SimSt.stVal = FALSE St.stVal = FALSE
SimSt.stVal = FALSE SimSt.stVal = FALSE
St.stVal = TRUE
St.stVal = FALSE [normal GOOSE received] St.stVal = TRUE
[LPHD.Sim.stVal==FALSE]
[simulated GOOSE received] [LPHD.Sim.stVal == FALSE]
[simulated GOOSE received]
w ait for Simulated

subscription simulated [TAL expired] GOOSE
GOOSE
[simulated GOOSE received] SimSt.stVal = TRUE
SimSt.stVal = TRUE St.stVal = FALSE
St.stVal = TRUE
It is possible to enable a GOOSE transmission simulation mode with the "TestEna" and "LogInTest" setpoints, included in GEN\LPHD
logical node:
❑ TestEna: If this setpoint is TRUE enables the GOOSE transmission simulation mode
❑ LogInTest: This setpoint allows to configure a signal which, when active, enables the GOOSE transmission simulation mode
In this mode all the GOOSEs transmitted by the device have the simulation field with TRUE value and the mode is indicated in the status
data GEN\LPHD.TestSt.
The following logic for the two configuration setpoints is used:
❑ TestEna=FALSE : TestSt=FALSE
❑ TestEna=TRUE and LogInTest=(not configured) : TestSt=TRUE
❑ TestEna=TRUE and LogInTest=(Signal data with value=TRUE) : TestSt=TRUE
❑ TestEna=TRUE and LogInTest=(Signal data with value=FALSE) : TestSt=FALSE

User Manual 130
RECEPTION GOOSES
16.3 TEST MODE
The device implements the Test mode defined in the IEC 61850 Edition 2.
Switching between the modes (Mod.stVal) only happen as a result of an operator command to the data object Mod.
The values of Mod and Beh that are used are:
❑ On:
❑ The application represented by the LN works.
❑ All communication services work and get updated values.
❑ Control commands with test bit will be rejected with AddCause "Blocked-by-mode".
❑ Test:
❑ The application represented by the LN works.
❑ All communication services work and get updated values.
❑ Data objects will be transmitted with quality “test”.
❑ Control commands with test bit will be accepted only by LNs in “test” mode.
❑ Off:
❑ The application represented by the LN doesn’t work.
❑ No process output is possible. No control command should be acknowledged (negative response).
❑ Data objects will be transmitted with quality “invalid”.
❑ Only the data object Mod and Beh should be accessible by the services.
On-blocked and test/blocked values are not supported.
16.3.1 Logical devices management hierarchy

Logical devices or LD, are used to represent a group of typical automation, protection or other functions. The functions
are defined as logical nodes contained and managed in logical devices. The hierarchy determines how the mode (e.g.
On, Off, Test …) of these functions and sub-functions is managed, so that a change in the value of the mode at higher
level influences the lower levels.
LLN0 of the logical devices that can be configured with a hierarchy contains a setting data named GrRef whose type is
objRef.
In order to configure a hierarchy the format of the GrRef value must be set with the name of the higher level logical device
concatenated to the IEDname of the installation. It is also possible that it is not configured.
The device implements the hierarchy on these logical devices:
❑ CTRL: Control functions (only present in devices with "Extended control")

❑ GEN: General functions
❑ PROT: Protection functions
GEN is considered the main logical node and its LLN0 logical node does not have the GrRef setting. CTRL and PROT
logical devices can be configured with a hierarchy.
So the typical hierarchy configuration is to assign the GEN logical device as higher level of CTRL and PROT. In this case, the
functions of CTRL and PROT logical devices are considered sub-functions of the GEN logical node and if the mode of
the GEN logical device is modified (GEN/LLN0.Mod) it will affect the CTRL and PROT logical devices also.

User Manual 131
RECEPTION GOOSES
The mode of the LNs in any logical device may be changed individually with its own Mod, or globally by means of LLN0 of
each logical device. Only changes in GEN/LLN0.Mod will affect the other logical devices that are configured as lower level
in the hierarchy.
For more details about how hierarchy affects commands behaviour, consult on this manual the "Command Blocks: Commands
blocks by mode (Mod/Beh)" section.
16.4 SERVICE TRACKING
Service tracking is represented by the logical node LTRK and is defined as the function in charge of recording the
parameters values used by any service defined in IEC 61850-7-2 (after a service execution). It is thus possible to read, report
or log these values for system behavior analysis.
The trigger option for these data is "data-update", so it has to be configured in the associated control block if, for example, it is
included in a report.
Service type values tracked by Ingepac EF:
❑ 16 - SelectActiveSG
❑ 17 - SelectEditSG
❑ 19 - ConfirmEditSGValues
❑ 24 - SetBRCBValues
❑ 26 - SetURCBValues
❑ 34 - SetGoCBValues
❑ 43 - Select
❑ 44 - SelectWithValue
❑ 45 - Cancel
❑ 46 - Operate
❑ 47 - CommandTermination
❑ 54 - InternalChange
Service error implemented values:
❑ 0 - no-error
❑ 1 - instance-not-available
❑ 2 - instance-in-use
❑ 3 - access-violation
❑ 4 - access-not-allowed-in-current-state
❑ 5 - parameter-value-inappropriate
❑ 6 - parameter-value-inconsistent
❑ 7 - class-not-supported
❑ 8 - instance-locked-by-other-client
❑ 9 - control-must-be-selected
❑ 10 - type-conflict
❑ 11 - failed-due-to-communications-constraint
❑ 12 - failed-due-to-server-constraint

User Manual 132
RECEPTION GOOSES
The logical node LTRK contains data classes with functional constraint FC=SR needed for track the previously defined services. The
following common attributes are included in all services:
❑ objRef: Reference of the object that is being tracked: either a control block that is being accessed or a control object that is
being controlled.
❑ serviceType: Type of the tracked service.
❑ errorCode: Error associated to the service that is specified by serviceType; value no-error for successful service.
❑ originatorID: Originator of the service. In general, the IP address of the client.
❑ t: TimeStamp of the completion of the service.
❑ d: Description
The following specific data objects are and included in the LTRK logical node:
Command service tracking:
Each enumerated has its own particular EncTrk, in which the ctlVal matches with the enumerated type defined for the controllable
object.
The index at the end may be incremented (For example EncTrk2) to define different instances.
❑ SpcTrk: Control service tracking for controllable single point.

❑ DpcTrk: Control service tracking for controllable double point.
❑ EncTrk1: Control service tracking for enumerated controllable. Mod (OFF)
❑ EncTrk2: Control service tracking for enumerated controllable. Mod (Test)
 Associated services:
▪ Select, SelectWithValue, Cancel, Operate
 Specific attributes (in addition to common attributes):

▪ ctlVal
▪ origin
▪ ctlNum
▪ T
▪ Test
▪ Check
▪ respAddCause
Unbuffered report service tracking:
The IED generates a tracking register when a SetURCBValues is done over the following attributes: rptID, rptEna, datSet, optFlds,
bufTm, trgOps, intPd and resv, what is according to IEC 61850-7-2 Subclause 15.3.2.3.1.
The change of other attributes associated to a URCB like confRev, gi, etc. will not generate a tracking register.
The attributes RptEna and Resv of the URCB instances are tracked at loss of association with the Client, with ServiceType =
InternalChange, with “127.0.0.1” as content of the originatorID field.
❑ UrcbTrk: Access service tracking for unbuffered report control block.

User Manual 133
RECEPTION GOOSES
▪ SetURCBValues

▪ rptID
▪ rptEna
▪ resv
▪ datSet
▪ confRev
▪ optFlds
▪ bufTm
▪ sqNum
▪ trgOps
▪ intgPd
▪ gi
▪ owner
Buffered report service tracking:
The IED generates a tracking register when a SetBRCBValues is done over the following attributes: rptID, rptEna, datSet, optFlds,
bufTm, trgOps, intPd, purgeBuf, entryID, and resvTms, what is according to IEC 61850-7-2 Subclause 15.3.2.2.1.
The setting of other attributes associated to a BRCB like confRev, gi, etc. will not generate a tracking register.
The attributes RptEna and ResvTms of the control block are tracked at loss of association with the Client with ServiceType =
InternalChange, with “127.0.0.1” as content of the originatorID field.
❑ BrcbTrk: Access service tracking for buffered report control block.

▪ SetBRCBValues

▪ rptID
▪ rptEna
▪ datSet
▪ confRev
▪ optFlds
▪ bufTm
▪ sqNum
▪ trgOps
▪ intgPd
▪ gi
▪ purgeBuf
▪ entryID
▪ timeOfEntry
▪ resvTms
▪ owner
Goose service tracking:
❑ GocbTrk: Access service tracking for goose control block.


User Manual 134
RECEPTION GOOSES
▪ SetGoCBValues

▪ goEna
▪ goID
▪ datSet
▪ confRev
▪ ndsCom
▪ dstAddress
▪ minTime
▪ maxTime
▪ fixedOffs
Settings service tracking
❑ SgcbTrk: Access service tracking for setting group control block.

▪ SelectActiveSG
▪ SelectEditSG
▪ ConfirmEditSGValues

▪ numOfSG
▪ actSG
▪ editSG
▪ cnfEdit
▪ lActTm
▪ resvTms
16.5 SUBSTITUTION MODEL
It allows to establish individually the values of some data that are sent through the protocol IEC61850.
Usually, input from the process or the result of the calculation from a function provides the value of a data (in that case, the
source is called "process"). In case of substitution model, the value of the data may be provided by an operator making use
of an IEC 61850 client.
Substitution model is available for the following common data classes:
❑ SPS (Single Point Status)

❑ DPS (Double Point Status)
❑ INS (Integer Status)
❑ SPC (Single Point Control)
❑ DPC (Double Point Control)
❑ MV (Measured Value)
❑ CMV (Complex Measured Value)
The IEC 61850 standard does not define the substitution model for other classes like ACT (Protection activation
information), ACD (Directional protection activation information), VSS (Visible String Status) or any of the settings classes.
Data classes that allow substitution have an attribute "subEna". If it is set to TRUE, the value of the data used for the IEC
61850 communications is the value configured in the following attribute (depending on the data type):

User Manual 135
RECEPTION GOOSES
❑ Value:
❑ subVal: SPS, DPS, INS, SPC, DPC
❑ subMag: MV
❑ subCVal: CMV
❑ Quality: The attribute "subQ" is the value used to substitute the data attribute q. When subEna is true, the source quality
bit substituted is always set.
On measurement data substitution, the value is checked against the configuration of the measure (max, min, db …) so the
substituted value is affected by such configuration.
It is the responsibility of the client application, in particular in the case of multiple attributes to be substituted, to set the
relevant substitution values before enabling substitution, as well as, disable substitution on all substituted values.
The substituted values only apply to the IEC 61850 communication values. These means that the substituted values are not
used in the logics or protection functions of the device.
There are several data with a special behavior for which the substitution of the value affects to the behaviour of the
IEC61850 server:
❑ BlkGoose.stVal: It allows blocking the transmission of all gooses.

❑ TestSt.stVal: It allows enabling the simulation bit in transmitted gooses.
❑ Sim.stVal: It allows activating the simulation mode.
Also defined in the substitution model, it is available the attribute "subID". When the substitution is activated, the device
automatically sets the subId to the IP address of the client device that activated the substitution. After this moment, the client can
write any other string to identify itself. Later when substitution is deactivated, the value is modified to a fixed empty string. In
conclusion, this attribute can be only modified after setting subEna to true.
16.6 FILE TRANSFER
The IED implements the IEC61850 MMS file services. Following the Edition 2 of the IEC61850 standard, the structure of files and
directories is based on a FLAT FILESYSTEM with pseudofolders. This means that it is not accessed through folders, it is only allowed to
read the root directory where all the existing files in the different subfolders are shown concatenating the path to the file name.
The available permissions are the same as those of the user 'ftpuser', and only writing the pseudofolder /SCL/notvalidated/ is allowed.
This behavior is used from firmware version 6.0.17.0 for both Edition 1 and Edition 2 configurations. In firmware versions prior to this
(only Edition 1 configurations were supported) the file and directory structure is based on folders, being able to access and read each
one separately.
16.7 EDITION1 SUBSCRIPTION. LGOS MODEL.
Only for ICD configured as Ed1: This model makes it possible to configure and supervise the complete status of each reception goose
within a single logical node.
Each goose subscription is associated with one LGOS logical node wich contains the configuration for that subscription, so there can be
as many subscriptions as LGOS logical nodes in the data model. The factory CID file contains up to 32 LGOS logical nodes that allow the
subcription to up to 32 goose messages.
To use the received data in the goose message they must be mapped to LGOS data. Each LGOS has:
❑ 17 boolean signals (Ind1 to Ind17 data)

❑ 4 dbpos signals (DPSInd1 to DPSInd4 data)

User Manual 136
RECEPTION GOOSES
❑ 8 float values (AnIn1 to AnIn8 data)
16.7.1 Configuration values

Used to establish the desired subscription parameters for each goose.
To create a subscription it must be configured:
❑ Configuration data of the Goose message to subscribe.

❑ Data assignment: Each data from the received Goose message can be assigned to one data in the LGOS logical node
in which the received value will be copied.
Table 66 LGOS model configuration values
ConfRev.setVal Must match the value received in the goose.
GoCBRef.setRef The goose reference to which we subscribe.
GoDatSetRef.setRef The reference of the dataset to which we subscribe.
GoID.setVal The identifier of the goose to which we subscribe.
The reference to the signal in which the goose element established by the InRef index is
InRef[..].intAddr
received. It must be a mapped signal within the goose signals range.
MAC.setVal The multicast MAC to which we subscribe.
These values, apart from the “intAddr” for the internal data assignement, must be the same ones received in the Goose message.
The data mapping is configured with the InRef data (InRef1 to InRef34). The InRef index indicates the reception goose data position
associated with that InRef (InRef1 associated to first goose data, InRef2 associated to second goose data, etc.)
In the InRefx.intAddr attibute must be configured the LGOS data in which the value will be copied. The value must be:
❑ Boolean signals: Indx.stVal / Indx.q

❑ Dbpos signals: DPSIndx.stVal / DPSIndx.q
❑ Float values: AnInx.mag.f / AnInx.q
If in the Goose message the qualities of the data are also received they must be assigned to a “q” data of one of the LGOS node
data, like the rest of the Goose data.
To configure this assignment the user must know the format of the data of the Goose message because the selected data in the
LGOS node to copy the received value must have the same format.
Each LGOS logical node in the the factory CID data model has 34 InRef data so the device can subscribe to Gooses with up to 34
elements.
For example if the configured value is InRef3.intAddr = Ind2.stVal this means that the third value in the received goose (that must
be a boolean value) will be copied to the LGOSx.Ind2.stVal data.
The software tool allows configuring these goose subscritpions manually or automatically (for more information consult the
pacFactory software tool manual).

User Manual 137
RECEPTION GOOSES
16.7.2 Supervision values

They indicate information about the status of the goose subscription at all times. The status signal conditions the updating of the
rest of the Data. If the status is incorrect, the rest of the signals will not be updated with the values received.
Table 67 LGOS model supervision values
St.stVal Subscription status. Value “1” indicates that the subscription was successful.
Sim.stVal Activated when the subscription is received in test mode.
NdsCom.stVal Activated when the subscription has the “Needs Commissioning” flag activated.
LastStNum.stVal The last status number received.
ConfRevNum.stVal The configuration revision received.
Note: Only the St data is mapped to the internal database to be used in for example logics or local display. The other values are
only available through the IEC 61850 communication.
16.7.3 Checked values

The following values are checked to decide if the goose message is valid:
❑ TAL (Time Allowed to Live) not zero

❑ MAC multicast
❑ Dataset
❑ GoCBRef
❑ GoID
It is also checked that the types of each goose data mach the types of the LGOS data in which they will be copied.

User Manual 138
TCP/IP NEWORK CONFIGURATION
17. TCP/IP NEWORK CONFIGURATION
17.1 DESCRIPTION
In the device has a front Ethernet interface and may have up to two rear Ethernet interfaces. Each of which can be configured to
belong to the network that the user wants, as seen in the figure below:
❑ ETH0, frontal Ethernet.

❑ ETH1, rear Ethernet.
❑ ETH2, rear Ethernet.
The rear ethernets can be selected from one of the following options (see commercial code):
❑ Independent port
❑ Redundancy module configurable between PRP, HSR and Switch mode
❑ Link failover redundancy (both ethernet ports used)
The configuration of each network can be made:
❑ From the device Display (see section of the display).

❑ From PacFactory configuration tool (see user manual pacFactory).
The device has signals to indicate the link status of each of the ethernet ports in the LPHD1 node of the logical device GEN:
Table 68. Link status signals
Señal Dato Atributo

Link Ethernet 0 Eth0Link stVal
Link Ethernet 1 Eth1ALink stVal
Link Ethernet 1 redundant Eth1BLink stVal
Link Ethernet 2 Eth2ALink stVal
Link Ethernet 2 redundant Eth2BLink stVal

User Manual 139
Redundant Link indications are only used in the case of redundant communications. In non-redundant communications, the link
indications are shown in the Eth1ALink and Eth2ALink data.
In the link failover redundancy the link indications are shown in the Eth1ALink and Eth1BLink data.
17.2 COMMUNICATIONS REDUNDANCY
The device has several options of physical communications redundancy divided into two hardware solutions:
❑ PRP / HSR / Switch mode (Options O and P of the commercial code)

❑ Link redundancy (Options I, J and K of the commercial code)
When the device has the PRP/HSR/Switch mode module, the user can configure any of the three options or consult the configured
option from the local display (Initial menu - Communications - Configuration PRP / HSR / Sw) or from the web server of the device
(Maintenance menu - Communications - IP network configuration).
17.2.1 PARALLEL REDUNDANCY PROTOCOL (PRP)

The PRP (Parallel Redundancy Protocol) is a redundancy communication protocol defined in the IEC 62439-3 standard and it is one
of the redundancy mechanism recommended in IEC 61850 networks.
In the PRP protocol the device use two redundant ethernet ports and the protocol is based on the simultaneous transmission and
reception of data via both independent ports.
In PRP solutions two independent ethernet networks are used. Each device is attached to both networks and sends and receives all
the frames over both LANs simultaneously, consumes the first frame and discards the duplicate. With this mechanism PRP ensures
zero-packet loss and zero recovery time upon single network failures.
The two LANs have no connection between them and are assumed to be fail-independent, both are identical in protocol at the
MAC-LLC level, but they can differ in performance and topology.
With the PRP protocol additional information called RCT (Redundancy Control Trailer) is added to the Ethernet frame at the link
layer in order to control redundancy. This information is transparent for devices that do not use PRP protocol and it is used by PRP
devices to discard the duplicate frames.
Devices without PRP can be connected to one of the redundant ethernet networks but in that case they only can communicate with
the devices connected to the same network. In order to enable redundancy in non-PRP devices an external converter called RedBox
(Redundancy Box) can be used.
17.2.2 HIGH-AVAILABILITY SEAMLESS REDUNDANCY (HSR)

The HSR is a redundancy communication protocol defined in the IEC 62439-3 standard and it is one of the redundancy mechanism
recommended in IEC 61850 networks.
In the HSR protocol the device use two redundant ethernet ports and the protocol is based on the simultaneous transmission and
reception of data via both independent ports.
In the HSR networks no external switches are used, instead each device has two ring ports, and all the devices are connected in a
ring topology, with one port of the device connected to the previous device and the other connected to the following device.
For each frame to send, the device sends it duplicated over both ports. So one frame travels in the ring in the clockwise direction
and the other frame travels in counter-clockwise direction. Each direction is treated as a separate network. So if there is a failure in
one point of the network, the frames reach the destination using the other direction in the ring. With this mechanism HSR ensures
zero-packet loss and zero recovery time upon single network failure.
An HSR tag is placed at the beginning of each frame to allow early identification of frames. With this tag each device can identify
the HSR tagged traffic and reject the duplicated frames coming from the both ports of a device and the frames circulating in the
ring. When a device receives a frame directed to it or that it sent, the frame is discarded and it is not forwarded again in the ring.
The frame is also discarded if it is a frame that it already sent in the same direction (i.e. multicast frames).

User Manual 140
Devices within the ring are restricted to be HSR-capable IEDs. In order to enable redundancy in non-HSR devices an external
converter called RedBox (Redundancy Box) can be used.
17.2.3 SWITCH MODE

In the switch mode both ethernet ports act as an unmanaged switch forwarding the network traffic.
The recommended network topology would be a cascade or Daisy-chain connection without closing a communication ring because
the IED integrated switch does not implement the RSTP protocol.
17.2.4 LINK FAILOVER REDUNDANCY

With the link failover redundancy the device uses two ethernet ports for a redundant communication.
In this redundancy mode the device communicates by one of the ethernet ports and if there is a link failure in that port, switches to
the redundant port if the link status of that port is active.
If the link status of the passive port returns to normal, the communication is maintained in the active port and the devices only
change the active port in case of link failure.
In this redundancy, unlike the case of PRP redundancy, it should not be used two independent ethernet networks. The two
Ethernet ports of the equipment must be connected to different network switches, but must belong to the same network, so that
the switches should be connected at some point in the network.
This switching is almost instantaneous, allowing even Gooses redundancy without loss or minimal loss (1 repetition). Regarding
communications with IEC 61850 clients, depending on the ring reconfiguration time communications, we even could not lose the
connection or the open session.
The device has link failover redundancy status signals in the logical node LPHD1 of the GEN logic device, to indicate which of the
two channels is active and to indicate possible failures in the redundancy.
Table 69. Link failover redundacy status signals
Señal Dato Atributo

Channel A active Ethernet 1 Eth1Ast stVal
Channel B active Ethernet 1 Eth1Bst stVal
Ethernet redundancy Alarm EthRAlm stVal
17.3 GENERAL CONSIDERATIONS ABOUT NETWORK CONFIGURATION
When configuring the network of the device it must be taken into account the following considerations:
❑ Basic concepta about networks:

 The format of the IP address or mask have the dotted decimal notation. The checks are performed according to this
standard.
 Addresses ending in 0 correspond to networks, not devices. For example : 192.168.200.0
 Addresses ending in 255 correspond to broadcast messages. For example : 192.168.200.255
 All network traffic for an IP address that is not included in the configured networks, will be redirected to the default
gateway configured.
❑ It is not allowed the IP address or mask 0.0.0.0.
❑ It is not allowed the IP address or mask 255.255.255.255.

User Manual 141
❑ From version 5.25.16.1 of firmware it is possible to configure several IP addresses in the same ethernet interface. For
previous versions it is not allowed.
❑ Gateways configuration:
 There can be only one default Gateway in the devices and it will be associated to a specific Ethernet interface.
 If a Gateway is configurec, the static routes for the ethernet traffic will be determined by up to 10 groups or three
parameters:
 IP address of the network or destination host. This IP address indicates the network or the device you want
to connect to.
 Network mask or destination host mask.
 Gateway IP address. It must be in the same net segment than the IP address configured in that ethernet
port; because in another way the device will not access to the gateway.
 If the IP address of the network or destination host or the mask of the network or destination host are not configured,
the default values are:
 IP address: 0.0.0.0, it will be all the networks or default gateway.
 Network Mask: 255.255.255.255, it will be all networks or default gateway.
 The configuration of gateways can only be done from the Display.
 When changing the IP address, the gateways that are no longer accessible by the new IP will be removed
permanently.
 The IP change command keeps the mask that was associated with that Ethernet interface.
 Do not configure two different Ethernet interfaces within the same network segment. When you configure
two interfaces within the same network segment, the device will use only one of them.
17.4 GOOSES
GOOSE messages (IEC 61850 peer-to-peer communications) are not on the TCP/IP layer, they are Ethernet packets and are configured
at the MAC level.
The devices subscribes to multicast MAC addresses for receiving messages and transmit to a specific Multicast MAC address.
Ethernet interface ETH0 is not ready to receive / transmit packets GOOSE.
17.5 FIREWALL
From firmware version 5.25.16.1 the device incorporates a firewall functionality through which any port in TCP/IP communications (eg
PING, FTP, sFTP, HTTP, etc.) can be blocked.
The firewall function can be enabled or disabled independently for each of the network interfaces. In case of link failover redundancy
interfaces, only the ETH1 interface shall be configured for both rear Ethernets.
Each TCP or UDP port can be configured as "closed" or "opened". When the firewall function is enabled on a network interface by
default all TCP ports are closed and those that want to be left opened must be configured. And in the case of configuring a port as open
the IP addresses from which the port will be accessible can be configured or leave it open for any IP address.
Configuration is done from the pacFactory / energyFactorySuite software tool. Refer to the user manual of the tool for more details on
the configuration.

User Manual 142
KEYBOARD AND GRAPHIC DISPLAY
18. KEYBOARD AND GRAPHIC DISPLAY
18.1 GENERAL OPERATION
18.1.1 Display structure

The screens are grouped into the following types:
❑ Graphic pages. Only available in models featuring "extended monitoring functions".

❑ I/O pages
❑ Secuence of Events (SOE)
❑ Protection events pages
❑ Alarm pages. Only available in models featuring "extended monitoring functions".
❑ Device status pages
❑ Fault pages. Not available in CDx models.
❑ Measurements pages. Only available in CD1 y CD2 models
❑ Grouping of other screens
Each display type has its own treatment.
There are also menu pages (which include the protection, control and general settings, such as the date and time, password, FW
versions, etc.), which are treated differently to those mentioned above.
18.1.2 Organization of the pages

The pages are organized into screen types, whose order of presentation is configurable using an external tool. The tool also enables
the unit’s start page to be assigned. The keys “(Left), →(Right)” allow the user to scroll through the different screen types
defined as main screens. The screens can be scrolled in both directions: upon reaching the last screen type the display returns to
the first screen, and vice-versa.
By clicking on the “ (Up),  (Down)” keys in any screen, the screens belonging to the same type are shown. The I/O, SOE, and fault
pages are presented in a preconfigured order. However, in the graphic and alarm screens the presentation order is defined using an
external tool.
If, when in any screen belonging to specific type, we press “(Left), →(Right)”, the following screen type is displayed whilst the
screen position remains within the type in question. Thus, when scrolling through the screen types the last screen types selected
when exiting a specific type are shown.
If no keys are pressed within a period greater than 5 minutes, the unit returns to the start page and the first page of each type is
selected.
By pressing on <ESC> from any screen we return to the start page, whilst the current page of each screen type is maintained.
There is a special screen type called “Menu to Other Screens” that contains an index of screens not considered important enough
to have been defined as main screens and which enables access to the same. This screen is configurable via a PC tool.
By pressing <MENU> from within any screen, the first page of the settings menus is displayed.
The possibility of multi-language is available.
Device with IP protection covers
If the unit is fitted with an IP protection cover, only certain buttons will be accessible from the front, depending on the model in
question:

User Manual 143
❑ Preset Keys (1/2 chassis – 5U and 19” chassis – 4U)

The only keys available are I, O, SEL, INF and DES.
The INF button allows the different screens to be displayed in a circular mode, whilst the order is configurable via a PC tool.
❑ Functional Keys (1/2 chassis – 5U and 19” chassis – 4U)

The only keys available are I, O, F1, F2, F3, F4, F5 and the DOT key.
The DOT button allows the different screens to be displayed in a circular mode, whilst the order is configurable via a PC tool.
18.1.3 Treatment of the functional keys

The functional keys are configured with the PC tool, with the control and associated status being configured for each key. In
addition there is a check box to reverse the status of the signal associated with the functional key. This option only applies to
Boolean (not double) signals.
The possible values of the status signal associated to the functional key and its corresponding representation via the LEDs are:
❑ Not configured: the 2 LEDs OFF.

❑ Unknown Status: the 2 LEDs OFF.
❑ OFF Status: upper LED OFF and lower LED ON.
❑ ON Status: upper LED ON and lower LED OFF.
❑ Invalid Status: the 2 LEDs ON.
The functional keys have 3 operating modes configurable by setting “GEN/LLN0/FbuttType”:
❑ “Functional keys” Mode:

 By pressing the key, the associated item is selected and the corresponding LED or LEDs blink.
 Once the item has been selected, the associated command can be executed by pressing the “I” or “O” keys.
 Once the above-mentioned key has been pressed, the unit executes the command and the lit LED or LEDs cease to
blink.
 Once a command has been executed, the status of the associated LED or LEDs is updated. In case of a failure, a
window indicating the cause of the failure will appear in the display.
❑ “Command 52 + Functional” Mode:

 By pressing the key, the associated item is selected and the corresponding LED or LEDs blink.
 Once the item is selected, depending on its status one of this windows is shown:
 ON Status: displays the confirmation window for the OFF command.
 OFF Status: displays the confirmation window for the ON command.
 Unknown / Undetermined Status: Displays the confirmation window for the two possible ON and OFF
commands. With the " (Up) or  (Down)" keys the desired command is selected and with the  (Enter) key
the command confirmation window appears. With the "ESC" key to exit the selection screen.
 Once a command has been executed, the status of the associated LED or LEDs is updated. In case of a failure, a
window indicating the cause of the failure will appear in the display.
❑ “Command Confirmation” Mode:

 The operation is the same as the "Functional Keys" mode but with the particularity that every time the user executes
an command (I / O buttons) a confirmation message will appear on the display (pressing the ENTER key executes the
command and Pressing ESC cancels).

User Manual 144
This mode will be applied for both the graphical screens commands and the functional key commands (contemplating
that we can be in any of the display screens)
NOTE 1: To change this setting from the display, the settings menu is accessed and in the initial menu select the 'general settings'
menu and press the ENTER key. Within this node, the setting is 'Command Type'. The 'With confitmation' option is selected and the
settings are validated.
NOTE 2: When a function key has not a configured signal but it has a configured command the 2 LEDs remain OFF until the function
key is pressed. At that moment the 2 LEDs start blinking.

User Manual 145
18.1.4 Graphics pages

The maximum number of graphic screens is 9.
Use the “ (Up),  (Down)” keys to switch from one group of graphic screens to another.
The order of the “live points” that have commands and the sequence of the graphic screens can be modified using the PC tool.
Figure 1 Single Line diagram Figure 2 Single Line diagram with indication of non-run command
The treatment of controls WITH Preset Keys:
❑ To run a command, we must first select the item to be sent. To do so, and once we have selected the screen
containing the item to be sent, we must press “SEL”. The symbol of the item that has been configured to priority 1
and which has an associated command will appear and begin to flash.
❑ By pressing “SEL” we scroll through the different “live points” with commands, in accordance with the preset
order.
❑ Once the item to be sent has been selected, the process is as follows:
 Press the key “I” for the following commands: close, in service, automatic, remote control, etc.
 Press the key “O” for the following commands: open, out of order, manual, local, etc.
 By pressing the key “DES” (if the item has maintenance configured), the command will be run, in accordance
with the item's status – if it is set to maintenance, the command will be “remove maintenance”, if it is not in
maintenance, the command will be “set to maintenance”.
If the command fails or if it can not be run due to a block, a small screen indicating the reason for the failure will be
displayed. This indication appears for 5 seconds, during which no operations can be carried out on the item.
❑ If the command is successful, no additional screen will be shown and the item's status will be refreshed.
❑ If it is in the control selection, only the “SEL”, <ESC> and “I, O, DES” keys are allowed.
The treatment of controls WITHOUT Preset Keys:
❑ To run a command, we must first select the item to be sent. To do so, and once we have selected the screen
containing the item to be sent, we must press  (Enter). The symbol of the item that has been configured to
priority 1 and which has an associated command will appear and begin to flash.
❑ By pressing the “(Left), →(Right)” keys, we scroll through the different “live points” with commands, in
accordance with the preset order.

User Manual 146
❑ Once the item to be sent has been selected, the process is as follows:
 Press the key “I” for the following commands: close, in services, automatic, remote control, etc.
 Press the key “O” for the following commands: open, out of order, manual, local, etc.
❑ If the command fails or if it can not be run due to a block, a small screen indicating the reason for the failure will be
displayed. This indication appears for 5 seconds, during which no operations can be carried out on the item.
❑ If the command is successful, no additional screen will be shown and the item's status will be refreshed to show
"normal".
❑ If it is in the control selection, only the <ESC>, (Left), →(Right) and “I, O” keys are allowed.
By pressing <ESC>, we exit the control selection, as we also do if we refrain from pressing any keys for a period of more than “10
sec”.
The measurements are displayed with the number of decimal points and digits preset with the configuration tool. The possible
situations that are covered when viewing a measurement are:
❑ Invalid: An '*' is placed in front of the measurement, there is no associated flashing. E.g.: * 25.3
❑ Outside range: '####' is displayed without flashing when the measurement’s value exceeds the maximum value for
the specified nº of digits and decimal points. E.g.: measurement value = 100 and number of digits = 2.
❑ Alarm: An 'A' is displayed in front of the measurement, with flashing, when the measurement exceeds the set
range. There is an upper and a lower limit. E.g.: If an alarm is activated when the upper limit is greater than 200 A,
the measurement will be displayed as follows: A 202.
Each of the measurements displayed in the graphic screens can be configured so that their values are referred to the primary or the
secondary.

User Manual 147
18.1.5 I/O pages

The device may be equipped with different types of cards, which are distinguished by the combination of inputs and outputs
grouped in 2 columns. Each card’s information is grouped in a page.
A text indicating the type of card, the address of the module assigned by HW and an indication of the current page number/number
of total pages, which is the same as that of the card, is displayed at the top of the screen.
An indication of a card failure is shown in the lower part of the screen. If the circle is filled, the card is in failure, whereas if it is
empty, the card is functioning correctly (Figure 57).The order of this type of screen is defined by the different card’s addresses –
the card with the lowest address is displayed first and the pages can be scrolled using the “ (Up),  (Down)” keys.
The digital I/O data are listed in 2 columns. Each column contains a graphic symbol (a circle), followed by the input or output text
and the corresponding number of terminals:
The digital signals are displayed as an empty circle, when disabled, or a filled circle, when enabled. In the event of an invalid signal,
an empty circle with a cross is displayed to represent a disabled status and a filled circle with an inverted cross is displayed to
represent an enabled status (Figure 58).
Figure 57 I/O Screen Figure 58 I/O Screen with card failure

User Manual 148
18.1.6 Event pages

The event screens display a chronological record of all the changes that take place in the signals that have been configured as
events in the display.
Each event’s presentation includes the date and time to the millisecond, a 29 character text and a 7 character acronym.
The texts to be displayed, as well as the signals’ identification, are set in attributes of the CID and may be modified using an
external tool.
The screen order is defined chronologically. Their display order goes from the newest to the oldest. Within each screen, the most
recent are shown at the top of the page and the oldest at the bottom.
We can scroll through the pages using the “ (Up),  (Down)” keys, going from the last page to the first, and vice-versa. The page
order runs from the first page, which has the most recent events, to the last page, which has the oldest events. The “ (Down)” key
is used to scroll from the first page to the following in increasing order, whereas the “ (Up)” key is used to scroll from the last page
to the previous pages.
Only the last 160 events are displayed in these pages.
The total number of pages and the number of the page currently displayed, as well as the number of events in the display, is shown
in the last row.
Treatment:
When accessing this screen for the first time, the most recent events are displayed. The “ (Down)” and “ (Up)” arrows are used
to scroll through the pages, as indicated above.
If new changes are registered whilst we are viewing the 1st page of this type of screen, the Display is refreshed accordingly and the
older changes are moved downwards.
When viewing any page other than the 1st page if new changes are registered, the Display will not be refreshed and the previous
data is shown. In such a case, a flashing, inverted video “NEW CHANGES” message is shown at the top of the page.
This indication is cleared when the most recent changes are viewed. To do so, we must go to the first screen.
Figure 59 Event Screen

User Manual 149
18.1.7 Protection event pages

The protection event screens display a chronological record of all the changes that take place in the signals that have been set as
such. Each protection event’s presentation includes the date and time to the millisecond, a 29 character text and a 7 character
acronym.
The texts to be displayed are defined in attributes of the CID. Signals are identified as protection events by means of the
corresponding enabling function in the corresponding settings node and by configuring the event masks. They can be modified
using the PC tool.
Figure 60 Protection event Screen
The screen order is defined chronologically. Their display order goes from the most recent to the oldest. Within each screen, the
most recent are shown at the top of the page and the oldest at the bottom (Figure 60). If the protection event list is empty, a text
indicating that the protection event queue is empty will appear.
We can scroll through the pages using the “ (Up),  (Down)” keys, going from the last page to the first, and vice-versa. The page
order runs from the first page, which has the most recent protection events, to the last page, which has the oldest protection
events. The “ (Down)” key is used to scroll from the first page to the following in increasing order, whereas the “ (Up)” key is
used to scroll from the last page to the previous pages.
Only the last 160 protection events are displayed in these pages.
The  (Enter) key is used to select the first protection event from the screen being viewed, whilst the “ (Up),  (Down)” keys are
used to scroll to the next protection event, with the following treatments:
❑ If, whilst at the bottom of the page, we press “ (Down)”, we are taken to the next page with the first selected
protection event, unless we are already viewing the last page, which case the display will not be changed.
❑ If we are in the protection event selected and we press “ (Up)” key, we are taken to the previous page, although
the last protection event remains activated, unless we are in the first page and in which case the display will remain
unchanged.
Once this protection event has been selected, we can press  (Enter) to view the page with the measurements associated to the
protection event. Use the “ (Up),  (Down)” keys to switch from one page to another if there is more than one measurements
page per protection event. These pages are browsed in a cyclical manner, going from the first to the last, and vice-versa, as
corresponds.
Use <ESC> to exit the screen displaying the measurements associated to the protection event. Within the protection events’
screen, the change is deselected by clicking on <ESC> once again.
The total number of pages and the number of the page is currently displayed, as well as the number of protection events in the
display’s queue, is shown in the last row.

User Manual 150
Treatment:
When accessing this screen for the first time, the most recent protection events are displayed.
The “ (Down)” and “ (Up)” arrows are used to scroll through the pages, as indicated above
If the appearance of new protection events is detected, a flashing, inverted video “NEW INC” (new protection event) message is
shown at the top of the page.
This indication is cleared when the latest protection events are viewed. To do so, no protection events must be selected and we
must go to the first screen. Once we have arrived at this screen, if we scroll back the first screen with the most recent protection
events to have been registered will be displayed.
18.1.8 Alarm pages

These screens emulate an alarm panel, displaying each alarm as a rectangle with a text inside. The page format is set and includes 2
columns containing 6 rectangles each. There will be a maximum of 15 alarm pages, i.e., a maximum of 180 alarms.
2 lines of 12 characters can be displayed within each rectangle. Each alarm’s texts, identification and the number of alarms are
configured using an external tool.
When in standby status, the text is displayed in a normal video with white background and, when enabled, in an inverted video
with a dark background.
When the alarm changes status, the signal’s text begins to flash and appears and disappears within the new status.
If the signal is invalid, the text will be displayed with a cross covering the entire rectangle. If the signal does not exist, the
corresponding alarm's gap will be displayed.
Use the “ (Up),  (Down)” keys to switch from page to another.
Individual acknowledgements of receipt are not issued for the alarms. Instead, it is possible to issue acknowledgement for all the
alarms displayed in the page that is being viewed. To do so, we must press  (Enter) in an active alarm page and the following
message will appear in a small screen:
Confirm receipt of all alarms of the page?
If we then press <ESC>, the message is cleared and no acknowledgment of the alarms is issued. If we press  (Enter), the message
disappears and an acknowledgment is issued for all the alarms displayed on the page.
An indication of the total pages and the number of the page displayed will appear at the top of the page.

User Manual 151
Figure 61 Alarm panel
18.1.9 Device status pages

The device status displays may differ depending on the model. Values may be referred to the primary or secondary.
NOTE: The measurements correspond to the fundamental frequency.
The different screens depending on the model samples of the device:
18.1.9.1 MDx, CDx, ZTx, CBx and BFx Models

There are 3 pages which describe the device status.
❑ Screen 1:
 Relay date and time.
 Frequency value.
 Type, module and angle of each of the unit’s 12 transformers.
❑ Screen 2:
 Direct, inverse and zero sequences of currents and voltages (module and angle).
 Total real, reactive and apparent power.
❑ Screen 3:
 Active table number (not available in CDx models).
 External power supply battery voltage.
 Phase and neutral thermal image value (only for MDx models).
 Restricted Earth value (only for MD0, MD2, TDx and LDx models).
 Maximeter value for each current and voltage phase (not available in CD0 model).
 Device temperature.
 Measures reactive power (only for CB model).
NOTE: The CD0 model only has a single screen with the following information:


User Manual 152
Figure 62 Device Status page 1, page 2 and page 3
18.1.9.2 TDx Models

❑ Screen 1:
❑ Screen 2:
 Maximeter value for each current phase of each winding
 Maximeter value for each current and voltage in TD0 model
❑ Screen 3:
 Active table number (not available in CDx models).
 Phase and neutral thermal image value (only for MDx models).
 Restricted Earth value (only for MD0, MD2, TDx and LDx models).
 Maximeter value for each current and voltage phase (not available in CD0 model).
 Measures reactive power (only for CB model).
❑ Measurements screen (4)
 Differential measures
 Restraint measures
 Differential 2º harmonics measures.
 Restricted Earth values.
❑ Measurements screen (5)
 Direct, inverse and zero sequences of currents (module and angle) of each winding.
 Direct, inverse and zero sequences of voltages (module and angle) in TD0 model.

User Manual 153
Figure 63 Device Status page 1, page 2 and page 3
Figure 64 Device Status page 4 and page 5
18.1.9.3 LDx Models

❑ Measurements Screen 1:
❑ Measurements screen 2
 Direct, inverse and zero sequences of currents and voltages (module and angle).

User Manual 154

❑ Measurements Screen 3:
 Active table number.
 Phase and neutral thermal image value.
 Maximeter value for each current and voltage phase.
❑ Measurements screen (4) Figure 64
 Differential measures
 Restraint measures
 Differential 2º harmonics measures
❑ Terminal Measurements screen (5)
 Synchronized measurements all terminals.
NOTE: The LD3 model does not have voltages and power.

User Manual 155
18.1.10 Fault pages

These pages display the last 20 fault reports filed by the protection.
These screens are divided into two levels. The first level displays a list of the most recent faults, as well as the fault number and the
fault trip date for each case (Figure 66). The total number of pages and the number of the page being displayed is shown at the
top, whilst the number of faults stored in the unit is shown in the last row.
If the fault list is empty, a text indicating that the fault queue is empty will appear (Figure 65).
The faults are ordered from the most recent or latest (Fault nº 1) to the oldest.
Figure 65 Empty fault list Figure 66 Fault list
The second level displays all the information related to the fault, organized in several pages. The page is displayed with the number
of the fault being displayed, as well as an indication of the number of the current page and the total number of pages per fault.
Use the “ (Up),  (Down)” keys to navigate through the first level screen. The page scroll is cyclical - when the end of the page is
reached we are taken to the next first level page and we are taken from the first page to the last page and vice-versa in accordance
with the key we press.
By pressing  (Enter), we access the second level of the selected fault. Use the “ (Up),  (Down)” keys to move between the
second level screens pertaining to a single fault. Use <ESC> to return to the first level page.
The values can refer to the primary or to the secondary. It is allowed to enable / disable the treatment to automatically display the
last fault on the display from the Configuration / Settings section of the display configuration tool.
Each screen’s content will be displayed as follows:
The contents of each screen may differ depending on the model, then the different possibilities:
18.1.10.1 MD, ZT, BC, BF and PB Models

There are 4 screens with data for each fault:
❑ Start Screen, which includes fault’s data.

 Date and time: Indicates the date in the “dd/mm/yy hh:mm:ss.ms” format. There are three dates:
 Start of the fault (first unit picked up).
 Trip (first unit tripped).
 End of fault (when the trip signal disappears).

User Manual 156
 Frequency in the moment of the fault.

 Pick up and trip types: Summary of the fault with the 3-letter code formed by combinations of the characters
A, B, C, N, NS and G (if tripped by a phase, neutral, sensitive neutral or ground), RTP (teleprotection), IF (phase
overcurrent), IN (neutral overcurrent), D (current unbalance), VO (zero-sequence overvoltage), HV
(overvoltage), LV (undervoltage), RTP (teleprotection), DT (transferred trip), DP (pole discordance), IT (thermal
image). Example: AC is a two-phase fault in phases A and C.
 Pick up type.
 Trip type.
 Distance: distance to the fault.
 Rf: resistance fault.
 LOC: locator code.
 Thermal image upon trip. The thermal image is indicated as a % of phases and neutral.
 Breaker. Indicates breaker monitoring data upon the fault:
 Open current. For each phase, indicates the current value upon the trip.
 Sigma ki. For each phase, indicates the sigma ki2 value.
❑ Fault screen, with the text “Fault information (I)”.
Figure 67 2nd level Fault Screens, page 1 and page 2
 Pre-fault and fault. Indicates the values measured before the fault and upon the fault. This screen displays the
following values:
 Transformer measurements <Trafos>. It indicates the measurement in the module and the angle of
each transformer.
 Restricted Earth value.
❑ Fault screen, with the text “Fault information (II)”.
following values:
 Sequences. Indicates the measurements in the module and the angle of the current sequences (I0,
I1 and I2) and the voltage (V0, V1 and V2).
 Power. Indicates the measurements of the total real, reactive and apparent powers.
❑ Tripped units screen, displays the picked up and the tripped units.

User Manual 157
Figure 68 2nd level Fault Screens, page 3 and page 4
NOTE: only the first 7 picked up and tripped units are displayed. If the number is greater than 7, a text appears at the bottom of
the screen indicating that there are more picked up units.
18.1.10.2 TDx Models

❑ Start Screen, which includes fault’s data.

A, B, C, N, NS and G (if tripped by a phase, neutral, sensitive neutral or ground), DIF (differential), RG (restricted
earth), IF (phase overcurrent), IN (neutral overcurrent), D (current unbalance), VO (zero-sequence
overvoltage), HV (overvoltage), LV (undervoltage), v/f (overexcitation v/f), IT (thermal image). Example: AC is a
two-phase fault in phases A and C.
 Pick up type.
 Trip type.
 Thermal image upon trip. The thermal image is indicated as a % of phases and neutral of each winding.
❑ Fault screen, with the text “Fault information (I)”
 Breaker. Indicates breakers monitoring data upon the fault of each winding:

following values:
 Transformer measurements <Trafos>. It indicates the measurement in the module and the angle of
each transformer.

User Manual 158
Figure 69 2nd level Fault Screens, page 1, page 2 and page 3
❑ Fault screen, with the text “Fault information (III)”.

following values:
 Differential current measure
 Restraint current measure
❑ Fault screen, with the text “Fault information (IV)”.
following values:
I1 and I2) of each winding.
 Sequences. Indicates the measurements in the module and the angle of the voltage (V0, V1 and V2)
in TD0 model.
Figure 70 2nd level Fault Screens, page 4, page 5 and page 6

User Manual 159
18.1.10.3 LDx Models

❑ 0Start Screen, which includes fault’s data.

A, B, C, N, NS and G (if tripped by a phase, neutral, sensitive neutral or ground), DIF (differential), RG (restricted
earth), IF (phase overcurrent), IN (neutral overcurrent), D (current unbalance), VO (zero-sequence
overvoltage), HV (overvoltage), LV (undervoltage), v/f (overexcitation v/f), IT (thermal image). Example: AC is a
two-phase fault in phases A and C.
 Pick up type.
 Trip type.
 Distance: distance to the fault.
 Rf: resistance fault.
 LOC: locator code.
 Thermal image upon trip. The thermal image is indicated as a % of phases and neutral.
 Breaker. Indicates breaker monitoring data upon the fault:
❑ Fault screen, with the text “Fault information (I)”

Transformer measurements <Trafos>. It indicates the measurement in the module and the angle of each
transformer.
following values:
I1 and I2) and the voltage (V0, V1 and V2).
❑ Fault screen, with the text “Fault information (III)”.
following values: Differential current measure and Restraint current measure.
 Restricted Earth value.
18.1.11 Measurement pages

There are 5 screens displaying the unit’s rms measurements referred to the primary (not available for devices without measure
module, for example CD0).
NOTE: Certain wiring diagrams have invalid measurements that do not exist. They are represented by “---“.

User Manual 160
❑ Measurements screen (I)

 Module and angle of each of the unit’s 8 transformers and phase to phase voltages.
❑ Measurements screen (II)
 Direct, inverse and zero sequences of currents and voltages (module).
 Frequency.
❑ Measurements screen (III)
 Power by real and reactive phase and apparent rms.
 Power factor per phase.
❑ Measurements screen (IV)
 Total real, reactive and apparent rms power.
 Total power factor.
 Real and Reactive Energy.
❑ Measurements screen (V)
 The harmonic distortion (%) of the 8 transformers’ measurements.

User Manual 161
Figure 71 Screen 1 Figure 72 Screen 2 Figure 73 Screen 3
Figure 74 Screen 4 Figure 75 Screen5
18.1.12 Menu to other screens page

This screen allows an access menu for the other types of screen that have not been given the consideration of main screens to be
displayed. We can group little-used screens within this screen and thus reduce the size of the main loop, making the movement
between those screens that are considered the most important quicker.
The content of this screen is set using the external configuration tool. Screens that are included in the main screen list cannot be
included in this menu.
The image below shows the following types of screen grouped in this screen: Events and Faults.

User Manual 162
Figure 76 Other screens
18.1.13 Shortcut menu page

This screen appears when we press “R”.
It contains those commands that can be given to the unit without having to enter a Password. The commands will vary in
accordance with the unit’s family.
Some examples are given below.

❑ Recloser command.
❑ Bank automatism command (for unit’s with a capacitor bank).
❑ .....
By pressing “R”, this page appears showing the first selected command. By clicking on the “ (Up),  (Down)” keys we can move
between the commands. By pressing “ (Enter)”, the selected command is run.
Figure 77 Quick access menu

User Manual 163
18.2 CONTROL AND PROTECTION MENUS PAGES
18.2.1 Operation of the menus

These screens enable us to view and modify the control and protection settings values. They consist of several levels of menus and
sub-menus.
18.2.1.1 Access to settings Menus

By pressing <MENU> from any of the other types of screen, a screen such as the one shown in Figure 87 will appear and
request that a password be entered.
Figure 78 Password request screen
We can access the menu pages with either viewing or modification permissions.
If we enter the correct password and press  (Enter), we will have permission to change settings. The “♦” symbol will appear in
the bottom left of the screen, as will the text “CHANGE SETTINGS”. However, if we press <ESC>, we will only be permitted to
consult the settings. Further more, a text indicating “VIEW SETTINGS” will be shown. The <ESC> key will function even when
some of the password’s numbers have been entered.
For more information, consult the point 4.2 of the Password Management section in this manual.
18.2.1.2 General operation

We can access the start menu screen by pressing <MENU> from any of the other pages described in the preceding paragraphs.
To exit the menus pages from the start page we must press <MENU> or <ESC>.
To move from a menu to a submenu we must select the menu that we want to explore and press  (Enter). To return to the
previous menu, we must press <ESC>. The <MENU> key enables us to return to the start menu from any submenu.
The  (Up),  (Down) keys can be used to change a menu's active line. If all the menu’s options can be displayed on the screen,
only the active line is changed when we change line. On the other hand, if not all of the menu’s options can be displayed on the
screen at the same time and the cursor is situated over the first or the last of the screen's menus, the menu will scroll up or
down, in accordance with the key used.
An indication of the number of the item selected from the total number of items in the menu on the screen currently displayed
is shown in the bottom right of the screen.
In the settings screens when a node does not exist in the cid an '*' before the text is displayed, indicating that the
node is disabled.

User Manual 164
The display change active table indicated by the following "(A)" the active table at that time.
Figure 79 Initial Settings Menu
18.2.1.3 Settings change operation

By pressing  (Enter) on an item from a settings menu screen that has no submenus, the settings changes screen will appear
(Figure 80). This screen displays the data corresponding to the first 6 settings. The selected setting can be modified using 
(Up),  (Down).
If all the node’s settings can be displayed on the screen, only the selected setting is changed when we change setting. On the
other hand, if not all of the menu’s options can be displayed on the screen at the same time and the cursor is situated over the
first or the last of the screen's settings, the settings will scroll up or down, in accordance with the key used. To return to the
menu screen, we must press <ESC>.
If the node is disabled, it is not allowed to modify settings and the display of the settings would be similar to the one you have
when entering the settings only mode. In the last row the text "DISABLED NODE" is displayed.
The following data can be seen on this screen:
❑ The following will appear at the top of the screen:

 Description of the settings node.
 Name of the settings node in IEC 61850.
 Current table (for settings which have the possibility of multiple tables).
 The number of the selected setting and the total number of the node’s settings.
❑ There are 3 lines for each setting, indicating the following:
 Description of the setting.
 Name of the setting in IEC 61850 and its corresponding value.
 New value of the setting. When this screen is accessed for the first time, the current value and the new value
coincide.
❑ The “VALIDATE PARAMETERS?” text appears in the last line. When selected and after pressing  (Enter), all the
changes to the screen's settings are validated. Until we press  (Enter) with the last line selected the changed
settings will not be validated.
❑ WARNING: If the user only has viewing permissions, the last line will not appear on the settings change screens.

User Manual 165
Figure 80 Settings change screen Figure 81 Setting Validated Screen
By pressing <ESC> after modifying a setting in the page, a confirmation message indicating that the user is about exit without
saving the settings in the CID appears:
Exit without changing settings?
Thus, by pressing  (Enter) we exit the screen and all the changes made so far in that menu are cleared. If we press <ESC> when
the message appears, we remain where we were.
By pressing  (Enter) after having modified one of the page's settings, another window appears. At this point, the user has 2
options:
❑ Wait until the CID modification process is completed with the new settings. At this point there are 3 possible
situations:
 If the modification is carried out successfully, a “Changing the settings OK” text will appear (Figure 81).
 If an error occurs during the CID modification process, an “Error in changing settings” text will appear.
 If a time out failure occurs whilst saving the modified settings, a “Time out in changing settings " message will
appear.
❑ Press  (Enter) and return to the settings change screen without the assurance of having modified the CID.
18.2.1.4 Settings Types

By pressing  (Enter) on one of the items that enables settings to be changed (the settings are text strings only be
displayed), and providing that the user has modification permissions, one of different types of small window will appear:
18.2.1.4.1 Option Type

By pressing  (Enter) on a setting of this type, a small window (Figure 82) displaying the following data appears:
❑ Setting name in IEC 61850.

❑ Setting description.
❑ Current setting value.
❑ New value of the setting. When this screen is accessed for the first time, the current value and the new value
coincide.
❑ The number of the current option from among the options available

User Manual 166
Using the  (Up),  (Down) keys, we can move through the different options in a circular manner, that is, when we reach
the last option we are returned to the first option. The selection option is chosen by pressing  (Enter). To exit without
selecting, press <ESC>.
Figure 82 Small screen for modifying OPTION type setting
18.2.1.4.2 Numeric Type

These can be changed using the numeric keys. The number is validated by pressing  (Enter), whilst <ESC> is used to cancel
and start again. The following data is displayed in each small window:
❑ Setting name in IEC 61850.

❑ Setting description.
❑ Current setting value.
❑ The setting’s new value. This field, which is empty, is where the value of the new setting entered via the keyboard
will be displayed.
❑ Maximum setting value.
❑ Minimum setting value.
❑ Setting step or increase.
The desired value is entered directly. The digits are entered from left to right. For example, to enter the number 2345, we
must successively press 2, 3, 4, 5,  (Enter).
The entered value is checked in order to ensure that it meets the maximum, minimum and step restrictions. Should it fail to
meet any of these restrictions, the “INVALID VALUE” text is shown. This text disappears when a number key is pressed.
There are 2 possibilities within this type, depending on the number, decimal or integer format.
Decimal: See Figure 83.
Integer: There are some integer type settings whose value is a signal number. In such cases, the “NOT DEFINED” text (Figure
85) indicates that this setting has no associated signal. If we wish to associate a signal, we must enter the desired signal
number with numeric keypad and press  (Enter).

User Manual 167
Figure 83 Small screen for modifying DECIMAL Figure 84 Small screen for modifying INTEGER Figure 85 Small screen for modifying INTEGER
type setting type setting type setting
18.2.1.4.3 Date Type

Equivalent to a numeric, although the numeric data entered are successively allocated in blocks of two to Day, month, year,
hour, minute, second. When the seconds have been entered, no further data can be entered until we have press  (Enter)
or <ESC> (the latter key deletes the data entered. If no data has been entered, we exit the settings modification). The
format displayed on the screen is: Day/Month/Year Hour:Min:sec
2 digits must always be entered for year, month and date. This means that in order to enter “1” we must enter “01”.
If the user enters an incorrect value, the last character entered can be deleted with the “” (Left) key.
To exit without saving any changes, press <ESC>.
Once the correct data have been entered, press  (Enter) to check that the values entered are valid. In the event of an
error, an “INCORRECT DATE” text will be shown. If the data are valid, no windows will be shown.
Figure 86 Unit date and time setting screen

User Manual 168
18.2.2 Password management
18.2.2.1 Changing the Settings Menu Password

The password may contain between 4 and 8 digits. The password is 1357 by default.
When we press a numeric key within the password screen, each keystroke will be considered part of the password and will be
indicated in the display with “*”. When we have entered between 4 and 8 characters and pressed "Enter", the data entered will
be validated against the unit’s password. If the password entered is incorrect, a warning text will be displayed.
Pressing <ESC> enables us to access the settings menus with viewing only permissions. If we enter the correct password we will
be able to view and modify. <ESC> will function even when certain of the password’s numbers have been entered, i.e., if we
press <ESC> while we are entering the password we will access the menu with viewing only permission.
The user can change the password, providing that he or she knows the former password.
You will be asked to type the password twice before changing it. The password numbers will appear hidden as they are entered
(the “*” will appear for each number entered). Once the first password has been entered, press  (Enter) and enter the second
password. Once the second password has been entered, press  (Enter) and the password will be changed (providing the two
passwords entered are the same). As with the numbers, they are entered from left to right.
Figure 87 Password modification screen
18.2.2.2 Changing FTP and SFTP Passwords

The FTP or SFTP password modification screen is accessed via the settings menu. This screen shows a virtual keyboard with
numbers from 0 to 9, the alphabet in uppercase and in lowercase.
Operation
❑ We must use the  (Up),  (Down),  (Left) and → (Right) keys to navigate around the virtual keyboard,
whilst  (Enter) is used to confirm the selected keyboard field.
❑ We must enter the old password and select the "Validate" field before finally pressing  (Enter).
❑ We must then enter the new password and select the "Validate" field before finally pressing  (Enter).
❑ A small window showing the result of the password modification (OK or the cause of the failure) will be
displayed.
If the user enters an incorrect value, must leave and enter the screen and start again.

User Manual 169
Figure 88 FTP Password modification screen
18.2.2.3 Commands management

18.2.2.3.1 Commands from the keyboard
There is a new settings menu within the Password screen to set the handling of commands from the keyboard. These
settings can only be changed from the display. There are 2 settings:
❑ Enabling key request to execute a command.

❑ Maximum time in which the entered password is valid, after this time you must enter the password again (time in
seconds).
Operation:
In graphic displays when you press the select key command the small screen that will ask the key display, after entering the
correct password will have some time to execute orders. After this time, the execution of orders will not be allowed. The
function keys have the same function.
The key settings menu and commands execution is the same, if you access the settings menu with the correct password will
be able to execute commands from the function keys without re-enter the password.
On the other hand, if you accessed the settings menu but only with permission from view settings, if you want to run a
command from the function keys will have to enter the password, same operation as if they were in a main menu screen.
18.2.2.3.2 PacFactory commands

From firmware version 6.1.18.5, the device implements the possibility of receiving remote control commands from the
pacFactory software tool as an alternative control channel to the telecontrol center.
The device considers the origin of these commands as "Remote" and applies the configured Local / Remote command
hierarchy.
For security reasons this functionality is disabled in the factory configuration and can only be enabled or disabled from the
local HMI of the device. It is not possible to modify the configuration by communications or from the pacFactory
configuration tool.
The function is configured by the setting "pacFactory Commands" ("YES": enabled / "NO": disabled).
If the device has this functionality enabled, the pacFactory configuration tool will detect it at the beginning of the
communication and enable an access to the command window in the "Tools -> Sending commands" menu.

User Manual 170
18.3 NETWORK CONFIGURATION
From the display it is possible to view and modify the network parameters of the equipment. For this there are a series Network
configuration menus.
Figure 89 Figure 90
The previous figures show 2 examples of possible situations:
❑ Figure 89 shows that the equipment has a network configuration with the 3 independent and enabled interfaces.
❑ Figure 90 shows that the device has a network configuration of ETH1 and ETH2 in Link Redundancy mode, and ETH1 has
been disabled.
18.3.1 Ethernet Configuration

❑ Ethernets Viewing
When accessing the data of an interface from the main menu of network configuration, a screen similar to Figure 91 will be
displayed, where the list of ips is presented, and 2 additional menus: Create new ips and enable or disable the interface It is
showing.
Figure 92 shows how the network interface, IP address, netmask, MAC address, and status link parameters are displayed
on the display, indicating whether the network cable is connected.
Depending on the configuration of the back ethernets the representation of some data of these interfaces varies:
ETH2 link: When a device is configured as a switch or link redundancy in the Network configuration screen on the ETH2
interface line, the text of Switch or Link Redundancy. The network parameters are the same as the ETH1 interface except
the link. For this reason, the ETH2 link status is displayed on the ETH1 screen.

User Manual 171
Figure 91 Figure 92 Figure 93
❑ Ips Editing
From the display screen (Figure 92) and having permissions to change settings by pressing the  (Enter) key, the screen in
Figure 94 shows the current data and a second row where you can enter the new values. Use the  (Up),  (Down) keys to
navigate the IP and MASK fields in a circular way, that is, when you reach the last, you return to the first one.
Figure 94 Ethernet parameters setting changes screen
To exit, press <ESC>.
Only the IP and MASK fields can be modified. If you want to change any of these fields, you must activate the special
mode keypad to do this, press the <MENU> key. For more information, consult the point 1.2.1 in this manual.
error, a small screen displaying the cause of the error will be shown.
❑ Ips Removing
From the ip display screen (Figure 92) you can delete the ip that is being displayed by pressing the (Left) key.

User Manual 172
❑ Creating new ips

Once on this screen (Figure 95) you can use the following keys:
 For information on how to enter the numbers, refer to the Functioning of the menus in this manual.
 The  (Left) key is used to delete the last entered value.
 The  (Up) and  (Down) keys to move between the IP line and the MASK line.
 The <ESC> key is used to exit the previous menu.
 The  (Enter) key is used to apply the change.
Figure 95 Figure 96
❑ Disabling / Enabling Ethernets

Once on this screen (Figure 97 and Figure 98) you can use the following keys:
 The  (Up),  (Down) and  (Left) keys to change the setting value.
 The <ESC> key is used to exit the previous menu.
 The  (Enter) key is used to apply the change.

User Manual 173
Figure 97 Figure 98
When an ethernet is disabled, all ips associated with that interface will be deleted. The DISABLED text will appear in the
Network Setup menu. If we access the menu of this interface will be shown the screen of Figure 99, with the ip 0.0.0.0.
If you want to enable again, change the setting to YES and then edit the IP1 to add the desired ip and mask
❑ Network configuration screen when there is a failure in the display configuration.

When there is a fault in the configuration of the display, there is the possibility to see the network configuration of the
equipment, pressing the  (Enter) key alternates the display of the error message and the screen with the network
configuration. The network configuration screen is shown below.
Figure 99
❑ Restore factory settings

At the end of the Network Configuration menu there is an option to restore the factory settings of the ethernets.

User Manual 174
18.3.2 Gateway Configuration

From the display it is also possible to view, add, modify and delete the gateways that are configured on the device. Up to 10
gateways can be configured, ONLY 1 of which can be a default gateway.
The following figures show the screens with the different interfaces for the unit’s network and gateways. We can see that a default
gateway with IP address 192.169.183.4 and a gateway with IP address 192.168.183.1 have been configured. The remaining
gateways have not been configured.
❑ Viewing a Gateway
If we select Gateway 2 and press  (Enter), the following screen appears (Figure 101) showing the Gateway’s data values
and a legend at the bottom with the different options available to the user.
Figure 100 Network Configuration Figure 101 Gateway display screen Figure 102 Default Gateway edition screen
If we select Gateway 1 and press  (Enter), the default gateway screen appears (Figure 102).
❑ Editing or creating a Gateway

If we press  (Enter) in the Gateway configuration screen and we have permission to change settings (having entered the
correct password into the password screen), the Gateway edition and creation screen will appear with the current data and
a second row into which the new values can be entered.
The following situations may arise when configuring a Gateway:
❑ Gateway Not Configured

 To add a default Gateway, we only have to complete the GATEWAY field (the Gateway IP address) and press 
(Enter). If not, an error will occur.
 To add a Gateway with a specific network destination, we must complete the 3 fields and press  (Enter). If
not, an error will occur.
❑ Gateway Configured
 To edit a default Gateway (Figure 102), we only have to modify the GATEWAY field (the Gateway’s IP address)
and, once the desired value has been entered, press  (Enter) for the change to become effective.
 To edit a Gateway with a specific network destination, we change the desired parameter(s) and press 
(Enter). Any parameters that are not modified will retain the current values.
To add a new Gateway, select a non-configured gateway, for example Gateway 3, and press  (Enter).
This screen shows the values of the Gateway’s 3 fields as non-configured. In such a case, we can only exit or edit (add) the
Gateway. By pressing  (Enter) again, the Gateway edition/creation screen will be displayed.

User Manual 175
The  (Up),  (Down) keys are used to move between destination IP address, destination network mask and the Gateway IP
address fields in a circular manner. This is not possible in the default Gateway, which has a single editable field.
To exit without saving any changes, press <ESC>.
If we want to enter the Gateway with the destination IP 10.15.1.6, Gateway mask 255.255.255.255 and Gateway IP address
192.168.182.252, you must activate the special mode keypad to do this, press the <MENU> key. For more
information, consult the point 1.2.1 in this manual.
error, a small screen displaying the cause of the error will be shown.
The screen will display the new configuration and the new Gateway introduced.
NOTE: If a default Gateway is configured, the last Gateway will ALWAYS be displayed, even if more gateways with a specific
network destination are added.
Figure 103 Gateway parameters setting changes screen
❑ Deleting a Gateway
If we press the “” (Left) key in the Gateway configuration screen and we have permission to change settings (having
entered the correct password into the password screen), the Gateway that is being displayed will be deleted.

User Manual 176
18.4 OTHER SCREENS
18.4.1 Contrast setting

To access the contrast setting screen we must press “0” and “9” at the same time in a screen that is not within the unit's settings
menu. Once we have pressed these two keys, the following image will appear in the display:
Figure 104 Contrast setting screen
If we then press  (Up) the contrast’s intensity will increase, and if we press  (Down), the intensity will decrease. To exit this
screen, press  (Enter).
18.4.2 USB treatment

When the user inserts a USB key, a small window will appear in the display indicating that a USB device has been detected and the
USB treatment will begin.
Figure 105 USB detected Figure 106 Remove the USB device

User Manual 177
Once the treatment has terminated, the following window will appear in the display indicating that we can remove the USB device.
NOTE: If the USB device is not removed within 5 seconds, the small screen will disappear and the display will return to the previous
screen.
Added a new menu of settings in the Password screen to set the USB treatment, this setting can only be changed from the display.
The setting will have 3 possible values:
❑ Disabled: The USB treatment is not available.

❑ With password: The USB treatment is available but needs the introduction of the key settings menu.
❑ Without password: The USB treatment is available without having to enter the password.
18.4.3 System Information

In this menu the information concerning Product Information and detailed version of the device.
The content of each submenu is:
❑ Product information: commercial computer code and the serial number of the CPU is displayed.
❑ Device versions:
 Versions of the CPU and the boards of the device are displayed.
 Sampled values firmware version. Only in models with sampled values modules.
 Micros expansion boards versions (CPU and HMI).
 Logic and CID versions.
❑ Last updates: last 18 updates are shown, for each update there is a record with the following data:
 Date and time of the update.
 Filename update.
 Result of the update.
❑ Last CIDs loaded: The display will show the latest cids loaded from the device boots where the following
information is displayed:
 Date and time.
 Cid name.
 Result validation.

User Manual 178
18.4.4 CID validation

Messages relating to the receipt and processing of a new CID on the device are displayed in a small window, the operation is as
follows:
❑ After a new CID give the device a small window indicating that you are validating the CID is displayed. Throughout
the process of validation when any key is pressed, the window disappears and you can access the different
menus display.
❑ Once the validation process resulting CID (CID Validated / CID unvalidated) is indicated in a new window, which will
remain on the display until you press any key or two minutes have elapsed.
Messages received new setting display is visualized between the windows and the window CID validating the result.
18.4.5 Security Logs

Are available which record user actions from the keyboard / display, such as:
❑ if the password setting menu or the key is modified FTP

❑ If the password is correct or incorrect
❑ Whether to enable / disable Enabling Ethernet ports
❑ If there is a change in the network configuration
18.4.6 Test Screens

There are 2 test screens on your device for digital outputs and programmable LEDs. To enter these screens need to have entered
the correct password to enter the settings menu.
The output test screen is in the Setup menu of GGIO cards. It defines the different cards and display equipment shown to modify
the time setting output activation.
Once access to one of the cards all outputs and the corresponding connection is. To activate the desired output is only necessary to
select and press  (Enter).
Pressing  (Up) or  (Down), keys allow to select different outputs. To return to the previous menu, press the '<ESC> key.

User Manual 179
Figure 107 Digital Output Test Figure 108 GGIO1 Test Figure 109 Leds Test
The LED screen test is in the I/O/Leds configuration menu.
To activate the desired LED is only necessary to select and press  (Enter) key. Pressing  (Up) or  (Down), keys allow to select
different led. To return to the previous menu, press the '<ESC> key.
18.4.7 Other Communications Menu Screens

The following submenus are available within the Communications menu:
❑ Network Configuration: mentioned in its corresponding section.
❑ PRP / HSR / Sw configuration: the ethernet corresponding to PRP, HSR or switch is configured (only available in models
with redundancy module PRP/HSR/Switch mode).
❑ Process Bus: shows the information of ethernets 3 and 4 if they are available (only available in models with sampled
values subscriptions).
❑ Communications protocols: a series of slave / server and master protocols are available depending on the model of the
equipment.

User Manual 180
WEB APPLICATION 
19. WEB APPLICATION
19.1 INTRODUCTION
This document describes the features and capabilities of the Web Application, which is supplied within the firmware and allows to set
up and monitor the target IED.
The Web Application has been built in order to be responsive, HTML5 and CSS3 compliant and as lightweight as possible. It is supported
by the following browsers and versions:
❑ Google Chrome version 40.0.2214 or higher.

❑ Mozilla Firefox version 35.0.1 or higher.
❑ Internet Explorer version 10 or higher.
19.2 WEB APPLICATION LOGIN
First, the IP address of the IED must be entered into the browser's address bar in order to load the login page, i.e.: http://100.0.0.1.
19.2.1 Login
The login page needs a username and its password to login.
There are two users defined by default: a management user and a read-only user. The main difference between them is that
management user is able to modify parameters while read-only user is not. However, when a user with management permissions
logs in, it is asked whether he would like to login with management permissions or with read-only permissions. The corresponding
user name and passwords are the following by default:
Management user: user name admin and password modifica.
Read-only user: user name consulta and password consulta.

Manual de usuario 181
WEB APPLICATION 
When a management user tries to login, if there is already a management user logged in, the new user will be asked whether to log
in as read-only user or throw away already logged user.
Once the login has been successful the web page starts to load several tabs described below.
19.3 TABS
The main tabs are the following:
❑ Reports
❑ Settings
❑ Maintenance
❑ SW/Configuration
❑ Logout
19.3.1 Reports
The following subtabs are displayed in this tab:
❑ Status
❑ Events
19.3.1.1 Status
In the Status tab real-time information about measures and signals is shown. It is possible to read this information periodically or
each time the read button is clicked.
In the Measurements menu, the main measures taken in the secondary are shown.

WEB APPLICATION 
In the Signals menu, the most important signals regarding IED status, protection units, input and outputs status, etc. are shown.

WEB APPLICATION 
19.3.1.2 Events
In this tab, the list of events recorded by the IED can be displayed and a compressed file with all the events can be downloaded.

WEB APPLICATION 
19.3.2 Settings
In this tab, it is possible to read and change the settings of the IED.
The settings are arranged in menus regarding their functionality and they are read from the IED according to these menus. At the
bottom of the page there are three buttons in order to read settings, erase changes and send changes to the IED.
The settings are displayed as tables where the first column is the description of the setting, the second column is its value in the IED
and the last column is its value in the web. The background color of each setting's row changes according to its value. If the value in
the IED and the value in the web do not match the background will turn into yellow. On the other hand, if the value in the web is
not valid the background will turn into red.
In addition, it is possible to change the active table and view the value of each setting for every table.

WEB APPLICATION 
19.3.3 Maintenance
This tab contains the following tabs:
❑ Communications
❑ Users
19.3.3.1 Communications
The following menus are available:
❑ Synchronization. It is possible to synchronize the IED with the desired date and time.
❑ IP Network configuration. It allows to configure the IED's IP addresses and static routes configuration
❑ IP Network Tools. It is possible to execute a ping command from the IED and view IED's actual IP configuration and
routing tables.

WEB APPLICATION 
19.3.3.2 Users
In this tab, detailed information about current active sessions logged into the web is shown.
Additionally, it is possible to change username and password.
19.3.4 SW/Configuration
The SW/Configuration tab contains the following tabs:
❑ Configuration
19.3.4.1 Configuration
In this tab it is possible to load the configuration file.

WEB APPLICATION 
19.3.5 Logout
This tab is to end the session in the web.

DNP PROTOCOL 
20. DNP PROTOCOL
20.1 INTRODUCTION
The device provides a DNP interface to act as RTU and to communicate with a DNP master (for example a remote control station).
The communication can be selected for a serial line or via Ethernet, using encapsulation by means of the TCP/IP protocol.
Below are described the following topics:
❑ Protocol configuration settings

❑ Protocol configuration tables for digital signals, measurements, counters and commands (which are configured with the
software configuration tool)
❑ Implemented Device Profile and object table.
20.2 CONFIGURATION SETTINGS
The protocol has the following configuration settings:
❑ Enable protocol:
 Yes
 No
❑ Slave address: DNP slave address of the device. Value between 0 and 65532.
❑ Master address: DNP master address of the master device. Value between 0 and 65532.
❑ Port Number: This setting enables the selection between the available communication channels:
 Disable
 COM1
 COM2
 COM3
 COM4
 COM5
 COM6
 Ethernet 1
 Ethernet2
❑ Comm speed (bauds): This setting enables the selection of the serial baud rate.
 600 baud
 1200 baud
 2400 baud
 4800 baud
 9600 baud
 19200 baud
 38400 baud
 57600 baud

DNP PROTOCOL 
❑ Parity: Enables the selection of the parity type to be used in transmission. The recommended default value is 0 (without
parity), as indicated by the DNP protocol.
 None
 Even
 Odd
❑ Number of Stop bits: Enables the selection of the number of stop bits.
 1 Bit
 2 Bit
❑ Communication control: Enables de selection of the communication control type.
 Normal
 Fixed + DCD
 RTS
 RTS+CTS
 RTS+CTS+DCD
 RS485
❑ Min. respond delay (ms): Waiting time for the activation of the RTS and the transmission of a message after the reception
of a message. Value between 0 and 1000.
❑ CTS max delay (ms): Waiting time for the CTS activation after the RTS activation. Value between 0 and 1000.
❑ Carrier stabilization (ms): Waiting time for the transmission of the message after the CTS detection in order to allow the
carrier stabilization. Value between 0 and 1000.
❑ RTS drop-off time (ms): Waiting time for the RTS deactivation after the message last byte transmission.
❑ ACK delay time(ms): Timeout for Link Confirm. Value between 0 and 1000.
❑ Need time delay (m): Waiting time in minutes that must elapse before the validity of the clock is checked after receiving a
synchronization or start up message. If it is invalid, synchronization is requested to the master. Value between 0 and 10.
❑ Permission to synchronize: Synchronization permission from control centre.
 Yes
 No
It is used to configure the synchronization source when there are several available.
❑ Local time offset (h): Local offset for the time.

❑ Communication fail T.(min): Waiting time in minutes without receiving any valid measure before indicate communication
failure. Value between 0 and 10000 minutes.
❑ Data link confirm: Indicates if confirm is requested at the connection level. The value must be set to NO for TCP/IP.
 NO
 YES
❑ Max. App Fragment Size: Maximum number of bytes in an application message. Value between 512 and 3072.
❑ Freeze time counters: : Indicates if the counters are frozen with or without time. Only acts when zero variation is
requested.
 NO
 YES
❑ Default Status: Indicates whether the digital signal objects, measurements and counters are sent with status or without
status in messages sent in response to requests in which variation is not specified. Also valid for responses to class 0
requests. The bits have the following meanings:

DNP PROTOCOL 
Bit Value
0 Send all with status
1 Send digitals with status
2 Send measurements with status
3 Send counters with status
4 Send frozen counters with status
Bin. output status default: Indicates whether the reply message to a class 0 data request also includes the object corresponding to the
binary outputs with status.
 NO
 YES
❑ Analog output status def.: Indicates whether the reply message to a class 0 data request also includes the object
corresponding to the analog outputs with status.
 NO
 YES
❑ Frozen Counters status def.: Indicates whether the reply message to a class 0 data request also includes the object
corresponding to the frozen counters with status.
 NO
 SI
❑ Analog input bits default: Indicates the default value for the "Var" field in the analog objects when no variation is
requested.
 16 Bits
 32 Bits
 Short floating point
❑ Normalized: Indicates the analog format.
 Secondary.
 Normalized.
 Primary. (Not operative in the current version, if used, the device configures Normalized)
❑ Counter bits default: Indicates the default value for the "Var" field in the counter objects when no variation is requested.
 16 Bits
 32 Bits
❑ Enable unsolicited: Enables the use of unsolicited responses with class 1, 2 o 3.
 NO
 YES
❑ Enable collision avoidance: Enables the collision avoidance detection with DCD method.
 NO
 YES
❑ Fixed Unsolicited T.out (ms): Fixed waiting time before transmitting an unsolicited response. Value between 0 and 5000.
❑ Variable Unsolicited T.out (ms): Variable waiting time additional to the previous setting of fixed time. The value options
are :

DNP PROTOCOL 
Setting Value Time in ms

0 255
1 127
2 63
3 31
4 15
5 7
6 3
7 1
❑ Unsolicited Repeat T.out (s): Waiting time in seconds before a retransmission of an unsolicited response when there is
not a link or application acknowledge to the previous message. Value between 0 and 630 seconds.
❑ Max.number rep. without solic.: Maximum number of retransmission of an unsolicited response. Value between 0 and
65535. Infinite for value 0.
❑ Special operations: Enables the activation of certain operational characteristics.
Bit Bit indication at 1

0 Dispatch of current counters with OBJ = 21
1 Reserve
2 Dispatch of unsolicited responses up to the IIN included each 10 seconds
3 Reserve
4 Reserve
5 Reserve
6 Restart message not sent on start up
❑ Change wait time (s): Waiting time for the SOE in the internal queue before processing the events. It is only necessary if
there are data from different IEDs in order to sort them chronologically.
❑ TCP Listen Port: TCP port used as server.
❑ Unsolicited react. delay (s): The waiting time to retry again the maximum number of retries an unsolicited message. Value
between 0 and 3600 seconds. Zero does not apply.
❑ Command selection time (ms): The waiting time to abort the selection command. Value between 100 and 15000
miliseconds. Default 15000.
❑ Max command wait time (ms): The maximum time waiting the protocol to the result of the command before responding
to the master. If expired is indicated “Not supported” Default 0.
❑ Enable T.correct.buf.events: True value performs the correction date all still digital events queues when the first
syncrhronization is received. The device does not answer with digital events since the first synchronization. Default No.
The configuration settings for the first DNP are in the GEN\DNPITCP1 node IEC 61850 data model, as detailed in the following
table:

DNP PROTOCOL 
Table 70 DNP protocol settings

ProtEna Enable protocol NO/YES Boolean
Slave Slave address 0 65532 1 Int32
Master Master address 0 65532 1 Int32
Disable
COM1
COM2
COM3
Port Port Number COM4 Enum
COM5
COM6
Ethernet 1
Ethernet2
600 baud
1200 baud
2400 baud
4800 baud
Speed Comm speed (bauds) Enum
9600 baud
19200 baud
38400 baud
57600 baud
Parity Parity None, Even, Odd Enum
Stopbit Number of Stop bits 1Bit, 2 Bit Enum
Normal
Fixed + DCD
RTS
RtsType Communication control Enum
RTS+CTS
RTS+CTS+DCD
RS485
RtsTmms Min. respond delay(ms) 0 1000 10 Int32
CtsTmms CTS max delay (ms) 0 1000 10 Int32
CarTmms Carrier stabilization (ms) 0 1000 10 Int32
RtsOffTmms RTS drop-off time (ms) 0 1000 1 Int32
AckTmms ACK delay time(ms) 100 10000 10 Int32
SynDl Need time delay(m) 0 10 1 Int32
SynEna Permission to synchronize NO/YES Boolean
SynOfs Local time offset(h) -12 12 1 Int32
ComFailTm Communication fail T.(min) 0 10000 1 Int32
LinkAck Data link confirm NO/YES Boolean
MaxAppSize Max. App Fragment Size 512 3072 256 Int32
FrzCnt Freeze time counters NO/YES Boolean
StDefault Default status 0 31 1 Meaning of bits (1) Int32
BinOutSt Bin. output status default NO/YES Boolean
AnOutSt Analog output status def. NO/YES Boolean
FrCntSt Frozen Counters status def. NO/YES Boolean
16 Bits
AnInBits Analog input bits default 32 Bits Enum
Short floating point
Primary, Normalized
Normalized Normalized Enum
Secondary
CntBits Counter bits default 16 Bits, 32 Bits Enum
UnSolEna Enable unsolicited NO/YES Boolean
CollEna Enable collision avoidance NO/YES Boolean
FixedTmms Fixed Unsolicit.Timeout (ms) 0 5000 10 Int32
255, 127, 63, 31, 15, 7,
VarTmms Var. Unsolicit. Timeout (ms) Enum
3, 1
UnSolTmms Unsolicit. Repeat T.out (s) 0 630 1 Int32
UnSolMaxR Max.number rep. without solic. 0 65535 1 Int32
SpecialBeh Special operations 0 255 1 Int32
CambTms Change wait time (s) 0 20 1 Int32
TcpPort TCP Listen Port 0 65535 1 Int32

DNP PROTOCOL 
ReacTms Unsolicited react. delay (s) 0 3600 1 Int32

TselecTmms Command selection time (ms) 100 15000 10 Int32
TOWaitTmms Max command wait time (ms) 0 1000 10 Int32
FixSynEna Enable T.correct.buf.events 0 1 1 Boolean
Where:
Meaning of bits (1) Bit Value

Send all with status 0 YES/NO
Send digitals with status 1 YES/NO
Send measurements with status 2 YES/NO
Send counters with status 3 YES/NO
Send frozen counters with status 4 YES/NO
20.3 TABLES
There are 4 tables to configure the list of digital status (binary inputs), analogs, counters and commands.
20.3.1 Digital status table

For each element the following fields must be configured*:
❑ Type: Type of signal.

 Simple.
❑ DNP Signal: Signal number with respect to the DNP protocol. Values from 0 to 4093. It should start at 0 and gaps
are not allowed.
❑ CIN: Signal incidence code:
 SP→ Value change in simple signaling
❑ InternalIED: IED of the signal. Value 0 corresponds to the device itself.
❑ Internal ID: Internal signal number that identifies the element inside the device.
❑ Class: Default class assigned to the signal. With value 0 the signal does not cause changes.
 Class 0
 Class 1
 Class 2
 Class 3
❑ Time: Time format for changes.
 Without time
 Absolute time
 Relative time
❑ Inverted: Indicates if the signal status is inverted. By default is not inverted.
 Not inverted
 Inverted
*The protocol configurator allows other non-operational options in this version.
20.3.2 Analog values table

For each element the following fields must be configured:
❑ DNP signal: DNP analog number. Values between 0 and 1023. Gaps are allowed.

DNP PROTOCOL 
❑ Internal IED: IED of the analog value. Value 0 corresponds to the device itself.
❑ Internal ID: Internal analog number that identifies the element inside the device. Selectable from a list.
❑ Class: Class assigned to the analog value. With value 0 the analog value does not cause events.
 Class 0
 Class 1
 Class 2
 Class 3
❑ Dead band: Absolute variation value to cause an event. Values between 0 and 10000. It is applied over the value
stored in 16 bits.
❑ Dec: Number of decimal places for the analog value when the setting “Normalizado” is set to Primary or Secondary.
(Factor of 10 raised to the number of decimal). Values between 0 to 4. At value 0, the value is sent without
modifications.
❑ Limit scale: Full scale used when the setting “Normalizado” takes the Normalized value. It is the value that causes
32767 to be sent in DNP.
❑ The deadband is defined as the value that the analog value must vary to be sent as a event. It is always applied on
the current value of the measure to be sent.
When the analog values are to be sent, the current value is compared to the last sent value and if the difference is greater than
the DeadBand the current value is transmitted. A zero value does not generate any events.
20.3.3 Counters table
❑ DNP signal: DNP counter number. Values between 0 and 63. Gaps are allowed.
❑ Internal IED: IED of the counter value. Value 0 corresponds to the device itself.
❑ Internal ID: Internal counter number that identifies the element inside the device. Selectable from a list.
❑ Class: Class assigned to the counter. With value 0 the counter value does not cause changes.
 Class 0
 Class 1
 Class 2
 Class 3
❑ Dead band: Absolute variation value to cause an event. Values between 0 and 10000.
20.3.4 Commands table

Fields that are expected to be received in the DNP command message:
❑ DNP command: DNP command number. Values between 0 and 255.

❑ Op type: DNP command value.
 TRIP

DNP PROTOCOL 
 CLOSE
 Latch ON
 Latch OFF
 Pulse ON
 Pulse OFF (deprecated)
❑ Comand type:
 All. All types supported.
 SBO. Only Selec Before Operate supported.
 DO. OnlyDirect operate supported.
Order configuration fields on the device itself:
❑ Internal IED: IED of the command. Value 0 corresponds to the device itself.
❑ Internal ID: Internal counter number that identifies the element inside the device. Selectable from a list. The
internal value is affected by the next field.
❑ ON_OFF: Internal command value. Use to select Internal ID.
 ON
 OFF
❑ Origin:
 Bay Control
 Station Control
 Remote Control
 Automatic Bay
 Automatic Station
 Automatic Remote
 Maintenance
 Process
Only one command is accepted in each message, count = 1. The On Time and Off Time fields are not used.

DNP PROTOCOL 
20.4 DEVICE PROFILE
DEVICE PROFILE DOCUMENT

Vendor Name: INGETEAM S.A.
Device Name: INGEPAC EF
Highest DNP Level Supported:
Device Function:
For Requests Level 3
 Master  Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the complete list is described in the
attached table):
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted 292 Transmitted 1024< >3072( configurable)
Received 292 Received 1024
Maximum Data Link Re-tries:
Maximum Application Layer Re-tries:
 None
 None
 Fixed at 1
 Configurable, range ____ to ____
 Configurable, range __ to __
Requires Data Link Layer Confirmation:
 Never
 Always
 Sometimes
 Configurable
Requires Application Layer Confirmation:
 When reporting Event Data
 When sending multi-fragment responses
Timeouts while waiting for:
Data Link Confirm  None  Fixed at _________  Variable  Configurable
Complete Appl. Fragment  None  Fixed at _________  Variable  Configurable
Application Confirm  None  Fixed at __10 sg____  Variable  Configurable
Complete Appl. Response  None  Fixed at _________  Variable  Configurable
Others
Sends/Executes Control Operations:
WRITE Binary Outputs  Never  Always  Sometimes  Configurable
SELECT/OPERATE  Never  Always  Sometimes  Configurable
DIRECT OPERATE  Never  Always  Sometimes  Configurable
DIRECT OPERATE – NO ACK Never  Always  Sometimes  Configurable
Count > 1  Never  Always  Sometimes  Configurable
Pulse On  Never  Always  Sometimes  Configurable
Pulse Off  Never  Always  Sometimes  Configurable
Latch On  Never  Always  Sometimes  Configurable
Latch Off  Never  Always  Sometimes  Configurable
Queue  Never  Always  Sometimes  Configurable
Clear Queue  Never  Always  Sometimes  Configurable
Reports Binary Input Change Events when no specific variation Reports time-tagged Binary Input Change Events when no specific
requested: variation requested:
 Never  Never
 Only time-tagged  Binary Input Change With Time
 Only non-time-tagged  Binary Input Change With Relative Time
 Configurable to send both, one or the other (attach explanation)  Configurable (attach explanation)
Sends Unsolicited Responses:
 Never Sends Static Data in Unsolicited Responses:
 Configurable (attach explanation)  Never
 Only certain objects  When Device Restarts
 Sometimes (attach explanation)  When Status Flags Change
 ENABLE/DISABLE UNSOLICITED
Function codes supported
Supports Collision Avoidance: Configurable Collision Avoidance Detection Method: DCD
Default Counter Object/Variation: Counters Roll Over at:
 No Counters Reported  No Counters Reported
 Configurable (attach explanation)  Configurable (attach explanation)
 Default Object _________  16 Bits
Default Variation ______  32 Bits
 Point-by-point list attached  Other Value _____________

DNP PROTOCOL 
 Point-by-point list attached

Sends Multi-Fragment Responses:  Yes  No
20.4.1 OBJECT TABLE

REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Codes Qual Codes Func Codes
Obj Var Description Qual Codes (hex)
(dec) (hex) (dec)
1 0 Binary Input – All Variations 1,22 00,01,06
1 1 Binary Input 1 00,01,06 129 00,01
1 2 Binary Input with Status 1 00,01,06 129 00,01
2 0 Binary Input Change - All Variations 1 06,07,08
2 1 Binary Input Change without Time 1 06,07,08 129, 130 28
2 2 Binary Input Change with Time 1 06,07,08 129, 130 28
2 3 Binary Input Change with Relative Time 1 06,07,08 129, 130 28
10 0 Binary Output - All Variations 1 00,01,06
10 2 Binary Output Status 1 00,01,06 129 00,01
12 1 Control Relay Output Block 3, 4, 5, 6 17, 28 129 Echo of request
1, 7, 8, 9,
20 0 Binary Counter - All Variations 00,01,06
10,22
1, 7, 8, 9,
20 1 32-Bit Binary Counter 00,01,06 129 00,01
10
1, 7, 8, 9,
20 2 16-Bit Binary Counter 00,01,06 129 00,01
10
20 3 32-Bit Delta Counter 1 00,01,06 129 00,01
20 4 16-Bit Delta Counter 1 00,01,06 129 00,01
20 5 32-Bit Binary Counter without Flag 1 00,01,06 129 00, 01
20 6 16-Bit Binary Counter without Flag 1 00,01,06 129 00, 01
20 7 32-Bit Delta Counter without Flag 1 00,01,06 129 00,01
20 8 16-Bit Delta Counter without Flag 1 00,01,06 129 00,01
21 0 Frozen Counters - All Variations 1, 22 00,01,06
21 1 32-Bit Frozen Counter 1 00,01,06 129 00,01
21 2 16-Bit Frozen Counter 1 00,01,06 129 00,01
21 3 32-Bit Frozen Delta Counter 1 00,01,06 129 00,01
21 4 16-Bit Frozen Delta Counter 1 00,01,06 129 00,01
21 5 32-Bit Frozen Counter with Time of Freeze 1 00,01,06 129 00, 01
21 6 16-Bit Frozen Counter with Time of Freeze 1 00,01,06 129 00, 01
32-Bit Frozen Delta Counter with Time of
21 7 1 00,01,06 129 00,01
Freeze
16-Bit Frozen Delta Counter with Time of
21 8 1 00,01,06 129 00,01
Freeze
21 9 32-Bit Frozen Counter without Flag 1 00,01,06 129 00,01
21 10 16-Bit Frozen Counter without Flag 1 00,01,06 129 00,01
21 11 32-Bit Frozen Delta Counter without Flag 1 00,01,06 129 00,01
21 12 16-Bit Frozen Delta Counter without Flag 1 00,01,06 129 00,01
22 0 Counter Change Event – All Variations 1 06,07,08
22 1 32-Bit Counter Change Event without Time 1 06,07,08 129, 130 28
22 2 16-Bit Counter Change Event without Time 1 06,07,08 129, 130 28

32-Bit Delta Counter Change Event without
22 3 1 06, 07, 08 129 28
Time
16-Bit Delta Counter Change Event without
22 4 1 06, 07, 08 129 28
Time
23 0 Frozen Counter Events – All Variations 1 06, 07, 08 129
23 1 32-Bit Frozen Counter Event without Time 1 06, 07, 08 129 28
23 2 16-Bit Frozen Counter Event without Time 1 06, 07, 08 129 28
23 3 32-Bit Frozen Delta Counter Event without Time 1 06, 07, 08 129 28
23 4 16-Bit Frozen Delta Counter Event without Time 1 06, 07, 08 129 28

DNP PROTOCOL 
REQUEST RESPONSE
OBJECT
(slave must parse) (master must parse)
Func Codes Qual Codes Func Codes
Obj Var Description Qual Codes (hex)
(dec) (hex) (dec)
30 0 Analog Input - All Variations 1, 22 00,01,06
30 1 32-Bit Analog Input 1 00,01,06 129 00, 01
30 2 16-Bit Analog Input 1 00,01,06 129 00,01
30 3 32-Bit Analog Input without flag 1 00,01,06 129 00, 01
30 4 16-Bit Analog Input without flag 1 00,01,06 129 00, 01
30 5 Analog Input — Single-prec flt-pt with flag 1 00,01,06 129 00, 01
32 0 Analog Change Event - All Variations 1 06,07,08
32 1 32-Bit Analog Change Event without Time 1 06,07,08 129, 130 28
32 2 16-Bit Analog Change Event without Time 1 06,07,08 129, 130 28
Analog Input Event — Single-prec flt-pt without
32 5 1 06,07,08 129,130 28
time
2 07, quantity=1
50 1 Time and Date
1 07, quantity=1 129 07, quantity=1
51 1 Time and Date CTO 129 07, quantity=1
51 2 Unsynchronized Time and Date CTO 129 07, quantity=1
52 2 Time Delay Fine 129 07, quantity=1
60 1 Class 0 Data 1 06
1 06,07,08
60 2 Class 1 Data
20, 21,22 06
1 06,07,08
60 3 Class 2 Data
20, 21, 22 06
1 06,07,08
60 4 Class 3 Data
20, 21, 22 06
1 00, 01 129 00
80 1 Internal Indications
2 00, index=7
No Object 13, 14
No Object 23

IEC 60870-5-103 PROTOCOL 
21. IEC 60870-5-103 PROTOCOL
21.1 INTRODUCTION
The device provides an IEC 60870-5-103 interface to act as RTU and to communicate with a IEC 60870-5-103 master (for example a
remote control station).

❑ Protocol configuration tables for digital signals, measurements and commands (which are configured with the software
configuration tool)
Depending on the model, the device has the following settings:
 Yes
 No
❑ Slave address: Slave address of the device. Value between 1 and 254.
 COM1
 COM2
 COM3
 COM4
 COM5
 COM6
 600 baud
 1200 baud
 2400 baud
 4800 baud
 9600 baud
 19200 baud
 38400 baud
 57600 baud
❑ Parity: Enables the selection of the parity type to be used in transmission.
 None
 Even
 Odd
❑ Number of Stop bits: Enables the selection of the number of stop bits.
 1 Bit
 2 Bit
❑ Communication control: Enables de selection of the communication control type.

 Normal
 Fixed + DCD
 RTS
 RTS+CTS
 RTS+CTS+DCD
 RS485
❑ Min. respond delay (ms): Waiting time for the activation of the RTS and the transmission of a message after the reception
❑ CTS max delay (ms): Waiting time for the CTS activation after the RTS activation. Value between 0 and 1000.
❑ RTS drop-off time (ms): Waiting time for the RTS deactivation after the message last byte transmission.
 Yes
 No
It is used to select the synchronization source when there are several available.
❑ Communication fail T.(min): Waiting time in minutes without receiving any valid measure before indicate communication
failure. Value between 0 and 10000.
❑ VDEW Compatible: A “No” value allows the use of private data range.
 No
 Yes
Compatible mode (Yes):
Digital control signals that are sent are those configured with a compatible Funtion Type. The zero value in the table
indicates Funtion Type = Compatible. The other signals do not appear.
The user is responsible for selecting the digital signals of the device in accordance to the IEC 60870-5-103 standard.
Analog measurements are at most the first nine measures configured in the table. The Function Type and Information
Number to use (144, 145, 146 o 148) depends on the number of configured measures. 1, 2, 4 or 9 measures in the
measurements table respectively. In the last case the ASDU 9 is used instead of ASDU 3. The user is responsible for selecting
the device measures in accordance with IEC 60870-5-103.
Only the compatible commands are processed, those which in the table are configured by Function type = 0. The user is
responsible for selecting them according to IEC 60870-5-103.
Private mode (No):
All programmed control signals are sent.
The measures are sent with the Function Type field equal to "TYP in measurands ASDU" and Information Number field
equal to "INF in measuransds ASDU".
Supported commands are all that are programmed in the table.
❑ Function type: Value used to describe the type of protection equipment used.
 distance protection ( 128 )
 overcurrent protection ( 160 )
 transformer differential protection ( 176 )
 line differential protection ( 192 )

❑ TYP in measurands ASDU: This setting only applies when the adjustment VDEW is set to No. Indicates the Function Type
that is used in measurands ASDU.
❑ INF in measurands ASDU: The setting only applies when the adjustment VDEW is set to not. The field indicates the
Information Number used in measurands ASDU.
❑ Transformation ratio: Transformation ratio applied in the measurands.
 Secundary
 Primary
The configuration settings for the IEC 60870-5-103 are in the GEN\103ITCP1 node IEC 61850 data model, as detailed in the following
table:
Table 71 IEC 60870-5-103 protocol settings

Slave Slave address 1 254 1 Int32
COM1
COM2
COM3
Port Port Number Enum
COM4
COM5
COM6
600 baud
1200 baud
2400 baud
4800 baud
Speed Comm speed (bauds) Enum
9600 baud
19200 baud
38400 baud
57600 baud
None
Parity Parity Even Enum
Odd
1Bit
Stopbit Number of Stop bits Enum
2 Bit
Normal
Fixed + DCD
RTS
RtsType Communication control Enum
RTS+CTS
RTS+CTS+DCD
RS485
RtsTmms Min. respond delay(ms) 0 1000 10 Int32
CtsTmms CTS max delay (ms) 0 1000 10 Int32
CarTmms Carrier stabilization (ms) 0 1000 10 Int32
RtsOffTmms RTS drop-off time (ms) 0 1000 1 Int32
CambTms Change wait time (s) 0 20 1 Int32
VDEW VDEW Compatible NO/YES Boolean
distance protection
overcurrent -
protection
FunTyp Function type transformer - Enum
differential protection-
line differential
protection
FunTypMed TYP in measurands ASDU 0 255 1 Int32
InfMed INF in measurands ASDU 0 255 1 Int32
RT Transformation ratio Secundary/Primary Boolean

21.3 TABLES
There are 3 tables to configure the list of digital signals, measurements and commands.
21.3.1 Digital signals table

Each digital signal device is identified in the IEC60870-5-103 protocol by the pair of fields Function Type and Information Number.
For each element the following fields must be configured with the software configuration tool:
❑ Type: Tipe of signal. Simple or double.

 Simple. (Default)
 DP
❑ CIN: Signal incidence code:
 SP→Value change in simple signaling. (Default)
 DP Open→ If the field Type = DP: Change in the calculated signal giving the 01 or open state of a double signal.
 DP Closed→ Change in the calculated signal giving the 10 or closed state of a double signal.
 DP Intermediate→ Change in the calculated signal giving the state 00 or intermediate of a double signal.
 DP Indeterminate→ Change in the calculated signal that gives the 11 or indeterminate of a double signal.
❑ Function type: Function type field of the signal. In the case that the signal belongs to the compatible range, (128,
160, 176 o 192), it should be configured a value of 0. The following values are not allowed: 129, 144, 145, 161, 177,
193, 208, 209, 224, 225, 240, 241, 254, 255.
❑ Information number: Information Number for the signal.
❑ Internal IED: IED of the signal value. Value 0 corresponds to the device itself.
❑ Internal ID: Internal signal number that identifies the element inside the device. In the case that the signal belongs
to the compatible range, the user is responsible for selecting the digital signals of the device in accordance to the
IEC 60870-5-103 standard.
❑ General interrogation: When selected it indicates that the information is included in the general interrogation (GI).
For these Information Numbers both status changes (OFF to ON and ON to OFF) are transmitted spontaneously.
For the others Information Numbers only the status OFF to ON are transmitted.
❑ Inverted: Indicates if the signal status is inverted. By default is not inverted
In the case of using a double-type signal, the four signals forming the double signal must be configured (Open, Close, Intermediate
and Indeterminate). Using this type of signal expands the meaning of the DPI field sent in the ASDUs:
When simple type signals are used, the field is sent as is the norm in section 7.2.6.5. Double-point information:
DPI := UI2[1..2] <0..3>
With <0> := not used
<1> := OFF
<2> := ON
<3> := not used
When using DP type signals, the meaning of the values 0 and 3 changes, becoming:
DPI := UI2[1..2] <0..3>
With <0> := Intermediate, (transitioning between end conditions)
<1> := OFF
<2> := ON
<3> := Indeterminate, (abnormal or custom condition)

21.3.2 Measurements table

❑ Measure number: Measure position inside the ASDU. The first position is zero.
❑ Internal IED: IED of the signal value. Value 0 corresponds to the device itself.
❑ Internal ID: Internal measure number that identifies the element inside the device. In the case that the measure
belongs to the compatible range, the user is responsible for selecting the measure of the device in accordance to
the IEC 60870-5-103 standard.
❑ Límit scale: Real positive measurement value corresponding to 4095 internal units. If the value is zero and the
transformation ratio setting indicates secondary, the database limit scale is applied to the measure. If the value is
zero and transformation ratio setting indicates primary, the database limit scale is applied to the measure
multiplied by the transformation ratio.

❑ Function type: Function Type field for the signal. In the case that the signal belongs to the compatible range, (128,
160, 176 o 192), it should be configured a value of 0.
❑ Information number: Information Number for the signal.
❑ DCO: ON/OFF value of the command.
❑ IED interno: IED of the command value. Value 0 corresponds to the device itself
❑ Internal ID: Internal command number that identifies the element inside the device. In the case that the command
belongs to the compatible range, the user is responsible for selecting the command of the device in accordance to
the IEC 60870-5-103 standard
❑ Origin: Command origin. Allowed values:
 Bay Control
 Station Control
 Remote Control
 Automatic Bay
 Maintenance
 Process

SLAVE PROCOME PROTOCOL 
22. SLAVE PROCOME PROTOCOL
22.1 INTRODUCTION
The device provides a Procome interface to act as RTU and to communicate with a Procome master (for example a remote control
station).
The communication can be selected for a serial line or via Ethernet, using encapsulation by means of the TCP/IP protocol.

❑ Protocol configuration tables for digital signals, measurements, counters and commands (which are configured with the
software configuration tool)
 Disable
 COM1
 COM2
 COM3
 COM4
 COM5
 COM6
 Ethernet 1
 Ethernet 2
❑ Procome address: Procome slave address of the device. Value between 0 and 254.
 300 baud
 600 baud
 1200 baud
 2400 baud
 4800 baud
 9600 baud
 19200 baud
 38400 baud
 57600 baud
 115200 baud
❑ Parity: Enables the selection of the parity type to be used in transmission.
 Without parity
 Even
 Odd
❑ Number of Stop bits: Value between 1 and 2.

User Manual 205
❑ CTS wait time (ms): Waiting time for the CTS activation after the RTS activation. Value between 0 and 10000.
❑ RTS activation time (ms): Waiting time for the activation of the RTS and the transmission of a message after the reception
❑ RTS drop out time (ms): Waiting time for the RTS deactivation after the message last byte transmission.
❑ Channel Type: Enables de selection of the communication control type.
 Standard
 RTS Control
 By Phone
 Yes
 No
It is used to configure the synchronization source when there are several available.
❑ TCP Listen Port: TCP port used as server.
The configuration settings for the first PROCOME are in the GEN\ITCP1 node IEC 61850 data model, as detailed in the following
table:

User Manual 206
Table 72 Slave Procome protocol settings
Data Setting Mín. Max. Step Remarks Type

Disable
COM1
COM2
COM3
Port Port Number COM4 Enum
COM5
COM6
Ethernet 1
Ethernet 2
DirEnl Procome Address 0 254 1 Uint32
300 baud
600 baud
1200 baud
2400 baud
4800 baud
VelTrans Speed (Bauds) Enum
9600 baud
19200 baud
38400 baud
57600 baud
115200 baud
Parity Parity None / Even / Odd Enum
Stopbit Number of Stop Bits 1 2 1 Uint32
PorTmms Carrier stabilization (ms) 0 1000 10 Uint32
ActCtsTmms CTS wait time (ms) 0 10000 5 Uint32
ActRtsTmms RTS activation time (ms) 0 5000 10 Uint32
DesRtsTmms RTS drop out time (ms) 0 5000 1 Uint32
Standard
TipoCan Channel type RTS Control Enum
By Phone
CambTms Change wait time (s) 0 20 1 Uint32
SynEna Permission to synchronize NO/YES Enum
TcpPort TCP Listen Port 0 65535 1 Uint32
22.3 TABLES
There are 4 tables to configure the list of digital status (binary inputs), analogs, counters and commands.
22.3.1 Digital status table

❑ Remte Signal, (nP): Procome signal number. Values between 0 and 1023.
❑ IED, (UCL): IED of the signal. Value 0 corresponds to the device itself.
❑ Internal signal, (nUCL): Internal signal number that identifies the element inside the device.
❑ Inverted, (Inv): Indicates if the signal status is inverted. By default is not inverted.
 Not inverted (0)
 Inverted (1)
❑ Reference 61850 of signal.
22.3.2 Analog values table

❑ Remote Measure, (nP): number of measure Procome. Values between 0 and 255. Gaps are allowed.
❑ Internal IED, (UCL): IED of the analog value. Value 0 corresponds to the device itself.

User Manual 207
❑ Internal ID, (nUCL): Internal analog number that identifies the element inside the device.
❑ Reference 61850 of measure.
22.3.3 Counters table

❑ Remote counter, (nP): Procome counter number. Values between 0 and 255. Gaps are allowed.
❑ Internal IED, (UCL): IED of the counter value. Value 0 corresponds to the device itself.
❑ Internal ID, (nUCL): Internal counter number that identifies the element inside the device.
❑ Reference 61850 of counter.

❑ Remote command, (nP): Procome command number. Values between 0 and 1023.
❑ Internal IED: IED of the command. Value 0 corresponds to the device itself.
❑ Internal ID, (nUCL): Internal command number that identifies the element inside the device. The value of the
Internal command ON corresponds to the number of even order and the value to be the odd OFF
❑ Source (origen):
 Station Control
 Remote Control
NOTE: If the 'source' field does not exist in the file, it takes as default Control Station.
❑ Reference 61850 of command.

User Manual 208
MODBUS MASTER PROTOCOL
23. MODBUS MASTER PROTOCOL
23.1 INTRODUCTION
The Modbus master protocol allows communication with control and/or protection and measuring devices.
Currently, the device has only asynchronous serial communication, with a start bit, 8 bits of data and configurable parity and stop bits.
The protocol allows the database to update with digital signals, measurements and counters. It also allows to send commands. For
some type of devices it allows to send synchronization messages and request for signal changes or events.
A configuration table, generated with a software tool dedicated to this effect, will indicate the number of information elements of each
type that each equipment has, as well as its address according to the Modbus RTU protocol.
The following are detailed:

❑ Data types that can be requested/written from/to slave devices
❑ Modbus functions that are implemented in the protocol
❑ Types of RTU to communicate with
❑ Configuration software tool
❑ Modbus messages supported
 No
 Yes
❑ Port Number: It allows to set the communication channel between the available serial COMs.
 COM1
 COM2
 COM3
 COM4
 COM5
 COM6
❑ Comm speed (bauds): It allows to select the serial transmission speed.
 600 baud
 1200 baud
 2400 baud
 4800 baud
 9600 baud
 19200 baud
 38400 baud
 57600 baud

User Manual
209
❑ Parity: It allows to select the type of parity to be used in the transmission.

 None
 Even
 Odd
❑ Number of stop bits:
 1 Bit
 2 Bit
❑ Communication control: It allows to select the type of communication channel.
 RS232_FO
 RS485
❑ RTS activation delay Time (ms): Minimum waiting time to activate the RTS and start the transmission. Value between 0 and 5000.
❑ CTS max delay (ms): How much time the device will wait to activate the CTS after the activation of the RTS. Value between 0 and
10000.
❑ Carrier stabilization (ms): Waiting time to start the transmission, once CTS has been detected, in order to stabilize the carrier. Value
between 0 and 5000
❑ RTS dropoff time (ms): This is the time that the RTS signal keeps activated after the transmission of the last byte. Value between 0
and 5000.
❑ Respond delay time (ms): Maximum time that the master waits to receive the slave response. Value between 10 and 30000.
❑ Inter request time (ms): The time between two request cycles of the master device. Value between 10 and 30000.
❑ Transmission retries number: Indicates the number of data request retries the master device does, if it does not receive any
response from the slave device at a given time (Respond delay time). Value between 0 and 10.
Table 73 Modbus Master protocol settings
Data Setting Min. Max. Step Remarks Type

COM1
COM2
COM3
Port Port Number Enum
COM4
COM5
COM6
600 baud
1200 baud
2400 baud
4800 baud
BaudRate Comm speed (bauds) Enum
9600 baud
19200 baud
38400 baud
57600 baud
Stopbit Number of stop bits 1 Bit / 2 Bit Enum
RS232_FO
ChType Communication control Enum
RS485
ActRtsTmms RTS activation delay Time (ms) 0 5000 10 int32
ActCtsTmms CTS max delay (ms) 0 10000 10 int32
CarTmms Carrier stabilization (ms) 0 5000 10 int32
DesRtsTmms RTS dropoff time (ms) 0 5000 10 int32
RespTmms Respond delay time (ms) 10 30000 10 int32
IntgcTmms Inter request time (min) 10 30000 10 int32
RetryNumb Transmission retries number 0 10 1 Int32

User Manual
210
23.3 DATA TYPES
The protocol allows the master device to read signals, measurements and counters from the slave devices. It also allows sending
commands to the devices. In addition it allows to request signal changes and synchronization for the next devices: PL300 and TCP-IH.
Different types and formats of signals, measurements and counters are supported. The device configuration will indicate the data and
formats to be requested for each slave.
23.3.1 Digital signals

The Modbus master has the following signal types:
Table 74 Digital signal types
Type Description Remarks

1 Relay status Status of relays bit by bit
4 Digital signal (16 signals/WORD) Digital inputs as 16-bit registers, 16 signals in each word
Similar to type 1 and 14 but to read the information of one
5 Device status
single byte: Fast read of a byte.
12 Digital signal (1 signal/WORD) Digital inputs as 16-bit registers. One digital input per word
14 Input status Digital inputs bit by bit
Type 14 can only be used for RTU type 5.
23.3.2 Measurements
The Modbus master has the following measurement types:
Table 75 Measurement types

2 Measurement For reading measurements with F03/F04 functions
7 Additional measurement For reading measurements with F03 function
Type 7 can only be used for RTU type 5.
The Modbus master has the following measurement formats:
Table 76 Measurement format types
Format Description Remarks
0 8 bits, unsigned Measurements in 8-bit unsigned format
1 8 bits, signed Measurements in 8-bit signed format
6 Float point Measurements in floating format
10 Procome Measurements in Procome format in accounts
11 15 bits plus sign Measurements in 16-bit signed format with sign in the higher bit

User Manual
211
23.3.3 Counters
Table 77 Counter types
3 Counter Counter reading
The following counter formats are supported
Table 78 Counter format types
Format Description Remarks
0 8 bits, unsigned Counters in 8-bit unsigned format
1 8 bits, signed Counters in 8-bit signed format
6 Float point Counters in floating format
Counters in 32-bit floating format:

7 Float point / 1000
The value is sent divided by 1000
23.3.4 Commands
The Modbus functions implemented in the device for the execution of commands are F05 and F16. Only one type of function can
be used for each device.
The information related to the Modbus functions is in the sections of Implemented functions and RTU types of this manual.
23.3.5 Request of events to Ingeteam Power Technology devices

Currently, the request of events or signal changes it is only implemented for PL300 and TCP-IH. This request may be enabled from
the “Modbus master configurator”.
23.3.6 Synchronization
Currently, the synchronization it is only implemented for PL300 and TCP-IH.

User Manual
212
23.4 IMPLEMENTED FUNCTIONS
The Modbus master functions that may be used for requesting and writing data in the slave devices are the following:
Table 79 Implemented Modbus functions
Function Code Description

01 Read Coils
02 Read Discrete Inputs
03 Read Holding Registers
04 Read Input Registers
05 Write single coil
07 Read exception status
16 Write multiple registers
The Modbus master will use these functions taking into account the type and database of the device configured in the “Modbus master
configurator”
23.5 RTU TYPES
The following table shows the type of devices currently considered in the Modbus master and the Modbus functions used for each
type:
Table 80 Characteristics of RTU types
RTU types Signal changes/Events Data request Command execution Synchronization

F01
1 NO F05 NO
F04
F01
3 NO F16 NO
F03
F02
F03
4 NO F05 NO
F04
F07
F01
F02
5 NO F16 NO
F03
F04
F01
10 YES F16 YES
F03
14 NO F04 NOT IMPLEMENTED NO
❑ RTU type 1: It supports reading digital outputs bit by bit, reading registers and writing digital outputs bit by bit
 F01: Function for reading digital outputs bit by bit
 F04: Function for reading registers
 F05: Function for writing digital outputs bit by bit
❑ RTU type 3: It supports reading digital outputs bit by bit, reading registers and writing multiple registers
 F16: Function for writing multiple registers
❑ RTU type 4: It supports reading digital inputs bit by bit, reading registers and exception states and writing digital outputs bit by bit
 F02: Function for reading digital inputs bit by bit

User Manual
213

 F07: Function for reading exception states
 F05: Function for writing digital outputs bit by bit
❑ RTU type 5: It supports reading outputs and digital inputs bit by bit, reading registers and writing multiple registers
 F02: Function for reading digital inputs bit by bit
 F16: Function for reading multiple registers
❑ RTU type 10: It supports reading digital outputs bit by bit, reading registers and writing multiple registers
 F16: Function for reading multiple registers
The request of events and synchronization is currently only implemented for PL300 and TCP-IH.
 F03: Function for event requests
 F16: Function for synchronizing
❑ RTU type 14: It supports reading registers
23.6 SW CONFIGURATION TOOL
The Modbus master protocol is configured using the “Modbus master configurator” available in the PacFactory configuration SW and
EFS tools. This tool generates a configuration file that is sent to the device.
23.6.1 Fields to be configured

The tool has different tabs that are filled based on what is going to be integrated. Each tab has several fields.
❑ IED
 Modbus address
Address of the slave device (1 - 128). It is the value of the Modbus address of the device to communicate with.
 Internal address
Address of the slave device in the internal database. Its value is between 1 and 32. All the elements that are requested from
the device will be mapped on this address of the master database.
 RTU type
This field can take the following values: 1, 3, 4, 5, 10 and 14. The characteristics of each of these values are given in the RTU
Types section of this manual. It shows the functions used for each type of device.
 Sync RTU

User Manual
214
Enables sending synchronization to the slave device. It is only implemented for RTU type 10 (TCP-IH or PL300).
To enable synchronization, the Sync RTU flag is activated. Once enabled, the following screen appears:
The synchronization address of the device is indicated in the Sync address field.
PL300 = 240 and TCP-IH = 240.
Sync adjust (ftrans) is the time in ms that will be added to the synchronization time to correct possible drifts.
 Events request
It enables the request of signal changes of the slave device. It is only supported for RTU type 10 (PL300 or TCP-IH).
Once enabled, the following screen appears:
In the Event address field, the signal change start address for the given device is indicated. PL300 = 20480 and TCP-IH =
1664.

User Manual
215
 Endianness
It can take two values: Big Endian and Little Endian. Default value: Big endian.
It indicates the way in which the slave equipment sends the data.
Examples:
 Big endian
Description Floating data
Decimal value 212.5
Hexadecimal value 43 54 80 00
Data sent by communications 43 54 80 00
 Little endian
Description Floating data
212.5
Decimal value
❑ Digital signals
 Modbus address
Modbus address of the slave device. It can take values between 1 and 128.
 Modbus signal
Initial memory address of the signal to be read in the slave device database.
 Type
Type of signal to be read. See the “Digital signals” section of this manual.
 No. of registers
It is the number of signals or the number of registers to be read, depending on the type of signal.
Relay status, Device status or Input status: number of signals.

User Manual
216
Digital signal (16 signals / WORD) or Digital signal (1 signal / WORD): number of registers.
 Internal ID
It indicates the first position in the master internal communication database on which these signals will be mapped. The
automatic assignment must be used by clicking on the button highlighted in red in the image, Set internal IDs
❑ Measurements
 Modbus address
 Modbus measurement
First memory address of the measurement to be read in the slave device database.
 Type
Type of measurement to be read. See the “Measurements” section of this manual.
 Format
Format of the measurement to be read. See the “Measurements” section of this manual.
 Swapping
Possible values: No swap, Byte Word swap, Byte swap and Word swap. Default value: No swap.
It indicates the order in which the slave device sends data greater than one byte. Usually used for measurements and / or
32bit counters.
Examples:
 No swap
Description Integer data
Decimal value 70000
This is the most usual option.

User Manual
217
 Byte Word swap
Decimal value 70000
 Byte swap
Decimal value 70000
 Word swap
Decimal value 70000
 No. of elements
It is the number of measurements to be read from the “Modbus measurement” field.
 Scale factor
The measurement value in the internal database is the value read multiplied by the scale factor.
By double-clicking on this field, it appears a screen for the scale factor configuration for this measurement.

User Manual
218
 Internal ID
It indicates the first position in the master internal communication database, where these measurements will be mapped.
The automatic assignment must be used by clicking on the button highlighted in red in the image, Set internal IDs.
❑ Counters
 Modbus address
 Modbus counter
Initial memory address of the counters to be read in the slave device database.
 Format
Format of the counters to be read. See the “Counters” section of this manual.
 Swapping
Possible values: No swap, Byte Word swap, Byte swap and Word swap. Default value: No swap.
It indicates the order in which the slave device sends data greater than one byte. Usually used for measurements and / or
32 bit counters.
Examples:
 No swap

User Manual
219
Decimal value 120000
Hexadecimal value 00 01 D4 C0
Data sent by communications 00 01 D4 C0
This is the most usual option.
 Byte Word swap
Data sent by communications C0 D4 01 00
 Byte swap
Data sent by communications 01 00 C0 D4
 Word swap
Data sent by communications D4 C0 00 01
 No. of elements
It is the number of counters to be read from the “Modbus counter” field.

User Manual
220
 Scale factor
The counter value in the internal database is the value read, multiplied by the scale factor.
By double-clicking on this field, it appears a screen for the scale factor configuration for that counter.
 Internal ID
It indicates the first position in the master internal communication database where these counters will be mapped. The
automatic assignment must be used by clicking on the button highlighted in red in the image, Set internal IDs.
❑ Commands
 Modbus address
 Command No.
Number of command in the master internal database (0-3071).
 Modbus command
Modbus address for the command to be executed.
 Value
Value to be written on the Modbus command field.
23.6.2 Configuration example

Database of the device to be integrated:

User Manual
221
❑ Big endian
❑ Events request: No
❑ Synchronization: No
❑ Signals to be read
 From address 0
 Number of signals: 2
 Type: Digital outputs
❑ Measurements to read
 From address 0
 Number of measurements: 2
 Format: 16-bit unsigned
 Swapping: No swap
 Scale factors
▪ Measurement 0: 0.1
 From address 40
 Format: 16-bit signed
 Scale factors
 From address 66
 Scale factors
▪ Measurement 0: 1
 From address 500
 Format: 32-bit signed
 Scale factors
 From address 530
 Format: float
 Scale factors
❑ Counters to read
 From address 60
 Number of counters: 4

User Manual
222
 Scale factors
▪ Counter 0: 0.001
▪ Counter 1: 0.001
▪ Counter 2: 0.001
▪ Counter 3: 0.001
❑ Commands to execute
 Number of command 0
 Address: 0
 Value: 255
With this configuration, digital output 1 is activated.
 Address: 1
 Value: 255
With this configuration, digital output 2 is activated.
 Address: 0
 Value: 0
With this configuration, digital output 1 is deactivated.
 Address: 1
 Value: 0
With this configuration, digital output 2 is deactivated.
Database configuration:
❑ IED
❑ Digital signals
❑ Measurements

User Manual
223
❑ Counters
❑ Commands
23.7 SERIAL MESSAGES
The format of the serial communication messages used by the Modbus Master protocol is shown below, with the functions used by the
device as an example.
23.7.1 Format
❑ Master request:
 Remote address - 1 byte
 Function code - 1 byte
 Data - variable number of bytes
 CRC - 2 byte
❑ Slave response:
 Data – variable number of bytes

User Manual
224
 CRC - 2 byte
Remote address: Modbus address (Value between 1 and 128). Broadcast messages (address 0) are not allowed.
Function code: If it is > 127 (bit MSB to 1) it means that the remote has not performed the required function and will answer with
an error code.
CRC: LSB is sent first, followed by the MSB.
CRC generator (polynomial): x16 + x15 + x2 +1
23.7.2 Examples
❑ Function code 01 – Read n output bits
❑ Example:
 Remote address: 1
 Request of 12 output bits, from output 3 to 14 (All of these bits are activated)
Table 81 Request
Description Bytes Example (Hex)
Remote address 1 0x01
Function code 1 0x01

0x00
Starting address 2
0x03 Start reading on digital output 3
0x00
Number of digital outputs 2
0x0C Reading of 12 digital outputs
CRC 2 xx xx
Table 82 Response

0x02
Byte count 1
2 bytes
0x0F
Outputs status 2
0xFF
CRC 2 xx xx
❑ In the request response, the LSB of the Outputs status byte contains the value of the first output (output 3). The rest of the
bytes are sent in lowest to highest order. If the number of bits requested is not a multiple of 8, the byte will be filled with
zeros.
❑ Function code 02 – Read n input bits
❑ Request and response frames are identical to the function 01.
❑ Function code 03 – Read n output words
❑ To read digital signals, measurements and counters.
❑ Example:

User Manual
225
 Address: 0400h - Data: 00AAh

 Address: 0401h - Data: 00FFh
Table 83 Request

0x04
Starting address 2
0x00
0x00
Number of registers (words) 2
0x02
CRC 2 xx xx
Table 84 Response

0x04
Byte count 1
2 registers = 4 bytes
0x00
Register value 1 2
0xAA Value in address 0x400
0x00
Register value 2 2
0xFF Value in address 0x401
CRC 2 xx xx
❑ Function code 04 – Read n input words

❑ For reading digital signals, measurements and counters.
❑ Function code 05 – One-bit writing
❑ For writing a bit to ON or OFF.
❑ Example:
 Writing command number 24 to 1

User Manual
226
Table 85 Request

0x00
Command number 2
0x18
0xFF
Output value 2
0x00 Writing to 1
CRC 2 xx xx
Table 86 Response

0x00
Command number 2
0x18
0xFF
Output value 2
0x00 Writing to 1
CRC 2 xx xx
❑ Function code 07 – Read exception status

❑ Quick reading of a byte.
❑ Example:
Table 87 Request
CRC 2 xx xx
Table 88 Response
Output data 1 0x6D
CRC 2 xx xx
❑ Function code 16 – Write multiple registers

User Manual
227
Writing of values on the device.
Example:
Table 89 Request

0x00
Starting address 2
0x80
0x00
0x01
0x02
Byte count 1
1 register = 2 bytes
0x00
Register value 2
0x18 Number of command to execute
CRC 2 xx xx
Table 90 Response

0x00
Starting address 2
0x80
0x00
0x01
CRC 2 xx xx

User Manual
228
MODBUS SLAVE PROTOCOL
24. MODBUS SLAVE PROTOCOL

Available since 6.2.19.0 version of firmware and 8.3.0.5 of CID.
24.1 INTRODUCTION
The device has a Modbus slave protocol which can communicate with a telecontrol station or with any system that works as a master.
The device has two types of communication:
❑ RTU (Remote terminal unit): Asynchronous serial communication, with a start bit, 8 bits of data and configurable parity and stop
bits.
❑ TCP/IP: Uses a TCP/IP network connecting through the registered port 502.
The protocol allows sending digital signals, measurements and counters to the master. It also allows the synchronization of the device
and the execution of commands.
A configuration table, generated with a software tool dedicated to this effect, will indicate the number of information elements that
the equipment has.
The following are detailed:

❑ Protocol profile
❑ Control processes
❑ Equipment address map
❑ Data format
❑ Configuration software tool
❑ Modbus messages supported (serial and TCP/IP)
 No
 Yes
❑ Modbus address: Modbus address of the slave device. Value between 1 and 128.
❑ Port number: It allows to set the communication channel
 COM1
 COM2
 COM3
 COM4
 COM5
 COM6
 Ethernet
❑ TCP listen port: It allows to set a number of network port to communicate via TCP/IP. Value between 0 and 65535. Default value
502.

User Manual
229
❑ Comm speed(bauds): It allows to set the speed of the serial transmission

 600 baud
 1200 baud
 2400 baud
 4800 baud
 9600 baud
 19200 baud
 38400 baud
 57600 baud
❑ Parity: It allows to select the type of parity to use in the transmission
 None
 Even
 Odd
❑ Number of stop bits:
 1Bit
 2Bit
❑ Communication control: It allows to select the type of communication channel
 RS232_FO
 RS485
❑ RTS activation delay time (ms): Minimum waiting time to activate the RTS and start the transmission. Value between 0 and 5000.
❑ CTS max delay (ms): How much time the device will wait to activate the CTS after the activation of the RTS. Value between 0 and
10000.
❑ Carrier stabilization (ms): Waiting time to start the transmission, once CTS has been detected, in order to stabilize the carrier. Value
between 0 and 5000.
❑ RTS dropoff time (ms): This is the time that the RTS signal keeps activated after the transmission of the last byte. Value between 0
and 5000.
❑ Change wait time (s): Waiting time in queue of the changes configured in the protocol tables before starting their treatment. It only
makes sense if signals from different IEDs are configured for their previous chronological ordering.
❑ Request for changes: It allows to set if the master device makes the request for changes to the slave equipment
 No
 Yes
❑ Data transmission type: It allows to set the order of the data to be transmitted
 Big endian
 Little endian
❑ Permission to synchronize: It allows to set if the master device makes the synchronization of the slave equipment
 No
 Yes
❑ Server IP address: It filters the possible connections available in the slave device configuring an IP. Possible values in the IP address
range. The value 255.255.255.255 allows connecting to any available connection

User Manual
230
Table 91. Modbus slave protocol settings
Data Setting Min. Max. Step Possible values Type

DirEnl Modbus address 1 128 1 int32
COM1
COM2
COM3
Port Port number COM4 Enum
COM5
COM6
Ethernet
TcpPort TCP listen port 0 65535 1 int32
600 baud
1200 baud
2400 baud
4800 baud
BaudRate Comm speed (bauds) Enum
9600 baud
19200 baud
38400 baud
57600 baud
Stopbit Number of stop bits 1Bit / 2 Bit Enum
RS232_FO
ChType Communication control Enum
RS485
ActRtsTmms RTS activation delay time (ms) 0 5000 10 int32
ActCtsTmms CTS max delay (ms) 0 10000 10 int32
CarTmms Carrier stabilization (ms) 0 5000 10 int32
DesRtsTmms RTS dropoff time (ms) 0 5000 10 int32
EspColTms Change wait time (s) 0 20 1 int32
SolicChgs Request for changes NO/YES Boolean
Big endian
Endianness Data transmission type Enum
Little endian
SynEna Permission to synchronize NO/YES Boolean
IPRTU Server IP address 0 65535 1 IP

User Manual
231
24.3 PROTOCOL PROFILE
24.3.1 Implemented functions in Modbus RTU

The implemented functions for serial communication are shown below:
Function
Description Use
Code
This function code is used to read contiguous status of

01 Read Coils
signals in a remote device
This function code is used to read the contents of a
contiguous block of registers in a remote device

This function code is used to write a single output to either

05 Write Single Coil
ON or OFF in a remote device
Writes a single register in a remote device (it is used to
06 Write Single Register
execute commands)
15 Write Multiple Coils
16 Write Multiple Registers
execute commands)
24.3.2 Implemented functions in Modbus TCP/IP

The implemented functions for TCP/IP communication are shown below:
Function
Description Use
Code

01 Read Coils


05 Write Single Coil
06 Write Single Register
execute commands)
15 Write Multiple Coils
16 Write Multiple Registers
execute commands)

User Manual
232
24.3.3 Exception codes

The protocol has the following exception codes:
Function Description Meaning

Code
The function code received in the query is
01 Illegal function
unknown by the server
The data address received in the query is not an
02 Illegal data address
allowable address for the server
A value contained in the query data field is not

03 Illegal data value
an allowable value for server
The server is processing other task. The client
06 Server device busy should retransmit the message later when the
server is free
24.4 CONTROL PROCESSES
24.4.1 Request for equipment status

Two functions can be used:
❑ Function 03
❑ Reading a register on 0000h address (see "Equipment address map" section of this manual). The device respond is a byte
with the LOCAL/REMOTE STATE of the device.
❑ Function 04
❑ It works the same way as Function F03.
24.4.2 Request for digital signals

The following functions can be used:
❑ Function 01
❑ Reading boolean data.
❑ Function 02
❑ Reading boolean data.
❑ Function 03
❑ Reading registers.
❑ Function 04
❑
Address range:
 Digital signals: 0400h - 0480h
24.4.3 Request for measurements and counters


User Manual
233
❑ Function 03
❑ Function 04
❑
Address range:
 Integer measurements: Address range 0480h - 0580h

 Counters: Address range 0580h - 0680h
 Floating type measurements: Address range 0700h - 0900h
24.4.4 Request for digital signal changes

The master device can get the information of all digital signal changes of the slave device, with the instant of time in which they
have happened. The process to do it is the following:
❑ Reading the address 0680h gets the number of changes to send by the slave device
❑ To obtain the information of the changes, reading the quantity of "number of changes x 5" on address 0682h is needed.
Reading range 0682h - 06FFh.
❑ The maximum quantity of registers that can be read is 125. This is the same as reading 25 changes since the information of
a digital signal change is stored in 5 registers. The number of registers to be read must be multiple of 5.
❑ Signal change structure format:
Number
MSB LSB
of Address
(Most Signifant Byte) (Least Significant Byte)
change (n)
0682h e v E V Bits and Signal number Signal number
0683h Milliseconds Milliseconds
n=1 0684h Hours Minutes
0685h Month Day of the week and day of the month
0686h --- Year
1 < n < 25 … … …
06FBh e v E V Bits and Signal number Signal number
06FCh Milliseconds Milliseconds
n = 25 06FDh Hours Minutes
06FEh Month Day of the week and day of the month
06FFh --- Year
 Signal number: It is stored in the first byte of the information of a digital signal change and in the first four bits of the
next byte.
 V Bit: Validity of the signal after its change (0: valid / 1: invalid)
 E Bit: State of the signal after its change (0 / 1)
 v Bit: It indicates if the signal change is due to a change in the validity V (0 / 1)
 e Bit: It indicates if the signal change is due to a change in the state E (0 / 1)
 Milliseconds: It is stored in the second register of the information of a signal change. Range of values 0 - 59999.
 Minutes: It is stored in the first byte of the third register of the information of a signal change. Range of values 0 - 59.
 Hours: It is stored in the second byte of the third register of the information of a signal change. Range of values 0 - 23.
 Day of the month: It is stored in the first byte of the fourth register of the information of a signal change. Its value is
registered in the first five bits of that byte. Range of values 1 - 31.
 Day of the week: It is stored in the first byte of the fourth register of the information of a signal change. Its value is
registered in the last three bits of that byte. Range of values 1 - 7.

User Manual
234
 Month: It is stored in the second byte of the fourth register of the information of a signal change. Range of values 1 -
12.
 Year: It is stored in the fifth register of the information of a signal change. Range of values 0 - 99.
❑ Writing the value 0 in address 0681h the last signal changes sent are validated. This means that the signal changes of the
device are considered as sent.
❑ If the signal changes are not validated, the device will consider that they have not been sent.
❑ If the device had more signal changes it will indicate it in the address 0680h and the master station could request them
repeating the process
❑ To read all the signal changes of the device, the process must continue until the reading of the address 0680h indicates
value 0
The requests are made with functions F03 and F04 and the writings with function F16.
24.4.5 Requesting data via memory map

The data of the configured addresses can be read in a single request. The addresses can be non-consecutive.
Functioning:
❑ The configured addresses must be written using function F16. Range of the writing area 0180h - 01FCh
❑ The data of the configured addresses must be read using function F03 or F04. Range of the reading area 0100h - 017Ch
❑ Up to 124 registers can be read and written
❑ The configured addresses must be in the range 0400h - 0680h and 0700h - 0900h
❑ To read the data of the configured addresses, the following must be taken into account:
 The position in the reading area from which to request the data, must be the same as the position in the writing area
where the configured addresses have been written
 Example:
 For a writing in address 0185h the reading has to be in address 0105h.
 Writing
 Writing address: 0185h
 Position in the writing area: 0185h - 0180h(initial address) = 0005h
 Reading
 The reading address must be: 0105h
 Position in the reading area: 0105h - 0100h(initial address) = 0005h
 The number of registers to be requested must be equal to the number of registers that add up the data of the
configured addresses
 Example:
 For a writing in address 0185h of the address 0400h, 0486h and 0581h the number of registers to be requested must
be 4.
 It must be ask for a register for the signals, another for the measurements of integer type and two registers for the
counters.
 Writing
 Writing address: 0185h
 Addresses configured:
▪ 0400h: First word of digital signals
▪ 0486h: Seventh measurement of integer type
▪ 0581h: Second counter
 Reading
 Reading address: 0105h
 The number of registers to request must be 4:

User Manual
235
▪ 0400h: Occupies a register (G9)

▪ 0486h: Occupies a register (G10)
▪ 0581h: Occupies two registers (G11)
 See section "Equipment address map" and "Data format" for G9, G10 and G11.
24.4.6 Synchronization
To synchronize the device it must be written with the function F16 the following information in the address 00F0h:
MSB LSB
Address
(Most Signifant Byte) (Least Significant Byte)
00F0h Milliseconds Milliseconds
00F1h Hours Minutes
00F2h Month Day
00F3h - Year
 To synchronize the device the four words must always be written. The partial writing of some data is not allowed, it is
always necessary to write the whole structure
 It is possible to read the address 00F0h to get the current time of the equipment. Any register can be read as long as
the range does not exceed the address 00F3h. For reading, functions F03 or F04 must be used
24.4.7 Command execution

❑ Function F05
❑ It allows the execution of commands to OFF and ON in the slave device database.
 For an OFF command it must be sent the number of command to execute and the operation value field to 0x0000.
 For an ON command it must be sent the number of command to execute and the operation value field to 0xFF00.
❑ Function F06
❑ It allows the execution of commands to ON in the slave device database.
 It must be written the number of command to execute in the address 0080h.
❑ Function F15
❑ It allows the execution of commands to OFF and ON in the slave device database.
 For an OFF command it must be sent the number of command to execute, the number of coils to be forced to one and
the operation value field to 0.
 For an ON command it must be sent the number of command to execute, the number of coils to be forced to one and
the operation value field to 1.
 It is only allowed the writing of one coil.
❑ Function F16
❑ It allows the execution of commands to ON in the slave device database.
 It must be written the number of command to execute in the address 0080h.
 It is only allowed the writing of one register.
Range of number of command to execute: 0 - 511
24.5 EQUIPMENT ADDRESS MAP
Distribution of the equipment address map:

User Manual
236
Register Memory
Description Length (words)
address(hex) zone
Identification of the equipment
0000 Device status 1 G1
Command address (*)
0080 Number of command to be executed 1 G2
System date
00F0 Milliseconds 1 G3
00F1 Hours and minutes 1 G4
00F2 Month and day 1 G5
00F3 Year 1 G6
User map
0100 User map values 124 G7
0180 User map addresses 124 G8
Reading zone
0400 Digital signal states 128 G9
0480 Measurements 256 G10
0580 Counters 256 G11
Digital signal changes zone
0680 Number of changes to be sent 1 G12
0681 Validation of sent changes (*) 1 G13
0682 Digital signal changes reading zone 125 G14
Reading zone
0700 Measurement 512 G15
Free memory zone
0900 Free
0HF Free
(*) Only for writing
The values of the Memory zone column are explained in the "Data format" section.

User Manual
237
24.6 DATA FORMAT
Data format depending on the memory zone (see section "Equipment address map"):
Memory
Format Description
zone
READING AREA OF THE DEVICE MODE
In the bit 0 LOCAL/REMOTE STATE of the device is indicated
G1 16 bits Value 0: REMOTE STATE
Value 1: LOCAL
Size of the area: A register (word)
WRITING AREA OF THE NUMBER OF COMMAND TO BE EXECUTED IN THE SLAVE DEVICE
DATABASE
G2 16 bits
Range of values: 0 - 511
MILLISECONDS READING AREA
G3 Unsigned 16 bits Range of values: 0 - 59999
READING AREA OF MINUTES AND HOURS
- Minutes: 0 to 7 bits
G4 16 bits
- Hours: 8 to 15 bits
READING AREA OF THE DAY OF THE WEEK AND MONTH
- Day: 0 to 7 bits
G5
16 bits - Month: 8 to 15 bits
READING AREA OF THE YEAR
- Year: 0 to 7 bits
G6 16 bits Range of values: 0 - 99
- It is not used: 8 to 15 bits
READING AREA OF THE VALUES OF THE CONFIGURED DATA ADDRESSES
- The unsigned 16 bits format is used for reading signals
16 bits - The signed 16 bits format is used for reading integer measurements
G7
Unsigned 32 bits - The unsigned 32 bits format is used for reading counters
Float - The Float format is used for reading floating type measurements
Size of the area: 124 registers (words)
WRITING AREA OF THE CONFIGURED ADDRESSES
G8 16 bits Range of values: 0400h - 0680h and 0700h - 0900h
READING AREA OF SIGNALS
G9 16 bits Compacted bits. A bit to 0 value means signal deactivated and to value 1 activated
READING AREA OF INTEGER MEASUREMENTS
G10 Signed 16 bits
READING AREA OF COUNTERS
G11 Unsigned 32 bits
READING AREA OF SIGNAL CHANGES TO BE SENT
G12 16 bits
WRITING AREA OF VALUE 0 TO VALIDATE THE SIGNAL CHANGES THAT HAS BEEN SENT
G13 16 bits
SIGNAL CHANGES INFORMATION AREA
G14
Unsigned 16 bits For more information go to the section "Request for digital signal changes"
Size of the area: 125 registers (word)
READING AREA OF FLOATING TYPE MEASUREMENTS
G15 Float

User Manual
238
24.7 CONFIGURATION SOFTWARE TOOL
The Modbus slave protocol is configured with the "Modbus Slave Configurator" available in the PacFactory configuration SW and the
EFS tools. This tool generates a configuration file that is sent to the device.
24.7.1 Fields to be configured

❑ Digital signals
 Modbus address
The number of the signal in the Modbus slave database. Range of values 0 - 2047.
 Internal IED
The address of the remote device from which read the signals. Range of values 0 - 32. The value 0 is the address of the
device itself.
 Internal ID
The number of the signal in the slave device database. It must be selected by clicking on button and choosing the signal
to be read. This signal will be mapped to the position indicated by Modbus address.
 Description
It doesn´t need to be configured. The own tool does it.
 IEC-61850 ref
 Inverted
 It allows to invert the value of the signal.
❑ Measurements
 Modbus address
The number of the measurement in the Modbus slave database. Range of values 0 - 255.
 Internal IED
The address of the remote device from which read the measurements. Range of values 0 - 32. The value 0 is the address of
the device itself.
 Internal ID
The number of the measurement in the slave device database. It must be selected by clicking on button and choosing
the measurement to be read. This measurement will be mapped to the position indicated by Modbus address.

User Manual
239
 Description
 It doesn´t need to be configured. The own tool does it.
 IEC-61850 ref
 It doesn´t need to be configured. The own tool does it.
❑ Counters
 Modbus address
The number of the counter in the Modbus slave database. Range of values 0 - 127.
 Internal IED
The address of the remote device from which read the counters. Range of values 0 - 32. The value 0 is the address of the
device itself.
 Internal ID
The number of the counter in the slave device database. It must be selected by clicking on button and choosing the
counter to be read. This counter will be mapped to the position indicated by Modbus address.
 Description
 IEC-61850 ref
❑ Commands
❑ There are two options for the execution of commands depending on the function that is used (go to the section
"Command execution" for more detail): Commands to ON and to OFF/ON.
❑ The default configuration allows executing ON commands only.
❑ COMMANDS TO ON:
 Command
Number of the command in the Modbus slave database. Range of values: 0 - 511.
 Internal IED
The address of the remote device in which execute the commands. Range of values 0 - 32. The value 0 is the address of the
device itself.
 Internal ID

User Manual
240
The number of the command in the slave device database. It must be selected by clicking on button and choosing the
command to execute. The execution of this command is a consequence of the activation of the command number that
appears in the field Command.
 Description
 IEC-61850 ref
 ON/OFF
 Origin
It is the origin from where the commands are executed.
 COMMANDS TO ON AND OFF:

To execute commands to OFF the option in the "Modbus Slave Configurator" must to be enabled.
To do this, go to the "View" menu, click on "Options…" and the following image appears:
Enabling "Show OFF command" option in Modbus Slave and clicking on OK the following image where commands to ON
and OFF are configured is shown:

User Manual
241
 Command
Number of the command in the Modbus slave database. Range of values: 0 - 511.
 Internal IED
The address of the remote device in which execute the commands. Range of values 0 - 32. The value 0 is the address of the
device itself.
 Internal ID(ON)
command to execute. The execution of this command is a consequence of the activation of the command number that
appears in field Command.
 Description (ON)
 IEC-61850 ref (ON)

 ON/OFF (ON)
 Internal ID(OFF)
command to execute. The execution of this command is a consequence of the deactivation of the command number that
appears in field Command.
 Description (OFF)
 IEC-61850 ref (OFF)

 ON/OFF (OFF)
 Origin
It is the origin from where the commands are executed.
24.7.2 Configuration example

Below is an example of a Modbus slave database. This database contains elements which the master device can read or in which
can write.
Elements of the Modbus slave database:
❑ 10 digital signals
❑ 5 measurements
❑ 5 counters
❑ 4 commands

User Manual
242
Database configuration:
❑ Digital signals
 This configuration allows the access to:

 The state of eight digital inputs of the input/output board 1 of the device, which value is stored in the first eight
positions of the Modbus slave signal database.
 The state of two digital inputs of the input/output board 2 of the device, storing the state of the first input in the
position 15 of the Modbus slave signal database and the state of the second input in the position 31.
❑ Measurements
❑ This configuration allows the access to:

 Five logical measurements of the device, whose value is stored in the positions 0,3,7,8 and 9 of the Modbus slave
measurements database.
❑ Counters
❑ This configuration allows the access to:

User Manual
243
 Five logical counters of the device, whose value is stored in the positions 0, 5, 10, 15 and 20 of the Modbus slave
counters database.
❑ Commands
❑ This configuration allows:

 Activate the digital output 1 of the input/output board 1 of the device, activating the command number 0 of the
Modbus slave database.
 Activate the digital output 2 of the input/output board 2 of the device, deactivating the command 10 of the Modbus
slave database.
24.8 SERIAL MESSAGES
The format of the serial communication messages used by the Modbus slave protocol is shown below, with the functions used by the
device as an example.
24.8.1 Format
❑ Master request:
 CRC - 2 byte
❑ Slave response:
 CRC - 2 byte

Remote address: Modbus address (Value between 1 and 128). Broadcast messages (address 0) are not allowed.
Function code: If it is > 127 (bit MSB to 1) it means that the remote device has not performed the required function and will answer
with an error code.
CRC: LSB is sent first, followed by the MSB.

User Manual
244
24.8.2 Examples
❑ Function code 01 – Read coils
❑ For reading boolean data.
❑ Example:
 Request of 12 output bits, from output 3 to 14 (All of these bits are activated)
Table 92. Request

Address of the first digital 0x00
2
output 0x03
0x00
Number of digital outputs 2
0x0C
CRC 2 xx xx
Table 3. Response

Number of bytes to store
the state of the digital 1 0x02
outputs
0xFF (LSB)
Digital outputs value 2
0x0F (MSB)
CRC 2 xx xx
❑ In the request response, the LSB of the Digital outputs value contains the value of the first output (output 3). The rest of
the bytes are sent in lowest to highest order. If the number of bits requested is not a multiple of 8, the byte will be filled
with zeros.
❑ Function code 02 – Read discrete inputs
❑ For reading boolean data.
❑ Function code 03 – Read holding registers
❑ Example:
 Address: 0400h - Data: 00AAh
 Address: 0401h - Data: 00FFh

User Manual
245
Table 4. Request

0x04
Starting address 2
0x00
0x00
0x02
CRC 2 xx xx
Table 5. Response
Byte count 1 0x04
0x00
Register value 1 2
0xAA
0x00
Register value 2 2
0xFF
CRC 2 xx xx
❑ Function code 04 – Read input registers

❑ Function code 05 – Write single coil
❑ For writing a bit to ON or OFF.
❑ Example:
Table 6. Request

0x00
Command number 2
0x18
0xFF
Writing to 1 2
0x00
CRC 2 xx xx

User Manual
246
Table 7. Response

0x00
Command number 2
0x18
0xFF
Writing to 1 2
0x00
CRC 2 xx xx
❑ Function code 06 – Write single register

For writing a single register.
Example:
Table 8. Request

0x00
Register address 2
0x80
0x00
Number of command to execute 2
0x18
CRC 2 xx xx
Table 9. Response

0x00
Register address 2
0x80
0x00
0x18
CRC 2 xx xx
❑ Function code 15 – Write multiple coils

For writing a bit to ON or OFF.
Example:

User Manual
247
Table 10. Response
Function code 1 0x0F

0x00
Number of command 2
0x18
Number of bits to 0x00
2
be forced 0x01
Byte count 1 0x01
Command value 1 0x01
CRC 2 xx xx
Table 11. Request
Function code 1 0x0F

0x00
Number of command 2
0x18
0x00
Number of forced bits 2
0x01
CRC 2 xx xx
❑ Function code 16 – Write multiple registers

For writing a single register.
Example:
Table 12. Request

0x00
Register address 2
0x80
Number of registers to be 0x00
2
written (words) 0x01
Byte count 1 0x02
0x00
0x18
CRC 2 xx xx

User Manual
248
Table 13. Response

0x00
Starting address 2
0x80
Number of written registers 0x00
2
(words) 0x01
CRC 2 xx xx
24.9 TCP/IP MESSAGES
24.9.1 Format
The message contains the following elements:
❑ Header
❑ It contains the following fields:
Length
Fields Description Client Server
(bytes)
Identification of a Modbus Recopied by the
Transaction Initialized by the
2 request/response server from the
identifier client
transaction received request
Recopied by the
Protocol It takes value 0 for Initialized by the
2 server from the
identifier Modbus protocol client
received request
Number of following Initialized by the Initialized by the

Length 2
bytes client (request) server (response)
Recopied by the
Identification of the Initialized by the
Unit identifier 1 server from the
connected slave device client
received request
❑ This fields are transmitted by communications as Big Endian.

❑ Function code
❑ Function code of the request/response. Size: 1 byte. If it is > 127 (bit MSB to 1) it means that the remote has not
performed the required function and will answer with an error code.
❑ Data
TCP/IP complete message:
Transaction Protocol
Length Unit identifier Function code Data
identifier identifier
(2 bytes) (1 byte) (1 byte) (n bytes)
(2 bytes) (2 bytes)
All the messages are sent via TCP to registered port 502.
❑ Master request:

User Manual
249
 Transaction Id. - Unique per transaction or 0x00

 Protocol Id. - Always 0
 Length - Number of bytes of Unity Id. + Function code + Data
 Unity Id. - Possible values: 0x00,0xFF or remote device number
 Function code
 Data - Number of variable bytes
❑ Slave response:
 Transaction Id. - Copy of the value received from the master device
 Protocol Id. - Copy of the value received from the master device
 Length - Number of bytes of Unity Id. + Function code + Data
 Unity Id. - Copy of the value received from the master device
 Function code
 Data - Number of variable bytes
24.9.2 Examples
The types of message are the same as the serial ones. The address map of the device and the way to treat it is the same as explained
before, only changes the structure of the message to send/receive.

User Manual
250
MEASUREMENT LIST 
25. MEASUREMENT LIST

The following tables show the list of available measurements. If the model doesn´t have a function, the measurements of that unit are no
available.
Table 93. General measurements
Measurement Node Instance Data Attribute Refresh (ms)

VA MMXU 1 PhV phsA 100
VB MMXU 1 PhV phsB 100
VC MMXU 1 PhV phsC 100
VN MMXU 1 PhV neut 100
AVERAGE V MMXU 1 PhV net 100
VAB MMXU 1 PPV phsAB 100
VBC MMXU 1 PPV phsBC 100
VCA MMXU 1 PPV phsCA 100
AVERAGE U MMXU 1 PPV (PPVm in Ed2) net 100
IN MMXU 1 A neut 100
IA MMXU 1 A phsA 100
IB MMXU 1 A phsB 100
IC MMXU 1 A phsC 100
AVERAGE I MMXU 1 A net 100
ACTIVE POWER P MMXU 1 TotW mag 100
REACTIVE POWER Q MMXU 1 TotVAr mag 100
POWER S MMXU 1 TotVA mag 100
Frequency MMXU 1 Hz net 2
Phase A Active Power MMXU 1 W phsA 100
Phase B Active Power MMXU 1 W phsB 100
Phase C Active Power MMXU 1 W phsC 100
Phase A Reactive Power MMXU 1 VAr phsA 100
Phase B Reactive Power MMXU 1 VAr phsB 100
Phase C Reactive Power MMXU 1 VAr phsC 100
Phase A S Power MMXU 1 VA phsA 100
Phase B S Power MMXU 1 VA phsB 100
Phase C S Power MMXU 1 VA phsC 100
Fault phase A Current MMXU 1 FltA phsA 1000
Fault phase B Current MMXU 1 FltA phsB 1000
Fault phase C Current MMXU 1 FltA phsC 1000
Fault Neutral Current MMXU 1 FltA neut 1000
Max. fault phase A Current MMXU 1 MaxFltA phsA 1000
Max. fault phase B Current MMXU 1 MaxFltA phsB 1000
Max. fault phase C Current MMXU 1 MaxFltA phsC 1000
Max. fault Neutral Current MMXU 1 MaxFltA neut 1000
Cosine phi rms phase A MMXU 1 PF phsA 100
Cosine phi rms phase B MMXU 1 PF phsB 100
Cosine phi rms phase C MMXU 1 PF phsC 100
Cosine phi rms average MMXU 1 PF net 100
Average Power Factor MMXU 1 TotPF mag 100

Table 94. Fundamental measurements

IA fundamental FUNMMXU 1 FunA phsA 100
IB fundamental FUNMMXU 1 FunA phsB 100
IC fundamental FUNMMXU 1 FunA phsC 100
IN fundamental FUNMMXU 1 FunA neut 100
VA fundamental FUNMMXU 1 FunPhV phsA 100
VB fundamental FUNMMXU 1 FunPhV phsB 100
VC fundamental FUNMMXU 1 FunPhV phsC 100
VN fundamental FUNMMXU 1 FunPhV neut 100
Cosine phi phase A (fund) FUNMMXU 1 FunPF phsA 100
Cosine phi phase B (fund) FUNMMXU 1 FunPF phsB 100
Cosine phi phase C (fund) FUNMMXU 1 FunPF phsC 100
Cosine phi average (fund) FUNMMXU 1 FunPF net 100
ACTIVE POWER P (fund) FUNMMXU 1 FunTotW mag 100
REACTIVE POWER Q (fund) FUNMMXU 1 FunTotVAr mag 100
POWER S (fund) FUNMMXU 1 FunTotVA mag 100
Phase A Active P (fund) FUNMMXU 1 FunW phsA 100
Phase B Active P (fund) FUNMMXU 1 FunW phsB 100
Phase C Active P (fund) FUNMMXU 1 FunW phsC 100
Phase A Reactive Q (fund) FUNMMXU 1 FunVAr phsA 100
Phase B Reactive Q (fund) FUNMMXU 1 FunVAr phsB 100
Phase C Reactive Q (fund) FUNMMXU 1 FunVAr phsC 100
Phase A S (fund) FUNMMXU 1 FunVA phsA 100
Phase B S (fund) FUNMMXU 1 FunVA phsB 100
Phase C S (fund) FUNMMXU 1 FunVA phsC 100
Table 95. Instantaneous Fundamental measurements

Analog 1 PHSMMXU 1 OpPhasor1 phsA 100
Analog 2 PHSMMXU 1 OpPhasor2 phsB 100
Analog 3 PHSMMXU 1 OpPhasor3 phsC 100
Analog 4 PHSMMXU 1 OpPhasor4 neut 100
Analog 8 PHSMMXU 1 OpPhasor8 neut 100
Analog 12 PHSMMXU 1 OpPhasor12 net 100
Table 96. Energy counter

Active Energy Out MMTR 1 SupWh actVal 100
Active Energy In MMTR 1 DmdWh actVal 100
Reactive Energy Out MMTR 1 SupVArh actVal 100
Reactive Energy In MMTR 1 DmdVArh actVal 100

Table 97. Sequences

I0 MSQI 1 SeqA c1 2
V0 MSQI 1 SeqV c1 2
I1 MSQI 1 SeqA c2 2
V1 MSQI 1 SeqV c2 2
I2 MSQI 1 SeqA c3 2
V2 MSQI 1 SeqV c3 2
Table 98. THD

THD phase A Current MHAI 1 ThdA phsA 100
THD phase B Current MHAI 1 ThdA phsB 100
THD phase C Current MHAI 1 ThdA phsC 100
THD Neutral Current MHAI 1 ThdA neut 100
THD Average Current MHAI 1 ThdA net 100
THD phase A Voltage MHAI 1 ThdPhV phsA 100
THD phase B Voltage MHAI 1 ThdPhV phsB 100
THD phase C Voltage MHAI 1 ThdPhV phsC 100
THD Neutral Voltage MHAI 1 ThdPhV neut 100
THD Averagel Voltage MHAI 1 ThdPhV net 100
Table 99. Historic Edition 1

Imax Historic phase A MSTA 1 MaxAmps phsA 1000
Imin Historic phase A MSTA 1 MinAmps phsA 1000
Imax Historic phase B MSTA 1 MaxAmps phsB 1000
Imin Historic phase B MSTA 1 MinAmps phsB 1000
Imax Historic phase C MSTA 1 MaxAmps phsC 1000
Imin Historic phase C MSTA 1 MinAmps phsC 1000
Vmax Historic phase A MSTA 1 MaxVolts phsA 1000
Vmin Historic phase A MSTA 1 MinVolts phsA 1000
Vmax Historic phase B MSTA 1 MaxVolts phsB 1000
Vmin Historic phase B MSTA 1 MinVolts phsB 1000
Vmax Historic phase C MSTA 1 MaxVolts phsC 1000
Vmin Historic phase C MSTA 1 MinVolts phsC 1000
VAmax Historic MSTA 1 MaxVA net 1000
VAmin Historic MSTA 1 MinVA net 1000
Wmax Historic MSTA 1 MaxW net 1000
Wmin Historic MSTA 1 MinW net 1000
VAr max Historic MSTA 1 MaxVAr net 1000
VAr min Historic MSTA 1 MinVAr net 1000

Table 100. Historic Edition 2

Imax Historic phase A maxMMXU 1 A phsA.cVal 1000
Imin Historic phase A minMMXU 1 A phsA.cVal 1000
Imax Historic phase B maxMMXU 1 A phsB.cVal 1000
Imin Historic phase B minMMXU 1 A phsB.cVal 1000
Imax Historic phase C maxMMXU 1 A phsC.cVal 1000
Imin Historic phase C minMMXU 1 A phsC.cVal 1000
Vmax Historic phase A maxMMXU 1 PhV phsA.cVal 1000
Vmin Historic phase A minMMXU 1 PhV phsA.cVal 1000
Vmax Historic phase B maxMMXU 1 PhV phsB.cVal 1000
Vmin Historic phase B minMMXU 1 PhV phsB.cVal 1000
Vmax Historic phase C maxMMXU 1 PhV phsC.cVal 1000
Vmin Historic phase C minMMXU 1 PhV phsC.cVal 1000
VAmax Historic maxMMXU 1 TotVA mag.f 1000
VAmin Historic minMMXU 1 TotVA mag.f 1000
Wmax Historic maxMMXU 1 TotW mag.f 1000
Wmin Historic minMMXU 1 TotW mag.f 1000
VAr max Historic maxMMXU 1 TotVAr mag.f 1000
VAr min Historic minMMXU 1 TotVAr mag.f 1000

Table 101. Board 1 of RTD and analogue outputs

Temperature 1 RTDGGIO 1 Tmp1 mag 1000
Analog. output 1 RTDGGIO 1 OutAn1 mag 1000
Table 102. Board 2 of RTD and analogue outputs

Table 103. Temperature

Temperature CTSU 1 Temp net 1000
Table 104. Power supply

Power Supply GENLLN0 1 PSup net 1000
Power Supply 2 GENLLN0 1 PSup2 net 1000
Table 105. Internal battery

Internal battery LPHD 1 IntBat net 1000

PREVENTIVE MAINTENANCE 
26. PREVENTIVE MAINTENANCE

The unit continually checks the various incorporated elements and cards. If an error is detected in any of the elements or cards, an
alarm is generated.
The available signals indicate faults in the card check, in the communications between the cards, in the unit’s configuration, etc.
The detected errors are shown in:
❑ Status report
❑ Incident report
❑ Sequence of events (SOE)
❑ Digital outputs and CPU hardware alarm output.
❑ IHMI leds and status leds
The errors can be critical and non critical, depending on the effect they have in the device.
Critical errors
Critical hardware error. Indicates that a critical error has been produced. In addition to this signal, the cause that produced the signal
will be indicated.
If the error affects the unit’s operation, a critical error is generated, which in addition to the signal acts on:
❑ Colour front LED. Non-configurable status LED, which indicates the unit’s general status. If the LED is green, it indicates
that everything is correct, while if it is red it indicates a critical error in the unit.
❑ CPU Relay. Non-configurable 3-contact relay, which indicates the unit’s general status. If the LED is active (common
terminal – NO), it indicates that everything is correct, while if it is deactivated (common terminal– NC) it indicates a critical
error in the unit. If the unit is switched off, the relay is deactivated.
The causes that produce errors are:
❑ CPU error. Indicates that the check has detected an error in the CPU
❑ Analogue error. Indicates an error in transformers card.
❑ I/O micro error. Indicates an error in the I/O cards’ micro.
❑ Analogue connection error. Indicates that a fault has been produced in the communications between the CPU and the
transformers card.
❑ I/O connection error. Indicates that a fault has been produced in the communication between the CPU and an I/O card.
Additionally, it will indicate the card which has suffered the failure:
 Error card address x. Indicates that there is a communication error with the card with the address x.
❑ Front connection error. Indicates that a fault has been produced in the communications between the CPU and the unit’s
front card.
❑ Shared analogue memory error. Indicates that a fault has been produced in the Data exchange memory between the CPU
and the transformers card.
❑ Error shared I/O memory. Indicates that a fault has been produced in the Data exchange memory between the CPU and
the I/O cards.
❑ Alarm settings. Indicates that errors have been detected in the storage of the unit’s settings.
❑ FW Alarm. Indicates that the relay firmware versions are incompatible.
❑ Memory check alarm. Indicates that errors have been detected in the checking of the unit’s memory.
❑ Converter check alarm. Indicates that errors have been detected in the transformers card AD converter.
❑ Converter voltage level alarm. Indicates that errors have been detected in the transformers card reference voltages..
❑ Relay activation alarm. Indicates that an error has been detected in the activation of at least one of the I/O cards’ relays.
❑ I/O configuration error. Indicates that the configuration of the I/O cards does not coincide with the unit’s correct
configuration.

❑ General Vdc error. Indicates a failure in the internal power supply levels.
❑ For each I/O card there is are 5 signals, indicating:
 Status OK. Indicates that the card is configured correctly and without errors
 Configured & No_detected. Indicates that the card is configured by the user, but not detected in the unit. This may be
because it is not assembled or because it has an error. Equivalent to the current communication error.
 Different configuration. The type indicated by the user and the type detected by the unit do not coincide.
 No_configured & detected. Indicates that card that has not been configured by the user has been detected in an
address.
 Internal card error. A card check error has been received (includes relay check).
Non critical errors
These errors have a limited effect on the device.
❑ RTC clock error. Indicates that the check has detected an error in the real time clock.
❑ Continuous component monitoring alarm. Indicates that an error in the continuous measurement monitoring has been
detected in the transformers card.
❑ Frequency configuration error. This is not a unit failure, but rather a configuration failure. Indicates that the frequency
measurement of the signals being injected into the unit do not match the set measurement, that is, the unit is configured
as 50Hz and the signals which are being injected are greater than 55Hz; or that the unit is configured as 60 Hz and the
signals being injected are less than 55 Hz.
❑ Internal battery failure. Indicates that the data storage battery is below the security levels and that the data may be lost at
shutdown.
❑ Version compatibility error. Indicates that the versions of the unit's firmware are not correct.
❑ Time setting configuration alarm. Indicates that there is an error in the configuration of the unit’s time setting.
26.1 ERROR DETECTION
The error detection can be made by any of the indicated ways.
Status report:
Figure 110 shows the screen of the PacFactory that show the available check signals.
The example screen shows activation of critical error (HW error), generated by I/O configuration error (card 2 is not detected). It
also indicates Internal battery failure. On the other hand, it shows I/O card 1 is correct.
Incident reports and sequence of events:

The available check signals are shown in both messages.
Led and digital outputs:

The leds and digital output can be configured with any of the error signals
Status Led and critical error output:

Colour front LED and CPU relay are activated when a critical error is detected. They are not configurable.

Figure 110 Device checks screen
26.2 ERROR HANDLING PROCEDURE
The procedure will depend on the detected error and the device status.
❑ If the device is off, check that the power supply is correct. If the device is well supplied, contact the technical service
❑ If the device is on but it shows failure, return to the events screen and check which type of error it is
 If critical error, with no specific indication, is shown and the error persists after turning the unit off and on,
contact the technical service.
 If converter or reference voltage error is shown. Check the Measurements, and if they are correct, turn off and
on the unit; if the error does not disappear, contact the technical service.
 If Clock error is shown, synchronize manually. If the error persists, contact the technical service.
 If error in the setting is shown, send the settings again. If error persists contact the technical service

PROTECTION DEVICES WITH SAMPLED VALUES 
27. PROTECTION DEVICES WITH SAMPLED VALUES

These protection units receive samples of analog measurements using Sampled Values (SV) protocol, through an Ethernet network.
They can be connected to merging units or electronic transformers that follow IEC61850-9-2 or IEC61869-9 standards.
The device can communicate through two physical Ethernet interfaces RJ45 or optic fibre. PRP/HSR redundancy and Link failover
redundancy are available.
Available measures and their accuracy are determined by the accuracy of the external SV publishers. These publishers will be responsible
for capturing and sending analog measurements of the lines, generating SV frames through an Ethernet communications network. The
device will only subscribe, among all the available measures, to those that are necessary for their correct operation.
Local measures captured directly through current and / or voltage input channels are allowed. Therefore, some of the measures can be
local and some others sampled values. In order to operate correctly, the measures must be synchronized by GPS.
The following figures show, according to model encoding, the board position.
Figure 111 19” chassis and redundant communications
Figure 112 19” chassis and redundant power supply and communications

User Manual 259
27.1 DEVICE MODELS
There are multifunction protection (MD), distance (ZT), differential transformer (TD), line differential (LD) and control with measure
(CD). The detailed functions included in every family are explained in the user manual of the family.
The device model code includes three additional characters at the end of the model encoding to select the sampled values ports and
the type of measures (see chapter 1).
In these devices, the housing must be Chassis 19" 4U and I/O board 6, 7 and 8 are not available.
Figure 113 Sampled values options
CONTROL
HOUSING
ANALOG
MODEL
COM1
COM2
COM3
COM4
COM5
COM6
ETH1
ETH2
ETH1
ETH2
I/O 1
I/O 2
I/O 3
I/O 4
I/O 5
I/O 6
I/O 7
I/O 8
INGEPAC EF XX MODEL INGEPAC EF- - A - A - A
MSV COMMUNICATION PORT (Sample values)

E GFO ETH-1
F RJ45 ETH-2
L LC
O GFO (ETH with PRP/HSR/Switch)
P RJ45 (ETH with PRP/HSR/Switch)
- Nada
LOCAL ANALOG MEASURES

No local measures -
Configurable (All/None local) D
27.2 PUBLISHERS DECLARATION
It is necessary to have configuration files (CID) or configuration data of the SV publishers. If the subscription is made using PacFactory
configuration tool, it is mandatory to import the CID files of the publishers and receivers into the same installation.
For detailed information see the "Add-in of subscription" chapter.
27.3 SAMPLED VALUES SUBSCRIPTION
The sampled values subscription is performed according to the IEC61850 standard (edition 2).
The details of this functionality are:
❑ It is only allowed sampled values that comply with the recommended for protection and measurement, indicated in IEC61850-9-
2LE ("Implementation guideline for digital interface to instrument transformers using IEC 61850-9-2" of UCA International Users
Group) and IEC61869-9 ("Instrument transformers - Part 9: Digital interface for instrument transformers") standards, allowing the
subscription up to 8 publishers. All subscribed publishers must use the same standard. If it is subscribed to publishers with different
standards, the CID will be erased because of a non-valid configuration.
❑ After sending a configuration file, the subscription and reception remain operative until the CID has been parsed and fully
validated. Then, the new subscription settings are loaded.
❑ The subscription is made with EC61850 edition 2 and can be used with edition 1.
27.3.1 Configuration
According to IEC 61850 edition 2, the sampled values subscription uses the Inputs-ExtRef in the CID.
The Inputs section defines all external values that will be received from other computers. In this section each ExtRef element refers
to an external data and the element intAddr performs the mapping or association to a data of the device.
In the case of sampled values, the Inputs section is included in the logical node "PHSMMXU". This node has an "OpPhasor" element
associated with each analog measurement of the device. In this way, an external measurement, received through sampled values,
can be assigned to an internal measurement of the subscriber device.

User Manual 260
The CID file of an IED with subscriptions to configured SMV messages contains several sections of IEDs. The section of the IED itself
and sections of each merging unit IEDs that publishes the sampled values to which it is subscribed.
These sections of the external IEDs only contain the data model necessary to perform the subscription in order to reduce the size of
the CID file.
For more information about the sampled values subscription configuration process, refer to the configuration software tool's user
manual (energyFactorySuite/pacFactory).
27.3.2 ADD-IN of subscription

The configuration tool has an add-in that allows the relay to subscribe to the publishers of sampled values in an easy way. To access it,
it is necessary to access the 61850 configuration menu, as shown in Figure 114.
Once the 61850 configuration menu is selected, through the icon , the subscriptions configurator is accessed, valid both for
subscriptions to Gooses and to sampled values. In this case, "Sampled Values" option will be selected, as shown in Figure 115.
Configuration tool shows all the sampled values control blocks available in the installation, allowing a maximum of 8 subscriptions
(Figure 114).
It is also possible to monitor the subscriptions by using LSVS logical nodes.
"Data Binding" tab (Figure 117) shows the measurement channels used by the protection (depending on the model), and the current
and voltage measurements (TCTR and TVTR) available in the added control blocks. Each data channel of the protection can be assigned
a data, respecting the type of measurement of each channel, TCTR for intensities and TVTR for voltages.
Figure 114 Subscription menu selection

User Manual 261
Figure 115 Subscription configuration
Figure 116 Sampled values control blocks selection

User Manual 262
Figure 117 LSVS nodes assignment
Figure 1182 Channel assignment
27.3.3 Monitoring
The LSVS logical node of the data model is used to monitor subscriptions to SV messages. There are 8 instances of LSVS logical
nodes that allow to monitor up to 8 subscriptions to sampled values.
The configuration value in the LSVS logical node is the SvCBRef data (reference to the Sampled Values control block subscribed).
This reference must be filled out when doing the configuration of the subscription, additionally allows to be modified in execution
through an IEC 61850 client.
The values monitored in this logical node are:
❑ NdsCom: Subscription needs commissioning. When true, the received SV message does not correspond to the current
subscription settings. Verify that the configuration revision is correct.
❑ St: When true, the subscription is active. Otherwise it is inactive.
❑ SimSt: If true, subscribed SV messages with the simulation bit set are being received and accepted
❑ ConfRevNum: The expected configuration revision number in SV messages.
❑ RxConfRevNum: The configuration revision number received in SV messages.
All this data are mapped in the internal database of the device and can be used in logics of the device and in the local display.
The assigned Boolean signals are listed in the following table:

User Manual 263
Table 106. LSVS internal signals
LOGICAL NODE ELEMENT ASOCIATED INTERNAL SIGNAL

St (Subscription status) 24960
LSVS1 NdsCom (Needs commissioning) 24961
SimSt (Simulation status) 24962
The following table, shows the integer signals. Internally they are mapped to counters
Table 107. LSVS counters
LOGICAL NODE ELEMENT ASOCIATED INTERNAL COUNTER

ConfRevNum (ConfRev configured) 177
LSVS1
RxConfRevNum (ConfRev received) 178
LSVS2
LSVS3
LSVS4
LSVS5
LSVS6
LSVS7
LSVS8

User Manual 264
27.4 CONFIGURABLE LOCAL MEASURES
The device code selection has different options for the local measures.
In the "-" option, all measures are received through communications, using sampled values messages.
In the "D" option, depending on the binary file loaded on the analog card, or all the measurements are wired directly to the analog
card's measurement transformers (conventional wiring), or all of them are received by communications in the form of sampled
values. The options are:
❑ All measures received from local transformer.

 The signal "SV receiver device" is deactivated.
 The device´s version doesn´t include the SV board versions.
❑ All measures received from sampled values.

 The signal "SV receiver device" is activated.
 The device´s version includes the SV board versions.
27.5 SAMPLED VALUES SIMULATION
The device implements the simulation mode defined in the IEC 61850 Edition 2.
This mode allows the simulation of any SV that is present in the communication network so that two SV with the same information
data will be present at the same moment, the real one without the simulation bit active and the simulated one with the simulation bit
active. If the subscriber is in simulation mode, once it has received the first simulation SV its values will be used instead of the values of
the original SV. Therefore, if the device is in simulation mode, it still accepts 'original' SV messages, and only discards the 'original' SV
messages for those SVs which are simulated.
Simulation mode is enabled with the controllable data "Sim" included in the LPHD logical node in the GEN logical device.
In each LSVS logical node, used to monitor SV subscription, the SimSt status shows with TRUE value that subscribed SV messages with
the simulation bit set are being received and accepted.
When the subscriber is not in simulation mode (GEN/LPHD.Sim.stVal=false) the simulated SVs are ignored. The device keep on using
the "real" SV messages.
When the subscriber is in simulation mode (GEN/LPHD.Sim.stVal=true) the simulated SVs are used for operational purposes. The device
ignores the "real" SV messages after a first simulated one has been received. The corresponding LSVS.SimSt is set when the first
simulated message is received and only cleared when LPHD.Sim.stVal is set to false.
Once the device has received a simulated message for one of the subscribed SV messages, it will not process the real one until the
simulation mode of the device (LPHD.Sim.stVal) is set to false.

User Manual 265
27.6 TEST MODE FOR SAMPLED VALUES
The device implements the test mode for the SV reception.
If the device is in test mode for the SV, only the measurements received in the message of sampled values with the Quality bit of the
test mode active will be considered valid.
The device can be set to test mode for SV using the "SV test mode On" Setting, included in GEN/LPHD logical node.
Table 108. Test mode for sampled values setting

SVTestEna SV Test mode On NO/Yes enum
The signal "SV mode test Status" is activated when the device is in test mode for SV.
Table 109. Test mode for sampled values signal

SV mode test Status SVTestSt stVal
27.7 BEHAVIOUR WITH LOSS OF SYNCHRONIZATION
When a loss of synchronization is detected in the sampled value messages, the device can keep on protection or not depending on the
settings.
There is a setting that indicates how the device should operate when sampled values are not synchronized or when local
synchronization is used. It is included in the logical node GEN/LPHD.
❑ Lost SV synchronization. Indicates the behaviour of the device depending on the synchronization type received in the
sampled values messages. The available options are:
 Allow local. The device has to see the measures synchronized (Locally or globally) to consider them valid.
 Allow only global. The device has to see the measures with global synchronization to consider them valid.
Table 110. Behavior with loss of synchronization setting

Allow local (1)
SyncLostMod Lost SV synchronization enum
Allow only global (2)
A device subscribed to a single MU, even if the measures it receives are not synchronized, it treats them as measures with local
synchronization.

User Manual 266
Parque Tecnológico de Bizkaia • Edificio 110
48170 Zamudio, Bizkaia, Spain
Tel + 34 944 039 600
Fax +34 944 039 345
technology@ingeteam.com

Ingeteam Power Technology, S.A.
www.ingeteam.com

Ume Ingepac Ef CD Eng

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ume Ingepac Ef CD Eng

Uploaded by

Copyright:

Available Formats

CONTROL AND MEASUREMENT DEVICES

© All rights reserved. No part of this publication

Ingeteam Power Technology reserves the right to

1. GENERAL DESCRIPTION ............................................................................................................................ 9

Ingeteam Power Technology S.A.

4.1.2 Synchronism permission ..................................................................................................................................... 51

Ingeteam Power Technology S.A.

9.4 FIRMWARE UPDATE............................................................................................................................................... 94

Ingeteam Power Technology S.A.

17. TCP/IP NEWORK CONFIGURATION .................................................................................................. 139

Ingeteam Power Technology S.A.

20.2 CONFIGURATION SETTINGS ............................................................................................................................... 189

Ingeteam Power Technology S.A.

24.4.3 Request for measurements and counters....................................................................................................... 233

Ingeteam Power Technology S.A.

1.1 FUNCTIONAL DESCRIPTION

Table 1 shows the features and measurements available.

Functions and measurements

Influence of environmental conditions:

Magnitude Tolerance Variation in % referred to the class

Ingeteam Power Technology S.A.

1.2 MODEL ENCODING

POWER SUPPLY MODULE

REAR SERIAL COMMUNICATION PORT

REAR ETHERNET COMMUNICATION PORT

I/O BOARD CONFIGURATION

Ingeteam Power Technology S.A.

Figure 3 CD0 ½ 19” chassis Figure 4 CD0 19” chassis

Figure 5 Redundant power supply Figure 6 Redundant power supply

Figure 7 PRP Redundancy (2LC) Figure 8 PRP Redundancy (2RJ45 + 2LC)

Ingeteam Power Technology S.A.

1.3 USER INTERFACE

The front board is equipped with:

❑ 10-digit numerical keyboard with decimal point, plus R key

The rear communications could be:

Ingeteam Power Technology S.A.

1.4.2 Power supply

Figure 11 Simple power supply

Figure 12 Double power supply

1.4.3 Input/output cards

Figure 13 Module 11 digital inputs and 9 digital outputs

Figure 14 Module 16 digital inputs and 16 digital outputs

Ingeteam Power Technology S.A.

Figure 15 Module 16 digital inputs and 8 digital outputs

❑ Module 4 (Figure 16): Equipped with 32 digital inputs grouped as follows:

Figure 16 Module 32 inputs

Input 1 Input 2 Input 3 Input 4 Input 5 Input 6 Input 7 Input 8

Figure 17 Module with 16 digital inputs and 8 analogue inputs

Standard configuration of analogue inputs

Input 5 Input 6 Input 7 Input 8

Figure 18 Module with 16 digital inputs and 8 analogue inputs (4 isolated)

Ingeteam Power Technology S.A.

Figure 19 Módule 8 inputs, 4 outputs (hbco) and 4 digital outputs

Figure 20 Módule 8 inputs, 8 outputs

Figure 22 Module 8 inputs, 8 outputs (hbco)

Ingeteam Power Technology S.A.

1.4.4 Analogue inputs

Ingeteam Power Technology S.A.

1.4.4.1 Wiring diagrams

Figure 24 Connection A. 3 wires connection: 3TT and 3TC

Ingeteam Power Technology S.A.

Figure 25 Connection A. 4 wires connection : 3TT and 3TC

Ingeteam Power Technology S.A.

Figure 26 Connection A. 3 wires connection: 3TT, Vneutral and 3TC