EcoSUI

Human Machine Interface

EcoSUI/EN AN/I-RC1
03/2021

Application Note

Configuration

Version I
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 1

CONTENT
1. Scope of the Document ............................................................................ 6
2. Prerequisite .............................................................................................. 6
3. Required Data Acquisition Files ................................................................ 7
3.1 The Database configuration file ............................................................................................ 7
3.2 The Signal List ........................................................................................................................ 8
3.3 The General.ini File ................................................................................................................ 8
3.4 The Mimics\General.ini File ................................................................................................... 8
3.5 The Ring.ini File ...................................................................................................................... 8
3.6 The Profile.xml File................................................................................................................. 8
3.7 The Servers.ini File................................................................................................................. 8
3.8 The DisturbanceFolders.ini File ............................................................................................ 8
3.9 The Graphical Configuration ................................................................................................. 8

4. The Signal List .......................................................................................... 9

4.1 Overview ................................................................................................................................. 9
4.2 Signal Attributes ................................................................................................................... 10
4.3 Specify / Change the separator ........................................................................................... 10
4.4 Add Communication Link Datapoint ................................................................................... 10
4.5 Example of Data Points ........................................................................................................ 11
4.5.1 SPS ........................................................................................................................................................... 11
4.5.2 DPS ........................................................................................................................................................... 11
4.5.3 MPS .......................................................................................................................................................... 11
4.5.4 DPC .......................................................................................................................................................... 12
4.5.5 MV ............................................................................................................................................................. 12
4.5.6 STR ........................................................................................................................................................... 12
4.5.7 SP ............................................................................................................................................................. 12

5. The General.ini File ................................................................................ 13

5.1 Overview ............................................................................................................................... 13
5.2 Possible Parameters ............................................................................................................ 14
5.2.1 [Database]................................................................................................................................................. 14
5.2.2 [General] ................................................................................................................................................... 14
5.2.3 [Supervisor] ............................................................................................................................................... 15
5.2.4 [Languages] .............................................................................................................................................. 15
5.2.5 [Alarms] ..................................................................................................................................................... 15
5.2.6 [SaveToFile] .............................................................................................................................................. 16
5.2.7 [SBUSServer]............................................................................................................................................ 16
5.2.8 [Project] ..................................................................................................................................................... 17
5.2.9 [AutomaticExport] ..................................................................................................................................... 17
5.2.10 [AlarmFileExport] ...................................................................................................................................... 17
5.2.11 [Dummy].................................................................................................................................................... 18
5.2.12 [Security] ................................................................................................................................................... 18
5.2.13 [Curves]..................................................................................................................................................... 18
5.2.14 [Mimics] ..................................................................................................................................................... 18
5.2.15 [StateViewer]............................................................................................................................................. 18
5.2.16 [EventViewer] ............................................................................................................................................ 18
5.2.17 [VCR] ........................................................................................................................................................ 19
5.2.18 [CurveTooltips] .......................................................................................................................................... 19
5.2.19 [Feedbacks] .............................................................................................................................................. 19
5.2.20 [Events] ..................................................................................................................................................... 19
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 2

5.2.21 [Chromium] ............................................................................................................................................... 19

6. The Mimics\General.ini File .................................................................... 20

6.1 Overview ............................................................................................................................... 20
6.2 Possible Parameters ............................................................................................................ 21
6.2.1 [Debug] ..................................................................................................................................................... 21
6.2.2 [General] ................................................................................................................................................... 21
6.2.3 [Version] .................................................................................................................................................... 22
6.2.4 [MimicDrawing] ......................................................................................................................................... 22
6.2.5 [Buzzer] ..................................................................................................................................................... 22
6.2.6 [Feedback] ................................................................................................................................................ 22
6.2.7 [HMI] ......................................................................................................................................................... 22
6.2.8 [Tooltips] ................................................................................................................................................... 23
6.2.9 [SetPoints]................................................................................................................................................. 23
6.2.10 [QualityHandling] ...................................................................................................................................... 23

7. The Ring.ini File ...................................................................................... 24

7.1 Overview ............................................................................................................................... 24
7.2 Possible Parameters ............................................................................................................ 25
7.2.1 [Ring] ......................................................................................................................................................... 25
7.2.2 [SBUSAccess]........................................................................................................................................... 27
7.2.3 [RedundantC264] ...................................................................................................................................... 27
7.2.4 [LogbookPrinterManager] ......................................................................................................................... 27
7.2.5 [IEC61850] ................................................................................................................................................ 28
7.2.6 [LogicalRing] ............................................................................................................................................. 28
7.2.7 [HotHotRedundant] ................................................................................................................................... 29
7.2.8 [OPC] ........................................................................................................................................................ 29
7.2.9 [External DLL] ........................................................................................................................................... 29
7.2.10 [SCE] ......................................................................................................................................................... 29
7.2.11 [AutoGI] ..................................................................................................................................................... 29
7.2.12 [Disconnection] ......................................................................................................................................... 30
7.2.13 [DeviceSynchro] ........................................................................................................................................ 30
7.2.14 [IncorrectTimeStamp] ............................................................................................................................... 30
7.2.15 [SBUSServerRedundancy] ....................................................................................................................... 30
7.2.16 [InitialValues]............................................................................................................................................. 30

8. The Profile.xml File ................................................................................. 31

8.1 Overview ............................................................................................................................... 31
8.2 Data structure ....................................................................................................................... 31
8.2.1 SPS ........................................................................................................................................................... 32
8.2.2 DPS ........................................................................................................................................................... 34
8.2.3 MPS .......................................................................................................................................................... 36
8.2.4 SPC ........................................................................................................................................................... 39
8.2.5 DPC .......................................................................................................................................................... 41
8.2.6 SP ............................................................................................................................................................. 42
8.2.7 MV ............................................................................................................................................................. 43
8.2.8 STR ........................................................................................................................................................... 51
8.2.9 SP ............................................................................................................................................................. 51
8.3 Example of Profiles.xml File ................................................................................................ 52

9. The Servers.ini File ................................................................................. 54

9.1 Overview ............................................................................................................................... 54
9.2 Main content ......................................................................................................................... 54
9.3 Possible Parameters ............................................................................................................ 55
9.3.1 [CentralDB] section ................................................................................................................................... 55
9.3.2 [MultiCentralDBLight] section ................................................................................................................... 57
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 3

9.3.1 [AdditionalCAEDatabases] section ........................................................................................................... 57

9.3.2 [SBUSServer] section ............................................................................................................................... 57
9.3.3 [SBUSServers] section ............................................................................................................................. 58
9.3.4 [CAEDatabases] section ........................................................................................................................... 58
9.3.5 [MVArchiving] section ............................................................................................................................... 58
9.3.6 [LogbookPrinter] section ........................................................................................................................... 59
9.3.7 [TelnetServer] section ............................................................................................................................... 59
9.3.8 [TimeSynchro] section .............................................................................................................................. 60
9.3.9 [MVRingsArchiving] section ...................................................................................................................... 60

10. The DisturbanceFolders.ini File .............................................................. 61

10.1 Overview ............................................................................................................................... 61
10.2 Main content ......................................................................................................................... 61
10.1 Possible Parameters ............................................................................................................ 61
10.1.1 [General] section ....................................................................................................................................... 61
10.1.2 [DownloadFolder] section ......................................................................................................................... 62
10.1.3 [DisturbanceFolder] section ...................................................................................................................... 62
10.1.4 [DeleteDisturbance] section ...................................................................................................................... 62

11. The Autoextract.ini File ........................................................................... 63

11.1 Overview ............................................................................................................................... 63
11.2 Main content ......................................................................................................................... 63
11.3 Possible Parameters ............................................................................................................ 64
11.3.1 [PC name] section .................................................................................................................................... 64

12. IEC 61850 LAN ....................................................................................... 65

12.1 From EPAS SCE zip File ...................................................................................................... 65
12.1.1 Create a ring folder ................................................................................................................................... 65
12.1.2 Edit the ring.ini file .................................................................................................................................... 65
12.1.3 Load the SCE database ............................................................................................................................ 66
12.2 From a Signal List ................................................................................................................ 68
12.2.1 Create a ring folder ................................................................................................................................... 68
12.2.2 Edit the ring.ini file .................................................................................................................................... 68
12.2.3 Create the Profiles.xml File ....................................................................................................................... 68
12.2.4 Create the Signal list with Profile Studio Tool ........................................................................................... 69
12.2.5 Import & fix SCD file ................................................................................................................................. 71
12.2.6 Deploy ....................................................................................................................................................... 71

13. Modbus LAN ........................................................................................... 72

13.1 Generalities ........................................................................................................................... 72
13.2 L_Modbus_XML_0.xml Data Structure ................................................................................ 72
13.3 Main Node <MAIN> ............................................................................................................... 74
13.4 Equipment Node <EQT>....................................................................................................... 74
13.4.1 Redundancy Node .................................................................................................................................... 76
13.4.2 Mailbox Node ............................................................................................................................................ 78
13.4.3 Frame Node .............................................................................................................................................. 80
13.5 Modbus addressing format .................................................................................................. 86
13.6 Modbus Hot-Hot Redundancy ............................................................................................. 87
13.6.1 Limitations ................................................................................................................................................. 87
13.6.2 Ring.ini configuration ................................................................................................................................ 87
13.6.3 Additional datapoints for Hot-Hot Redundancy ........................................................................................ 87
13.7 Selecting the Active IED....................................................................................................... 88
13.8 Supported Modbus Function codes .................................................................................... 89
13.9 Define a MODBUS LAN ........................................................................................................ 90
13.9.1 Create a Rings folder ................................................................................................................................ 90
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 4

13.9.2 Edit the Ring.ini file ................................................................................................................................... 90

13.9.3 L_Modbus.dll............................................................................................................................................. 90
13.9.4 L_Modbus_XML_0.xml ............................................................................................................................. 90
13.9.5 Create the Profiles.xml File ....................................................................................................................... 90
13.10 Create and prepare the Signal list ....................................................................................... 91
13.11 Import & fix SCD file ............................................................................................................. 91
13.12 Deploy ................................................................................................................................... 91

14. SNMP LAN ............................................................................................. 92

14.1 Create a ring folder............................................................................................................... 92
14.2 Edit the Ring.ini file .............................................................................................................. 92
14.2.1 Edit the Host file ........................................................................................................................................ 93
14.2.2 Prepare the Signal list according to MIB addressing ................................................................................ 93
14.2.3 How to find MIB addressing ...................................................................................................................... 94
14.3 Prepare Profiles.xml file ....................................................................................................... 96
14.4 Deploy ................................................................................................................................... 98

15. OPC LAN ................................................................................................ 99

15.1 Create a ring folder............................................................................................................... 99
15.2 Edit the Ring.ini file .............................................................................................................. 99
15.3 Create the Profiles.xml File ................................................................................................ 100
15.4 Create and prepare the Signal list ..................................................................................... 101
15.5 Import & fix SCD file ........................................................................................................... 102
15.6 Deploy ................................................................................................................................. 103

16. Virtual LAN ........................................................................................... 104

16.1 Principles ............................................................................................................................ 104
16.2 Create a ring folder............................................................................................................. 104
16.3 Edit the ring.ini file ............................................................................................................. 104
16.4 Create the Profiles.xml File ................................................................................................ 105
16.5 Define Formulas ................................................................................................................. 106
16.5.1 From Sbus SERVER .............................................................................................................................. 106
16.5.2 From EcoSUI Mimics .............................................................................................................................. 115
16.5.3 Output Files............................................................................................................................................. 118
16.6 Define Scripts ..................................................................................................................... 119
16.6.1 Presentation ............................................................................................................................................ 119
16.6.2 Prerequisites ........................................................................................................................................... 119
16.6.3 Create Scripts ......................................................................................................................................... 119
16.6.1 Configure Scripts .................................................................................................................................... 120
16.6.2 Execute Scripts ....................................................................................................................................... 120
16.7 Prepare the Signal list ........................................................................................................ 122
16.8 Define Extraction Reports.................................................................................................. 122
16.9 Deploy ................................................................................................................................. 122

17. PerfMon LAN ........................................................................................ 123

17.1 DEFINE A PERFMON RING ...................................................................................................... 124
17.1.1 CREATE A RING FOLDER ............................................................................................................................ 124
17.1.2 EDIT THE RING.INI FILE .............................................................................................................................. 124
17.2 RETRIEVE THE PERFMON ADDRESS ........................................................................................ 125
17.2.1 CREATE AND PREPARE THE SIGNAL LIST ..................................................................................................... 129
17.2.2 DEPLOY A PERFMON RING ........................................................................................................................ 130

18. Upgrade an SCE Project to EcoSUI ...................................................... 131

18.1 Requirements ..................................................................................................................... 131
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 5

18.2 Overview of SCE Project Files ........................................................................................... 131

18.3 Setup EcoSUI ...................................................................................................................... 132
18.3.1 Declare OI & Servers .............................................................................................................................. 132
18.3.2 Specify the Servers IP Addresses .......................................................................................................... 133
18.3.3 Configure your equipments ..................................................................................................................... 133
18.4 Setup Sbus Server Data Acquisition ................................................................................. 135
18.5 Import SCE Mimics files ..................................................................................................... 136
18.5.1 Extract the Image folder .......................................................................................................................... 137
18.5.2 Run the Migration Process ..................................................................................................................... 138
18.5.3 Final Adjustments in EcoSUI .................................................................................................................. 140
18.6 Import a Datapoint Configuration Database ..................................................................... 149
18.6.1 Clear former databases .......................................................................................................................... 149
18.6.2 Load Datapoint Configuration From an SCE Database ......................................................................... 150
18.6.3 Load Datapoint Configuration From a Signal List File ............................................................................ 151
18.7 Generate a ConfPackage ................................................................................................... 152
18.8 Deploy EcoSUI Configuration ............................................................................................ 154

19. Configure EcoSUI from a SET Project .................................................. 157

19.1 Requirements ..................................................................................................................... 157
19.2 Overview of SET Project Files ........................................................................................... 157
19.3 Export the SCD file from SET ............................................................................................ 159
19.4 Setup EcoSUI ...................................................................................................................... 159
19.5 Setup SBUS Server Data Acquisition................................................................................ 160
19.6 Import & fix SCD file ........................................................................................................... 160
19.7 Deploy ................................................................................................................................. 161

20. Configure EcoSUI with SEEFOX .......................................................... 162

20.1 Introduction ........................................................................................................................ 162
20.2 Limitations .......................................................................................................................... 162
20.3 Migration Tool Installation guide ....................................................................................... 163
20.3.1 Compatibility ........................................................................................................................................... 163
20.3.2 Installation Procedure ............................................................................................................................. 163
20.4 Migrating Seefox configuration ......................................................................................... 167
20.4.1 Converting the Seefox configuration into EcoSUI .................................................................................. 167
20.4.2 Importing the converted configuration into EcoSUI ................................................................................ 170

21. Add Supervision Datapoints.................................................................. 171

22. Add a Load Shedding Grid Artifact........................................................ 172
22.1 Introduction ........................................................................................................................ 172
22.2 Generalities ......................................................................................................................... 172
22.2.1 Global features........................................................................................................................................ 172
22.2.2 Cell Features........................................................................................................................................... 172
22.3 Grid configuration file ........................................................................................................ 172
22.3.1 Naming the configuration file .................................................................................................................. 173
22.3.2 [General] Section .................................................................................................................................... 173
22.3.3 [CellCXRY] Section ................................................................................................................................. 174
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 6

1. SCOPE OF THE DOCUMENT

This document is a chapter of the EcoSUI documentation. It describes the engineering process to configure the EcoSUI
and implement the various standard communications protocols in EcoSUI.

2. PREREQUISITE
Refer the Installation chapter (IN) of this product and proceed to EcoSUI software installation prior to use this
document.

Objects and attributes presented in this document are linked to system database configured by EPAS-E or EPAS-
SCE. For a better understanding of this document, it is recommended to be familiar with these two tools.

To add an EcoSUI OI into an existing system, first gather the mapping of the system (IP address, Network names of
equipment…).
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 7

3. REQUIRED DATA ACQUISITION FILES

To define a complete EcoSUI system, three aspects should be taken into account.

• System topology. It consists of device composition that manages the customer’s electrical process.
Generally, this part of furniture is relevant to Schneider-Electric and corresponds to Schneider-Electric system
process definition to respond customer’s needs.

• Electrical topology. It consists of the customer’s electrical process definition in term of typed electrical
devices (transformer, disconnector, circuit-breaker…) that are connected each other through busbars or lines.
Generally, this part of furniture is relevant to the customer.

• Graphical topology. It consists of the mimic and their graphical animation descriptions that appear at
substation control-points (operator interface) and bay control-points (LCD at C264 level). The graphical part
can be done directly in EcoSUI, exported from the SCE (.mpc file) or created from Schneider-Electric HMI
Configuration tool. For further information on this tool, please contact Schneider-Electric Support.

Whatever the type of LAN or protocol selected for your project deployment, EcoSUI always requires specific
configuration files as described in the following chapters.

3.1 THE DATABASE CONFIGURATION FILE

This configuration is stored locally on the SBUS Server.

This is the .SCD file generated by the SCE or SET and available in the .ZIP Databag or by using the ‘Export SCD’
feature of the SCE or SET.
tóm gọn , thâu lược trên lớp SBUS
This SCD file is used by the IEC 61850 acquisition layer (SBUS Access) of SBUS Server.

In a multi-LAN environment, several SCD files are available, one for each LAN. Only the SBUS Server that manages
the LAN needs the SCD file.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 8

3.2 THE SIGNAL LIST

The signals list is stored in the Central DB. It is imported to the Central DB from the ZIP
database created by EPAS SCE or the Profile editor tool.

In a multi-LAN environment, the global signals list is the concatenation of the signals list of
each LAN. The picture on the right represents a Global Signals List of 3 EPAS projects.

The signals of any of the 3 projects can be accessed as if they were part of a unique project
even if they come from different projects or LANs.

This signal list is used by SBUS Servers (to know signal IEC address or alarming/archiving
properties) and EcoSUI HMIs (to map graphic objects with signals).
luồng dữ liệu tới Central DB
Each computer has a local copy of the signals list. This is to limit dataflow to the Central DB.
Those signals are stored in a signalList file.

The local copy is updated if necessary when SBUS Server or EcoSUI HMI starts.

3.3 THE GENERAL.INI FILE

The General.ini file contains general EcoSUI parameters.

3.4 THE MIMICS\GENERAL.INI FILE

The General.ini file contains general EcoSUI parameters related to mimics.

3.5 THE RING.INI FILE

The Ring.ini file contains important SBUS Server LAN properties. This is where the user specifies the type of
protocol and specific settings for deploying an EcoSUI project.

3.6 THE PROFILE.XML FILE

For every different network in the configuration (Ring), a Profiles.XML file is defined. This XML file describes the
attributes to be shared and applied to all the datapoints within the LAN.

3.7 THE SERVERS.INI FILE

The Servers.ini file contains settings in order to configure objects and features (e.g. databases, servers,
archiving, printing, synchronizing).

3.8 THE DISTURBANCEFOLDERS.INI FILE

The DisturbanceFolders.ini file contains settings in order to download disturbance files from IEDs.

3.9 THE GRAPHICAL CONFIGURATION

The graphical configuration describes all the HMI views used by EcoSUI HMI.
The graphical configuration is stored locally on each EcoSUI HMI. Each view is described by a text containing the
properties of each object used in the view. The HMI View configuration can be done:
• ‘Online’ inside the EcoSUI HMI with the EcoSUI HMI Editor. configure graphical
• By importing the graphical part from an SCE configuration
• By importing HMI view files from the the HMI Configuration tool.

The required configuration files generally come from a configuration database set up in EPAS SCE or using SET (.scd
file, signalList & profiles) and then, imported directly to EcoSUI.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 9

4. THE SIGNAL LIST

4.1 OVERVIEW
The SignalList file is a comma-separated value (CSV) text files (.csv).
Separation value: semi-column or comma (can be changed by configuration)

Each value (separated by a comma) is called “Column”.

Top Columns Columns separated by delimiter

It is made up of the concatenation of information detailed below:

Column Value or examples
Top Columns 1 (1st field) {Sitename, SubstationName}: the two first lines MUST start with those barewords.
Top Columns 2 (2nd field) Site name and substation name for tree view
#Type Data point type:
SPS, DPS, MPS, MV, SPC, DPC, STR, SP
If followed by ‘_SYS’, it indicates the data point belongs to System part of tree view (e.g.
SPS_SYS)
#Equipment Equipment name
#Datapoint Address Datapoint Address (IEC 61850, OPC address, Perfmon function, MIB address…)
In our example, it is the IEC 61850 data point reference (separator is also = ‘;‘’)
Example:
• SPS,Station_CEC,IO_BOXCTRL;GGIO1;ST;SPCSO14;stVal
Or • MV,Station_CEC,PP2_7SJ80MEAS;MMXU1;MX;TotPF;mag;f
• DPC,Station_CEC,Depart_1_33kVCTRL;Q0CSWI4;CO;Pos;ctlVal

#Communication link Refer to chapter “Add IED Communication Link Datapoint” for further information.
#Voltage Level Data point Voltage level
#Bay Name Bay name to which belongs the data point (e.g. “Feeder1”)
#Module Name
#Long Name Current Phase A
#Spare YES or NO
#Profile Profile for the data point mentioned. The profile references (data point states) are defined in
profles.xml, for example: SPS_ALARM-NORMAL
#Attributes MV need attributes. Attributes columns are delimited by configured separator
Eg.: value min;value max

NOTE: Lines starting with a hash (#) are ignored. They can be used to comment out a line.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 10

The MV datapoints have the following attributes additional columns

Column
Min
Max
Deadband
Other attributes

For IEC 61850 data acquisition, the user can create the .signallist file automatically using the Profile Studio Tool
and import it to EcoSUI. Note: Profile Studio is an optional tool.

4.2 SIGNAL ATTRIBUTES

There is no limitation on the number of attributes assigned to every signal.
Signal attributes can be displayed on HMI mimics. They can also be displayed on State or Alarm Viewer through
additional columns. For this, the attributes shall be referred by using their position-number.
Example of Signal Attribute Usage:

4.3 SPECIFY / CHANGE THE SEPARATOR

In the Ring.ini file, use the following parameters to change the separator to be applied in the SignalList file:

Parameter name Description Default Values

;
SignalListColumnDelimiter Delimiter for columns of the .SignalList file
SignalListColumnDelimiter=;
Delimiter for 61850 addresses in $
SignalListAddressDelimiter
.SignalList file SignalListAddressDelimiter=$

4.4 ADD COMMUNICATION LINK DATAPOINT

It is possible to add a communication link datapoint to the .signallist file in order get the communication link between EcoSUI
and an "IED" equipment.
Open the .signallist and enter EQUIPMENTCOMMUNICATION, in the 3rd column, instead of the datapoint address.
Example:
SPS_SYS;IED;EQUIPMENTCOMMUNICATION;Network;IED;;Communication link status;NO;SPS_SET-RESET

In this example, the datapoint System/Network/IED/Communication link will return the link between 'EcoSUI and "IED"
equipment.

Note:
- Automatically added by SCE on each IED in configuration (called Device link)
- By default, 1 link per IED (= computed link)
- Possible by configuration to create 1 link per SBUS Server + 1 computed link (parameter MultipleDeviceLinks in
ring.ini)
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 11

Ring.ini section related to multiple device link:

MultipleDeviceLinks_Help=
When 1, use one IED device link per acquisition (In signallist, declare for each IED, several SPS with address
'equipmentcommunicationX' (with X from 0 to 3) and one SPS with address 'equipmentcommunication' which will be a
computed device link (true when one of other SPS is true).

From SCE one device link will be created by enabled equipment with index starting from 1 to 4 as description
(e.g. : Device link Acq1) and one computed device link will be created also).

When 0 (default value), there is only one IED device link for all acquisitions (In signallist, declare for each IED, only
one SPS with address 'equipmentcommunication')

4.5 EXAMPLE OF DATA POINTS

4.5.1 SPS
SPS data point is a single-point-status type.

4.5.2 DPS
DPS data point is a double-point-status type.

4.5.3 MPS

MPS data point is a double-point-status type.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 12

4.5.4 DPC
DPC is a double-point-control type data point.

4.5.5 MV
MV is a measurement data point.

4.5.6 STR

4.5.7 SP
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 13

5. THE GENERAL.INI FILE

5.1 OVERVIEW
The General.ini file contains general EcoSUI parameters.

It may be necessary to edit this file and setup the parameters based on project needs.

The General.ini is located under folder C:\MCIS

The parameters in the General.ini file are gathered into dedicated section. Follow the links to know how to manage
these parameters:

• [Database]
• [General]
• [Supervisor]
• [Languages]
• [Alarms]
• [SaveToFile]
• [SBUSServer]
• [Project]
• [AutomaticExport]
• [AlarmFileExport]
• [Dummy]
• [Security]
• [Curves]
• [Mimics]
• [StateViewer]
• [EventViewer]
• [VCR]
• [CurveTooltips]
• [Feedbacks]
• [Events]
• [Chromium]
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 14

5.2 POSSIBLE PARAMETERS

5.2.1 [DATABASE]
Parameter Description Values
MySQLSettingsPath This is the MySQL configuration file's path:
e.g. C:\ProgramData\Schneider-Electric\EcoSUI\EcoSUI.config
NOTE: DO NOT EMBED INTO YOUR EcoSUI CONFPACKAGE
LastDatabaseStructureUpdate_Supervisor_AllTables Internal (do not modify). Software version of last database upgrade. If the
software version changes, a database upgrade will be done at software startup.
LastDatabaseStructureUpdate_SBUSServer_Software Internal (do not modify). Software version of last database upgrade. If the
software version changes, a database upgrade will be done at software startup.
SaveStatesToDatabase 1 to send states to recordedstates database table
0 by default to NOT send states to recordedstates database table
SaveStatesToDatabaseTimeFrame Integer. Time in seconds to wait after first 30 by default. Accepted values
state reception, to save the received states from 1 to 300 (300s = 5 min)
in database

5.2.2 [GENERAL]
Parameter Description Values
Timestamping Timestamping reference used to display any Local by default. Accepted values are
information on SBUS Servers and HMIs. UTC or Local
ModuleNameIsBayName Module name to have the bay name or the correct 1 module name is by bay name
path to the point. 0 module name is the path to the point
MainWindowLeft Main window displaying 0 by default
MainWindowTop Main window displaying 0 by default

Other additional paramters can be managed in General section. See below examples:
PropertyWindowLeft=1950
PropertyWindowTop=4350
PropertyWindowWidth=19785
PropertyWindowHeight=9015
LibraryWindowLeft=390
LibraryWindowTop=645
LibraryWindowWidth=24000
LibraryWindowHeight=14010
General_NavWindowCanClose="0"
General_NavWindowTitle="Navigation Window"
General_NavWindowBackgroundImageFilename=
General_NavWindowBackgroundColor="255;255;255"
General_NavWindowWidth="200"
General_NavWindowHeight="100"
General_NavWindowPosX="100"
General_NavWindowPosY="100"
General_Width="100"
General_Height="300"
General_ExecActionOnEvent_Formula=
General_ExecActionOnEvent_Action=
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 15

5.2.3 [SUPERVISOR]
Parameter Description Values
AutomaticallyRepairMySqlOnComputerFailure 0 by default to warn the user that computer restarted after a power failure and
advise to do a check and fix operation.
1 to automatically check and fix operation at Supervisor startup after a power
failure.
AutomaticRepairApplicationStartupDelay The time, in seconds, Supervisor will wait Accepted values from 1 to 300
applications to complete startup before (300s = 5 min)
stopping them for the automatic check and
fix process.

Other additional paramters can be managed in General section. See below examples:
Generator_ConfPackageGatewaysPath=C:\MCIS\Gateways
Generator_ConfPackageMimicsPath=C:\MCIS\Mimics
Generator_ConfPackageRingsPath=C:\MCIS\Rings
Generator_ConfPackageName=
Generator_ConfPackageFormulasPath=C:\MCIS\Formulas
AutomaticallyImportDatabase_ExportFolder=C:\MCIS\ConfPackages\DemoPackage\Export
AutomaticallyImportDatabase_CentralDBIP=localhost
AutomaticallyImportDatabaseAtStartup=0

5.2.4 [LANGUAGES]
Parameter Description Values
CurrentLanguage Application language English.lng by default

5.2.5 [ALARMS]
Parameter Description Values
EnableAlarmAckClearInEvents Alarms acknowledge and Alarm 1 (default) adds alarm ack + alarm clear to events
clear to events 0 to disable
HighestAlarmLevelIsHighestGravity Alarms gravity 1 (default) the highest alarm level is the highest
gravity.
0 the lowest alarm level is the highest gravity (with
alarm level > 0)
AddOneEventForEachAckOfAckAllOrAckPage Add event 0 by default. AckAll or AckPage will add only one
event
1 adds one event to each ackowledged alarm
ReplaceUncertainByQualityDescription Alarm description display 0 (default) uncertain message is displayed
1 the current quality of the alarm is displayed instead
of uncertain
InvalidQualitySignalsCanTriggerAlarms Invalid signals to tigger alarms 1 (default), invalid quality signals can trigger alarms
0 invalid quality signals will not trigger alarms
TestQualitySignalsCanTriggerAlarms Test signals to tigger alarms 1 (default) test quality signals can trigger alarms.
0 test quality signals will not trigger alarms
SubstitutedQualitySignalsCanTriggerAlarms Substituted signals to tigger alarms 1 (default) substituted quality signals can trigger
alarms.
0 substituted quality signals will not trigger alarms
ForcedQualitySignalsCanTriggerAlarms Forced signals to tigger alarms 1 forced quality signals can trigger alarms.
0 (default) forced quality signals will not trigger
alarms
DisconnectedIED_DeleteAlarms Disconnected IED alarm 1 (default) alarm of disconnected IED will be deleted
0 alarm of disconnected IED will NOT be deleted
DisconnectedIED_ChangeAlarmQualityTo Only if DisconnectedIED_DeleteAlarms=False
1 (default) signal quality of alarm will not be changed
>0 alarm quality will be updated to a new quality
(0=valid, 1=disconnected, 2=invalid, 3=Forced, 4=Questionnable, ...)
DisconnectedIED_DeactivateAlarms Only if DisconnectedIED_DeleteAlarms=False
0 (default), active alarms remain active.
1, active alarms will be made inactive
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 16

Parameter Description Values

DisconnectedIED_ChangeMessage Only if DisconnectedIED_DeleteAlarms=False
If empty, alarm message will not be updated
If not empty i.e.Unknown, message will be replaced
BadQualitySignals_DeactivateAlarm Alarms when signal quality is not 0 (default), to not deactivate alarm when signal
valid quality becomes not valid.
1 to deactivate alarm when signal quality becomes
not valid
BadQualitySignals_ChangeMessage Messages when signal quality is not If empty, alarm message will not be updated if signal
valid quality becomes not valid.
If not empty i.e.Unknown, message will be replaced
if signals becomes not valid
SubstationLRMnemonic Put a substation L/R mnemonic here to stop buzzer Path of the LR mnemonic
when substation is in L/R
AutoStopBuzzerIfInRemote Stop buzzer when back in local If 1, substation in remote and new alarms appear,
the buzzer will not sound when substation will be
back in local.
AutoAckAlarmsIfInRemote If 1 and substation in remote, new alarms will be automatically acknowledged.
BuzzerPlayCurrentHighestGravity Buzzer 0 (default) buzzer is for the the highest gravity alarm
ever received
1 buzzer is for the current highest alarm active in
base
AutoAckAutoClear_AttributeIndex This Option lets you This parameter indicates the attribute number.
autoack/autoclear alarms according -1 to disable.
to a datapoint defined in one Remark: You can use special keywords
attribute of the alarmed datapoint (e.g. 'autoack', 'autoclearifinactiveacked',
'autoclearifinactive', 'autoackthenautoclearifinactive')
AutoAckAutoClear_Username Acknowledged by username When AutoAckAutoClear_AttributeIndex <> -1, this
is the username used to fill Acknowledged By
column

5.2.6 [SAVETOFILE]
Parameter Description Values
Delimiter Separator used when exporting 0 Comma
curve data 1 Semi-Colon
2 Tab
SeparateMilliseconds

5.2.7 [SBUSSERVER]
Parameter Description Values
AttributeColumnIdx Enable/disbable Attribute column -1 to disable it in eventviewer and alarmviewer.
x to show it in column x
SecondAttributeColumnIdx Enable/disable a second Attribute column -1 to disable a 2nd attribute column in
eventviewer and alarmviewer.
x to show it in column x
CheckFormulaEveryXInMs To check/update formulas every X milliseconds. 250 ms by default
DescriptionsToHide Signals with that description will be hidden from Signal description
SBUS Server State viewer
KillSbusAxsAtStartup To kill all SbusAxs.exe when SBUS Server 0 disabled
starts 1 enabled
KillSbusAxsAtExit To kill all SbusAxs.exe when SBUS Server exits 0 disabled
1 enabled
ShowFlagsColumnInStateViewer Flags column in Stateviewer 1 to show it
0 to hide it
FlagsColumnWidthInStateViewer Flags column width Stateviewer DefaultFlagsColumnWidthInAlarmViewer
ShowFlagsColumnInEventViewer Flags column in EventViewer 1 to show it
0 to hide it
FlagsColumnWidthInEventViewer Flags column width EventViewer DefaultFlagsColumnWidthInAlarmViewer
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 17

Parameter Description Values

ShowFlagsColumnInAlarmViewer Flags column in AlarmViewer 1 to show it
0 to hide it
FlagsColumnWidthInAlarmViewer Flags column width AlarmViewer DefaultFlagsColumnWidthInAlarmViewer
HideAfterStart
FixSCDHasToBeAsked For the user to be asked for SCD fixing, knowing 1 (default) to ask
there could be incidence on the behavior of the 0 to not ask
communication with recent generation tools
FixSCDForced To force SCD fixing 1 (default) to force SCD fixing if user is not
asked for the action to do
0 to avoid SCD fixing in case user is not asked
for the action to do

Other additional paramters can be managed in SBUSServer section. See below examples:
AlwaysOnTop=1
Alarms_SignalListVisible=1
Alarms_ShowToolbar=1
Alarms_ShowSummary=0
chkShowSummary_CheckedChanged=
DefaultFlagsColumnWidthInAlarmViewer=30
DefaultFlagsColumnWidthInStateViewer=30
DefaultFlagsColumnWidthInEventViewer=30
Filter0=
Filter1=
HideAfterStart=0

5.2.8 [PROJECT]
Parameter Description Values
LookForScriptsAndFormulasInLocalhostFolder To look for scripts and formulas in localhost folder 0 disabled
instead of computername folder 1 enabled

5.2.9 [AUTOMATICEXPORT]
Parameter Description Values
Enabled Automatic export 0 to disable
1 to enable
EveryXDays Automatically export every X days at time H:M x days
LastXDays Number of days that will be exported x days
ExportFolder Folder in which exports will be located Path to related folder
ExportAtHourH Automatic Export will be run at this time (hour) H:M
ExportAtMinuteM Automatic Export will be run at this time (minute) H:M
UseFolderHierarchyAsTimestamp If 1, export will be stored in a folder hierarchy i.e. ExportFolder\2015\12\28

5.2.10 [ALARMFILEEXPORT]
Parameter Description Values
EnableAlarmFileExport Alarm File export 0 (default) to disable
1 to enable
AlarmFilesFolderAFE Folder where Alarm files will be created C:\MCIS\AlarmsFilesExport (default)
ListofAlarmsFileAFE If no file is specified, a default file will be created named AlarmConfiguration.csv under specified
folder.
Heartbeat Heartbeat system (creates a heartbeat file when alarm 0 (default) to disable heartbeat
didn't change depending of the configuration) 1 to enable
HeartbeatTick Time between each heartbeat file creation in minutes From 1 min to 120 min
HeaderAlarmFileTranslation Change value of AlarmFile header AlarmFile by default
ShowDeamonLine Deamon line 0 to disable
1 (default) to enable Deamon line
ShowExecutable Name of the application 0 (default) to disable
1 to enable name of application
AlarmHeartbeatTranslation Change value of AlarmHeartbeat header Heartbeat by default
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 18

Parameter Description Values

AlarmMessageTranslation Change value of AlarmMessage header AlarmMessage by default
AlarmTypeTranslation Change value of AlarmType header AlarmType by default
AlarmPriorityTranslation Change value of AlarmPriority header AlarmPriority by default
AlarmTimestampTranslation Change value of AlarmTimestamp header AlarmTimestamp by default
ExportLocalTime Export UTC or Local 0 to export UTC date
1 to export Local date
ExecutableName Change value of AlarmTimestamp header Change value of field executable name:
SBUS Server by default

5.2.11 [DUMMY]
Parameter Description Values
ComputerUnlockProfiles Profiles allowed to unlock the computer when List of profiles separated by ';'
logging + unlock mimic edition in HMI.

Other additional paramters can be managed in Dummy section. See below example:
Dummy=1

5.2.12 [SECURITY]
Parameter Description Values
UsersInDB (Obsolete) Users are located in Database instead of file 0 to disable
1 to enable

5.2.13 [CURVES]
Parameter Description Values
ShowInvalidLabel

5.2.14 [MIMICS]
These are examples of the parameters that can be managed in Mimics section:
RefreshMimicsIfNecessaryEveryXMillisec=500
RefreshMimicsEveryXMillisecWhenBlinking=100
ForceRefreshEveryXSeconds=60

5.2.15 [STATEVIEWER]
Parameter Description Values
NbMaxOfRegisteredSignals Authorizes to sort by date if the number of signals is lower than this number e.g. 1000

5.2.16 [EVENTVIEWER]
Parameter Description Values
PageSize When reading events, loading is divided in pages of x events. Before 10000 (default)
R16236, default (hardcoded) was 1000
Live_NbOfEvents Number of events shown in real-time events 1000 (default),
NbMaxOfEventsInViewer Maximun number of events that will be shown in EventViewer. By 250000 (default)
increasing this number, you may face OutOfMemory Errors
FilterOnQueryResult Set to 1 if the quality, event type and bit change filters should apply on 0 to disable
the result of the mysql query instead inside the MySQL query. it will 1 to enable
reduce the number of events retrieved but fasten the filtering
TimeSpanLimit The number of hours back in time after which the live events will not be Integer (number of hours)
retrieved when FilterOnQueryResult is enabled
ShowStatusMessage Status label on top of the event list True (default) to show it
False to hide it
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 19

5.2.17 [VCR]
These are examples of the parameters that can be managed in VCR section:
VCR_DateWidth="135"
VCR_OriginWidth="330"
VCR_NameWidth="220"
VCRWidth=12765
VCRHeight=7620
VCRTop=6075
VCRLeft=14625
VCRLongDateFrom=1599132266
VCRLongDateTo=1599132566
VCRExclude=
VCRHighlight=
VCRCycle=0
VCRUpdateCurves=0
ShowFilters=1
ShowTreeview=0
VCRInclude=

5.2.18 [CURVETOOLTIPS]
These are examples of the parameters that can be managed in CurveTooltips section:
DefaultLastXMinutes="15"
ShowTooltips="1"
ShowGlassEffect="1"
ShowLegend="0"
ShowMinMax="0"
ShowScale="1"
ShowTitle="1"
ShowTimeScale="1"
ShowHorizontalGrid="1"
DrawSplineCurves="1"
NbOfHorizontalTick="1"
NbOfVerticalTick="3"
TooltipBackcolor="242,242,242"
ChartBackcolor="162,197,165"

5.2.19 [FEEDBACKS]
Parameter Description Values
DifferentiateOrderSentAndSelectSent 0 (default) feedback when a control is selected is Order in Progress (like when executing a
control).
1 feedback when a device is selected is Select in Progress

5.2.20 [EVENTS]
These are examples of the parameters that can be managed in Events section:
SiteSignalBackColor="13158600"
SystemSignalBackColor="9868950"

5.2.21 [CHROMIUM]
These are some parameters that can be managed in Chromium section:
Args
LogSeverity
MultiThreadedMessageLoop
DownloadDefaultFolder
IgnoreCertificateErrors
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 20

6. THE MIMICS\GENERAL.INI FILE

6.1 OVERVIEW
The Mimics\General.ini file contains general EcoSUI parameters concerning the mimics.

It may be necessary to edit this file and setup the parameters based on project needs.

The Mimics\General.ini is located under folder C:\MCIS\Mimics

The parameters in the Mimics\General.ini file are gathered into dedicated section. Follow the links to know how to
manage these parameters:

• [Debug]
• [General]
• [Version]
• [MimicDrawing]
• [Buzzer]
• [Feedback]
• [HMI]
• [Tooltips]
• [SetPoints]
• [QualityHandling]
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 21

6.2 POSSIBLE PARAMETERS

6.2.1 [DEBUG]
These are examples of the parameters that can be managed in the Debug section:
DisableAudio=0
DontDisposeItemsAndMimics="0"
DontAutoHideTaskBar=0

6.2.2 [GENERAL]
Parameter name Description Expected value
DeleteCompiledFolder To delete or NOT delete compiled folder 0 DOES NOT delete compiled
folder
1 (default) deletes compiled folder
RequiredNbOfScreens Enable/disable scroll bar (number of required 0 to disable scroll bars
screens) 1 to enable scroll bars
UserActiveTimeout Automatic logoff after defined time in millliseconds 0 to disable auto logoff
1 to enable auto logoff
MillisecondsBeforeShowingTooltip Time in milliseconds (ms) before showing tooltips 0 to disable
(curve tooltip, ...) on mimics x ms (500 ms default)
CentralizeModificationsOnCentralDB Modifications done on this computer will be sent 0 to disable
to Central DB and deployed on other computers 1 to enable
UseCompiledMimicFiles Use mimic compiled files (decrease mimic 0 to disable mimic compiled file
opening time) 1 to enable mimic compiled file
SignalSelectionReturnsPath If 1, signal selection returns site-x.subst-y,voltlevel-z...
If 0, signal selection returns Subst / VoltageLevel / Bay
DontDisableWorkspaces If 1, prevent workspace disabling (used to disable a workspace when another workspace
opens over it)
NbOfTrendsInAGraph Define the maximum number of trends in a Curve Object (Default is 8)
RestrictUserActionToOneFolder 0, user can browse/load/save files anywhere
1 to restrict to one folder
RSSNotification_Enabled RSS Notification 0 to disable RSSNotification
1 to enable RSSNotification
ForceLowQualityResize Force low quality when resizing image (doesn’t take into account Picture_ResizeQuality
parameter)
ShowUnknownSignalWithHelpImage Replace dynamic pictures by a ? for signals not 0 to disable
found in database 1 to enable
LogOffAction Action that will be executed when a user log off or when autologoff. Action has to be
separated by a comma (,)
LogInAction Action that will be executed when a user logs in
ShowUnknownSignalWithUnknownState Set Unknown picture for signals not found in 0 to disable
database 1 to enable
StopBlinkWhenAlarmInactive If set to 1, object will not blink when alarm turns to Inactive
UseSmartActionSplit 0 (default) to use old way to split actions (separated by \n)
1 to use smart split (do not split \n inside parenthesis)
InterlockViewer_TabStyle Interlock Viewer 0 to have classic tab style
1 to have flat tab style
InterlockViewer_AddInterlockNameToTitle Interlock name in the title bar 0 1 to NOT add interlock name
1 to add interlock name (open,
close, ...) in title bar
ViewPDFExportsAfterGeneration 0 to inhibit viewing of PDF exports after generation
1 to allow viewing
UseCommentFeatureExtension If 1, change scope of comments and link alarm and event comments to the related alarm
or event datapoint.
If 0 (default), keep scope of a comment to an alarm or an event.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 22

Parameter name Description Expected value

CanClearCommentedAlarms Property unused if UseCommentFeatureExtension is reset. Otherwise:
If 1, user can clear commented alarms
If 0 (default), only uncommented alarms may be cleared
EnableNavigationWithArrowKeys Navigation with arrow keys 0 to disable
1 to enable
AllowTemplateFieldEdition 0 (default)
1 if you really handle what you do, and you do not use group- in-group instanciation

6.2.3 [VERSION]
These are examples of the parameters that can be managed in the Version section:
Major=1
Minor=0
Revision=2198

6.2.4 [MIMICDRAWING]
These are examples of the parameters that can be managed in the MimicDrawing section:
UseCachedBitmaps="0"
DrawTextWithGDIP="0"
DrawTexts="1"
DrawBitmaps="1"
DrawShapes="1"

6.2.5 [BUZZER]
Parameter name Description Expected value
PlayWavSound Sound for the buzzer 0 To use PC buzzer
1 to use a wav file instead
WavFilename File name of the wav file
e.g. C:\MCIS\Mimics\Buzzer.wav

WavFilename_0 Available properties are WavFilename_x where x corresponds to alarm level x (x = 1 to

15). The highest active alarm level determines the wav played
Examples
WavFilename_0="C:\MCIS\Mimics\Buzzer.wav"
WavFilename_1="C:\MCIS\Mimics\Buzzer.wav"
WavFilename_2="C:\MCIS\Mimics\Buzzer.wav"
WavFilename_3="C:\MCIS\Mimics\Buzzer.wav"
WavFilename_4="C:\MCIS\Mimics\Buzzer.wav"

6.2.6 [FEEDBACK]
Parameter name Description Expected value
AddCommandDescriptionToFeedbackMessage To add the command description (i.e. OPEN, 0 to disable
CLOSE, ...) to feedback message 1 to enable
FailureFeedbackInDifferentColor To have failure feedback in different color. Color will 0 to disable
be OffColor in dynamic text instead of OnColor 1 to enable

6.2.7 [HMI]
DescriptionsToHide=
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 23

6.2.8 [TOOLTIPS]
Parameter name Description Expected value
DisableCurveTooltips When 1, disable curve tooltips globally. No more curve tooltips over analog values

6.2.9 [SETPOINTS]

Parameter name Description Expected value

DisableDot 0 to authorize dot (.) in SETPOINT and SETPOINTEX actions. Also, for TextBox when
NumericOnly.
1 to disable
DisableComma 0 to authorize comma (,) in SETPOINT and SETPOINTEX actions. Also, for TextBox
when NumericOnly.
1 to disable

6.2.10 [QUALITYHANDLING]
Parameter name Description Expected value
ConsiderInvalidAsValid C264 has a bug, setting quality=invalid for DPS in jammed or undefined position. When
set to 1, invalid signals will be considered valid

Other additional paramters can be managed in the QualityHandling section:

ConsiderBadReferenceAsValid="0"
ConsiderDisconnectedAsValid="0"
ConsiderFailureAsValid="0"
ConsiderInaccurateAsValid="0"
ConsiderInconsistentAsValid="0"
ConsiderOldDataAsValid="0"
ConsiderOperatorBlockedAsValid="0"
ConsiderOscillatoryAsValid="0"
ConsiderOutOfRangeAsValid="0"
ConsiderOverflowAsValid="0"
ConsiderQuestionableAsValid="0"
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 24

7. THE RING.INI FILE

7.1 OVERVIEW
The Ring.ini file contains important SBUS Server LAN properties.
This is where the user specifies the type of protocol and specific settings for deploying an EcoSUI project.
It may be necessary to edit this file and setup the parameters based on the protocol in use.
The Ring.ini is located under folder C:\MCIS

The parameters in the Ring.ini file are gathered in the following dedicated sections. Follow the links to know how to
manage these parameters:

• [Ring]
• [SBUSAccess]
• [RedundantC264]
• [LogbookPrinterManager]
• [IEC61850]
• [LogicalRing]
• [HotHotRedundant]
• [OPC]
• [EXTERNAL DLL]
• [SCE]
• [AutoGI]
• [Disconnection]
• [DeviceSynchro]
• [IncorrectTimeStamp]
• [SBUSServerRedundancy]
• [InitialValues]
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 25

7.2 POSSIBLE PARAMETERS

The sections and their parameters in the Ring.ini files are filled automatically as the EcoSUI requires them based on
protocol needs. This means that depending on the protocol used, the parameters to configure can vary:

7.2.1 [RING]

Parameter Name Description Expected Values

Type Type of the protocol used by the EcoSUI LAN. EFIP, IEC61850, PERFMON, OPC, OW,
RFXCOM, ZWAVE, MODBUS,
EXTERNALDLL, SPACE2k, GOOSE,
ECOGTW, TOPO or VIRTUAL (NO
ACQUISITION)

Enabled List of computer names (separated with ;) where this ring is enabled.

The first one is considered main SBUS Server. The second one is considered backup SBUS Server,
e.g.: OIS_M;OIS_B

In case of OI Server redundancy, DB names must match PC names:

SignalListColumnDelimiter To set column celimiter of the SignalList file ; by default.

SignalListAddressDelimiter To set the address delimiter of the SignalList file $ by default.
MultipleDeviceLinks When 1, use one IED device link per acquisition (In signallist, declare for each IED, several SPS with
address 'equipmentcommunicationX' (with X from 0 to 3) and one SPS with address
'equipmentcommunication' which will be a computed device link (true when one of other SPS is true),
from SCE one device link will be created by enabled equipment with index starting from 1 to 4 as
description (e.g. : Device link Acq1) and one computed device link will be created also).
When 0 (default value), there is only one IED device link for all acquisitions (in signallist, declare for
each IED, only one SPS with address 'equipmentcommunication')
SiteID This parameter is only used during import from SCE. 1 keeps SCE-Site ID
It allows the use of Site ID generated by SCE or Any number > 1 to replace the ID with
change these IDs. such number
SCSID This parameter is only used during import from SCE. 1 keeps SCE SCS ID.
It allows the use of the SCS ID generated by SCE or Any number > 1 to replace the ID with
change these IDs. such number
SubstID This parameter is only used during import from SCE. 1 keeps SCE substation ID
It allows the use of the substation ID generated by Any number > 1 to replace the ID with
SCE or change it. such number.
AutoDisturbanceDownload Automatic disturbance download. 1 to enable automatic download

0 to disable automatic download

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 26

Parameter Name Description Expected Values

EcoSUI uses the Disturbances folder file to retrieve

the path in the IED where disturbance data is stored.

The user should manually fill in this path in the

Disturbance folder IED key section of the
Disturbances folder file.
ExcludedEquipment This parameter is only used during import from SCE. List of equipments separated by a ';'

When loading the S2kloader.xml file, all signals from Example :

these equipment will be ignored. Very useful to OI_Main;OI_Backup;External_clock_
exclude IEC/IEC gateway in multiple rings. Reload 1
the configuration after each modification

ExcludedPath This parameter is only used during import from SCE. List of path separated by a ';'

When loading the S2kloader.xml, all signals from the Example:

specified path will be ignored. site-1.subst-3;site-2.subst-4

Very useful to exclude IEC/IEC gateway in multiple

rings. Reload the configuration after modification.
HasSecondaryLanguage Obsolete parameter 0 to disable secondary language,
Enables / Disables secondary language 1 to enable secondary language
AutomaticGI_EqptTypeList To avoid unexpected behaviors on P40 series List of equipments where this automatic GI
concerning device status. option is enabled.
This parameter requests a GI (general interrogation) Separate each type with a ';'
when a JAMMED position is received. Example. P142;P143
AutomaticGI_WaitTime When a JAMMED position is received, EcoSUI waits In milliseconds
for x milliseconds before sending a General
interrogation to the IED in order to get the latest
correct status.
DefaultIntegrityPeriodForMXInM Forces the IEC Equipment to send MX values every In milliseconds
s X milliseconds even if their state didn't change
DefaultIntegrityPeriodForSTInM Forces the IEC Equipment to send ST values every In milliseconds
s X milliseconds even if their state didn't change
SCDVersion=? Read only
DBVersion=? Read only
IEC61850_AcqVersion Version of IEC 61850 Acquisition. Version 2 by default
Note : This is not about IEC 61850 Protocol version I
or II
IEC61850_GatewayNames This parameter is used to adjust SCD file which List of the IEC/IEC gateways separated by ';'
contains some non- valid data about IEC/IEC Ex: GTW_IEC;GTW_BCK
gateways.
During import from SCE, EcoSUI updates the file by
adding the necessary signals
Scada_GatewayNames This parameter is used to adjust SCD file which Lists the SCADA gateways separated by ';'
contains some non- valid data about IEC/IEC
gateways.
During import from SCE, EcoSUI updates the file by
adding the necessary signals
AddRingNameToIECAddress Helps to prevent confusion between IED Addresses 1 when managing multiple LANs
when managing the same IED names over different 0 when managing 1 LAN (default value)
LANs.
AlternateMethodToComputeUID32 Obsolete parameter
When 2 objects in s2kloader.xml lead to the same
uid32, we can try to compute uid32 with alternate
method. 1 to use alternate method. 0 By default
SignalListVersion Version of .SignalList file 2 by default
1 helps to ensure retrofit compatibility on
former projects
EthernetNetID Keeps the EthernetNetwork ID generated by SCE. 1 keeps SCE-generated ID
Any number > 1 to replace the ID by this
number
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 27

Parameter Name Description Expected Values

VoltLevelID Keeps the Subst ID generated by SCE. 1 keeps SCE-generated ID
Any number > 1 to replace the ID by this
number
MultiAccessPointConfiguration IED access point (AP) 0 for configurations with IEDs with mono AP,
1 if at least one IED with multi AP

MultiAccessPointShowIEDSameAPO Acquisition tab to show all the IEDs in the SCD file or 0 shows all available IEDs from SCD in the
nly only the current connected AP acquisition tab,
1 shows only IEDs connected to the current
connected AP
UseReportCapabilities Use report capabilities instead of using standard 0 standard parameters (default)
parameters
FilterReccuringEventWithSameSt Events filtering 1 to filter events with same value on
ateOnMultiPhaseStatus Multiphase status (ie. multiphase trips)
2 to filter those events but keeping the date.
0 (default) to keep these events
RemoveUnusedLN to remove LN without DataSet 0 disabled
1 enabled

7.2.2 [SBUSACCESS]
Parameter Name Description
UDPPortIn In case of multiple 61850 LANs, it is recommended to differentiate UDP ports used by SBUSAccess interfaces
• The UDPPortIn parameter specifies the UDP Port Input.
• SBUSAccess receives requests from this UDP Port Input.
If the workstation manages several LANs, this UDP Port Input must be unique to be able to connect to the
agency.
UDPPortOut In case of multiple 61850 LANs, it is recommended to differentiate UDP ports used by SBUSAccess interfaces
• The UDPPortOut parameter specifies the UDP Port Output
• SBUSAccess sends results from this UDP Port Output.
If the workstation manages several LANs, this UDP Port Output must be unique.

MaxCallingConnection Default value is 99

7.2.3 [REDUNDANTC264]
Parameter Name Description Example
MainC264 Specify each main redundant C264 MainC264=RedundantC264

7.2.4 [LOGBOOKPRINTERMANAGER]
Parameter Name Description Expected Values
MainIPAddress Each SBUS Server can manage one Logbook Printer. Empty if logs are not sent to a printer
In that case, it becomes a ‘Logbook Printer Manager’. manager
It receives events to print from a TCP connection.
This parameter specifies the IP Address of the Main SBUS Server
LogbookPrinterManager.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 28

BackupIPAddress IP Address of the Backup SBUS Server LogbookPrinterManager. Empty if logs are not sent to a printer
manager
FilterGI Do not send to log book General Interrogations 1 to filter (default value)
PrintUppercase Print All in uppercase 1 to Print All in uppercase

7.2.5 [IEC61850]
Parameter Name Description Expected Values
TapchangerLowerCommand For tapchanger lower control, specify Default is 'off;Dbpos'
the IEC 61850 CtlVal parameter.
ManageTapChgTransInd When using TapChg$valWTr$transInd 0 by default
1 when using TapChg$valWTr$transInd
EnableLPHDReport For LPHD report 0 by default, to not enable LPHD report (if found) for devices
1 enables the LPHD report for the devices if found (for Buffer
Overflow management on C264 for example) vices if found
OrCat 2 (default) orCat of StationControl
1 orCat of BayControl
3 orCat of RemoteControl
ForceOrIdent Empty to send HMI username in orIdent, a string to force orIdent. Use 0x... (ie 0x8A) if you want to send
strings declared in hexadecimal
AppendOrIdent If set, append a string on OrIdent
AskForDataRefInReport Help debug report from device 0 (default) to not ask for the data reference in the reports
1 enables data reference in the reports. It should be used for
debugging only
ForceOrIdent_Substition Empty to send HMI username in orIdent, a string to force orIdent for Substitution.
NOTE: You CANNOT use 0x... (ie 0x8A) if you want to send strings declared in hexadecimal. Not
permitted on Substitution
SendFSSAtOnce Manage FSS to the device 0 (default), to send FSS leaf by leaf as per Ed2 requirements,
1 to send FSS all at once: it will send all the subVal, subQ,
subEna and subId in one single request instead of one by one.
SetpointSendDate Setpoint date and time 1 to send the date and time in the setpoint
0 to not send the date and time in the setpoint
SetpointSendCheckByte Setpoint check byte 1 to send the check byte with real value in the setpoint,
0 to send 00 all the time

7.2.6 [LOGICALRING]
Parameter Name Description Expected Values
IsLogicalRing One LAN in split into several logical LANs. 1 if this LAN is a logical LAN
IEDToExclude List of IED (separated by ;) to be excluded from this logical LAN to avoid SbusAxs unexpected
behaviors (optional).
An IED cannot be in Exclude and Include mode at the same moment.

IEDToInclude List of IED to Include into this logical LAN. List of IEDs separated by ;
An IED cannot be in Exclude and Include mode at the same
moment.
RingName Define the LAN name of the logical LANs
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 29

7.2.7 [HOTHOTREDUNDANT]
Parameter Name Description Expected Values
NameOfIEDMain NameOfIEDBackup. The name of the IED used as backup in a
Hot/Hot redundancy configuration
HotHotRedundant Add one row in this section for each main Modbus MainDeviceName=RedundantDeviceName
device equal to its redundant pair e.g. PLC_A=PLC_B

7.2.8 [OPC]
Parameter Name Description
MainServerURL URL of the main OPC Server
Ex : //localhost/Matrikon.OPC.Simulation.1
BackupServerURL URL of the backup OPC Server

7.2.9 [EXTERNAL DLL]

Parameter Name Description Expected Values
DllName Name of the dll Name of the dll
AddEqptConnectionSignals 0 disabled
1 enabled
ProtNB When more than one modbus LANs is Integer identifying the protocol number
defined in the same computer, a different
Protocol Number shall be assigned to
every LAN.
This protocol number will be used for
naming the XML file describing the
modbus protocol.
E.g. L_modbus_xml_[protnb].xml
Where [protnb] is the protocol number
defined in [ExternalDLL]/ProtNb
AutoRestartAcq 0 disabled
1 enabled
AutoRestartAcq_FilterXSeconds 0 disabled
AfterRestarting 1 enabled
AutoRestartEqpt_List Automatically restarts TCP Connection EquipmentName1#Period1;EquipmentName2#Period2;...
with equipment every X Minutes e.g. MYSEPAM#60;MYSISGTW#30

7.2.10 [SCE]
Parameter Name Description Expected Values
RebuildSiteSCSNodes to update site-x.subst-y... when necessary (conflict with 0 to do nothing
another SCE configuration) 1 to rebuild
MainOIServerName Network Name of the Main OI Server Leave empty to automatically select
server name
BackupOIServerName Network Name of the Backup OI Server Leave empty to automatically select
server name
OIServer3Name Network Name of the OI Server 3 Leave empty to automatically select
server name
OIServer4Name Network Name of the OI Server 4 Leave empty to automatically select
server name

7.2.11 [AUTOGI]
Parameter Name Description Expected Values
IEDName Used to automatically request a value every X Minutes NameOfIED=x where x is the
to keep communication active with the device number of minutes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 30

7.2.12 [DISCONNECTION]
Parameter Name Description Expected Values
KeepValue values of signals from disconnected 0 default
IED are unknown (disconnected) 1 values of signals from disconnected IED are 'last value'
(quality defined by KeepValue_SetQuality). Note: This
has been developed for Amprion project, limited to one
SBUS Server (no redundancy)
KeepValue_SetQuality (Default=OldData) quality of signals from disconnected
IED.
Note: This has been developed for Amprion project,
limited to one SBUS Server (no redundancy).
Note: Signals are still considered 'disconnected' until first
connection.

7.2.13 [DEVICESYNCHRO]
Parameter Name Description Expected Values
DeviceName Used to update synchronization status of the device. NameOfDevice=x where x is the full path to
the synchronization datapoint of the device.

7.2.14 [INCORRECTTIMESTAMP]
Parameter Name Description Example
XSecondsAheadIsIncorrect If timestamp is X seconds ahead of computer date and time, timestamp is 0 to disable
considered invalid. Updated timestamp will be computer date and time.
XSecondsBehindIsIncorrect If timestamp is X seconds behind of computer date and time, timestamp is 0 to disable
considered invalid. Updated timestamp will be computer date and time.

7.2.15 [SBUSSERVERREDUNDANCY]
Parameter Name Description Example
EquipmentName Defines the redundancy of SBUS Server Acquisition Can be HOTHOT (default) or HOTSTANDBY.
on one IED. If 'MySEPAM=HOTHOT', main SBUS Server and backup
SBUS server will access in parallel MySEPAM.
If 'MySEPAM=HOTSTANDBY', backup SBUS Server will
access MySEPAM only if main SBUS Server is faulty.

7.2.16 [INITIALVALUES]
Parameter Name Description Example
LoadInitialValuesFromLastValues Defines initial values of the ring 0 values are not initialized
1 values are initialized from lastvalues.ini
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 31

8. THE PROFILE.XML FILE

8.1 OVERVIEW
For every different network in the configuration (ring), a Profiles.XML file is defined.
This XML file describes the attributes to be shared and applied to all the datapoints within the LAN. These attributes
are organized by type (STR, SPS, DPS, MV, SPC, DPC, MPS). Many profiles can be defined for every datapoint
type.
In order to facilitate the comprehension of the data structure, in this document we have represented the XML content
in grid and textual views.

8.2 DATA STRUCTURE

The Profiles.XML file is composed by a root node “Profiles” with no attributes.
The “Profiles” node is composed by eight mandatory nodes representing the datapoint types:
• SPS
• DPS
• MV
• SPC
• DPC
• MPS
• STR
• SP

Figure 1: Grid view of the Main structure of the Profiles.XML file

<?xml version="1.0" encoding="UTF-8"?>

<Profiles>
<STR>
</STR>
<SPS>
</SPS>
<DPS>
</DPS>
<MPS>
</MPS>
<SPC>
</SPC>
<DPC>
</DPC>
<MV>
</MV>
<SP>
</SP>
</Profiles>
Example 1: Text view of the Main structure of the Profiles.XML file
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 32

8.2.1 SPS
The SPS node gathers all the profiles of single-point-status type. There is no limitation concerning the number of
profiles of this type.

Figure 2: SPS node with many profiles

An SPS profile is composed by two nodes representing the two datapoint’s states: STATE0 and STATE1

Figure 3: Nodes composing an SPS profile

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 33

Every SPS’s state is composed by the following mandatory attributes

Attribute name Possible Values

label “RESET” or “SET”
“OFF“ or “ON“…
archived Yes / No
printed Yes / No
Alarmlevel 0 for Event
1 for Alarm
2 for Warning
alarmdelay Numeric. Default 0
alarmaudible Yes / No
Eventdelay Numeric. Default 0
Alarmackprofiles Users Profile Names, separated
by « , »
Table 1: SPS’s mandatory attributes

The following example shows an SPS node with a single profile named SPS_ALARM-SET and with all its attributes

<SPS>
<SPS_ALARM-SET>
<STATE0 label="RESET" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE1 label="SET" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0" alarmackprofiles="
operator, administrator" />
</SPS_ALARM-SET>
</SPS>
Example 2: SPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 34

8.2.2 DPS
The DPS node gathers all the profiles of double-point-status type. There is no limitation concerning the number of
profiles of this type.

Figure 4: DPS node with some profiles

A DPS profile is composed by four nodes representing the four datapoint’s states: STATE0, STATE1, STATE3 and
STATE4.

Figure 5: Nodes composing a DPS profile

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 35

Every DPS’s state is composed by the following mandatory attributes

Attribute name Possible values

label “RESET”, “SET”, “JAMMED” or “UNDEFINED”…
archived Yes / No
printed Yes / No
alarmlevel • 0 for Event
• 1 for Alarm
• 2 for Warning
alarmdelay Numeric. Default 0
alarmaudible Yes / No
Eventdelay Numeric. Default 0
Alarmackprofiles Users Profile Names, separated by « , »
Table 2: DPS’s mandatory attributes

The following example shows a DPS node with a single profile named DPS_POSITION and with all its attributes

<DPS>
<DPS_POSITION>
<STATE0 label="RESET" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0" alarmackprofiles=""/>
<STATE1 label="SET" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0" alarmackprofiles=""/>
<STATE2 label="JAMMED" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0" alarmackprofiles=""/>
<STATE3 label="UNDEFINED" archived="yes" printed="yes" alarmlevel="1"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles="operator, administrator"/>
</DPS_POSITION>
</DPS>
Example 3: DPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 36

8.2.3 MPS
The MPS node gathers all the profiles of multi-point-status type. There is no limitation concerning the number of
profiles of this type.

Figure 6: MPS node with many profiles

An MPS profile is composed by at least 3 nodes representing the datapoint’s states: STATE0; STATE 1 and STATE2. A
maximum of 16 states can be defined on an MPS profile.

Figure 7: Nodes composing an MPS profile

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 37

Every MPS’s state is composed by the following mandatory attributes

Attribute name Possible values

label “STATE 0”, “STATE 1”, “STATE 2”, etc.
archived Yes / No
printed Yes / No
alarmlevel 0 for Event
1 for Alarm
2 for Warning
alarmdelay Numeric. Default 0
alarmaudible Yes / No
Eventdelay Numeric. Default 0
Alarmackprofiles Users Profile Names, separated by « , »
Table 3: MPS’s mandatory attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 38

<MPS>
<MPS_RGD_ALARM>
<STATE0 label="STATE 0" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE1 label="STATE 1" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE2 label="STATE 2" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE3 label="STATE 3" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE4 label="STATE 4" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE5 label="STATE 5" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE6 label="STATE 6" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE7 label="STATE 7" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE8 label="STATE 8" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE9 label="STATE 9" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE10 label="STATE 10" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE11 label="STATE 11" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE12 label="STATE 12" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE13 label="STATE 13" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE14 label="STATE 14" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles=""/>
<STATE15 label="STATE 15" archived="yes" printed="yes"
alarmlevel="0" alarmdelay="0" alarmaudible="no" eventDelay="0"
alarmackprofiles="operator, administrator"/>
</MPS_RGD_ALARM>
</MPS>
Example 4: MPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 39

8.2.4 SPC
The SPC node gathers all the profiles of single-point-control type. There is no limitation concerning the number of
profiles of this type.

Figure 8: SPC node with some profiles

An SPC profile is composed by three nodes representing the duration of a pulse and the two possible states:
PROTOCOL, STATE0 and STATE1.

The PROTOCOL node is optional and is only used for MODBUS LANs. The STATEx nodes are mandatory.

Figure 9: Nodes composing the SPC profile

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 40

The following table describes the nodes and attributes of an SPC profile.

Node Attribute name Possible values

By default 1000
PROTOCOL Timedpulse Time is measured
in milliseconds
label “OFF” or “ON”
STATEx archived Yes / No
printed Yes / No
Table 4: SPC’s attributes

The following example shows an SPC node with a single profile named COMM_ON-OFF and with all its attributes

<SPC>
<COMM_ON-OFF>
<PROTOCOL timedpulse="1000"/>
<STATE0 label="OFF" archived="yes" printed="yes"/>
<STATE1 label="ON" archived="yes" printed="yes"/>
</COMM_ON-OFF>
</SPC>
Example 5: SPC profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 41

8.2.5 DPC
The DPC node gathers all the profiles of double-point-control type. There is no limitation concerning the number of
profiles of this type.

Figure 10: DPC node with some profiles

A DPC profile is composed by two nodes representing the two possible states: STATE0 and STATE1

Figure 11: Nodes composing the DPC profile

The following table describes the mandatory attributes of an SPC profile.

Attribute name Possible values

label “OFF” or “ON”
archived Yes / No
printed Yes / No
Table 5: DPC’s mandatory attributes

The following example shows a DPC node with a single profile named COMM_OPEN_CLOSE and with all its attributes

<DPC>
<COMM_OPEN_CLOSE>
<STATE0 label="OFF" archived="yes" printed="yes"/>
<STATE1 label="ON" archived="yes" printed="yes"/>
</COMM_OPEN_CLOSE>
</DPC>
Example 6: DPC profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 42

8.2.6 SP
The SP node gathers all the profiles of SetPoint-control type. There is no limitation concerning the number of
profiles of this type.

Figure 12: SP node with some profiles

A SP profile is composed by one node representing the state: STATE

Figure 13: Nodes composing the SP profile

The following table describes the mandatory attributes of an SP profile.

Attribute name Possible values

archived Yes / No
printed Yes / No
Table 6: SP’s mandatory attributes

The following example shows a SP node with a single profile named SP_ARCHNOPRINT and with all its attributes

<SP>
<SP_ARCHNOPRINT>
<STATE archived="yes" printed="yes"/>
</ SP_ARCHNOPRINT >
</SP>
Example 7: SP profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 43

8.2.7 MV
The MV node gathers all the profiles of measurement type. There is no limitation concerning the number of profiles
of this type.

Figure 14: MV node with some profiles

An MV profile is composed by nodes representing the state and the different thresholds (low-low-low, low-low,
low, high, high-high and high-high-high).

Figure 15: Nodes composing the MV profile

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 44

The following table describes the nodes composing an MV profile and their attributes.

Node Attribute name Possible values

unit -
Hrs
V
A
VA
VAr
Hz
VAh
VArh
%
°C
Bar
W
STATE kW
rpm
s
m/s
scale
format 0.0
0.00
archived yes
printed no
Archivefrequency(1)
label “NORMAL,
“THRESHOLD LLL,
“THRESHOLD LL,
“THRESHOLD L,
THRESHOLD_NORMAL
“THRESHOLD H,
THRESHOLD_LLL
“THRESHOLD HH,
THRESHOLD_LL
“THRESHOLD HHH”
THRESHOLD_L
THRESHOLD_H archived Yes / No
THRESHOLD_HH
THRESHOLD_HHH printed Yes / No
alarmlevel 0 for Event
1 for Alarm
2 for Warning
Table 7: MV’s nodes and their attributes

------------------------------------------------
(1)This attribute is available only for EFIP and OPC LANs.
MVs are archived at least every x seconds as defined in the Archivefrequency attribute.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 45

8.2.7.1 THRESHOLD Management

8.2.7.1.1 From the SignalList

EcoSUI manages MV thresholds: THRESHOLD_NORMAL, THRESHOLD_LLL, THRESHOLD_LL, THRESHOLD_L,
THRESHOLD_H, THRESHOLD_HH, THRESHOLD_HHH.

Threshold values are defined in the .SignalList file whatever the LAN type (except IEC 61850 since
measurement thresholds are natively managed by this protocol).

The syntax should be:

MV_A;Min#Threshold L#Threshold LL#Threshold LLL;Max#Threshold H#Threshold HH#Threshold HHH

Example of OPC Signal list

Where:
• Amper 1 Min=0; Max=100; no threshold
• Amper 2 Min=0; Max=100; L, H
• Volt1 Min=0; Max=100; L, LL, H, HH
• Volt2 Min=0; Max=100; L, LL, LLL, H, HH, HHH
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 46

8.2.7.1.2 Show Thresholds in the State Viewer

Thresholds are displayed in State viewer with MV current values.

Labels are defined in C:\MCIS\Mimics\Language\language.lng file.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 47

8.2.7.1.3 Show Thresholds in the Event Viewer

For each MV state (THRESHOLD_NORMAL, THRESHOLD_LLL, THRESHOLD_LL, THRESHOLD_L, THRESHOLD_H,

THRESHOLD_HH, THRESHOLD_HHH), {0} can be added, in the Profile.xml file, at the end of the label attribute.

• If {0} is added to the Profile.xml file, the state label together with the value which triggered this state will
be shown in the Event Viewer (Message column).
• If {0} is not added to the Profile.xml file, only the state label is displayed.

</MPS>
<MV>
<DUMMY>
<STATE unit="V" scale ="1.0" format="0.0" archived="yes" printed="false" />
<THRESHOLD_LLL label="THRESHOLD LLL" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_LL label="THRESHOLD LL" archived="no" printed="no" alarmlevel="0" />
<THRESHOLD_H label="THRESHOLD H" archived="no" printed="no" alarmlevel="0" />
<THRESHOLD_HH label="THRESHOLD HH" archived="no" printed="no" alarmlevel="0" />
<THRESHOLD_HHH label="THRESHOLD HHH" archived="no" printed="no" alarmlevel="0" />
</DUMMY>
<MV_A>
<STATE unit="A" scale="0.1" format="0.0" archived="yes" printed="yes" archivefrequency="180"/>
<THRESHOLD_NORMAL label="NORMAL {0}" archived="yes" printed="no" />
<THRESHOLD_LLL label="THRESHOLD LLL {0}" archived="yes" printed="yes" alarmlevel="1"/>
<THRESHOLD_LL label="THRESHOLD LL {0}" archived="yes" printed="yes" alarmlevel="1"/>
<THRESHOLD_L label="THRESHOLD L {0}" archived="yes" printed="yes" alarmlevel="1" />
<THRESHOLD_H label="THRESHOLD H {0}" archived="yes" printed="yes" alarmlevel="1" />
<THRESHOLD_HH label="THRESHOLD HH {0}" archived="yes" printed="yes" alarmlevel="1" />
<THRESHOLD_HHH label="THRESHOLD HHH {0}" archived="yes" printed="yes" alarmlevel="1" />
</MV_A>
<MV_V>
<STATE unit="V" scale="0.001" format="0.0" archived="yes" printed="yes"
archivefrequency="180"/>
<THRESHOLD_NORMAL label="NORMAL" archived="yes" printed="no" />
<THRESHOLD_LLL label="THRESHOLD LLL" archived="yes" printed="yes" alarmlevel="2" />
<THRESHOLD_LL label="THRESHOLD LL" archived="yes" printed="yes" alarmlevel="2" />
<THRESHOLD_L label="THRESHOLD L" archived="yes" printed="yes" alarmlevel="2" />
<THRESHOLD_H label="THRESHOLD H" archived="yes" printed="yes" alarmlevel="2" />
<THRESHOLD_HH label="THRESHOLD HH" archived="yes" printed="yes" alarmlevel="2" />
<THRESHOLD_HHH label="THRESHOLD HHH" archived="yes" printed="yes" alarmlevel="2" />
</MV_V>
</MV>
</Profiles>
Example 8: DPC profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 48

See the picture below:

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 49

8.2.7.2 Measurement Scaling

To add scaling on a measurement, either:

• Set this information in the scale attribute of C:/MCIS/ring_name/profile.xml file

<MV_A>
<STATE unit="A" scale="0.1" format="0.0" archived="yes" printed="yes"
archivefrequency="180" />
<THRESHOLD_NORMAL label="NORMAL {0}" archived="yes" printed="no" />
<THRESHOLD_LLL label="THRESHOLD LLL {0}" archived="yes" printed="yes"
alarmlevel="1" />
<THRESHOLD_LL label="THRESHOLD LL {0}" archived="yes" printed="yes"
alarmlevel="1" />
<THRESHOLD_L label="THRESHOLD L {0}" archived="yes" printed="yes"
alarmlevel="1" />
<THRESHOLD_H label="THRESHOLD H {0}" archived="yes" printed="yes"
alarmlevel="1" />
<THRESHOLD_HH label="THRESHOLD HH {0}" archived="yes" printed="yes"
alarmlevel="1" />
<THRESHOLD_HHH label="THRESHOLD HHH {0}" archived="yes" printed="yes"
alarmlevel="1" />
</MV_A>
<MV_V>

In our example, for all measurements defined with this profile, acquired value will be multiply by 0.1

After a profile.xml modification, reload the signalList and restart SBUSserver.

• Or add the C:/MCIS/ring_name/OverridenCoefList.ini file (if it does not exist).

In this file, define the list of signals and a scaled value for each of them.

This scaled value will override the value specified in profile.xml file.

After OverridenCoefList.ini modification, don’t need to reload the signalList, just restart SBUSserver (if
signalList).
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 50

The following example shows an MV node with a single profile named MV_VOLTAGE and with all its attributes

<MV>
<MV_VOLTAGE>
<STATE unit="V" scale="0.1" format="0.0" archived="yes"
printed="no"/>
<THRESHOLD_NORMAL label="NORMAL {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_LLL label="THRESHOLD LLL {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_LL label="THRESHOLD LL {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_L label="THRESHOLD L {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_H label="THRESHOLD H {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_HH label="THRESHOLD HH {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_HHH label="THRESHOLD HHH {0}" archived="no" printed="no"
alarmlevel="0"/>
</MV_VOLTAGE>
</MV>
Example 9: MV profile with attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 51

8.2.8 STR
The STR profile represents a String of characters. This String can be used for representing, for example, the
manufacturer’s name associated to an IED. No attributes are currently defined for this profile.

Figure 16: STR node with profiles

The following example shows an STR node with a single profile named STR_SNMP_WALK

<STR>
<STR_SNMP_WALK>
</STR_SNMP_WALK>
</STR>
Example 10: STR profile with its nodes and their attributes

The following example is for SNMP monitoring and control: In the profile.xml, “STR” profile will have to be added for
string objects to be linked in SNMP signallist.

8.2.9 SP
The following example shows an SP node with a single profile named _ARCHNOPRINT
<SP_ARCHNOPRINT>
<STATE archived="yes" printed="false">
</SP_ARCHNOPRINT>
Example 11: SP profile with its nodes and their attributes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 52

8.3 EXAMPLE OF PROFILES.XML FILE

The following figure represents a simple profiles.xml file in a grid view.

Figure 17: Example of a simple Profiles file

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 53

And this is the text version of the same profiles.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<Profiles>
<SPS>
<SPS_ALARM-SET>
<STATE0 label="RESET" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE1 label="SET" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
</SPS_ALARM-SET>
</SPS>
<DPS>
<DPS_POSITION>
<STATE0 label="RESET" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE1 label="SET" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE2 label="JAMMED" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE3 label="UNDEFINED" archived="yes" printed="yes" alarmlevel="1"
alarmdelay="0" alarmaudible="no"/>
</DPS_POSITION>
</DPS>
<MPS>
<MPS_RGD_ALARM>
<STATE0 label="STATE 0" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE1 label="STATE 1" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
<STATE2 label="STATE 2" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0"
alarmaudible="no"/>
</MPS_RGD_ALARM>
</MPS>
<SPC>
<COMM_ON-OFF>
<STATE0 label="OFF" archived="yes" printed="yes"/>
<STATE1 label="ON" archived="yes" printed="yes"/>
</COMM_ON-OFF>
</SPC>
<DPC>
<COMM_OPEN_CLOSE>
<STATE0 label="OFF" archived="yes" printed="yes"/>
<STATE1 label="ON" archived="yes" printed="yes"/>
</COMM_OPEN_CLOSE>
</DPC>
<MV>
<MV_VOLTAGE>
<STATE unit="V" scale="0.1" format="0.0" archived="yes"
printed="no"/>
<THRESHOLD_NORMAL label="NORMAL {0}" archived="no" printed="no"
alarmlevel="0"/>
<THRESHOLD_LLL label="THRESHOLD LLL {0}" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_LL label="THRESHOLD LL {0}" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_L label="THRESHOLD L {0}" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_H label="THRESHOLD H {0}" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_HH label="THRESHOLD HH {0}" archived="no" printed="no" alarmlevel="0"/>
<THRESHOLD_HHH label="THRESHOLD HHH {0}" archived="no" printed="no"
alarmlevel="0"/>
</MV_VOLTAGE>
</MV>
</Profiles>
Example 12: Simple example of a profiles.xml file
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 54

9. THE SERVERS.INI FILE

9.1 OVERVIEW
This section describes the Servers.ini configuration file.
The user edits Servers file and configures settings in order to configure objets and features (databases,
servers, archiving, printing, synchronizing).
The Servers.ini is located under folder C:\MCIS
The Servers file is a comma-separated value (CSV) text files (.csv).

9.2 MAIN CONTENT

The Servers.ini file is composed of the following sections:
CAE in this context means Confguration, Alarms and Events.
Section name Details
CentralDB Configuration of the central database
MultiCentralDBLight Configuration of the Multi central database
AdditionalCAEDatabases Configuration for additional CAE databases
SBUSServers List of SBus servers
SBUSServer Configuration of the SBus server
CAEDatabases Configuration of the CAE database
MVArchiving Locally archived or not
LogbookPrinter Configuration of the printer
TelnetServer Configuration of the telnet server
TimeSynchro To use EcoSUI NTP Client feature
MVRingsArchiving Locally save measurements or not

Table 8: Sections composing the Servers.ini file

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 55

The following limitation shall be taken into account:

Section name Limit Value

AdditionalCAEDatabases Maximum of Additional Central Databases 32
(with or without redundant Central Database)

Table 9: Limitations

NOTE: AdditionalCAEDatabases section allows the user to define the Main and BackUp IP adresses for
Multi-Central DB configuration with:

• IP0 = Main MultiCentralDB IP address or host name of the computer managing the first
Config/Alarms/Events Database.
• IP1 = BackUP MultiCentralDB IP address or host name of the computer managing the second
Config/Alarms/Events Database. Leave empty if there is only one CAE Database.
Meanwhile, no acquisition is possible on configured Rings for these PCs. This means the “Enabled”
parameter should be empty on Ring.ini file for each configured ring.

9.3 POSSIBLE PARAMETERS

9.3.1 [CENTRALDB] SECTION

Parameter Name Description Expected Values
DefaultCharSet latin1 : default value
Charset of Database
utf8 : for unicode database
CheckTablesAtStart

1 : to enable of all tables

(recommended),
0 : to disable,
Check all MySQL tables at start. Can take a 2 : to enable check of all tables except
long time on multi Gigabytes databases. events & measurements (not
recommended).
3 : to check critical tables at
SBUSServer startup, other table
checking will be delayed

Purge_PurgeEventsAfterXDays All Events older than this number of days will e.g: 90
be purged
Purge_PurgeMVAfterXDays All MV older than this number of days will be e.g: 90
purged
Purge_PacketSize Purge By Packets of X rows to limit lock in E.g: 5000
MySQL
Purge_TimeToWaitInSec Time in Second between each purge SQL E.g: 10
command
Sync_NbOfItems Number of Items for each table that will be E.g: 1000
synced between both Central DB
Sync_TimeToWaitInSec Time in Second between each table E.g: 20
Synchronisation
StopBuzzerAfterTimeout Automatically stops alarm buzzer after x 0 : feature is disabled
seconds
StopBuzzerWhenAllAlarmsAreAcknowledged Automatically stops alarm buzzer when 1 : buzzer will stop if all alarms are
alarms acknowledged acknowledged.
0 : feature is disabled

AutoClearAlarms Automatically clears inactive & acknlowledged 0: (Default value) Alarms are
alarms automatically cleared if status is
NACT/ACK (Not Active/Acknowledged)
1 : disable
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 56

Parameter Name Description Expected Values

SetAlarmMessageToCurrentStateMessage Alarms Message column is modified 1: alarm message will be set to current
accorddingly with Signal status message. status of signal
Exemple: Open/Closed. Otherwisethe Alarm 0: alarm messages keep alarmed state
message dispayss the initial Signal Status message (Default).
(when Alarm was raised).
LogbookPrinterManagerIPAddress0 IP Address of the Main Empty value : if MCIS Events are not
LogbookPrinterManager for Central DB. send to a printermanager.
If not empty (default value): parameter
can be filled with - IP address for Main
Central DB

LogbookPrinterManagerIPAddress1 IP Address of the Backup Empty value : if MCIS Events are not
LogbookPrinterManager for Central DB send to a printermanager.
If not empty (default value): parameter
can be filled with - IP address for
BackUP Central DB (in case of
Redundant Central DB)

CheckAndUpdateStatusOnCentralDBEveryXMs Status of all EcoSUI Equipment are stored in 1000 ms is default value.
CentralDB. Each EcoSUI Client Example:
(SBUSServer, HMI, EcoGTW, ...) polls or CheckAndUpdateStatusOnCentralDBE
updates those statuses every X ms. veryXMs=1000
StartUpConnectionTimeout Applications will start after X seconds, if both 0: disable
CentralDB are not responding during startup. Value (in second) > 0: and if both
Value in second. CentralDB are not responding during
startup, applications will start after X
seconds.
RaiseAnAlarmWhenDBSizeIs When the size of the database Is bigger than Example for 20 Gbytes:
this (in megabytes), an alarm will be raised. RaiseAnAlarmWhenDBSizeIs=20000
Default Value: 10000
RaiseAnHighAlarmWhenDBSizeIs Example for 20 Gbytes:
When the size Of the database Is bigger than
RaiseAnHighAlarmWhenDBSizeIs
this (In megabytes), an alarm will be raised.
=20000 (default value)
UpdateIEDStatusOnCentralDBEveryXMs Status of IED are stored in CentralDB. SBUS 1000 ms is the default value
Servers updates those statuses every X ms. (UpdateIEDStatusOnCentralDBEveryX
Value in ms. Ms=1000)
Sync_MaxNbLogFiles Maximum number Of log files. For replication e.g for 100 files
that can be handled, Each file can grow up To Sync_MaxNbLogFiles=100
1 Gb so Default number To 100 files makes a
Default maximum amount Of space Of
100Gb, after Then oldest log files are deleted
To keep only 100 active files.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 57

9.3.2 [MULTICENTRALDBLIGHT] SECTION

Parameter Name Description Expected Values

UseMultiCentralDBLight Activate MultiCentralDB 'Light'.
Defines couples like
'[MultiCentralDBLight]MyLowerSubstationName=
MainIP;BackupIP'

9.3.1 [ADDITIONALCAEDATABASES] SECTION

Parameter Name Description Expected Values

CAEDB_<X> Enter the IP address or host name of the computer Example:
managing the first Config/Alarms/Events Database for CAEDB_0=192.168.0.2;192.168.0.3;
external databases then (separated by ;) Remote_A;
Redundant IP address or host name if it exists then CAEDB_1=192.168.0.5;192.168.0.6;
(separated by ;) a description (separated by ;) Remote_B;
ShowSubstationNameInNode Display the additional substation description in tree node 0: disable
1: enable

9.3.2 [SBUSSERVER] SECTION

Parameter Name Description Expected Values

EqptStatusUpdateTimeout After X seconds without Equipment update E.g: 10
(heartbeat), equipment is declared absent
Activate61850Server Activate 61850 Server on computer 1 activated
0 stopped
UseOdTimeForSynchronization Use OdTime agency feature to synchronize 1 used,
SBUS Server 0 not used (default value)
NbMaxOfHeartbeatFailure Number max of heartbeat failure before E.g: 3
declaring an equipment absent
SendNewEventsToCentralDB_EveryXMS From a performance point of view, it's better to Default value is 500ms
write events by packets of events This value (Hardcoded 1000 ms in
represents how much time we wait before versions < R16155)
sending new events to database. E.g : 500

SendNewMVsToCentralDB_EveryXMS From a performance point of view, it's better to Default value is 1000ms
write MVs by packets of MVs This value
represents how much time we wait before
sending new MVs to database. Value in ms.
ForceSBUSServerClosing
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 58

9.3.3 [SBUSSERVERS] SECTION

Parameter Name Description Expected Values

Server<X> List of servers and for each one, the IP address Example for 3 servers
and the description (separated by ;):
X=0,1,2… Server0=192.168.0.2;OIS_A
Server1=192.168.0.3;OIS_B
Server2=192.168.0.8;GTW_
1

NbMaxOfEcoSUIClientConnection This is the max number of connection a SBUS Max value is 250 (default
Server can receive from EcoSUI Clients (HMI, value)
GTW).
NOTE: Each workspace in HMI opens a
separate connection. HMI with 10 workspaces
opens at least 10 connections to SBUS Server.
ValueRetrivalOptions Get realtime values from SBUS server 0: to get realtime values
from the first SBUS Server
in the list that respond
(default value)
1: to get realtime values
from the SBUS Server that
has the newest value

9.3.4 [CAEDATABASES] SECTION

Parameter Name Description Expected Values

IP0 Mandatory field
Enter the ip address or host name of the Main
Example:
Central DB from the computer (managing the
IP0=10.22.91.1
first Config/Alarms/Events Database).
IP1 Enter the ip address or host name of the Optional field, only in case of
Redundant Central DB of the computer Redundant Central DB
(managing the second Config/Alarms/Events Leave empty if there is only
Database). one CAE Database.

9.3.5 [MVARCHIVING] SECTION

Parameter Name Description Expected Values

ArchiveLocaly Archive localy 0 (default value) disable
1 : enable
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 59

9.3.6 [LOGBOOKPRINTER] SECTION

Parameter Name Description Expected Values

EnableLogbookPrinterManager Computer manage a logbook 0 (default value): disable
printer or a list of computers
Not empty: Let this computer manage a
logbook printer or a list of computers
(separated by ;) where manager is enabled
Example:
EnableLogbookPrinterManager=OIS_A;OIS
_B

MainRedundantPrinter Empty : if printer redundancy is not used

Not empty: computer name
Name of the computer where the
Example:
Main Redundant Printer is
MainRedundantPrinter=OIS_A
installed

BackupRedundantPrinter Empty : if printer redundancy is not used

Name of the computer where the
Not empty: computer name
Backup Redundant Printer is
Example:
installed
BackupRedundantPrinter =OIS_B
LogbookPrinterName Example:
Windows Name of the Printer
LogbookPrinterName= OKI ML5721
LogbookRowsPerPage Number of rows in a logbook 0: to never send a form feed
page
AlsoSendToFile 0 (default value): disable
Send also events to a text file 1: enable

SendToFileFolder In case SendToFile is enabled, Example:

this is the folder were text files SendToFileFolder=C:\MCIS\LogbookManag
will be stored er
GetStatusFromSNMP For network printer, use SNMP 0: not used (default value)
to get printer Error. 1: to enable.
SNMP_IRC 0 if there is no error. Default for LEXMARK is
SNMP OID for Intervention
1.3.6.1.4.1.641.2.1.3.1.2
Required Code.
e.g: SNMP_IRC=1.3.6.1.4.1.641.2.1.3.1.2.1
DontPrintTheseSignals Ignore these signals and don't
print them

9.3.7 [TELNETSERVER] SECTION

Parameter Name Description Expected Values

TCPPort 0 : disable telnet port
Telnet server port
23 : enable telnet port
(default value)
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 60

9.3.8 [TIMESYNCHRO] SECTION

Parameter Name Description Expected Values

UseEcoSUINTPClient Use Client NTP type 1 : use EcoSUI NTP Client
feature to synchronize
SBUS Server (or odTime
from Agency if Gateway V5
is installed
0 : use Meinberg NTP client
(default value)

WaitDelayResponse NTP request timeout default value is 10

Value in second.
ServerMain Default value (127.0.0.1): if
default value kept, the time
synchronization of system is
NTP main server IP address
not updated.
Example:
ServerMain=10.22.91.29
ServerBackup empty value: disable the
redundancy (defaut value)
NTP backup server IP address
e.g :
ServerMain=10.22.91.30

9.3.9 [MVRINGSARCHIVING] SECTION

Parameter Name Description Expected Values

ArchiveLocal 0: default value
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 61

10. THE DISTURBANCEFOLDERS.INI FILE

10.1 OVERVIEW
This section describes the DisturbanceFolders.ini configuration file.

The user edits DisturbanceFolders file and configures settings in order to download disturbance files from
IEDs.

The DisturbanceFolders file is located under folder C:\MCIS

The DisturbanceFolders file is a comma-separated value (CSV) text files (.csv).

10.2 MAIN CONTENT

The DisturbanceFolders.ini file is composed of the following sections:

Section name Details

[General] General
[DownloadFolder] Disturbance path folder to PC
[DisturbanceFolder] Disturbance path folder from IEDs
[DeleteDisturbance] Management of disturbance files

Table 10: Sections composing the DisturbanceFolders.ini file

10.1 POSSIBLE PARAMETERS

10.1.1 [GENERAL] SECTION

Parameter Name Description Expected Values

DownloadDisturbancesOnAllIEDs 0: get disturbance files from IED (if
Get disturbance files fromIEDS
RcdMade is configured)
1: get disturbance files from all IEDs
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 62

10.1.2 [DOWNLOADFOLDER] SECTION

Parameter Name Description Expected Values

DownloadFolder The path of the folder that store Example
disturbance files from IEDs. DownloadFolder=C:\Disturbance

10.1.3 [DISTURBANCEFOLDER] SECTION

Parameter Name Description Expected Values

List of <IED name> The path folder that contains Example for 4 IED:
disturbance files for each IED. C264_TR1.AP2=/RAMDEV/WAVEFORM
IED is idenfied with IED name GTW_IEC.AP2=/RAMDEV/PERT_IED
S40_01.AP1=/RAMDEV/PERT_IED
S80_01.AP1=/RAMDEV/PERT_IED

10.1.4 [DELETEDISTURBANCE] SECTION

Parameter Name Description Expected Values

List of <IED name> Allow deleting /not deleting 1: deleting
disturbance file from IED after a 0 or empty: not deleting (default value)
successful downloading Example: C264_TR1.AP2=1
C264_TR2.AP2=1
S40_01.AP1=1
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 63

11. THE AUTOEXTRACT.INI FILE

11.1 OVERVIEW
The signal list extraction (datapoints) can be created or updated from SBUS Server, from Extraction tab.
The Autoextract.ini is located under folder C:\MCIS\Reports folder. It contains EcoSUI parameters for the signal
list extraction reports. It may be necessary to edit this file and setup the parameters based on project needs. It is a
comma-separated value text file.
The result file (Events_<datation>.csv) will be automatically created under C:\MCIS\Reports folder and it
contains all datapoints varation already selected on ListOfSignalToExtract file during the configured period.

<datation> format: YYYYMMDD_HHMMSS

11.2 MAIN CONTENT

The Autoextract.ini file is composed of the following sections

Section name Details

[PC name] Fill the section name with the PC name

Table 11: Sections composing the Autoextract.ini file

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 64

11.3 POSSIBLE PARAMETERS

11.3.1 [PC NAME] SECTION

Parameter Name Description Expected Values
SignalListFilename The name of signal list report file e.g:
SignalListFilename=ListOfSignalsToEx
Important: The extraction will be done only for the signal tract3.lst
list included in the file

ExtractEveryXMinutes When using MinuteBased Extraction plan, extraction will e.g: ExtractEveryXMinutes=1
be done every x minutes
ExtractXMinutes In all Extraction plans, this is the number of minutes that e.g: ExtractXMinutes=1
will be extracted
CSVFilename Filename of the file generated e.g: CSVFilename=Events
Extension .CSV
ExtractPlan L = Minute based Extraction plan
Extraction Plan periodicity
J = Daily Extraction plan
O = Weekly Extraction plan
B = Monthy Extraction plan

DailyExtract_Hour Value = 0 or missing parameter:

When using Daily extraction plan, extraction will be
disable
done every day at 'hour' hour
Eg:
08 = 08h00 AM
13 = 01:00 PM

WeeklyExtract_Hour Value = 0 or missing parameter:

When using Weekly extraction plan, extraction will be
disable
done every 'dayofweek' day at 'hour' hour

WeeklyExtract_DayOfWeek 0: Sunday = DayOfWeek

When using Weekly extraction plan, extraction will be
1: Monday = DayOfWeek
done every 'dayofweek' day at 'hour' hour.
…
6: Saturday = DayOfWeek

MonthlyExtract_Hour When using Monthly extraction plan, extraction will be Value = 0 or missing parameter:
done every 'day' day at 'hour' hour disable

MonthlyExtract_Day When using Monthly extraction plan, extraction will be Value = 0 or missing parameter:
done every 'day' day at 'hour' hour disable
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 65

12. IEC 61850 LAN

This chapter describes how to implement IEC 61850 protocol edition 1 and edition 2 for data acquisition (LAN) in
EcoSUI.

The user can implement an IEC 61850 protocol-based project:

• From a configuration database that has been set up in EPAS SCE

• Using SET (.scd file, signalList & profiles) and then, import it directly to EcoSUI.

12.1 FROM EPAS SCE ZIP FILE

To implement an IEC 61850 protocol-based project from the EPAS SCE database, follow the procedure:

12.1.1 CREATE A RING FOLDER

Create a ring folder such as C:\MCIS\Rings\IEC61850

12.1.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the ring.ini file of EcoSUI. This file contains important Sbus Server LAN
properties.

• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\IEC61850\

• Copy it in the previously created folder (C:\MCIS\Rings\IEC61850)
• Open the file Ring.Ini file with any text editor (using Notepad++ in the hereunder screenshot).
• Fill in the following parameters:
o Type= Enter IEC61850
o Enabled= Write the SBUS Server names (Windows network name), separated with ; where this
LAN is enabled.

Note: Refer to the chapter about ring.ini file to get additional information on the possible parameters.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 66

12.1.3 LOAD THE SCE DATABASE

Before loading a SCE database to SBUS Server, make sure that the SCL.zip file is in the generated SCE database
zip file.

1. Copy the SCE database .ZIP file in C:\MCIS\SCEConfiguration. It is composed of 2 folders and 2 INI
files.
2. Unzip it in C:\MCIS.

3. Start EcoSUI SBUS Server.

4. Click the Acquisition tab.
5. Stop data acquisition by clicking on the Stop button.
6. Click the Tools… button and select Load Configuration from SCE Zip.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 67

7. In the explorer window, browse and select the configuration file to be imported:

8. Click Open. This will upload the configuration into the database.
9. Once the new configuration is loaded, click the Dashboard tab and exit the SBUS Server (Dashboard tab
→ Close button)
10. Restart the EcosSUI SBUS Server and the EcoSUI application.

The SBUS Server is now configured. As a result, Alarms, States and Events tabs will show relevant information.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 68

12.2 FROM A SIGNAL LIST

To implement an IEC 61850 protocol-based project from the .SignalList file (SCD file generated from SET),
follow the procedure:

12.2.1 CREATE A RING FOLDER

Create a ring folder such as C:\MCIS\Rings\RINGIEC61850

12.2.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the Ring.ini file of EcoSUI. This file contains important Sbus Server LAN
properties.

• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\IEC61850\

• Copy it in the previously created folder (C:\MCIS\Rings\RINGIEC61850)
• Open the file Ring.Ini file with any text editor (using Notepad++ in the hereunder screenshot).
• Fill in the following parameters
o Type= Enter IEC61850
o Enabled= Write the SBUS Server names (Windows network name), separated with ; where this LAN
is enabled.

Note: Refer to the chapter about ring.ini file to get additional information on the possible parameters.

12.2.3 CREATE THE PROFILES.XML FILE

The Profiles.xml file contains data point profiles referenced by the .SignalList file
• <SPS>, <DPS>, <MPS>
• <SPC>, <DPC>, <SP>
• <MV>

This is where to define ON and OFF states whether signal is alarmed or not.

Profile properties are similar to the ones in EPAS SCE.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 69

12.2.4 CREATE THE SIGNAL LIST WITH PROFILE STUDIO TOOL

The Signal list file gathers the list of data points managed by the IEC 61850 LAN.

For IEC 61850 data acquisition, the user create the.signallist file automatically using the Profile Studio tool
and import it to EcoSUI.

Note: Profile Studio is an optional tool. For further information, please contact the support team.

To create the signal list with the Profile Studio software, follow instructions:

In case of the .SCD file has been already imported:

• Choose GET STARTED tab and click on Open existing project button

• Locate the.XPE file and Open file; Profile Studio software will automatically detect data point and the
configuration is displayed

• From the control bar click on Auto Assign

Profiles icon to assign profiles to datapoint

• Automatic Profiles Association window is displayed; choose options as below

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 70

• Ok button; the Profile column is updated

• Click on Export Configuration Full Package icon to export the configuration

• Choose the destination folder to save the configuration and the starting exportation…

• When the exportation is completed, a window message is displayed in order to display the destination
folder content

• Yes button, the configuration .zip file generated is displayed

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 71

NOTE: the zip file contains a set of files (per device) used by EcoSUI and the .SignalList file

12.2.5 IMPORT & FIX SCD FILE

Now import the SCD file. This step is important as typical SCD incompatibilities generated by SCE will also be fixed
in the process.

• To do so, from Acquisition tab, click the Tools… button.

• Select Advanced > Import & Fix SCD

12.2.6 DEPLOY
Now load datapoint configuration from SignalList to the CentralDB.

• From Acquisition tab, click the Tools… button.

• Select Tools… > Load Configuration from SignalList

• Exit and restart SBUS Server (Dashboard tab → Close button).

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 72

13. MODBUS LAN

This document provides detailed information about the “L_Modbus_XML_0.xml” file content.

It describes how this file is composed and the default values for every attribute. It also describes the Modbus
addressing to be used in the SignalList and the list of Modbus’ functions supported.

13.1 GENERALITIES
An “L_Modbus_XML_0.xml” file is defined in EcoSUI for a Modbus network. This file describes the elements
necessary in order to manage a Modbus LAN.

The following limitations shall be taken into account:

Limitation Description
Number of IEDs No more than 300 IEDs are supported
Mailbox reading compatibility Compatible with SisGTW and SEPAM.
Not compatible with Micom and Siemens.
Table 12: Limitations

In order to facilitate the comprehension of the data structure, in this document we have represented the XML
content in grid and textual views.

13.2 L_MODBUS_XML_0.XML DATA STRUCTURE

The “L_Modbus_XML_0.xml” file describes the elements composing a Modbus LAN. This file is composed by a
main node named “ModbusMaster”. This node has no attributes.

The ModbusMaster node is composed by 2 types of nodes representing the Modbus network description and the
list of equipments within the network: MAIN and EQT.

The following figure represents the main structure of the ModbusMaster node in a grid view.

Figure 18: ModbusMaster node with Main description and 8 associated equipments
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 73

The next example shows the main structure of the ModbusMaster node in a textual view.

xml version="1.0" encoding="utf-8" standalone="yes"?>

<ModbusMaster>
<MAIN/>
<EQT>
</EQT>
<EQT>
</EQT>
<EQT>
</EQT>
<EQT>
</EQT>
<EQT>
</EQT>
<EQT>
</EQT>
</ModbusMaster>
Example 13: Text view of the Main structure of the Modbus.XML file
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 74

13.3 MAIN NODE <MAIN>

The Main node mainly describes the link name. It contains a single attribute:

Attribute name Description

linkName Network Name (String)
debugLevel Debug level
0 no trace
-1 full traces
keepAliveDelayInS Keep alive delay (in seconds)
Table 13: Main node’s attributes

ModbusMaster>
< MAIN linkName="SHELL_SERAYA" debugLevel="-1" keepAliveDelayInS="10"></MAIN>
</ModbusMaster>
Example 14: Main node with attributes

13.4 EQUIPMENT NODE <EQT>

The ModbusMaster node contains zero or more Equipments described by the EQT node. The EQT node is
composed by some attributes and nodes described in the following figure and table.

Figure 19: Attributes and nodes composing the EQT node

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 75

Attribute name Description

nameEqu Equipment name (String)
numEqu Equipment Number (Int32)
ipAddress Equipment IP Address (String)
portNumber Port Number (UInt16)
Modbus Address
• 0 : Broadcast address
address
• 1-254 : Address
• 255 : Unused
Redundant Equipment with IP Swap
swapIP
(Boolean)
type Equipment Type 0..9
tableNum Mailbox Number 1..2
Time in milliseconds before considering the
TransactionTimeoutInMilliseconds equipment as disconnected.
-1 for infinite timeout
Optional attribute.
Offset that will be added to addresses -
offset 32768...+32767 ie. Modbus=-1, JBUS=0
(Int16)
Default value is 0
pollFuncode Polling functional code
pollAddr Polling address
REDUNDANCY Node
Frame Node
MAILBOX Node
Table 14: Attributes and nodes composing the EQT node

<EQT nameEqu="GW_1" numEqu="8" ipAddress="100.100.12.191" portNumber="502"

address="248" swapIP="1" type="8" tableNum="1"
TransactionTimeoutInMilliseconds="1000" offset="0" pollFuncode="1"
pollAddr="16">
<REDUNDANCY>
</REDUNDANCY>
<MAILBOX>
</MAILBOX>
<Frame>
</Frame>
</EQT>
Example 15: Attributes and nodes composing the EQT node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 76

13.4.1 REDUNDANCY NODE

This node represents the redundant equipment corresponding to the one being currently defined; thus, it mostly
contains the same attributes than the container EQT node.

Two exceptions are made, Equipment Name (nameEqu) is not used and Equipment Number (numEqu) is
automatically calculated. numEqu of a redundancy node is automatically set as the negative of the redounded
equipment; for example, if the redounded equipment’s number is 10, then the redundant equipment’s number will
be -10. This value cannot be manually modified.

Figure 20: Attributes composing the REDUNDANCY node

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 77

The following table describes the attributes composing the Redundancy node.

Attribute name Description

ipAddress Equipment IP Address (String)
portNumber Port Number (UInt16)
Modbus Address
• 0 : Broadcast address
address
• 1-254 : Address
• 255 : Unused
Redundant Equipment with IP Swap
swapIP
(Boolean)
type Equipment Type 0..9
tableNum Mailbox Number 1..2
Time in milliseconds before considering the
TransactionTimeoutInMilliseconds equipment as disconnected.
-1 for infinite timeout
Optional attribute.
Offset that will be added to addresses -
offset 32768...+32767 ie. Modbus=-1, JBUS=0
(Int16)
Default value is 0
True: when both, the main and the
redundant equipments, are used in Hot-Hot
redundancyHot
redundancy
False: otherwise
Table 15: Attributes composing the REDUNDANCY node

ModbusMaster>
<MAIN linkName="NET_1"/>
<EQT nameEqu="GW_1" numEqu="8" ipAddress="100.100.12.191" portNumber="502"
address="248" swapIP="1" type="8" tableNum="1"
TransactionTimeoutInMilliseconds="1000" offset="0" pollFuncode="1"
pollAddr="16">
<REDUNDANCY ipAddress="100.100.12.191" portNumber="502" address="248"
swapIP="false" type="0" tableNum="1"
TransactionTimeoutInMilliseconds="1000" offset="0"
redundancyHot="true"/>
<Frame>
</Frame>
<MAILBOX>
</MAILBOX>
</EQT>
</ModbusMaster>
Example 16: Attributes composing the REDUNDANCY node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 78

13.4.2 MAILBOX NODE

This node represents the Mailbox Polling characteristics (time stamped events). Due to DLL restrictions, if more
than one Mailbox is defined, only the first one will be read.

Figure 21: Attributes composing the MAILBOX node

The following table describes the attributes composing the Redundancy node.

Attribute name Description

Delay in millisecond between the polling of the
intervalPollingPeriodTS
mailbox
exchangeWordRegister Address of the exchange word
sizeBuffer Maximum number of events stored in mailbox
dataLossBitNumber Bit address of data loss
notSynchronousBitNumber Bit address of sync loss
Optional attribute
‘2’ indicates the configuration of the slave
MasterSlave mailbox. Any other number indicates the
configuration of the master mailbox. (Int8).
Default value is 1
Table 16: Attributes composing the MAILBOX node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 79

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<ModbusMaster>
<MAIN linkName="NET_1"/>
<EQT nameEqu="GW_1" numEqu="8" ipAddress="100.100.12.191" portNumber="502"
address="248" type="8" TransactionTimeoutInMilliseconds="1000" offset="0"
pollFuncode="1" pollAddr="16">
<Frame>
</Frame>
<MAILBOX intervalPollingPeriodTS="100" exchangeWordRegister="55000"
sizeBuffer="15" dataLossBitNumber="700"
notSynchronousBitNumber="0" MasterSlave="master"/>
</EQT>
</ModbusMaster>
Example 17: Attributes composing the MAILBOX node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 80

13.4.3 FRAME NODE

This node describes a data frame used in the associated equipment (EQT). An Equipment may use as many
Frames as necessary.

Figure 22: Attributes and nodes composing the FRAME node

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 81

The following table describes the attributes and nodes composing the FRAME node.

Attribute name Description

numFrame Frame number in Equipment
Frame type (String)
TS – Digital Input
type TM – Measurement and ‘Bit in Word’
Co – Control
Sp – SetPoint
Modbus Function Code

If type=”TS” -> Function codes 1 or 2

numFct
If type=”TM” -> Function codes 3 or 4
If type=”Co” -> Function code 5
If type=”Sp” -> Function code 16
Optional attribute
True/False or Yes/no
horodated True if this signal can be found in mailbox
If true, then frequency and length attributes
are not read
Optional attribute
frequency Frequency in milliseconds of frame polling.
Not used if horodated is true.
Bit address of sync loss
beginAddr

Optional attribute
length Size of elements to read.
Not used if horodated is true.
TS Optional node
TM Optional node
Co Optional node
Sp Optional node
Table 17: Attributes and nodes composing the FRAME node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 82

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<ModbusMaster>
<MAIN linkName="NET_1"/>
<EQT nameEqu="GW_1" numEqu="8" ipAddress="100.100.12.191" portNumber="502"
address="248" type="8" TransactionTimeoutInMilliseconds="1000" offset="0"
pollFuncode="1" pollAddr="16">
<Frame numFrame="15" type="TM" numFct="4" frequency="2000"
beginAddr="22000" length="67" horodated="no">
<!--GW_SVC-->
<TM id="1027" type="BIT" addr="22051" format="UINT16_LB"
numBit="0"/>
</Frame>
<Frame numFrame="17" type="TS" numFct="1" frequency="3000"
beginAddr="26000" length="16" horodated="yes">
<!--GW_MOT-->
<TS id="1934" basicAddrOpen="26014" bitAddrOpen="0"/>
<TS id="1939" basicAddrOpen="26007" bitAddrOpen="0"/>
</Frame>
<Frame numFrame="19" type="Sp" numFct="16" frequency="200"
beginAddr="24000" length="10">
<Sp id="1940" basicAddrOpen="24005" bitAddrOpen="0"
format="UINT16_LB" byteOrdering="4321"/>
<Sp id="1941" basicAddrOpen="24006" bitAddrOpen="0"
format="UINT16_LB" byteOrdering="4321"/>
<Sp id="1942" basicAddrOpen="24008" bitAddrOpen="0"
format="UINT16_LB" byteOrdering="4321"/>
</Frame>
</EQT>
</ModbusMaster>
Example 18: Attributes composing the FRAME node

13.4.3.1 Bit Acquisition Node (TS)

A Frame node can contain as many Bit Acquisition (TS) nodes as necessary. This node contains the following
attributes.

Attribute name Description

Unique ID number within the entire
id
configuration
basicAddrOpen Basic address
bitAddropen Bit offset
Table 18: Attributes composing the TS node

<Frame numFrame="17" type="TS" numFct="1" frequency="3000" beginAddr="26000" length="16"

horodated="yes">
<!--GW_MOT-->
<TS id="1934" basicAddrOpen="26014" bitAddrOpen="0"/>
<TS id="1939" basicAddrOpen="26007" bitAddrOpen="0"/>
</Frame>
Example 19: Attributes composing the TS node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 83

13.4.3.2 Register Acquisition Node (TM)

A Frame node can contain as many Register Acquisition (TM) nodes as necessary. This node contains the
following attributes.

Attribute name Description

Unique ID number within the entire
id
configuration
type Measurement type (String or Int8)
MEAS = 0
NOTUSE = 1
TPI = 2
COUNT = 3
BIT = 4
addr Register address
numBit Optional attribute
Bit number to read in the register. If present,
bit value is returned, if absent, register value
is returned. (UInt8)
format Register Value Format (String or Uint16)
INT8_LB=0
INT8_HB=1
UINT8_LB=2
UINT8_HB=3
INT16_LB=4
UINT16_LB=5
INT32_LW_LB=6
INT32_LW_HB=7
INT32_HW_LB=8
INT32_HW_HB=9
UINT32_LW_LB=10
UINT32_LW_HB=11
UINT32_HW_LB=12
UINT32_HW_HB=13
REAL32_LW_LB=14
REAL32_LW_HB=15
REAL32_HW_LB=16
REAL32_HW_HB=17
M230_T5_TYPE=18
M230_T6_TYPE=19
M230_T7_TYPE=20
ION_MODULUS_1000_UNSIGNED=21
ION_MODULUS_1000_SIGNED=22
KITZ202_K8=23
INT16_HB=24
UINT16_HB=25
UNKNOWN_FORMAT=255
Table 19: Attributes composing the TM node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 84

<Frame numFrame="12" type="TM" numFct="3" frequency="5000" beginAddr="50000"

length="16" horodated="no">
<!--GW_TM32TRD_1-->
<TM id="1846" type="MEAS" addr="50000" format="UINT32_HW_LB"/>
<TM id="1847" type="MEAS" addr="50002" format="UINT32_HW_LB"/>
<TM id="1848" type="MEAS" addr="50004" format="UINT32_HW_LB"/>
<TM id="1850" type="MEAS" addr="50006" format="UINT32_HW_LB"/>
<TM id="1851" type="MEAS" addr="50008" format="UINT32_HW_LB"/>
<TM id="1852" type="MEAS" addr="50010" format="UINT32_HW_LB"/>
<TM id="1853" type="MEAS" addr="50012" format="INT32_HW_LB"/>
<TM id="1854" type="MEAS" addr="50014" format="INT32_HW_LB"/>
</Frame>
Example 20: Attributes composing the TM node

13.4.3.3 Bit Write Node (Co)

A Frame node can contain as many Bit Write (Co) nodes as necessary. This node contains the following attributes.

Attribute name Description

Unique ID number within the entire
id
configuration
basicAddrOpen Basic address
bitAddropen Bit offset
Table 20: Attributes composing the Co node

<Frame numFrame="13" type="Co" numFct="15" frequency="200" beginAddr="18000"

length="24">
<Co id="1045" basicAddrOpen="18002" bitAddrOpen="0"/>
<Co id="1046" basicAddrOpen="18000" bitAddrOpen="0"/>
<Co id="1047" basicAddrOpen="18001" bitAddrOpen="0"/>
<Co id="1165" basicAddrOpen="18005" bitAddrOpen="0"/>
<Co id="1166" basicAddrOpen="18003" bitAddrOpen="0"/>
<Co id="1838" basicAddrOpen="18019" bitAddrOpen="0"/>
</Frame>
Example 21: Attributes composing the Co node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 85

13.4.3.4 Register Write Node (Sp)

A Frame node can contain as many Register Write (Sp) nodes as necessary. This node contains the following
attributes.

Attribute name Description

Unique ID number within the entire
id
configuration
basicAddrOpen Basic address
bitAddropen Bit offset
Optional but recommended attribute
Register Value Format (String or Uint16)
REAL32=0
INT32TOREAL32=1
format
INT32=2
INT16=3
If attribute is absent or incorrect, 0 or 1
depending on control.
Optional but recommended attribute
Byte order, string composed of 4 mandatory
byteOrdering (optional but
numbers 1..4 (String)
recommended)
Ie. “1234” or “4321”
Default value is “4321”
Table 21: Attributes composing the SP node

<Frame numFrame="19" type="Sp" numFct="16" frequency="200" beginAddr="24000"

length="10">
<Sp id="1940" basicAddrOpen="24005" bitAddrOpen="0" format="UINT16_LB"
byteOrdering="4321"/>
<Sp id="1941" basicAddrOpen="24006" bitAddrOpen="0" format="UINT16_LB"
byteOrdering="4321"/>
<Sp id="1942" basicAddrOpen="24008" bitAddrOpen="0" format="UINT16_LB"
byteOrdering="4321"/>
</Frame>
Example 22: Attributes composing the Co node
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 86

13.5 MODBUS ADDRESSING FORMAT

The Modbus network requires some specific datapoint addressing within the Signal List file.

The Signal List is a text file in CSV format (Comma Separated Value). It describes the datapoints to be used in
a given LAN within EcoSUI. The details concerning the general format of the Signal List file can be found in the
Signal List section of this document.

The addressing format is as follows:

<IED IP ADDRESS>:<IED IP PORT>@<IED MODBUS ADDRESS>;<MODBUS FUNCTION CODE>;<MODBUS ADDRESS>

Description Format Example

IED IP ADDRESS IP address 100.100.16.69
IED IP PORT 0.. 65535 502
IED MODBUS ADDRESS 1.. 254 1
MODBUS FUNCTION CODE 1, 2, 3, 4, 5, 16 16
MV <modbus address> 5001
xPS <bit number>@<modbus address> 0@6
MODBUS ADDRESS
SetPoint <modbus address> 500
xPC <bit number>@<modbus address> 0@500
Table 22: Signal list addressing for a Modbus LAN

SPS,INC_1#GW_1,100.100.12.191:502@248;1;0@17,SS1,SS1_BB1,INC_1,MINOR_FAULT,NO,SPS___AlarmLo0,,,MIMIC,
MV,INC_1#GW_1,100.100.12.191:502@248;3;45002,SS1,SS1_BB1,INC_1,I1,NO,MV_0,0,6000,MIMIC,
SP,INC_1,100.100.12.191:502@1;16;0@5,SS1,SS1_BB1,INC_1,MILLI,NO,SP_0,0,65535,,
SPC,GW_1,100.100.12.191:502@248;15;0@18002,SS1,SS1_BB1,INC_1,REM_RESET_CNTRL,NO,SPC_Control0,,,MIMIC,
Example 23: Signal list addressing for a Modbus LAN within the Signal List
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 87

13.6 MODBUS HOT-HOT REDUNDANCY

13.6.1 LIMITATIONS
In a Hot-Hot redundancy configuration, when both equipments are connected, the first equipment notifying its
presence is declared as being Active and the other one is declared as Stand-by. EcoSUI will store only the events
and measurements coming from the Active IED; those coming from the Stand-by IED will be ignored.

EcoSUI cannot instantaneously detect an Active IED goes offline. Indeed, a brief time-lapse is needed between the
effective offline event and the detection of the offline state. Thus, no messages will be stored during this lapse.

13.6.2 RING.INI CONFIGURATION

The Modbus Hot-Hot redundancy shall be defined within the Ring.ini file as follows:

[HotHotRedundant]
NameOfIEDMain=NameOfIEDBackup

Example 24: Modbus Hot-Hot redundancy declaration within the Ring.ini file

13.6.3 ADDITIONAL DATAPOINTS FOR HOT-HOT REDUNDANCY

Five datapoints are automatically created in order to manage a Modbus configuration with Hot/Hot redundancy,

Description Type Values

Connection status of IED 1 SPS CONNECTED/DISCONNECTED
Redundancy status of IED 1 SPS ACTIVE/STAND-BY
Connection status of IED 2 SPS CONNECTED/DISCONNECTED
Redundancy status of IED 2 SPS ACTIVE/STAND-BY
Redundancy switch. 0 = Set Redundant IED as Active
SPC
Control to manually select the active IED 1 = Set Main IED as Active
Table 23: Datapoints needed for Modbus Hot-Hot redundancy
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 88

The following figures show an example of the datapoints created for managing the redundancy.

Figure 23: Example of Status datapoints for HOT/HOT redundancy

Figure 24: Example of Control datapoints for HOT/HOT redundancy

13.7 SELECTING THE ACTIVE IED

When the Active IED is detected to be Disconnected, then the Stabd-by IED becomes the Active one. When the
disconnected equipment comes back online, it is declared as Stand-by.

The User can manually select the IED to be set as Active by using the Control Datapoint described in section 8.3.
The following table describes this behavior:

Value of Control Datapoint Main IED Redundant IED

0 Stand-by Active
1 Active Stand-by
Table 24: Manually selecting the Active IED
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 89

13.8 SUPPORTED MODBUS FUNCTION CODES

The following table describes the by the Modbus implementation in EcoSUI.

Function Code Description Supported

1 Read Coils Supported
2 Read Discrete Inputs Supported
3 Read Holding Registers Supported
4 Read Input Registers Supported
5 Write Single Coil Supported
6 Write Single Register Supported
7 Read Exception Status Not Supported
8 Diagnostic Not Supported
11 Get Com Event Counter Not Supported
12 Get Com Event Log Not Supported
15 Write Multiple Coils Supported (Only With Free Controls –
Particular function, only accessible from HMI)
16 Write Multiple Registers Supported
17 Report Slave ID Not Supported
20 Read File Record Not Supported
21 Write File Record Not Supported
22 Mask Write Register Not Supported
23 Read/Write Multiple Registers Not Supported
Table 25: Function codes
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 90

13.9 DEFINE A MODBUS LAN

To implement a MODBUS LAN, follow the procedure:

13.9.1 CREATE A RINGS FOLDER

Create a Rings folder such as C:\MCIS\Rings\MODBUS

13.9.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the Ring.ini file of EcoSUI. This file contains important SBUS Server LAN
properties:
• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\MODBUS\
• And copy it in the previously created folder (C:\MCIS\Rings\MODBUS)
• Open the file Ring.Ini file with Notepad++.
• Fill in the following parameters
o Type= Enter EXTERNALDLL
o Enabled= Write the SBUS Server names (separated with ;) where this LAN is enabled.

Note: Refer to the chapter about ring.ini file to get additional information on the possible OPC parameters.

13.9.3 L_MODBUS.DLL
In the LAN, the L_Modbus.dll shall be present (stored in the C:\MCIS\Bin folder).
DLL is automatically copied by EcoSUI from C:\MCIS\Bin to ring folder.

13.9.4 L_MODBUS_XML_0.XML
Create one L_Modbus_XML_0.xml file per ModbusMaster LAN (L_Modbus_XML_1.xml, L_Modbus_XML_2.xml...)
Refer to the chapter L_MODBUS_XML_0.XML DATA STRUCTURE for further information.

13.9.5 CREATE THE PROFILES.XML FILE

The Profiles.xml file contains datapoint profiles referenced by the SignalList:

• <SPS>, <DPS>, <MPS>

• <SPC>, <DPC>, <SP>
• <MV>

This is where the user can define On and Off states when signal is alarmed or not, specify the interval at which MV
data flow will be archived….
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 91

13.10 CREATE AND PREPARE THE SIGNAL LIST

The Signal List gathers the list of datapoints managed by the MODBUS LAN.

To enable MODBUS protocol, set up a signal list according to your needs.

Note: Refer to the chapter about the SignalList file for further information on the contents of a SignalList.

13.11 DEPLOY
Now load datapoint configuration from SignalList to the CentralDB.

• From Data Acquisition tab, click the Tools button.

• Select Tools >Load Configuration from SignalList

• Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 92

14. SNMP LAN

This chapter describes how to implement SNMP protocol for data acquisition (LAN) in EcoSUI.
SNMP is abbreviation of Simple Network Management Protocol. SNMP protocol provides generic information
such as:
• Status of equipment of a Printer or switch
• Hard Drive capacity for a computer
• Packet lost for a Switch

EcoSUI gives capability for user to monitor information from any equipment compliant with this protocol, for
instance, to collect data from SNMP V1/V2 servers such as Ethernet switches.

To implement a SNMP protocol-based project, follow the methodology below:

14.1 CREATE A RING FOLDER

• Create a ring folder such as C:\MCIS\Rings\SNMP

14.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the Ring.ini file of EcoSUI. This file contains LAN properties.
To configure, please follow instructions:

• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\SNMP\

• Copy it to the previously created folder (C:\MCIS\Rings\SNMP)
• Open the Ring.ini file with Notepad++.
o Fill in the following parameters
o Type= Enter SNMP

NOTE: Refer to the chapter 5 of this manual about Ring.ini to get additional information on the possible
parameters
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 93

14.2.1 EDIT THE HOST FILE

In C:\Windows\System32\drivers\etc\hosts, add or edit SNMP servers IP addresses:

14.2.2 PREPARE THE SIGNAL LIST ACCORDING TO MIB ADDRESSING

Signal List gathers the datapoint configuration. In this file, specify the type, the equipment name, the SNMP
address...

To enable SNMP protocol, set up the signal list according to MIB (management information base) of SNMP
servers:

SNMP hostname

MIB address
Profile used

Note: Refer to the chapter 4 about the SignalList file, EcoSUI_EN_AN_ECOSUIENG_E manual for further
information on the contents of a SignalList.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 94

14.2.3 HOW TO FIND MIB ADDRESSING

Refer to RFC standards on internet:

• RFC 1213-MIB (http://www.oidview.com/mibs/0/RFC1213-MIB.html)

Example : port status

• OID is an identifier used to name and point to an object in the MIB hierarchy. Another example of MIB with
many OIDs as given below.

Source: http://www.oidview.com/mibs/0/Printer-MIB.html
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 95

Note: Reference to see OID description: http://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?module=Printer-

MIB&fournisseur=CISCO
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 96

14.3 PREPARE PROFILES.XML FILE

This file manages states of datapoints.
This is where to define On and Off states when signal is alarmed or not.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 97

By default, SNMP V2 is used but the user can force SNMP V1 by adding dedicated elements in profile:

Note: For further information about the profile.xml attributes and contents refer to the Profile section in this
document.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 98

14.4 DEPLOY
Load datapoint configuration from the SignalList file to the CentralDB.

• From Data Acquisition tab, Tools > Load Configuration from SignalList

• Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 99

15. OPC LAN

This chapter describes how to implement OPC protocol for data acquisition (LAN) in EcoSUI.

The OPC defines the Object Linking and Embedding (OLE) for Process Control. OPC is an open method of
communicating and exchanging data between software applications using COM (Component Object Model)
interfaces. EcoSUI is a Digital Control System suite of OPC Clients and Server applications.

To implement an OPC protocol-based project, follow the procedure:

15.1 CREATE A RING FOLDER

Create a ring folder such as C:\MCIS\Rings\OPC.

15.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the Ring.ini file of EcoSUI. This file contains important SbusServer LAN
properties.
• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\OPC\
• And copy it in the previously created folder (C:\MCIS\Rings\OPC)
• Open the Ring.Ini file with Notepad++.
• Fill in the following parameters
o Type= Enter OPC
o Enabled= Write the SBUS Server names (separated with ;) where this LAN is enabled.

NOTE: Refer to the chapter about Ring.ini file to get additional information on the possible OPC parameters.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 100

15.3 CREATE THE PROFILES.XML FILE

The Profiles.xml file contains datapoint profiles referenced by the SignalList:
• <SPS>, <DPS>, <MPS>
• <SPC>, <DPC>,
• <MV>

This is where to define On and Off states when signal is alarmed or not.

Profile properties are similar to the ones in EPAS SCE.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 101

15.4 CREATE AND PREPARE THE SIGNAL LIST

Signal List gathers the list of datapoints managed by the OPC LAN.

To enable OPC protocol, set up your signal list as indicated below:

• Column 1: Datapoint type (SPS, DPS, MPS, MV…)

• Column 2: OPC Equipment Address (for ex : //localhost/PACIS.OPC SERVER.V2.0)
• Column 3: OPC Tag (the OPC server provides OPC tags such as //<pc name>/<Server ID>/tag)
• Column 4: Voltage level
• Column 5: Bay name
• Column 6: Module name
• Column 7: Long name
• Column 8: Spare
• Column 9: Profile reference

Note: Refer to the chapter about the SignalList file for further information on the contents of a SignalList.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 102

15.5 IMPORT & FIX SCD FILE

Now, import the SCD file. This step is important as typical SCD incompatibilities generated by SCE will also be
fixed by the process.

• To do so, from Data Acquisition tab, click the Tools button.

• Select Advanced > Import & Fix SCD
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 103

15.6 DEPLOY
Now load datapoint configuration from SignalList to the CentralDB.

• From Data Acquisition tab, click the Tools button.

• Select Tools >Load Configuration from SignalList

• Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 104

16. VIRTUAL LAN

This chapter describes how to implement a virtual LAN in EcoSUI using formulas.

16.1 PRINCIPLES
You may need EcoSUI to carry out actions based upon checks and logical conditions on datapoints of your
configuration.

You may want the application to perform a set of actions in case A, but perform another set of actions in case B. It
is possible to create and compute data through formulas by defining logics and equations based on any inputs of
your database.

Formulas allow you to implement decision points in the program, associated with conditions. Usually, you will be
checking what the value of a variable is. Then based on this value, you will trigger specific actions on electrical or
system devices (open, close), animation of busbar and so on.

To implement a virtual LAN (no data acquisition), follow the procedure:

16.2 CREATE A RING FOLDER

Create a ring folder such as C:\MCIS\Rings\Formulas

16.3 EDIT THE RING.INI FILE

• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\Formulas\
• And copy it in the previously created folder (C:\MCIS\Rings\Formulas)
• Open the file Ring.Ini file with Notepad++ (or any editor).
• Fill in the following parameters
o Type= Enter VIRTUAL
o Enabled= Write all SBUS Server names (separated with ;) where this LAN is enabled.

Note: Refer to the chapter about Ring.ini file to get additional information on the possible parameters.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 105

16.4 CREATE THE PROFILES.XML FILE

The Profiles.xml file contains datapoint profiles referenced by the SignalList:
• <SPS>, <DPS>, <MPS>
• <SPC>, <DPC>,
• <MV>
• <STR>

This is where to define On and Off states when signal is alarmed or not.
Profile properties are similar to the ones in EPAS SCE.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 106

16.5 DEFINE FORMULAS

The user can define formulas from the Sbus Server if several HMI are deployed or directly from MIMICS views in
EcoSUI.

16.5.1 FROM SBUS SERVER

1. Start Sbus Server from the task bar.
2. Click the Formula tab

3. Click Add at the bottom the screen to add a formula.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 107

4. A new row appears in the table:

5. Double click this row to open the Formula editor. From this editor, click the Signal List button to browse
the database to select input signals.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 108

6. The State Viewer appears on screen. It shows a picture of the current situation of all data points issued
either from wired signals, data from IED as well as system self monitoring information. The left part of the
window displays a tree view of the database, which is used as a filter.

7. Expand the tree view on the left and check the desired signals. The selected signals appear in the table on
the right.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 109

8. Just double click the signals in the table to use them in your formula (they are then automatically added to
the Formula Editor).

9. Add as many signals as necessary.

10. Then, specify a single logical expression by linking signals with an operator or combine several logical
expressions to form a complex condition by using the operators AND and OR.

Note: do not forget to add brackets before and after your statement.

11. Select the type of formula using the Formula Quality drop-down (Always valid, Valid if all signals are
valid, Valid if one signal is valid).
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 110

A real-time syntax checker is enabled. EcoSUI monitors formula as you type, flagging when the syntax is not
correct by displaying a diagnostic message in the split view and indicating which line it's on.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 111

16.5.1.1 Actions
‘Action On’ is executed when formula evaluation is true or is a number (double float, integer).
‘Action Off’ is executed when formula evaluation is false.

Possible actions are:

Help on Actions is accessible from the ‘Help’ button:

Examples:

SETIN [Formula / Formulas / A / B / CPU Overload]

SETPOINT [SS1 / VL110 / Q01 / MV_SETPOINT]
CMD_EXECUTE [SS1 / VL110 / Q03 / QA1 / Position. Control]@1

SET [Formula / Formulas / A / B / Computed SPS]@1

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Carefully evaluate the impact of formulas before usage.

Failure to follow these instructions can result in injury or equipment damage

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 112

16.5.1.2 Alarm Status

It is possible to retrieve alarm status for SPS and DPS datapoints.

5 different possible values:

• Inactive and Unacknowledged alarm
• Active and Unacknowledged alarm
• Active and Acknowledged alarm
• Inactive and Acknowledged alarm
• alarm not present (never raised or cleared)

In the Formulas editor, click the Help button.

In the drop-down menu, select Mnemonic parameter > SPS/DPS/MPS > @ALARMSTATUS
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 113

• Returns 0 ACT / ACK

• Returns 1 ACT / NACK
• Returns 2 NACT / ACK
• Returns 3 NACT / NACK
• Returns 4 NOT PRESENT
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 114

16.5.1.3 Getting Help on Formulas From Sbus SERVER

The user can get general help on Formulas from the Sbus Server.

• Right-click on the SBUS Server window to display the context menu.

• Then, select Show Help.

A help guide containing information on expressions & functions to be used in Formulas appears on screen.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 115

16.5.2 FROM ECOSUI MIMICS

It is possible to add formulas to objects of in HMI views. To do so, EcoSUI HMI has to be in “Edit Mode” (CTRL +
SHIFT + ALT + F12).

Once in Edit mode, right-click anywhere in the HMI view and select Unlock Mimic.

1. Double click an object in the mimic where to add a formula. The Mimic editor shows up:

EcoSUI allows the user to add formulas to the following objects:

• [object]_Mnemonic
• [object]_Interlock
• [object]_HideCond
• Rectangle_CondX

2. In the Mnemonic field, for instance, enter evaluate()

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 116

3. Click ” …” next to the mnemonic field to open the Formula Editor.

4. Repeat the same methodology as described in the previous section.
5. The Analog0 object will now display the result of "evaluate" function.

Note: Tooltip property of "Analog_Mnemonic"

• The tooltip can only be available on mnemonic value.
The tooltip on analog value cannot be empty and if the value of the parameter is set to empty it will be
forced to CURVE.
• Mnemomic attribute of analog value object can take a datapoint and a function (evaluate() etc..) but for
function the tool tip will not be displayed.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 117

16.5.2.1 Help on Formulas

The Formula editor provides a useful help on conditions and parameters to be used in formulas.

Click the Help button at the bottom of the screen to get help on functions and parameters:

It is possible to mix analogical & numerical values in formulas but functions that require numerical values are
specified by (double)
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 118

16.5.3 OUTPUT FILES

Formulas are stored in the Formulas_SBUSServer text file located in C:\MCIS\Formulas\<PC name> directory.
It contains all formulas you may have defined for your HMI objects.

This file contains the same information as it appears in the Formulas table in the Sbus Server. Columns are
separated by ## based on the following principle:

• Formula ## Action on ## Quality

o ####0 for Always Valid
o ####1 for Valid if all signals are valid
o ####2 for Valid if one signals is valid

The user can directly modify the formulas text file. To refresh the modifications in the Sbus Server, just click Reload
in the Formulas tab:

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Carefully evaluate the impact of formulas before usage.

Failure to follow these instructions can result in injury or equipment damage

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 119

16.6 DEFINE SCRIPTS

16.6.1 PRESENTATION

The user can define own Python scripts dedicated to specific project.

Script allows to execute specific functions for EcoSUI:

• Get and Set values (datapoint)
• Set commands
• Signal registration and callbacks
• Signal Quality forcing
• Debug

The scripts are executed by the EcoSUI Sbus server and can be started automatically or manually.

16.6.2 PREREQUISITES

In order to excute python scripts, IronPython software has to been installed on EcoSUI platform. IronPython is
an open-source implementation of the Python programming language.

The IronPython version 2.7.3 is recommended. The software can be downloaded from https://ironpython.net/.

16.6.3 CREATE SCRIPTS

The first step is the creation of your own script(s) file(s) dedicated to the specific project (file extension .py)

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Carefully evaluate the impact of scripts before usage.

Failure to follow these instructions can result in injury or equipment damage

NOTE: To help to create scripts, use the Help for Special Python functions oriented EcoSUI:

1. Start Sbus Server from the task bar.

2. Click on Scripts tab

3. Click on Help button, a list of functions is available

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 120

16.6.1 CONFIGURE SCRIPTS

16.6.1.1 Script(s) file(s) installation

The second step is the copy of script(s) file(s) into the EcoSUI platform.
• Copy Python script(s) file(s) into the C:\MCIS\Scripts folder (and not into the <PC_NAME> subfolder)

NOTE: The EcoSUI installer automatically creates the folder C:\MCIS\Scripts and a subfolder with the PC name
(<PC_NAME>) where the application EcoSUI is installed. The <PC_NAME> subfolder is used to store the
configuration files for triggering the scripts.
There are as many <PC_NAME> subfolders as PCs running scripts. For example, in case of redundancy, there are
the <SERVER1> and <SERVER2> subfolders on both PCs and the SBUS Server will look for the scripts configuration
file inside the subfolder matching its own PC name. It will then execute the scripts registered within its own
configuration file. In this way, the configuration package can contain the scripts for the whole platform.

16.6.1.2 Configuration for script running

The last step is the configuration of parameter file Scripts_SBUSServer.xml.

This file has to be edited in order to indicate the list of script(s) file(s) and parameters for execution.
To configure file, please following:
• Open the file Scripts_SBUSServer.xml file in C:\MCIS\Scripts\<PC_NAME>\ with Notepad++ (or any
editor).
• For each script, fill in the following line <Script /> with mandatory parameters:
o filename= Enter the path and the file name of the Python script (.py)
o when= choose the running mode: start manually “1” or start automatically when SBUS server is started
“0”.

16.6.2 EXECUTE SCRIPTS

1. Start Sbus Server from the task bar.
2. Click on Scripts tab

3. Click Start button to execute script(s)

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 121

NOTE: The user does not need to press the Start button in the case of a script configured in automatic mode
because it will be executed automatically by the EcoSUI SBUS server.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 122

16.7 PREPARE THE SIGNAL LIST

Once the required formulas are defined, add them to the Formulas SignalList file.
The Formulas SignalList gathers the list of datapoints manages by the virtual LAN.

Set up a signal list as indicated below:

• Column 1 : Datapoint type

• Column 2 : Equipment name
• Column 3 : Address of the datapoint (formulas defined earlier)
• Column 4 : Voltage level name
• Column 5 : Bay name
• Column 6 : Module name
• Column 7 : Long name
• Column 8 : Spare
• Column 9 : Profile reference

Note: Refer to the chapter about the SignalList file for further information on the contents of a SignalList.

16.8 DEFINE EXTRACTION REPORTS

The user can define extractions reports from the Sbus Server

12. Start Sbus Server from the task bar.

13. Select Extraction tab

16.9 DEPLOY
Now load datapoint configuration from SignalList to the CentralDB.

• From Data Acquisition tab, click the Tools button.

• Select Tools >Load Configuration from SignalList

• Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 123

17. PERFMON LAN

This chapter describes how to implement a PerfMon LAN to collect system data in EcoSUI.
PerfMon (Performance Monitor) is an embedded system monitoring program in Windows.
This system is used to:
• Monitor various activities on a computer such as CPU usage or memory usage.
• Determine the cause of problems on a local or remote computer by measuring the performance of
hardware, software services, and applications…
Thanks to a specific parameterization detailed below, it is possible to collect data from PerfMon tool in order to
visualize important system information such as, % processor time, threads, handles, % disk space in the State
Viewer of SBUS Server.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 124

17.1 DEFINE A PERFMON RING

To implement a PerfMon LAN, follow the procedure:

17.1.1 CREATE A RING FOLDER

Create a ring folder such as C:\MCIS\Rings\PerfMon

17.1.2 EDIT THE RING.INI FILE

The type of protocol to be used is defined in the Ring.ini file of EcoSUI. This file contains important SBUSServer
LAN properties.

• Edit the sample Ring.ini file in C:\MCIS\Examples\Rings_Example.zip\PerfMon

• Copy it to the previously created folder (C:\MCIS\Rings\PerfMon)
• Open the Ring.Ini file with Notepad++ software.
o Fill in the following parameters
o Type= Enter PERFMON

Note: Refer to the chapter about Ring.ini file to get additional information on the possible parameters.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 125

17.2 RETRIEVE THE PERFMON ADDRESS

To retrieve the PerfMon address of a counter source you want to use or monitor in EcoSUI, follow the procedure:

• On your keyboard, press Windows button + R and type PerfMon in the Run dialog that shows up.
• Click OK.

• The Performance Monitor tool appears on screen. Click Performance Monitor in the left pane:
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 126

The right-pane turns into a live graph/chart as shown below.

Let’s take the example the user is trying to look at memory usage. He will need to add it to what’s tracked by the
live graph. To do so, click the + sign.

Now scroll down the list of counters in the left pane and select Memory, then click Add. Memory is added as an
active counter in the right-pane, and once it is, click OK to save changes and exit.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 127
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 128

• Back to the Performance Monitor screen, click Copy Properties icon:

• Start Notepad++. In the File menu, select New and copy the selection in a new tab.
• Locate the desired counter path and copy the associate value :

o by omitting the backslash “\” at the beginning of the path:

o by reverting backslash into simple slash in the path
For instance: Memory/Available Kbytes

Copy this modified path into the PerfMon SignalList as explained in the next chapter.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 129

17.2.1 CREATE AND PREPARE THE SIGNAL LIST

The .SignalList file gathers the list of datapoints managed by the PerfMon LAN. In this file, specify the
equipment name, the PerfMon address and so on.

1. Edit the sample PerfMon.signalList file in C:\MCIS\Examples\Rings_Example.zip\PerfMon

2. Copy this file to the folder C:\MCIS\Rings\PerfMon
3. Open the PerfMon.signalList file with Notepad++ and setup the signal list as indicated below:

Column Value
Top row 1 {Sitename, SubstationName}
Top row 2 Site name or substation name for treeview

#Type Datapoint type :

SPS, DPS, MPS, MV, SPC, DPC, STR
If followed by ‘_SYS’, datapoint belongs to System part of treeview (ex SPS_SYS)
#Equipment Equipment name
#PerfMon address Enter the PerfMon address.
Refer to the procedure explained in the previous chapter “Retrieve the PerfMon Address”

Note: Refer to the chapter about the SignalList file for further information on the contents of a SignalList.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 130

17.2.2 DEPLOY A PERFMON RING

The PerfMon Ring.ini & PerfMon SignalList are parameterized. Now, load the datapoint configuration from
SignalList to the CentralDB.

• From Data Acquisition tab, click the Tools button.

• Select Tools >Load Configuration from SignalList

• Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 131

18. UPGRADE AN SCE PROJECT TO ECOSUI

This chapter describes the steps to be performed to upgrade an existing SCE configuration database into the
EcoSUI environment.

18.1 REQUIREMENTS
For a better understanding of objects and attributes of a referenced database, it is recommended to be familiar with
SCE.

Before upgrading a SCE configuration to EcoSUI, the user should have a clear idea of the steps to be performed
during the migration. The migration procedure is reserved for PCL Lattes System Engineers only.
Please contact Schneider Electric Support for a migration procedure.

18.2 OVERVIEW OF SCE PROJECT FILES

When creating a new configuration using EPAS SCE, the System, Electrical & Graphical topologies are
automatically instantiated via root objects:

• A ‘Site’ object for the electrical topology, containing one ‘Substation’ object
• A ‘Scs’ object for the system topology, containing one ‘Ethernet network’ object (Scs is an abbreviation of
Substation Control System)
• A ‘Graphic’ object for the graphical topology.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 132

18.3 SETUP ECOSUI

18.3.1 DECLARE OI & SERVERS

Start by declaring the operating & engineering workstations & Servers.

This information appears in the package.ini file.

1. Go to C:\MCIS and open the package.ini file

2. Enter the EPAS databag server in the [GENERAL] section
3. For each PC, create a dedicated [PC_NAME] section:
o Replace PC_NAME with the equipment name
o Specify the Type = HMI, GTW or SBUSServer
o Enter the IP Address

Any equipment on the LAN has to be declared the same way: one section per EcoSUI equipment.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 133

18.3.2 SPECIFY THE SERVERS IP ADDRESSES

Modify the SERVERS.INI file in order to specify the IP address of the main & backup servers.

1. Go to C:\MCIS
2. Open the file SERVERS.INI file at the root of the folder.

3. In the [CAEDatabases] section, enter for

• IP0: the IP address or host name of the main computer managing the first Config/Alarms/Events
Database
• IP1: the IP address or host name of the backup computer managing the second Config/Alarms/Events
Database. Leave empty if there is only one CAE Database.

Save the modifications.

18.3.3 CONFIGURE YOUR EQUIPMENTS

Modify the MCISEqpt.ini file in order to specify the device characteristics.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 134

1. Go to C:\MCIS
2. Open the file MCISEqpt.ini file at the root of the folder. This file opens a [Dummy_EQPT] section header.

3. Duplicate this [Dummy_EQPT] section as an example and adapt it for each equipment:
• HasLogbookPrinter_Help=1 If the equipment uses a log book printer
• HasSBUSServer_Help=1 if it makes data acquisition
• HasHMI_Help=1 if it is a EcoSUI computer
• HasGateway_Help=1 if it is an OPC gateway
• HasCentralDB_Help=1 if it is an archive computer
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 135

18.4 SETUP SBUS SERVER DATA ACQUISITION

EcoSUI supports the following protocols for Data Acquisition (LAN):
• IE C61850 edition 1 and edition 2
o From EPAS database (SCE ZIP file)
o From the Signal List (SCD file from SET)
• Modbus TCP
• OPC
• …

Whatever the type of protocol selected for your project deployment, EcoSUI requires the parameterization of
specific files, which are detailed in this EcoSUI documentation.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 136

18.5 IMPORT SCE MIMICS FILES

This section describes how to upgrade the graphical part and electrical links from a SCE database to EcoSUI
environment.

To reuse the graphical part designed in EPAS SCE, export the .mpc file from the SCE. This process will generate
a package of the configuration files that will be used by the migration tool (.zip folder). The migration tool will to
convert graphical data and electrical links in order to be compliant with EcoSUI environment.

• Start EPAS SCE

• Open the .mpc file of the configuration to be upgraded
• Depending on the SCE version, click Tools > Export or Data > SCE Data > Export to generate the
configuration package.
• In the Export Manager popup, select the files to be exported:
✓ Check the Database box
✓ Click the Check all icon in the tool bar

All boxes are checked.

• Click Export.
• Enter a file name and select the folder where the zip file will be exported. Click Save.

The export process is started.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 137

18.5.1 EXTRACT THE IMAGE FOLDER

To update EcoSUI environment with the images used in your configuration:
• Unzip the exported .zip file preferably in an empty repository (the content is flat)
• Open the .mpc file as a zip file and extract the image folder (right click zip file and extract or unzip file)

The Images folder will be used by the migration tool to replace the one in C:\MCIS\Mimics and update EcoSUI
environment.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 138

18.5.2 RUN THE MIGRATION PROCESS

The .zip file has been generated in the folder specified earlier. It contains a Catalog.xml file that will be used as
input data to the migration tool.

• Unzip the zip file to make the catalog.xml file accessible.

• Once unzipped, double click the PacisXmltoMCIS.exe migration tool.

The application appears on screen.

• Click Choose Input File. The migration tool uses the catalog.xml file to generate a Worskspace
output folder containing the MIMIC files compliant with EcoSUI environment. Browse your machine and
select the Catalog.xml file that is in the unzip directory.
• Choose Output: Browse your machine and select where the Worskspace folder will be generated. By
default, the program automatically sets the same folder as for export. You can change knowing that it is
not a big deal keeping the same directory as sub-folders will be created.
• Either copy the extracted image folder in C:\MCIS\Mimics\Images or click on "Choose Source Image
Directory" and select the extracted image folder.
• Click Process to start the export: it will create a folder for each workspace present in the mpc export.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 139

Then, copy the entire content of the desired workspace folder in the MCIS\Mimics folder.

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
◼ Close and restart the PacisXmltoMCIS.exe migration tool before using it on
other projects.

Failure to follow these instructions can result in injury or equipment damage.

Elements in the GUI

Options Description
Project Identifier To add a part of text in filenames not to replace former files such as TPL ….
Reserved to advertised users
Create button Replace objects that have actions with buttons
Use ExtID To use human names voltage ….
If not checked, names will appear like this: site 1 … site xxx
Interlocks If not checked, interlocks are not imported to EcoSUI
Automation If not checked, automation information is not imported to EcoSUI

At the end of the migration process, a log summurazing the detected errors appear at the bottom of the window.
Two reports are also generated: one for interlocks and another for views …
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 140

18.5.3 FINAL ADJUSTMENTS IN ECOSUI

The migration tool has now generated an output folder called Workspace.zip. It contains the mimics files required
for running your configuration under EcoSUI.

Best practice: rename the Mimics folder in C:\MCIS to revert its contents in case of troubles.
• In C:\MCIS, rename the Mimics folder to Mimics_old for instance.
• In the Output folder, extract the <Workspace>.zip file.
• Rename the unzipped folder <Workspace> to Mimics and paste it to C:\MICS.

Manual adjustments are necessary to setup EcoSUI environment:

18.5.3.1 EcoSUI Workspaces

EcoSUI is based on workspaces.ini file. This file defines how the HMI & System views will be restituted on the
operator screen.
1. To setup these workspaces according to your project, go to C:\MCIS\Mimics
2. Open the Workspaces.ini file.
3. Add a workspace and change workspace dimensions or add a background image if need be.

Sections Attribute Description

Workspaces WKSPx Define all workspaces
in the main mimic
General GlobalZoomFactorX All workspaces will be
resized according to
this factor
GlobalZoomFactorY All workspaces will be
resized according to
this factor
AutoAdjustGlobalZoomFactor Automatically Adjust
Global Zoom Factor,
comparing project
screen resolution and
current screen
resolution
ProjectScreenResolutionWidth Width of Project Main
Screen Resolution
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 141

ProjectScreenResolutionHeight Height of Project Main

Screen Resolution
WorkspacesLayer EnableWorkspaceLayers to activate Layers
Management for
Workspaces, 0
otherwise
Refer to §14.3 of
EcoSUI User Manual
for more information
related to layers
PreloadedMimics WKSP1=My_View_Name.cfg;Other_View_On_Same_Workspace_Name.cfg Add a list of workspace
index, with name of the
preloaded mimic, this
should reduce opening
time, BE CAREFULL it
has a direct impact on
RAM usage !!!

18.5.3.2 EcoSUI Images

In C:\MCIS\Examples:
• Open the Standard Images.zip file and copy-paste the contents to C:\MCIS\Mimics\Images
• Open the Standard Popups.zip file and copy-paste the contents to C:\MCIS\Mimics
• Open the Standard Languages.zip file and copy-paste the contents to C:\MCIS\Mimics\Languages

18.5.3.3 EcoSUI Users & Profiles

C:\MCIS\Mimics\Users:
To use exported EPAS User Profiles:
• Delete the PacisProfiles.ini file (filenames without underscore)
• Rename the PacisProfiles_.ini to PacisProfiles.ini

18.5.3.4 Launch Popup control

It is recommended to manually configure user profiles in EcoSUI to make it possible to launch the control sequence
from HMI according to the SCE configuration.

• In your mimics, select one device

• Double-click to open the object properties and modify the ActionProfiles parameter
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 142

18.5.3.5 Auto Log-off

Configure ECOSUI to fix the inactivity time for auto log-off to match values set in SCE DB.

For the Standard version,

• Open the General.ini file in the Mimics folder and set the value needed for your project in the
UserActiveTimeout field.

For the Secured version,

it is the Cyber Security component which manage timer.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 143

18.5.3.6 Alarm Color Management

18.5.3.6.1 Configuration

Configure manually Alarm colors which are not upgraded by default:

• Launch Alarm Object mimic view in edit mode, and unlock
• Double-click the Alarm object to access the mimic object property window.
• Expand the On the left of object property window, expand the tree-view and go to the AlarmControl node
• Set the desired values for the alarm color parameters on the right:

• AlarmControl_GravityActiveAckBackColorX
• AlarmControl_GravityActiveAckForeColorX
• AlarmControl_GravityActiveNotAckBackColorX
• AlarmControl_GravityActiveNotAckForeColorX
• AlarmControl_GravityNotActiveAckBackColorX
• AlarmControl_GravityNotActiveAckForeColorX
• AlarmControl_GravityNotActiveNotAckBackColorX
• AlarmControl_GravityNotActiveNotAckForeColorX

Abbreviation Signification
Back Background
Fore Foreground
X = <1..4> 1 / 2 / 3 / 4 are severity level “4” is the highest while “1” is the smallest
severity
Active when the alarm is SET
NotActive when the alarm is RESET
Ack acknowledged
NotAck unacknowledged
Values RGB

Features of Alarm color:

SNo Description Example
1 Each entry has a value field made of a 3-tuple value “255, 128, 0”.
(3 values separated with a comma). The values are in
the range <0..255>
2 Any invalid numeric value will internally default to “255,255,400” →
“255” but the invalid value will still be visible. “255,255,255”
3 Any non-numeric value will default to “0” but the “255,255,tagada” →
invalid value will still be visible. “255,255,0”

NOTE: In the client HMI, the foreground and background color of an alarm shall be the one set in the mimic editor
for its level.

EXAMPLE: If ActiveNotAckBackColor1 = 192,0,0 (dark red) and ActiveNotAckforColor1=255,255,255 (white),

then if the alarm SET is of a priority (or “level”) 1 AND unacknowledged, its date of appearance, label, state, etc.
will be shown as white on dark red.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 144

18.5.3.7 Direct Link Management

Direct link configuration allows the user to access up to two specific views by right clicking on an alarm and
choosing one of the two possible locations which will be displayed in a popup menu. Those two locations are “per
alarm” or “with wildcards”.

The destination view name is only the labels “Go to dedicated view 1” and “Go to dedicated view 2”.

In HMI Client, when parameter AlarmControl_EnableContextMenu=1, performing a right click on an Alarm

Viewer let user navigate to a view where mnemonic is visible by clicking on GoToDedicatedView1 or
GoToDedicatedView2 depending on the configuration. If AlarmControl_EnableContextMenu=1, when right-clicking
the alarm viewer, a pop-up menu appears.

NOTE: That menu has the following entries:

• Information,
• Comment
• Go to Dedicated View1
• Go to Dedicated View2
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 145

18.5.3.7.1 Configuration

The configuration is stored in « C:\MCIS\Mimics\Actions.ini ».

There are two sections named “GotoDedicatedView1” and “GotoDedicatedView2” (“per alarm” group) and two
sections named “GotoDedicatedView2_Via_Wildcards” and “GotoDedicatedView2_Via_Wildcards” (“per
wildcard” group).

The syntax is as follow:

<Mnemonic>=“show <number> <my_view.cfg>”
Where:
• <Mnemonic> is the data point address,
• <number> is the workspace where the view will be loaded,
• <my_view.cfg> the configuration file for the view.
NOTE:
• Mnemonic are automatically added in Actions.ini if user click on “Go to dedicated view 1” or “Go to
dedicated view 2” in context menu from an alarm viewer. The user can then edit the file and fulfill the line
with the relevant information.
• If Actions.ini doesn’t exist, it is created prior adding the line as stated here above.

18.5.3.8 Alarm Viewer Summary Management

The Alarm viewer summary can be displayed depending on the parameter AlarmControl_ShowAlarmSummary.
It can be accessed through the alarm view mimic editor
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 146

18.5.3.8.1 Configuration in Mimic Editor

Object Default Description

property
AlarmControl_S 0 When the value is 0, then the Alarm viewer summary is not displayed.
howAlarmSumm When the value is 1, then the Alarm viewer summary is displayed.
ary
The viewer displays a panel at the bottom of it with:
• The current page number and the total number of pages
containing alarms which correspond to the selected criteria (tree
node, or other filter).
• The total number of alarms corresponding to the criteria,
• The number of unacknowledged alarms,
• The number of alarms with level 1,2,3 or 4 according to the criteria.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 147

18.5.3.9 Sound Management

18.5.3.9.1 Configuration
User can configure different buzzer sounds according to the alarm level, parameters of the [Buzzer] section of the
General.ini file located in the Mimics folder. PlayWavSound property enables playing a custom WAV file or using
default PC sound. Only WAV sound files are supported.

Up to 4 different alarms level can be customized with a sound. Alarm level are in the <1..4> range. The four
instruction dedicated to those alarm levels are named “WavFilename_<1..4>”.
• WavFilename_1 is the WAV file associated to alarm level 1
• WavFilename_2 is the WAV file associated to alarm level 2
• WavFilename_3 is the WAV file associated to alarm level 3
• WavFilename_4 is the WAV file associated to alarm level 4

The syntax is as follow:

WavFilename_<1..4>=<absolute_path><filename.wav>
e.g. WavFilename_3=C:\myWavFiles\my_sound.wav

Note:
• if a sound file is left blank (i.e. “WavFilename_2=”), no sound will be played,
• if a sound file doesn’t exist, no sound will be played.

18.5.3.9.2 How it works

When an alarm occurs, the sound associated to its level will be played. If a new alarm occurs, the sound
associated to its level will be played only if its level is equal (same sound will be played) or higher than the previous
one (the sound associated to its level will be played). If an alarm (or all alarms) disappear (i.e. reset), the sound is
still played. The sound is no longer played when the user acknowledges them or press the “mute” button.

If PlayWavSound=0, default computer sound of the operating system is played,

If PlayWavSound=1, the customs sound is played:
• Alarm level 1: WavFilename_1 sound is played,
• Alarm level 2: WavFilename_2 sound is played,
• Alarm level 3: WavFilename_3 sound is played,
• Alarm level 4: WavFilename_4 sound is played.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 148

Property Condition Description

PlayWavSound=1 If a WavFilename_x parameter is left No sound is played when an alarm
blank corresponding to this alarm level is SET.
PlayWavSound=1 If a WavFilename_x parameter leads No sound is played when an alarm
to a non-existing file name corresponding to this alarm level is SET.
PlayWavSound=1 If a WavFilename_x parameter leads The windows error sound will be played.
to an existing but non-WAV file name
PlayWavSound=1 When an alarm sound is emitted The reset of the alarm doesn’t stop the
sound to be played
PlayWavSound=1 When an alarm sound is emitted, if The sound is no longer played.
the user press “Stop buzzer” If a new alarm occurs, the sound
corresponding to its level is played.
PlayWavSound=1 If Toggle Mute is enabled No sound is played. The sound being
played (if any) is muted locally to the HMI.

18.5.3.10 Blinking Management

User can set blinking attributes for the following HMI elements:
• Dynamic text,
• Dynamic picture,
• Analog measurement.
In HMI client, a graphical object has the following properties:
Properties Description
BlinkingOnAlarmed = 0 The graphical object will not blink if alarmed
The graphical object will blink when linked alarm is both Active AND
Unacknowledged
BlinkingOnAlarmed = 1 The graphical object will stop blinking when
• The alarm has been acknowledged (user clicked on the
link “click to acknowledge”)
• The alarm has reset (yes, even if NOT acknowledged)
BlinkingOnAlarmedBlinkRate Equals to 1000, rate of blinking set in milliseconds (range = <0..9999>)
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 149

18.6 IMPORT A DATAPOINT CONFIGURATION DATABASE

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Ensure that the graphical representations associated with the different states of datapoints:
◼ clearly indicate the state they intend to represent
◼ are clearly distinguishable from each other
◼ are clearly visible when displayed inside the graphical user interface.

Failure to follow these instructions can result in injury or equipment damage.

18.6.1 CLEAR FORMER DATABASES

Clear any database that might have been used by EcoSUI:

1. In the Start menu, click Schneider Electric > EcoSUI > EcoSUI SBUS Server.
2. Click the Data Acquisition tab.
3. Stop data acquisition by clicking on Stop.
4. Click the Other tab.
5. Click the Tools… button and select Database Clean-up.
6. From the list, select Clear All Rings And Objects. This process deletes any database template.

7. Answer the confirmation messages that shows up.

8. Once the database is cleared, click the Dashboard tab and close EcoSUI SBUS server.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 150

18.6.2 LOAD DATAPOINT CONFIGURATION FROM AN SCE DATABASE

In the following example, we assume that your electric database has been set up through EPAS SCE.
Before loading a SCE database to SBUS Server, make sure that the SCL.zip is in the generated zip file.

1. Copy the .Zip file generated by the SCE earlier in C:\MCIS\SCEConfiguration.

2. Get the configuration zip file. It is composed of 2 folders and 2 ini files.
3. Unzip it in C:\MCIS.

4. Connect to the EcoSUI SBUS Server.

5. Click the Data Acquisition tab.
6. Stop data acquisition by clicking on Stop.
7. Click the Tools… select Load Configuration from SCE Zip.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 151

8. In the explorer window, browse and select the configuration file to be imported:

9. Click Open. This will download the configuration into the database.
10. Once the new configuration is loaded, click the Dashboard tab and exit the SBUS Server.
11. Restart EcoSUI softwares.

Now the SBUS Server is configured together with Alarm, State & Event Viewer tabs.

18.6.3 LOAD DATAPOINT CONFIGURATION FROM A SIGNAL LIST FILE

Depending on your project’s need, you may want to load configuration from the Signal List file you have setup (IEC
61850, SNMP…). In this case, follow the procedure:

• From Data Acquisition tab, click the Tools button.

• Select Tools >Load Configuration from SignalList

Exit and restart SBUSServer.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 152

18.7 GENERATE A CONFPACKAGE

Generate a configuration package to be used in EcoSUI. This package will use the ini files that have been modified
(HMI views, LANs, gateways…).
This step is done from the EcoSUI Supervisor. EcoSUI Supervisor is installed and started automatically (after
installation and at windows startup) on each computer.

1. Double-click on the systray icon in your task bar to open EcoSUI Supervisor.

2. Log into the EcoSUI Supervisor.

Note: only the “Engineer” role has the rights to generate a configuration package. For more information
about the users and passwords management refer to the Cyber Security (CS) chapter of this EcoSUI
documentation.

3. Click the ConfPackage Generator tab.

4. Enter the configuration package name and its version.
5. Specify a different folder for storing Mimics, Rings, or Formulas in the Advanced option.
6. Click the Generate ConfPackage button and wait until the files are created.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 153

7. Close EcoSUI Supervisor.

EcoSUI Supervisor has created a configuration package in C:\MCIS\ConfPackages.
A folder and a zip file have been created with the name specified earlier.

This folder contains the following files:

• EXPORT: Folder with stored data in central DB (MySQL)
• GENERAL.INI: Global parameters
• SERVER.INI: Server configuration
• EcoSUIEQPT.INI: List of equipments used by supervision brick
• MIMICS.ZIP: Project’s mimics
• PACKAGE.INI: Identification of PC (OI& Server)
• RINGS.ZIP: Project’s LAN (or LANs for multi-ring project)
• GATEWAY.ZIP: Conversion table for transmitted datapoint in OPC network
• FORMULAS.ZIP: List of user-defined logics
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 154

18.8 DEPLOY ECOSUI CONFIGURATION

EcoSUI Supervisor allows the deployment of EcoSUI configuration package on HMIs over the network.

1. Double-click on the systray icon to open EcoSUI Supervisor.

2. Login to the EcoSUI Supervisor.

Note: only the “Engineer” role has the rights to deploy a configuration package. For more information
about the users and passwords management refer to the Cyber Security (CS) chapter of this EcoSUI
documentation.

3. Click on the ‘Configuration Deployment’ Tab. At first startup, there is no configuration package ready
to be uploaded to Central DB, SBUS Servers & EcoSUI HMI.

4. Click Import a new package and upload the configuration package.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 155

5. Once imported, select your database using the ‘Select a Configuration Package’ drop-down list. Wait
few seconds so that active equipments appear.

6. The EcoSUI equipment list is automatically filled in:

A summary of versions installed appear at the top of the window.

This ‘EcoSUI Equipment List’ is divided into 4 parts:

• The list of HMIs

• The list of SBUS Servers
• The list of Gateways
• The list of EcoSUI Supervisors

From there, see active softwares with their configuration version and software version:

• Software versions & configuration versions should be the same for any HMIs installed
• Software versions & configuration versions should be the same for any SBUS Servers installed
• Software versions & configuration versions should be the same for any Gateways installed
• Software versions should be the same for any Supervisors (The is no configuration for EcoSUI Supervisors).
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 156

Now that your configuration packages is loaded. Deploy the EcoSUI package by clicking on “Upload configuration
into selected components” :

After confirmation, all selectioned equipments will be loaded

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 157

19. CONFIGURE ECOSUI FROM A SET PROJECT

This chapter describes the steps to be performed to configure EcoSUI environment from a SET project.

19.1 REQUIREMENTS
Make sure EcoSUI is installed on your machine. If not, refer to the Installation chapter (IN).

For understanding the objects and the attributes of a referenced database it is recommended to be familiar with
SET.

Before configuring EcoSUI from a SET project, you should have a clear idea of the steps to be performed during
the migration.

The migration procedure is reserved for PCL Lattes System Engineers only. Please contact Schneider Electric
Support for a migration procedure.

19.2 OVERVIEW OF SET PROJECT FILES

If you have created a configuration using SET, the topologies (system, electrical) are automatically instantiated via
the following files:

SLD

Configuration of IEDs
Build Substation
description SYD SCD SFT850

Micom S1
Update System from IEDs

SSD
IID
IED Conf

SCD
ICD Define template / initial
configuration of IEDs
IID
Legend:

• SLD: Single Line Diagram

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 158

• SSD: System Specification Description. This file contains complete specification of a substation automation
system including single line diagram for the substation and its functionalities (logical nodes). This will have
Substation part, Data type templates and logical node type definitions but need not have IED section.

• SYD: System Design

• SCD: Substation Configuration Description. This file describes the complete substation. It contains
substation, communication, IED and Data type template sections. An .SSD file (System Specification
Description) and different .ICD files (IED Capability Description) contribute in making an SCD file. SCD file
will create a SYD project with substation, Voltage Levels, bays, primary equipments and system view
populated with the IEDs and SBUS.

• ICD: IED Capability Description (It defines complete capability of an IED. This file needs to be supplied by
each manufacturer to make the complete system configuration. The file contains a single IED section, an
optional communication section and an optional substation part which denotes the physical entities
corresponding to the IED)

• CID: Configured IED Description. It is a file used to have communication between an IED configuration tool
to an IED. It can be considered as an SCD file stripped down to what the concerned IED need to know and
contains a mandatory communication section of the addressed IED.

• IID: Instantiated IED Description (IEC 61850 ed2). It defines the configuration of one IED for a project and
is used as data exchange format from the IED configurator to the system configurator. This file contains
only the data for the IED being configured: one IED section, the communication section with the IED's
communication parameters, the IED's data type templates, and, optionally, a substation section with the
binding of functions (LNodes) to the single line diagram.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 159

19.3 EXPORT THE SCD FILE FROM SET

Given a SYD project whose electrical view is populated with Substation, SubNetworks and IEDs with data model:

• Click the Export SCL menu to export the current SYD project.

• Save the SCD file in a suitable location. The saved SCD file shall contain the available electrical parts and
Subnetworks with the IED elements and DataTypeTemplates.
• Saved file is then stored in the Project repository into [SCL Files] document with name as Exported SCD
file and with a tag and revision for each export.

19.4 SETUP ECOSUI

To upgrade a SET project to EcoSUI, three input files need to be imported:

• .SCD file from SET as explained earlier

• SignalList file (short & long name of devices) created with the Profile editor tool
• Profile.xml file (datapoints settings called by each device in the signalist) manually created with an XML
editor

Follow the procedure below to import the above mentioned files:

1. Save the .scd file generated by SET as sbuserver.scd in the C:\MCIS\Rings\<project_name> folder.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 160

19.5 SETUP SBUS SERVER DATA ACQUISITION

To implement IEC 61850 protocol edition 1 and edition 2 for data acquisition (LAN) in EcoSUI, from a SignalList
(SCD file generated from SET.

19.6 IMPORT & FIX SCD FILE

Now, import the SCD file. Detected SCD errors (generated by the SCE) will be fixed by this process.
1. To do so, from Data Acquisition tab, click the Tools button.
2. Select Advanced > Import & Fix SCD
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 161

19.7 DEPLOY
Now load datapoint configuration from SignalList to the CentralDB.

CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Ensure that the graphical representations associated with the different states of datapoints:
◼ clearly indicate the state they intend to represent
◼ are clearly distinguishable from each other
◼ are clearly visible when displayed inside the graphical user interface.

Failure to follow these instructions can result in injury or equipment damage.

1. From Data Acquisition tab, click the Tools button.

2. Select Tools >Load Configuration from SignalList

3. Exit and restart SBUS Server.

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 162

20. CONFIGURE ECOSUI WITH SEEFOX

20.1 INTRODUCTION
This section provides details on the “Migration Tool” allowing an automatic creation, from a Seefox (PCVue)
configuration, of the files required on an EcoSUI configuration. The automatic Migration Tool does not take into
account the “views”. Thus, Seefox’s views are out of the scope of this document.

Based on an existing Seefox (PCVue) configuration, the EcoSUI migration tool automatically creates the files
required on an EcoSUI configuration.

20.2 LIMITATIONS
The following files in the Seefox configuration are excluded from the migration process:

• Archive files management

• Network management
• Graphic
• Colorization variable

Only the following files within the Seefox configuration are taken into account:

• user.dat: User Right file.

• Var_syst.dat: Tag TLR used for variable profile.
• _varmg.dat: Communication and internal variables declaration.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 163

20.3 MIGRATION TOOL INSTALLATION GUIDE

20.3.1 COMPATIBILITY
The EcoSUI Migration Tool is compatible with Microsoft Windows® 10 Enterprise Build 1607 (OS Build
14393.1770) English version 64 bits.

20.3.2 INSTALLATION PROCEDURE

The EcoSUI Migration Tool is distributed as an executable file named “Migration Tool Setup
<Version>.<Number>.exe”

In order to install the EcoSUI Migration Tool, launch the executable file and follow the instructions:

• Click on the Next button to start the installation.

Figure 25: Installing the EcoSUI Migration Tool (1/7)

• Accept the software license agreement and click on the Next button.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 164

Figure 26: Installing the EcoSUI Migration Tool (2/7)

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 165

• Select the destination folder in your local drive and click on the Next button.

Figure 27: Installing the EcoSUI Migration Tool (3/7)

• Select the folder name to be added to the Windows Start Menu and click on the “Next” button.

Figure 28: Installing the EcoSUI Migration Tool (4/7)

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 166

• Choose if you want to add a desktop or a quick launch icon for the tool and click on the “Next” button.

Figure 29: Installing the EcoSUI Migration Tool (5/7)

• Click on the “Install” button to perform the installation.

Figure 30: Installing the EcoSUI Migration Tool (6/7)

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 167

• Check the Run Migration Tool.exd option for launching automatically the tool after quitting the setup
wizard and click on the Finishbutton.

Figure 31: Installing the EcoSUI Migration Tool (7/7)

20.4 MIGRATING SEEFOX CONFIGURATION

20.4.1 CONVERTING THE SEEFOX CONFIGURATION INTO ECOSUI

Launch the EcoSUI Migration Tool. If no icon is present in the desktop or in the quick-launch menu; run the
“Migration Tool.exe” file from the C:\<installationFolder>\Bin folder.

Figure 32: Main interface

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 168

Select the Source Project folder containing the Seefox configuration and the Output folder where the EcoSUI
configuration will be created, then click on the Start migration button.

The Source Project folder shall contain a “C” and “C1” folders where the files to be converted (user.dat,
Var_syst.dat and _varmg.dat) are usually stored. Otherwise, an information message will be displayed at the
bottom of the popup window:

Figure 33: Information message when the Source folder does not contain the C and C1 folders

The main interface allows the user to define a set of words from the source configuration to be ignored during the
migration process.

Figure 34: Ignoring words from source configuration

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 169

At the end of the migration process, the new EcoSUI configuration is created in the folder previously indicated in
the Migration Tool’s window.

Figure 35: Success migration message

The upgraded EcoSUI configuration is composed by:

• A “logs” folder containing the log message of the migration process

• A “Mimics” folder containing the “Users” data imported from the Seefox configuration
• A “NET_x” folder containing the EcoSUI data for a LAN: Formulas, Modbus configuration, Signal list and
Profiles

Figure 36: Upgraded EcoSUI configuration

APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 170

20.4.2 IMPORTING THE CONVERTED CONFIGURATION INTO ECOSUI

Once the Seefox files are converted into EcoSUI format, the user can integrate the new rings into an existing
EcoSUI configuration.

• First, copy the content of the “Mimics” folder into the destination EcoSUI folder; usually: “C:\MCiS\Mimics”.
• After that, copy the content of the “NET_x” folder into the EcoSUI ring folder, usually “C:\MCiS\Rings”
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 171

21. ADD SUPERVISION DATAPOINTS

To retrieve the link status between EcoSUI equipments (as defined in the C:/MCIS/MCISEqpt.ini file) and
EcoSUI components (CENTRALDB, HMI, SBUSSERVER, GATEWAY, PRINTER …), you will need to add
supervision datapoints to the Central DB.

To do so:

• Start the Sbus Server

• From the Other tab, click the Tools… button.
• Select Tools… > Reload MCIS Equipment List (MCISEqpt.ini)

Exit and restart SBUS Server (In the Dashboard tab, click Exit button).
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 172

22. ADD A LOAD SHEDDING GRID ARTIFACT

22.1 INTRODUCTION
This section describes how to configure a Grid artifact to be used in HMI. A grid can be used in order to show
load shedding parameters and modify them.

Thus, a Grid is an EcoSUI HMI object that allows the operator to see and modify values in a grid format.

For more details on the utilization of a Grid into the HMI interface, please refer to the chapter “EcoSUI HUMAN
MACHINE INTERFACE” (HI) of this User Manual.

22.2 GENERALITIES

22.2.1 GLOBAL FEATURES

Grid element Details Configured in
Row header Can be enabled or disabled Configuration file
Column header Can be enabled or disabled Configuration file
Position and size Relative to the mimic HMI
Number of rows - Configuration file
Number of columns - Configuration file
Background color - Configuration file
Foreground color - Configuration file
Font type - Configuration file
Load or save cell values Whether the cell will be saved into a setting file or not Configuration file
Table 26: Grid Elements

22.2.2 CELL FEATURES

Cells have the following properties:

Property Details
• Read-Only
Rights • Write-Only
• Read/Write
• A Text
Type
• A Button
textbox text or button text can be
• SPS, DPS, MPS signal status
Value • Datapoint Attribute
• MV signal value
• Result of a Formula
Cells can run standard HMI Action through buttons
• Open view
Active behavior
• Send Controls
• Send SetPoints
Table 27: Cells’ properties

22.3 GRID CONFIGURATION FILE

The grid is configured within a text configuration file composed of two sections: General and CellRXRY. The
following sections describe the characteristics of this configuration file.
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 173

22.3.1 NAMING THE CONFIGURATION FILE

There is no restriction to the name of this file. However, we recommend using the name Grid.ini.
This configuration file shall be placed into the folder containing the protocol to be defined; for example:
C:\MCIS\Rings\Modbus\

22.3.2 [GENERAL] SECTION

The General section describes the grid’s general parameters. It is composed by the following attributes

Attribute Description Format Example

NbOfRows Number of rows Integer 15
NbOfColumns Number of columns Integer 3
RowHeaderIsVisible 0 to hide row headers, 0 or 1 1
1 to show row headers
ColumnHeaderIsVisible 0 to hide column 0 or 1 0
headers,
1 to show column
headers
DefaultFont Font used on the grid Font name, size and attribute Arial ;10 ;B
separated by semi-colons.
Attribute:
(B = Bold ; I = Italic ; U = Underlined)
DefaultForeColor Text color RGB separated by semi-colons 0;128;0
DefaultBackColor Background color RGB separated by semi-colons 255;255;255
Table 28: Grid’s properties

This is an example of the General section:

[General]
NbOfRows=15
NbOfColumns=4
RowHeaderIsVisible=1
ColumnHeaderIsVisible=0
DefaultFont=Arial;10;B
DefaultForeColor=0;128;0
DefaultBackColor=255;255;255
Example 25: General section
APPLICATION NOTE EcoSUI Configuration/EN AN/I
EcoSUI Page 174

22.3.3 [CELLCXRY] SECTION

The CELLCXCY section contains the attributes describing a Cell.

• X represents the column number

• Y represents the row number.

Attribute Description Format Example

RWType Rights R: Read-Only RW
W: Write-Only
RW: Read/Write
Type Cell type Text Text
Button
Empty
A Signal status or [SS / VL / BAY / ..]
value
Value Cell value
A Formula Evaluate()
A Signal Attribute Attribute(AttributeIdx;[SS /
VL / BAY / …])
Action The action triggered Text
SHOWMIMIC 3
when clicking on the
MyView.cfg
button
SaveLoadInSettingFile Whether the cell will 0: Not saved 1
be saved into a setting 1: Saved
file or not
Table 29: Attributes composing the CELLRXRY section

This is an example of the General section:

[CellC2R13]
RWType=R
Type=Button
Value=Open View
Action=SHOWMIMIC 3 MyView.cfg
SaveLoadInSettingFile=0
[CellC1R13]
RWType=RW
Type=Text
Value=[MySubstation / 110 Kv / E10 / Reactive Power]
Action=
SaveLoadInSettingFile=1
Example 26: CELLRXRY section