Manual de Usuario saTECH-CNF en

saTECH CNF
User Manual
Rev: 2.03
Date: July 2020
© Electrotécnica Arteche Smart Grid, S.L.
RESTRICTED USE DOCUMENT.
The total or partial reproduction of this

information is forbidden without express prior
written authorization.
Document subject to change.

LIST OF CONTENTS
LIST OF CONTENTS
LIST OF CONTENTS ..................................................................................................... 3
Chapter 1. Introduction ................................................................................................ 9

1.1. Description...................................................................................................................... 9
1.2. Hardware requirements ................................................................................................ 10
1.3. Operative system requirements .................................................................................... 10
1.4. Installation .................................................................................................................... 11
1.4.1. Description of the installation process .................................................................... 12
Chapter 2. Application's main window ..................................................................... 14

2.1. File Menu ...................................................................................................................... 15
2.1.1. New Project ............................................................................................................ 15
2.1.2. Open Project .......................................................................................................... 21
2.1.3. Save Project ........................................................................................................... 22
2.1.4. Close Project .......................................................................................................... 22
2.1.5. Import Project ......................................................................................................... 22
2.1.6. Import project from IED .......................................................................................... 22
2.1.7. Generating Configurations...................................................................................... 22
2.1.8. Export Project ......................................................................................................... 23
2.1.9. Associate Signals ................................................................................................... 23
2.1.10. Export Signals ...................................................................................................... 24
2.1.11. Generate SCD file ................................................................................................ 25
2.1.12. Delete Project ....................................................................................................... 25
2.1.13. Exit ....................................................................................................................... 25
2.2. Edit menu ..................................................................................................................... 25
2.2.1. Work Directory Selection ........................................................................................ 25
2.2.2. Hide HelpScreens .................................................................................................. 26
2.2.3. Project IED parameters .......................................................................................... 26
2.2.3.1. Advanced Properties of saTECH IEDs ............................................................................... 26
2.2.3.2. saTECH IEDs TP and TC Boards ......................................................................................... 26
2.2.4. Default values for saTECH CNF ............................................................................. 26
2.2.4.1. saTECH BCU TP and TC Boards ......................................................................................... 27
2.2.4.2. Self-generated signals ...................................................................................................... 27
2.2.4.3. IED as a synchronism source ............................................................................................ 28
2.3. View Menu .................................................................................................................... 29
saTECH CNF|User Manual 3

LIST OF CONTENTS
2.3.1. Project .................................................................................................................... 29

2.3.2. IEDs ....................................................................................................................... 29
2.3.3. IED details .............................................................................................................. 29
2.3.4. Console .................................................................................................................. 29
2.3.1. Clear Status ........................................................................................................... 29
2.4. Graphics Menu ............................................................................................................. 29
2.4.1. Edit HMI Drawing Templates .................................................................................. 30
2.4.2. Graphics Association for Bays at the HMI............................................................... 50
2.4.3. HMI Single-Line Edition .......................................................................................... 52
2.4.4. Validation of HMI Single-Line signals ..................................................................... 53
2.4.5. Generation of the HMI single-line graph ................................................................. 54
2.4.6. Edit BCU Drawing Templates ................................................................................. 54
2.4.7. Signal validation of all BCUs .................................................................................. 55
2.4.8. Generation of drawings of all BCUs ........................................................................ 56
2.4.9. Editing the System Status Window ......................................................................... 57
2.4.10. System Status Signal Validation ........................................................................... 59
2.4.11. Generating the system status window .................................................................. 59
2.4.12. Update Project Libraries ....................................................................................... 60
2.4.13. CNF SVG File Viewer ........................................................................................... 61
2.5. Tools Menu ................................................................................................................... 61
2.5.1. Update the application ............................................................................................ 61
2.5.2. Standardized Signal Table ..................................................................................... 62
2.5.3. Update CID Templates ........................................................................................... 66
2.5.4. Validate CIDs ......................................................................................................... 68
2.5.5. Configure Logos ..................................................................................................... 69
2.5.6. Configure Equipment Models ................................................................................. 70
2.6. Historical Menu ............................................................................................................. 71
2.6.1. See history ............................................................................................................. 71
2.6.2. Configure Historical Measurement Records ........................................................... 72
2.7. Help Menu .................................................................................................................... 74
Chapter 3. Project Engineering and IED Configuration .......................................... 75

3.1. Voltage level ................................................................................................................. 75
3.2. Bay ............................................................................................................................... 76
3.3. Adding IED ................................................................................................................... 78
3.4. Add Function ................................................................................................................ 85
3.5. Association of functions ................................................................................................ 86
3.6. Edit Project ................................................................................................................... 86

LIST OF CONTENTS
3.7. Edit/Delete Voltage Levels and Bays ............................................................................ 86

3.8. Removing IEDs and Functions...................................................................................... 87
3.9. Update CID Templates ................................................................................................. 87
Chapter 4. IED Group Configuration ......................................................................... 88

4.1. Hardware Model ........................................................................................................... 88
4.2. Publishing configuration ................................................................................................ 88
4.2.1. Goose Control Block .............................................................................................. 88
4.2.2. Report Control Block .............................................................................................. 94
4.3. Logic functions .............................................................................................................. 98
4.3.1. Logic Functions Toolbar ....................................................................................... 101
4.3.2. Table of variables of the logic functions ................................................................ 102
4.3.2.1. Types of variables ........................................................................................................... 104
4.3.2.2. Adding variables to the variables table .......................................................................... 105
4.3.2.2.1. Adding variables from the menus ........................................................................... 105
4.3.2.2.2. Adding variables by dragging and dropping ............................................................ 107
4.3.2.3. Deleting variables ........................................................................................................... 108
4.3.3. Configuration of the logic functions ....................................................................... 109
4.3.3.1. Available FBD functions .................................................................................................. 112
4.4. Configuration options .................................................................................................. 118
4.4.1. Generating CID .................................................................................................... 121
4.4.1.1. Generating Configurations ............................................................................................. 121
4.4.1.2. Generating CID ............................................................................................................... 121
4.4.1.3. Validating CID ................................................................................................................. 121
4.4.2. Send Configuration............................................................................................... 121
4.4.2.1. Load Configuration ......................................................................................................... 121
4.4.2.2. PLC Monitoring ............................................................................................................... 122
4.4.3. 1850 Network configuration .................................................................................. 122
4.4.4. Time Configuration ............................................................................................... 123
4.4.5. Synchronization settings....................................................................................... 123
4.4.6. Historical Measurements Configuration ................................................................ 127
4.4.7. Slave Protocol Configuration ................................................................................ 127
4.4.8. Master Protocol Configuration .............................................................................. 139
4.4.9. 61850 Communication.......................................................................................... 148
4.4.9.1. Gooses Subscription ....................................................................................................... 149
4.4.9.2. Subscription to Reports of other IED.............................................................................. 151

LIST OF CONTENTS
4.4.9.3. Subscription to all ReportControls ................................................................................. 153

4.4.9.1. Publish GSEControl ......................................................................................................... 153
4.4.9.2. Edit a DataSet ................................................................................................................. 154
4.4.10. Signals configuration .......................................................................................... 155
4.4.10.1. IED Signal Editor ........................................................................................................... 156
4.4.10.1.1. Filters ..................................................................................................................... 157
4.4.10.1.2. Row Options .......................................................................................................... 157
4.4.10.1.3. Insert Row Above/Below ....................................................................................... 158
4.4.10.1.4. Delete Row ............................................................................................................ 158
4.4.10.1.5. Copy Row ............................................................................................................... 158
4.4.10.1.6. Paste Row .............................................................................................................. 159
4.4.10.1.7. Disable Row ........................................................................................................... 159
4.4.10.1.8. Enable Row ............................................................................................................ 160
4.4.10.1.9. Autocomplete ........................................................................................................ 160
4.4.10.1.10. Delete cell contents ............................................................................................. 160
4.4.10.1.11. Undo .................................................................................................................... 161
4.4.10.1.12. Column-Specific Context Menu ........................................................................... 161
4.4.10.1.13. Drag and drop ...................................................................................................... 171
4.4.10.1.14. Editing the standardized signal file ..................................................................... 172
4.4.10.2. Signal Association from File .......................................................................................... 175
4.4.11. Standardized Signal Format .............................................................................. 177
4.4.11.1. Configuration of each signal ......................................................................................... 178
4.4.11.1.1. Signal location ....................................................................................................... 178
4.4.11.1.2. Behavior Configuration ......................................................................................... 179
4.4.11.1.3. Data Acquisition Mode .......................................................................................... 183
a) IED-specific data acquisition ............................................................................................ 183
b) Data acquisition via DNP protocol ................................................................................... 185
c) Data acquisition via MODBUS protocol ........................................................................... 186
d) Data acquisition via SAP20_TCD protocol ....................................................................... 189
4.4.11.1.4. Destination to Higher Levels ................................................................................. 190
a) Data destination by DNP3 protocol ................................................................................. 190
b) Data destination by IEC101 or IEC104 protocol .............................................................. 192
c) Data destination by MODBUS protocol ........................................................................... 193

LIST OF CONTENTS
4.4.11.2. Standardized texts associated with signals .................................................................. 197

4.4.11.3. Configuration parameters ............................................................................................ 212
4.4.12. Calculated Signals .............................................................................................. 214
4.4.13. Graphics ............................................................................................................. 215
4.4.13.1. Associate BCU positions ............................................................................................... 215
4.4.13.2. Edit Single-Line BCU ..................................................................................................... 216
4.4.13.3. Generation of the Single Line associated to an IED...................................................... 217
4.4.14. TFT Password Configuration .............................................................................. 217
4.4.15. Configurable Parameters .................................................................................... 218
4.4.15.1. HMI Historical Measurements Restorer ....................................................................... 220
4.4.15.2. IED as a Source of SNTP Synchronization ..................................................................... 222
4.4.15.3. SaTECH Application Update.......................................................................................... 223
4.4.15.4. TP and TC board configuration ..................................................................................... 223
4.4.15.5. Configurable Parameters of the Function 25 ............................................................... 226
4.4.15.6. External Equipment Monitoring ................................................................................... 228
4.4.15.7. Communications Identifiers ......................................................................................... 229
4.4.15.8. Self-Generated Signals ................................................................................................. 232
4.4.15.9. Advanced Properties .................................................................................................... 245
4.5. Add IED without Bay ................................................................................................... 251
4.6. Removing IED and logic functions .............................................................................. 251
4.1. IEC-61850 Signal Tree ............................................................................................... 252
Chapter 5. Modeling of elements ............................................................................ 255

5.1. Modeling of the acquisition board (I/O) ....................................................................... 256
5.2. Modeling of the logical functions ................................................................................. 256
5.3. Modeling of slave equipment ...................................................................................... 257
5.4. Publication of gooses .................................................................................................. 257
5.5. Hardware anomalies modeling .................................................................................... 258
5.5.1. Serial port failures ................................................................................................ 258
5.5.2. Ethernet anomalies .............................................................................................. 258
5.5.3. I/O board failure (grouped into levels) ................................................................... 259
5.5.4. Critical hardware failure and non-critical hardware failure..................................... 259
5.6. Configuration parameter modeling .............................................................................. 260
Chapter 6. Version and Compatibility Matrix ......................................................... 269
List of Contents ........................................................................................................ 272

LIST OF CONTENTS
Index of tables .......................................................................................................... 279

INTRODUCTION
Chapter 1. Introduction
1.1. Description
The saTECH CNF software allows for the configuration of Arteche's SAS IEC 61850
Substation Automation Systems. It allows for configuring all the Arteche Control equipment
that make up the solution - process bus controllers (saTECH RIO), bay or position
controllers (saTECH BCU), gateway (saTECH SCU), and SCADA systems (saTECH HMI) -
from a single project.
It has the ability to integrate the configuration (CID) of IEDs from any manufacturer and
import signaling from other equipment, implement logic functions based on the IEC 61131-6
standard, edit and generate single-line position, substation and communications diagrams.
The application is multi-lingual (Spanish, English, French and Portuguese) and generates
open and standardized configurations based on IEC 61850 files.
The software saTECH CNF works under the Project scheme, and makes it possible to get,
 In the case of IED's:
o saTECH RIO, Input and Output Modules: CID file with the required
functionalities based on the project requirements.
o saTECH BCU, Bay Controller (position): CID file with the configuration, SVG
file with the single-line position diagram (when a TFT display is available) and
SVG file for logic functions simulation in the equipment.
 In the case of Systems:
o The configuration is comprised of the CID configuration files of each

substation IED (control, measurement and protection) and those of the
Substation Control Units (saTECH SCU.) If there is HMI, when creating the
project, we can choose if we prefer to configure the HMI automatically from
the SCU CID, or as another independent device. The SVG files
corresponding to the BCU units with display will also be generated and, in the
case of HMI, the SVG files corresponding to the single line diagrams of
position, bay, parks, general, etc.

INTRODUCTION
1.2. Hardware requirements

The minimum requirements for the PC on which the saTECH CNF software is to be installed
are shown in the Table 1.
Hardware Recommended Hardware
CPU 1.0 GHz 2.2 GHz
RAM 1 GB 4 GB
Disk space 2 GB 4 GB
Monitor 1024 x 768 1280 x 1024
Graphics Card Not required Recommended
Ethernet port Necessary Necessary
Table 1 Hardware Requirements
1.3. Operative system requirements

The minimum requirements for the operating system of the PC where the saTECH CNF
software is to be installed are shown in the Table 2
Operating System Recommended
Microsoft Windows XP 32-bit SP2 or higher
Microsoft Windows Server 2003 32-bit SP2
Microsoft Windows Vista Business 32-bit SP2
Microsoft Windows 7 Professional 32-bit SP1
Microsoft Windows 7 Professional 64-bit SP1
Microsoft Windows 8 64-bit SP1
Microsoft Windows 10 Home 32-bit
Microsoft Windows 10 Home 64-bit
Microsoft Windows 10 Pro 32-bit
Microsoft Windows 10 Pro 64-bit
Table 2 Operatingsystem

INTRODUCTION
1.4. Installation
The software is distributed with an installer, which makes it possible to configure the different
installation options at will, as shown in Figure 1-1.
Figure 1-1 Software installation

INTRODUCTION
1.4.1. Description of the installation process

The following parameters must be taken into account during the installation process:
A. Application language. Selection of the language to be used during installation and

later in the application. Once the application is installed, the language can be
changed by selecting one of the available ones, but restarting the application will
be necessary.
B. Installation information. Software version.
C. Application installation folder. Selection of the installation location and reading

permission request.
D. Work folder. This is the folder where the application's projects will be stored. Read
and write permissions are required for the user. Note: If there is more than one
operating system user using the application, this work directory folder must have
the appropriate permissions. By default, a "Public" folder is used.
E. Information on the components to be installed.
F. Installation outcome. Brief summary of the application’s components and files

installed in the PC.
G. On Windows Operating Systems there might be third party programs installed that
use the components of the saTECH CNF application. The installation and
deinstallation process will attempt to free all connections to these components, but
in some cases it may cause some inconsistency in the final installation.
 Abort: Stop the installation, it is recommended to close all programs, restart

Windows and re-start the installation process.
 Retry: Proceed with the installation; first we must close the third party
program that is causing the crash.
 Omit: Proceed with the installation by omitting the error; it is not

recommended (only for administrators.) It is recommended that we close all
programs, restart Windows and re-start the installation process.

INTRODUCTION
Figure 1-2 Inconsistent installation
If after an installation we encounter the error seen in Figure 1-2, we must manually
remove the Windows Service "SATECHCNF_MySQL55" and all the files in the
installation path, for example "C:Program Files\SATECH-CNF" or "C:Program Files
(x86){SATECH-CNF}". Once this is done, we must reboot the operating system and re-
start the installation process.

APPLICATION'S MAIN WINDOW
Chapter 2. Application's main window
When the saTECH CNF application is started, the following window is displayed:
Figure 2-1 Main Window
 At the top is the application's Main Menu
 At the bottom is the Status Bar, which indicates the result of the operations being
executed
 The Project panel represents the substation engineering, where the substation is
shown with its voltage levels, at each voltage level its bays and at each bay the IED
provision with its functionality. This setting is used for automatic adjustments in the
generation of single-line drawings
 The IED panel shows all the IEDs of the project to be configured. This is the
configuration area for each IED, settings for: time configuration, synchronization,
communications, logic functions, single-line drawings, signal files, etc
 The IED Details panel shows the specifications of the IED selected in the IED panel.
This area is the working area of the CNF; each IED setting will be configured in this
area of the screen with a new tab

 Under the IED Details panel you will find the Console panel, which will show all the
relevant messages of the actions and possible errors that are detected when
configuring and validating a project. It is possible to:
o Save all this information in CSV format by clicking on the 'save' button
o Delete all the messages with the 'clean' button
o Apply a filter to easily find a specific message.
The distribution of the tabs is free, it can be adjusted to screen requirements. In addition,
the tabs have buttons to 'close', 'minimize' and 'maximize'.
2.1. File Menu

When clicking on the menu option File, the options of the
Figure 2-2 are displayed:
Figure 2-2 File Menu

2.1.1. New Project
Makes it possible to create a new project. When this option is selected, a window is
displayed to request the Name and Description of the project to be created:
Figure 2-3 New Project

The user must enter the requested data and then press the Next button, thus a window
similar to the one shown in the Figure 2-4 is displayed.
Figure 2-4 Project Data - Screen 1
The user must enter the general data of the project:
 Type of project communication: The communication type between the IED and
the UCS and/or HMI can be chosen from among the following:
o IEC-61850: When the project has 61850 communication with or without

other conventional protocols (e.g. DNP3)
o NOT 61850 when the project has no 61850 communication
 UCS number: If the project has UCS, this option must be selected, indicating
below whether it is single or dual.
 HMI: If the project has HMIs, this option should be selected, indicating below the
number of IEDs with HMI functionality.
 Show Advanced Settings. It shows a set of functionalities described in the

Figure 2-5

Figure 2-5 Project Data - Screen 2
 Project language: Language of the ICD templates (texts of the descriptions.) If

the ICD version for the selected language does not exist, the English or Spanish
language version will be used by default.
 Data Model Type: The default option is "LD by Control and Protection Function."
For projects with type configurations, it can be changed to the advanced option:
"LD by Type Position."
 Control model for the commands: At the project level, the default control model
is configured for all IED commands (except for IEDs from other manufacturers.)
Options:
o 0: Status
o 1: Direct execution with normal security
o 2: Direct selection and execution with normal security
o 3: Direct execution with advanced security
o 4: Direct selection and execution with advanced security
 Command conversion: It makes it possible to have a different control model in

an IED and in the Dispatch or Control Center. If we activate this option, the IEDs

internally transform the commands that arrive from dispatch to the control model
configured in the IED and when they respond they carry out the transformation in
the opposite direction.
 Associated reports by client name: Allows multiple clients to subscribe to a

single report, instead of creating one report per client. By enabling this option, in
each ReportControl node of the CID, an RptEnabled sub-node is generated with a
ClientLN for each IED subscribed to the Report, one connection for each of them
and an additional one to monitor the system with, for example, IEDScout, will be
allowed. For the IED that appears in the first ClientLN, each Report will be created
by adding the suffix "01" to the name, the next one’s will be created adding the
suffix "02", and so on.
 Graphic Elements Library: Versions of graphic element libraries, according to

the project application.
 Historical Measurements: Configuration suitable for the version of HMI

equipment installed.
 System disconnection: It is possible to enable or not to enable this functionality,

associated to maintenance tasks in the system.
 Number of characters: Allows for configuring the number of characters for the
Substations, Voltage Levels and Bay names, which will be used in the project
configuration.
Once the data has been entered, the user must press the Next button, and a window
similar to Figure 2-6 will be displayed.

Figure 2-6 Substation data
Once the Substation data is completed, the software will ask if the UCS and HMI
equipment share the configuration in the same CID, or if they are configured
independently (different CIDs and SVG drawings.)
Figure 2-7 SCU and HMI equipment configuration
In addition, the number of network ports, the number of serial ports and the model can be
chosen for the SCU. The Figure 2-8 screen is displayed in case the option to share
configuration among all SCU and HMI equipment has been chosen.
Figure 2-8 SCU and HMI equipment configuration

If the user chooses not to share configuration between SCU and HMI, the options will be
identical, but an additional screen will appear to ask for the number of network ports and
the number of HMI SERIAL ports:
Figure 2-9 HMI equipment configuration
Upon completion, the new substation will be shown on the Project Panel, as seen in the
Figure 2-10:
Figure 2-10 Project created
As can be seen here, the Project Panel displays the name of the substation created, and
the IED Panel displays the IED corresponding to the UCS, whose name is formed with
the following rule:
 UCSxxx__: Where xxx is the code of the substation created.

If we chose not to share the configuration between SCU and HMI, then the IED
corresponding to the HMI will also appear in the IED Panel , whose name will be HMI__
2.1.2. Open Project

It makes it possible to open a previously saved project from the application database. When
this option is selected, a window is displayed which requests the name of the project:
Figure 2-11 Open Project
The user must select the project they want to open with a double click or select it and
then press the Finish button. The information of the loaded project will be displayed:
Figure 2-12 Open project

2.1.3. Save Project

Makes it possible to save the project in the application database. Normally, it is not
necessary to execute it, since saTECH-CNF saves the data in a database, as we add
and configure the different elements of the project.
2.1.4. Close Project

Makes it possible to close the project that is active at that time.
2.1.5. Import Project

This option makes it possible to import a previously saved project file
'ProjectName_satech-cnf.project.zip'. Once the import is done, the project is saved in the
application's database, so it can be opened for editing at any time.
2.1.6. Import project from IED

Makes it possible to import a project file which was previously saved in an IED of the
saTECH range. When a new configuration is loaded onto the computers, the exported
project is sent, which allows for it to be recovered later via this option.
For this option, the following is required:
 IP: IP address of the equipment with the

project.
 User: User for authentication.
 Password: Password for secure connection.
Once the import is done, the project is saved in the

application's database, so it can be opened for
editing at any time.
Figure 2-13 Import project from IED
2.1.7. Generating Configurations

It generates the CIDs of all the Arteche IEDs that make up a Project, and loads them into
the memory, along with the other IEDs from other manufacturers, with the objective of
executing the future options that require a signal tree more quickly.

2.1.8. Export Project

Makes it possible to save all the project generated with the software in a single file
'ProjectName_satech-cnf.project.zip.' This file includes the configuration (CID) of
Arteche's IEDs and those of the other manufacturers that make up the project as a whole,
allowing for a backup of the configuration of the entire Substation SAS.
2.1.9. Associate Signals

Makes it possible to associate a signal file - XLS extension - to the project. When opening
it, we can see the association of each IED in the project with the Signal Files:
Figure 2-14 Link Signals, project information view
The associations of each IED can be removed with the "Disassociate" button and there is
also the option to "Disassociate all."
When selecting the "Disassociate all" option, if the saTECH CNF detects that there are
backups (.xls files) in the same project folder where the signal association files of each
IED (.csv files) are saved, the option to delete them will be enabled.

Note: If we edit the *.xls file with "Microsoft Excel", we must make sure that all cells are
formatted as text before saving. This problem does not occur when using the programs
"LibreOffice Calc" and "OpenOffice Calc."
When a new *.xls file is selected, a drop-down list of all the sheets is displayed for each
IED that has no previous association (See Figure 2-15.) By default, the saTECH CNF
selects a suitable sheet, but changing the sheet is possible. (Note: if the wrong sheet is
selected when "Generating Settings", configuration errors will appear.)
Once the changes have been made, press the "Save" button to save the new information
and return to the Project Information view.
Figure 2-15 Associating signals, associating sheets to the IEDs
Note: It is recommended that the section 4.4.11 Standardized Signal Format be

analyzed.
2.1.10. Export Signals

It allows for exporting the signals associated with each IED in the project to a single *.xls
file. Note: If we edit the *.xls file with "Microsoft Excel", we must make sure that all cells
are formatted as text before saving. This problem does not occur when using the
programs "LibreOffice Calc" and "OpenOffice Calc."

2.1.11. Generate SCD file

It generates the Project SCD, it contains all the information of the CIDs, but in a single
configuration file.
Note: This file is only used for substation engineering documentation , it is not currently
uploaded to any system equipment.
2.1.12. Delete Project

It allows for deleting the project from the software database, via the following options:
o Delete the folder and files from the

work directory.
o Export the project to be deleted.
When we confirm the deletion, the

selected options will be executed before
the project is removed from the
database.
Figure 2-16 Confirmation to Delete Project
2.1.13. Exit
Terminates the saTECH CNF application.
2.2. Edit menu

Pressing the Edit menu option displays the
following options:
Figure 2-17 Edit Menu
2.2.1. Work Directory Selection

Makes it possible to establish the work folder for projects generated by the saTECH CNF
software. In this folder, a sub-folder will be created for each project, with the name of the
project, where configuration files such as CID files generated by the application for the
project will be stored.
Note: Changing the folder will move all project subfolders to the new destination.

2.2.2. Hide HelpScreens

Makes it possible to remove the initial help screens associated with each project option.
2.2.3. Project IED parameters

Makes it possible to configure some properties of the Project's IEDs.
Figure 2-18 Project IED parameters
2.2.3.1. Advanced Properties of saTECH IEDs

Makes it possible to configure the advanced properties of all saTECH IEDs in the
project, from a single screen. To learn more about the advanced properties see the
section 4.4.15.9 Advanced Properties.
2.2.3.2. saTECH IEDs TP and TC Boards

It makes it possible to configure the parameters of the TP and TC boards of all the
BCUs with TP and TC boards of saTECH, that appear in the project.
BCU TP and TC boards with ICD version 2.1.1 or higher and LDevice Bay mode (See
section 4.4.15.9 Advanced Properties) will have the function 25 setting available.
To learn more about the configuration of TP and TC boards, please refer to the
sections 4.4.15.4 TP and TC board configuration and 4.4.15.5 Configurable
Parameters of the Function 25.
2.2.4. Default values for saTECH CNF

Makes it possible to define some default values in the software.
Figure 2-19 Default values for saTECH CNF

2.2.4.1. saTECH BCU TP and TC Boards

These values will be available by default as values of the TP and TC boards, including
the default values of the function 25 as well (See Figure 2-20.)
Figure 2-20 Default values for TP and TC boards
At the end of the wizard the values are stored in the saTECH CNF and this will not
modify any values in the project. To configure the different parameters of the Power
Transformer (PT) and Current Transformer (CT) boards of each project BCU, the user
has to execute the option TP and TC board configuration where they can replace the
values configured for that BCU from the Default values for saTECH CNF.
The parameters set here are the same as those set for each individual IED,
specifically, see 4.4.15.4 TP and TC board configuration and 4.4.15.5 Configurable
Parameters of the Function 25.
2.2.4.2. Self-generated signals

It allows for changing the default configuration of the self-generated signals for the
different saTECH range IEDs.

2.2.4.3. IED as a synchronism source

Makes it possible to change the default configuration of the equipment as a source of
synchronization. This option is only available for IEDs of the saTECH range that can
act as a source of synchronization. These equipment are: SCU and SCU-HMI.
These values will be available as defaults when configuring a computer as a

synchronization source.
Figure 2-21 Default values for SCU as a synchronism source
At the end of the wizard the values are stored in the saTECH CNF and this will not
modify any values in the project. To configure the different parameters of the project’s
SCU or the SCU-HMI as a source of synchronism, the user has to execute the option,
IED as a Source of SNTP Synchronization where they can replace the values
configured for that equipment from the Default values for saTECH CNF.
The parameters set here are the same as those set for each individual IED (See
4.4.15.2 IED as a Source of SNTP Synchronization), although they are shown
differently to facilitate setting the default values for redundant ports.

2.3. View Menu

It makes it possible to open one of the four software work areas
or sections: Project, IEDs, IED Detail and Console, as shown in
the Figure 2-22 View Menu
Figure 2-22 View Menu

2.3.1. Project
This panel allows for the structure of the substation to be displayed.
2.3.2. IEDs
This panel makes it possible to view the IED settings.
2.3.3. IED details

This panel shows the IED settings.
2.3.4. Console
This panel shows the traces associated with the software operation.
2.3.1. Clear Status

Removes the information of the last executed operation from the status bar.
2.4. Graphics Menu

Clicking on the Graphics menu option shows the options
that we can see in the Figure 2-23
These options make the generation of the necessary

graphics possible, both for the TFT display of the
saTECH BCU units (when these contain this component),
and for the HMI (views of single line diagrams of position,
bay, parks, general, etc.), if the project has it.
Figure 2-23 Graphics Menu

2.4.1. Edit HMI Drawing Templates

It makes it possible to generate customized graphics for each type of position (bay), by
storing them as templates. In the templates, the graphic elements are configured without
specifying any references, only general properties that are self-generated by the IEC
61850 references themselves. Later, these templates can be assigned to different bays in
order to automatically compose an approximation to the substation's single-line diagram.
Most IEC 61850 references are generated for the Status (digital inputs) and Commands
(digital outputs) of graphic elements, and compose the different views of the Single-Line:
Substation, Voltage Level, Bay, General, etc.
If we have more than one bay with the same Single Line Graph, this option will make the
Template only once and it will be used as many times as there are bays in the project.
The application, at a later stage, will automatically assign the particular characteristics of
each of the bays. The user must click (with the mouse) on the Graphics menu, and then
Edit HMI Drawing Templates, thus displaying a figure similar to the Figure 2-24:
Each of the lines that appear corresponds to a Drawing Template which has been
previously created and stored in the project for HMI equipment, in what is called a
standard graphics library. Initially, this standard graphics library may be empty.

Figure 2-24 HMI Templates - Drawing Selector
Options available:
 Import: Makes it possible to store in the current project library any Graphic
Template generated in another project's library. We can import graphics from
either another library (libXXX.svg files) or from a final drawing
(finalDrawingXXX.cid files). These files are stored in the project folder, Single-Line
sub-folder (e.g: C:\ Users\ Public\ Documents\ARTECHE\ SATECH-CNF\
Projects\ ESCOBEDO\ Unifilar).
 Copy: Selecting a template from the list and pressing this button, a copy of the
selected template will be created, on which the user will be able to make the
necessary modifications to create a new template.
 Modify: Makes it possible to modify and save a previously created template.
 Create new: Makes it possible to create a new drawing template and store it in
the library, with a name chosen by the user.
 Delete: Removes the template selected in the list from the library.
 Save: Stores the changes made and returns to the previous window.

 Cancel: Returns to the previous window, without storing the changes in the
standard graphics library.
To edit a new Drawing Template, select the option Create new in the Figure 2-24, and
the following window will appear:
Figure 2-25 HMI Drawing Template Creation
The following tabs are available in the left panel:
 Library: Basic symbols required for the creation of graphics. The application has
different symbol libraries, and thus, for the installation, selects the most suitable
one for the projects to be carried out.
 Elements: This tab shows the elements that make up the Graph that is being
edited, it is different for the drawings for HMI equipment or the ones for BCU
equipment.
 Canvas: In this tab we define the properties of the drawing canvas.
The library of elements is subdivided into the following categories:

Drawings Switches Buttons
Measures Power transformers Others

Table 3 shows properties of the dynamic behavior of these symbols (except those of the semaphores):
Element Graphic Representation Inverted Flashing C Open C Closed Thicknes Level Status System Aux Status Command/Status Command
s disconne
ction
Switch with If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It is Status4, and is No matter what is
Text colors the C Open C Closed Thickness XXXX effect used for control configured, it takes on the
statuses of switch where commands 4 and is the ctlVal [CO] from the signal
1 and 2 as 2 and X=1/0 status to look at so as set to Status
1, respectively to see whether or not it
has changed in order to
give Attended or
Unattended command
DO Switch with If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It is Status4, and is No matter what is
Text colors the C Open C Closed Thickness XXXX effect used for control configured, it takes on the
statuses of switch where commands 4 and is the ctlVal [CO] from the signal
1 and 2 as 2 and X=1/0 status to look at so as set to Status
1, respectively to see whether or not it
has changed in order to
give Attended or
Unattended command
Switch If inverted, it d: 0.1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It is Status4 and is Regardless of how it is
colors the C Open C Closed Thickness XXXX effect used for control configured, it will take on
statuses of switch where commands, 4 is the the ctlVal [CO] from the
1 and 2 as 2 and X=1/0 status to where we can signal set to Status
1, respectively see whether or not it
has changed to give
Attended or
Unattended commands

s disconne
ction
DO switch If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It is Status4 and is Regardless of how it is
has changed to give
Attended or
Unattended commands
O Switch If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 Status2 It has no It has no effect Regardless of how it is
colors the C Open C Closed Thickness XXXX effect configured, it will take on
statuses of switch where the ctlVal [CO] from the
1 and 2 as 2 and X=1/0 signal set to Status
1, respectively
DO switch O If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 Status2 It has no It is Status4 and is Regardless of how it is
has changed to give
Attended or
Unattended commands

s disconne
ction
Car switch If inverted, it d: Bl:0/1 elmWidth: elmMask: status1 status2 It has no It is Status4 and is Regardless of how it is
colors the Thickness XXXX effect used for control configured, it will take on
statuses of slide where commands, 4 is the the ctlVal [CO] from the
1 and 2 as if they X=1/0 status to where we can signal set to Status
were 2 and 1, see whether or not it
respectively has changed to give
Attended or
Unattended commands
Isolator with If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 Status2 It has no It has no effect Regardless of how it is
text colors the C Open C Closed Thickness XXXX effect configured, it will take on
1, respectively
DO isolator If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
with text colors the C Open C Closed Thickness XXXX effect configured, it will take on
1, respectively

s disconne
ction
Isolator If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
1, respectively
DO isolator If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
1, respectively
O Isolator If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
1, respectively

s disconne
ction
DO O Isolator If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
1, respectively
Analog elmMask: status1 status2 status2 action1

Transformer XXXX
where
X=1/0
Long elmWidth: elmMask:
Transformer Thickness XXXX
where
X=1/0
Transformer elmWidth: elmMask:

Circles Thickness XXXX
where
X=1/0
Double winding elmWidth: elmMask:

transformer Thickness XXXX
where
X=1/0

s disconne
ction
Auto- elmWidth: elmMask:
transformer Thickness XXXX
where
X=1/0
Lateral elmWidth: elmMask:

where
X=1/0
Single elmWidth: elmMask:

where
X=1/0
Name elmMask:
Transformer XXXX
where
X=1/0
Fused circuit elmWidth: elmMask:

breaker Thickness XXXX
where
X=1/0
Generator elmWidth: elmMask:

Thickness XXXX
where
X=1/0

s disconne
ction
Recierre79 If inverted, it elmWidth: elmMask: status1 status2 It has no Used for control model Regardless of how it is
colors them the Thickness XXXX effect 4, it is the status which configured, it will take on
other way where can see the changes in the ctlVal [CO] from the
around. It is X=1/0 order to give attended signal set to Status
configured in the or unattended
property command, in case it is
fonTyp=0/1 different from status1
0=Not inverted,
1=Inverted
Relay 86 elmMask: status1 status3 It has no effect Regardless of how it is

XXXX configured, it will take on
where the ctlVal [CO] from the
X=1/0 signal set to status1
Poly-Button If inverted, it elmWidth: elmMask: status1 status2 Regardless of how it is

colors them the Thickness XXXX configured, it will take on
other way where the ctlVal [CO] from the
around. It is set X=1/0 signal that is set in Status
to the property
fonTyp=0/1
0=Not inverted,
1=Inverted
Led d: Bl:0/1 elmWidth: elmMask: status1 status2

Thickness XXXX
where
X=1/0
Alarm elmMask: status1 status2

XXXX
where
X=1/0

s disconne
ction
Local/Remote If inverted, it elmWidth: elmMask: status1 status2 It has no It has no effect
colors the local(0) Thickness XXXX effect
and remote(1) where
statuses as if X=1/0
they were
Remote(0) and
local(1),
respectively
Double If Inverted, it elmWidth: elmMask: status1 status2 It has no It has no effect

Local/Remote colors the states Thickness XXXX effect
of the local(0) where
and remote(1) as X=1/0
if they were
Remote(0) and
local(1),
respectively. In
the case of
Single Signal,
and in the case
of a double with 1
(Remote) and 2
(Local) inverted,
i.e. 1 (Local) and
2 (Remote.)
Watertight If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask: status1 status2 It has no It has no effect Regardless of how it is
1, respectively
Reactance If inverted, it d: Bl:0/1 elmCol:Ca: elmCol:Cc: elmWidth: elmMask:

colors the C Open C Closed Thickness XXXX
statuses of switch where
1 and 2 as 2 and X=1/0
1, respectively

s disconne
ction
DTD/DTL/Auto/ d: Inv: 0-Not elmMask: status1 Regardless of how it is
Manual inverted, 1- XXXX configured, it will take on
Inverted. If where the ctlVal [CO] from the
inverted, change X=1/0 signal set to status1
1 to 0 and 0 to 1
Measurements elmMask: status1

XXXX
where
X=1/0
Table 3 Common dynamic behavior of the graphical symbols of the Single Line diagram
Table 4 shows other properties of dynamic behavior, which are present only in some graphic symbols of the Single Line diagram:
Element Name ID Name C Ind C Com Fail Color Manual Text Signal Type Dir Txt Font Txt Siz Txt POS Siz Txt PAR Siz Txt SUB
Switch with Text d: E:Name elmTxt Tx: Manual elmTxt elmTxt elmTxt elmTxt elmTxt
text Or:0/1/2/3 Tx:Ft:Source TPo:Siz Txt TPa:Txt Size TSu:Txt Size
Txt Position View Park View Substation
View
DO Switch with d: E:Name elmTxt Tx: Manual Single Signal/Double elmTxt elmTxt elmTxt elmTxt elmTxt
Text text Signal. If single, in mTxt Or:0/1/2/3 Tx:Ft:Source TPo:Siz Txt TPa:Txt Size TSu:Txt Size
DO:0, if double DO:1 Txt Position View Park View Substation
View
O Switch elmCol: CU: C Failure: Cf:
Color Undefined color Failure
DO switch O elmCol: CI: elmCol: Cf: Single Signal/Double
Color Undefined color failure Signal. If single, in mTxt
DO:0, if double DO:1
Car switch elmCol: CI: elmCol:C:
Color Undefined color
Isolator with text elmTxt Tx: Manual elmTxt elmTxt elmTxt elmTxt elmTxt
text Or:0/1/2/3 Tx:Ft:Source TPo:Siz Txt TPa:Txt Size TSu:Txt Size
Txt Position View Park View Substation
View
DO isolator with elmTxt Tx: Manual Single Signal/Double elmTxt elmTxt elmTxt elmTxt elmTxt
text text Signal. If single, in mTxt Or:0/1/2/3 Tx:Ft:Source TPo:Siz Txt TPa:Txt Size TSu:Txt Size
DO:0, if double DO:1 Txt Position View Park View Substation
View

Element Name ID Name C Ind C Com Fail Color Manual Text Signal Type Dir Txt Font Txt Siz Txt POS Siz Txt PAR Siz Txt SUB
DO isolator Single Signal/Double
Signal. If single, in mTxt
O Isolator C Ind: CI: Color C Failure: Cf:
Undefined color Failure
DO O Isolator C Ind: CI: Color C Failure: Cf: Single Signal/Double
Undefined color Failure Signal. If single, in mTxt
Analog d: E:Name ElmCol: color
Transformer
Single d: E:Name ElmCol: color
Transformer
Name d: E:Name ElmCol: color
Transformer
Fused circuit d: E:Name ElmCol: Color
breaker
Generator d: E:Name ElmCol:L:Colo elmTxt Tx: Manual fonTyp:Ft:Font
r text Txt
Relay 86 d: E:Name elmTxt Tx: Manual Single Signal/Double
text Signal. If single, in mTxt
Led d: E:Name elmTxt Tx: Manual elmTxt
text Tx:Ft:Font Txt
Local/Remote d:E:Local/Rem elmCol:Cf:colo elmTxt Tx: Manual
ote r failure text
Double E:Local/Remot elmCol:Cf:colo Single Signal/Double
Local/Remote eS or r failure Signal. If it is simple in d:
E:Local/Remot DO:0, if it is double DO:1
eD, depending
on whether it
is Single or
Dual Signal
Watertight d: E:Name elmTxt Tx: Manual Single Signal/Double
text Signal. If single, in mTxt
DTD/DTL/Auto/ d: E:Name elmCol:B0: D:E:Text. It makes DTD,DTL,Automatic/Man fonTyp: Font
Manual Color BG Off it possible to place ual,
in the Text DTD, or Manual/Automatic,Raise
M or A Tap, Lower Tap,
Raise/Lower Tap
Table 4 Other dynamic behavior properties
Table 5 shows more properties of the dynamic behavior, present only in some graphic symbols of the Single Line diagram:
Element Color Letter/ Color Serv/ B Color Color Ok Color Local Remote Color Font Style Justified Always ON Place Tilted General
A Block/ C Error Color
Analog fonTyp: Opaque/Itali Center/Left/Right
Transformer c/underlined
/black
background
Long ElmCol: colorA elmTxt: colorB fonTyp: Horizontal/v

Element Color Letter/ Color Serv/ B Color Color Ok Color Local Remote Color Font Style Justified Always ON Place Tilted General
A Block/ C Error Color
Transformer ertical
Transformer ElmCol: colorA elmTxt: colorB fonTyp: Up/Down/Le Horizontal/v
Circles ft/Right ertical
Transformer ElmCol: colorA elmTxt: colorB fonTyp: Up/Down/Le Horizontal/v
Circles ft/Right ertical
Double winding ElmCol: colorA elmTxt: colorB fonTyp: Up/Down/Le Horizontal/v
transformer ft/Right ertical
Auto- Up/Down/Le
transformer ft/Right
Lateral Up/Down/Le Down/Up
Transformer ft/Right
Transformer elmTxt:Text fonTyp: Opaque/Itali Center/Left/Right
Name c/underlined
/black
background
Fused circuit fonTyp: 0/1 elmTxt:Dir:1
breaker /2/3/4
Generator ElmCol:Tx:
Letter Color
Reclose79 elmTxt:Cls: elmCol:
Service Color Color Block
Relay 86 elmCol: fonTyp:
Color Ok Color
Error
Poly-Button elmTxt:Cls: elmCol:
Service Color Color Block
LED elmCol:E elmCol:E
0:ColorOk 1:ColorEr
ror
Local/Remote elmCol:Cl elmCol:Cr:rem
:local ote color
color
Double elmCol:Cl elmCol:Cr:rem
Local/Remote :local ote color
color
DTD/DTL/Auto/ elmCol:T0:Col elmCol:B1: elmCol:T1: elmCol: fonTyp: d: On:0 (Off)/1
Manual or Txt Off Color BG On Color Txt Color Ok Color (On)
On Error
Measurements elmCol:T0:Col elmCol:B1: elmCol:T1: elmCol: fonTyp: d: On:0 (Off)/1
or Txt Off Color BG On Color Txt Color Ok Color (On)
On Error
Table 5 More dynamic behavior properties

Lastly, Table 6 shows the properties of the dynamic behavior of semaphores:
Element Graphic Representation Status Command Operation Errors

Semaphore 86 Status: It can be renamed (e.g. AAA, R85, etc.). It Command: The command is configured in the Operation: When the BCU boots, the semaphore Errors: The element appears
consists of two status signals (Signal 1 and Signal 2). "Action/Command" field of the CNF. When the has no positioning and is grayed out. Once either with no status when the
The initial state is undetermined in gray, because until semaphore is in any of the three states (gray, color input is enabled, it does not happen again until the machine boots. It has two
one of the two inputs is enabled, it does not take the OK and color Error), the semaphore offers two equipment is rebooted. When we enable the input inputs and the element can
value of either one. It is positioned with the signals from control buttons if both acronyms (OO and OC) are configured in Signal 1, the semaphore changes to appear in a state without the
the "Status/Signal 1" and "Status/Signal 2" fields of the configured in the signal table or a control button if the color Error and, even if we disable this input, it signal that enabled it being
CNF, which, when the first one is enabled, changes its only one acronym (OO or OC) is configured, continues to be the same color. It will not change active. It has three statuses
status to "Color Error" (configurable color) and the although the only one that actually runs through the color if while Signal 1 is enabled, we enable Signal 2 (counting the initial one after
message it sends to the timer/alarm system is "A1" relays regardless of the status of the input is "OC" as well, since the color remains the same after the start-up) and always executes
(configurable text.) When the second one is enabled, it (configurable text but if the field is empty it appears states 01 and 10 are positioned, until we position 10 the same command. In the CNF
changes its status to "Color OK" (configurable color) and blank) and the message it sends to the timer/alarm and 01, respectively. When Signal 1 is disabled and default configuration,
the message it sends to the chronological/alarm system system is "A0" (configurable text.) When we execute Signal 2 is positioned, the semaphore color changes configuration is applied only to
is "A1" (configurable text.) When either signal is enabled the "OO" command (configurable text, but if the field to OK and remains the same as the previous case. the first entry and we need to
while the other is disabled, the semaphore changes to is empty it appears blank), the message it sends to In any of the three statuses, the commands have both configured.
the color configured for that signal and does not change the timer/alarm system is "A1", (configurable text) configured in the signal table are offered, but the
color until the other is enabled while the previous one is and it does not execute any action beyond activating only one that is executed is the OC activating the
disabled (attached table.) For this signal to appear in the the selection relay, since it sends a zero to the configured command relay.
event window, we have to configure the acronyms EV0 output. Note, all this is so only if the command is
and EV1, and for the alarm window, the acronyms AL0 configured in the Signal Mapping, otherwise nothing The activation of the signaling is not affected by the
and AL1. is displayed. If we configure a GAPC or GGIO latency of the TFT or by it being located on any
Functional element in this field, in the memory, this screen other than the SINGLE-LINE one. However,
element appears as in error and we cannot see what the change of color of the element on the TFT is
the command is doing on the semaphore. affected, since it is not updated until more than one
second has elapsed since we were first located on
the TFT screen.
Semaphore 79, Status: It can be renamed (e.g. AAA, R85, etc.). It is Command: The command is configured in the Operation: If the semaphore positioning is at zero, it
81, 87, 51. positioned with a signal in the "Status" field of the CNF, "Action/Command 1" field of the CNF. If we suggests the OO command which, when executed,
which - when enabled - changes its status to "Color configure a FUNCTIONAL GAPC signal as a activates a GAPC Functional input configured as a
Block" (configurable color) and the message it sends to semaphore command, when it is enabled it suggests command; this makes it remain active until the
the chronological/alarm system is "A1" (configurable the "OC" command (configurable text, but if the field opposite command is executed. To be able to
text). When it is disabled, it changes status to the "Color is empty it is Unlocked) to change the status by execute the opposite command, we must position
Serv." color (configurable color), the message it sends to sending the message "A0" (configurable text) to the the semaphore to one in order to execute the OC
the timer/alarm system is "A0" (configurable text.) This chronological/alarm system, and when it is disabled command, which causes the GAPC Functional input
signal may be a FUNCTIONAL GGIO associated with a it suggests the "OO" command (configurable text but to be disabled. The Functional GACP signal is
digital input in the Signal Table, an INOUT GGIO input if the field is empty it is Unlocked) and the message associated to physical elements of our equipment
(which must be indicated in the Signal Table to see the it sends to the chronological/alarm system is "A1" via PLC or to other equipment via gooses. In the
description) or a FUNCTIONAL GAPC used to enable it (configurable text.) But when we configure an case of a signal with a physical command, the
through a PLC function. For this signal to appear in the INOUT GGIO signal or a FUNCTIONAL GGIO semaphore is positioned in the same way and, when
event window, we have to configure the acronyms EV0 signal associated to an output, as it has only one the commands are executed, only the OC that
and EV1 and, for the alarm window, the acronyms AL0 physical output, the only control that is effective is activates a pulse from an output relay is effective
and AL1. the "OC" and, even if we have configured the "OO" while, when the OO command is executed, it is not
and we press the button to execute the command, effective because it would disable the output which,
the output does not go beyond the selection relay. It due to the fact that it is a pulse, would not act (this
must be taken into account that the texts in the could be used to disable sustained outputs.)
chronological depend on having them configured
together with the acronyms. The activation of the signaling is not affected by the
latency of the TFT or by it being located on any
screen other than the SINGLE-LINE one. However,

Element Graphic Representation Status Command Operation Errors

the change of color of the element on the TFT is
affected, since it is not updated until more than one
second has elapsed since we were first located on
the TFT screen.
Manual, Status: It can be renamed (e.g. G, R, 8, etc.) although for Command: The command is configured in the Operation: When the BCU boots, the positioning of
Automatic the ON state this is not an option. It is positioned with a "Action/Command 1" field of the CNF. This signal the semaphore is at zero, the element configured as
semaphore signal in the "Status" field of the CNF, which - when copies the value of the signal configured for the a GAPC or GGIO Functional type command is in the
enabled - changes its status to "Color Block" input. When the semaphore is enabled, the same status. If we change the input to one, the
(configurable color) and the message it sends to the command it suggests is "Manual" (non-configurable status of the control signal also changes to one. If
timer/alarm system is "A1" (configurable text.) When it is text) and changes the output value from one to zero we change the signal back to zero, the control signal
disabled, it changes to the "Color Serv." color and the message it sends to the chronological/alarm also changes to zero. When the input is at zero, the
(configurable color) and the message it sends to the system is "A0" (configurable text). When the semaphore on the TFT suggests the Automatic
chronological/alarm system is "A0" (configurable text). semaphore is off, the command it suggests is command which, when executed, changes the
For this signal to appear in the event window, we have to "Automatic" (non-configurable text) and changes the status of the signal configured as command to one.
configure the acronyms EV0 and EV1 and, for the alarm output value from zero to one and the message it After the command is executed, the status of the
window, the acronyms AL0 and AL1. sends to the chronological/alarm system is "A1" input signal does not change until a new one is
(configurable text). received and it continues to offer the same
Automatic command which, when executed again,
only refreshes the date of the one already enabled
in the first command. If we change the positioning of
the input to one, this change is reflected in the
element configured as a Functional GAPC or GGIO
command that changes to one as well. In this case,
the semaphore on the TFT suggests the Manual
command which, when executed, changes the
status of the signal configured as command to zero.
After the command is executed, the status of the
input signal does not change until a zero reaches it,
and continues to suggest the same Manual
command which, when executed again, only
refreshes the date of the one already disabled in the
first command.
The activation of the signaling is affected by the

latency of the TFT or by being located on any
screen other than the SINGLE-LINE one, since the
value of the signal set as a command does not
change until we are located on that screen. Also the
change of color of the element in the TFT is
affected, since it is not updated until more than one
second after we are located on the SINGLE-LINE
screen.
Table 6 Dynamic behavior of the graphical semaphore symbols of the single line diagram

The Figure 2-26 shows an example of the information displayed on the Elements tab:
Figure 2-26 Elements tab
It Figure 2-27 shows the characteristics of the Drawing canvas. These sizes are used to
automatically compose the Substation and Voltage Level views.
Figure 2-27 Drawing Canvas Configuration

To compose the drawing, the user must select the necessary symbols on the Library tab.
Each time a symbol is selected, it appears in the right panel, (drawing area) in the upper
left corner, from where it can be moved by dragging it with the mouse to the desired
position on the canvas.
For each symbol included in the drawing the user can change its properties. To do so,
they must select the symbol from the drawing area, and its current properties will appear
in the upper left panel, and they can be edited, as shown in the Figure 2-28:
Figure 2-28 Symbol configuration

In Figure 2-29 the properties of the Switch and Blade elements are shown.
Figure 2-29 Properties of the Switches and Blades elements
An example of a Graphic Template is shown in Figure 2-30:
Figure 2-30 Example of a Single Line Drawing Template

Once the drawing for the template has been made, the
user must select the Save option from the menu Graphic
Editor/File, as shown in Figure 2-31.
Figure 2-31 Save drawing template
The user must then fill in the name for the drawing template, see Figure 2-32.
Figure 2-32 Drawing template name
2.4.2. Graphics Association for

Bays at the HMI
Once the HMI drawing templates required for the
project are generated, the user must associate
the appropriate template for each substation bay.
This option will be enabled if the project contains

at least one HMI or UCS with HMI functions.
To do this, go to the Graphics menu, and then

Associate HMI positions:
Figure 2-33 Menu Associate HMI

positions

The following panel will be displayed:
Figure 2-34 Associate HMI positions
For each substation bay, the user must select the graph representing its Single Line. By
displaying the combo associated with each bay, the set graphics are shown, and the user
must select the one that corresponds to the bay to be represented:
The drawing area (right panel) will show the substation's General Single Line diagram
display, automatically composing the graphs associated to each bay.
Display options:
- General view of the substation: It's the default view. To return to it, we must
click on the substation label in the left panel.
- Voltage level view: To view a park, in the left panel, we must click on the label
of the voltage level to be displayed.
- Bay view: To visualize a bay, in the left panel, we must click on the bay we
want to visualize.
Bay order in the park

The user can sort the bays within the Voltage Level to which they belong, changing the
default sorting done by the application. To do this, we must select the bay we want to
reorder and press the arrow buttons on the lower left panel.
It is also possible to rearrange the Stress Levels in the General Single Line. To do this,
the user must select the park to be rearranged and press the arrow buttons on the lower
left panel.
Finally, the user can also choose to display a General Single Line Voltage Level divided
into several voltage sub-levels. To do this, we must select the bay for which we want to
split the Voltage Level and press the Separator button on the lower left panel.
2.4.3. HMI Single-Line Edition

Allows the user to manually modify the
substation's Single Line drawing for each HMI,
which were automatically generated by the
application from each of the bay’s Type Graphs.
Modifications can be done on the drawing of the
Single Line diagram or change of signals
associated with graphic elements.
The user must go to the Edit Single Line

diagram HMI option in the Graphics menu and Figure 2-35 Edit HMI Single Line
select the HMI to be edited (See Figure 2-35).
It is important to note that the main screen must be saved under the GENERAL SINGLE-
LINE name, since the application uses that criterion to decide which is the main window
in the composition.

2.4.4. Validation of HMI Single-Line signals

Allows the user to see which of the signals
configured in the HMI single-line drawing have not
been found or are not assigned. If they have not
been found, it is a sign that there is an error; if
they have not been assigned, it is for information
purposes.
Figure 2-36 Validating signals from the

Single Line
To access the report, the user must go to the Validate HMI signals option in the
Graphics menu, and select the HMI for which they want to validate the signals. A report
similar to that of the Figure 2-37 will be displayed.
Figure 2-37 Signal Validation in Single Line Report

2.4.5. Generation of the HMI single-line graph

Allows for the generation of the final SVG file with the substation's Single Line Graph for
an HMI unit.
The user must go to the Generate Single Line

diagram HMI option in the Graphics menu, and then
select the HMI for which they wish to generate the
single-line diagram, as shown in the Figure 2-38.
A file called singlelineHMI.svg will be created, which

is the file containing the single-line graph of the HMI,
in a format similar (but not equal) to the svg standard.
Figure 2-38 Generate Single Line
HMI
In the project folder there is a sub-folder
SINGLELINE/Svg/{nameIED}. In this sub-folder is where the single-line diagram
HMIsingleline.svg will be created.
2.4.6. Edit BCU Drawing Templates

It makes it possible to generate customized graphics for each type of position (bay), by
storing them as templates. In the templates the graphic elements are configured without
specifying anything particular to the project, i.e. no 61850 references will be configured,
only properties of the graphic elements so that they self-generate the 61850 references
themselves. Later, these templates can be assigned to as many bays as desired, in order
to automatically compose a first approximation to the final single-line diagram of the
substation. Most of the 61850 references are generated for the status and commands of
graphic elements, and compose the different views of the Single Line diagram: Bays
Group and specific bay.
It allows the generation of personalized graphics for each type of bay, which can later be
assigned to as many bays as desired in order to compose the Single-Line Graph for the
BCU's TFT display, in case this element is available.

The user must go to the Edit BCU Drawing

Templates option from the Graphics menu
(View Figure 2-39)
The procedure for generating Drawing

Templates for BCU is the same as the one
described in chapter 2.4.1 Edit HMI Drawing
Templates, making it possible to:
 Import: Makes it possible to store in

the current project library any Graphic Template generated
Figure 2-39 Edit BCUinDrawing
another project's
Templates
library.
 Derive: By selecting a Drawing Template from the list of existing ones and pressing
this button, a copy of the selected Drawing Template will be created, on which the
user can make the necessary changes to create a new Drawing Template.
 Modify: Makes it possible to modify and save a previously created Drawing

Template.
 Create new: Makes it possible to create a new drawing template and store it in the
library, with a name chosen by the user.
 Delete: Removes the selected Drawing Template from the library.
 Save: Stores the changes made and returns to the previous window.
 Cancel: Makes it possible to cancel the changes made, without storing them in the
library
2.4.7. Signal validation of all BCUs

It allows the user to see which signals from the single line diagrams of all the BCUs have
not been found or are not assigned. If they have not been found, it is a sign that there is
an error; if they have not been assigned, it is for information purposes.

To access the report, the user must select the

option Validate signals of all BCUs in the
Graphics menu (See Figure 2-40).
A report similar to that of the Figure 2-41 will be

displayed
Figure 2-40 Validate signals BCU

drawings
Figure 2-41 BCU Drawings Signal Validation Report
2.4.8. Generation of drawings of all BCUs

It allows for the generation of the final SVG file
with the Single Line Graph for each of the
BCUs.
The user must select the Generate drawings of

all BCUs option from the Graphics menu, as
shown in the Figure 2-38.
A file called singlelineBCU.svg will be created,

which is the file containing the BCU's SINGLE-
Figure 2-42 Generate drawings of all BCUs

LINE graphic, in a format similar (although not equal) to the svg standard.
In the project folder there is a SINGLE-LINE sub-folder, which in turn will contain one
sub-folder for each BCU with the name of that BCU. In this last sub-folder is where the
single-line fileBCU.svg will be created.
2.4.9. Editing the System Status Window

It allows for the creation of a graph corresponding to the System Communication
Architecture, which shows all of the project's communication status for all the elements in
the HMI. It can consist of one or more drawings, which we can navigate.
It is important to note that the main

screen must be saved under the
SYSTEM STATUS name, since the
application uses that criterion to decide
which is the main window in the
composition. A different drawing can be
configured for each of the HMIs in the
project (including the SCU if it is also an
HMI.) The user must go to the System
Figure 2-43 Edit System Status
Status Editor option in the Graphics
menu, and select the HMI for which they
want to edit the system status:
The following window then appears, showing the existing System Status drawings, as
shown in the Figure 2-44:
Figure 2-44 Selection of system status drawing
When selecting any of them with the mouse, their drawing is shown in the right panel, as
in the Figure 2-45.

Figure 2-45 System status drawing
The procedure for generating System Status Graphs is the same as the one described in
the chapter 2.4.1 for HMI Type Graphs, making it possible to:
 Import: Makes it possible to store any Graphic Template generated in the library
of another project in the library of the current project
 Derive: By selecting a System Status drawing from the list and pressing this
button, a copy of the selected drawing will be created, on which the user can
make the necessary modifications to create a new System Status drawing.
 Modify: Makes it possible to modify and save a previously created System Status
drawing.
 Create new: Makes it possible to create a new drawing template and store it in
the library, with a name chosen by the user
 Delete: Removes the System Status drawing which is selected in the list from the
library.
 Save: Stores the changes made and returns to the previous window
 Cancel: Makes it possible to cancel the changes made, without storing them in
the library.
The symbols library is specific to this type of drawing, representing the possible types of
equipment that constitute a project.

It is important to note that the main screen must be saved under the SYSTEM STATUS
name, since the application uses that criterion to decide which is the main window in the
composition.
2.4.10. System Status Signal Validation

Allows the user to see which of the signals
configured in the system status drawing
have not been found or are not assigned. If
they have not been found, it is a sign that
there is an error; if they have not been
assigned, it is for information purposes.
In order to access the report, the user must

go to the Validate System Status Signals
option in the Graphics menu and select the Figure 2-46 Validate system status signals
HMI whose drawing is to be validated (See
Figure 2-52).
A report similar to that of the Figure 2-47 will be displayed
Figure 2-47 Status Signal Validation Report
2.4.11. Generating the system status window

It allows for the creation of the file with the System Communication Architecture.

The user must go to the option Generate system status drawing from the Graphics
menu, and then select the HMI for which they want to generate the system status
drawing (See Figure 2-48)
A file called status.svg, which is the one

containing the system status graph for the HMI, will
be generated in a format similar (but not equal) to
the svg standard.
In the project folder there is a sub-folder

SINGLELINE/Svg/{nameIED}. This sub-folder is
where the .svg status file will be generated. Figure 2-48 Generation of system
status drawing
2.4.12. Update Project Libraries

Makes it possible to update the project drawing libraries, which contain the graphic
elements of the system. These libraries will be updated from those of the version of
saTECH-CNF from which the update is
performed.
To update the libraries the user must select

the option Update Project Libraries from the
Graphics menu. See Figure 2-49
The HMI, BCU and system status drawings

that are configured will not be lost, what will
be updated will be the drawing elements that
will be used the next time we generate those
drawings. Figure 2-49 Updating the project's graphic
libraries

2.4.13. CNF SVG File Viewer

It makes it possible to select and view any SVG generated by the CNF. If the SVG is for
HMI equipment, such as substation single line or system status, the CNF adds a tool for
status simulation and screen navigation.
Figure 2-50 Signal simulator
2.5. Tools Menu

When clicking on the Tools menu option, the following options are displayed:
Figure 2-51 Tools Menu
2.5.1. Update the application

It allows for the connection to an IED to load a new firmware version.
To update the firmware version of an IED, the user must select one of the options from
the Update the Application sub-menu of the Tools menu. See Figure 2-53
Selecting the Send Firmware option from this menu will display the following window:

The user must enter the IP address of the device, as well as the path where the file with
the firmware version to be uploaded is located.
Figure 2-52 Send Firmware
The rest of the options are specific to each type of IED, and before the selection screen
of the update file, another screen will be shown for us to configure the necessary
parameters for each saTECH equipment type.
The following is an overview of the menu, where we can see for which types of IEDs
there is a specific shipping option:
Figure 2-53 Send Firmware and Update Application
2.5.2. Standardized Signal Table

It allows us to see the standardized table of signals for the version of saTECH that we
have installed, to see the current standardized table of signals of the project, to compare
the table of the project with the table of the application (the version of saTECH that we
have installed) and to overwrite the table of the project with the application version's
table, or with another one that it has stored in an xls file.

We must take into account that the standardized table of signals is closely related to the
ICD templates of the equipment and that there should therefore be some consistency
between the two.
In order to see the standard table of signals of the version of the saTECH-CNF
installation, the user must select the option View Table of saTECH-CNF in the sub-menu
File Standard Table of Signals of the Tools menu. See Figure 2-54
Figure 2-54 See Standard Table of Signals in saTECH CNF
The options for displaying the standardized signal table will show a screen similar to that
of the Figure 2-55:
Figure 2-55 Display Standardized Signal File
To view the standardized project signal table, the user must have a project open and
select the View Project Table option from the Standardized Signal Table sub-menu of
the Tools menu. See Figure 2-56

Figure 2-56 See Standardized Project Signal Table
A screen similar to that of the standardized saTECH CNF signal table will be shown, but
with the data of the standard signal table of the Project.
To compare the saTECH CNF table with the project table, the user must have a project
open and select the option Compare project table from the Standard signal table sub-
menu in the Tools menu. See Figure 2-57
Figure 2-57 Compare Project Table
From this screen the user can carry the changes from the saTECH CNF table to the
project table and save them by clicking on the save button (See Figure 2-58). If the
user wishes to reload the project table data on the screen before saving, they can do so
by pressing the reload button.

Figure 2-58 Project Table Comparator
As we can see in Figure 2-58, the modified signals, the inserted and deleted ones are all
marked in different colors and we can easily go from one modification to the other by
using the arrows at the top of the screen, or carry the changes from the CNF table to the
project table, by clicking on the arrows and blades that will appear next to the
modifications, between the two tables. In order to save the changes made in this screen
in the TAI table of the project, it is necessary to press the save button located in the
upper left section of the screen.
In order to update the standardized project signal table with the signals of the saTECH-
CNF installation version or with those of an external xls file, the user must select the
Overwrite Project Table option from the Standardized Signal Table sub-menu of the
Tools menu. See Figure 2-59
Figure 2-59 Update Standardized Project Signal File

The user must select the update source or the saTECH CNF version file, or provide a file
with standardized signals.
2.5.3. Update CID Templates

Makes it possible to carry the updated saTECH-CNF ICD templates (those of the installed
version + those of the 17.08u00 version) over to old projects. In addition, there is an
option to automatically update the ICD version of all IEDs whose current version of the
ICD is that of the project (the most recent
version of ICD templates that the project had
before the update.) When performing the
update, the project's template version will
become the version of the installation, even
if we do not tick the option to automatically
update the ICD version of all IEDs whose
current version of the ICD is that of the Figure 2-60 Update CID Templates
project version.
The improvements in the ICDs are for extensions of new functionalities in the SAS
systems. An ICD file, normally only has modifications at template level and/or internal
alarms to maintain compatibility between new CIDs and old equipment; an exception
would be version 17.08u00. When the user performs configurations with the new
templates, they will have a value as an instance of the CID and therefore as one in the
computer (there are old versions where this could cause problems.)
When the user selects the update the CID templates option, if the project already has the
templates corresponding to the 17.08u00 version of saTECH CNF, then these will always
be updated automatically when updating the rest, without asking for a specific
confirmation. However, if the version of the saTECH-CNF templates already exists in the
project, confirmation will be requested and the option will be given to save the current
ones in the project by renaming them to another version. See Figure 2-61
In the same project we can have several versions of ICD templates of the same
equipment model and we can change the ICD version for a specific IED at any time from
an IED’s Advanced Properties configuration screen, without having to change the
version of the rest of the IEDs. To reach this configuration screen the user would have to
go to the IED menu, and right-click on an IED to access the menu.

In this menu, they will select the Advanced Properties option in the Configurable
Parameterssub-menu.
To add the CID Templates of saTECH-CNF (those of the installed version + those of the
17.08u00 version) to the project, the user must select the option Update CID Templates
from the Tools menu. See Figure 2-60
If the project already contains templates of the same version, the user will be asked for
confirmation before any action is taken. Optionally, the user can create a backup by
renaming the current templates, and will be offered the option to update all templates
from the template version of the project to the current one.
Figure 2-61 CID templates update confirmation
If the project does not yet contain the templates of the current installation version, then no
backup is necessary, since the previous templates of the project will always be
preserved, and therefore the user will only have to decide whether or not to update the
templates in all IEDs whose current version is the project version. The user will usually be
interested in performing this update, except when the IEDs in the saTECH range of the
project are very old and will not be updated, in which case it will probably be in the
interest of the user to update the template of each IED to the 17.08u00 version.
Figure 2-62 CID templates update confirmation

2.5.4. Validate CIDs

It allows for validation of the IED’s CIDs of the project against the schemes of the
standard 61850 2.1 edition, indicating the deviations and how to solve them. The
messages that this validation will show us will normally be warnings and not errors, since
the equipment supports edition no. 1 in most cases.
When this option is enabled, the CIDs which are currently in the project folder are
validated. This way, it is possible to validate the CID files of projects imported with
previous versions and to validate the new CID files generated by the current version as
well, by previously executing the option 2.1.7.Generating Configurations
When integrating non-saTECH equipment by means of CID files, 'OTHER

MANUFACTURERS' type IEDs, the validator can report "Problems" due to issues related
to the validation of configuration files in accordance with the second edition IEC 61850,
but many of them are solved when loaded into the saTECH equipment itself. It is
recommended to use the Update CID options, in order to allow new transformations and
try to auto-solve possible problems.
There are two message solving modes, both of which can be accessed from the IED
menu by right-clicking on the IED:
- "Update CID > Select CID" mode will be updated with a file external to the CNF,
preferably the CID loaded in the
Other Manufacturer's equipment
- "Update CID > Internal CID" mode

will obtain the copy of the original
file to apply the new
Figure 2-63 Updating a third-party CID
transformations. See Figure 2-63
As we have seen in the Update CID Templates section, there is an option to update the
project templates as separate ICD files for each saTECH equipment type. In addition,
from the Advanced Properties configuration screen of an IED, we can change the
version of the ICD for a specific IED at any time, without having to modify the version of
the rest of the IEDs.
To reach this configuration screen the user would have to go to the IED menu, and right-
click on an IED to access the menu. In this menu, they will select the Advanced
Properties option in the Configurable Parameterssub-menu. See 4.4.15.9.

The improvements in the ICDs are for extensions of new functionalities. An ICD file only
has template-level changes and/or internal alarms to maintain compatibility between new
CIDs and old equipment. When the user performs configurations with the new templates,
they will have a value as an instance of the CID and therefore as one in the computer
(there are old versions where this could cause problems.)
2.5.5. Configure Logos

Makes it possible to select a logo for each
SCU and HMI in the project. In both cases the
chosen logo will be used on the IED website,
and if it is a SCU, then it will also be used on
its display.
Figure 2-64 Logo Configuration
To configure the logos, the user must select the option Configure Logos from the Tools
menu. See Figure 2-64 Logo Configuration.
From this option, they will access the logo configuration screen, where they can select a
logo for each SCU and HMI of the project.
Figure 2-65 Logo Allocation
From this screen, we can preview the logo by clicking on it in the view column. We can
also remove it or replace it with another one.
When a logo is configured, it will be updated on the corresponding IED detail screen.
Figure 2-66 SCU with changed logo details

2.5.6. Configure Equipment Models

It allows for configuring the Equipment Models for the Master Protocols - that is, the
server/slave equipment models of a certain protocol - so that we can create equipment of
these models when we are configuring a master protocol in one of the IEDs of the
saTECH range.
The equipment model will be shared by all projects

in the CNF installation, and when exporting a
project, the information of the equipment models it
uses is included in the export file, so that it can be
added to the CNF installations where that project is
Figure 2-67 Configure Equipment
imported. Models
The user must select the option Configure Equipment Models from the Tools menu
(ViewFigure 2-67).
From this option, we can access the Equipment Model Configuration screen of the
Figure 2-68. Each model belongs to a specific protocol, therefore each protocol will have
different parameters.
Figure 2-68 Configuration of equipment models for each master protocol

The Model name will be used to identify its own LNodeType from the CID templates, the
values will be used in CID templates (DataTypeTemplates) as default values for all new
specific equipment (used in master profiles), and the possibility to configure the Model
value so that they are not configurable by a specific profile's equipment (checkbox on the
right of each parameter.)
2.6. Historical Menu

Makes it possible to view the historical records stored in the equipment and to configure
them
2.6.1. See history

It allows for the connection with a saTECH BCU or saTECH RIO type IED (CUFO or MES
functionality) and the stored historical records display. To perform this operation it is not
necessary to have any project open.
Figure 2-69 See History
The following figure shows an example of the Historical Records stored in the equipment:
Figure 2-70 Displaying historical records

These can be sorted by any of the columns (Record, Time, Description, Status, Quality)
and exported to a *.csv file, as shown in the figure below:
Figure 2-71 Historical records export
2.6.2. Configure Historical Measurement Records

Makes it possible to configure the system’s historical records to be displayed on the HMI
of the current project or on the SCU-HMI if there is no HMI, as shown in the Figure 2-72.
Figure 2-72 Historical record configuration
We can configure the number of records stored by the HMI to display the history of the
analogs, there are also two types of historical records supported:
 Historical record by time. Set the time in seconds for the "Period" field.
 Historical record by event. By enabling the "By Event" option, the HMI will record
the values for a change of value in the analog.
It allows for configuring measure-associated values grouped into 3 Categories:

 GGIO: It offers the possibility of associating measurement values that are

acquired via communications (for example, in a DNP master protocol profile) in
the SCU or HMI.
 MMTR: Variables associated to this LN (Counters or accumulated values)
o TotVAh; TotWh; TotVArh; SupWh; SupVArh; DmdWh; DmdVArh
 MMXU: Variables associated to this LN (instant values)
o TotW; TotVAr; TotVA; TotPF; Hz; PPV; PhV; A; W; Var; VA; PF; Z
Additionally, it offers the possibility of selecting measurements by selecting custom 61850

references. To view all IED signals, it is necessary to be subscribed to all Reports, and it
will be necessary to close the tab in order to reload the tree.
“Select Signal" button , opens the substation

IED signal tree with its ST and MX signals, and
all subscribed signals.
"Signal group": It transforms the 61850 specific

reference into a generic one to allow for
groupings in the HMI.
“IED name”: Add the name of the IED in the

selected reference.
Figure 2-73 Signal tree of the historical record
Figure 2-74 Custom measures selection

Therefore, for the same measurement, three configuration modes are possible, e.g.
UCSLVE__GENERAL/DNP_GGIO1.AnIn1.mag.i allows for the configuration shown in the
Figure 2-74.
The personalized references will be unique in the historical records.
The analogs entered in the measurement logs require the configuration of the Units,
"SIUnit" and "Multiplier" of the signal file (see section 4.4.11.1.3 Data Acquisition Mode).
2.7. Help Menu

- Language: Offers the possibility of changing the
language of the saTECH CNF application, but not
of the project. Note: the internal alarms which are
self-generated in the CIDs will be generated in
the language found in the saTECH CNF.
Figure 2-75 Help Menu
- User Manual: Displays the User Manual with the
Operating System's default PDF viewer.
- About: Displays the configurator version.
Figure 2-76 CNF version
Note: The window with the version number has keyboard shortcuts to view information on
the new version of saTECH CNF. For more information consult your distributor.

PROJECT ENGINEERING AND IED CONFIGURATION
Chapter 3. Project Engineering and IED Configuration
From the Project Panel the substation structure is configured, and the IEDs are added for each
bay, together with the functions performed by the IED for that bay.
3.1. Voltage level

Right-clicking on the Substation name displays a window with the option to add a new
Voltage Level (see Figure 3-1):
Figure 3-1 New Voltage Level

A window similar to the Figure 3-2 below is displayed, where the name, description and
voltage level can be defined:
Figure 3-2 Voltage Level Name

The number of characters allowed for the voltage level name is configured in the advanced
properties of the project and by default it will have a minimum of 1 character and a
maximum of 8.
The new substation voltage level will be displayed on the Project Panel:
Figure 3-3 Voltage level in the substation
3.2. Bay
Right-clicking on the name of the Voltage Level displays a window with the option to add
the new Bay (See Figure 3-4)
Figure 3-4 New Bay

A window will then be displayed allowing us to enter the name and description of the bay:
Figure 3-5 Name of the Bay

The number of characters allowed for the name of the bay is configured in the advanced
properties of the project and by default it will have a minimum of 1 character and a
maximum of 8.
The Project Panel will display the new bay at the voltage level to which we have added it:
Figure 3-6 Voltage level in the substation

3.3. Adding IED

To register an IED, we must right-click on the name of the bay:
Figure 3-7 IED registration
The IED Allocation window displays the available equipment models. In this window we
must determine the name of the IED:
Figure 3-8 IED allocation
In this screen we will select the equipment model and name.
It is also possible to press the button to the right of the name in order to select an IED that
already exists in the project and add it to the bay to which we are allocating the IED. In this
case, the model of the equipment will be selected automatically.
After selecting the model of the equipment and its name, it is necessary to register the
Control Functions that we will implement, as shown in the Figure 3-9:

Figure 3-10 Control Functions
Each function has one or more logical nodes associated to it.
If function modeling is used in the IED (although currently bay modeling is recommended),
each function has the LLN0 and LPHD nodes of ASG_LLN0 and ASG_LPHD type
respectively, at least.
In the following Table 7 we can see the available Control Functions and their specific
logical nodes:

Allows
Control Function Description Logical Nodes Identifier
LNPrefix
CSWI Switch or Blade Control CSWI, CILO Yes
XSWI Blade Status XSWI Yes
XCBR Switch Status XCBR, SIMG Yes
Switch Synchronization Control (25 *

RSYN RSYN Yes
Synchrocheck)
YPTR Transformation Bank YPTR, YLTC, CCGR No
*
MOPR Operation Measurements with Phases MMXU Yes
*
MBAL Measurement for Energy Balance MMTR Yes
MPQM Power Quality Measurement - No
SERV Supervision for the Substation Services - No
ZSEV General Services - No
ZAXN Auxiliary Services ZAXN No
ZBAT Battery Bank ZBAT No
ZCAP Capacitor bank ZCAP No
ZEGE Emergency Plant - No
ZREA Reactors - No
GAPC Generic Logic Functions GAPC No
GGIO Generic Inputs and Outputs GGIO No
GGIO-USER GGIO with User Alarms GGIO No
Table 7 Control functions with logical nodes
The RSYN function is only available in BCU devices with TP and TC board and CID
version 2.1.1 or higher.

Some functions need to be associated with each other, for example to connect the
Command-State-Lock on a Switch or Blade, allowed with the Figure 3-11 Associate
Function.
Figure 3-11 Associate Function

Once the IED is added, we can add more functions by right-clicking on it.
Then we must select the equipment model that is necessary for the Project. Pressing the
Next button of the Figure 3-12, we select the Hardware Module Data, in the Figure 3-13
we can see the screen that will be shown when the IED we have selected is a BCU or RIO.
Figure 3-13 Hardware model selection

The equipment model can then be edited at any time from the IED panel. By right-clicking
on the Hardware Model and selecting the Edit Hardware Model option from the pop-up
menu, as shown in the Figure 4-1.
The hardware model defines a number of physical capabilities as shown by the Figure
3-13:
 Levels
 Model
 TFT display
 Ethernet port type
 Power supply and acquisition voltages
 Number of Digital Inputs, Digital Outputs and Analog Inputs per level
The nomenclature used to define the model of the saTECH BCU is as follows:
STF-ABC-DEDEDE-LT where:
 S: Model, fixed at 1 representing the 100 series
 T: Size of the equipment (U):

o 2: 19" x 3.50" (88.90) Rack - 2U
o 3: 19" x 5.25" (133.35) Rack - 3U
o 4: 19" x 7.00" (177.80) Rack - 4U
o 5: 19" x 8.75" (222.25) Rack - 5U
 F: Functionality
o 1: Inputs/Outputs (CUFO)
o 2: Bay Controller (CDAM)
o 3: Remote modules (MES)
 A: Supply voltage
o 5: 125 VDC
o 8: 48 VDC
o 0: 250 VDC
 B: Pickup voltage
o 5: 125 VDC
o 8: 48 VDC
o 0: 250 VDC

 C: Back Ethernet port

o F: ETH Dual-Fiber 100Base - FX (ST Type)
o C: ETH Dual-Copper 10/100Base - TX (RJ45 Type)
o L: ETH LC Fiber
 D: Bus cards
o 1: 16 Digital Inputs with independent common ground
o 2: 32 Digital Inputs with common ground every group of 8 inputs
o 3: 16 Digital Outputs
o 4: 16 Analog Inputs (mA, V)
o 5: 4U / 4I. PT, TC Analog inputs
o M: CPU card
o P: CPU card Model P
o X: There is no card on this level
 E: Expander type card

o A: 16 Digital Inputs with independent common ground
o B: 32 Digital Inputs with common ground every group of 8 inputs
o C: 16 Digital Outputs
o D: 16 Digital Inputs with common ground every group of 8 inputs and 8
Digital Outputs
o E: 4U / 4I. PT, TC Analog inputs
o F: 4SB / 8SD. 4 Bistable and 8 Digital Outputs
o X: There is no card on this level
 L: LCD display. All 100 series devices have an LCD display
 T: Graphic display.
o F: TFT graphic display available
o X: No graphic display available

In the IED Panel we can verify the model of the new IED (see Figure 4-1), and in the IED
Details Panel, a photo of the equipment and the information that was determined with the
equipment code is displayed (see Figure 3-14)
Figure 3-14 IED details panel
If the equipment is a SCU, the Figure 3-15 menu will be displayed, although since the SCU
are substation equipment, they will usually not be registered from this menu, but rather
from the IED Panel, by right-clicking on IEDGroup "IEDs", so as not to link them to any
particular bay.
Figure 3-15 SCU Hardware Model Edition
 Network Port Number: Number of Ethernet cards available in the equipment.
 Serial Port Number: Number of serial ports available in the equipment.
 SCU model: SCU-121 hardware or SCU-131 hardware.

If the equipment is an HMI, the menu of the Figure 3-16 will be displayed, although as the
HMI are substation equipment, they will usually not be registered from this menu, but
rather from the IED Panel, by right-clicking on IEDGroup "IEDs", so as not to link them to
any particular bay.
 Network Port Number: Number of Ethernet cards available in the equipment.
 Serial Port Number: Number of serial ports available in the equipment.
Figure 3-16 HMI Hardware Model Edition
3.4. Add Function

In order to add a function to an IED in a bay, we must right-click on the name of the IED.
Figure 3-17 Add Function
A screen similar to the screen for selecting functions when adding IED (see Figure 3-18
Associate Function) will appear, as already seen in the 3.3 Adding IED section.

3.5. Association of functions

The functions of an IED that are in the same bay can be associated to each other,
configuring them with the same prefix and instance number.
When we right-click on a function, if it does not have a prefix and instance to associate itself
with another one, then we will see the option "Add association" and if it already has a prefix
and instance configured, then we will see the options "Edit association" and "Remove
association."
The case of the CSWI function is special. As it has a particularly strong relationship with
XSWI and XCBR functions, when we add an association to a CSWI function, we are asked
to select an XSWI or XCBR function to which we will assign the same prefix and instance.
And when we edit/delete the association of the CSWI or XSWI or XCBR, we will also be
editing/deleting the association of their associated function.
3.6. Edit Project

When right-clicking on the project name, a menu is displayed with the option to edit the
project:
Figure 3-19 Edit Project
Next, we will see screens similar to the project creation screens (See 2.1.1 New Project)
with the only difference being that now we will be allowed to uncheck the "Show advanced
settings" option, so that the advanced settings screen is shown.
3.7. Edit/Delete Voltage Levels and Bays

When right-clicking on the name of the Voltage Level or Bay, a menu is displayed with the
options to edit and delete.

Figure 3-20 Edit/Delete Voltage Level or Bay
The editing screens are similar to the creation screens, already seen in the sections 3.1
Voltage level and 3.2 Bay
3.8. Removing IEDs and Functions

By right-clicking on the name of the IED or function, a menu with the option to delete is
displayed.
Figure 3-21 Removing Functions on Bays and IEDs
3.9. Update CID Templates

By right-clicking on the Project name, a menu is displayed with the option to update the
CID templates:
Figure 3-22 Update Project CID Templates
This option is the same as the one that can be found in the Tools Menu of the Main Menu.
See section 2.5.3 Update CID Templates for details.

IED GROUP CONFIGURATION
Chapter 4. IED Group Configuration
4.1. Hardware Model

It makes it possible to edit the hardware model
of an IED. To do so, right-click on the IED
hardware model, in the IED panel. See Figure
4-1
Figure 4-1 Hardware Model Edition
A screen with the same options as the

Hardware Model configuration wizard will be displayed for Adding IED.
This option is not available for other manufacturers' equipment.
4.2. Publishing configuration

The publishing options of the saTECH BCU are shown in the Figure 4-2 Goose and Report
Figure 4-2 Gooses and Reports Configuration
4.2.1. Goose Control Block

To add a GoCB (Goose Control Block) to
the equipment, we must right-click on the
word Publication, from the IEDs Panel,
then Add New, and then GSEControl,
as shown in the picture Figure 4-3:
Figure 4-3 GSEControl

Figure 4-4 New GSEControl
In the next window the Goose Control Block (GoCB) can be configured:
To configure a Goose Control Block (GoCB), the following fields must be defined:
- Type of signals: Signals it stores (binary states or measurements).
- GooseID: Goose message identifier
- VLAN ID: The VLAN Identifier is responsible for controlling the data flow and real-
time behavior of messages within a VLAN. The range of possible values is between
000 - FFF
- VLAN priority: Its function is to prioritize the Goose message within the VLAN, in a
range of 0 to 7.
- MAC address: Identifies the source and enables Goose message filtering. It must be
unique for an application within the subnet. Format: 01-0C-CD-01-0X-YY, where X
can be 0.1 or 2; Y is between 0 - F.
- APP ID: This is the application identification, it must contain four characters (0-F),
identifies the source and allows for Goose messages filtering. It must be unique for
an application within the subnet. Hexadecimal format.

Next, a list of the DataSets registered for the selected type will be displayed, from which
the user must select the one they wish to associate to the GSE Control Block that they are
registering.
The gooses publication modeling is detailed in the Publication of gooses section of this
document. Once the Goose Control Block has been configured, the following window is
displayed when the Next button is clicked:
Figure 4-5 Add DataSet
In this window, by clicking on the "more" button, a new DataSet is registered, as shown
in the picture Figure 4-6:
Figure 4-6 New DataSet

In the window shown in the Figure 4-8 the signals in a DataSet can be added. We will be
able to choose: in the LN INOUTGGIO1 we have all the signals of the first level of the
equipment available and in the LN INOUTGGIO2 we have all the signals of the second
level of the equipment available.
Figure 4-7 DataSet Available Signals
Depending on the type of signals that were selected when the GSEControl was configured
(see Figure 4-4), different signals will be available in the signal tree. For example, if we
select Binary States we will now have the value (stVal[ST]), quality (q[ST]) and time stamp
(t[ST]) attributes of the logical nodes available, so as to be able to form with them the list of
signals within the DataSet.
We can select several signals at the same time by holding down the Control key while
making our selections.

Figure 4-8 DataSet Attributes
We also have the option to make the selection at the Data Object level in which case all its
Data Attributes will be automatically selected according to the Functional Group filter we
had when making the selection. If the Data Object has a hierarchical structure, either
because some Data Attribute has other Data Attributes (case of DA with bType 'Struct') or
because the Data Object has other Data Objects (case of DO with SDO)
Figure 4-9 Selection at the Data Object level
In the IED Details Panel we can see that there is a section called Publishing, and that
space is divided into GSEControl and ReportControl:

Figure 4-10 Publication Space GSEControl
In the GSEControl section we have the GoCB that was created with the name GSE01, and
when double-clicking on it, the following figure will be shown:
Figure 4-11 GSEControl
In this section, all of the attributes that were added to that DataSet can be verified.
From this window, by pressing the Delete button, we can remove the created GSEControl
from the IED. By pressing the Modify button, we can edit its configuration parameters.
To see how to edit the DataSet see the 4.4.9.2 Edit a DataSet section

4.2.2. Report Control Block

To add a RCB (Report Control Block) on the computer we mustright-click on the word
Publication in the IEDs Panel , then Add New, and finally ReportControl, as shown in
Figure 4-12
Figure 4-12 ReportControl
In the next window, the Report Control Block (RCB) can be configured:
Figure 4-13 New ReportControl
The fields to be entered are:
- Type of signals it stores: Binary states or measures.
- Type of Report Control: With or without buffer
- Report Name

- Buffer time: Storage depth, in case of a buffered RCB
- Trigger options: Causes for the transmission of the RCB.
- Integrity period: If the integrity option has been selected, period for the cyclic
reporting.
- Association by clients: With this parameter we can specify whether the server that
publishes this report should reserve a connection for a particular client or clients. If it
is not disabled, in addition to the reserved connections that are specified, one more
will always be created so that it is possible to connect from a client, such as
IEDScout. If According to number of computers is selected, the server will be
configured to allow as many connections as number of subscribed computers there
are (plus one so that we can connect from a client), but without reserving any
particular connection for any particular client.
The names for the Report Control Blocks will be generated automatically, following the
rules below:
- The first part corresponds to the name of the RCB, and will have one of the
following values
o brcbEDO for binary states, when the RCB is buffered
o brcbMED for the measurements, when the RCB is buffered
o urcEDO for binary states, when the RCB is without buffer.
o urcbMED for the measurements, when the RCB is without buffer.
- The second part should be the consecutive number indicating the RCB number,
according to the number of existing clients in the project. We should always start
with number 1.
Once the Report Control Block has been configured the following window will be displayed
when clicking on the Next button, which will show a list of the DataSets registered for the
selected type and will also give us the option of creating a new one by clicking on the
"more" button :

Figure 4-14 Add DataSet
The procedure is the same as for the GSEControl, as explained in the previous section.
The only difference is that in this case the references of the signals we publish through the
DataSet will be added at the Data Object level instead of at the Data Attribute level. Note in
Figure 4-15 that only one reference has been added at the level of Ind1[ST] instead of
adding Ind1.stVal[ST], Ind1.q[ST] and Ind1.t[ST]
In the IED Details Panel we verify that there is a section called Publication, where the
created RCB appears:
Figure 4-15 Report DataSet Edition

Figure 4-16 Publication Space
In the ReportControl section we have the RCB that was created, called brcbEDO1, and
when double-clicking it, the following figure is shown:
Figure 4-17 Report Control Block
In this section all of the attributes that were added to that RCB can be verified.
From this window, by pressing the Delete button, we can remove the created RCB from
the IED. By pressing the Modify button, we can edit its configuration parameters.
To see how to edit the DataSet see the 4.4.9.2 Edit a DataSet section

4.3. Logic functions

To add a logic function to the equipment, we must right-click on the word Logic Functions
in the IED Panel, then Add New and at the end Logic Functions, as shown in Figure 4-12
Figure 4-18 Logic Function
Then, a window will be displayed to determine the name and description of the Logic
Function:
Figure 4-19 Logic Function Name

When pressing finish, the new logic function will be created and the logic functions screen
will open up, where we can set the variables and configure the logic function in FBD
(Function Block Diagram) language.
Figure 4-20 Logic functions screen before loading the signal tree
Although this screen appears instantly (See Figure 4-20), to see the table of variables we
must wait until the signal tree is internally loaded, tree from which saTECH-CNF creates
and validates the variables (See Figure 4-21).
Figure 4-21 Logic functions screen after loading the signal tree

The added logic functions will be displayed in the IED Panel and in the Details Panel of
each IED. Both can be seen in the Figure 4-22
Figure 4-22 Logic functions panels
Double-clicking on a logic function in either panel will open up a window with information
on the logic function. See Figure 4-23
Figure 4-23 Information panel of a logic function

The Properties button shows a screen that allows us to modify the logic functions data
panel, name and description. Edit Logic Functions will show the logic functions editor, as
we can see in the Figure 4-24.
Figure 4-24 Logic functions edition
In the same figure we observe:
- At the top a Logic Functions Toolbar
- On the left side, we can see several tabs with the different types of Logic Functions
available, which we can drag to the panel. And below, a navigation screen where we
can see which part of the graphic is being displayed, quickly move to another part or
change the zoom level.
- On the right side we have the table of variables, in which we determine the inputs,
outputs, auxiliary variables and constants that we will use in the logic functions. And
underneath we have the panel on which we will form the logic functions.
4.3.1. Logic Functions Toolbar

To edit and configure the logic functions, a toolbar is available at the top of the screen, as
shown in the Figure 4-25 Logic Functions Toolbar.
Figure 4-25 Logic Functions Toolbar

Each of the buttons on this toolbar is shown in the Table 8 Logic functions toolbar
functionality:
Create new logic function, and

save the logic function in the Undo and redo.
BD.
Import and Export panel logic
Create a text box.
functions. MXE format.
Add and delete blank sheets. Source.
Add and delete variables from

Font size.
the variables table.
Zoom. Bold or italic text.
Text search. Change colors, boxes and text.
Cut, Copy and Paste. Align text.
Delete. Print.
Table 8 Logic functions toolbar functionality
4.3.2. Table of variables of the logic functions

The table of variables is the place where we will define the input, output, and auxiliary
variables, as well as the constants, so that they can be used in the logic functions.
It has been introduced in the latest versions of saTECH CNF to facilitate the management
and location of the different signals in the logic functions. It is also the first step in
facilitating a possible future migration of the E3 format logic functions to the PLCOpen
format on which the logic functions of the future IEC 61850-90-11 standard will be based.
When migrating logic functions from a previous version, the variables will be automatically
created from the logic inputs and outputs and, in the case of input signals and output
signals, the variable’s name will be created from the acronyms or from the template
descriptions if the acronyms are not configured.

Figure 4-26 Table of logic functions variables
As we can see in the Figure 4-26, the logic functions table has the following columns:
- Name: It's the name of the variable. If the signal has no set acronym, when a
variable is registered, the name is automatically created from the acronym or from
the descriptions in the CID templates. We can then modify it by double-clicking on
the corresponding cell, or by selecting the cell and pressing the F2 key.
- Class: It tells us what type of variable it is, that is, whether it is an input variable, an
output variable, an auxiliary variable or a constant. Only signals with CF, SP, ST or
MX function group can be input variables and only signals with CO, ST or MX
function group can be output variables. If a variable is not yet being used in the
current logic function (it has not been dragged onto the blank sheet) and, according
to its functional group, it could be either an input or an output variable, then we can
change its class by double-clicking on the corresponding cell, or by selecting that cell
and pressing the F2 key. For more information, see 4.3.2.1 Types of variables.
- Type: Indicates the 61850 data type to which the signal belongs. This column is non-
editable, since the ICD templates already set what type of data each signal has. For
more information on the 61850 and 61131 data type equivalences, see the table
Table 10 Data type equivalence in logic functions.
- Reference: It is the 61850 signal reference that we are configuring as input or

output. For the rest of the variables - auxiliary variables and constants - this field is
meaningless and will therefore be empty. The input and output variables can be
edited by double-clicking on the corresponding cell. Changing the reference will
automatically update the value in the Type column.
- Value: This field is used for constants, so it will remain empty for all other variables. If
the variable is a constant, we can modify the content of this field by double-clicking or
selecting the cell and pressing the F2 key.

- Use: It tells us if the variable contains any errors, if it has already been dragged to a
sheet of the current logic functions panel and if there is a variable of the same type
(input/output) that uses the same reference in any other panel. We must take into
account that the variables of each logic are independent and can only be related
through the reference, that is to say: if in a logic we have a variable named "Input 1”
and in another one a variable with "Input 1” as its name as well, but they do not have
the same reference, then there is no relation between them. When we place
ourselves over the cell of the signal corresponding to this column, a 'tooltip' will be
shown with information about the variable’s use. The symbols used in this column
are as follows:
Used in another logic

Used in the current
Symbol Contains error functions
logic functions panel
panel of the same IED
No No No
Yes No No
No No Yes
Yes No Yes
No Yes No
Yes Yes No
No Yes Yes
Yes Yes Yes
Table 9 Symbols in the 'Use' column
4.3.2.1. Types of variables

Variables can be of four types: Inputs, outputs, auxiliary variables and constants
The inputs of the logic functions can be associated to a physical Digital Input of the
equipment, to a Goose (previously saTECH BCU must be subscribed to the IED that
publishes that Goose), to some logical node's state or to another logic function’s result.
In the logic functions’ Outputs, we can take the result of the logic to a Digital Output or
some logical node’s status. GGIO and/or GAPC are often used

Auxiliary variables are used to divide a logic function into several simpler ones or to reuse
a part of the function that is common to several others. Thus they would be used as a logic
function output and as an input for one or more logic functions.
Constants are used to determine a fixed value to be used in one or more inputs.
Some table cells are editable: Names of the variables, class for switching from input to
output and vice versa (if the signal is not yet used and the function group is valid for both
input and output) and initial value of the constants. To edit these cells we can double click
on them or select them and press F2.
4.3.2.2. Adding variables to the variables table
4.3.2.2.1. Adding variables from the menus

To add variables to a logic function we can right click on the logic table and a menu with
several sub-menus will appear. The first three sub-menus will allow us to: add variables at
the end of the table, add variables above the selected row and add variables below the
selected row.
Figure 4-27 Add Variables Menu
We can also directly access the sub-menu that adds variables to the end of the selected
row by clicking on the "more" button in the Logic Functions Toolbar.

Figure 4-28 Add Variables Menu
Once we are inside the desired sub-menu, we will see an option for each type of variable
we can add.
If we press on input signal or output signal, we will be shown a signal selector with all
available signals for the selected variable type.
Figure 4-29 Signal Selector
Pressing the accept button will add the new variable to the table with a name formed from
the acronyms or template descriptions. By double-clicking on the name of the added
variable (in the table) or by selecting the name cell and pressing F2, we can change the
name if we so wish. If the variable is not yet being used and the signal's functional group is
allowed in both types of signals, it will also be possible to change the input to output type or

vice versa; to do this, we would have to double click on the corresponding cell or select the
cell and press F2.
If what we add is a local variable, the only thing we will be asked for is the name of the
variable, and a new local variable of the BOOLEAN type will be added, since it is currently
the only type we allow for local variables.
If we are going to add a constant, a menu will appear for us to select the name, type and
value. See Figure 4-30 New Constant
Once created we can change the name or the

value by double clicking on the corresponding
cell in the table or by selecting the cell and
pressing F2.
Figure 4-30 New Constant

4.3.2.2.2. Adding variables
by dragging and dropping
We can also add variables that are input signals by dragging them from the signal table. To
do this, with the logic functions editor open, we can open the IED's Signal Editor (see
Figure 4-31 IED Signal Editor) and sort them as we like, so that we can easily drag the
signals from the Signal Editor to the Variable Table (see Figure 4-32 Dragging signals from
the signal editor).
Figure 4-31 IED Signal Editor

Figure 4-32 Dragging signals from the signal editor
Note: Although when dragging the variables they are always created as input signals, if the
signal's functional group allows it, it is possible to change them to output signals by double-
clicking on the cell in the Class column or by selecting that cell and pressing F2.
4.3.2.3. Deleting variables

Variables can be deleted either by selecting them in the table of variables and right-clicking
to display the pop-up menu with the delete options (see Figure 4-33) or by selecting them
in the table of variables and pressing the 'minus' button Logic Functions Toolbar to
display the pop-up menu with the delete options (see Figure 4-34)
Figure 4-33 Delete variables from the table.

Figure 4-34 Delete variables from the table.
If the variables are already in use, in addition to being deleted from the variable table, they
will also be deleted from the logic panel.
4.3.3. Configuration of the logic functions

The available Logic Functions are displayed in the Logic Functions tabs; to add a logic
function to the blank sheet, we must simply select it by clicking on it and dragging, as
shown in the Figure 4-35 Dragging a logic function
Figure 4-35 Dragging a logic function
To add a variable or a constant to the blank sheet, we must simply select it by clicking on it
on the table of variables and drag it, as shown in the Figure 4-36 Dragging a variable from
the table of variables.
After dragging a variable to the edit panel (blank sheet), when we select the entry in the
edit panel, the corresponding row of the variable table will be automatically selected.

In order to link the input and the logic function, we must place the mouse over the right end
of the input until a green rectangle is shown, and we must then click on the green rectangle
and hold down and drag the mouse to one of the logic's pins, and they will be joined by a
line, as shown in Figure 4-37 Link between the blocks
Figure 4-36 Dragging a variable from the table of variables
Figure 4-37 Link between the blocks
An example of a logic function to perform the supervision of switch trip coils is shown here
Figure 4-38 .
Figure 4-38 Trip coil supervision of a circuit breaker

When making the connections between the logic functions we should respect the type
equivalences between 61131 and 61850. Also taking into account that:
 In the PLC of the saTECH equipment, 64 bits are always used to store the real
values, so the FLOAT32 signals of 61850 must be considered as LREAL in the
logic functions, instead of being considered REAL.
 Types 61850 Dbpos are processed by the PLC as INT32 (DINT).
 In 61131, the TIME type data has the format t#10ms, but the PLC in the TP, TON
and TOFoperators, admits any INT32 (DINT ) as input, interpreting it as time in
milliseconds.
61131/PLCOpen Groupings/Type PLC 61850 N bits

inheritances in 61131
SINT INT8 8
INT INT16 16
DINT DINT Int (32 bits) INT32 and 32

some
Enumerated
ANY_INT
LINT LINT Longlong INT64 64

ANY_MAGNITUDE
(64bits)
ANY_NUM
USINT INT8U 8
UINT INT16U 16
ANY_ELEMENTARY
UDINT INT32U 32
REAL LREAL double FLOAT32 32

ANY_REAL
(64 bits)
LREAL LREAL double (64 bits) FLOAT64 64
TIME DINT Int (32 bits)
BOOL BOOL bool BOOLEAN 1
BYTE DINT Int (32 bits) Dbpos and 8

Coded
Enum
ANY_BIT
WORD Some 16
Enumerated
DWORD 32
LWORD 64

61131/PLCOpen Groupings/Type PLC 61850 N bits

inheritances in 61131
STRING 8
ANY_STRING
WSTRING 16
Table 10 Data type equivalence in logic functions
4.3.3.1. Available FBD functions

The following FBD functions are available at saTECH-CNF:
Binaries
Graphical Input types Output

Name Description
representation types
AND Boolean AND 2 Boolean Boolean
AND 8 Input Boolean AND 8 Boolean Boolean
OR Boolean OR 2 Boolean Boolean
Inputs OR 8 Boolean OR 8 Boolean Boolean
XOR Boolean exclusive OR 2 Boolean Boolean

Graphical Input types Output

Name Description
representation types
Exclusive OR with eight

8 Inputs XOR 8 Boolean Boolean
entries
NOT Negation 1 Boolean Boolean
Arithmetics
Graphical Input types Output types

Name Description
representation
2 Real Numbers or 2 Same as input

ADD Addition
Integers data

SUB Subtract
Integers data

MUL Multiplication
Integers data

IVD Division
Integers data
MOD Module 2 Integers Integer
Comparison

Name Description
representation
GT Greater than 2 of the same type Boolean


Name Description
representation
GE Greater or equal 2 of the same type Boolean
EQ Equal 2 of the same type Boolean
LE Less than or equal 2 of the same type Boolean
LT Less than 2 of the same type Boolean
NE Not Equal 2 of the same type Boolean
General
Input types Output types

Graphical
Name Description
representation
Same as the
ABS Absolute value 1 Number of any type
input type
SQRT Square root 1 Real number Real number
Logarithmic

Graphical
Name Description
representation
LN Nepalese logarithm 1 Real number Real number


Graphical
Name Description
representation
LOG Base-10 logarithm 1 Real number Real number
EXP Napierian exponential 1 Real number Real number
Trigonometrics

Graphical
Name Description
representation
SIN Sine in radians 1 Real number Real number
COS Cosine in radians 1 Real number Real number
TAN Tangent in radians 1 Real number Real number
ASIN Arcsine 1 Real number Real number
ACOS Arccosine 1 Real number Real number
ATAN Arctangent 1 Real number Real number

Bistable

Graphical
Name Description
representation
S1: Boolean
SR Bistable (set dominant) Q1: Boolean
R: Boolean
S: Boolean
RS Bistable (reset dominant) Q1:Boolean
R1: Boolean
Edges detection

Graphical
Name Description
representation
R_TRIG Rising edge CLK: Boolean Q: Boolean
F_TRIG Falling edge CLK: Boolean Q: Boolean
Timers

Graphical
Name Description
representation
IN: Boolean
TP Pulse timer PT: Integer Q: Boolean
(milliseconds)
IN: Boolean
TON Timer ON PT: Integer Q: Boolean
(milliseconds)


Graphical
Name Description
representation
IN: Boolean
TOF Timer OFF PT: Integer Q: Boolean
(milliseconds)
Converters
Input types Output

Graphical
Name Description types
representation
Real
DINT_TO_REAL Double integer to real long 1 Integer
number
Real
LINT_TO_LREAL Long integer to long real 1 Integer
number
1 Real
LREAL_TO_DINT Long real to double integer Integer
number
1 Real
LREAL_TO_LINT Long real to long integer Integer
number
BOOL_TO_DINT Boolean to double integer 1 Boolean Integer
When using the converters we must take into account that the PLC takes the INT32
signals as LREAL, that is, it treats all real numbers as LREAL
Conditionals (extension on the FBD language)

Graphical
Name Description
representation
CND: Boolean
IN_T: Real number, integer or
The value of IN_T if
boolean * OUT: Same
the condition is true,
IF_ELSE type as IN_T
and of IN_F if it is IN_F: Real number, integer or
and IN_F
false boolean *
* IN_T and IN_F must be of the same
type


Graphical
Name Description
representation
CND: Boolean
The value of IN if the OUT: Same
IF IN: Real number, integer or
condition is true type IN
boolean
4.4. Configuration options

Right-clicking on an IED in the IED panel will bring up a menu with different configuration
options, depending on the type of IED we have clicked on. In the Figure 4-39 different
configuration options of the saTECH BCU are shown, in the Figure 4-40 are the RIO units, in
the Figure 4-41 the SCU-HMI units, in the Figure 4-42 the SCU units, in the Figure 4-43 the
HMI units, and in the Figure 4-44 the non-saTECH range units.
As we can see in the Table 11 Configuration Options by SaTECH Equipment Model, the
Graphics and TFT Password Configuration options only appear in the BCUs with TFT, the
Historical Measurement Configuration option only appears in the HMI and SCU-HMI. Neither
slave nor master protocols can be configured on RIOs and no slave protocols can be
configured on HMIs.
saTECH saTECH saTECH saTECH saTECH

Configuration Option
SCU-HMI HMI SCU BCU RIO
Slave Profiles Yes No Yes Yes No
Master Profiles Yes Yes Yes Yes No
Subscription to Reports Yes Yes Yes No No
Gooses Subscription No No No Yes Yes
Publication of Reports Yes No Yes Yes Yes
Publication of Gooses Yes No Yes Yes Yes
Hardware Model Yes Yes Yes Yes Yes
Historical measurements record Yes Yes No No No
System disconnection Yes Yes No No No


Configuration Option
SCU-HMI HMI SCU BCU RIO
Yes
Single Line Drawing Yes Yes No Yes
(MES)
System Status Drawing Yes Yes No No No
'UCSs' and 'HMIs’ Communication section Yes No No No No
Signal Editor Yes Yes Yes Yes Yes
Logic Functions Yes Yes Yes Yes Yes
PLC load/status monitoring Yes Yes Yes Yes Yes
Advanced Properties Compatibilities Yes Yes Yes Yes Yes
CID validations Yes Yes Yes Yes Yes
Table 11 Configuration Options by SaTECH Equipment Model
As we can see, the options for Other Manufacturer are much more limited: subscription to their
Gooses and Reports, configuration of signals and points to the Control Center, options to
update and validate the 61850 configuration settings through the CID file,

In any case, as we will see below, the options in the sub-menus are not the same for each type
of IED either.
Figure 4-39 BCU Configuration Options Figure 4-40 RIO Configuration Options
Figure 4-42 SCU configuration Options

Figure 4-41 SCU-HMI Configuration Options
Figure 4-44 Other Manufacturer

Configuration Options
Figure 4-43 HMI Configuration Options

4.4.1. Generating CID

Allows for generating the *.cid file of the equipment and/or validate it against the IEC-61850
standard.
4.4.1.1. Generating Configurations

It performs the same action as the Generating Configurations option from the File sub-
menu in the main menu. It generates all CID files with all of the points to all
"Destination to Higher Levels". The points of the CID-SCU file which have been
configured in any IED will only be added, deleted or modified via this option.
4.4.1.2. Generating CID

It offers the option to generate the CID file of the current IED with all its configuration,
but only with the "Behavior Configuration" and "Data Acquisition Mode" parts of of its
Signal File (4.4.11); it does not process the points that use the SCU as proxy (see
protocol configuration in "Destination to Higher Levels.") It does not modify the CID-
SCU file. This option is not available in SCUs or HMIs, is is used to validate the
configuration of a single unit.
4.4.1.3. Validating CID

Validates only the CID file of the selected IED. See "Validate CIDs” section for more
information.
4.4.2. Send Configuration

From the options in this menu, a configuration can be loaded onto a device or the PLC
status can be monitored.
4.4.2.1. Load Configuration

This option allows us to load the configuration onto the equipment.
During this process, the CID and the project will be sent to the equipment, generating
these CIDs and exporting the project, if they are not already in the project folder. If we
suspect that these files already exist in the project, but are out of date, we will have to

regenerate settings and export the project to ensure that the data we send is up to
date.
In order to perform these actions we will be asked to enter the IP of the equipment and
its user and password (it will offer some default values.)
We will also be given the option to monitor the equipment after finishing the
configuration load: this option will be display information about the load process and
we will be able to see what errors have occurred during that process, if any.
In case the name of the equipment is not the same it previously was, it will show us a
confirmation message before changing it.
4.4.2.2. PLC Monitoring

It displays a screen with information about the loading of logic functions onto the PLC,
which will allow us to know if any error has occurred when loading the logic functions.
In order to perform this action we will be asked to enter the IP of the equipment and its
user and password (it will offer some default values.)
4.4.3. 1850 Network configuration

Allows to configure the equipment's network parameters (see Figure 4-45):
 IP address
 Network mask
 Gateway
 Physical port
Figure 4-45 Network configuration

4.4.4. Time Configuration

It allows to configure the time treatment applied to the saTECH equipment, as shown in
the Figure 4-46:
Figure 4-46 Time Configuration
 UTC/Local time: Defines the internal logic functions of events in local/UTC time
If local time is selected, the user must enter the Local Time Zone (recommended
option) or select "--" from the drop-down list to indicate that they prefers to manually set
the following parameters:
 Displacement of local time over UTC time (positive or negative).
 Activate/Deactivate the automatic summer time update.
 If automatic summer time updating is enabled, the following parameters must be

entered:
 Daylight saving time shift (positive or negative).
 Changeover dates for summer/winter time changes.
4.4.5. Synchronization settings

Allows to configure the synchronization sources of the saTECH equipment (see Figure
4-47). More than one source can be defined, sorted by priority, so that when the
computer cannot synchronize by the highest priority source, after specified period of time,
it will try the next source in the established order of priority.

Recovering a higher priority source will cause the computer to switch to that source
immediately.
Figure 4-47 Synchronization source configuration
The user can determine up to 4 synchronization sources, in case of BCU equipment, 1 for
RIO equipment and up to 7 in case of HMI or UCS IED.
In order to do this, the synchronization type for the source to be registered must be
selected; among the possible ones:
 NTP
 IRIG-B: For HMI, this option is not available
 Slave protocol: It only applies when the IED has a communications master by
protocol which is not IEC-61850, as this protocol does not allow for
synchronization
 PTP-IEEE1588
Once the synchronization mode of the source being configured has been selected, the
requested parameters will be entered, which depend on the synchronization mode.
NTP
 Priority: Number indicating the priority of the source being configured, taking into
account that '1' is the highest priority.

 Switching time in case of failure(s): The time that must elapse from moment of
synchronism source failure, before moving to a lower priority source. When a
higher priority source has recovered from a failure, the return to that
synchronization source is immediate.
 Network configuration of the synchronization source: IP, Subnet, Gateway,

connection type and connector.
 Equipment network configuration to communicate with the synchronization source:

IP, Subnet, Gateway, connection type and connector. We should bear in mind that
IED may have more than one network interface, so it is necessary to specify which
one is used for each functionality.
If the computer is a dual UCS or a UCS with HMI or an HMI with multiple instances, we
will have to configure a network interface for each of them, as can be seen in the Figure
4-48 Dual UCS with HMI sync-source configuration .
Figure 4-48 Dual UCS with HMI sync-source configuration

IRIGB:
account that '1' is the highest priority
higher priority source has recovered from failure, the return to that timing source is
immediate
SLAVE PROTOCOL
immediate
 Name of the master device of the non-61850 slave protocol communication profile
(previously configured in the IED.)
PTP - IEEE1588
immediate
 Frame types for synchronization (ETHERNET/UDP): Frame types for

synchronization via PTP
 IP transmission mode: The standard determines it must be MULTICAST
 Delay detection mode: Delay detection mode: The standard determines that it has
to be P2P, but we will allow E2E configuration

 PTP domain number: PTP domain number: Determine the domain in order to
avoid conflicts with other PTPs (the standard recommends using 93 in case of
conflict with 0)
 VLAN configuration: If enabled, the identifier (identifier 0 indicates no association)

and the VLAN priority, which can be set between 0 and 7, will be configured.
 Configuration of the physical port number of the equipment (PortLocal), type of

redundancy (No/Bonding/PRP) and in case of redundancy, redundant physical
port. We should bear in mind that IED may have more than one network interface,
so it is necessary to specify which one is used for each functionality.
If the equipment is a dual UCS or a UCS with HMI or an HMI with multiple instances, we
must configure its physical port and redundancy for each of them.
4.4.6. Historical Measurements Configuration

This option is only available for the units with HMI functions (SCU-HMI and HMI units),
and leads to the same screen as the option in theHistorical Menu, in the main menu.
4.4.7. Slave Protocol Configuration

One of the distinctive features of saTECH BCU versus saTECH RIO is its capability to be
a "Slave" to any IED in the following protocols:
 DNP 3.0 TCP/IP and serial
 IEC 60870-5-104
 IEC 60870-5-101 (check availability)
In Figure 4-49 this selection is shown:

Figure 4-49 Creation of a slave protocol
Depending on the selected slave protocol, it will be necessary to select the profile
parameters:
 DNP 3.0 TCP/IP
Connection:
o Physical port: 1…50

o IP address
o Subnet mask:
o Gateway
o Connection port: 20.000
o Connection: TCP/UDP
o Type of Redundancy: No; secondary backup IP channel; secondary

backup SERIAL channel; single channel with double physical interface.
If one of the backup channels is chosen, the corresponding fields of the
physical connection and port configuration of that secondary channel
will appear for us to configure as well. If we select the single channel
with double physical interface, the field Redundant physical port will
appear so that we can also configure it.
Master Equipment:
o Master equipment name

o IP 1 of the Master equipment:

o Master equipment subnet mask 1

o Master equipment gateway 1
o IP 2 of the Master equipment:
o Master equipment subnet mask 2
o Master equipment gateway 2
o Permission filter
Basic parameters:
o Slave address: 1..65519

o Master address: 1..65519
o Local time processing

o Monitoring Model: Selection and execution, Direct execution, Command
conversion
o Command selection timeout (ms)
Advanced parameters:
o Digital Values Sending Class: No Class, Class 1; Class 2; Class 3

o Analog Values Sending Class: No Class, Class 1; Class 2; Class 3
o Counters Sending Class: No Class, Class 1; Class 2; Class 3
o Default value Obj01:
 Var1: Binary Input Packet Format
 Var2: Binary Input with Flags
 Var1: Binary input without time
 Var2: Binary input with absolute time
 Var3: Binary input with relative time

 Var2: Binary Output status
 Var1: 32-bit counter with flags
 Var5: 32-bit counter without flags

 Var1: 32-bit frozen counter with flags
 Var9: 32-bits frozen counter without flags

 Var1: 32-bit event counter with flags
 Var1: 32-bit Frozen Event Counter with flags

 Var1: 32-bit analog input with flags
 Var3: 32-bit analog input without flags

 Var1: 32-bit Analog Input Event without time
 Var3: 32-bit Analog Input event with time
 Var1: 16-bit Deadband Analog Input

 Var1: Analog Output Status 32 bits with flags
 Var2: 16-bit Analog output Status with flags

o List of objects that are included as static data:
 Object 1: Binary Input
 Object 10: Binary Output Status

 Object 20: Counter
 Object 21: Frozen Counter
 Object 30: Analog input
 Object 40: Analog Output Status
 Timeout to first character: 100
 Waiting time between characters: 50
 Time between the last received byte and the first transmitted byte
(ms): 0
 Maximum number of simultaneous Ethernet connections allowed 1
 TCP connection waiting time (ms): 3000

o Maximum application fragment size: 2048
o Maximum frame size at link layer: 292
o Full frame Reception waiting time (ms): 15000
o Waiting time for confirmation at link layer (ms): 3000
o Link level confirmations: Never; Multi-frame fragment; Always
o Link layer retries: 3
o Frequency status requests not master frames (ms): 0
o Master address validation
o Multiple fragment frames allowed
o Multi-Fragment Response Application Level Confirmation
o Master confirmation waiting time for a REQUESTED response (ms):
10000
o Digital event queue: 5000
o Digital Event Queue Management
o Analogical event queue: 1000
o Analogical event queue management
o Counter event queue: 1000
o Counter event queue management
o Frozen counter event queue: 1000
o Frozen counter event queue management

o Maximum time for indication of communications failure with the master

(ms): 15000
o “Analog Limits" version: ICD Template Version, Modify ICD Templates
for FLOAT64 Type
o Points: It shows the signals that have been configured in the signal
editor to be acquired by this protocol. See Figure 4-51.
 DNP 3.0 Series
Physical connection
o Connector type: RS-232/RS-485

o Type of Redundancy: No; secondary backup IP channel; secondary
backup SERIAL channel. If one of the backup channels is chosen, the
corresponding fields of the physical connection and port configuration of
that secondary channel will appear for us to configure as well.
Port Configuration
o Speed:
o Parity:
o Data bits:
o Stop Bits
o Hardware flow control
Master equipment

o Type of communication: RS-232/RS485
o Port number: 1
Basic Parameters
o Slave address
o Master address
conversion
o Command selection waiting time (ms)

Advanced Parameters
o Digital Values Sending Class: No Class, Class 1; Class 2; Class 3

o Analog Values Sending Class: No Class, Class 1; Class 2; Class 3
o Counters Sending Class: No Class, Class 1; Class 2; Class 3
 Var1: Binary Input Packet Format
 Var2: Binary Input with Flags

 Var1: Binary input without time
 Var2: Binary input with absolute time
 Var3: Binary input with relative time

 Var2: Binary Output status








o List of objects that are included as static data:
 Object 1: Binary Input
 Object 10: Binary Output Status
 Object 20: Counter
 Object 21: Frozen Counter
 Object 30: Analog input
 Object 40: Analog Output Status

o Waiting time to the first character (ms): 100
o Waiting time between characters (ms): 50
o Time between the last received byte and the first transmitted byte (ms):
0
o Maximum number of simultaneous Ethernet connections allowed 1
o TCP connection waiting time (ms): 3000
o Maximum application fragment size (reception): 2048
o Maximum frame size at link layer (reception): 292
o Full frame reception waiting time (ms): 15000

o Waiting time for confirmation at link layer(ms): 3000

o Link level confirmations: Never; Multi-frame fragment; Always
o Link level retries: 3
o Frequency status requests not master frames (ms): 0
o Master address validation
o Multiple fragment frames allowed
o Multi-Fragment Response Application Level Confirmation
o Master confirmation time for a REQUESTED response (ms): 10000
o Digital event queue: 5000
o Digital event queue management

o Analogical event queue: 1000
o Analog event queue management
o Counter event queue: 1000
o Counter event queue management
o Frozen counter event queue: 1000
o Frozen counter event queue management
o Maximum time for indication of master communication failure (ms):
15000
o "Analog Limits" version: ICD Template Version, Modify ICD Templates

for FLOAT64 Type
editor to be acquired by this protocol. See Figure 4-51.
 IEC-60870-5-101
Physical connection
o Communication type: RS-232/RS485

o Type of redundancy: No; secondary SERIAL back-up channel. If the
SERIAL backup channel is chosen, the corresponding fields of the
physical connection and port configuration of that secondary channel
will appear for us to configure as well.
Port Configuration

o Speed
o Parity
o RTS activation waiting time
o Data bits
o Stop Bits
o Hardware Flow Control
Master Equipment

o Type of communication: RS-232/RS485
Basic Parameters
o Link address:1
o ASDU Common Address:1
o Waiting time communication control center (s):30
o Local time processing:
conversion
o Command selection timeout (s):30
Advanced Parameters
o Waiting time to the first character (ms): 100

o Waiting time between characters (ms): 50
o Link address size: 2
o ASDU common address size: 2
o IOA size: 2
o Transmission cause size: 1
o Periodic and spontaneous change: 0
o Reliable signal changes sending time. (ms). 1440
o Scanning period Analog measurements: 2
o Counters freezing period startup time (ms): 1

o Counter freezing period (ms): 60
o Class 2 queue deletion Reset Link: 1
o ActTerm in digital commands

o ActTerm on analog commands

o Order buffer length: 3
o Command buffer length: 10
o Class 1 data Buffer length: 1000
o Class 2 ACK buffer length: 30
o Class 2 Data Buffer length: 1000
o Class 2 file buffer length: 1
Points: It shows the signals that have been configured in the signal editor
to be acquired by this protocol. See Figure 4-51
 IEC-60870-5-104
Connection
o IP address
o Subnet mask
o Gateway
o Connection port:2404
o Type of Redundancy: No; secondary IP backup channel; single channel

with double physical interface. If the SERIAL backup channel is chosen,
the corresponding fields of the physical connection and port
configuration of that secondary channel will appear for us to configure
as well. If we select the single channel with double physical interface,
the field Redundant physical port will appear so that we can also
configure it
Port Configuration
o Waiting time for connection to be established: 30
o Waiting time for a test frame or APDU(I): 15

o Acknowledgment with no messages waiting time: 10
o Waiting time for sending S-type packages (test): 20
o APDUS received without confirmation max. no.: 12
o APDUS sent without confirmation max. no.: 8
Master Equipment


o IP of the Master Equipment
o IP of the Master equipment 2
o Master equipment subnet mask

o Master equipment gateway
Basic Parameters
o ASDU Common address

conversion
o Command selection timeout: 30
Advanced Parameters
o Periodic and spontaneous change: 0

o Reliable signal changes sending time. (ms): 0
o Scanning period for analog measurements
o Counters freezing period startup time (ms):
o Freezing period counters (ms)
o Class 2 Queue Deletion Reset Link:
o ActTerm on digital commands:
o ActTerm on analog commands:
o Order buffer length:
o Command buffer length:

o Data Class 1 Buffer length
o Class 2 ACK buffer length:
o Class 2 Data Buffer length

o Class 2 File Transfer Buffer Length

editor to be acquired by this protocol. Figure 4-51
From the points screen, the user can select a point and right-click on it, and a menu will
appear with the Edit point option, which leads to the corresponding row of the IED Signal
Editor.
Figure 4-50 Slave Protocol Settings - Points Tab - Edit Point
4.4.8. Master Protocol Configuration

One of the distinctive features of saTECH BCU versus saTECH RIO is its capability to be
a "Master" of any IED in the following protocols:
 DNP 3.0 TCP/IP and serial
 Modbus TCP/IP and Serial
 SAP20
This capability is very important when we have IEDs that do not include IEC 61850
protocols, but need to be integrated into IEC 61850 Substation Automation Systems.

This is why we have configured a Master Profile in the saTECH BCU; the signals of these
IEDs are acquired, and once this information is in the saTECH BCU, it can be sent to the
higher level via Goose/MMS or it can be locally processed.
The window for creating the master protocol is shown in Figure 4-51.
Figure 4-51 Creation of master protocol
Depending on the selected master protocol, it will be necessary to select the profile
parameters:
 DNP 3.0 TCP/IP
Physical connection
o DNP address: 1..1000

o Physical Port: 1 (Ethernet port through which communications go. In the
current versions it is not used, but in later versions it will specify the port
through which the communications profile will go and on which the
networks will be defined according to the configured IPs.)
o Type of redundancy: No, simple channel with double physical interface.
If we select the single channel with double physical interface, the field
Redundant physical port will appear so that we can also configure it
Connection
o IP address
o Subnet mask:
o Gateway

o Connection: TCP/UDP
Advanced Parameters
o Data link timeout (ms)
o Confirm data timeout (ms)
o Re-tries after error
o Data link retries
o Link reset sending T. (ms)
o Timeout to first character (ms)
o Timeout between characters (ms)

o Minimum connection time (ms)
Equipment: It shows a panel with the current configuration of the configured
slave equipment. To register a new slave equipment in the master profile, the
user must select from the drop-down list one of the DNP3-IP slave equipment
models registered in the CNF (see 2.5.6), enter the model configuration
parameters and press the button.
Add. From this panel it is also possible to modify the configuration of the
existing models, by pressing the
Edit button. We can register new equipment models from the tools sub-menu
option Configure Equipment Models in the main menu. The parameters to be
configured for each slave equipment will be:
o Equipment Name
o Slave Address
o IP address
o Physical Port
o Sync sending time (ms)
o Class 0 request T. (ms)

o Command execution waiting time (ms)
o Full reception waiting time (ms)

o IIN Bitmask
o Digital inputs
o Digital outputs
o 'i' Analog inputs
o 'i' Analog outputs
o 'f' Analog inputs
o Active pulse counter
Points: It shows the signals that have been configured in the signal editor to
be published by this protocol. See Figure 4-52.
 DNP 3.0 Serial
Physical connection
o DNP address: 1..1000
o Type of communication: RS-232/RS-485. Currently, the systems only
support RS-232 selection. In order to communicate via RS-485, RS232
must be configured in this section and then RS485 must be configured
via other mechanisms (jumpers and/or internal system configuration)
o Physical Port: 1. Ethernet port through which communications go: 1

(COM1), 2 (COM2), 3 (COM3), etc.
Port Configuration
o Speed
o Parity
o Data bits
o Stop Bits
o Hardware flow control
Advanced Parameters
o Data link timeout (ms)

o Confirm data timeout (ms)
o Re-tries after error
o Data link retries
o Link Reset Sending Time (ms)


o Minimum connection time (ms)
user must select from the drop-down list one of the DNP3-SERIE slave
equipment models registered in the CNF (see 2.5.6), enter the model
configuration parameters and press the button.
Add. From this panel it is also possible to modify the configuration of existing
models, by pressing the Edit button. We can register new equipment models
from the tools sub-menu option Configure Equipment Models in the main
menu. We can register new equipment models from the tools sub-menu
o Equipment Name
o Slave Address
o Type of connection: RS-232/RS-485
o Physical Port
o Sync sending time (ms)

o Speed
o Command execution waiting time (ms)
o IIN Bitmask
o Digital inputs
o Digital outputs
o 'i' Analog inputs
o 'f' Analog inputs


 TCP/IP Modbus
Physical connection
o Physical Port: 1 (Ethernet port through which communications go. In the
current versions it is not used, but in later versions it will specify the port
through which the communications profile will go and on which the
networks will be defined according to the configured IPs)
o Type of redundancy: No, simple channel with double physical interface. If
we select the single channel with double physical interface, the field
Redundant physical port will appear so that we can also configure it
Connection
o IP address
o Subnet mask:
o Gateway

Advanced Parameters
o Data link retries
user must select one of the MODBUS-IP slave equipment models registered
in the CNF (2.5.6) from the drop-down list, enter the model configuration
parameters and press the Add button. From this panel it is also possible to
modify the configuration of existing models, by pressing the Edit button. We
can register new equipment models from the tools sub-menu option Configure
Equipment Models in the main menu. The parameters to be configured for
each slave equipment will be:
o Equipment Name

o Slave Address
o IP address
o Physical Port
o Waiting time between requests (ms)
o Invert Bytes in the Frame
o Digital inputs
o 'i' Analog inputs
o 'f' Analog inputs

o Digital outputs
o 'f' Analog outputs
 Modbus Serial
Physical connection
o Type of communication: RS-232/RS-485
o Physical Port: 1
Port Configuration:
o Speed:
o Parity: No/ Odd/Even
o Data bits: 8
o Stop bits: 1
o Hardware Flow Control

Advanced Parameters

o Data link retries


user must select one of the MODBUS-SERIE slave equipment models
registered in the CNF (see2.5.6) from the drop-down list, enter the model
configuration parameters and press the Add button. From this panel it is also
possible to modify the configuration of existing models, by pressing the Edit
button. We can register new equipment models from the tools sub-menu
o Equipment Name
o Slave Address
o Physical Port
o Speed
o Invert Bytes in the Frame
o Digital inputs
o 'i' Analog inputs
o 'f' Analog inputs
o Digital outputs
o 'f' Analog outputs
 SAP20
Physical connection
o Type of communication: RS-232/RS-485

o Physical Port: 1

o Type of redundancy: No, communication ring. If the communication ring is

selected, the field Redundant Physical Port will appear so that we can also
configure it
Port Configuration:
o Speed:
o Parity: No/ Odd/Even
o Data bits: 8
o Stop bits: 1

user must select from the drop-down list one of the SAP20_TCD slave
equipment models registered in the CNF (see 2.5.6), enter the model
configuration parameters and press the Add button. From this panel it is also
possible to modify the configuration of existing models, by pressing the Edit
button. We can register new equipment models from the tools sub-menu
o Operation mode: Mode 8, Mode 9, Mode 11
o Equipment Name
o RTU address
o Digital inputs
o Digital outputs
o 'i' Analog inputs
o Tap changer
o Speed
o Connector
o Cable
o Physical port

Points: It shows the signals that have been configured in the signal editor to be
published by this protocol. See Figure 4-52
From the points screen, the user can select a point and right-click on it, and a menu will
appear with the Edit point option, which leads to the corresponding row of the IED
Signal Editor.
Figure 4-52 Master Protocol Setup - Points Tab - Edit Point
4.4.9. 61850 Communication

This is one of the sub-menus that appear when right-clicking on an IED that is not from
another manufacturer, in the IED panel. In the Figure 4-53 61850 BCU Communication
the different configuration options of the saTECH BCU units are displayed, in the Figure
4-54 are the RIO units, in the Figure 4-55 the SCU-HMI units, in the Figure 4-56 the SCU
units, and in the Figure 4-57 the HMI units.

Figure 4-54 61850 RIO Communication

Figure 4-53 61850 BCU Communication
Figure 4-55 61850 SCU-HMI Communication Figure 4-56 61850 SCU Communication
Figure 4-57 61850 HMI Communication
As we can see in the images, the position equipments subscribe to Gooses, while the
substation equipments subscribe to Reports. Conversely, HMIs do not publish signals,
they only subscribe to them.
4.4.9.1. Gooses Subscription

The user can configure the subscription to gooses of any IED which has been previously
registered in the project. A subscription to Gooses is required to view the signals from the
publisher IED in the subscribed IED signal tree.
To define the subscription to gooses we must right click on the IED name, and select the
option Subscription to gooses in the 61850 communication sub-menu.

The following screen will appear:
Figure 4-58 Selection of gooses publisher IED
The user will select the IED for which they wish to create the subscription, then press the
Next button:
Figure 4-59 GSE Control Selection
This window shows the GSE Control published by the selected IED. The user will select
one of them and press the Finish button.
In the IED Details panel, we can see that there is a section called Subscription, where
the GSE Control to which the subscription was made is displayed:

Figure 4-60 Gooses subscription zone
When double-clicking on the GSE Control, its information will be displayed:
Figure 4-61 Gooses subscription information
4.4.9.2. Subscription to Reports of other IED

The user will be able to configure the subscription to reports control block of any IED
which has been previously registered in the project. This option is visible for substation
IEDs, SCU/HMI. A subscription to Reports is required in order to view the signals from the
publishing IED in the signal tree of the subscribed IED.

In order to determine the subscription to reports control block, we must right-click on the
name of the IED, and select the option Subscription to ReportControl, from the 61850
communication submenu
The following screen will appear:
Figure 4-62 Selection of publisher reports IED
The user will select the IED to which they want to subscribe, then press the Next button:
Figure 4-63 Report Control Block Selection
This window displays the Report Control Block published by the selected IED. The user
will select one of them and press the Finish button.
In the IED Details panel, we can see that there is a section called Subscription, where
the Report Control to which the subscription was made is displayed:

Figure 4-64 Report subscription section
By double-clicking on the subscribed Report Control, its information will be displayed:
Figure 4-65 Report subscription information
4.4.9.3. Subscription to all ReportControls

With this option, which is available in the substation IEDs (SCU and HMI), we will
automatically subscribe to all ReportControls published by any IED in the project.
4.4.9.1. Publish GSEControl

From the option publish GSEControl from the 61850 communication sub-menu

From the option publish ReportControl from the communication sub-menu 61850
we will arrive at the same wizard seen in the 4.2.2 Report Control Block item
4.4.9.2. Edit a DataSet

We can modify a DataSet, that is, add or remove attributes. To do so, we must right-click
on the name of the IED, and select the option Edit DataSet from the 61850
communication sub-menu, as shown in the Figure 4-66:
Figure 4-66 Edit DataSet
Afterwards, the following window will be displayed so as to select the DataSet to be

modified:
Figure 4-67 DataSet Selection

We go back to the Dataset editing screen:
Figure 4-68 Dataset Editing
And afterwards, the Dataset signals editing
Figure 4-69 Dataset signal editing
4.4.10. Signals configuration

Once the master profiles corresponding to the application's master and slave protocols are
set, the user may determine how the signal is transmitted to the lower and upper levels via
a spreadsheet. In addition, in special cases, configuration parameters which are signal-
specific could be configured.

See Signal File Format
4.4.10.1. IED Signal Editor

With the same Signal File Format of the project, it is possible to configure with an interface
specific to the saTECH CNF application. The new interface makes it easier to configure for
a particular IED because its current configuration in the project is known.
To access the CSV Editor, select the IED Signal Editor option in the Signal Setup sub-
menu of the selected IED context menu.
Figure4-70 IED Signal Editor
In the central panel a new tab will appear where we can visualize and edit the CSV data of
the selected IED.
Figure 4-71 CSV display panel

4.4.10.1.1. Filters
All columns can be filtered for faster information searches, from the header of each
column. The list displayed for each header will contain all the values which exist in the
table at the time of filtering.
Figure 4-72 Filter by columns
Figure 4-73 Signal filtering from the heading
4.4.10.1.2. Row Options

When clicking on a row with the right mouse button, a context menu with various options
will appear. Depending on which cell is selected when it is right-clicked, more or less
options will appear in this menu as shown below Figure 4-74.

Figure 4-74 Row Context Menu
4.4.10.1.3. Insert Row Above/Below

A blank row just below the selected row will be created when pressing "Insert Row Below."
A blank row just below the selected row will be created when pressing "Insert Row Above."
Figure 4-75 Insert Row
4.4.10.1.4. Delete Row

The row that is selected will be deleted when clicking on the "Delete" option.
4.4.10.1.5. Copy Row

The "Copy Row" option will copy from 1 to several of the entire rows selected when clicking
on the "Row No." column, in the case of a single row, or when dragging the mouse in the
case of several rows. We should not confuse copying rows with copying cells, which will
happen if, instead of selecting from the "Row No." column, we select from a different
column.
What rows are selected can be clearly seen if their background color is set to green. The
rows must be consecutive
Figure 4-76 Selection of rows to be copied
4.4.10.1.6. Paste Row

The "Paste row" option will overwrite the selected row to the end of the copied rows with
the clipboard information, that is to say, if there are 3 rows in the clipboard and we select
one it will overwrite the selected row and the next two rows as well.
The information in the clipboard can come from either the previous "Copy Row" option and
from the usual key combination "CTRL + c", just as we can Paste from the clipboard with
'CTRL + v'.
4.4.10.1.7. Disable Row

Disable row will change the row color to a light orange to promptly indicate that the row is
disabled in the original CSV, by means of the usual characters for it, "#" or "--".

If a disabled row is copied, it will be disabled where we copy it as well.
Figure 4-77 Disabled Row
4.4.10.1.8. Enable Row

This option will remove the color signature from the previously disabled row and the
corresponding character in the original CSV.
4.4.10.1.9. Autocomplete
Starting from the number copied from a selected cell by means of the "CTRL + c" keys, the
desired set of cells must be selected and, with them still selected, this option must be
clicked, which will autocomplete with the copied number; if there is text in it, it looks for the
first whole number from right to left. Useful for autocomplete references where it changes
to the DO name index, as shown below Figure 4-78.
Figure 4-78 Autocomplete
4.4.10.1.10. Delete cell contents

It will delete the contents of the selected cells as shown below Figure 4-79:

Figure 4-79 Delete cell content
4.4.10.1.11. Undo
Undoes the previous copy operation, given there is one. This option can also be performed
with the usual key combination "CTRL + z" and "CTRL + y" for redo.
4.4.10.1.12. Column-Specific Context Menu

Column Signal Name
A new option will be displayed in the "Show signal tree" menu, and will pop a new window
up with the existing signals of the logic device selected in the previous column, logic
device.

If nothing is selected in the logic device column, the signal tree will be empty until
something from the drop-down list is selected.
Figure 4-80 Show signal tree

Acronym Column
In this column, a new option will be displayed which will show the acronym editing screen.
Figure 4-81 Show acronym panel
Figure 4-82 Acronyms panel

As explained in the section 4.4.11.1.2 Behavior Configuration, the acronyms specify the
behavior of the signals in the system display windows.
As we can see in the Figure 4-82, the acronym configuration screen has the following
parts:
- Type Acronym Selector: It allows us to load a set of preset acronyms or clear all
fields in the current configuration. Behaviors for signals with the same CDC (common
data class) are usually very similar, so saTECH-CNF suggests the following options:
o (???) Clear: This option is intended for signals from any CDC and eliminates all
signal settings, so we can start setting it up from scratch.
o (SPS) Single Point Status - A: This option is intended for CDC SPS (Single point
status) signals, in the case where the value for the normal status is 0 and an alarm
must be enabled for the value 1. Therefore, it will generate the configuration
"A0:NORMAL;A1:ALARM;AL1;EV0;EV1"
o (SPS) Single Point Status - B: This option is intended for CDC SPS (Single point
status) signals, in the case where the value for the normal status is 1 and an alarm
must be enabled for the value 0. It will therefore generate the configuration
"A0:ALARM;A1:NORMAL;AL0;EV0;EV1"
o (DPC) Double Point Command: This option is intended for CDC DPC (Double
point status) signals and will generate the configuration:
"A0:UNKNOWN;A1:OPEN;A2:CLOSED;A3:INCONGRUENT;OO:OPEN;OC:CLO
SE;EV0;EV1;EV2;EV3;EVFA;ALPHA;AL1;AL2"
o (SPC) Single Point Command: This option is intended for CDC SPC (Controllable
Single Point) signals and will generate the configuration:
"A0:NORMAL;A1:ALARM;OO:OPEN;OC:CLOSE;EV0;EV1;EVOK;EVFA;ALPHA"
o (DPS) Double Point Status: This option is intended for CDC DPS (Double point
status) signals and will generate the configuration:
"A0:UNKNOWN;A1:OPEN;A2:CLOSED;A3:INCONGRUENT;A1:ALARM;EV0;EV1
;EV2;EV3;EVFA;AL1;AL2"

o (ACT) Protection Activation Information: This option is intended for CDC ACT
(Protection activation information) signals and will generate the configuration:
"A0:NORMAL;A1:ALARM;AL1;EV0;EV1"
o (BSC) Binary Step Command: This option is intended for CDC BSC (Binary
controlled step position information) signals with the option to go up and down,
and will generate the configuration:
"A0:REST;A1:UP;OC:DOWN;OO:UP;ALPHA;ALOK;EVFA;EVOK"
o (BSC) Single Step Binary Command - Up: This option is intended for CDC BSC
(Binary controlled step position information) signals only with the option to go up,
and will generate the configuration:
"A0:REST;A1:UP;OC:UP;ALPHA;ALOK;EVFA;EVOK"
o (BSC) Single Step Binary Command - Go down: This option is intended for CDC
BSC (Binary controlled step position information) signals only with the option to go
down and will generate the configuration:
"A0:REST;A1:UP;OC:DOWN;ALPHA;ALOK;EVFA;EVOK"
- Names. This section allows for the configuration of:
o An element identifying name: It is normally used in signals related to equipment

communication and represents the name of the equipment. It accepts
alphanumeric values of up to 32 characters and is generated as the acronym E.
This field is only mandatory if the box to the left of it is enabled.
o An element description: This is the description of the text identifying the signal on
the IHMI screens. It supports alphanumeric values of up to 100 characters and
can include the expression ${element} to reference the signal name field in the
signal editor. The item description is generated as the acronym D and is the only
mandatory field in the acronym configuration panel.
o Signal State Names: Set the names for each state that can the signal can adopt.
Each status text can be alphanumeric and up to 64 characters. These are the
names that will appear in the "Status" field of the "alarm screen" and "event
screen" table. If so configured, this signal value will also appear represented on
the "panel screen." They are added using this section’s "more" button and
removed using the "delete" button to the left of each one. These names are

generated as the acronym AX: where X is the value for which we are setting the
name.
- Command texts: This section only makes sense for controllable signals (Common
data Class SPC and DPC). This is where the texts for the opening and closing
commands are configured. Both are alphanumeric and are generated as the
acronyms OO and OC, respectively.
- Texts for Blocking: This section only makes sense for CILO node signals. Makes it
possible to configure the opening or closing blocking texts, or both. These texts are
alphanumeric and are generated as the acronyms BO, BC and BG, respectively.
- Alarms: From this section we can configure:
o The activation/deactivation of the Horn associated with the alarm. It is enabled by

default, and if we disable it, the acronym NBC will be generated.
o Send Alarms with Value: Defines by which value an alarm should be triggered and
to what color a signal should change when that alarm is triggered. They are added
using this section’s "more" button and removed using the "delete" button to
the left of each one. It generates two acronyms, one ALx and, in case of setting a
color in the drop-down list, another Cox one: y where x is the value of the alarm
and y is a letter that represents the color for that alarm. The admissible values for
y are: R -> Red color, G -> Green color, B -> Blue color, O -> Orange color, Y ->
Yellow color, P -> Purple color and W -> White color. If no color is defined, the
default color is Red for the values configured as alarm (ALx)
- Events: It allows for the configuration the following settings:
o Creating events when the source is "CURRENT COMMAND". It only makes sense
for controllable elements’ signals (Common Data Class SPC and DPC).
Generating the EVOR acronym
o Creating events when the source is "COMMAND OK". It only makes sense for
controllable elements’ signals (Common Data Class SPC and DPC). Generating
the EVOK acronym

o Creating events when the source is "COMMAND FAULT." It only makes sense for
controllable elements’ signals (Common Data Class SPC and DPC). Generating
the EVFA acronym
o Setting values for which new events will occur on the "event screen." They are
added using this section’s "more" button and removed using the "delete" button
to the left of each one. They generate EVx acronyms where x is the value for
which the new event will occur.
Acquisition Column
These columns will have two more options in the contextual menu that will serve to enable
and disable the acquisition associated cells. A hash (#) will be displayed in front of the
commented cell text.
Figure 4-83 Disable acquisition

The acquisition columns will also have three more options in the context menu. One of
them will show a menu to configure the range of the analog signals, another one will show
a menu to configure the pulse and the last one will show a menu to configure the automatic
override.
Figure 4-84 Context menu Properties column

Figure 4-85 Analog Range Configuration Figure 4-86 Pulse Configuration
Figure 4-87 Automatic Override Configuration
These settings will be displayed in the properties column and can be viewed or edited at
any time by reopening the corresponding menu (See Figure 4-84 Context menu Properties
column.)

Publication Columns
These columns will have two more options in the context menu that will serve to activate
and deactivate the cells associated with the publication. A hash (#) will be displayed in
front of the commented cell text.
Figure 4-88 Disable publication address
Cell Edition
The cells’ contents can be directly modified by selecting the cell and typing in the desired
text.
For the user's convenience, there are cells that offer a drop-down list with all possible
elements.
To display the list, double-click on the selected cell.
Figure 4-89 Editing Cells

4.4.10.1.13. Drag and drop

In the signal editor, several functions are available through drag and drop. The most
important ones are:
Changing the rows’ order

By selecting one or more rows, we can drag them to a different position, for example,
several rows down, as is seen in the following figure, in which we are moving the signals
from positions 36 to 40, so that they are between the one currently in position 44 and the
one in position 45:
Figure 4-90 Dragging signals
Creating new entries in the logic functions variable table.

By selecting one or more rows we can drag them to the logic variables table and thus new
entries will be created whose references will be those of the dragged signals. See section
4.3.2.2.2 Adding variables by dragging and dropping
Assigning references to the single line editor.

By selecting a row we can drag it over the text box of a signal reference of an element in
the Single Line Editor, and thus the reference will be configured with that of the dragged
signal.
For example, in the following figure, for a BCU, in addition to the signal editor, we have
opened the BCU Single Line Editor (see 4.4.13.2 Edit Single-Line BCU) and are
configuring the switch status signal by dragging the corresponding signal from the signal
editor.

Figure 4-91 Drag to Single Line Editor
4.4.10.1.14. Editing the standardized signal file

The standardized signal file will appear when we click on the "StandardizedFile"
icon in the menu bar and will disappear when we click on it again.
Figure 4-92 Standardized signal file
The rows with the blue background will indicate that they contain a special signal,
capable of creating an LN.
This table will have only a few of the above context menu options. The selection
can be made at Row level, from the Row Number column, and the Cell selection
can be made from the content of each row. It allows for multiple selection as well.

Figure 4-93 Row and Cell Operations
 Insert:
 Insert Row/Cell Above: creates an empty row on top of the current position.
 Insert Row/Cell Below: creates an empty row below the current position.
 Insert Row/Cell Copied Above: creates a row with the copied data on top of
the current position.
 Insert Row/Cell Copied Below: creates a row with the copied data below the
current position.
 Cut Row/Cell
 Copy Row/Cell
 Paste Row/Cell
 Delete Row Contents: removes the contents of the entire row.
 Delete Row: removes the entire row
 Show signal treeMakes the configuration of 61850 reference possible, by visually
displaying the data template (DataTypeTemplates) in a tree form. In addition, it
allows for the use of X and N variables in the reference in order to configure the
column where the LNPrefix or LNInst of the signal will be read.
 Autocomplete: see the option 4.4.10.1.9
 Create new 'Data Object': Makes it possible to create a new DO in the CID
templates and use it as a private signal inside any ICD logical node of the
equipment.
o Logical Node: selection of the LN class.
o Logical Node Type: optional, it makes it possible to determine the selected LN's
specific class type. When generating CID, if the LN with the specific type does
not exist, an error will be generated and the new OD will not be created in the
CID.
o Function: optional; filter of the logic device used in the signal editor to display
signals associated with the particular function.

o LN button: allows for configuring the fields described above for the
configuration of the logical node in a visual manner, from a signal tree, with all
LN types from the equipment's ICD templates.
Figure 4-94 Operation: Show signal tree from data templates
Figure 4-95 Operation: Create new 'Data Object' type configuration.
o Data Object Name: allows the user to set a valid name in 61850 for the new
signal.
o Data Object Type: Data type for the signal.
o Final reference: signal instance, needs to end with the final status attribute,
LNClass.DO.DA for example GGIO1.Ind100. stVal
o DO button: makes it possible to configure the fields described above for the
configuration of the Data Object and its Final Reference.
Projects use their own standardized signal file and can be updated with the
standardized file of the CNF (see 2.5.2 for the different options.) Note: Comparing the
Project Table with the current table of the CNF version allows us to the New Data
Objects since they are not visually detected as modifications.

Figure 4-96 Update Standardized Project Signal File (overwrite)
4.4.10.2. Signal Association from File

To associate an IED to an Excel file with the configuration of its signals, right-click on
the IED name and select the Signal Association from File option in the Signal
Configuration sub-menu:
Figure 4-97 Signal association from file
The following window will then appear:

Figure 4-98 Signal association file selection
The user must select the XLS or CSV file with the IED signal configuration. Since XLS
files can contain several sheets, if the user selects an XLS file, a new list with the
sheets it contains will be displayed at the bottom of the menu, so that they can select
which one they want to use:

Figure 4-99 Signal association file selection - sheet selection
This file will be copied to the project folder, within the TechnicalAddress sub-folder,
renaming the file to the IED name.
For position IEDs, the mapping to the destinations (control centers) contained in the
file can be interpreted in two ways, depending on whether or not the Use SCU CID
option is enabled:
 If it is not enabled, it means that the mapping is for the position IED itself: this
happens when the IED communicates with the UCS via DNP3 protocol.
 If it is enabled, it means the mapping is for the UCS: The position IED reports
its statuses by IEC-61850 protocol to the UCS, and the UCS uploads them to
the dispatches by means of the point map defined in the file.
4.4.11. Standardized Signal Format

A CSV format file is needed for each IED, or an XLS book with the signals of each IED
on separate sheets. There are two options for associating a signal file: either from the
File menu with the Associate Signals option or from the signal configuration menu,
with the Signal Association from File option.

The application offers the 4.4.10.1 IED Signal Editor option, where some columns are
hidden, below, we can see the description of each column and those columns which
are visible from the interface.
4.4.11.1. Configuration of each signal

Each row defines the behavior, source and possible destinations for a signal. The
columns can be categorized into: "Signal Location", "Behavior Configuration", "Data
Acquisition" and "Higher Level Destination"
The meaning of each column is described below:
4.4.11.1.1. Signal location

Columns A, B, C, D, E and F are used to position the signal in the Project, making it
possible to locate the signal within the Substation, Voltage Level, Bay, IED
Equipment and signal functionality within the IEC 61850 Standard.
 A: IED name. It must coincide with the name of the Project's IED, to
which the signal file is associated.
 B: Project Substation Code.
 C: Voltage Level Code, matches the name used in the Project.
 D: Bay Code, matches the name used in the Project.
 E: Function Instance, function code plus the number of times the function
has been used, e.g. CSWI1 and CSWI2 for the case of an IED with two CSWI
Functions on the same bay.
 F - Logical device: Instance of the "Logical Device" (LD) to which the

signal belongs.
If the modeling is per bay, (the one used by default in all new projects) the
logical device will be formed by: Substation code + "_" + voltage level name +
"_" + bay name. For example: CAP_115kV_72090.
If the modeling is done by function (used in old projects) the logical device will
be formed by the fields: "Substation Code", "Bay Code", 'MCA' literal text and
"Instance Function."

Figure 4-100 Details of IED Functions on an Old Project Bay
Under IED Details > Bays, we can see in which bays the selected IED is located. In
the details, the Functions implemented by the IED are shown, therefore, so are the
signals that can be configured in the signal file. The required fields in the signal file
are: Column A, IED Name, in blue; Column F, LD (LDEVICE), in green. For
example, the MOPR function is used to configure measurements, so the
standardized signals for the MOPR function must be used, see 4.4.11.2
Standardized texts associated with signals
4.4.11.1.2. Behavior Configuration

The signal is configured for all the Graphical System Interfaces, e.g. configure a
signal from a BCU and indicate with which values it is inserted in the timeline and
the text associated with each value.
 G - Signal Name: Standardized text (ELEMENT) or 61850 reference. In the

case of signals belonging to switches and blades, the instance within the
position is identified between "{..}" brackets, according to the following rule:
 Q0_: Switch
 Q1_: Busbar Blades 1
 Q2_: Busbar Blades 2
Note: For signals from Other manufacturers, or non-standardized settings,
the use of references 61850,instance-id, is allowed:
(LNPrefix+ LNClass+ LNInst).DOI.DAI[FC]. For example:
INOUT_GGIO1.Ind03.stVal[ST]

 H - Instanc: Signal number within the logic device to which the signal belongs
(Logical node instance.) There are standardized signals in the "TA-I Table"
where the variable ${X} is used, for example in the configuration of direct
acquisition signals with TP/TC cards where the LEVEL must be indicated:
"Phase A voltage module CAPDIR"  DIRCAP_GGIO${X}.DOI.DAI There is
also the variable ${Y}, its value will be separated by a dash '-' and it will be
used to indicate the DOI instance, so the column will configure the instance of
the logical Node and the Data Object, for example "Analog input" 
${N}GGIO${X}.AnIn${Y}.mag.f
 I - Acronym definition: Specifies the behavior of the signals in the system's

display windows. The maximum length for the complete acronym (the string
formed by the set of all acronyms) is 255 characters. Acronyms allowed:
 E: Element identifying name: It is normally used in signals related

to equipment communication and represents the name of the
equipment.
 D: Signal description. Format:
Text '${element}' The description of the signal is obtained by

replacing '${element}' with the contents of column J - Acron.D.
Element. This composition is optional (column J may be empty), but
may be useful when the descriptive texts are standardized, since
'${element}' can be used to define the bay to which the signal
belongs.
All other acronyms only have an effect on digital signals (single and double
states):
o A0: Text representing the value 0.
o OC: Text associated with the Close command (used in the HMI)

o OO: Text associated with the Open command (used in the HMI)
o BO: Text for blocking the opening.
o BC: Text for blocking the closing.
o BG: Text for blocking the opening and closing
o NBC: Deactivation of the horn associated with the alarm.
o EV0: The signal is shown in the Chronological when it takes a value of 0.
o AL0: The signal is displayed in Alarms when it takes a value of 0.
o CO0:x Color for the Alarm signal when it takes a value of 0 where 'x' can
have the following values:
 R: Red Color
 G: Green Color
 B: Blue Color
 O: Orange Color
 Y: Yellow Color
 P: Purple Color
 W: White Color

o CO1:x Color for the Alarm signal when it takes a value of 0, where 'x' can
have the values described above.
o EVOR: Only used in CDC elements: "SPC" and "DPC". It means that the
source signals (opOpnOr and opClsOr) related to this signal will produce
events in the "event screen" when they report current command value
(value 1).
o EVOK: Only used in CDC elements: "SPC" and "DPC". It means that the
events in the "event screen" when they report command value OK (value
2).
o EVFA: Only used in CDC elements: "SPC" and "DPC". It means that the
events in the "event screen" when they report command value Fault
(value 3).
o ALOR: Only used in CDC elements: "SPC" and "DPC". It means that the
source signals (opOpnOr and opClsOr) related to this signal, will produce
alarms in the "alarm screen" when they report current order value (value
1).
o ALOK: Only used in CDC elements: "SPC" and "DPC". It means that the
source signals (opOpnOr and opClsOr) related to this signal, will produce
alarms in the "alarm screen" when they report order value OK (value 2).
o ALFA: Only used in CDC elements: "SPC" and "DPC". This means that
the source signals (opOpnOr and opClsOr) related to this signal will
produce alarms in the "alarm screen" when they report a Fault command
value (value 3).

The acronyms are separated by the string ";" if the edition is made with the
IED Signal Editor option; if instead, it is with external application, it is better to
use "::" to separate it.
 J - Acron.D Element: Variable part of the text, ${element}.
 K - Value: Configuration value of a signal parameter, belonging to the CF or

SP function group. In very special cases, some adjustment is needed in the
signal, i.e. it is a signal adjustment and will thus be in a new row. This row, not
being the configuration of a signal of its own, will not have any additional
configuration. All signals must be standardized in Table TA-I.
 L: Currently unused.
4.4.11.1.3. Data Acquisition Mode

The columns N, O, P, Q and R define the signal's information source, they compose
the field address. In addition, it is possible to set signal parameters with the M, S, T,
U and V columns.
 M - (C) Properties: It is used to store parameter settings, for example the

range of analogs or the pulse duration on digital outputs. See "4.4.10.1.12
Column-Specific Context Menu" in the "Acquisition Column" section.
a) IED-specific data acquisition

 N - (C) Master Protocol: CAPT for acquisition boards or DCAP for TP/TC
direct acquisition boards.
 O - (C) Master Profile: It should always be at 1.
 P - (C) LEVEL: Number of the level the signal belongs to.
 Q - (C) Signal type: Type of signal. Possible values:
o MSP: Simple digital input. Possibility to invert the digital input with the
suffix '_INV', example: MSP_INV
o MIT: Counter.
o MMN: Simple analog input (magnitude).
o MMC: Complex analog input (vector).

o MMF: Analog input in engineering values.
o MST: Transformer tap input
o CSC: Simple digital output. CSC_INV. Possibility of changing the control

model of the command, by forming the suffix with '_' and 'id-ctlModel'; for
example, CSC_3 generates the command with model 3 (Direct execution
with Advanced Security.) Admissible values:
 _0: status-only
 _1: direct-with-normal-security
 _2: sbo-with-normal-security
 _3: direct-with-enhanced-security
 _4: sbo-with-enhanced-security
If the signal has to be inverted and the control model changed, the control
model must be indicated first, and then the configuration of the inversion,
for example: CSC_3_INV.
o CDC: Double digital output. Possibility to change command control

model, in the same way as the CSC type.
o CRC: Output for transformer regulation. Possibility to change command

control model, in the same way as the CSC type.
o CMN: Analog output on 16-bit accounts.
o CMN32: Analog output on 32-bit accounts.
o CMF: Analog output in 32-bit engineering values.
 R - (C) Point: Signal number inside the level. The signals composed of two
single points are separated by the dash character '-', example 12-13
 S - (C) SIUnit/multiplier: Analog configuration, units and multiplier. SIUnits'

unit where the measurement is received. 'multiplier' the multiplication factor
for the unit in which the measurement is received, it is a number representing
the power of 10 that is applied to the measurement value before it is sent. The

values of each property will be separated by a blank space and the value of
each of them may be the value or the index (ordinal) of the enumeration. See
'SIUnits' and 'multiplier' from the IEC-61850 standard, 2nd edition, section
4.4.11.3 o 5.6.
 T - (C) DeadBand: ‘db' Threshold of change for measurements (by a

thousand.) It represents the percentage that the measure must vary to
generate an incidence in the system.
 U - (C) Scale: 'scaleFactor' for analog measurements or 'pulsQty' for

counters. Multiplication factor to obtain the value of the measurement from the
one received, in engineering value. When the measurement is received in
engineering value, the multiplication factor will be '1'.
 V - (C) Offset: 'Offset' Additive factor to obtain the value of the measurement
from the one received, in engineering value. When the measurement is
received in engineering value, the additive factor will be '0'.
b) Data acquisition via DNP protocol

 N - (C) Master Protocol: CDNP for DNP3 communications.
 O- (C) Master Profile: Index of the master protocol profile configured in the
IED. (Number of the communications master obtaining the data.) Matches the
number used in the profile code, for example: DNP3-IP_2, DNP3-SERIE_3.
Under IED details > Protocols > Master Profiles, we can select a profile and
see the details as shown in the figure below. This field is marked with the
color orange.

Figure 4-101 Master Communication Profile Details
 P- (C) Equipment: DNP address of the equipment. This equipment will be

added to a master protocol profile as a slave equipment. It corresponds to the
yellow color of the Figure 4-101 Master Communication Profile Details.
 Q - (C) Signal type: Type of signal. Possible values: idem previous point IED-
specific acquisition.
 R - (C) Point: DNP point corresponding to the data.
 S, T, U, V: configuration of analogs, the same as the configuration by IED-

c) Data acquisition via MODBUS protocol

 N - (C) Master Protocol: CMBUS for MODBUS communications.
 O - (C) Master Profile: Same as DNP, but for MODBUS master profiles. It
corresponds to the orange color of the Figure 4-101 Master Communication
Profile Details.
 P - (C) LEVEL/Equipment: Physical address of the equipment. This device

will be added to a MODBUS master protocol profile as a slave device. It
corresponds to the yellow color of the Figure 4-101 Master Communication
Profile Details.
 Q - (C) Signal type: Type of signal. Possible values: idem previous point IED-

 R - (C) Point: MODBUS address, consisting of the fields

[ReadCode][NumBytes][InvertByte][InvertWord][InvertLong][Address]:[Offset]
, the double signals are separated with the character '-', the fields are:
o ReadCode  modbus read code, admissible values: 1, 2, 3, 4.
o NumBytes  Number of bytes to be read, admissible values: 2, 4, 8.

Only valid for configuration of numerical registers (codes 3 and 4), for
the case of digital registers only a value of 1 makes sense.
o InvertByte  Flag that indicates whether or not to invert the 2 bytes of

the modbus registers (LittleEndian/BigEndian), values: 1 to invert them,
0 not to invert them.
o InvertWord  Flag that indicates whether or not to invert the 2 words of

the numerical data that occupy 2 modbus registers
(LittleEndian/BigEndian), values: 1 to invert them, 0 not to invert them.
o InvertLong  Flag that indicates whether to invert the 2 longs of the

numerical data that occupy 4 modbus registers
(LittleEndian/BigEndian), values: 1 to invert them, 0 not to invert them.
o Address  point address, admissible values: 0 to 65535.
o Offset  Applies only for MSP and CSC signal types in the cases
where the digital signal is inside numerical modbus registers, readable
through modbus codes 3 or 4, or writable through modbus codes 6. In
these cases, it is necessary to specify which bit is the one that indicates
the digital signal, within the 16 that a standard modbus register has;
values: from 1 to 16 (1 for the least significant and 16 for the most
significant.) If there is no offset it is not included in the MODBUS
address and its ':' separator will not be added either.
 Bits:
o Examples:
 Analog input: MMN340001201

 3 is ReadCode. Corresponds to reading numerical modbus registers.
 4 NumBytes (analog value consisting of 2 modbus registers of 16 bits
each)
 0 InvertByte (do not invert at byte level), 0 InvertWord (do not invert at
word level), 0 InvertLong (do not invert at long level)

 1201 Address. Initial numerical modbus register address number 1201

identifying the point; as we have indicated that it is 4 bytes (2 modbus
registers of 16 bits each) the analog value will be formed by registers
1201 and 1202. No ':' or Offset is entered as the signal type is neither
MSP nor CSC
 Simple digital input: MSP110001

 1 is ReadCode. Corresponds to reading digital modbus registers.
 1 NumBytes
 1 Address and 16 Offset. Digital modbus register address number 1
 Simple digital input: MSP320001:16

 3 is ReadCode. Corresponds to reading numerical modbus registers. In
this case, as MSP is a digital point, we are configuring for digitals
reading via numerical modbus registers, and therefore, we will need to
configure the ':' field and the Offset.
 2 NumBytes
 1 Address and 16 Offset. Numerical modbus register address number 1,
and within the 16 bits of the modbus register, the digital point set will be
bit 16 (the least significant.)
 Double digital input composed of two single ones: MDP320001:16-

320001:15
 Where 320001:16 is for the configuration of the first DI and 320001:15
for the second one.
 320001:16
 3 is ReadCode. Corresponds to reading numerical
modbus registers. In this case, as MSP is a digital point,
we are configuring for digitals reading via numerical
modbus registers, and therefore, we will need to configure
the ':' field and the Offset.
 2 NumBytes

 0 InvertByte (do not invert at byte level), 0 InvertWord (do

not invert at word level), 0 InvertLong (do not invert at long
level)
 1 Address and 16 Offset. Numerical modbus register
address number 1, and within the 16 bits of the modbus
register, the configured digital point will be bit 16 (the least
significant.)
 320001:15
 2 NumBytes
level)
register, the configured digital point will be bit 15.
d) Data acquisition via SAP20_TCD protocol

 N - (C) Master Protocol: CTCD for SAP20 TCD communications.
 O - (C) Master Protocol: Same as DNP, but for SAP20_TCD master

profiles. It corresponds to the orange color of the Figure 4-101 Master
Communication Profile Details.
 P - (C) Master Profile: Physical address of the equipment. This equipment

will be added to a master protocol profile SAP20_TCD as a slave
equipment. It corresponds to the yellow color of the Figure 4-101 Master
Communication Profile Details.
 Q - (C) Signal type: Type of signal. Possible values: idem previous point
IED-specific acquisition.
 R - (C) Point: SAP20_TCD point corresponding to the data.

 S, T, U, V: configuration of analogs, the same as the configuration by IED-

4.4.11.1.4. Destination to Higher Levels

Columns W, X, Y, Z determine the information destination for the signal, which will
be communicated by a Slave Protocol Profile. In addition, it is possible to set
parameters in the communication with the master equipment through the AA, AB,
AC, AD, AE columns. These columns correspond to the first address of a slave
protocol profile used to communicate with a master device, e.g. to communicate
with ControlCenter3. The following columns (AF-AN, AO-AW, etc.) would constitute
the second slave address, thus, forming groups of 9 columns, the information of a
signal would be communicated to several master equipment. The maximum
number of addresses is 10 in a row.
a) Data destination by DNP3 protocol

 W - (S1) Slave Protocol: Protocol identification string. For a DNP3 Slave
Protocol Profile configured in the UCS, the string is 'SDNP', i.e. the signal will
be published in the UCS, even if it is a signal from another IED. Allows for
configuration with the '_IED' suffix, e.g. 'SDNP_IED'. This suffix indicates that
the Slave Protocol Profile is from the IED itself, it is used, for example, to
communicate a BCU with another BCU or SCU by DNP.
 X - (S1) Slave profile: It coincides with the index of the Slave Protocol Profile
configured in the IED. In the case of 'SDNP', the slave profile is configured in
the SCU, to communicate with the control center. In the case of 'SDNP_IED',
the profile is configured in the BCU, to communicate via DNP3 with the other
IED. Under IED details > Protocols > Slave profiles, we can select a profile and
see the details as shown in the figure below. This field is marked with the color
orange.

Figure 4-102 Slave Communication Profile Details
 Y - (S1) Signal type: Type of signal. Possible values
suffix '_INV', example: MSP_INV
o MDP: Double digital input. MDP_INV
o MSP_MDP: Simple digital input, simple to double point functionality.

"asgFunc" initialized to "SP TO DP"
o MIT: Counter.
o MMN: Simple 16-bit (magnitude) analog input.
o MMN32: Simple 32-bit (magnitude) analog input.
o MMC: Complex (vector) 16-bit analog input.
o MMC32: Complex (vector) 32-bit analog input.
o MMF: Analog input in 16-bit engineering values.
o MMF32: Analog input in 32-bit engineering values.
o MST: Transformer tap input
o CSC: Simple digital output. CSC_INV

o CDC: Double digital output. CDC_INV
o CRC: Output for transformer regulation.
o CMN: Analog output on 16-bit accounts
o CMN32: Analog output on 32-bit accounts
 Z - (S1) Point: DNP point for the signal
 AA: Currently unused, the configurator automatically allocates the instance

number
 AB - (S1) LowLim: Analog configuration, lower limit
 AC - (S1) UppLim: Analog configuration, upper limit
 AD - (S1) Multiplier: Analog configuration, multiplier. Allowed values: in text

or ordinal number. See 'multiplier' in IEC-61850 standard, 2nd edition, section
4.4.11.3 o 5.6.
 AE - (S1) BanTreat/timEsp: For inputs (digital, analog, counters) the

"banTreat" parameter is configured and, for outputs, only for protocols S101
and S104, the "timEsp" parameter
b) Data destination by IEC101 or IEC104 protocol

(Only the differences with the DNP protocol are specified)
 W - (S1) Slave Protocol: 'S101' and 'S101_IED' or 'S104' and 'S104_IED'
 X - (S1) Master Protocol: See above
 Y - (S1) Signal type: Type of signal. Possible values
o MMEA: Measurement, standardized value
o MMEC: Measurement, floating point value.
suffix '_INV', example: MSP_INV.
o MDP: Double digital input. MDP_INV
o MSP_MDP: Digital input, single-point to double-point functionality

"asgFunc" initialized to "SP TO DP"

o MDP_MSP: Digital input, double point to single point functionality.

"asgFunc" initialized to "DP TO SP ON"
o MDP_MSP_INV: Digital input, double point to single point inverted

functionality. "asgFunc" initialized to "DP TO SP OFF"
o MIT: Counter.
o MST: Transformer tap input.
o CSEA: Analog control, standardized value.
o CSEC: Analog command, floating point value.
o CSC: Simple digital output. CSC_INV
o CDC: Double digital output. CDC_INV
o CRC: Output for transformer regulation.
 Z - (S1) Point: IOA signal address. To monitor an input IOA, the Output IOA
is configured and the input IOA to be monitored with a blank space.
Example: 12 100; with the IOA 22 the IOA 100 is monitored
 AE - (S1) BanTreat/timEsp: For inputs (digital, analog, counters) the

"banTreat" parameter is configured and, for outputs, only for protocols S101
and S104, the "timEsp" parameter
c) Data destination by MODBUS protocol

(Only the differences with the DNP protocol are specified)
 W - (S1) Slave Protocol: 'SMBUS' and 'SMBUS_IED'
 X -(S1) Master Protocol: See above
 Y - (S1) Signal type: Type of signals allowed
suffix '_INV', example: MSP_INV.
o MDP_MSP: Simple composite digital input "DP TO SP ON."
o MDP_MSP_INV: Simple composite digital input "DP TO SP OFF."

o MMN: Simple 16-bit (magnitude) analog input.
o MMN32: Simple 32-bit (magnitude) analog input.
o MMF: Analog input in engineering values.
o CSC: Simple digital output. Invert with CSC_INV.
o CMF: Analog output in engineering values.
 Z - (S1) Point: MODBUS address, composed of the fields
 [ReadCode] [NumBytes] [InvertByte] [InvertWord] [InvertLong] [Address]:

[Offset], the double signals are separated with the character '-', the fields are:
 ReadCode  modbus read code, values allowed: 1, 2, 3, 4, 5 and 6.
o MSP: 1 (COIL STATUS), 2 (DISCRETE INPUT)
o MMN, MMN32 and MMF: 3 (...HOLDING REGISTER), 4 (...INPUT

REGISTER)
o CSC: 5 (COIL OUTPUT)
o CMN, CMN32, CMF: 6 (…OUTPUT)
 NumBytes  Number of bytes to be read, admissible values: 1, 2, 4.
 InvertByte  Flag that indicates whether to invert the 2 bytes of the modbus
registers (LittleEndian/BigEndian), values: 1 to invert them, 0 not to invert
them.
 InvertWord  Flag that indicates whether to invert the 2 words of the

numerical data that occupy 2 modbus registers (LittleEndian/BigEndian),
values: 1 to invert them, 0 not to invert them.

 InvertLong  Flag that indicates whether to invert the 2 longs of the numerical
data that occupy 4 modbus registers (LittleEndian/BigEndian), values: 1 to
invert them, 0 not to invert them.
 Address  point address, admissible values: 0 to 65535.
 Offset  Applies only for MSP and CSC signal types, in the cases where the
digital signal is inside numerical modbus registers, readable through modbus
codes 3 or 4, or writable through modbus codes 6. In these cases, it is
necessary to specify which bit is the one that indicates the digital signal, within
the 16 that a standard modbus register has; values: from 1 to 16 (1 for the least
significant and 16 for the most significant.) If there is no offset it is not included
in the MODBUS address and its ':' separator will not be added either.
o Bits:
o Examples:
 Analog input: MMN340001201

 3 is ReadCode. Corresponds to reading numerical modbus registers.
 4 NumBytes (analog value consisting of 2 modbus registers of 16 bits
each)
 1201 Address. Initial numerical modbus register address number 1201
identifying the point; as we have indicated that it is 4 bytes (2 modbus
registers of 16 bits each) the analog value will be formed by registers
1201 and 1202. No ':' or Offset is entered as the signal type is neither
MSP nor CSC
 Simple digital input: MSP110001

 1 is ReadCode. Corresponds to reading digital modbus registers.
 1 NumBytes
 1 Address and 16 Offset. Digital modbus register address number 1
 Simple digital input: MSP320001:16

 3 is ReadCode. Corresponds to reading numerical modbus registers. In
this case, as MSP is a digital point, we are configuring for digitals

reading via numerical modbus registers, and therefore, we will need to

configure the ':' field and the Offset.
 2 NumBytes
 1 Address and 16 Offset. Numerical modbus register address number 1,
and within the 16 bits of the modbus register, the digital point set will be
bit 16 (the least significant.)
 Double digital input composed of two single ones: MDP320001:16-

320001:15
 Where 320001:16 is for the configuration of the first DI and 320001:15
for the second one.
 320001:16
 2 NumBytes
level)
register, the configured digital point will be bit 16 (the least
significant.)
 320001:15
 2 NumBytes
level)

o 1 Address and 15 Offset. Numerical modbus register address number 1,

and within the 16 bits of the modbus register, the configured digital point
will be bit 15.
4.4.11.2. Standardized texts associated with signals

As explained in the 4.4.11.1.2 section, the signals are identified by a standardized text
(column G of the file.) These standardized texts are associated with the corresponding
61850 references, where the signal values will be deposited.
Each project will have its own file of standardized signals, which can be edited at any
time (see 4.4.10.1.14 Editing the standardized signal file) or overwritten with the file
provided by the CNF version. See section 2.5.2 Standardized Signal Table.
The signals can use variables for standardization:
 The column "Variable N" indicates that the signal requires a value - usually the
identifier - in the same column where we enter the Signal Name, using the {}
brackets, for example: LocalRemoteCSWI{Q0_}.
 The "Variable X" column indicates that the signal requires a value - usually the
instance of the logical node or instance in the object name - in the "Instanc.”
column. (column H) for example, in the column "Signal Name" the text "Logic
Command {22}", and in the column "Instanc" the value "3" would correspond to
the logic command 22 of the MLOGIC_GGIO3 node.
The following table describes the standard text for each of the signals which are classified
by the function that the signal contains:
CSWI function Switch or Blade Control

N Variable
X Variable
Signal Name Description Type
SPS
LocalRemoteCSWI A 1 when the switch or blade is in remote X -
ASG_CSWI
DPC
CutoffStatus Switch or blade status X -
ASG_CSWI

N Variable
X Variable
DPC
CutoffStatusPhaseA Switch status, phase A X -
ASG_CSWI
DPC
CutoffStatusPhaseB Switch status, phase B X -
ASG_CSWI
DPC
CutoffStatusPhaseC Switch status, phase C X -
ASG_CSWI
Pulse signal associated with each switch or blade

SPS
CommandAlarm command to indicate that a failure has occurred in X -
ASG_CSWI
the execution of the command
Table 12 Standardized signals CSWI function
XSWI function Blade status
N Variable
X Variable
SPS
LocalRemoteXSWI A 1 when the blade is in remote X -
ASG_XSWI
SPS
VDCLos Blade VCD Loss X -
ASG_XSWI
SPS
VACLos Blade VCA Loss X -
ASG_XSWI
Table 13 Standardized signals XSWI function
XCBR function Circuit breaker status

N Variable
X Variable
LocalRemoteXCBR A 1 when the switch is on remote SPS X -

ASG_XCBR
SupervTripCoil1 Tripping coil supervision 1 SPS X -

ASG_ XCBR
SupervTripCoil2 Tripping coil supervision 2 SPS X -

ASG_XCBR
SupervTripCoil12OpPhaseA Tripping coil failure 2 Phase A Open SPS X -

ASG_XCBR

N Variable
X Variable
SupervTripCoil2OpPhaseB Tripping Coil Failure 2 Phase B Open SPS X -

ASG_XCBR
SupervTripCoil2OpPhaseC Tripping coil failure 2 Phase C Open SPS X -

ASG_XCBR
SupervTripCoil2ClPhaseA Tripping Coil Failure 2 Phase A Closed SPS X -

ASG_XCBR
SupervTripCoil2ClPhaseB Tripping Coil Failure 2 Phase B Closed SPS X -

ASG_XCBR
SupervTripCoil2ClPhaseC Tripping Coil Failure 2 Phase C Closed SPS X -

ASG_XCBR
PolDisc Pole Discrepancy SPS X -

ASG_XCBR
VCDLossTrigCirc1 VCD loss trigger circuit 1 SPS X -

ASG_XCBR
VCDLossTrigCirc2 VCD loss trigger circuit 2 SPS X -

ASG_XCBR
VCASwiLos VCA switch loss SPS X -

ASG_XCBR
VDCIntLos VCD switch loss SPS X -

ASG_XCBR
MechanismBlocked Locked mechanism (unloaded spring) SPS X -

ASG_XCBR
VCDLossIntClosCirc VCD loss interrupter closing circuit SPS X -

ASG_XCBR
MotorCirVDCLos VDC loss Motor Circuit SPS X -

ASG_XCBR
PotentialFailure Potential failure SPS X -

ASG_XCBR
PopupCommandOpening Opening of pop-up command. SPS X -

ASG_XCBR
VdcCufoLoss VDC CUFO loss SPS X -

ASG_XCBR
PP1Abnormality PP1 abnormality SPS X -

ASG_XCBR
PP2Abnormality PP2 abnormality SPS X -

ASG_XCBR
50FI Abnormality 50FI abnormality SPS X -

ASG_XCBR
AlarmOp86FI 86FI abnormality SPS X -

ASG_XCBR
EncReengInt1 Reclose Interlock I SPS X -

ASG_XCBR
EncReengInt2 Reclose Interlock II SPS X -

ASG_XCBR

N Variable
X Variable
ClosSpringDsch Unloaded Closing Spring SPS X -

ASG_XCBR
ExtSequentialCircuit External Sequential Circuit SPS X -

ASG_XCBR
LockingCoup Locking coupling SPS X -

ASG_XCBR
ThermoCirLocClosVDC Thermostat Circuit Local Lock Out VDC SPS X -

ASG_XCBR
CircRemoteLockOutVDC Thermostat Circuit Remote Lock Out VDC SPS X -

ASG_XCBR
ThermoCircOpen1VCD Thermostat Circuit Opening 1 out VCD SPS X -

ASG_XCBR
ThermoCircOpen2VCD Thermostat Circuit Opening 2 out VCD SPS X -

ASG_XCBR
VDCBladCircLoss VDC Blades Circuit Loss SPS X -

ASG_XCBR
SYNCAbnormality SYNC abnormality SPS X -

ASG_XCBR
VerLowGasPressure Very low gas pressure SPS X -

ASG_SIMG
LowGasPressureOpLock Low gas pressure operation lockout SPS X -

ASG_SIMG
LowPressureTrig Low pressure trigger SPS X -

ASG_SIMG
MinGasPressure Low gas pressure SPS X -

ASG_SIMG
Table 14 Standardized signals XCBR function
MOPR function Phase Operation Measurement

N Variable
X Variable
CMV
Module of the phase A voltage Module of the phase A voltage X -
ASG_MMXU

N Variable
X Variable
CMV
Module of the phase B voltage Module of the phase B voltage X -
ASG_MMXU
CMV
Module of the phase C voltage Module of the phase C voltage X -
ASG_MMXU
CMV
Module of the phase S voltage Module of the phase S voltage X -
ASG_MMXU
CMV
Neutral voltage module Neutral voltage module X -
ASG_MMXU
CMV
Phase A current module Phase A current module X -
ASG_MMXU
CMV
Phase B current module Phase B current module X -
ASG_MMXU
CMV
Phase C current module Phase C current module X -
ASG_MMXU
CMV
Neutral current module Neutral Current Module X -
ASG_MMXU
MV
Three-phase active power Three-phase active power X -
ASG_MMXU
MV
Three-phase reactive power Three-phase reactive power X -
ASG_MMXU
MV
Three-phase apparent power Three-phase apparent power X -
ASG_MMXU
MV
Three-phase power factor Three-phase power factor X -
ASG_MMXU
MV
Frequency Frequency X -
ASG_MMXU
Fundamental average of the voltages of the three MV

Average V X -
phases ASG_MMXU
Fundamental average of the currents of the three MV

I average X -
phases ASG_MMXU
CMV
AB line voltage module AB line voltage module X -
ASG_MMXU
CMV
BC line voltage module BC line voltage module X -
ASG_MMXU
CMV
AC line voltage module AC line voltage module X -
ASG_MMXU
MV
V fundamental average Arithmetic average of the voltages of the three phases X -
ASG_MMXU

N Variable
X Variable
CMV
Active power phase A Active power phase A X -
ASG_MMXU
CMV
Active power phase B Active power phase B X -
ASG_MMXU
CMV
Active power phase C Active power phase C X -
ASG_MMXU
CMV
Reactive power phase A Reactive power phase A X -
ASG_MMXU
CMV
Reactive power phase B Reactive power phase B X -
ASG_MMXU
CMV
Reactive power phase C Reactive power phase C X -
ASG_MMXU
CMV
Apparent power phase A Apparent power phase A X -
ASG_MMXU
CMV
Apparent power phase B Apparent power phase B X -
ASG_MMXU
CMV
Apparent power phase C Apparent power phase C X -
ASG_MMXU
CMV
Power factor phase A Power factor phase A X -
ASG_MMXU
CMV
Power factor phase B Power factor phase B X -
ASG_MMXU
CMV
Power factor phase C Power factor phase C X -
ASG_MMXU
CMV
Voltage Unbalance Voltage Unbalance (%) X -
ASG_MMXU
CMV
Current Unbalance Current Unbalance (%) X -
ASG_MMXU
MV
Line side frequency Line side frequency X -
ASG_MMXU
MV
Bar side frequency Bar side frequency X -
ASG_MMXU
Table 15 Standardized signals MOPR function

MBAL function Measurement for Energy Balance
N Variable
X Variable
BCR
Active Energy Delivered Active Energy Delivered - -
ASG_MMTR
BCR
Active Energy Received Active Energy Received - -
ASG_MMTR
BCR
Apparent Energy Apparent Energy - -
ASG_MMTR
BCR
Total active energy Total active energy - -
ASG_MMTR
BCR
Reactive energy delivered Reactive energy delivered - -
ASG_MMTR
BCR
Reactive energy received Reactive energy received - -
ASG_MMTR
BCR
Total reactive energy Total reactive energy - -
ASG_MMTR
BCR
ConWhPos Wh+ consumed at the last Station Base Rate - -
ASG_MMTR
BCR
ConWhNeg Wh- consumed at the last Base Rate Station - -
ASG_MMTR
BCR
TotWhPos Total Wh+ - -
ASG_MMTR
BCR
TotWhNeg Total Wh- - -
ASG_MMTR
BCR
TotVArh1 Total VARh I - -
ASG_MMTR
BCR
TotVArh2 Total VARh II - -
ASG_MMTR
BCR
TotVArh3 Total VARh III - -
ASG_MMTR
BCR
TotVArh4 Total VARh IV - -
ASG_MMTR
BCR
ConDWhPos Previous day Wh+ Consumption - -
ASG_MMTR
BCR
ConDWhNeg Previous day Wh- Consumption - -
ASG_MMTR
BCR
FrWhPos Frozen Wh+ last base rate station - -
ASG_MMTR

N Variable
X Variable
BCR
FrWhNeg Frozen Wh- last base rate station - -
ASG_MMTR
BCR
FrWh2Pos Frozen Wh+ penultimate base station - -
ASG_MMTR
BCR
FrWh2Neg Frozen Wh- Base Rate Penultimate Station - -
ASG_MMTR
BCR
ConWh2Pos Wh+ Consumption last third - -
ASG_MMTR
BCR
ConDWhHPos Positive active energy demand (delivered) - -
ASG_MMTR
BCR
ConDWhHNeg Negative active energy demand (received) - -
ASG_MMTR
BCR
ConVArh1 Reactive energy demand 1 quadrant - -
ASG_MMTR
BCR
ASG_MMTR
BCR
ASG_MMTR
BCR
ASG_MMTR
BCR
ConWhPosUETB Active energy delivered demand last station base rate - -
ASG_MMTR
BCR
ConWhNegUETB Active power received demand last station base rate - -
ASG_MMTR
Quadrant 1 reactive power demand, last base rate BCR

ConVArh1UETB - -
station. ASG_MMTR

ConVArh2UETB - -
station. ASG_MMTR

ConVArh3UETB - -
station. ASG_MMTR

ConVArh4UETB - -
station. ASG_MMTR
Table 16 Standardized signals MBAL function

BCU - TP/TC Direct Acquisition function
N Variable
X Variable
MV
CAPDIR three-phase active power Three-phase active power - X
DCAP_GGIO
MV
CAPDIR three-phase reactive power Three-phase reactive power - X
DCAP_GGIO
MV
CAPDIR three-phase apparent power Three-phase apparent power - X
DCAP_GGIO
MV
CAPDIR three-phase power factor Three-phase power factor - X
DCAP_GGIO
CMV
Module of the phase A voltage CAPDIR Module of the phase A voltage - X
DCAP_GGIO
Module of the voltage of CAPDIR phase CMV

Module of the phase B voltage - X
B DCAP_GGIO
CMV
Module of the C-phase voltage CAPDIR Module of the phase C voltage - X
DCAP_GGIO
CMV
Module of the phase S voltage CAPDIR Module of the phase S voltage - X
DCAP_GGIO
CMV
NEUTRAL CAPDIR voltage module Neutral voltage module - X
DCAP_GGIO
Module of the NET CURRENT CAPDIR CMV

Net Current Voltage Module - X
voltage DCAP_GGIO
CMV
Module of the phase A current CAPDIR Module of phase A current - X
DCAP_GGIO
CMV
Module of the phase B current CAPDIR Module of the phase B current - X
DCAP_GGIO
CMV
Module of the phase C current CAPDIR Module of the phase C current - X
DCAP_GGIO
CMV
NEUTRAL CAPDIR current module Neutral Current Module - X
DCAP_GGIO
CMV
Module of the NET CURRENT CAPDIR Net current module - X
DCAP_GGIO
CMV
Active power phase A CAPDIR Active power of phase A - X
DCAP_GGIO
CMV
Active power phase B CAPDIR Active power phase B - X
DCAP_GGIO
CMV
Active power phase C CAPDIR Phase C active power - X
DCAP_GGIO
Table 17 Standardized signals DIRCAPT function

YPTR function Transformation Bank
N Variable
X Variable
BSC
RaiseLowerTap Transformer regulation - -
ASG_YLTC
MV
TapStatus Transformer tap status - -
ASG_ YLTC
Table 18 YPTR function Standardized signals
GAPC Function Generic logic functions
N Variable
X Variable
Generic use digital input 'n', where 'n' can take on values from 1 SPS
Digital input GAPC 'n’ - -
to 40. ASG_GAPC
General purpose digital input which can take on values from 1 to SPS
GAPC Digital input - X
over 40. ASG_GAPC
Table 19 GAPC function Standardized signals
GGIO function Generic Inputs and Outputs
N Variable
X Variable
General purpose 'n' digital input, where 'n' can take on values SPS
'N' Digital input - -
from 1 to 32. ASG_GGIO_GEN
General purpose digital input which can take on values from 1 to SPS
Digital input - X
over 32. ASG_GGIO_GEN
General purpose double digital input which can take on values DPS
Double digital input - X
from 1 to over 32 ASG_GGIO_GEN
General purpose 'n' counter, where 'n' can take on values from 1 BCR
'n' Counter - -
to 32. Instant values. ASG_GGIO_GEN
Generic purpose counter which can take on values from 1 to over BCR
Counter - X
32. Instant values. ASG_GGIO_GEN
Generic purpose counter which can take on values from 1 to over BCR
Frozen counter - X
32. Frozen values. ASG_GGIO_GEN

N Variable
X Variable
Generic purpose analog input 'n', where 'n' can take on values MV
'n' Analog input - -
from 1 to 32. Floating point values. ASG_GGIO_GEN
General purpose analog input which can take on values from 1 MV

Analog input - X
to over 32. Floating point values ASG_GGIO_GEN
General purpose analog input which can take on values from 1 MV

i Analog input - X
to over 32. Integer values. ASG_GGIO_GEN
General purpose digital output 'n', where 'n' can take on values CPS
Digital output 'n' - -
from 1 to 32. ASG_GGIO_GEN
General purpose digital output which can take on values from 1 CPS
Digital output - X
to over 32 ASG_GGIO_GEN
Double digital output General purpose double digital output 'n', where 'n' can take on CPD
- -
'n' values from 1 to 32. ASG_GGIO_GEN
Double digital output for general purpose which can take on CPD
Double digital output - X
values from 1 to over 32. ASG_GGIO_GEN
General purpose analog output which can take on values from 1 APC
Analog output - X
to over 32. Floating point values. ASG_GGIO_GEN
General purpose analog output which can take on values from 1 APC
Analog output i - X
to over 32. Integer values. ASG_GGIO_GEN
CMV
Reactive power Phase A CAPDIR Phase A reactive power - X
DCAP_GGIO
CMV
Reactive power Phase B CAPDIR Phase B reactive power - X
DCAP_GGIO
CMV
Reactive power Phase C CAPDIR Phase C reactive power - X
DCAP_GGIO
CMV
Apparent power phase A CAPDIR Phase A apparent power - X
DCAP_GGIO
CMV
Apparent power phase B CAPDIR Phase B apparent power - X
DCAP_GGIO
CMV
Apparent power phase C CAPDIR Phase C apparent power - X
DCAP_GGIO
CMV
Power factor phase A CAPDIR Phase A power factor - X
DCAP_GGIO
CMV
Power factor phase B CAPDIR Phase B power factor - X
DCAP_GGIO
CMV
Power factor phase C CAPDIR Phase C power factor - X
DCAP_GGIO
Module of the line voltage AB CMV

AB line voltage module - X
CAPDIR DCAP_GGIO
Voltage module of the BC CAPDIR CMV

BC line voltage module - X
line DCAP_GGIO

N Variable
X Variable
Voltage module of the AC CAPDIR CMV

AC line voltage module - X
line DCAP_GGIO
BCR
Apparent Energy CAPDIR Apparent energy - X
DCAP_GGIO
BCR
Total reactive energy CAPDIR Total reactive energy - X
DCAP_GGIO
BCR
Total active energy CAPDIR Total active energy - X
DCAP_GGIO
BCR
Active Energy Delivered CAPDIR Active energy delivered - X
DCAP_GGIO
BCR
Active Energy Received CAPDIR Active energy received - X
DCAP_GGIO
BCR
Reactive energy delivered CAPDIR Reactive energy delivered - X
DCAP_GGIO
BCR
Reactive energy received CAPDIR Reactive energy received - X
DCAP_GGIO
Table 20 GGIO function Standardized signals
GENERAL function Internal alarms of saTECH equipment
This function is internal to the equipment. Each IED model has its own GENERAL
function, so there are differences in signals.
Common GENERAL function:

N Variable
X Variable
SPS
GPSFail GPS failure - -
ASG_LTMS
SPS
DriftSynchronization Synchronization drift - -
ASG_LTMS
SPS
EthernetFailure1 Ethernet port failure 1 X -
ASG_LCCH
SPS
ASG_LCCH
SPS
ASG_LCCH
NetworkEquipFailure Ethernet port 'n' failure SPS - X

N Variable
X Variable
ASG_LCCH
DNP3 Equipment SPS

DNP3 slave equipment responds - X
Responds DNP_GGIO
Counter for failed communication retry attempts via BCR

DNP3 RetryCounterV1 - X
Channel 1 with DNP3 slave equipment DNP_GGIO
Counter for failed communication retry attempts via BCR

DNP3 RetryCounterV2 - X
Channel 2 with DNP3 slave equipment DNP_GGIO
Counter for failed communication attempts via Channel BCR

DNP3 FailureCounterV1 - X
1 with DNP3 slave equipment DNP_GGIO
DNP3
FailureCounter - X
2 with DNP3 slave equipment DNP_GGIO
V2
SAP20RTU Equipment SPS
RTU-SAP20 slave equipment responds - X
Responds RTU_GGIO
SAP20RTU Protocol SPS

SAP20-TCD Protocol Error - X
error RTU_GGIO
SAP20RTU SPS
To 1 when the RTU is in remote - X
LocalRemote RTU_GGIO
SAP20RTU SPS
Secondary channel of communication - X
Communication Channel RTU_GGIO
SAP20RTU Hardware SPS

Digital inputs hardware failure in RTU-SAP20 - X
failure digital inputs RTU_GGIO

Digital outputs hardware failure in RTU-SAP20 - X
failure digital outputs RTU_GGIO

Analog inputs hardware failure in RTU-SAP20 - X
failure analog inputs RTU_GGIO
SAP20RTU Counter for failed communication retry attempts via BCR

- X
RetryCounterV1 Channel 1 with RTU-SAP20 slave equipment RTU_GGIO
SAP20RTU Counter for failed communication retry attempts via BCR

- X
RetryCounterV2 Channel 2 with RTU-SAP20 slave equipment RTU_GGIO
SAP20RTU Counter for failed communication attempts via Channel BCR

- X
FailureCounterV1 1 with RTU-SAP20 slave equipment RTU_GGIO
SAP20RTU
FailureCounter - X
2 with RTU-SAP20 slave equipment RTU_GGIO
V2
MODBUS Team SPS
MODBUS slave equipment responds - X
Responds MBUS_GGIO
MODBUS Counter for failed communication retry attempts via BCR

- X
RetryCounterV1 Channel 1 with MODBUS slave equipment MBUS_GGIO

N Variable
X Variable
MODBUS Counter for failed communication retry attempts via BCR

- X
RetryCounterV2 Channel 2 with MODBUS slave equipment MBUS_GGIO

MODBUS FailCounterV1 - X
1 with MODBUS slave equipment MBUS_GGIO

MODBUS FailCounterV2 - X
2 with MODBUS slave equipment MBUS_GGIO
SPC
Creation of the GENERAL/MLOGIC_GGIO logical
MLOGIC ASG_GGIO_ - X
nodes
MLOGIC
SPC
Logic Command General digital output for simple logic commands ASG_GGIO_ X X
MLOGIC
DPC
Dual Logic Command General dual digital output for dual logic commands ASG_GGIO_ X X
MLOGIC
SPC
LOGGAPC Creation of the GENERAL/LOGGAPC logical nodes - X
ASG_GAPC
Table 21 GENERAL Common Standardized signals
GENERAL function for substation equipment (UCS or HMI):
N Variable
X Variable
SPS
LocalRemoteSU To 1 when the equipment is in remote - -
ASG_LLN0_GEN
SPS
AlarmProcess Alarm in process - -
ASG_LLN0_GEN
SPS
AlarmHDError HD disk with error alarm - -
ASG_LLN0_GEN
SPS
AlarmDBError Database with error alarm - -
ASG_LLN0_GEN
SPS
RAIDAlarma RAID Alarm - -
ASG_LLN0_GEN
SPS
MemoryConsumption Current memory consumption - -
ASG_LLN0_GEN
SPS
MemoryConsumptionAlarm Memory consumption alarm - -
ASG_LLN0_GEN

N Variable
X Variable
SPS
CPUConsumption Current CPU consumption - -
ASG_LLN0_GEN
SPS
CPUConsumptionAlarm CPU consumption alarm - -
ASG_LLN0_GEN
SPS
CPUTemperature Current CPU temperature - -
ASG_LLN0_GEN
SPS
CPUTemperatureAlarm CPU Temperature Alarm - -
ASG_LLN0_GEN
SPS
HDConsumptionAlarm HD disk consumption alarm - -
ASG_LLN0_GEN
SPS
M8LinkAlarm M8 link alarm - -
ASG_LLN0_GEN
SPS
AlarmaFuenteAlimentacion1 Power supply 1 alarm - -
ASG_LLN0_GEN
SPS
PowerSupply2Alarm Power supply 2 alarm - -
ASG_LLN0_GEN
Alarm alert via email or SMS. See HMI/SCU VSG

SMS-email - X
installation manual ASG_GGIO_ALERT
Table 22 GENERAL SU Standardized signals
GENERAL function for Positioning equipment (BCU or RIO):

N Variable
X Variable
SPS
LocalRemotoBU A 1 when the equipment is in remote - -
ASG_LLN0_GEN
SPS
DisplayChange Programming changes via display - -
ASG_LLN0_GEN
SPS
EmergCommPopup Opening of Pop-up Command - -
GENGGIO
SPS
Abnorm50FI 50 FI abnormality function - -
GENGGIO
SPS
SwitchFailure Communication switch failure - -
GENGGIO
Table 23 GENERAL BU Standardized signals

Note: See Standardized Signal File, (Table TA-I) provided by the configurator from the
Standardized Signal Table submenu in the Tools menu.
4.4.11.3. Configuration parameters

The following parameters are for analog configuration. During an analog signal
configuration, the default values of the following parameters can be adjusted:
 Units: Unit where the measurement is received, also known as SIUnit

Enumeration which can have the following values or the index that references
them:
o 1 o 35  Lm
o 2m o 36  Wb
o 3  Kg o 37  T
o 4s o 38  W
o 5A o 39  Pa
o 6K o 41  m2
o 7  mol o 42  m3
o 8  cd o 43  m/s
o 9  deg o 44  m/s2
o 10  rad o 45  m3/s
o 11  sr o 46  m/m3
o 21  Gy o 47  M
o 22  q o 48  Kg/m3
o 23  ºC o 49  m2/s
o 24  Sv o 50  W/m K
o 25  F o 51  J/K
o 26  C o 52  ppm
o 27  S o 53  1/s
o 28  H o 54  rad/s
o 29  V o 61  W/m2
o 30  ohm o 62  Watts
o 31  J o 63  VAr
o 32  N o 64  phi
o 33  Hz o 65  cos (phi)
o 34  lx o 66  Vs

o 67  V2 o 76  char
o 68  As o 77  char/s
o 69  A2 o 78  Kgm2
o 70  A2t o 79  dB
o 71  VAh o 80  J/Wh
o 72  Wh o 81  W/s
o 73  VArh o 82  I/s
o 74  V/Hz o 83  dBm
o 75  Hz/s
 Multiplier: Multiplication factor for the unit in which the measurement is received.
It is a number representing the power of 10 that is applied to the measurement
value before it is sent.
o -24  y
o -21  z
o -18  a
o -15  f
o -12  p
o -9  n
o -6  µ
o -3  m
o -2  c
o -1  d
o 0
o 1  da
o 2h
o 3k
o 6M
o 9G
o 12  T
o 15  P
o 18  E
o 21  Z
o 24  Y

 db: Threshold of change for the measures (by a thousand). It represents the
percentage that the measure must vary to generate an incidence in the system.
 scale factor: Multiplication factor to obtain the value of the measurement from the
one received, in engineering value - also known as "ScaleFactor". When the
measurement is received in engineering value, the multiplication factor will be '1'.
 offset: Additive factor to obtain the value of the measurement from the one
received, in engineering value. When the measurement is received in engineering
value, the additive factor will be '0'.
4.4.12. Calculated Signals

In addition to the signals coming from logic, there are other signals calculated internally
by the equipment, such as hardware anomalies (Ethernet port anomalies, serial port
anomalies, etc.), these signals will be automatically registered.
These signals can be configured in the same way as any other signal (slave addressing,
acronyms, etc.).
 Hardware anomalies. The modeling of the hardware anomalies of the

equipment is detailed in the Hardware anomalies modeling section of this
document.
 Communications statistics. The equipment stores, for each equipment with
which it communicates by conventional protocols, its communication statistics:
o Primary communication attempt counter.
o Secondary communication attempt counter.
o Counter for failed communication attempts via primary channels.
o Counter for failed communication attempts via secondary channels.
These values are stored as counters in the GGIO representing equipment (the
modeling of the slave equipment is detailed in the Modeling of slave equipment
section of this document.)
The user must configure the behavior of these counters, which must be the
same for all the slave equipment:
o Enabling/Disabling the Counter Freeze
o If counter reset is enabled, counter freeze period (seconds.)
o Enabling/Disabling the counter reset.
o If counter reset is enabled, reset period (seconds.)

o Source for freezing and resetting periods.
 Local/general IED control:

It is modeled in the 'LocKey' DO (CDC SPS) of the LLN0 LN, in the 'GENERAL’
LD. This calculated signal allows the logic command to change the status. When
its value is '1', all commands are inhibited in the IED.
 Local/Remote associated with each controllable element:
The 'LocKey' DO is determined in the LNs with control: CSWI, ZGEN, GAPC,
YLTC, ATCC.
4.4.13. Graphics
This sub-menu is only available for BCU devices. It is not available for RIO, substation or
other manufacturers' equipment.
4.4.13.1. Associate BCU positions

It makes it possible to associate a previously created (by means of the saTECH CNF)
single-line diagram to a bay. By displaying the combo associated with each bay, the set
graphics will be shown, and the user can select the one that corresponds to the bay to be
represented, as shown in the Figure 4-103.
When an IED controls more than one bay, this operation will be repeated for each bay,
and the overview of all bays will be automatically composed in the drawing area.
The saTECH CNF software will automatically allocate the signals associated to each
element (switches, isolators, system disconnection, semaphores, measurements and
alarms) to each bay chart.

Figure 4-103 Bay graphic selection
4.4.13.2. Edit Single-Line BCU

It allows for editing and modifying the single-line diagram associated to a position, as
shown in the Figure 4-104:
Figure 4-104 Edit Single Line BCU
If the single-line diagram already exists, selecting YES will display the Figure 4-105, in
which the Graphic Editor of the saTECH BCU is shown, allowing its modification

Figure 4-105 Single Line BCU Array Editing
It should be noted that once the single-line diagram has been edited, the signals represented in
the drawing must be associated.
4.4.13.3. Generation of the Single Line associated to an IED

To do this, right click on the IED name, click
on the Graphics sub-menu and select the
option Generate Single Line Drawing for
BCU:
The application will generate the file

corresponding to the Single Line diagram
defined for the IED. This file will be stored in
Figure4-106 Graph generation
the project folder, in the Single Line sub-
Single line IED
folder, and within it, in a sub-folder whose name coincides with the name of the IED. The
file is named single-line.svg.
4.4.14. TFT Password Configuration

It makes it possible to set the password to be entered when the user carries out a
command from the Position Single Line of the equipment's TFT display (see Figure
4-107.) This option only applies to saTECH BCU models with built-in TFT.

Figure 4-107 TFT password configuration
For the password, only numbers between 1 and 8 digits are allowed. Once the password
has been entered, it will be requested again when the user wants to give a new
command.
Terminating the wizard with an empty Password will clear the project’s last password
setting.
4.4.15. Configurable Parameters

It makes it possible to adjust configurable parameters of the different saTECH equipment.
The options found in this sub-menu will depend on the type of IED we have clicked on.
The following figures show the different configuration options of the saTECH equipment
The BCU device options "Configurable parameters TP and TC" and "Function 25" will only
be available when the device has TP and TC acquisition boards. Remember that these
cards cannot be on the first two levels and that, when they are on a BUS card we must add
a 5 in the equipment model’s corresponding place and, when they are on an expander
card, we must add an E in the equipment model’s corresponding place. We can therefore
quickly find out if the equipment has this type of card by looking at their model. In addition,
for Function 25 to be available, the ICD template version must be higher than 2.1.1 since
the older BCUs did not include this functionality.

Another difference we can see in the menus is that only SCU and SCU-HMI units have the
IED as a Source of SNTP Synchronization sub-menu. And only the HMIs have the HMI
Historical Measurements Restorer sub-menu.
All other options will be shared by all equipment in the saTECH range, IEDs from other
manufacturers will not have Configurable Parameters

Figure 4-108 BCU parameters Configurable Figure 4-109 Configurable BCU Parameters
Options (with TC and TP card) Options (without TC and TP card)
Figure 4-110 Configurable RIO CuFo parameters Figure 4-111 Configurable RIO MES Parameters
Options Options
Figure 4-112 Configurable SCU parameters Figure 4-113 Configurable HMI Parameters
Options Options
4.4.15.1. HMI Historical Measurements Restorer

This option, which is only available for HMIs, allows for backing up the current data of the
HMI history so that an HMI can be restored later with these values (Figure 4-114).
Figure 4-114 HMI Historical Measurements: Generate and Download the backup files

 "Generate and download backup file": It makes a backup with the current data of
the HMI unit and downloads the file to the user selected folder.
 "Restore Configurator": Customize the type of restoration to be performed by the

HMI equipment (Figure 4-115).
Figure 4-115 HMI Historical Restorer Configurator
o "Enable the recovery of historical values": Enabling this option will perform a historical
values retrieval after a configuration load.
 "Back up with current HMI data": saves the historical values of the
equipment in advance.
 "Back up with a downloaded file": the user provides a previously

downloaded file
o "Force HMI name change": If this option is enabled, it will allow to restore historical
values of a different HMI identifier than the current one. We must use this option if we
wish to load the historical values from another HMI or if we have changed the name of
the computer.
o "Consider unit in the measurements recovery": We must select this option if we want to
take into account unit consistency in measurement recovery. If we enable this option,
the measurements whose unit has changed with respect to the backup made will not
be recovered.
o "Consider signal description in the measurements recovery": Select this option if we

want to take into account the consistency of descriptions in the recovery of
measurements. If we enable this option, the measurements whose description has
changed with respect to the backup made will not be recovered.

The restoration depends on a configuration load, so that when we click on the save button
there will be the option to send a configuration to the HMI.
Note: The Send Configuration process will not send data from the restorer, the functionality
will only be available in this window.
4.4.15.2. IED as a Source of SNTP Synchronization

SaTECH's SCU and SCU-HMI equipment can act as SNTP synchronization sources.
From this option we can enable this functionality and configure each of its parameters.
Figure 4-116 Configuring IEDs as an SNTP Synchronization Source
The 'save' button stores the panel data as an IED-specific project configuration.
The 'reload' button loads the default data from the CNF (2.2.4 Default values for
saTECH CNF) on the IED panel; it is necessary to press the 'save' button to store the
values in the project.
IED parameters as a source of SNTP Synchronization:
 Source of SNTP Synchronism: It enables the IED as a source of SNTP

synchronization for the other IEDs in the project.
 Stratum level: The lower value is more accurate (Stratum)
 Force 'Leap Indicator' to accurate time: Force the 'Leap Indicator' to always be
sent with 'No warning.' We will always provide accurate time to 'true', and to
'false', time will be given according to the state of the system synchronization.
 IP address: IP address of the SCU as SNTP server
 Subnet mask: TCP/IP subnet mask of the SCU as SNTP server

 Gateway: SCU Gateway as SNTP server
 Physical Port: Physical port of the SCU ETH port as SNTP server
 Type of redundancy: Different options to configure the SCU communication as a

SNTP server.
 Redundant Physical Port: Redundant Physical Port with ETH-Bonding Port (only
available when selecting the "Bonding" redundancy type)
 PRP Physical Port: Redundant Physical Port with ETH-PRP port (only available
when "PRP" redundancy type is selected)
4.4.15.3. SaTECH Application Update

Makes the connection to the IED to load a new firmware version possible. The functionality
and options available are the same as those seen in the section 2.5.1 Update the
application.
4.4.15.4. TP and TC board configuration

The following option is only available in the equipment with TP and TC boards in order to
be able to adjust them for each separate equipment.
Figure 4-117 'Configurable Parameters for TP and TC Cards' option
When the option is executed we will see the specific values of the selected TP and TC
boards. If there is no expansion card, only the options in the left box will appear.

Figure 4-118 Specific configuration of TP and TC cards
In the drop-down lists, a list will appear with the MOPR functions of the equipment whose
prefix and instance coincide with those of another MBAL function of the equipment, and
which have not been selected for another TP and TC card.
Once an MOPR has been selected, all the configurable parameters of the TP and TC card
will appear.
Figure 4-119 Specific configuration of TP and TC cards

TP and TC board parameters:
 MOPR and MBAL on which to associate the Acquisition: Disable or enable the
generation on the MOPR and MBAL associated with the acquisition.
 Nominal phase voltage, high voltage (V) side: Nominal phase voltage, high
voltage (V-primary) side.
 Nominal phase voltage, low voltage (V) side: Nominal phase voltage, low voltage
(V-primary) (V-primary) side.
 Nominal voltage, synchronization, High voltage (V) side: Nominal voltage,

synchronization channel, high voltage (V-primary) side.
 Nominal voltage, synchronization, Low voltage (V) side: Nominal voltage,

synchronization channel, low voltage (V-primary) side.
 Nominal phase current, high voltage (A) side: Nominal phase current, high voltage
(A) side
 Nominal phase current, low voltage (A) side Nominal phase current, low voltage
(A) side
 Nominal neutral current, High voltage (A) side: Nominal neutral current, high
voltage (A) side
 Nominal neutral current, Low voltage (A) side: Nominal neutral current, Low
voltage (A) side
 Nominal frequency: Nominal frequency
 BCU TP and TC version with Frequency (only shown in administrator mode): BCU
application version for TP and TC Card with Frequency (This property appears
only on the BUS card, if there is an expander card it does not appear on it)

4.4.15.5. Configurable Parameters of the Function 25

This option is only available in equipment with TP and TC cards, and is configured from the
configuration screen of these cards.
Function 25 is associated with the RSYN functions (or logical nodes) of 61850, and
saTECH BCUs with ICD template versions prior to 2.1.1 do not contain the RSYN function.
Therefore, Function 25 will only be available if the BCU has a 2.1.1 ICD template version
or higher. Another prerequisite for the configuration of function 25 is to have the LDevice
mode set to Bay. If the BCU contains TP and TC cards, we want to set up function 25; and,
in the TP and TC part configuration screen, only the option "Disable" appears in the drop
down list of function 25, see section 4.4.15.9 Advanced Properties to see how to set up the
ICD version and LDevice generation mode.
Figure 4-120 ‘Configurable Parameters Function 25' Option
When executing the option we will see the values configured for the function 25 of the
selected TP and TC card.

Figure 4-121 Function 25 Configuration
Function 25 Configuration Parameters for a TP and TC Card:
 Switch to associate Function 25: With this parameter, we can disable the function
25 on this TP and TC card, or select the RSYN associated to a switch in order to
control the function 25 on that switch. Only
RSYNs that have been added in a bay with the
same prefix and instance as a CSWI will appear
in the drop-down list (See figure Figure 4-122
RSYN Association). If an RSYN function is
already being controlled by another TP and TC
card, then it will not appear in the list. Figure 4-122 RSYN Association
 Control Model for Start/Stop: Control model to start and stop the progress of the
synchronization check
 Reference phase.

 Deadline threshold (V-sec): Maximum value to consider that there is no line

voltage (V-secondary).
 Dead bar threshold (V-sec): Maximum value to consider that there is no busbar
voltage (V-secondary.)
 Permission for Substation closing. Live dead mode.
 Permission by Synchronism:
o Time for compliance with conditions (ms): Total time of synchronization

process conditions compliance, time of conditions compliance (ms.)
o Minimum voltage (V-sec): Minimum voltage for real time synchronization

(V-secondary.)
o Angle difference (Ang): Phase angle difference in absolute value (Ang.)
o Voltage difference (V-sec): Voltage difference in absolute value (V-

secondary)
o Frequency difference (Hz): Frequency difference in absolute value (Hz).
4.4.15.6. External Equipment Monitoring

It makes it possible to monitor network equipment (other than 61850) in the system which
may produce communication failures (responding to a ping request), as may be the case
with printers.
From this option, we can configure the network of the external equipment. Optionally, we
can overwrite the equipment's self-generated acronyms. (See Figure 4-123):
 Equipment name: It is the name that will be used for the self-generated acronyms
 IP address
 Network mask
 Gateway
 Behavior: Optional, it offers the possibility of overwriting all the acronyms for this
particular machine.

Figure 4-123 Monitoring of external equipment
4.4.15.7. Communications Identifiers

Configures communications identifiers for an IED. 61850 communications and other
protocol communications as well.
Figure 4-124 Communication Identifiers

The 'reload' button replaces the modified values with the current values of the IED
communications identifiers.
The identifiers are grouped by the type of communication. Thus, we have the following
groups:
 Identifiers for Slave Profiles: The identifier of each slave protocol will be used to
form the name of the protocol, the SubNetwork and the ConnectedAP. So, for
example, if one of the DNP3-IP slave protocols were to have its identifier changed
to 7, the protocol would be called DNP3-IP_7. In addition, a SubNetwork with
name SDNP_7, a ConnectedAP with apName SDNP_7, an AccessPoint with
name "SDNP_7" and an ITCI logical node with inst="7" and
lnType="ITCI_DNP3_ASG_7" would be formed in the CID to monitor
communications through this protocol.
Figure 4-125 Details of the Slave Profile Identifier
 Identifiers for External Equipment Monitoring: The configuration of the ICD

external equipment monitoring is done through an ITMI logical node. The number
we associate as an identifier to each External Equipment will generate the
instance number (inst) in the CID of the corresponding ITMI logical node and it will
also be used to form the IEDName of the external equipment in the CID. For
example, if the identifier 12 is configured, the IEDName in the CID for that external
equipment will be EE012.
 Identifiers for Master Profiles: The identifier of each master protocol will be used to
form the name of the protocol and the SubNetwork. So, for example, if one of the
DNP3-IP slave protocols were to have its identifier changed to 8, the protocol

would be called DNP3-IP_8. In addition, in the CID, a SubNetwork would be

formed with the name CDNP_8.
Figure 4-126 Details of the Master Profile Identifier
 Master Profile Slave Equipment Identifiers: For each master profile, in addition to
its identifier, we can also configure the identifier of each of the slave devices in
that profile. For each slave equipment, a ConnectedAP will be generated within
the corresponding SubNetwork, and the IEDName of said ConnectedAP will be
formed by a protocol type dependent prefix, followed by three digits (including
zeros) and the slave device identifier. For example, if the protocol is DNP3 and
the identifier is 11, the ConnectedAP IEDName will be DNP011. The slave
equipment also allows for the generation of a GGIO logical node within the
"GENERAL" logical device, the inst of this logical node will be the identifier that we
configure.
 Identifiers for 61850 Communication: For each IED to which we subscribe (either
gooses or reports) in the CID, an LDES logical node is generated, with information
on the connectivity with that IED. The identifier we configure in this screen for
each IED will be used as the value of the inst attribute of said LDES.
 LGOS Identifiers: For each Goose to which we are subscribed, an LGOS logical
node is generated in the CID, with information about the connectivity through that
Goose. The identifier that we configure in this screen for each GOOSE will be
used as the value of the inst attribute of that LGOS.

4.4.15.8. Self-Generated Signals

Configures signal acronyms that will be automatically generated when the CID
configuration file is generated.
Figure 4-127 Self-Generated BCU Signals
The 'reload' button replaces the IED values in the graphic interface with those
configured for the equipment model in the 2.2.4.2 Self-generated signals option.
Clicking on the 'more' button will display the Acronyms configuration panel, to configure
the behavior of the signals in the system display windows. This panel is explained in the
Acronym Column section of the IED Signal Editor.
The self-generated signals depend on the equipment model. And they have been grouped
into the following blocks:
 Local/Remote equipment signals.
Figure 4-128 Local/Remote equipment signals

Parameter Description Default value of the acronym IED
SCU
D:LOCAL REMOTE %s (LOCAL);
Equipment Local/Remote IED 'Loc' HMI
Equipment Local A1:LOCAL;A0:REMOTE;OC:LOCAL;OO:RE
GENERAL BCU
MOTE;AL1;EV0;EV1;EVOK;EVFA
RIO
D:LOCAL REMOTE %s (LOCAL PHYSICAL SCU

Physical Equipment Local/Remote with IED Physical Key KEY); HMI
Key 'LocKey' GENERAL A1:LOCAL;A0:REMOTE;OC:LOCAL;OO:RE BCU
MOTE;AL1;EV0;EV1;EVOR;EVOK;EVFA RIO
D:LOCAL REMOTE %s (LOCAL SCU

Substation Level Local/Remote IED SUBSTATION LEVEL); HMI
Substation Level
'LocSta' GENERAL A1:LOCAL;A0:REMOTE;OC:LOCAL;OO:RE BCU
MOTE;AL1;EV0;EV1;EVOR;EVOK;EVFA RIO
 Signals internal to the equipment.
Figure 4-129 Signals internal to the equipment

D:OPERATING MODE %s;

Operation Mode of the A0:UNKNOWN;A1:ACTIVE;A2:PASSIVE;A
IED GENERAL operation mode SCU
Equipment 3:TEST;A4:TEST/BLOCKED;A5:OFF;EV0;E
V1;EV2;EV3;EV4;EV5
SCU
D:ETHERNET PORT STATUS LAN %s; HMI
Ethernet Port Status Ethernet status
A0:FAIL;A1:NORMAL;AL0;EV0;EV1 BCU
RIO
D:ETHERNET PORT STATUS LAN %s

Dual Ethernet Port
Dual Ethernet Port Status OTHER UCS; SCU
Status
A0:FAIL;A1:NORMAL;AL0;EV0;EV1
SCU
D:SERIAL PORT STATUS %s; HMI
Serial Port Status Serial Port Status
A0:NORMAL;A1:FAIL BCU
RIO
Failure on the D:BOARD FAILURE - LEVEL %s OF %s; BCU

Failure on the X Acquisition LEVEL
Acquisition LEVEL A0:DISABLED;A1:ENABLED;EV0;EV1;AL1 RIO
D:M8-CPU LINK ALARM %s;

M8-CPU Link Alarm M8-CPU Link Alarm SCU
A0:FAIL;A1:NORMAL;EV0;EV1;AL0
D:POWER SUPPLY STATUS 1 %s; SCU

Power Supply 1 Status Power Supply 1 Status
A0:NORMAL;A1:FAIL;EV0;EV1;AL1 BCU
D:POWER SUPPLY STATUS 2 %s; SCU

Power Supply 2 Status Power Supply 2 Status
A0:NORMAL;A1:FAIL;EV0;EV1;AL1 BCU
SCU
CPU Consumption Value for CPU Consumption D:CPU CONSUMPTION %s HMI
BCU
SCU
CPU Consumption D:CPU CONSUMPTION ALARM %s;
CPU Consumption Alarm HMI
Alarm A0:NORMAL;A1:FAIL;EV0;EV1;AL1
BCU
SCU
CPU Temperature Value for CPU Temperature D:CPU TEMPERATURE %s HMI
BCU
SCU
CPU Temperature D:CPU TEMPERATURE ALARM %s;
CPU Temperature Alarm HMI
BCU
SCU
Memory Consumption Value for Memory Consumption D:MEMORY CONSUMPTION %s HMI
BCU

SCU
Memory Consumption D:MEMORY CONSUMPTION ALARM %s;
Memory Consumption Alarm HMI
BCU
SCU
Disk Consumption D:DISK CONSUMPTION ALARM %s;
Hard Disk Consumption Alarm HMI
BCU
SCU
D:DISK CORRUPTION ALARM %s;
Disk Corruption Alarm Hard Drive Corruption Alarm HMI
A0:NORMAL;A1:FAIL;EV0;EV1;AL1
BCU
Database Corruption D:DATABASE CORRUPTION ALARM %s; SCU

Database Corruption Alarm
Alarm A0:NORMAL;A1:FAIL;EV0;EV1;AL1 HMI
D:RAID ALARM %s; SCU

RAID Alarm RAID Alarm
A0:NORMAL;A1:FAIL;EV0;EV1;AL1 HMI
D:PROCESS ALARM %s; SCU

Process Alarm Process Alarm
A0:NORMAL;A1:FAIL;EV0;EV1;AL1 HMI
 Higher Levels
Figure 4-130 Higher Levels

SCU
Internal Command D:INTERNAL COMMAND REQUEST; HMI
Internal Command Request
Request A1:REQUESTED;EV1 BCU
RIO
SCU
PLC Command D:COMMAND REQUEST PLC; HMI
PLC Command Request
Request A1:REQUESTED;EV1 BCU
RIO
SCU
Command Request D:COMMAND REQUEST FROM SCU1; HMI
Command Request from SCU1
from SCU1 A1:REQUESTED;EV1 BCU
RIO
SCU
Command Request D:COMMAND REQUEST FROM SCU2; HMI
Command Request from SCU2
from SCU2 A1:REQUESTED;EV1 BCU
RIO
SCU
Command Request D:COMMAND REQUEST FROM HMI1; HMI
Command Request from HMI1
from HMI1 A1:REQUESTED;EV1 BCU
RIO
SCU
RIO
SCU
RIO
Bay System Disconnection (D:BAY

D:BAY SYSTEM DISCONNECTION %s;
SYSTEM DISCONNECTION
Bay System A0:DISABLED;A1:ENBALED;OC:START;O SCU
%s;A0:DISABLED;A1:ENABLED;OC
Disconnection O:FINISH;EV0;EV1;EVOR;EVOK;EVFA;AL HMI
:START;OO:FINISH;EV0;EV1;EVOK
FA
;EVFA;ALFA)
Communication failure with Master

Communication Failure D:FAILURE TO COMMUNICATE %s; SCU
Equipment, control centers, in
with Master Equipment A0:NORMAL;A1:FAIL;EV0;EV1;AL1 BCU
conventional protocol
Communication Communication channel with Master

D:COMMUNICATION WITH %s VIA SCU
channel with Master Equipment, control centers, in
CHANNEL; A0:MAIN;A1:SECONDARY BCU
Equipment conventional protocol
Request for Command from Master

Command from Master D:REQUEST FOR COMMAND FROM %s; SCU
Equipment, control centers, in
Equipment Request A1:REQUESTED;EV1; BCU
conventional protocol

 61850 Communication
Figure 4-131 61850 Communication
IP connectivity with IP connectivity with IED-61850 D:IP CONNECTIVITY FAILURE %s; SCU
IED-61850 Failure Failure A1:FAIL;A0:NORMAL;AL1;EV0;EV1 HMI
Connectivity Failure MMS connectivity failure with IED- D: MMS CONNECTIVITY FAILURE%s; SCU
REPORTS 61850 A1:FAIL;A0:NORMAL;AL1;EV0;EV1 HMI
Subscription to Failure to subscribe to REPORTS D:REPORTS SUBSCRIPTION FAILURE SCU

REPORTS Failure with IED-61850 equipment %s; A1:FAIL;A0:NORMAL;AL1;EV0;EV1 HMI
Counter for failed

communication Counter for failed communication
D:COMMUNICATION ATTEMPT SCU
attempts via Channel 1 attempts via Channel 1 with IED-
COUNTER V1 WITH %s HMI
with IED-61850 61850 equipment
equipment
Counter for failed

D:COMMUNICATION ATTEMPT SCU
equipment
Counter for failed

D:FAILED COMMUNICATION ATTEMPT SCU
equipment
Counter for failed

D:FAILED COMMUNICATION ATTEMPT SCU
equipment

Subscription to Failure to subscribe to GOOSES with D:GOOSE SUBSCRIPTION FAILURE %s; BCU
GOOSES Failure IED-61850 equipment A1:FAIL;A0:NORMAL;AL1;EV0;EV1 RIO
D:NEGOTIATION REQUIRED IN
Negotiation required in Negotiation required in Goose BCU
SUBSCRIPTION TO IED %s GOOSE %s;
Goose subscription subscription RIO
A1:FAIL;A0:NORMAL;AL1;EV0;EV1
Goose subscription D:IED SUBSCRIPTION %s GOOSE %s; BCU

Goose subscription status
status A1:FAIL;A0:NORMAL;AL1;EV0;EV1 RIO
Simulated messages D:SIMULATED IED MESSAGES %s

Simulated messages are received BCU
are received and GOOSE %s RECEIVED AND ACCEPTED;
and accepted RIO
accepted A1:YES;A0:NO;AL1;EV0;EV1
 Acquisition Level
Figure 4-132 Acquisition Level
SCU
Communication failure Communication failure with RTU in D:FAILURE TO COMMUNICATE %s;
HMI
with slave equipment conventional protocol E:%s;A0:FAIL;A1:NORMAL;AL0;EV0;EV1
BCU

SCU
Communication with
Communication failure with D:FAILURE TO COMMUNICATE %s; HMI
External Equipment
external TCP/IP equipment E:%s;A0:NORMAL;A1:FAIL;AL1;EV0;EV1 BCU
Failed
RIO
SCU
Protocol Failure with Master Protocol Failure with RTU D:FAILURE TO COMMUNICATE %s;
HMI
Slave Equipment in conventional protocol E:%s;A0:FAIL;A1:NORMAL;AL0;EV0;EV1
BCU
Local/Remote Status with RTU SCU

Local/Remote with D:LOCAL REMOTE %s;
Slave Equipment in conventional HMI
Slave Equipment A0:LOCAL;A1:REMOTE;AL0;EV0;EV1
protocol BCU
Communication Communication channel with RTU D:COMMUNICATION WITH %s VIA SCU

channel with slave slave equipment in conventional CHANNEL; HMI
equipment protocol A0:MAIN;A1:SECONDARY;EV0;EV1 BCU
Counter for
Counter for communication SCU
communication D:COMMUNICATION ATTEMPT COUNTER
attempts via Channel 1 with Slave HMI
attempts via Channel 1 V1 WITH %s
equipment BCU
with Slave equipment
Counter for failed

communication Counter for failed communication SCU
D:COMMUNICATION ATTEMPT COUNTER
attempts via Channel 2 attempts via Channel 2 with IED- HMI
V2 WITH %s
with IED-61850 61850 equipment BCU
equipment
Counter for failed

D:FAILED COMMUNICATION ATTEMPT
COUNTER V1 WITH %s
equipment
Counter for failed

D:FAILED COMMUNICATION ATTEMPT
COUNTER V2 WITH %s
equipment
Digital inputs of the

Hardware failure in the digital D:HARDWARE FAILURE OF DIGITAL SCU
SAP20 Slave
inputs of the RTU-SAP20 slave INPUTS %s; HMI
Equipment Hardware
equipment in conventional protocol A0:NORMAL;A1:FAIL;AL0;EV0;EV1 BCU
failure
Digital Outputs of
Hardware failure in the Digital D:HARDWARE FAILURE OF DIGITAL SCU
SAP20 Slave
Outputs of the RTU-SAP20 Slave OUTPUTS %s; HMI
Equipment Hardware
Equipment in conventional protocol A0:NORMAL;A1:FAIL;AL0;EV0;EV1 BCU
Failure
Analog inputs of the

Hardware failure in the analog D:HARDWARE FAILURE OF ANALOGUE SCU
SAP20 Slave
inputs of the RTU-SAP20 slave INPUTS %s; HMI
Equipment Hardware
equipment in conventional protocol A0:NORMAL;A1:FAIL;AL0;EV0;EV1 BCU
failure
 Measurements of Analog TP and TC Card(s)

Figure 4-133 Analog TP and TC Card(s) Measurements

Three-phase active P3 - Three-phase active power D:P3 - THREE-PHASE ACTIVE POWER BCU
power (TotW) (TotW) on level with TP/TC (TotW) - LEVEL %s OF %s
Three Phase Reactive Q3 - Three-Phase Reactive Power D:Q3 - THREE-PHASE REACTIVE POWER
BCU
Power (TotVAr) (TotVAr) on Level with TP/TC (TotVAr) - LEVEL %s OF %s
Three-phase Apparent S3 - Three-phase Apparent Power D:S3 - APPARENT THREE-PHASE

BCU
Power (TotVA) (TotVA) on Level with TP/TC POWER (TotVA) - LEVEL %s OF %s
Three-phase Power FP3 - Three-phase Power Factor D:FP3 - THREE-PHASE POWER FACTOR
BCU
Factor (TotPF) (TotPF) on Level with TP/TC (TotPF) - LEVEL %s OF %s
Line Side Frequency LINFR - Line SideFrequency (LinHz) D:LINFR - LINE SIDE FREQUENCY (LinHz)
BCU
(LinHz) on Level with TP/TC - LEVEL %s OF %s
Bar Side Frequency BARFR - Bar Side Frequency D:BARFR - BAR SIDE FREQUENCY
BCU
(BarHz) (BarHz) on Level with TP/TC (BarHz) - LEVEL %s OF %s
Voltage Between AB VABM - AB Interphase Voltage D:VABM - PHASE AB VOLTAGE

BCU
Phases (PPV.phsAB) (PPV.phsAB) on Level with TP/TC (PPV.phsAB) - LEVEL %s OF %s
Voltage Between BC VBCM - BC Interphase Voltage D:VBCM - BC INTERPHASE VOLTAGE

BCU
Phases (PPV.phsBC) (PPV.phsBC) on Level with TP/TC (PPV.phsBC) - LEVEL %s OF %s
D:VCAM - AC INTERPHASE VOLTAGE

VCAM - Voltage Between AC (PPV.phsCA) - LEVEL %s OF %s
Voltage Between AC
Phases (PPV.phsCA) on Level with BCU
Phases (PPV.phsCA)
TP/TC
Phase A voltage VAM - Phase A Voltage (PhV.phsA) D:VAM - PHASE A VOLTAGE (PhV.phsA) -
BCU
(PhV.phsA) on Level with TP/TC LEVEL %s OF %s
Phase B voltage VBM - Phase B voltage (PhV.phsB) D:VBM - PHASE B VOLTAGE (PhV.phsB) -
BCU
(PhV.phsB) on Level with TP/TC LEVEL %s OF %s
Phase C voltage VCM - Phase C Voltage (PhV.phsC) D:VCM - PHASE C VOLTAGE (PhV.phsC) -
BCU
(PhV.phsC) on Level with TP/TC LEVEL %s OF %s
Phase S voltage VSM - Phase S Voltage (PhV.phsS) D:VSM - PHASE S VOLTAGE (PhV.phsS) -
BCU
(PhV.phsS) on Level with TP/TC LEVEL %s OF %s

Neutral voltage VNM - Neutral Voltage (PhV.neut) on D:VNM - NEUTRAL VOLTAGE (PhV.neut) -
BCU
(PhV.neut) Level with TP/TC LEVEL %s OF %s
Net Current Voltage VGM - Net Current Voltage (PhV.net) D:VGM - NET CURRENT VOLTAGE
BCU
(PhV.net) on Level with TP/TC (PhV.net) - LEVEL %s OF %s
Phase A Current IAM - Phase A Current (A.phsA) on D:YAM - PHASE A CURRENT (A.phsA) -
BCU
(A.phsA) Level with TP/TC LEVEL %s OF %s
Phase B current IBM - Phase B Current (A.phsB) on D:IBM - PHASE B CURRENT (A.phsB) -
BCU
(A.phsB) Level with TP/TC LEVEL %s OF %s
Phase C Current ICM - Phase C Current (A.phsC) on D:ICM - PHASE C CURRENT (A.phsC) -
BCU
(A.phsC) Level with TP/TC LEVELS %s OF %s
Neutral Current INM - Neutral Current (A.neut) on D:INM - NEUTRAL CURRENT (A.neut) -
BCU
(A.neut) Level with TP/TC LEVEL %s OF %s
IGM - Net Current (A.net) on Level D:IGM - NET CURRENT (A.net) - LEVELS
Net Current (A.net) BCU
with TP/TC %s OF %s
Phase A Active Power Pa - Active Power Phase A (W.phsA) D:Pa - ACTIVE POWER PHASE A
BCU
(W.phsA) on Level with TP/TC (W.phsA) - LEVEL %s OF %s
Phase B Active Power Pb - Active Power Phase B (W.phsB) D:Pb - PHASE B ACTIVE POWER
BCU
(W.phsB) on Level with TP/TC (W.phsB) - LEVEL %s OF %s
Phase C Active Power Pc - Active Power Phase C (W.phsC) D:Pc - PHASE C ACTIVE POWER
BCU
(W.phsC) on Level with TP/TC (W.phsC) - LEVEL %s OF %s
Phase A Reactive Qa - Reactive Power Phase A D:Qa - PHASE A REACTIVE POWER

BCU
Power (VAr.phsA) (VAr.phsA) on Level with TP/TC (VAR.phsA) - LEVEL %s OF %s
Phase B Reactive Qb - Reactive Power Phase B D:Qb - PHASE B REACTIVE POWER

BCU
Power (VAr.phsB) (VAr.phsB) on Level with TP/TC (VAR.phsB) - LEVEL %s OF %s
Phase C Reactive Qc - Phase C Reactive Power D:Qc - PHASE C REACTIVE POWER

BCU
Power (VAr.phsC) (VAr.phsC) on Level with TP/TC (VAR.phsC) - LEVELS %s OF %s

Phase A Apparent Sa - Apparent Power Phase A D:Sa - APPARENT POWER PHASE A

BCU
Power (VA.phsA) (VA.phsA) on Level with TP/TC (VA.phsA) - LEVEL %s OF %s
Phase B Apparent Sb - Apparent Power Phase B D:Sb - APPEARENT POWER PHASE B

BCU
Power (VA.phsB) (VA.phsB) on Level with TP/TC (VA.phsB) - LEVEL %s OF %s
Phase C Apparent Sc - Apparent Power Phase C D:Sc - APPARENT POWER PHASE C

BCU
Power (VA.phsC) (VA.phsC) on Level with TP/TC (VA.phsC) - LEVEL %s OF %s
Phase A Power Factor Fpa - Power Factor Phase A D:Fpa - PHASE A POWER FACTOR
BCU
(PF.phsA) (PF.phsA) on Level with TP/TC (PF.phsA) - LEVEL %s OF %s
Phase B Power Factor Fpb - Power Factor Phase B D:Fpb - PHASE B POWER FACTOR
BCU
(PF.phsB) (PF.phsB) on Level with TP/TC (PF.phsB) - LEVEL %s OF %s
Phase C Power Factor Fpc - Phase C Power Factor D:Fpc - PHASE C POWER FACTOR
BCU
(PF.phsC) (PF.phsC) on Level with TP/TC (PF.phsC) - LEVEL %s OF %s
Total Apparent Energy VAhTot - Total Apparent Energy D:VAhTot - TOTAL APPARENT ENERGY
BCU
(TotVAh) (TotVAh) on Level with TP/TC (TotVAh) - LEVEL %s OF %s
Total Reactive Energy VArhTot - Total Reactive Energy D:VArhTot - TOTAL REACTIVE ENERGY
BCU
(TotVArh) (TotVArh) on Level with TP/TC (TotVArh) - LEVEL %s OF %s
Total Active Energy WhTot - Total Active Energy (TotWh) D:WhTot - TOTAL ACTIVE ENERGY
BCU
(TotWh) on Level with TP/TC (TotWh) - LEVEL %s OF %s
Active Energy WhIn - Active Energy Delivered D:WhIn - ACTIVE ENERGY DELIVERED
BCU
Delivered (SupWh) (SupWh) on Level with TP/TC (SupWh) - LEVEL %s OF %s
Active Energy WhOut - Active Energy Received D:WhOut - ACTIVE ENERGY RECEIVED
BCU
Received (DmdWh) (DmdWh) on Level with TP/TC (DmdWh) - LEVEL %s OF %s
Reactive Energy VArhIn - Reactive Energy Delivered D:VArhIn - REACTIVE ENERGY

BCU
Delivered (SupVArh) (SupVArh) on Level with TP/TC DELIVERED (SupVArh) - LEVEL %s OF %s
Reactive Energy VArhOut - Reactive Energy Received D:VArhOut - REACTIVE ENERGY

BCU
Received (DmdVArh) (DmdVArh) on Level with TP/TC RECEIVED (DmdVArh) - LEVEL %s OF %s

 RSYN Function 25
Figure 4-134 RSYN Function 25
Start and Stop

Start and Stop Synchronization Check D:SYNCHROCHECK - LEVEL %s OF
Synchronization
Progress (Function 25 Synchrocheck) %s;A0:STOP;A1:START;OC:START;OO:ST BCU
Check Progress
(SynPrg) on Level with TP/TC OP;AL0;EV0;EV1;EVOR;EVOK;EVFA
(SynPrg)
Lock Release (Function 25 D:SYNCROCHECK - LEVEL %s OF

Lock Release (Rel) Synchrocheck) (Rel) on Level with %s;A0:LOCK;A1:PERMISSION;AL0;EV0;E BCU
TP/TC V1
D:VOLTAGE DIFFERENCE - LEVEL %s

Voltage Difference Voltage Difference (VInd) on Level with
OF BCU
(VInd) TP/TC
%s;A0:NORMAL;A1:ALARM;AL0;EV0;EV1
D:FREQUENCY DIFFERENCE - LEVEL %s

Frequency Frequency Difference (HzInd) on Level
OF BCU
Difference (HzInd) with TP/TC
%s;A0:NORMAL;A1:ALARM;AL0;EV0;EV1
Angle Difference Angle Difference (AngInd) on Level with D:ANGLE DIFFERENCE - LEVEL %s OF
BCU
(AngInd) TP/TC %s;A0:NORMAL;A1:ALARM;AL0;EV0;EV1
Calculated
Calculated Difference in Voltage D:CALCULATED VOLTAGE DIFFERENCE
Difference in BCU
(DifVClc) on Level with TP/TC - LEVEL %s OF %s
Voltage (DifVClc)

Calculated
Difference in Calculated Difference in Frequency D:CALCULATED FREQUENCY
BCU
Frequency (DifHzClc) on Level with TP/TC DIFFERENCE - LEVEL %s OF %s
(DifHzClc)
Calculated Phase
Calculated Phase Angle Difference D:CALCULATED DIFFERENCE IN PHASE
Angle Difference BCU
(DifAngClc) on Level with TP/TC ANGLE - LEVEL %s OF %s
(DifAngClc)
Average voltage on
Average Voltage on the Busbar Side of D:AVERAGE VOLTAGE ON THE BAR
the side of the BCU
the Switch (V1Clc) on Level with TP/TC SIDE OF THE SWITCH - LEVEL %s OF %s
switch bar (V1Clc)
Average voltage on
Average Voltage on the Line Side of the D:AVERAGE VOLTAGE ON THE SIDE OF
the line side of the BCU
Switch (V2Clc) on Level with TP/TC THE SWITCH LINE - LEVEL %s OF %s
switch (V2Clc)
Average Frequency
on the Busbar Side Switch Bar Side Medium Frequency D:AVERAGE FREQUENCY ON THE BAR
BCU
of the Switch (Hz1Clc) on Level with PT/TC SIDE OF THE SWITCH - LEVEL %s OF %s
(Hz1Clc)
Switch Line Side

Switch Line Side Medium Frequency D:AVERAGE FREQUENCY ON THE SIDE
Medium Frequency BCU
(Hz2Clc) on Level with PT/TC OF THE SWITCH LINE - LEVEL %s OF %s
(Hz2Clc)
4.4.15.9. Advanced Properties

Makes it possible to configure the Advanced Properties of the IED. These options are
different depending on the IED model.
In the case of a BCU they are:
 ICD file version: This option displays a drop-down list with the versions of ICD files
available in the project, so that the user can decide from which of them they want
the BCU CID to be generated.
 'Local/Remote' functionality at Substation level: Inhibited control from higher

substation levels with 'LocSta'.
 Generation of one LDevice per bay or one LDevice per function: Generation of an
LDevice for each bay in which the IED is located, or generation of an LDevice for
each function that the IED implements in a bay.

 CID generation according to IEC-61850, 2007-B edition (only available in

administrator mode): Generation of CID with 2007-B IEC-61850 standard
attributes, otherwise a warning will appear.
 Add Traceability of 'Analog Controls' in DataSet (only available in administrator

mode): Generate the CID with the 'GENERAL' DataSet modified to add the
Traceability of 'Analog Commands', otherwise a warning will be displayed.
 Force 'Internal Commands' as self-generated signals (only available in

administrator mode): The CID will be generated with the internal alarms by
command request, without the need to update templates. If they already exist in
templates, this configuration will be ignored, otherwise a warning will be displayed.
See 4.4.15.8 Self-Generated Signals
 Force templates to use 'Percentage of Variation to generate Alarm': Without the

need to update templates, the CID will include the possibility to configure a
percentage in the 'asgPerChg' analog parameterization, so that a variation higher
than this percentage between two consecutive readings generates an alarm. If
they already exist in templates, this configuration will be ignored, otherwise a
warning will be displayed.
 Force the new 'Hardware Alarms' as self-generated signals (only available in

administrator mode): Without the need to update templates, the CID will be
generated with the new hardware alarms.
 Maximum number of records per DataSet: Maximum number of records (FCDA

'Functional Constrained Data Attribute') per DataSet, Published and Subscribed,
supported by the equipment.
In the case of a RIO equipment they are:
 ICD file version: This option displays a drop-down list with the versions of ICD files
available in the project, so that the user can decide from which of them they wants
the CID of the RIO equipment to be generated.




generated with the internal alarms by command request. If they already exist in


In the case of a UCS they are:
 ICD file version: This option shows a drop-down list with the versions of ICD files
available in the project, so the user can decide from which of them they want the
UCS CID to be generated.





 Force the new 'Hardware Alarms' as self-generated signals Without the need to
update templates, the CID will be generated with the new hardware alarms. If they
already exist in templates, this configuration will be ignored, otherwise a warning
will be displayed. See 4.4.15.8 Self-Generated Signals

 Subscription to all Reports: Subscription to all of the project ReportControls

In the case of a UCS-HMI they are:
UCS-HMI CID to be generated.





 Force the new 'Hardware Alarms' as self-generated signals (only available in

generated with the new hardware alarms. If they already exist in templates, this
configuration will be ignored, otherwise a warning will be displayed. See 4.4.15.8
Self-Generated Signals

 Horn activation by default: Enable or disable the general horn warning.


In the case of an HMI they are:
HMI CID to be generated.



 Force the new 'Hardware Alarms' as self-generated signals Without the need to
update templates, the CID will be generated with the new hardware alarms. If they
already exist in templates, this configuration will be ignored, otherwise a warning
will be displayed. See 4.4.15.8 Self-Generated Signals


 Horn activation by default: Enable or disable the general horn warning.

4.5. Add IED without Bay

From the IED Panel, we can add an IED to the project without associating it to a bay. When
what we want to add is a substation IED instead of a bay IED, this option is more
appropriate than adding it from the Project panel (See 3.3 Adding IED)
To add an IED to the project without associating it to a bay, we must right click on the root
element ("IEDs" IED Group) of the IED Panel. As we can see in the following figure:
Figure 4-135 Add IED without a bay
A wizard will appear, similar to the one that appears when adding a function from the
Project panel, but without the screen for adding functions, since these are associated to an
IED in a particular Bay.
4.6. Removing IED and logic functions

By right-clicking on the name of the IED, or the Logic Function, a menu is displayed with the
corresponding delete option as shown in the Figure 4-136 Removing IED and project logic
functions.
Figure 4-136 Removing IED and project logic functions

4.1. IEC-61850 Signal Tree

In the application, it is common to configure the signals as 61850 references by means of a tree
window as shown in the Figure 4-137.
The structure is formed by the IED configuration and subscriptions. Within 'IEDs', the IED is
displayed, and then its LD ('Logical Device' configured as a logical device) - each LD has its
own logical nodes - and in the following levels, the DOs ('Data Objects') - nests for complex
data (SDIs) - and lastly, the DAs ('Data Attributes') are displayed.
The subscribed signals will appear as Other IED signals. The main IED will always be the first
IED in the tree, but it will only show those references subscribed through Report or Goose.
In the signals, DO of the tree, we will find a text in blue, corresponding to the description of the
signal. The description will be obtained from the ICD templates and therefore, it can vary
depending on the version of the ICD or the project language. Finally, they are overwritten
based on the configuration of the signal acronym 'D', whether it be self-generated or based on
the configuration of the IED signal file.

The subscribed signals will

appear as Other IED signals. The
main IED will always be the first
IED in the tree, but it will only
show those references
subscribed through Report or
Goose.
In the signals, DO of the tree, we

will find a text in blue,
corresponding to the description
of the signal. The description will
be obtained from the ICD
templates and therefore, it can
vary depending on the version of
the ICD or the project language.
Finally, they are overwritten
based on the configuration of the
signal acronym 'D', whether it be
self-generated or based on the
configuration of the IED signal
file.
Figure 4-137 IEC-61850 Signal Tree
The bottom form has a 'Description' field that will be filled in when selecting the signal from the
tree. The color 'green' indicates that there is no selection or that the 61850 reference is not in
the signal tree of the main IED.
In the multi-device IED configurations, such as dual UCS or HMIs, we will be able to choose the
exact name of the device or its 'dual' name by selecting the purple-colored text, or from the 'IED
option' in the bottom form list.
The form below adds filters to search, in order to find references more easily:
 'Common Data Class' filter: types of 'Data Objects' useful to differentiate status,
command, measurement or complex measurement signals. For more information, see
7-3 of IEC-61850 standard, 2-2007B edition, document.

 'Functional Group' filter: types of the 'Data Attribute', useful in differentiating the attribute
with status, measurement and configuration value. For more information, see 7-2 of
IEC-61850 standard, 2-2007B edition, document.
The Figure 4-137 IEC-61850 Signal Tree can change its appearance and functionality
depending on the module to be configured. For example, for the configuration of the IED Signal
Editor, it implements a filter onto the signal tree, to show only those references of the 'Logical
Device' corresponding to the 'Logical Device' column.

MODELING OF ELEMENTS
Chapter 5. Modeling of elements
The MICS document that certifies the data model according to the 2 – 2007-B edition of the IEC
61850 standard:
MICS_ServerIEC618
50_ed2_2007B.pdf

5.1. Modeling of the acquisition board (I/O)

A template is defined for each level in the IED ICD. The name is generated with the
following format:
 xxGGIOx, where xx corresponds to the card codes that compose the level.
The following Data objects (DO) are defined:
o NamPlt
o Beh
o Health
o ASGFailCom: Indication of communication failure with the level, through
the bus.
o ASGFailRel: Selection relay failure indication.
o ASGFailFPGA: FPGA failure indication.
o An 'Indn' for each input, where 'n' is the level’s digital input number
o For digital output cards:
o An 'SPCSOn' for each output, where 'n' is the level's digital output
number.
o For analog input cards:
o An 'AnInX' for each input, where 'X' is the level’s analog input number.
5.2. Modeling of the logical functions

The logical functions are represented in structured language, following the IEC-61131
standard. Each logic function is entered into the Logical Node (LN) where the DO
belongs, DO to which we wish to assign the result of the logic function.
For this purpose, two new CDCs are used, in those LNs where logic functions are to be
introduced:
 "Data objects" (DO) of type 'Logic Function', of the class (CDC) "Visible String
Setting" (VSG). The formula is included in this DO.
 "Data objects" (DO) of type 'InRef', of the class (CDC) "Object Reference
Setting" (ORG) to transfer data to the LN where the formula is determined.
An InRef is declared for each term in the formula.

5.3. Modeling of slave equipment

A template is defined in the IED CID for each model of slave equipment registered in the
Configuration Tool.
The name is generated with the following format:
 MMMM_GGIO, where MMMM is the equipment model (entered by the user when
registering the equipment model.)
The following DOs are defined:
o Beh
o Health
o ASGDir: Physical address of the equipment.
o ASGTestPoll: Retrograde test mode interrogations counter (GNF functionality.
Confirm if it is to be used in Mexico)
o ASGRTURspnde: RTU responds.
o ASGConLocal2: Equipment communicating via secondary channels.
o ASGErrorProt: Protocol error.
o CntRs1: Primary communication attempt counter.
o CntRs2: Secondary communication attempt counter.
o CntRs3: Counter for failed communication attempts via primary channels.
o CntRs4: Counter for failed communication attempts via secondary channels.
o Lockey: 1- local (remote control not accepted), 0- remote control accepted
o An 'Indn' for each input served by the RTU, where 'n' is the equipment's digital
input number (sequential).
o An 'SPCSOn' for each output served by the RTU, where 'n' is the equipment’s
digital output number (sequential).
o One 'AnInn' for each analog input, where 'n' is the number of the equipment’s
analog input (sequential).
o A 'CntRsn' for each pulse counter, where 'n' is the counter equipment’s input
number (sequential), starting with 5 (the first 4 are reserved for
communications statistics.)
5.4. Publication of gooses

The publication parameters for each goose are defined in the 'Subnetwork' section for the
IEC-61850 protocol, in the 'ConnectedAp' corresponding to the equipment.

For example:
<GSEcbName="GSEEDO1"ldInst="GENERAL">
<Address>
000
0
01-0C-CD-01-00-A1
1000
</Address>
<MinTime multiplier="m" unit="s">1</MinTime>
<MaxTime multiplier="m" unit="s">2000</MaxTime>
</GSE>
In the LL0 of the LD 'GENERAL' the GSE Control Block is declared, with the APPID
entered by the user.
For example:
<GSEControl appID="SAS" confRev="1" datSet="GOOSE" desc="Salida de GOOSE1"

name="GSEEDO1" type="GOOSE"/>
5.5. Hardware anomalies modeling

The following hardware anomalies are modeled:
5.5.1. Serial port failures

A DO is defined in the LD 'GENERAL' LPHD LN in order to monitor the failure of each
serial port defined in the equipment model to which the CID corresponds. The name of
each DO (CDC SPS) is created with the following rule:
- ASGFallRSPn, where 'n' is the physical port number of the equipment
5.5.2. Ethernet anomalies

Ethernet anomalies are monitored by the LN LCCH, indicating whether or not there is
a link on each of its ports.

An LN of class LCCH is defined for each physical Ethernet port determined in the
equipment model to which the CID corresponds. The LN instance indicates the
number of the physical Ethernet port it monitors.
The equipment has 3 Ethernet ports, although, at configuration and application level,
two of them behave as one. In this case, 3 LN LCCH are defined, since it is possible to
detect the link individually for each of the physical ports.
5.5.3. I/O board failure (grouped into levels)

GGIO LN with INOUT_ or DIRCAP_ prefix are defined within the 'GENERAL' LD; the
following DOs are used to indicate card failure:
- The failure of communication via the bus with each level is monitored in the OJ
'ASGComFail', defined in each template associated with a level.
- The selection relay failure of each level is monitored in the 'ASGSelFail' DO,
defined in each template associated to a level.
- The FPGA failure of each level is monitored in the 'ASGFPGAFail' DO , defined in

each template associated to a level.
- The relay failure of each digital output is monitored in the DO 'asgReleFailn',

where 'n' is the level’s digital output number.
- The analog/digital converter failure of each analog input is monitored in the DO

'asgReleFailn', where 'n' is the level’s analog input number.
5.5.4. Critical hardware failure and non-critical hardware failure

The following DOs, defined in the 'GENERAL' LD LN LPHD, indicate hardware
anomalies:
- ASGPhyHCr: Indication of critical hardware failure. The user can determine a

logic, grouping the failure signals that they consider critical for their system.
- ASGPhyHNC: Indication of non-critical hardware failure. The user can determine a

logic, grouping the failure signals that they consider non-critical for their system

5.6. Configuration parameter modeling

There are configuration parameters that do not have a Graphical Interface in the CNF and
therefore must be adjusted with the option. Many of these parameters are listed and their
values are validated against the CID data template. The CSV Editor accepts both the value
of the enumeration and its 'ord' attribute, e.g. for <EnumVal_ord="0"unknown</EnumVal>
can be configured with 'unknown' or with the value 0; in the CID it will always be initialized
with the value, in this example, the value is 'unknown'.
List of available Enumerations for saTECH equipment with their corresponding values:
<EnumType id="ACDdir">
<EnumVal ord="0">unknown</EnumVal>
<EnumVal ord="1">forward</EnumVal>
<EnumVal ord="2">backward</EnumVal>
<EnumVal ord="3">both</EnumVal>
</EnumType>
<EnumType id="AutoRecSt">
<EnumVal ord="1">Ready</EnumVal>
<EnumVal ord="2">In progress</EnumVal>
<EnumVal ord="3">Successful</EnumVal>
<EnumVal ord="4">Waiting for trip</EnumVal>
<EnumVal ord="5">Trip issued by protection</EnumVal>
<EnumVal ord="6">Fault disappeared</EnumVal>
<EnumVal ord="7">Wait to complete</EnumVal>
<EnumVal ord="8">Circuit breaker closed</EnumVal>
<EnumVal ord="9">Cycle unsuccessful</EnumVal>
<EnumVal ord="10">Unsuccessful</EnumVal>
<EnumVal ord="11">Aborted</EnumVal>
</EnumType>
<EnumType id="seqT">
<EnumVal ord="0">pos-neg-zero</EnumVal>
<EnumVal ord="1">dir-quad-zero</EnumVal>
</EnumType>
<EnumType id="Dbpos">
<EnumVal ord="0">intermediate</EnumVal>
<EnumVal ord="1">off</EnumVal>
<EnumVal ord="2">on</EnumVal>
<EnumVal ord="3">bad</EnumVal>
</EnumType>
<EnumType id="ctlModel">
<EnumVal ord="0">status-only</EnumVal>
<EnumVal ord="1">direct-with-normal-security</EnumVal>
<EnumVal ord="2">sbo-with-normal-security</EnumVal>

<EnumVal ord="3">direct-with-enhanced-security</EnumVal>
<EnumVal ord="4">sbo-with-enhanced-security</EnumVal>
</EnumType>
<EnumType id="sboClass">
<EnumVal ord="0">operate-once</EnumVal>
<EnumVal ord="1">operate-many</EnumVal>
</EnumType>
<EnumType id="orCategory">
<EnumVal ord="0">not-supported</EnumVal>
<EnumVal ord="1">bay-control</EnumVal>
<EnumVal ord="2">station-control</EnumVal>
<EnumVal ord="3">remote-control</EnumVal>
<EnumVal ord="4">automatic-bay</EnumVal>
<EnumVal ord="5">automatic-station</EnumVal>
<EnumVal ord="6">automatic-remote</EnumVal>
<EnumVal ord="7">maintenance</EnumVal>
<EnumVal ord="8">process</EnumVal>
</EnumType>
<EnumType id="Mod">
<EnumVal ord="2">blocked</EnumVal>
<EnumVal ord="3">test</EnumVal>
<EnumVal ord="4">test/blocked</EnumVal>
</EnumType>
<EnumType id="LoadMod">
<EnumVal ord="1">indifferent</EnumVal>
<EnumVal ord="2">protected</EnumVal>
<EnumVal ord="3">upload</EnumVal>
</EnumType>
<EnumType id="GnSt">
<EnumVal ord="1">Stopped</EnumVal>
<EnumVal ord="2">Stopping</EnumVal>
<EnumVal ord="3">Started</EnumVal>
<EnumVal ord="4">Starting</EnumVal>
<EnumVal ord="5">Disabled</EnumVal>
</EnumType>
<EnumType id="Health">
<EnumVal ord="1">Ok</EnumVal>
<EnumVal ord="2">Warning</EnumVal>
<EnumVal ord="3">Alarm</EnumVal>
</EnumType>
<EnumType id="range">
<EnumVal ord="0">normal</EnumVal>
<EnumVal ord="1">high</EnumVal>

<EnumVal ord="2">low</EnumVal>
<EnumVal ord="3">high-high</EnumVal>
<EnumVal ord="4">low-low</EnumVal>
</EnumType>
<EnumType id="multiplier">
<EnumVal ord="-24">y</EnumVal>
<EnumVal ord="-21">z</EnumVal>
<EnumVal ord="-18">a</EnumVal>
<EnumVal ord="-15">f</EnumVal>
<EnumVal ord="-12">p</EnumVal>
<EnumVal ord="-9">n</EnumVal>
<EnumVal ord="-6">µ</EnumVal>
<EnumVal ord="-3">m</EnumVal>
<EnumVal ord="-2">c</EnumVal>
<EnumVal ord="-1">d</EnumVal>
<EnumVal ord="0"/>
<EnumVal ord="1">da</EnumVal>
<EnumVal ord="2">h</EnumVal>
<EnumVal ord="3">k</EnumVal>
<EnumVal ord="6">M</EnumVal>
<EnumVal ord="9">G</EnumVal>
<EnumVal ord="12">T</EnumVal>
<EnumVal ord="15">P</EnumVal>
<EnumVal ord="18">E</EnumVal>
<EnumVal ord="21">Z</EnumVal>
<EnumVal ord="24">Y</EnumVal>
</EnumType>
<EnumType id="SIUnit">
<EnumVal ord="1"/>
<EnumVal ord="2">m</EnumVal>
<EnumVal ord="3">kg</EnumVal>
<EnumVal ord="4">s</EnumVal>
<EnumVal ord="5">A</EnumVal>
<EnumVal ord="6">K</EnumVal>
<EnumVal ord="7">mol</EnumVal>
<EnumVal ord="8">cd</EnumVal>
<EnumVal ord="9">deg</EnumVal>
<EnumVal ord="10">rad</EnumVal>
<EnumVal ord="11">sr</EnumVal>
<EnumVal ord="21">Gy</EnumVal>
<EnumVal ord="22">q</EnumVal>
<EnumVal ord="23">ºC</EnumVal>
<EnumVal ord="24">Sv</EnumVal>
<EnumVal ord="25">F</EnumVal>
<EnumVal ord="26">C</EnumVal>

<EnumVal ord="27">S</EnumVal>
<EnumVal ord="28">H</EnumVal>
<EnumVal ord="29">V</EnumVal>
<EnumVal ord="30">ohm</EnumVal>
<EnumVal ord="31">J</EnumVal>
<EnumVal ord="32">N</EnumVal>
<EnumVal ord="33">Hz</EnumVal>
<EnumVal ord="34">lx</EnumVal>
<EnumVal ord="35">Lm</EnumVal>
<EnumVal ord="36">Wb</EnumVal>
<EnumVal ord="37">T</EnumVal>
<EnumVal ord="38">W</EnumVal>
<EnumVal ord="39">Pa</EnumVal>
<EnumVal ord="41">m²</EnumVal>
<EnumVal ord="42">m³</EnumVal>
<EnumVal ord="43">m/s</EnumVal>
<EnumVal ord="44">m/s²</EnumVal>
<EnumVal ord="45">m³/s</EnumVal>
<EnumVal ord="46">m/m³</EnumVal>
<EnumVal ord="47">M</EnumVal>
<EnumVal ord="48">kg/m³</EnumVal>
<EnumVal ord="49">m²/s</EnumVal>
<EnumVal ord="50">W/m K</EnumVal>
<EnumVal ord="51">J/K</EnumVal>
<EnumVal ord="52">ppm</EnumVal>
<EnumVal ord="53">1/s</EnumVal>
<EnumVal ord="54">rad/s</EnumVal>
<EnumVal ord="61">VA</EnumVal>
<EnumVal ord="62">Watts</EnumVal>
<EnumVal ord="63">VAr</EnumVal>
<EnumVal ord="64">phi</EnumVal>
<EnumVal ord="65">cos(phi)</EnumVal>
<EnumVal ord="66">Vs</EnumVal>
<EnumVal ord="67">V²</EnumVal>
<EnumVal ord="68">As</EnumVal>
<EnumVal ord="69">A²</EnumVal>
<EnumVal ord="70">A²t</EnumVal>
<EnumVal ord="71">VAh</EnumVal>
<EnumVal ord="72">Wh</EnumVal>
<EnumVal ord="73">VArh</EnumVal>
<EnumVal ord="74">V/Hz</EnumVal>
<EnumVal ord="75">Hz/s</EnumVal>
<EnumVal ord="76">char</EnumVal>
<EnumVal ord="77">char/s</EnumVal>
<EnumVal ord="78">kgm²</EnumVal>

<EnumVal ord="79">dB</EnumVal>
</EnumType>
<EnumType id="ParTraMod">
<EnumVal ord="1">No Mode Predefined</EnumVal>
<EnumVal ord="2">Master</EnumVal>
<EnumVal ord="3">Follower</EnumVal>
<EnumVal ord="4">Power Factor</EnumVal>
<EnumVal ord="5">Negative Reactance</EnumVal>
<EnumVal ord="6">Circulating Current</EnumVal>
<EnumVal ord="7">Circulating Reactive Current</EnumVal>
<EnumVal ord="8">Circulating Reactive Current By Equalizing Calculated Transformer Power
Factor</EnumVal>
</EnumType>
<EnumType id="TmSyn">
<EnumVal ord="2">Synchronized by a global area clock signal</EnumVal>
<EnumVal ord="1">Synchronized by a local area clock signal</EnumVal>
<EnumVal ord="0">Not synchronized by a global area clock signal</EnumVal>
</EnumType>
<EnumType id="ServiceType">
<EnumVal ord="0">Unknown</EnumVal>
<EnumVal ord="1">Associate</EnumVal>
<EnumVal ord="2">Abort</EnumVal>
<EnumVal ord="3">Release</EnumVal>
<EnumVal ord="4">GetServerDirectory</EnumVal>
<EnumVal ord="5">GetLogicalDeviceDirectory</EnumVal>
<EnumVal ord="6">GetAllDataValues</EnumVal>
<EnumVal ord="7">GetDataValues</EnumVal>
<EnumVal ord="8">SetDataValues</EnumVal>
<EnumVal ord="9">GetDataDirectory</EnumVal>
<EnumVal ord="10">GetDataDefinition</EnumVal>
<EnumVal ord="11">GetDataSetValues</EnumVal>
<EnumVal ord="12">SetDataSetValues</EnumVal>
<EnumVal ord="13">CreateDataSet</EnumVal>
<EnumVal ord="14">DeleteDataSet</EnumVal>
<EnumVal ord="15">GetDataSetDirectory</EnumVal>
<EnumVal ord="16">SelectActiveSG</EnumVal>
<EnumVal ord="17">SelectEditSG</EnumVal>
<EnumVal ord="18">SetEditSGValue</EnumVal>
<EnumVal ord="19">ConfirmEditSGValues</EnumVal>
<EnumVal ord="20">GetEditSGValue</EnumVal>
<EnumVal ord="21">GetSGCBValues</EnumVal>
<EnumVal ord="22">Report</EnumVal>
<EnumVal ord="23">GetBRCBValues</EnumVal>
<EnumVal ord="24">SetBRCBValues</EnumVal>
<EnumVal ord="25">GetURCBValues</EnumVal>

<EnumVal ord="26">SetURCBValues</EnumVal>
<EnumVal ord="27">GetLCBValues</EnumVal>
<EnumVal ord="28">SetLCBValues</EnumVal>
<EnumVal ord="29">QueryLogByTime</EnumVal>
<EnumVal ord="30">QueryLogAfter</EnumVal>
<EnumVal ord="31">GetLogStatus</EnumVal>
<EnumVal ord="32">SendGOOSEMessage</EnumVal>
<EnumVal ord="33">GetGoCBValues</EnumVal>
<EnumVal ord="34">SetGoCBValues</EnumVal>
<EnumVal ord="35">GetGoReference</EnumVal>
<EnumVal ord="36">GetGOOSEElementNumber</EnumVal>
<EnumVal ord="37">SendMSVMessage</EnumVal>
<EnumVal ord="38">GetMSVCBValues</EnumVal>
<EnumVal ord="39">SetMSVCBValues</EnumVal>
<EnumVal ord="40">SendUSVMessage</EnumVal>
<EnumVal ord="41">GetUSVCBValues</EnumVal>
<EnumVal ord="42">SetUSVCBValues</EnumVal>
<EnumVal ord="43">Select</EnumVal>
<EnumVal ord="44">SelectWithValue</EnumVal>
<EnumVal ord="45">Cancel</EnumVal>
<EnumVal ord="46">Operate</EnumVal>
<EnumVal ord="47">CommandTermination</EnumVal>
<EnumVal ord="48">TimeActivatedOperate</EnumVal>
<EnumVal ord="49">GetFile</EnumVal>
<EnumVal ord="50">SetFile</EnumVal>
<EnumVal ord="51">DeleteFile</EnumVal>
<EnumVal ord="52">GetFileAttributValues</EnumVal>
<EnumVal ord="53">TimeSynchronisation</EnumVal>
<EnumVal ord="54">InternalChange</EnumVal>
</EnumType>
<EnumType id="ServiceError">
<EnumVal ord="0">no-error</EnumVal>
<EnumVal ord="1">instance-not-available</EnumVal>
<EnumVal ord="2">instance-in-use</EnumVal>
<EnumVal ord="3">access-violation</EnumVal>
<EnumVal ord="4">access-not-allowed-in-current-state</EnumVal>
<EnumVal ord="5">parameter-value-inappropriate</EnumVal>
<EnumVal ord="6">parameter-value-inconsistent</EnumVal>
<EnumVal ord="7">class-not-supported</EnumVal>
<EnumVal ord="8">instance-locked-by-other-client</EnumVal>
<EnumVal ord="9">control-must-be-selected</EnumVal>
<EnumVal ord="10">type-conflict</EnumVal>
<EnumVal ord="11">failed-due-to-communications-constraint</EnumVal>
<EnumVal ord="12">failed-due-to-server-constraint</EnumVal>
</EnumType>

<EnumType id="AddCause">
<EnumVal ord="1">Not-supported</EnumVal>
<EnumVal ord="2">Blocked-by-switching-hierarchy</EnumVal>
<EnumVal ord="3">Select-failed</EnumVal>
<EnumVal ord="4">Invalid-position</EnumVal>
<EnumVal ord="5">Position-reached</EnumVal>
<EnumVal ord="6">Parameter-change-in-execution</EnumVal>
<EnumVal ord="7">Step-limit</EnumVal>
<EnumVal ord="8">Blocked-by-Mode</EnumVal>
<EnumVal ord="9">Blocked-by-process</EnumVal>
<EnumVal ord="10">Blocked-by-interlocking</EnumVal>
<EnumVal ord="11">Blocked-by-synchrocheck</EnumVal>
<EnumVal ord="12">Command-already-in-execution</EnumVal>
<EnumVal ord="13">Blocked-by-health</EnumVal>
<EnumVal ord="14">1-of-n-control</EnumVal>
<EnumVal ord="15">Abortion-by-cancel</EnumVal>
<EnumVal ord="16">Time-limit-over</EnumVal>
<EnumVal ord="17">Abortion-by-trip</EnumVal>
<EnumVal ord="18">Object-not-selected</EnumVal>
<EnumVal ord="19">Object-already-selected </EnumVal>
<EnumVal ord="20">No-access-authority</EnumVal>
<EnumVal ord="21">Ended-with-overshoot</EnumVal>
<EnumVal ord="22">Abortion-due-to-deviation</EnumVal>
<EnumVal ord="23">Abortion-by-communication-loss</EnumVal>
<EnumVal ord="24">Blocked-by-command</EnumVal>
<EnumVal ord="25">None</EnumVal>
<EnumVal ord="26">Inconsistent-parameters</EnumVal>
<EnumVal ord="27">Locked-by-other-client</EnumVal>
</EnumType>
<EnumType id="SecurityViolation">
<EnumVal ord="0">unknown</EnumVal>
<EnumVal ord="1">critical</EnumVal>
<EnumVal ord="2">major</EnumVal>
<EnumVal ord="3">minor</EnumVal>
<EnumVal ord="4">warning</EnumVal>
</EnumType>
<EnumType id="RotDir">
<EnumVal ord="1">Clockwise</EnumVal>
<EnumVal ord="2">Counter-Clockwise</EnumVal>
</EnumType>
<EnumType id="SwTyp">
<EnumVal ord="1">Load-break-switch</EnumVal>
<EnumVal ord="2">Disconnector</EnumVal>

<EnumVal ord="3">Earthing-switch</EnumVal>
<EnumVal ord="4">High-speed-earthing-switch</EnumVal>
</EnumType>
<EnumType id="CmdQual">
<EnumVal ord="0">pulse</EnumVal>
<EnumVal ord="1">persistent</EnumVal>
</EnumType>
<EnumType id="typeDNPObj_ASG_1">
<EnumVal ord="0">BINARY INPUT</EnumVal>
<EnumVal ord="1">16 BITS ANALOG INPUT</EnumVal>
<EnumVal ord="2">32 BITS ANALOG INPUT</EnumVal>
<EnumVal ord="3">FLOAT ANALOG INPUT</EnumVal>
<EnumVal ord="4">COUNTER</EnumVal>
<EnumVal ord="5">BINARY OUTPUT</EnumVal>
<EnumVal ord="6">16 BITS ANALOG OUTPUT</EnumVal>
<EnumVal ord="7">32 BITS ANALOG OUTPUT</EnumVal>
<EnumVal ord="8">FLOAT ANALOG OUTPUT</EnumVal>
</EnumType>
<EnumType id="NominalFrequency_ASG_1">
<EnumVal ord="0">50 HZ</EnumVal>
</EnumType>
<EnumType id="typeFuncIn_ASG_1">
<EnumVal ord="0">NO FUNC</EnumVal>
<EnumVal ord="1">INVERTED</EnumVal>
<EnumVal ord="2">DP TO SP OFF</EnumVal>
<EnumVal ord="3">DP TO SP ON</EnumVal>
<EnumVal ord="4">SP TO DP</EnumVal>
</EnumType>
<EnumType id="typeFuncOut_ASG_1">
<EnumVal ord="0">NO FUNC</EnumVal>
<EnumVal ord="1">INVERTED</EnumVal>
</EnumType>

<EnumType id="typeIECIoa_ASG_1">
<EnumVal ord="0">SINGLE POINT</EnumVal>
<EnumVal ord="1">DOUBLE POINT</EnumVal>
<EnumVal ord="2">MEASURED NORMALIZED</EnumVal>
<EnumVal ord="3">MEASURED SCALED</EnumVal>
<EnumVal ord="4">MEASURED SHORT FLOATING</EnumVal>
<EnumVal ord="5">STEP POSITION</EnumVal>
<EnumVal ord="6">INTEGRATED TOTALS</EnumVal>
<EnumVal ord="7">SINGLE COMMAND</EnumVal>
<EnumVal ord="8">DOUBLE COMMAND</EnumVal>
<EnumVal ord="9">SET POINT COMMAND NORMALIZED</EnumVal>

<EnumVal ord="10">SET POINT COMMAND SCALED</EnumVal>

<EnumVal ord="11">SET POINT COMMAND SHORT FLOATING</EnumVal>
<EnumVal ord="12">REGULATING STEP COMMAND</EnumVal>
</EnumType>
<EnumType id="Beh">
<EnumVal ord="2">on-blocked</EnumVal>
<EnumVal ord="3">test</EnumVal>
<EnumVal ord="4">test/blocked</EnumVal>
</EnumType>

<EnumType id="CtlModel_asg_1">
<EnumVal ord="0">sbo</EnumVal>
<EnumVal ord="1">direct</EnumVal>
<EnumVal ord="2">inheritance</EnumVal>
</EnumType>
<EnumType id="ScuId_asg_1">
<EnumVal ord="0">SCU 1</EnumVal>
<EnumVal ord="1">SCU 2</EnumVal>
</EnumType>
<EnumType id="ClassType">
<EnumVal ord="0">ClassNone</EnumVal>
<EnumVal ord="1">Class1</EnumVal>
</EnumType>
<EnumType id="VoltageWiring_ASG_1">
<EnumVal ord="0">estrella-estrella</EnumVal>
<EnumVal ord="1">estrella-delta</EnumVal>
<EnumVal ord="2">delta-delta</EnumVal>
<EnumVal ord="3">delta-estrella</EnumVal>
</EnumType>
<EnumType id="PhaseRotation_ASG_1">
<EnumVal ord="0">ABC</EnumVal>
<EnumVal ord="1">ACB</EnumVal>
</EnumType>
<EnumType id="NominalFrequency_ASG_1">
</EnumType>

VERSION AND COMPATIBILITY MATRIX
Chapter 6. Version and Compatibility Matrix
Currently the SAS versions must be compatible with each other, specifying the steps required
to migrate a project from a previous version to the new SAS version for the user to see.
There are three cases where the ACP can be used to update the installed base.
1. Hardware modification for the SCU without configuration modification. The CNF is not
updated and, with the same CIDs, the new SCU is able to function. Compatibility
depends upon the SCU software.
2. Partially update the project configuration in order to later update some substation
equipment. The user will be able to change the templates for a particular IED without
updating the templates for the other IEDs in the project, to which they are subscribed
via Goose. The user must adjust the IED configuration in the project, update project CID
templates and then assign them only to the IED to be updated, resolve "Error" or
"Warning" messages. Compatibility is up to the user with the CNF.
3. New or non-energized project, same as case 2, the difference is that it will be possible
to upgrade the version of ICDs for all IEDs in the project. We can make configurations
where the SCU and HMI share settings, and others where the settings are independent.
Important Note: Modifications to the project must first be done in the Factory, in order to be able
to compare the new CID files against the substation CID files to be replaced. In this way, we
can ensure good performance in the substation.
The new option allows for compatibility to be maintained in all cases. The second case is the
most important, in order to solve the problem of different versions in same type equipment, the
project's IEDs become different versions of ICD.
From the ICD version, the CID generator can generate different configurations, allowing to
generate the same CIDs as in previous versions. For any parameter configurable by means of
the user interface of the new version, if later in the ICD version the object to be parameterized
does not exist, the CNF will warn the user with an information message in the User Console.
Example of an information message for a visual configuration of the switching time between
synchronization sources generated in ICDs prior to version 18.11:
Cause - ICD without the new visual configuration: GENERAL/LTMS1.SynChTout1.setVal

Message - New parameter in templates. If we wish to update the templates of the

'ESCOBEDO' Project, we must execute the option 'Update CID Templates' and in the
IED the option 'Advanced Properties of Configurable Parameters'.
The types of messages where the code is INFO do not cause errors and it is not necessary to
update templates; they warn about visual parameters that cannot be generated in the CID by
the version of ICD assigned at that time to the IED. IED template updates will depend on the
ongoing needs.
The following Table 24 summarizes the parameters and configurations supported by the
different software versions of the equipment.


Advanced Parameters
SAS 2.00 SAS 1.07 SAS 1.06 SAS 1.05 SAS 1.04
IED with ICD version:
- 18.11u06 Version Yes No No No No
- 17.08u00 Version Yes Yes No No No
- Imported Project Version Yes Yes Yes Yes Yes
Generation of CID according to IEC-61850 Edition 2007-

Yes No No No No
B
Adding 'Analog Controls' Traceability to DataSet Yes No No No No
Forcing 'Internal Commands' as self generated signals Yes No No No No
Force the new 'Hardware Alarms' as self generated

Yes No No No No
signals
Force templates to use 'Percentage of Variation to

Yes Yes Yes Yes Yes
generate Alarm'
Maximum number of records per DataSet:
- Value at 512 FCDA Yes Yes Yes Yes Yes
- Value at 1024 FCDA Yes No No No No
Visual Configuration Options
Configuration of images within the Single Line diagram or

Yes No No No No
configuration of logos
CTCD acquisition points of the SAP20-TCD master

Yes No No No No
protocol
Redundancy of Ethernet or Serial ports in protocols Yes Yes * No No No
Table 24 Supported parameters between software versions

List of Contents
Figure 1-1 Software installation ........................................................................................... 11

Figure 1-2 Inconsistent installation....................................................................................... 13
Figure 2-1 Main Window ...................................................................................................... 14
Figure 2-2 File Menu............................................................................................................ 15
Figure 2-3 New Project ........................................................................................................ 15
Figure 2-4 Project Data - Screen 1 ...................................................................................... 16
Figure 2-5 Project Data - Screen 2 ...................................................................................... 17
Figure 2-6 Substation data................................................................................................... 19
Figure 2-7 SCU and HMI equipment configuration ............................................................... 19
Figure 2-8 SCU and HMI equipment configuration ............................................................... 19
Figure 2-9 HMI equipment configuration .............................................................................. 20
Figure 2-10 Project created ................................................................................................. 20
Figure 2-11 Open Project..................................................................................................... 21
Figure 2-12 Open project ..................................................................................................... 21
Figure 2-13 Import project from IED ..................................................................................... 22
Figure 2-14 Link Signals, project information view ............................................................... 23
Figure 2-15 Associating signals, associating sheets to the IEDs .......................................... 24
Figure 2-16 Confirmation to Delete Project .......................................................................... 25
Figure 2-17 Edit Menu ......................................................................................................... 25
Figure 2-18 Project IED parameters .................................................................................... 26
Figure 2-19 Default values for saTECH CNF ....................................................................... 26
Figure 2-20 Default values for TP and TC boards ................................................................ 27
Figure 2-21 Default values for SCU as a synchronism source ............................................. 28
Figure 2-22 View Menu ........................................................................................................ 29
Figure 2-23 Graphics Menu ................................................................................................. 29
Figure 2-24 HMI Templates - Drawing Selector ................................................................... 31
Figure 2-25 HMI Drawing Template Creation ....................................................................... 32
Figure 2-26 Elements tab..................................................................................................... 47
Figure 2-27 Drawing Canvas Configuration ......................................................................... 47
Figure 2-28 Symbol configuration ........................................................................................ 48
Figure 2-29 Properties of the Switches and Blades elements .............................................. 49
Figure 2-30 Example of a Single Line Drawing Template..................................................... 49
Figure 2-31 Save drawing template ..................................................................................... 50
Figure 2-32 Drawing template name .................................................................................... 50
Figure 2-33 Menu Associate HMI positions .......................................................................... 50
www.arteche.com © Arteche
Figure 2-34 Associate HMI positions ................................................................................... 51
Figure 2-35 Edit HMI Single Line ......................................................................................... 52
Figure 2-36 Validating signals from the Single Line ............................................................. 53
Figure 2-37 Signal Validation in Single Line Report ............................................................. 53
Figure 2-38 Generate Single Line HMI................................................................................. 54
Figure 2-39 Edit BCU Drawing Templates ........................................................................... 55
Figure 2-40 Validate signals BCU drawings ......................................................................... 56
Figure 2-41 BCU Drawings Signal Validation Report ........................................................... 56
Figure 2-42 Generate drawings of all BCUs ......................................................................... 56
Figure 2-43 Edit System Status ........................................................................................... 57
Figure 2-44 Selection of system status drawing ................................................................... 57
Figure 2-45 System status drawing ...................................................................................... 58
Figure 2-46 Validate system status signals .......................................................................... 59
Figure 2-47 Status Signal Validation Report ........................................................................ 59
Figure 2-48 Generation of system status drawing ................................................................ 60
Figure 2-49 Updating the project's graphic libraries ............................................................. 60
Figure 2-50 Signal simulator ................................................................................................ 61
Figure 2-51 Tools Menu ....................................................................................................... 61
Figure 2-52 Send Firmware ................................................................................................. 62
Figure 2-53 Send Firmware and Update Application ............................................................ 62
Figure 2-54 See Standard Table of Signals in saTECH CNF ............................................... 63
Figure 2-55 Display Standardized Signal File ...................................................................... 63
Figure 2-56 See Standardized Project Signal Table............................................................. 64
Figure 2-57 Compare Project Table ..................................................................................... 64
Figure 2-58 Project Table Comparator ................................................................................. 65
Figure 2-59 Update Standardized Project Signal File ........................................................... 65
Figure 2-60 Update CID Templates ..................................................................................... 66
Figure 2-61 CID templates update confirmation ................................................................... 67
Figure 2-62 CID templates update confirmation ................................................................... 67
Figure 2-63 Updating a third-party CID ................................................................................ 68
Figure 2-64 Logo Configuration ........................................................................................... 69
Figure 2-65 Logo Allocation ................................................................................................. 69
Figure 2-66 SCU with changed logo details ......................................................................... 69
Figure 2-67 Configure Equipment Models ............................................................................ 70
Figure 2-68 Configuration of equipment models for each master protocol ........................... 70
Figure 2-69 See History ....................................................................................................... 71
Figure 2-70 Displaying historical records ............................................................................. 71
Figure 2-71 Historical records export ................................................................................... 72
Figure 2-72 Historical record configuration .......................................................................... 72
Figure 2-73 Signal tree of the historical record..................................................................... 73
Figure 2-74 Custom measures selection.............................................................................. 73
Figure 2-75 Help Menu ........................................................................................................ 74
Figure 2-76 CNF version ..................................................................................................... 74
Figure 3-1 New Voltage Level .............................................................................................. 75
Figure 3-2 Voltage Level Name ........................................................................................... 75
Figure 3-3 Voltage level in the substation ............................................................................ 76
Figure 3-4 New Bay ............................................................................................................. 76
Figure 3-5 Name of the Bay ................................................................................................. 77
Figure 3-6 Voltage level in the substation ............................................................................ 77
Figure 3-7 IED registration ................................................................................................... 78
Figure 3-8 IED allocation ..................................................................................................... 78
Figure 3-11 Associate Function ........................................................................................... 81
Figure 3-13 Hardware model selection ................................................................................ 81
Figure 3-14 IED details panel .............................................................................................. 84
Figure 3-15 SCU Hardware Model Edition ........................................................................... 84
Figure 3-16 HMI Hardware Model Edition ............................................................................ 85
Figure 3-17 Add Function .................................................................................................... 85
Figure 3-19 Edit Project ....................................................................................................... 86
Figure 3-20 Edit/Delete Voltage Level or Bay ...................................................................... 87
Figure 3-21 Removing Functions on Bays and IEDs ............................................................ 87
Figure 3-22 Update Project CID Templates ......................................................................... 87
Figure 4-1 Hardware Model Edition ..................................................................................... 88
Figure 4-2 Gooses and Reports Configuration ..................................................................... 88
Figure 4-3 GSEControl ........................................................................................................ 88
Figure 4-4 New GSEControl ................................................................................................ 89
Figure 4-5 Add DataSet ....................................................................................................... 90
Figure 4-6 New DataSet ...................................................................................................... 90
Figure 4-7 DataSet Available Signals .................................................................................. 91
Figure 4-8 DataSet Attributes .............................................................................................. 92
Figure 4-9 Selection at the Data Object level ....................................................................... 92
Figure 4-10 Publication Space GSEControl ......................................................................... 93
Figure 4-11 GSEControl ...................................................................................................... 93
Figure 4-12 ReportControl ................................................................................................... 94
Figure 4-13 New ReportControl ........................................................................................... 94
Figure 4-14 Add DataSet ..................................................................................................... 96
Figure 4-15 Report DataSet Edition ..................................................................................... 96
Figure 4-16 Publication Space ............................................................................................. 97
Figure 4-17 Report Control Block......................................................................................... 97
Figure 4-18 Logic Function .................................................................................................. 98
Figure 4-19 Logic Function Name ........................................................................................ 98
Figure 4-20 Logic functions screen before loading the signal tree........................................ 99
Figure 4-21 Logic functions screen after loading the signal tree........................................... 99
Figure 4-22 Logic functions panels .................................................................................... 100
Figure 4-23 Information panel of a logic function ............................................................... 100
Figure 4-24 Logic functions edition .................................................................................... 101
Figure 4-25 Logic Functions Toolbar ................................................................................. 101
Figure 4-26 Table of logic functions variables .................................................................... 103
Figure 4-27 Add Variables Menu ....................................................................................... 105
Figure 4-28 Add Variables Menu ....................................................................................... 106
Figure 4-29 Signal Selector ............................................................................................... 106
Figure 4-30 New Constant ................................................................................................. 107
Figure 4-31 IED Signal Editor ............................................................................................ 107
Figure 4-32 Dragging signals from the signal editor ........................................................... 108
Figure 4-33 Delete variables from the table. ...................................................................... 108
Figure 4-34 Delete variables from the table. ...................................................................... 109
Figure 4-35 Dragging a logic function ................................................................................ 109
Figure 4-36 Dragging a variable from the table of variables ............................................... 110
Figure 4-37 Link between the blocks ................................................................................. 110
Figure 4-38 Trip coil supervision of a circuit breaker .......................................................... 110
Figure 4-39 BCU Configuration Options............................................................................. 120
Figure 4-40 RIO Configuration Options .............................................................................. 120
Figure 4-41 SCU-HMI Configuration Options ..................................................................... 120
Figure 4-42 SCU configuration Options ............................................................................. 120
Figure 4-43 HMI Configuration Options.............................................................................. 120
Figure 4-44 Other Manufacturer Configuration Options ..................................................... 120
Figure 4-45 Network configuration ..................................................................................... 122
Figure 4-46 Time Configuration ......................................................................................... 123
Figure 4-47 Synchronization source configuration ............................................................. 124
Figure 4-48 Dual UCS with HMI sync-source configuration................................................ 125
Figure 4-49 Creation of a slave protocol ............................................................................ 128
Figure 4-50 Slave Protocol Settings - Points Tab - Edit Point ............................................ 139
Figure 4-51 Creation of master protocol............................................................................. 140
Figure 4-52 Master Protocol Setup - Points Tab - Edit Point .............................................. 148
Figure 4-53 61850 BCU Communication ........................................................................... 149
Figure 4-54 61850 RIO Communication............................................................................. 149
Figure 4-55 61850 SCU-HMI Communication .................................................................... 149
Figure 4-56 61850 SCU Communication ........................................................................... 149
Figure 4-57 61850 HMI Communication ............................................................................ 149
Figure 4-58 Selection of gooses publisher IED .................................................................. 150
Figure 4-59 GSE Control Selection .................................................................................... 150
Figure 4-60 Gooses subscription zone............................................................................... 151
Figure 4-61 Gooses subscription information ..................................................................... 151
Figure 4-62 Selection of publisher reports IED................................................................... 152
Figure 4-63 Report Control Block Selection ....................................................................... 152
Figure 4-64 Report subscription section............................................................................. 153
Figure 4-65 Report subscription information ...................................................................... 153
Figure 4-66 Edit DataSet ................................................................................................... 154
Figure 4-67 DataSet Selection ........................................................................................... 154
Figure 4-68 Dataset Editing ............................................................................................... 155
Figure 4-69 Dataset signal editing ..................................................................................... 155
Figure4-70 IED Signal Editor ............................................................................................. 156
Figure 4-71 CSV display panel .......................................................................................... 156
Figure 4-72 Filter by columns ............................................................................................ 157
Figure 4-73 Signal filtering from the heading...................................................................... 157
Figure 4-74 Row Context Menu ......................................................................................... 158
Figure 4-75 Insert Row ...................................................................................................... 158
Figure 4-76 Selection of rows to be copied ........................................................................ 159
Figure 4-77 Disabled Row ................................................................................................. 160
Figure 4-78 Autocomplete.................................................................................................. 160
Figure 4-79 Delete cell content .......................................................................................... 161
Figure 4-80 Show signal tree ............................................................................................. 162
Figure 4-81 Show acronym panel ...................................................................................... 163
Figure 4-82 Acronyms panel .............................................................................................. 163
Figure 4-83 Disable acquisition .......................................................................................... 167
Figure 4-84 Context menu Properties column .................................................................... 168
Figure 4-85 Analog Range Configuration ........................................................................... 169
Figure 4-86 Pulse Configuration ........................................................................................ 169
Figure 4-87 Automatic Override Configuration ................................................................... 169
Figure 4-88 Disable publication address ............................................................................ 170
Figure 4-89 Editing Cells ................................................................................................... 170
Figure 4-90 Dragging signals ............................................................................................. 171
Figure 4-91 Drag to Single Line Editor ............................................................................... 172
Figure 4-92 Standardized signal file................................................................................... 172
Figure 4-93 Row and Cell Operations ................................................................................ 173
Figure 4-95 Operation: Create new 'Data Object' type configuration. ................................. 174
Figure 4-96 Update Standardized Project Signal File (overwrite) ....................................... 175
Figure 4-97 Signal association from file ............................................................................. 175
Figure 4-98 Signal association file selection ...................................................................... 176
Figure 4-99 Signal association file selection - sheet selection ............................................ 177
Figure 4-100 Details of IED Functions on an Old Project Bay ............................................ 179
Figure 4-101 Master Communication Profile Details .......................................................... 186
Figure 4-102 Slave Communication Profile Details ............................................................ 191
Figure 4-103 Bay graphic selection.................................................................................... 216
Figure 4-104 Edit Single Line BCU .................................................................................... 216
Figure 4-105 Single Line BCU Array Editing ...................................................................... 217
Figure4-106 Graph generation Single line IED.................................................................. 217
Figure 4-107 TFT password configuration ......................................................................... 218
Figure 4-108 BCU parameters Configurable Options (with TC and TP card) ..................... 220
Figure 4-109 Configurable BCU Parameters Options (without TC and TP card) ................ 220
Figure 4-110 Configurable RIO CuFo parameters Options ................................................ 220
Figure 4-111 Configurable RIO MES Parameters Options ................................................. 220
Figure 4-112 Configurable SCU parameters Options ......................................................... 220
Figure 4-113 Configurable HMI Parameters Options ......................................................... 220
Figure 4-114 HMI Historical Measurements: Generate and Download the backup files ..... 220
Figure 4-115 HMI Historical Restorer Configurator ............................................................ 221
Figure 4-116 Configuring IEDs as an SNTP Synchronization Source ................................ 222
Figure 4-117 'Configurable Parameters for TP and TC Cards' option................................. 223
Figure 4-118 Specific configuration of TP and TC cards .................................................... 224
Figure 4-119 Specific configuration of TP and TC cards .................................................... 224
Figure 4-120 ‘Configurable Parameters Function 25' Option .............................................. 226
Figure 4-121 Function 25 Configuration ............................................................................. 227
Figure 4-122 RSYN Association ........................................................................................ 227
Figure 4-123 Monitoring of external equipment .................................................................. 229
Figure 4-124 Communication Identifiers ............................................................................ 229
Figure 4-125 Details of the Slave Profile Identifier ............................................................. 230
Figure 4-126 Details of the Master Profile Identifier ........................................................... 231
Figure 4-127 Self-Generated BCU Signals ........................................................................ 232
Figure 4-128 Local/Remote equipment signals .................................................................. 232
Figure 4-129 Signals internal to the equipment .................................................................. 233
Figure 4-130 Higher Levels................................................................................................ 235
Figure 4-131 61850 Communication .................................................................................. 237
Figure 4-132 Acquisition Level ........................................................................................... 238
Figure 4-133 Analog TP and TC Card(s) Measurements ................................................... 240
Figure 4-134 RSYN Function 25 ........................................................................................ 244
Figure 4-135 Add IED without a bay .................................................................................. 251
Figure 4-136 Removing IED and project logic functions ..................................................... 251
Figure 4-137 IEC-61850 Signal Tree ................................................................................. 253
Index of tables
Table 1 Hardware Requirements ............................................................................................. 10

Table 2 Operatingsystem ........................................................................................................ 10
Table 3 Common dynamic behavior of the graphical symbols of the Single Line diagram ....... 42
Table 4 Other dynamic behavior properties ............................................................................. 43
Table 5 More dynamic behavior properties.............................................................................. 44
Table 6 Dynamic behavior of the graphical semaphore symbols of the single line diagram ..... 46
Table 7 Control functions with logical nodes ............................................................................ 80
Table 8 Logic functions toolbar functionality .......................................................................... 102
Table 9 Symbols in the 'Use' column ..................................................................................... 104
Table 10 Data type equivalence in logic functions ................................................................. 112
Table 11 Configuration Options by SaTECH Equipment Model ............................................. 119
Table 12 Standardized signals CSWI function ....................................................................... 198
Table 13 Standardized signals XSWI function ....................................................................... 198
Table 14 Standardized signals XCBR function ...................................................................... 200
Table 15 Standardized signals MOPR function ..................................................................... 202
Table 16 Standardized signals MBAL function ...................................................................... 204
Table 17 Standardized signals DIRCAPT function ................................................................ 205
Table 18 YPTR function Standardized signals ...................................................................... 206
Table 19 GAPC function Standardized signals ...................................................................... 206
Table 20 GGIO function Standardized signals ....................................................................... 208
Table 21 GENERAL Common Standardized signals ............................................................. 210
Table 22 GENERAL SU Standardized signals ...................................................................... 211
Table 23 GENERAL BU Standardized signals ...................................................................... 211
Table 24 Supported parameters between software versions ................................................. 271

Manual de Usuario saTECH-CNF en

Uploaded by

Copyright:

Available Formats

Manual de Usuario saTECH-CNF en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual de Usuario saTECH-CNF en

Uploaded by

Copyright:

Available Formats

saTECH CNF

Date: July 2020

© Electrotécnica Arteche Smart Grid, S.L.

RESTRICTED USE DOCUMENT.

The total or partial reproduction of this

Document subject to change.

LIST OF CONTENTS ..................................................................................................... 3

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

Chapter 2. Application's main window ..................................................................... 14

saTECH CNF|User Manual 3

2.3.1. Project .................................................................................................................... 29

Chapter 3. Project Engineering and IED Configuration .......................................... 75

saTECH CNF|User Manual 4

3.7. Edit/Delete Voltage Levels and Bays ............................................................................ 86

Chapter 4. IED Group Configuration ......................................................................... 88

saTECH CNF|User Manual 5

4.4.9.3. Subscription to all ReportControls ................................................................................. 153

saTECH CNF|User Manual 6

4.4.11.2. Standardized texts associated with signals .................................................................. 197

Chapter 5. Modeling of elements ............................................................................ 255

Chapter 6. Version and Compatibility Matrix ......................................................... 269

List of Contents ........................................................................................................ 272

saTECH CNF|User Manual 7

Index of tables .......................................................................................................... 279

saTECH CNF|User Manual 8

 In the case of IED's:

 In the case of Systems:

o The configuration is comprised of the CID configuration files of each

saTECH CNF|User Manual 9

1.2. Hardware requirements

Hardware Recommended Hardware

CPU 1.0 GHz 2.2 GHz

Monitor 1024 x 768 1280 x 1024

Graphics Card Not required Recommended

Ethernet port Necessary Necessary

Table 1 Hardware Requirements

1.3. Operative system requirements

Operating System Recommended

Microsoft Windows XP 32-bit SP2 or higher

Microsoft Windows Server 2003 32-bit SP2

Microsoft Windows Vista Business 32-bit SP2

Microsoft Windows 7 Professional 32-bit SP1

Microsoft Windows 7 Professional 64-bit SP1

Microsoft Windows 8 64-bit SP1

Microsoft Windows 10 Home 32-bit

Microsoft Windows 10 Home 64-bit

Microsoft Windows 10 Pro 32-bit

Microsoft Windows 10 Pro 64-bit

saTECH CNF|User Manual 10

Figure 1-1 Software installation

saTECH CNF|User Manual 11

1.4.1. Description of the installation process

A. Application language. Selection of the language to be used during installation and

B. Installation information. Software version.

C. Application installation folder. Selection of the installation location and reading

E. Information on the components to be installed.

F. Installation outcome. Brief summary of the application’s components and files

 Abort: Stop the installation, it is recommended to close all programs, restart

 Omit: Proceed with the installation by omitting the error; it is not