EcoSUI

Engineering Guide
Application Note

ECOSUIENG/EN AN/E

Application Note
For EcoSUI Configuration
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 3/142

ENGINEERING GUIDE: ECOSUIENG/EN

AN/E
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 4/142
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 5/142

CONTENT

ENGINEERING GUIDE: EcoSUIENG/EN AN/E .................................................... 3

1 Scope of the Document ............................................................................ 9

1.1 Requirements ......................................................................................................................... 9

2 Safety and Handling ............................................................................... 10

2.1 Symbols and Messages ....................................................................................................... 10
2.1.1 Health and Safety ..................................................................................................................................... 10
2.1.2 Explanation of symbols and labels ........................................................................................................... 10
2.1.3 Important notes ......................................................................................................................................... 12

3 Required Data Acquisition Files .............................................................. 13

3.1 The Database configuration file .......................................................................................... 13
3.2 The Signal List ...................................................................................................................... 14
3.3 The Ring.ini File .................................................................................................................... 14
3.4 The Profile.xml File............................................................................................................... 14
3.5 The Graphical Configuration ............................................................................................... 14

4 The Signal List ........................................................................................ 15

4.1 Overview ............................................................................................................................... 15
4.2 Signal Attributes ................................................................................................................... 16
4.3 Specify / Change the separator ........................................................................................... 16
4.4 Add Communication Link Datapoint ................................................................................... 16
4.5 Example of Data Points ........................................................................................................ 17
4.5.1 SPS ........................................................................................................................................................... 17
4.5.2 DPS ........................................................................................................................................................... 17
4.5.3 MPS .......................................................................................................................................................... 17
4.5.4 DPC .......................................................................................................................................................... 18
4.5.5 MV ............................................................................................................................................................. 18
4.5.6 STR ........................................................................................................................................................... 18

5 The Ring.ini File ...................................................................................... 19

5.1 Overview ............................................................................................................................... 19
5.2 Possible Parameters ............................................................................................................ 20
5.2.1 [Ring] ......................................................................................................................................................... 20
5.2.2 [SBUSAccess]........................................................................................................................................... 23
5.2.3 [RedundantC264] ...................................................................................................................................... 23
5.2.4 [LogbookPrinterManager] ......................................................................................................................... 23
5.2.5 [IEC61850] ................................................................................................................................................ 24
5.2.6 [LogicalRing] ............................................................................................................................................. 24
5.2.7 [HotHotRedundant] ................................................................................................................................... 24
5.2.8 [OPC] ........................................................................................................................................................ 24
5.2.9 [External DLL] ........................................................................................................................................... 25

6 The Profile.xml File ................................................................................. 26

6.1 Overview ............................................................................................................................... 26
6.2 Data structure ....................................................................................................................... 26
6.2.1 SPS ........................................................................................................................................................... 27
6.2.2 DPS ........................................................................................................................................................... 29
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 6/142

6.2.3 MPS .......................................................................................................................................................... 31

6.2.4 SPC ........................................................................................................................................................... 33
6.2.5 DPC .......................................................................................................................................................... 35
6.2.6 MV ............................................................................................................................................................. 36
6.2.7 STR ........................................................................................................................................................... 45
6.3 Example of Profiles.xml File ................................................................................................ 46

7 The Servers.ini File ................................................................................. 49

7.1 Overview ............................................................................................................................... 49
7.2 Main content ......................................................................................................................... 49
7.3 Measurement archiving........................................................................................................ 49
7.3.1 [MVArchiving] section ............................................................................................................................... 49
7.3.2 [MVRingsArchiving] section ...................................................................................................................... 49

8 IEC 61850 LAN ....................................................................................... 50

8.1 From PACiS SCE zip File ..................................................................................................... 50
8.1.1 Create a ring folder ................................................................................................................................... 50
8.1.2 Edit the ring.ini file .................................................................................................................................... 50
8.1.3 Load the SCE database ............................................................................................................................ 51
8.2 From a Signal List ................................................................................................................ 53
8.2.1 Create a ring folder ................................................................................................................................... 53
8.2.2 Edit the ring.ini file .................................................................................................................................... 53
8.2.3 Create the Profiles.xml File ....................................................................................................................... 53
8.2.4 Create the Signal list with Profile ET Tool ................................................................................................ 54
8.2.5 Import & fix SCD file ................................................................................................................................. 55
8.2.6 Deploy ....................................................................................................................................................... 55

9 Modbus LAN ........................................................................................... 56

9.1 Generalities ........................................................................................................................... 56
9.2 L_Modbus_XML_0.xml Data Structure ................................................................................ 56
9.3 Main Node <MAIN> ............................................................................................................... 58
9.4 Equipment Node <EQT>....................................................................................................... 58
9.4.1 Redundancy Node .................................................................................................................................... 60
9.4.2 Mailbox Node ............................................................................................................................................ 62
9.4.3 Frame Node .............................................................................................................................................. 64
9.5 Modbus addressing format .................................................................................................. 70
9.6 Modbus Hot-Hot Redundancy ............................................................................................. 71
9.6.1 Limitations ................................................................................................................................................. 71
9.6.2 Ring.ini configuration ................................................................................................................................ 71
9.6.3 Additional datapoints for Hot-Hot Redundancy ........................................................................................ 71
9.7 Selecting the Active IED....................................................................................................... 72
9.8 Supported Modbus Function codes .................................................................................... 73
9.9 Define a MODBUS LAN ........................................................................................................ 74
9.9.1 Create a ring folder ................................................................................................................................... 74
9.9.2 Edit the ring.ini file .................................................................................................................................... 74
9.9.3 L_Modbus.dll............................................................................................................................................. 74
9.9.4 L_Modbus_XML_0.xml ............................................................................................................................. 74
9.9.5 Create the Profiles.xml File ....................................................................................................................... 74
9.10 Create and prepare the Signal list ....................................................................................... 75
9.11 Import & fix SCD file ............................................................................................................. 75
9.12 Deploy ................................................................................................................................... 75

10 SNMP LAN ............................................................................................. 76

10.1 Create a ring folder............................................................................................................... 76
10.2 Edit the ring.ini file ............................................................................................................... 76
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 7/142

10.2.1 Edit the Host file ........................................................................................................................................ 77

10.2.2 Prepare the Signal list according to MIB addressing ................................................................................ 77
10.2.3 How to find MIB addressing ...................................................................................................................... 78
10.3 Prepare Profiles.xml file ....................................................................................................... 79
10.4 Deploy ................................................................................................................................... 81

11 OPC LAN ................................................................................................ 82

11.1 Create a ring folder............................................................................................................... 82
11.2 Edit the ring.ini file ............................................................................................................... 82
11.3 Create the Profiles.xml File .................................................................................................. 83
11.4 Create and prepare the Signal list ....................................................................................... 84
11.5 Import & fix SCD file ............................................................................................................. 85
11.6 Deploy ................................................................................................................................... 86

12 Virtual LAN ............................................................................................. 87

12.1 Principles .............................................................................................................................. 87
12.2 Create a ring folder............................................................................................................... 87
12.3 Edit the ring.ini file ............................................................................................................... 87
12.4 Create the Profiles.xml File .................................................................................................. 88
12.5 Define Formulas ................................................................................................................... 89
12.5.1 From Sbus SERVER ................................................................................................................................ 89
12.5.2 From EcoSUI Mimics ................................................................................................................................ 98
12.5.3 Output Files............................................................................................................................................. 101
12.6 Prepare the Signal list ........................................................................................................ 102
12.7 Deploy ................................................................................................................................. 103

13 Upgrade an SCE Project to EcoSUI...................................................... 104

13.1 Requirements ..................................................................................................................... 104
13.2 Overview of SCE Project Files ........................................................................................... 104
13.3 Setup EcoSUI ...................................................................................................................... 105
13.3.1 Declare OI & Servers .............................................................................................................................. 105
13.3.2 Specify the Server IP Addresses ............................................................................................................ 106
13.3.3 Configure your equipments..................................................................................................................... 107
13.4 Setup Sbus Server Data Acquisition ................................................................................. 108
13.5 Import SCE Mimics files ..................................................................................................... 109
13.5.1 Extract the Image folder .......................................................................................................................... 110
13.5.2 Run the Migration Process ..................................................................................................................... 111
13.5.3 Final Adjustments in EcoSUI .................................................................................................................. 113
13.6 Import a Datapoint Configuration Database ..................................................................... 116
13.6.1 Clear former databases .......................................................................................................................... 116
13.6.2 Load Datapoint Configuration From an SCE Database ......................................................................... 117
13.6.3 Load Datapoint Configuration From a Signal List File ............................................................................ 118
13.7 Generate a ConfPackage ................................................................................................... 119
13.8 Deploy EcoSUI Configuration ............................................................................................ 121

14 Configure EcoSUI from a SET Project .................................................. 124

14.1 Requirements ..................................................................................................................... 124
14.2 Overview of SET Project Files ........................................................................................... 124
14.3 Export the SCD file from SET ............................................................................................ 126
14.4 Setup EcoSUI ...................................................................................................................... 126
14.5 Setup SBUS Server Data Acquisition................................................................................ 127
14.6 Import & fix SCD file ........................................................................................................... 127
14.7 Deploy ................................................................................................................................. 128
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 8/142

15 Configure EcoSUI with SEEFOX .......................................................... 129

15.1 Introduction ........................................................................................................................ 129
15.2 Limitations .......................................................................................................................... 129
15.3 Migration Tool Installation guide ....................................................................................... 130
15.3.1 Compatibility ........................................................................................................................................... 130
15.3.2 Installation Procedure ............................................................................................................................. 130
15.4 Migrating Seefox configuration ......................................................................................... 133
15.4.1 Converting the Seefox configuration into EcoSUI .................................................................................. 133
15.4.2 Importing the converted configuration into EcoSUI ................................................................................ 136

16 Add Supervision Datapoints.................................................................. 137

17 Add a Load Shedding Grid Artifact........................................................ 138

17.1 Introduction ........................................................................................................................ 138
17.2 Generalities ......................................................................................................................... 138
17.2.1 Global features........................................................................................................................................ 138
17.2.2 Cell Features........................................................................................................................................... 138
17.3 Grid configuration file ........................................................................................................ 139
17.3.1 Naming the configuration file .................................................................................................................. 139
17.3.2 [General] Section .................................................................................................................................... 139
17.3.3 [CellCXRY] Section ................................................................................................................................. 140
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 9/142

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.

1.1 REQUIREMENTS
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 SET or PACiS 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 10/142

2 SAFETY AND HANDLING

This document is a chapter of the EcoSUI manual. It describes the safety procedure applicable to EcoSUI software
tools.

2.1 SYMBOLS AND MESSAGES

Read these instructions carefully and look at the equipment to become familiar with the device before trying to install,
operate, service or maintain it. The following special messages may appear throughout this bulletin or on the
equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a
procedure.

2.1.1 HEALTH AND SAFETY

The data in the Safety Section of the product documentation ensures that products are properly installed and safely
operated to maintain them in a serviceable condition. Everyone who operates the equipment must be familiar with the
contents of the Safety Section and all Safety documents related to the PC and Communication networks.

2.1.2 EXPLANATION OF SYMBOLS AND LABELS

The explanation of symbols and labels, installed on the equipment or used in the product documentation, is given
below.

2.1.2.1 Risk of Electric Shock

The addition of either symbol to a Danger or Warning safety label indicates that an
electrical hazard exists, which will result in personal injury if the instructions are not
followed.

2.1.2.2 Safety Alert

This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all
safety messages that follow this symbol to avoid possible injury or death.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 11/142

2.1.2.3 Safety Messages

PLEASE NOTE

Electrical equipment should be installed, operated, serviced, and maintained only by qualified
personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of
the use of this material.

A qualified person is one who has skills and knowledge related to the construction, installation, and
operation of electrical equipment and has received safety training to recognize and avoid the
hazards involved.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 12/142

2.1.3 IMPORTANT NOTES

2.1.3.1 Restricted liability

Electrical equipment should be serviced and maintained only by qualified personnel.
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this manual. This
document is not intended as an instruction manual for untrained persons.

2.1.3.2 Device operation

The user is responsible for checking that the rated characteristics of the device are suitable for its application. The
user is responsible for reading and following the device‟s operating and installation instructions before attempting to
commission or maintain it. Failure to follow these instructions can affect device operation and constitute a hazard for
people and property.

2.1.3.3 Protective grounding

The user is responsible for compliance with all the existing international and national electrical codes concerning
protective grounding of any device.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 13/142

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.

This SCD file is used by the IEC61850 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 14/142

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 PACiS 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 PACiS 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).
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 RING.INI FILE

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

3.4 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.5 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.
 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 PACiS SCE or using SET (.scd
file, signalList & profiles) and then, imported directly to EcoSUI.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 15/142

4 THE SIGNAL LIST

4.1 OVERVIEW
The SignalList file is a comma-separated value (CSV) text files (.csv).

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
st
Top Columns 1 (1 field) {Sitename, SubstationName}: the two first lines MUST start with those barewords.
nd
Top Columns 2 (2 field) Site name and substation name for tree view
#Type Data point type :
SPS, DPS, MPS, MV, SPC, DPC, STR
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 (IEC61850, 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

Note: any line starting with a hash (#) is ignored. They can be used to comment out a line.
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 ET Tool and
import it to EcoSUI. Note: Profile ET is an optional tool. For further information, please contact your support team.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 16/142

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.

rd
Open the .signallist and enter EQUIPMENTCOMMUNICATION, in the 3 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.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 17/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 18/142

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
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 19/142

5 THE RING.INI FILE

5.1 OVERVIEW
The Ring.ini file contains important SbusServer LAN properties.

This is where the user specifies the type of protocol and specific settings for deploying his project in EcoSUI.

It may be necessary to edit this file and setup the parameters based on the protocol in use.

Parameters in the ring.ini file are gathers into dedicated section:

 [Ring]
 [SBUSAccess]
 [RedundantC264]
 [LogbookPrinterManager]
 [IEC61850]
 [LogicalRing]
 [HotHotRedundant]
 [OPC]
 [EXTERNAL DLL]

Please find below further information about these parameters.

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 20/142

5.2 POSSIBLE PARAMETERS

5.2.1 [RING]

Parameter Name Description Expected Values

Type EFIP, IEC61850, PERFMON, OPC,
Type of the protocol used by the EcoSui OW, RFXCOM, ZWAVE, MODBUS,
LAN. EXTERNALDLL or VIRTUAL (NO
ACQUISITION)
Enabled List of all Sbus Server names (separated with ;) where this LAN is enabled.
Example: OIS_M;OIS_B

The first one is considered as the main SBUS Server.

The second one is considered as the backup SBUS Server.

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

AutoDisturbanceDownload Automatic disturbance download.  1 to enable automatic

EcoSUI uses the Disturbances folder file download
to retrieve the path in the IED where  0 to disable automatic
disturbance data is stored. download
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 List of equipments separated by a ';'
from SCE.
When loading the S2kloader.xml file, all Ex : OI_Backup;External_clock_1
signals from the specified list of
equipments will be ignored. For instance,
all signals from the OI Server are useless
as it does not exist anymore in the SCE.
Reload the configuration after each
modification.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 21/142

SiteSCSID This parameter is only used during

1: keeps SCE-generated ID
import from SCE.
It allows the use of the SCS and Site
Any number > 1 to replace the ID
ID generated by SCE or change these
with this number
IDs.
SubstID This parameter is only used during 1: keeps substation ID from SCE
import from SCE.
It allows the use of the substation ID Any number > 1 to replace the ID
generated by SCE or use the any one with this number.
ExcludedPath This parameter is only used during List of path separated by a ';'
import from SCE. Ex: site-1.subst-3;site-2.subst-4
When loading the S2kloader.xml, all
signals from the specified path will be
ignored.
Reload the configuration after each
modification.
HasSecondaryLanguage  0: to disable secondary
Obsolete parameter
language,
Enables / Disables secondary
 1: to enable secondary
language
language
MainOIServerName Network Name of the Main OI Server
(Used to read the generated .ZIP file,
find the OI server and extract
s2kloader.xml inside)

BackupOIServerName Network Name of the Backup OI

Server (Used to read the generated
.ZIP file, find the OI Server and extract
s2kloader.xml inside)

AutomaticGI_EqptTypeList To avoid unexpected behaviors on P40 List of equipments where this

series about device status. automatic GI option is enabled.
This parameter requests a GI (general
interrogation) when a JAMMED Separate each type with a ';'
position is received.
Ex P142;P143
AutomaticGI_WaitTime When a JAMMED position is received, In milliseconds
EcoSUI waits for x milliseconds before
sending a General interrogation to the
IED in order to get the latest correct
status.
DefaultIntegrityPeriodForMXInMs Forces the IEC Equipment to send MX In milliseconds
values every X milliseconds even if
their state didn't change
DefaultIntegrityPeriodForSTInMs Forces the IEC Equipment to send ST In milliseconds
values every X milliseconds even if
their state didn't change
SCDVersion=? Read only
DBVersion=? Read only
IEC61850_AcqVersion Version of IEC61850 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 contains some non- valid Lists the IEC/IEC gateways
data about IEC/IEC gateways. separated by a ';'
During import from SCE, EcoSUI
updates the file by adding the Ex: GTW_IEC;GTW_BCK
necessary signals
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 22/142

Scada_GatewayNames This parameter is used to adjust SCD

file which contains some non- valid
data about IEC/IEC gateways. Lists the scada gateways separated
During import from SCE, EcoSUI by a ';'
updates the file by adding the
necessary signals
Helps to prevent confusion between 1: when managing multiple LANs
AddRingNameToIECAddress IED Addresses when managing the 0: when managing 1 LAN (default
same IED names over different LANs. value)
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  2: by default
 1: helps to ensure retrofit
Version of .SignalList file
compatibility on former
projects
EthernetNetID 1: keeps SCE-generated ID
Keeps the EthernetNetwork ID
generated by SCE. Any number > 1 to replace the ID by
this number
VoltLevelID 1 keeps SCE-generated ID
Keeps the Subst ID generated by SCE.
Any number > 1 to replace the ID by
this number
UseReportCapabilities Use report capabilities instead of using
0 : Standard parameters (default
standard parameters
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 23/142

5.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.

5.2.3 [REDUNDANTC264]

Parameter Name Description Example

MainC264 Specify each main redundant C264 MainC264=RedundantC264

5.2.4 [LOGBOOKPRINTERMANAGER]

Parameter Name Description Expected Values

MainIPAddress Each SBUS Server can manage one Logbook Empty if logs are not send to a
Printer. printer manager

In that case, it becomes a „Logbook Printer Manager‟.

It receives events to print from a TCP connection.

This parameter specifies the IP Address of the Main

SBUS Server LogbookPrinterManager.
BackupIPAddress IP Address of the Backup SBUS Server Empty if logs are not send to a
LogbookPrinterManager. printer manager
FilterGI Do not send to log book General Interrogations 1 to filter (default value)
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 24/142

5.2.5 [IEC61850]

Parameter Name Description Expected Values

TapchangerLowerCommand For tapchanger lower command, specify the Default is 'off;Dbpos'
IEC61850 CtlVal parameter.

5.2.6 [LOGICALRING]

Parameter Name Description Expected Values

IsLogicalRing_Help 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

5.2.7 [HOTHOTREDUNDANT]

Parameter Name Description Expected Values

NameOfIEDMain NameOfIEDBackup. The name of the IED used as
backup in a Hot/Hot redundancy
configuration

5.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
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 25/142

5.2.9 [EXTERNAL DLL]

Parameter Name Description Expected Values

ProtNb When more than one modbus LANs is Integer identifying the
defined in the same computer, a different protocol number
Protocol Number shall be assigned to every
LAN.

This protocol number will be used for naming

the XML file describing the modbus protocol;
for example:

 L_modbus_xml_[protnb].xml

Where [protnb] is the protocol number

defined in [ExternalDLL]/ProtNb

BackupServerURL URL of the backup OPC Server

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 26/142

6 THE PROFILE.XML FILE

6.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.

6.2 DATA STRUCTURE

The Profiles.XML file is composed by a root node “Profiles” with no attributes.

The “Profiles” node is composed by six mandatory nodes representing the datapoint types:

 SPS
 DPS
 MV
 SPC
 DPC
 MPS
 STR

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>
</Profiles>
Example 1: Text view of the Main structure of the Profiles.XML file
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 27/142

6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 28/142

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 0
alarmaudible Yes / No
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"/>
<STATE1 label="SET" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
</SPS_ALARM-SET>
</SPS>
Example 2: SPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 29/142

6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 30/142

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 0
alarmaudible Yes / No
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"/>
<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>
Example 3: DPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 31/142

6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 32/142

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 0
alarmaudible Yes / No
Table 3: MPS’s mandatory attributes

<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"/>
<STATE3 label="STATE 3" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE4 label="STATE 4" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE5 label="STATE 5" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE6 label="STATE 6" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE7 label="STATE 7" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE8 label="STATE 8" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE9 label="STATE 9" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE10 label="STATE 10" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE11 label="STATE 11" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE12 label="STATE 12" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE13 label="STATE 13" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE14 label="STATE 14" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
<STATE15 label="STATE 15" archived="yes" printed="yes" alarmlevel="0"
alarmdelay="0" alarmaudible="no"/>
</MPS_RGD_ALARM>
</MPS>
Example 4: MPS profile with its nodes and their attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 33/142

6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 34/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 35/142

6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 36/142

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

Figure 12: 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 13: Nodes composing the MV profile

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 37/142

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 6: 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 38/142

6.2.6.1 THRESHOLD Management

6.2.6.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 IEC61850 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 39/142

6.2.6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 41/142

6.2.6.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 7: DPC profile with its nodes and their attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 42/142

See the picture below:

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 43/142

6.2.6.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 44/142

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 8: MV profile with attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 45/142

6.2.7 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 14: 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 9: STR profile with its nodes and their attributes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 46/142

6.3 EXAMPLE OF PROFILES.XML FILE

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

Figure 15: Example of a simple Profiles file

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 47/142

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"/>
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 48/142

<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 10: Simple example of a profiles.xml file
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 49/142

7 THE SERVERS.INI FILE

7.1 OVERVIEW
This section describes the Servers.ini configuration file.

7.2 MAIN CONTENT

The Servers.ini file is composed of the following sections

Section name Details

SBUSServer Configuration of the SBus server
CentralDB Configuration of the central database
CAEDatabases Configuration of the CAE database
LogbookPrinter Configuration of the printer
TelnetServer Configuration of the telnet server
SBUSServers List of SBus servers
MVArchiving Locally archived or not
MVRingsArchiving Locally save measurements or not

Table 7: Sections composing the Servers.ini file

7.3 MEASUREMENT ARCHIVING

The client has to pay attention to the configuration to be able to retrieve the measurements on the correct DB. It
has to be transparent for the user whether the measurements are archived locally or centrally.

7.3.1 [MVARCHIVING] SECTION

The MVArchiving section allows us to select whether the measurements will be saved into the local or the central
database.

Attribute Description Format Example

ArchiveLocaly Whether the 0: Central database 1
measurements will be 1: Local database
saved into the local or the
central database
Table 8: Attributes of the MVArchiving section

7.3.2 [MVRINGSARCHIVING] SECTION

As the measurements can be stored locally on every redundant server (main and backup), the full list of servers
has to be known by each other so they can retrieve the values of the measurements.

The MVRingsArchiving section gives the list of servers in the following format

<index>; <IP of Main server>; <IP of backup server>

[MVRingsArchiving]
0;192.168.1.1;192.168.1.2
Example 11: List of servers archiving locally
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 50/142

8 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 PACiS SCE

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

8.1 FROM PACIS SCE ZIP FILE

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

8.1.1 CREATE A RING FOLDER

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

8.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 51/142

8.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 52/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 53/142

8.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:

8.2.1 CREATE A RING FOLDER

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

8.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.

8.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>,
 <MV>

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

Profile properties are similar to the ones in PACiS SCE.

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 54/142

8.2.4 CREATE THE SIGNAL LIST WITH PROFILE ET TOOL

The .SignalList file gathers the list of data points managed by the IEC61850 LAN.

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

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

To do so start Profile ET and then:

 In the File menu, click Import SCD and locate the .SCD file generated by SET. From this file, Profile ET
will then do automatic data point detection.
 To assign specific profiles to these data points, in the File menu, click Import Profile and select the
profile.xml file previously defined:

 Once mapped, click Export EcoSUI in the File menu to generate the .SignalList file (.csv extension)
that will be used in EcoSUI.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 55/142

8.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

8.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 56/142

9 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.

9.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 9: 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.

9.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 16: ModbusMaster node with Main description and 8 associated equipments
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 57/142

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 12: Text view of the Main structure of the Modbus.XML file
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 58/142

9.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 10: Main node’s attributes

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

9.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 17: Attributes and nodes composing the EQT node

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 59/142

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 11: 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 14: Attributes and nodes composing the EQT node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 60/142

9.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 18: Attributes composing the REDUNDANCY node

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 61/142

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 12: 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 15: Attributes composing the REDUNDANCY node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 62/142

9.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 19: 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 13: Attributes composing the MAILBOX node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 63/142

<?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 16: Attributes composing the MAILBOX node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 64/142

9.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 20: Attributes and nodes composing the FRAME node

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 65/142

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 – Command
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 14: Attributes and nodes composing the FRAME node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 66/142

<?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 17: Attributes composing the FRAME node

9.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 15: 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 18: Attributes composing the TS node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 67/142

9.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 16: Attributes composing the TM node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 68/142

<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 19: Attributes composing the TM node

9.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 17: 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 20: Attributes composing the Co node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 69/142

9.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 command.
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 18: 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 21: Attributes composing the Co node
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 70/142

9.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 19: 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 22: Signal list addressing for a Modbus LAN within the Signal List
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 71/142

9.6 MODBUS HOT-HOT REDUNDANCY

9.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.

9.6.2 RING.INI CONFIGURATION

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

[HotHotRedundant]
NameOfIEDMain=NameOfIEDBackup

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

9.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
Command to manually select the active SPC
1 = Set Main IED as Active
IED
Table 20: Datapoints needed for Modbus Hot-Hot redundancy
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 72/142

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

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

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

9.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 21: Manually selecting the Active IED
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 73/142

9.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 Not Supported (Done with Function Code 16)
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 Commands)
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 22: Function codes
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 74/142

9.9 DEFINE A MODBUS LAN

To implement a MODBUS LAN, follow the procedure:

9.9.1 CREATE A RING FOLDER

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

9.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 SbusServer 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.

9.9.3 L_MODBUS.DLL
In the LAN, the L_Modbus.dll shall be present (stored in the C:\MCIS\Bin folder).

9.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.

9.9.5 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 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 75/142

9.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.

9.11 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

9.12 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 76/142

10 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:

10.1 CREATE A RING FOLDER

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

10.2 EDIT THE RING.INI FILE

The type of protocol can be defined in the ring.ini file of EcoSUI. This file contains important LAN properties.
 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 about ring.ini file to get additional information on the possible parameters.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 77/142

10.2.1 EDIT THE HOST FILE

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

10.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 about the SignalList file for further information on the contents of a SignalList.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 78/142

10.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

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 79/142

10.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 80/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 81/142

10.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 82/142

11 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:

11.1 CREATE A RING FOLDER

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

11.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 83/142

11.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 PACiS SCE.

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 84/142

11.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 85/142

11.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 86/142

11.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 87/142

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

12.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:

12.2 CREATE A RING FOLDER

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

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 88/142

12.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 PACiS SCE.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 89/142

12.5 DEFINE FORMULAS

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

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 90/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 91/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 92/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 93/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 94/142

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 95/142

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 96/142

 Returns 0 ACT / ACK

 Returns 1 ACT / NACK
 Returns 2 NACT / ACK
 Returns 3 NACT / NACK
 Returns 4 NOT PRESENT
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 97/142

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 98/142

12.5.2 FROM ECOSUI MIMICS

It is possible to add formulas to objects of in HMI views. To do so, EcoSUI HMI must 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
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 99/142

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

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

4. Repeat the same methodology as described in the previous section.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 100/142

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 101/142

12.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 102/142

12.6 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.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 103/142

12.7 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 104/142

13 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.

13.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.

13.2 OVERVIEW OF SCE PROJECT FILES

When creating a new configuration using PACiS 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 105/142

13.3 SETUP ECOSUI

13.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 PACiS 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 106/142

13.3.2 SPECIFY THE SERVER IP ADDRESSES

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

1. Go to C:\MCIS
2. Open the file SERVER.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.

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 107/142

13.3.3 CONFIGURE YOUR EQUIPMENTS

Modify the MCISEqpt.ini file in order to specify the device characteristics.

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 108/142

13.4 SETUP SBUS SERVER DATA ACQUISITION

EcoSUI supports the following protocols for Data Acquisition (LAN):
 IEC61850 edition 1 and edition 2
o From PACiS 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 109/142

13.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 PACiS 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 PACis 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 110/142

13.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 111/142

13.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.
Then, copy the entire content of the desired workspace folder in the MCIS\Mimics folder.
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 112/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 113/142

13.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:

13.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.

13.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

13.5.3.3 EcoSUI Users & Profiles

C:\MCIS\Mimics\Users:
To use exported PACIS User Profiles:
 Delete the PacisProfiles.ini file and PacisUsers.ini (filenames without underscore)
 Rename the PacisProfiles_.ini to PacisProfiles.ini
 Rename the PacisUsers_.ini to PacisUsers.ini
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 114/142

13.5.3.4 Launch Popup command

It is recommended to manually configure user profiles in EcoSUI to make it possible to launch the command
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

13.5.3.5 Auto Log-off

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

 Open the General.ini file in the Mimics folder and set the value needed for your project:
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 115/142

13.5.3.6 Alarm Color Management

Configure manually Alarm colors which are not upgraded by default:
 Double-click the Alarm object in your mimic view
 Expand the object property tree-view on the left and go to the AlarmControl node
 Set the desired values for the alarm color parameters on the right:
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 116/142

13.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.

13.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 117/142

13.6.2 LOAD DATAPOINT CONFIGURATION FROM AN SCE DATABASE

In the following example, we assume that your electric database has been set up through PACIS 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 118/142

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.

13.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 119/142

13.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.

7. Close EcoSUI Supervisor.

APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 120/142

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 121/142

13.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 122/142

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

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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 123/142

Now that your configuration packages is loaded. Deploy the EcoSUI package by running steps 1, 2, 3 and 4 by at
the bottom of the window :

At least, CentralDB0 (Main MySQL) should be running before starting to upload the configuration

Step 1 of the configuration deployment:

The configuration is uploaded to CentralDBs : Wait the completion of this step.

A message box will appear to show the result of this upload
Step 2 of the configuration deployment:

The configuration is uploaded to SBUS Servers.

Wait until SBUS Servers are restarted and wait one more minute.
Step 3 of the configuration deployment:

The configuration is uploaded to HMI. Please make sure to press this button
only when configuration is deployed in SBUS Servers !

Wait until HMIs are restarted

Step 4 of the configuration deployment:

The configuration is uploaded to Gateways.

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 124/142

14 CONFIGURE ECOSUI FROM A SET PROJECT

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

14.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.

14.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
SFT850
Build Substation
description SYD SCD

Micom S1
Update System from IEDs
IID
SSD IED Conf
SCD
ICD Define template / initial
configuration of IEDs
IID

Legend:

 SLD: Single Line Diagram

 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

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 125/142

 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 EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 126/142

14.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.

14.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 EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 127/142

14.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.

14.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 EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 128/142

14.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 EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 129/142

15 CONFIGURE ECOSUI WITH SEEFOX

15.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.

15.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 EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 130/142

15.3 MIGRATION TOOL INSTALLATION GUIDE

15.3.1 COMPATIBILITY
The EcoSUI Migration Tool is compatible with Microsoft Windows 7 32 and 64 bits.

15.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 23: Installing the EcoSUI Migration Tool (1/7)

 Accept the software license agreement and click on the Next button.

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

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 131/142

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

Figure 25: 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 26: Installing the EcoSUI Migration Tool (4/7)

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 132/142

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

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

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

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

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 133/142

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

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

15.4 MIGRATING SEEFOX CONFIGURATION

15.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 30: Main interface

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.
APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 134/142

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 31: 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 32: Ignoring words from source configuration

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 135/142

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 33: 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 34: Upgraded EcoSUI configuration

APPLICATION NOTE EcoSUIENG/EN AN/D30
EcoSUI Documentation Page 136/142

15.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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 137/142

16 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 EcoSUIENG/EN AN/E
EcoSUI Documentation Page 138/142

17 ADD A LOAD SHEDDING GRID ARTIFACT

17.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.

17.2 GENERALITIES

17.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 23: Grid Elements

17.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 Commands
 Send SetPoints
Table 24: Cells’ properties
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 139/142

17.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.

17.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\

17.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 25: 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 24: General section
APPLICATION NOTE EcoSUIENG/EN AN/E
EcoSUI Documentation Page 140/142

17.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 26: 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 25: CELLRXRY section
 Customer Care Centre
http://www.schneider-electric.com/CCC

 2014 Schneider Electric. All rights reserved.

Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone: +33 (0) 1 41 29 70 00
Fax: +33 (0) 1 41 29 71 00
www.schneider-electric.com Publishing: Schneider Electric
Publication: ECOSUIENG/EN AN/E 12/2014