Saitel DR

DIN Rail RTU

User Manual
This manual provides general information about Saitel DR Platform, including
installation, wiring and other useful data for installers and designers.

SE-F800-USR

Publication Date (11/2019)

Read carefully the information contained in this manual before assembly, installation and use of the
equipment.

www.schneider-electric.com
11/11/2019 User Manual – Saitel DR Platform

Change Control
Rev Date Description
01 19-11-2019 Initial edition.

General Information
The Saitel platform and all its components have been developed in accordance to the requirements
for a quality management system, complying with the ISO 9001:2015 Norm.

Document nº: SE-F800-USR

Revision/Date: 01 / 19-11-2019
File: Saitel DR Platform – User Manual_EN_01.pdf
Retention period: Permanent throughout its validation period + 3 years after its
cancellation.

Reference Documents

User Manual Document Code

Easergy Builder user manual FTE-S856-MSS

webTool user manual FTE-S856-MSW

IEC101 user manual FTE-S854-I1D

IEC104 user manual FTE-S854-I4D

IEC103 Master user manual FTE-S854-I3D

Modbus user manual FTE-S854-MBD

ISaGRAF user manual FTE-ISD-S854

DNP user manual FTE-S854-DNP

SOE user manual FTE-S854-SOE

IEC61850 Ed1 user manual FTE-S854-IEC61-1

IEC61850 Ed2 user manual FTE-S854-IEC61-2

HUe user manual SE-M588-USR

HU_A user manual SE-M551-USR

HU_AF user manual SE-M503-USR

HU120 user manual SE-M590-USR

AB_AI user manual SE-M556-USR

AB_AO user manual SE-M557-USR

AB_DI user manual SE-M555-USR

AB_DO user manual SE-M554-USR

AB_DIDO user manual SE-M572-USR

AB_MIO user manual SE-M566-USR

Pag 2
User Manual – Saitel DR Platform 11/11/2019

AB_SER user manual SE-M-USR

AB_AC user manual SE-M562-USR

AB_AC/LPVT user manual SE-M579-USR

Software Version in this Manual

The information in this manual is valid for the software versions listed below. This information is
also valid for later versions, although some parameters may change slightly:

RTU Software Easergy Builder (Plugin)

Module
Module Version Plugin Version

Baseline 11.04.17_6825

VxWorks VxW_19_06_27_15_35_02

Easergy Builder Tool 1.5.9.1

Local Acquisition claqBinC 10.00.12 CLAQ 01.01.01

Synchronization thm 05.03.13

coreDb coreDb 10.01.08

Channels chan 03.00.19

Formula formBinC 10.00.13

Web Server (webTool) webServer 03.03.01

Supervision supBinC 10.01.18

Sequence of Events soeBinC 10.00.07 SOE 01.01.02

AB_AC software AB_AC_A.bin 02.00.13

AB_AI software AB_AI.bin 01.07.07

AB_AO software AB_AO.bin 01.00.01

AB_DI software AB_DI.bin 01.07.08

AB_DIDO software AB_DI_DO.bin 01.01.06

AB_DO software AB_DO.bin 01.07.10

AB_MIO software AB_MIO.bin 02.00.03

AB_SER software AB_SER.bin 01.00.05

HU_AF acquisition software AB_F.bin 01.00.04

HU120 acquisition software AB_RIO.bin 01.00.02

Pag 3
11/11/2019 User Manual – Saitel DR Platform

Content

1 SAFETY & HEALTH .................................................................................................. 5

2 SAITEL DR FAMILY ................................................................................................ 16

3 BASELINE SOFTWARE IN SAITEL DR ................................................................. 32

4 PHYSICAL MOUNTING & INSTALLING ................................................................ 51

5 CONFIGURATION & MAINTENANCE .................................................................... 63

Pag 4
User Manual – Saitel DR Platform 11/11/2019

1 Safety & Health

Pag 5
11/11/2019 User Manual – Saitel DR Platform

Content

1 SAFETY & HEALTH .................................................................................................. 5

1.1 INTRODUCTION ........................................................................................................ 7

1.1.1 INFORMATION OF SECURITY .............................................................................. 7
1.1.2 PRESENTATION ................................................................................................ 8
1.2 INTRODUCTION TO SAFETY ....................................................................................... 8
1.3 SYMBOLS AND LABELS ON THE EQUIPMENT ............................................................. 9
1.4 INSTALLATION, SETUP AND OPERATION ................................................................... 9
1.5 EARTHING ............................................................................................................. 11
1.5.1 ELECTRICAL SAFETY ...................................................................................... 11
1.5.2 FUNCTIONAL EARTH (EMC) ............................................................................ 12
1.6 HANDLING ELECTRONIC COMPONENTS .................................................................. 13
1.7 TECHNICAL SPECIFICATIONS FOR SAFETY .............................................................. 13
1.7.1 PROTECTIVE ELEMENTS ................................................................................. 13
1.7.2 ENVIRONMENTAL CONDITIONS ........................................................................ 13
1.7.3 STORAGE CONDITIONS ................................................................................... 14
1.8 TECHNICAL LABEL ................................................................................................. 14
1.9 PACKING AND UNPACKING ..................................................................................... 15
1.10 DECOMMISSIONING AND DISPOSAL ......................................................................... 15
1.11 NORMS AND STANDARDS / CE MARK ..................... ERROR! BOOKMARK NOT DEFINED.

Pag 6
User Manual – Saitel DR Platform 11/11/2019

1.1 Introduction

1.1.1 Information of Security

Important information
The illustrations shown in this manual are intended for exemplary purposes. As there are variables
and requirements which depend on each particular installation, Schneider Electric will not be held
responsible for the misuse of the equipment based on the examples herein published.
Read these instructions carefully and look at the equipment to become familiar with the device
before trying to install, operate, service or maintain it. In this manual you can find different types of
messages associated with situations that have different level of risk for people and / or for the
equipment.

This symbol indicates "DANGER" or "WARNING". This symbol informs of an

electrical risk that will cause personal injuries if the instructions are not followed.

This symbol is associated to a safety alert. It is used to warn of possible personal

injury hazards. The user must follow all instructions or messages associated to this
symbol to avoid possible injuries.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or serious
injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

NOTICE
NOTICE is used to address practices not related to physical injury. The safety alert symbol shall
not be used with this signal word.

Restricted Liability
Electrical equipment should be serviced and maintained only by qualified personnel. All person
who can contact the equipment must be informed and must read the chapter “Safety & Health” of
this manual.

WARNING
If this equipment is used in a different form from the recommended one by Schneider Electric,
the protection assured for the equipment could be compromised.

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.

Pag 7
11/11/2019 User Manual – Saitel DR Platform

To Keep in Mind
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 who fulfill with requirements in paragraph 1.2 .

1.1.2 Presentation
This manual provides information for a safe handling, commissioning and testing. This chapter also
includes descriptions of the labels on the equipment.
Documentation for equipment ordered from Schneider Electric is dispatched separately from
manufactured goods and may not be received at the same time. Therefore, this guide is provided
to ensure that printed information which may be present on the equipment is fully understood by
the recipient.
The technical data in this safety guide is typical only, see the technical data section of the user
manual for specific details of a particular equipment.
Before carrying out any work on the equipment the user should be familiar with the
contents of this Safety chapter and the ratings on the equipment’s rating label.
THE SAFETY SECTION MUST BE READ BEFORE STARTING ANY WORK ON
THE EQUIPMENT.

1.2 Introduction to Safety

The information in this chapter is provided in order to the equipment is properly installed and
handled maintaining it in a safety condition. It is assumed that everyone who will be associated with
the equipment will be familiar with the contents of that Safety section.
When electrical equipment is in operation, high voltages will be present in certain parts of the
equipment. Failure to observe warning notices, an incorrect or not appropriate use may endanger
personnel and equipment and also cause personal injury or physical damage.

WARNING
Before working with the terminal of connection, the equipment must be switched off and
disconnected of the power supply.

Proper and safe operation of the equipment depends on appropriate shipping and handling, proper
storage, installation and commissioning, and on careful operation, maintenance and servicing. For
this reason, only qualified personnel may work on or operate the equipment.
Qualified personnel are individuals who:

• Have read and understood the information on the device and its user manual.

• Are familiar with the installation, commissioning, and operation of the equipment and of the
system to which it is being connected.

• Are able to safely perform switching operations in accordance with accepted safety engineering
practices and are authorized to energize and de-energize equipment and to isolate, ground,
and label it.

• Are trained in the care and use of safety apparatus in accordance with safety engineering
practices.

• Are trained in emergency procedures (first aid).

Pag 8
User Manual – Saitel DR Platform 11/11/2019

It is necessary to consider that the documentation of the equipment collects the instructions for its
installation, set up and operation. However, the manuals could not cover all the possible
circumstances neither include specific information on all the details.
In case of questions or specific problems, contact with his sales office of Schneider Electric or with
the customer care center and request the necessary information.

1.3 Symbols and Labels on the Equipment

Before the equipment is installed or commissioned, the user must understand the following
symbols, which may be used on the equipment or referred to in the user documentation:
Table 1 – Symbols
Symbol Associated Text Description
International Electrotechnical Commission (IEC)
symbol associated to a DANGER or WARNING
Possibility of electric
message indicating that there is an electrical
chock
risk. Failure to follow these instructions could
cause damage to people or death.
Symbol associated with a risk alert. The user
Caution, read the
must read the manual before handling the
manual.
equipment.
American National Standards Institute (ANSI)
symbol associated to a DANGER or WARNING
Possibility of electric
message indicating that there is an electrical
chock
risk. Failure to follow these instructions could
cause damage to people or death.

Protective earth Associated symbol to the protective ground

connection connection.

This symbol indicates that the equipment has

CE Mark been developed in compliance with all
applicable European Directives.
Electronic This symbol indicates that, at the end of its life,
equipment. Special this module must be discarded according to the
instructions must be WEEE Directive (Waste Electrical and Electronic
followed for Equipment).
disposed.
The equipment has been designed and
Compliant with
manufactured according to RoHS Directive
RoHS.
(Restriction of Hazardous Substances).

Direct Voltage Symbol of direct voltage (VDC).

Alternate Voltage Symbol of alternate voltage (VAC).

1.4 Installation, Setup and Operation

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.

Pag 9
11/11/2019 User Manual – Saitel DR Platform

There are several acquisition blocks in Saitel DR that use high voltages (> 50 V). The user is
responsible to check that the characteristics of each equipment are adapted and convenient for his
installation.
Not following these instructions can be dangerous for the people and the equipment.

DANGER
Devices that handle dangerous tensions are marked with a sticker on the front label (size: 12,5
mm). This label must be visible all the time while the module is installed on the DIN rail.

The following products handle dangerous tensions:

• HU120: High-performance CPU with acquisition (P/N M590xx000x).

• HU_AF: Advanced head unit with acquisition (P/N M503xx3x0x and P/N M503xx4x0x). For
other part numbers, depending on the voltage managed by the equipment connected to digital
outputs, the module should be marked. It will not be marked at the factory.

• AB_DI: Digital inputs module (P/N: M55520000x, M55530000x and M55540000x).

• AB_DIDO: Input and output digital module (P/N M5722x000x, M5723x000x and M5724x000x).
For other part numbers, depending on the voltage handled by the equipment connected to the
digital outputs (voltage > 50 V), this module must be marked with a electric risk label. It will not
be marked on factory.

• AB_AC: Direct measurements module (P/N M562x0000x).

• AB_DO: This module does not handle high voltages, it will not be marked at the factory. This
module must be marked with a electric risk label when some equipment that manage voltage
higher than 50 V are connected to digital outputs.
It is recommended to install the RTU inside a cabinet with a key. This cabinet only should be
opened by a qualified person.
If this type of cabinet isn't available, a barrier must be installed in order to avoid an accidental
contact with these dangerous elements. This barrier only should can be removed using a special
tool.

An electrical risk symbol with enough size must be included on the cabinet’s door or
on the barrier.

The following image shows an example:

Figure 1 – Barrier of protection for elements with dangerous voltages.

Pag 10
User Manual – Saitel DR Platform 11/11/2019

WARNING
If the barrier has to be removed in order to access to equipment, personnel responsible for the
task must be sure that the barrier is installed again when the task is finished.
While the RTU is accessible for a user, all people must follow all instructions to prevent
electrical risk or discharges.

Not following these instructions can give like result that the device do not work properly
or even can damage to the people or devices.

Terminals will not be accessible to the user directly once it has made the installation of the
equipment.

NOTICE
The cabinet must remain closed with key or the protection barrier installed after the installation is
finished.

The cabinet or installation must have a general switch placed just in the cable entry of the
installation (see paragraph 1.7.1 )
For the cleaning of the equipment, it is recommended to remove the power and to use only a dry
cloth by the surface when it detects excessive presence of dust or any element deposited on the
surface.

WARNING
Don’t use liquid products of cleanliness due to the presence of active parts.

Because of the variety of uses of the product, the managers of the application and use of this
controller device will have to take the measures to ensure the fulfillment of all the requests of
security and provision of each application. The requests do reference to the applicable laws,
regulations, codes and standard.

1.5 Earthing

WARNING
• Before energizing the equipment, it has to be earthed properly such as it indicates in
following sections.
• When installing the equipment, ground is the first thing that should be connected and
the last one that should be disconnected.
Saitel can be earthed for two distinct needs:

• Electric safety (Protective Earth, PE).

• Functional earth: To improve the behavior in ElectroMagnetic Compatibility (EMC) and to

derive perturbances to earth.

1.5.1 Electrical Safety

Only qualified personnel, with knowledge about hazards associated with electrical equipment is
authorized to install Saitel DR. In general, the installation shall comply with the standard IEC
61010-1.

The modules must be installed on a metallic DIN Rail which is fixed on a metallic
surface. This metallic surface must have an M4 screw marked with this symbol.
According to the norm IEC 61010-1, the ground of the cabinet or installation must be
connected to this screw.

Pag 11
11/11/2019 User Manual – Saitel DR Platform

Saitel DR modules have a metallic enclosure offering protection for isolation faults.

WARNING
All electronic equipment with high voltage must be disconnected before dismounting a module
from the DIN rail.

A dedicated connection with green/yellow wire should be used to have electric continuity to the
installation protective earth. Use a wire with adequate section according to IEC 61010.
Figure 2 – Yellow and Green cable for earthing.

The design and installation of the cabinet is responsible for compliance with all the existing
international and national electrical codes concerning protective grounding of any equipment.

WARNING
According to Electrical Safety:

• The screw for ground must be exclusive for this use.

• The power voltage must be supplied by a power supply that offers double or reinforced
insulation against voltages higher than 50 V.

1.5.2 Functional Earth (EMC)

In this case the main rule is that the connection has to do with wires of the lower possible length to
the screen or connection of put to earth nearer. In this case the section of the driver is not notable,
is more, it advises that the use of flat wires or flexible conductive bands for a good behavior EMC.
The lane DIN must have terminals of earthing (of yellow and green color) necessary to connect the
terminals of PE (if it is present).
Figure 3 – Terminal for functional earth (EMC).

All Saitel DR modules with power or polarization connector have an exclusive terminal for earthing
EMC. These modules are HU120, HUe, HU_A, HU_AF, XU, AB_DO, AB_DIDO and AB_SER with
external polarization.
Figure 4 – Example of earthing for EMC.

Pag 12
User Manual – Saitel DR Platform 11/11/2019

1.6 Handling Electronic Components

Like any electronic equipment, Saitel is susceptible to receive electrostatic discharges during the
handling. It is necessary to take the usual measures to minimize this risk, since serious damage to
the equipment can be caused, which may not be detected immediately but which may affect the
reliability of the product.

WARNING
The enclosure ONLY should be removed when is strictly necessary, because this action has a
risk for the equipment. The following precautions will be taken:

• Before removing the enclosure, you must be equipotential with the equipment. You must
have a grounding bracelet and the device must be connected to ground as well

• Avoid touching the electronic. The board must be always manipulated for the edges.

• If the equipment has to be passed between two persons, both must be equipotential.

• Put the module always on an antistatic surface or on a surface equipotential with you.

• During the storage and transport, the module will remain in the packaging.
Not following these instructions can give like result that the device do not work properly
or even can damage to the people or equipment.

1.7 Technical Specifications for Safety

1.7.1 Protective Elements

The cabinet's engineering and installation must include a general automatic switch next to the
cables' input in the cabinet; once the door is opened, high voltages must be interrupted inside. This
switch must be located at a place which is not accessible by a third person while the operator is
working in the cabinet.
Moreover, the installation will incorporate a circuit breaker of 5A next to the cabinet protecting it
from possible overcurrent in the power supply.
Both switches will be labeled with the symbol O as "Off" and I as “On”.

WARNING
The connection / disconnection switch must be installed in a fixed element (for example the wall
of the cabinet) and it mustn’t break any earthing wire.

1.7.2 Environmental Conditions

The protection degree of the device is IP20.

WARNING
This equipment has been designed ONLY for indoor use.

If it is necessary for its use in some external surroundings, it must be installed into a cabinet or
specific accommodation that contributes at least a degree of protection IP54, protected against the
dust and water.
The electronic cards of the modules will be able to be tropicalized or no according to the
manufacturing option. The tropicalized used is the AVR80, of the company ABchimie. It can consult
all the technical information of this type of finishing in http://www.abchimie.com/.

Pag 13
11/11/2019 User Manual – Saitel DR Platform

Other important data are:

• Altitude until 2000 m.

• Operation temperature range: Between -40 ºC and 70 ºC. (IEC 60068-2-1 and IEC 60068-2-2).

WARNING
According to the standard 60950-1, all electrical safety tests have been done in an
environmental temperature range of -40 ºC to 60 ºC. For higher temperature (> 60 ºC), the
module must be handled with care, since the metal surface could reach a dangerous
temperature for the user.

• Maximum relative humidity of 95%. (IEC 60068-2-30)

• Degree of pollution II. (IEC 60255-5)

• Overvoltage transitory until levels of Category III. (IEC 60255-5)

1.7.3 Storage Conditions

The continuous exhibition to some high levels of humidity during the storage can cause damages
to the electronic components and reduce the useful life of the equipment.
We recommend that, in the enclosure of storage, the relative humidity do not exceed 50%.
Before the installation of an electrical equipment, it is recommended to leave the necessary time for
the acclimatization of the environmental temperature.

1.8 Technical Label

Each Saitel product includes a technical label with the following information:
Figure 5 – Technical label.

NOTICE
On the “Technical data” zone, you can see relevant information about the input and output
voltage in the module. Any voltage greater than 50 V must be consider as a high voltage.

Pag 14
User Manual – Saitel DR Platform 11/11/2019

1.9 Packing and Unpacking

All Saitel modules are packaged separately in their own carton box and shipped inside outer
packaging. Use special care when unpacking the device. Don’t use force.

NOTICE
Our products leave our factory in closed, sealed original packaging. If at receipt of the delivery
the transport packaging is open or the seal is broken, the confidentiality and authenticity of the
information contained in the products cannot be ensured.

The design revision and manufacturing options can be determined using the P/N included in the
packaging label on packaging.
After unpacking the device, inspect it visually to be sure it is in proper mechanical condition.
If the product needs to be shipped, the original packaging must be used, including foams and the
carton box. If the original packaging is no longer available, make sure that the packaging used is
according to ISO 2248 specifications for a drop height 1 m.

1.10 Decommissioning and Disposal

Saitel products are marked with this symbol, it means that, at the end of its life cycle,
you mustn't dispose the product together with habitual residues. To avoid the
possible damage to the environment or to the human health that represents the
uncontrolled elimination of residues, please, separate the battery (if there is one) of
the other elements, and each one must be recycled according to the local regulation.
Some Saitel DR modules include a Lithium battery NOT rechargeable: HU_A and HU_AF. More
information about the model in the technical data table included in the user manual for each
module.

WARNING
Only a qualified person should change the battery when is necessary, and the same model of
battery must be used. More information in the technical specifications table at the end of each
user manual.

Pag 15
11/11/2019 User Manual – Saitel DR Platform

2 Saitel DR Family

Pag 16
User Manual – Saitel DR Platform 11/11/2019

Content
2 SAITEL DR FAMILY ................................................................................................ 16

2.1 FIRST APPROACH .................................................................................................. 18

2.2 SAITEL DR MODULES ............................................................................................ 18
2.2.1 GENERAL FEATURES ...................................................................................... 19
2.2.2 LED INDICATORS ........................................................................................... 19
2.3 TYPES OF MODULES .............................................................................................. 20
2.3.1 HU MODULES (CPU) ...................................................................................... 20
2.3.2 COMMUNICATION MODULES ............................................................................ 21
2.3.3 ACQUISITION BLOCKS (I/O MODULES) ............................................................. 21
2.4 ITB (INTELLIGENT TERMINAL BLOCK) ..................................................................... 23
2.4.1 GENERAL DESCRIPTION .................................................................................. 23
2.4.2 DATA ACQUISITION BUS.................................................................................. 24
2.4.3 ARCHITECTURE LIMITS ................................................................................... 25
2.4.4 ITB BASIC FUNCTIONS.................................................................................... 26
2.5 SAITEL DR ARCHITECTURES .................................................................................. 28
2.5.1 STAND-ALONE CONFIGURATION...................................................................... 28
2.5.2 MICRORTU .................................................................................................... 28
2.5.3 SMALL/MEDIUM RTU ...................................................................................... 29
2.5.4 LARGE RTU / DISTRIBUTED ACQUISITION ........................................................ 29
2.5.5 DISTRIBUTED ACQUISITION AND CONTROL/PROCESS REDUNDANCY................. 30
2.6 STANDARDS COMPLIANCE ..................................................................................... 31

Pag 17
11/11/2019 User Manual – Saitel DR Platform

2.1 First Approach

Saitel DR is a hardware platform by Schneider Electric. It consists of a set of equipment which

have been specifically designed for real-time control and automation applications. Saitel DR is a
high-technology platform which serves Schneider Electric’s business areas.
On this hardware platform, the Baseline Software Platform is installed. This software is used in
Saitel families (Saitel DP and Saitel DR) and other Schneider Electric products.
Other features identifying Saitel DR are:

• A DIN rail is used for the mechanical installation.

• The terminal blocks for field-connection are completely built into acquisition blocks.

• The communication between the controls units integrated in a distributed system is mainly
established by Ethernet.
Figure 6 – Saitel DR.

Saitel DR’s design has been optimized to meet the most demanding requirements of multiple
sectors:

• Safety and reliability requirements for power, gas and water supply, as well as sewage
treatment plants, etc.

• Compliance with all directives under CE mark.

• Centralized monitoring and control of geographically-distributed systems which support

hierarchical data acquisition and sharing networks.

• Local monitoring and control with data sharing capabilities of plant-distributed equipments.

• Quick troubleshooting, including the possibility of using programmable automation execution.

WARNING
Please note Saitel DR does not support hot-swapping. If a module is disconnected on
operation, the RTU will be reset.

2.2 Saitel DR Modules

Saitel DR modules are designed to operate in aggressive industrial environments, meeting the
most demanding immunity requirements to reduce electromagnetic disturbances. The low-
consumption design allows modules to operate without forced ventilation, which widens the
application range considerably.
All modules are mounted on a DIN rail and can be distributed in several rows within the same
cabinet.

Pag 18
User Manual – Saitel DR Platform 11/11/2019

2.2.1 General Features

The figure below shows the typical appearance of a Saitel DR module:
Figure 7 – Saitel DR module

Modules are designed to be interconnected by using a flat ribbon, as shown in the figure below.
Thus, the module’s mount and dismount procedures are easier, since only flat ribbon bridges need
to be removed from attached modules. These resistant bridges are manufactured to allow multiple
connections and disconnections.
Figure 8 – Connection between modules

2.2.2 LED Indicators

Saitel modules integrate visible indicators in the upper front panel to provide status and diagnostic
information. All these LED indicators are labeled to make interpretation easy.
Following figure shows an example of LED indicators on a Saitel DR module:
Figure 9 – LED indicators

Pag 19
 11/11/2019 User Manual – Saitel DR Platform

2.3 Types of Modules

2.3.1 HU Modules (CPU)

The following CPUs are available in Saitel DR:
HUe – High-Performance HU

• OS: Linux.
• Web tool: webApp.
• Ethernet ports: 3 (copper or fiber optic).
• USB port and SD card.
• Synchronization: GPS / SNTP / IRIG-B / Protocol.
• Serial communications: 3 ports (RS-232 / RS-485).
• Watchdog output.
• Command console tool: MiniUSB port and Bluetooth.
• Cybersecurity included in baseline.

HU120 – High-Performance HU with Local Acquisition

• OS: Linux.
• Web tool: webApp.
• Ethernet ports: 3 (copper or fiber optic).
• USB port and SD card.
• Synchronization: GPS / SNTP / IRIG-B / Protocol.
• Serial communications: 2 ports (RS-232 / RS-485).
• Watchdog output.
• Command console tool: MiniUSB port.
• Cybersecurity included in baseline.
• Field connection: 16 DI and 8 DO.
HU_A – Advanced HU

• OS: vxWorks.
• Web tool: Saitel webTool.
• Ethernet ports: 3 (copper).
• Compact flash.
• Synchronization: GPS / SNTP / IRIG-B / Protocol.
• Serial communications: 3 ports (RS-232 / RS-485).
• Watchdog output.
• Command console tool: DB-9 port.

Pag 20
 User Manual – Saitel DR Platform 11/11/2019

HU_AF – Advanced HU with Local Acquisition

• OS: vxWorks.
• Web tool: Saitel webTool.
• Ethernet ports: 3 (copper).
• Compact flash.
• Synchronization: GPS / SNTP / IRIG-B / Protocol.
• Serial communications: 3 ports (RS-232 / RS-485).
• Watchdog output.
• Command console tool: DB-9 port.

2.3.2 Communication Modules

There is only one communication module in Saitel DR but with 4 different models depending on its
P/N:
AB_SER – Communication module
• 4 serial ports.
• DB-9 / Fiber Optic
• Synchronous and asynchronous communications
• Synchronization from HU.
• RS-232 / RS-485 / RS-422
• Power input depending on the ordering options.

2.3.3 Acquisition Blocks (I/O Modules)

The following AB are available:
AB_DI – Digital Inputs
• Two removable terminal blocks.
• 16 digital inputs (single/double/slow counter)
• 4 options for DI polarization:
o 12 – 24 VDC
o 48 – 60 VDC
o 125 VDC
o 220 VDC

Pag 21
 11/11/2019 User Manual – Saitel DR Platform

AB_DO – Digital Outputs

• Three removable terminal blocks (signals and polarization).
• 8 digital outputs (single/double and SBO/Direct)
• 2 options for DO polarization:
o 24 VDC
o 48 VDC

AB_AI – Analog Inputs

• Two removable terminal blocks.
• 8 analog inputs (voltage / current (external resistor is required)).
• Range configurable in voltage or current.

AB_AO – Analog Outputs

• Four removable terminal blocks (analog and digital signals).
• 4 analog outputs.
• 4 digital outputs (only for validation purpose).
• Open loop indication

AB_DIDO – Digital Inputs and Outputs

• Five removable terminal blocks (signals and polarization).
• 16 Digital Inputs (single/double/slow counter)
• 8 Digital Outputs (single/double and SBO/Direct).
• 4 options for DI polarization:
o 12 – 24 VDC
o 48 – 60 VDC
o 125 VDC
o 220 VDC
• 2 options for DO polarization:
o 24 VDC
o 48 VDC
AB_MIO – Multiple Inputs and Outputs
• Six removable terminal blocks.
• 8 Analog inputs (range configurable in voltage or current)
• 2 RTD inputs (4-wire inputs).
• 2 Fast-counter inputs (single and double pulse)
• 2 Analog outputs (open loop indication)

Pag 22
 User Manual – Saitel DR Platform 11/11/2019

AB_AC – Direct Measurements

• Four removable terminal blocks.
• 3 Voltage inputs
• 3 Current inputs (0 – 5 VRMS)
• 1 Neutral (homopolar) input.
• 2 options for voltages:
o 110 VAC (L-L)
o 400 VAC (L-L)
• 1 Digital input and 1 digital output (only for Synchrocheck
application)
• Available applications:
o Basic application (calculation of measurements)
o Synchrocheck (monitor and control based on
conditions of synchronism)
AB_AC/LPVT – Direct Measurements (Low Power)
• Three removable terminal blocks + 3 BNC connectors.
• 3 Voltage inputs (0 – 1.2 VRMS)
• 3 Current inputs (0 – 5 ARMS)
• 1 Neutral (homopolar) input.
• 1 Digital input and 1 digital output (without use)
• Available applications:
o Basic application (calculation of measurements)
o Fault Indication
o Quality

2.4 ITB (Intelligent Terminal Block)

2.4.1 General Description

An ITB consists of one HU, a set of ABs, together with all required building elements (termination
module, expansion module, flat cables…)
Figure 10 – Basic ITB

The following figure shows a typical architecture of a system based on the Saitel DR platform.
There is an HU module (or two if CPU are redundant) connected to a series of AB acquisition
blocks including the expansion (XU) and termination units (TU or BT) needed.

Pag 23
11/11/2019 User Manual – Saitel DR Platform

Figure 11 – Saitel DR Architecture.

To define the ITB’s structure, the user should consider the following factors:

• The system’s bus is expandable so acquisition blocks can be installed in different rows.

• Each row can contain a maximum number of ABs are interconnected through flat ribbon
bridges.

• The last module in each row containing ABs must be a TU (Termination Unit) or a BT (Basic
Termination Unit) in the last row.

• The first module in each row (except for the first row) must be an XU (eXpansion Unit). This
module, together with the TU from the previous row, is used for bus expansion by
interconnecting one row to the next.

• If some communication modules (AB_SER) are included, they all must be installed in the first
row.

• The physical support of each row is a DIN rail, which allows modules to be installed by a simple
click.
Other hardware and software limits are indicated later in this manual.
The system can include more than one ITB, communicating with each other through an Ethernet
network. This functionality allows designing architectures capable of covering any requirement of
the current distributed control systems.

2.4.2 Data Acquisition Bus

Power, data, synchronization, signals and other information are transmitted between HU and ABs
using an internal bus. This bus is based on a removable flat ribbon cable between a module and
the following one in the ITB.
The bus is expanded to the following ITB rows by using a cable which connects the DB15 pins
available in the TU and XU modules. The power isn’t expanded between a row and the following. A
power input terminal is available in each HU and XU modules. This terminal is used in order to
power all module in its row.

Pag 24
User Manual – Saitel DR Platform 11/11/2019

Figure 12 – TU-XU connection.

At the end of each row there must be a termination module, that is, a TU or a BT.

2.4.3 Architecture Limits

Depending on the type of HU and the ITB architecture, you must have in account some limitations
to make the ITB:
Table 2 – Hardware and database limits depending on the HU

Limitation HU_A HU_AF HUe HU120

Max total number of AB modules 32 31 32 31

Max consumption per row (first row) 10 W 10 W 10 W 5W

Other limitations not depending on the CPU:

• Max number of rows: 4

• Max number of AB modules per row: 8.

• Max consumption per row (excluding the first): 10 W

• Max longitude of the bus flat ribbon: 5 cm

• Max long of extension cable (between rows): 1.5 m

• Max number of communication modules: 4, always in the first row next to the HU
If you need to install some AB_MIO modules (revision B3 and earlier) and / or some AB_AC
modules (revision B5 or earlier) in the ITB, you should take into account some additional
restrictions:

• The AB_MIO and AB_AC modules must be installed in the first positions right after an XU or an
HU module.

• If you install an AB_AC or AB_MIO module in a row, the maximum number of modules to be
installed in this row is 4.

• In a row there can only be installed a maximum of two AB_MIO or AB_AC modules (same or
mixed types).
According to these restrictions, valid combinations are as follows:

• If it is the 1st row of the ITB: (x,x,x,x,y,y,y,y) or (z,z,x,x).

• If it is the 2st, 3st or 4st row: (y,y,y,y,y,y,y,y) or (z,z,y,y)

Where:

Pag 25
 11/11/2019 User Manual – Saitel DR Platform

x = AB_SER, AB_AI, AB_AO, AB_DI, AB_DO or AB_DIDO.

y = AB_AI, AB_AO, AB_DI, AB_DO or AB_DIDO.
z = AB_MIO or AB_AC.

NOTICE
These restrictions don’t apply to later revisions of the AB_MIO and AB_AC modules.

2.4.4 ITB Basic Functions

The control unit (CPU), also called head unit (HU), performs the control functions for the complete
system, centralizes the information acquired by other modules, and executes the programmable
logic control, communication protocols and user-specific applications.
The communication with the acquisition modules in the ITB is established by an internal high-speed
bus that makes the system highly reliable even in noisy environments.
Figure 13 – Communication between the CPU and acquisition blocks.

The CPU module controls and manages the following functions:

ITB Controller
The Baseline software installed in the HU controls the operation of both, HU and ABs connected to
the head unit througth the bus.
This control includes:

• Operation mode monitoring. It performs functions as hardware and software Watchdog control,
the states control of the ABs and the HU and the provision of diagnostic information about the
ITB status through the LED indicators and several log files. These files can be consulted by a
user with sufficient privileges through SFTP, webTool or webApp.

• Interface with the operator through the console, webApp or webTool (for supervision and
maintenance) and Easergy Builder (for configuration).

• Firmware upgrade by SFTP or webApp (using and Ethernet port) or USB 2.0 port.
ITB Configuration
The HU module maintains and manages the information that supports the real-time database,
coreDb. In this database, the I/O signals are related to the communication protocols signals. The
configuration is based on XML files that are generated with the Easergy Builder tool. These files
are generated on a PC and sent to the CPU via an SFTP connection through Ethernet ports.
ITB Synchronization
Up to two different synchronization sources can be configured. In this configuration is included the
priority level for each source, so there will be a primary and a secondary source. If both sources
are active, only the primary source will synchronize the system.

Pag 26
 User Manual – Saitel DR Platform 11/11/2019

NOTICE
The primary source is used to synchronize the ITB, if available. Otherwise, the secondary source
is used.

The available synchronization sources are:

• GPS: A GPS connected to a serial port (usually COM1). The time received from the GPS is
used to set the system’s clock and the RTC.

• SNTP: A SNTP source through Ethernet. HU modules can operate as an SNTP client or as an
SNTP server.

• Protocol: Most control protocols allow synchronizing slave devices.

• Console: The user can set the system's time manually from the console terminal.

• IRIG-B: It’s possible to configure the HU as a server and/or client. The communication always
will be made with IRIG-B compliant devices.

NOTICE
If the HU is configured as an IRIG-B server, it’s necessary to include an AB_SER module in the
ITB. The IRIG-B signal will be sent to client devices through the COM ports of this module. More
information in the AB_SER user manual.

If the synchronization source is not configured, the console device will always be created by
default. The console operates as the lowest priority when another source is configured.
ITB Communications
Saitel DR supports the following communication protocols with field devices:

• IEC101 master and slave.

• IEC103 master.

• IEC104 master and slave.

• DNP 3.0 master and slave.

• Modbus master and slave.

• IEC61850 client, Edition 1 and 2.

• IEC61850 server, Edition 1 and 2.

Each protocol is available or not depending on the type of CPU (More information in each HU user
manual).
I/O Acquisition
The CPU manages the information exchange with the AB modules. This information is sent from
the AB to the CPU through the bus.
The software in the CPU adds the following features:

• Processing I/O information, which offers an added value to the information from field.

• Accessing the internal bus to exchange information with the ABs.

• HU_A, HUe and HU_AF include 4 digital inputs that can be used as 4 general-purpose digital
inputs or as 2 specific-purpose digital inputs and 2 general-purpose digital inputs.

• HU_AF and HU120 are special HU that perform all CPU functions and also has their own
acquisition signals, like other ABs.

Pag 27
 11/11/2019 User Manual – Saitel DR Platform

Real-time Database (coreDb)

The core of the Baseline Software Platform is the real-time database or coreDb. It is a real-time
database which stores not only the information acquired from field devices, but also the information
about the status of the CPU modules and ABs included in the ITB.
coreDb also relates the acquisition signals to the communication protocol signals. This database is
generated in the CPU by using the configuration information.
The information which is received from field in real time is processed, stored in the soreDb and
then related to the communication protocols signals of the ITB, which function is to transfer that
information to the master device.
coreDb can also have as a source of information the result of a logic, which can be implemented by
a third-party software such as ISaGRAF® or within the database itself witch an internal device of
the type “Formula”.
Consult more information about this functionality in the Easergy Builder user manual.
Cybersecurity
Some HU module (for example HUe) are supplied with a standard security policy, complemented
with the definition of an RBAC model (Role-Based Access Control). This model is defined and
managed through a special tool, CAE (EcoStruxure™ Cybersecurity Admin Expert.
This funcionality is not available for HU_A and HU_AF.

2.5 Saitel DR Architectures

Thanks to its modular and flexible nature, Saitel DR allows the implementation of a small RTU
system which can be expanded to the most complex distributed control system. Some examples
can be found below.

2.5.1 Stand-Alone Configuration

HU_AF and HU120 are control modules with integrated signal acquisition (digital inputs, digital
outputs and analog inputs). Both can be used in stand-alone mode, but can be expanded with
other ABs if required.

2.5.2 microRTU
A single head unit (for example HU_A) plus a set of acquisition blocks make a microRTU with a
single ITB.
Figure 14 – microRTU.

Pag 28
User Manual – Saitel DR Platform 11/11/2019

2.5.3 Small/Medium RTU

The system illustrated in the previous example can be expanded incresing both, processing
capacity and number of ABs in the ITB. These components are used to build a small/medium size
RTU.
Figure 15 – Small / Medium RTU.

2.5.4 Large RTU / Distributed Acquisition

The following figure illustrates a system which integrates a large RTU with distributed data
acquisition and processing capabilities:
Figure 16 – Large RTU with distribute acquisition.

As shown in the figure, there are various acquisition ITBs which are interconnected through an
Ethernet network and controlled by a primary ITB (which also operates as an acquisition ITB). This
primary ITB includes at least one HU in charge of gathering and processing all the information.

Pag 29
11/11/2019 User Manual – Saitel DR Platform

2.5.5 Distributed Acquisition and Control/Process Redundancy

To build a distributed acquisition and control system, which requires process redundancy, two HU
modules can be installed in a redundant configuration. In this case, all signals are obtained from
other separate acquisition ITBs.

Figure 17 – Distributed acquisition and control system / processing redundancy.

The more powerful HUs have double Ethernet ports to connect to two different buses; the first one
is a data bus to communicate with the acquisition ITBs and the second one is a processing bus to
communicate with the other processing units in the system.
As shown in the figure from above, there are multiple ITBs acquiring and sending field data by
means of an Ethernet bus to a control unit made up of two redundant HU modules. This control unit
communicates with a switch using the second Ethernet bus.

Pag 30
User Manual – Saitel DR Platform 11/11/2019

2.6 Standards Compliance

Cybersecurity (Only available in HUe and HU120 modules)

Based on IEC62351
IEC62443
Security Engine SEC 3.3.2 (XOR acceleration)
Supported cryptographic algorithms 3DES, AES, MD5/SHA, RSA/ECC, & FIPS (determinist generator)
Processing Single pass encryption and authentication
Security protocols SSL 3.0, SSL 3.1 / TLS 1.0

CE Mark
Standards, Directives LVD – Low Voltage Directive Directive 2014/35/UE
and harmonized norms.
EMC – Electromagnetic Compatibility Directive 2014/30/UE
RoHS 2 Directive 2011/65/EU, according to royal legislative
decree (RD) 219/2013
WEEE – Waste Electrical and Electronic Directive 2012/19/UE according to RD 110/2015
Equipment
EMC tests according to EN 60870-2-1:1996
IEC/TS 61000-6-5:2015
Emission EMC tests Radiated emissions
EN 55022:2006 + A1:2007 From 30 to 1000 MHz (Class A)
EN 55032:2012 From 30 to 6000 MHz (Class A)
Conducted emissions
EN 55022:2006 + A1:2007 From 0.15 to 30 MHz (Class A)
Immunity EMC tests Electrostatic discharges (ESD)
EN 61000-4-2:2009 By air ±8 kV and by contact ±6 kV (Level 3)
Radiated, radio-frequency, electromagnetic field
EN 61000-4-3:2006 + A2:2010 From 80 to 6000 MHz (Level 3).
Electrical fast transient/burst Power: ±4 kV, 5kHz.
EN61000-4-4:2012 Communications ±4 kV 5kHz and 2.5kHz.
E/S ±4 kV 5kHz (Level 4).
Power: ±4 kV symmetric and asymmetric (Level 4)
Surge
Power: ±4 kV, 5kHz.
EN 61000-4-5:2006 Communications: ±4 kV CM, ±2 kV DM (Level 4).
I/O: ±4 kV CM, ±2 kV DM
Conducted disturbances, radio-frequency fields
EN 61000-4-6:1996 + A1:2001 10V 0.15-80MHz 80% AM (Level 3).
Magnetic field
EN 61000-4-8:2010. 100 A/m, 1000 A/m 3s (Level 4).
Immunity to conducted disturbances, induced by
radio-frequency fields
EN 61000-4-16:1998 30V 50Hz, 300V 50Hz 1s (Level 4).
Damped oscillatory wave Power: 1kV DM, 2.5kV CM (Level 4),
Communications and I/O. (f=1MHz)
EN 61000-4-18:2007 + A1:2010
Electric Safety General requirements
EN 60950-1:2006 + A11:2009 + A1:2010 + AC:2011 + A12:2011+ A2:2013
RoHS Directive 2011/65/UE Verification of Lead, Cadmium, Mercury, Chrome
and Bromine

Environmental tests Cold - EN 60068-2-1:2007 -20ºC during 16h (100h)

Dry heat - EN 60068-2-2:2007 +80ºC during 16h (100h)
Damp heat - EN 60068-2-30:2005 25-60ºC with 95%RH during 24h

Pag 31
11/11/2019 User Manual – Saitel DR Platform

3 Baseline Software in Saitel DR

Pag 32
User Manual – Saitel DR Platform 11/11/2019

Contents

3 BASELINE SOFTWARE IN SAITEL DR ................................................................. 32

3.1 GENERAL DESCRIPTION ......................................................................................... 34

3.2 MAIN ELEMENTS .................................................................................................... 35
3.2.1 COREDB – REAL TIME DATABASE (RTDB) ...................................................... 35
3.2.2 DEVICES ........................................................................................................ 36
3.2.3 USER INTERFACES ......................................................................................... 36
3.3 SOFTWARE TOOLS................................................................................................. 36
3.4 SOFTWARE COMPATIBILITY .................................................................................... 37
3.5 LOCAL ACQUISITION .............................................................................................. 38
3.5.1 CENTRALIZED LOCAL ACQUISITION ................................................................. 38
3.5.2 DISTRIBUTED LOCAL ACQUISITION .................................................................. 39
3.5.3 SIGNAL IDENTIFICATION - COORDINATES ......................................................... 40
3.6 ITB INITIALIZATION PROCESS ................................................................................. 41
3.7 TREATMENT OF LOCAL ACQUISITION SIGNALS........................................................ 42
3.7.1 INTRODUCTION ............................................................................................... 42
3.7.2 DIGITAL INPUTS .............................................................................................. 42
3.7.3 DIGITAL OUTPUTS .......................................................................................... 46
3.7.4 ANALOG INPUTS ............................................................................................. 47
3.7.5 ANALOG OUTPUTS.......................................................................................... 49

Pag 33
11/11/2019 User Manual – Saitel DR Platform

3.1 General Description

The Baseline Software Platform is used with Saitel products and other Schneider Electric products.
It consists of:

• Real-time operating system (RTOS): VxWorks or Linux.

• Real-time applications and configuration files (XML format).

• Software tools: Configuration, local and remote maintenance, supervision and monitorization.
The following figure shows the different applications included in the software platform, as well as
additional applications (Devices) implementing new Devices or protocols to upgrade Easergy
Builder.
Figure 18 – Baseline Software Platform.

The operating system abstracts the hardware from the software applications and manages the
applications in real time. It integrates the basic protocols to access the remote unit (SFTP, SSH,
etc.) and manage multiple users.
The real-time database, named coreDb, is probably the most important element. All the other
elements are developed around coreDb.
Figure 19 – Relation between coreDb and other applications.

Pag 34
User Manual – Saitel DR Platform 11/11/2019

The following concepts are related to coreDb:

• Device Controller (also referred to as Controller): Real-time application that accesses coreDb.
Each Controller acts as a producer and/or consumer of information managed by coreDb.

• Point: Each register of coreDb is a point. A point can be included in the table Status, Analog,
Command or Setpoint.

• Device: A set of I/O points that share a common source/destination. A typical example of a
Device is an IED that communicates with the RTU, or the representation of a SCADA
exchanging information acquired or generated by the RTU. A Device is always associated to a
type of Controller.

• Source: Origin of the value of a coreDb data point. Any coreDb data point can have several
different sources (in one or several Devices). This means that a value of a database point can
be configured to be updated by several different entities.

• Destination: Target of the value of a coreDb data point. coreDb data points can be configured
to have several different destinations (in one or several Devices).

NOTICE
It should be noted that any coreDb signal can be associated to more than one source; this is
only applicable to Command and SetPoint tables. Allocating more than source to one point is
not recommended in Status and Analog tables.

• Coordinate: Point identification within a Device. It is unique for each point and has a different
structure for each Controller.

• Configuration Plugin: Specific Configuration plugins extend the Easergy Builder application to
configure Device Controllers.
The user can modify the configuration of each Controller and Device using the appropriate Plugin.
Once the database is completely configured, the files with the new information can be generated
and transferred to the RTU, where they will be processed by the software on startup.

NOTICE
The information exchange, that is, the exchange of configuration data between the RTU and
Easergy Builder is not continuous, but performed through XML files under user’s request. When
the configuration is modified in Easergy Builder and the XML files are sent to the RTU, it
is necessary to reboot the RTU.

3.2 Main Elements

For the user, the Baseline Software Platform has the following main elements:

3.2.1 coreDb – Real Time DataBase (RTDB)

coreDb is the real-time database which stores not only the information acquired from field devices,
but also the information about the HU and acquisition blocks status that are part of the ITB. coreDb
also relates the acquisition signals to the communication protocol signals. This database is
generated in the HU by using the configuration information.
The information which is received from field in real time is processed, stored in the RTDB and then
related to the communication protocols signals of the ITB, which function is to transfer that
information to the master device.

Pag 35
11/11/2019 User Manual – Saitel DR Platform

Figure 20 – Interfaces with coreDb.

CoreDb points are organized in four tables: Status, Analog, SetPoint and Command to group the
different types of points. These internal tables present the following differences:

• Depending on the point type: status, and command tables support integer values, whereas
setpoint and analog tables manage floating values.

• Depending on the treatment of the point: Status and Analog points can be locked or reset to
initial values, whereas the other two signal types cannot. All types can retain the value in a
non-volatile memory.

3.2.2 Devices
Each type of device keeps a list of its associated points, identified by unique labels. These labels
allow the identification of each device point unequivocally as source or destination of a coreDb data
point.
Each point is a piece of information produced (or consumed) by a Device. Within a single Device,
point identifiers (coordinates) are unique and cannot be used by two different points.

3.2.3 User Interfaces

The user can use the following tools in order to access to the RTU information:

• Easergy Builder: configuration tool for Schneider Electric RTUs that uses the Baseline
Software Platform. It has to be installed in a PC, and among other features, it can be used to
perform: offline configuration of the general settings of an RTU (IP address, user
administration, communication channels and so on), design and maintenance of coreDb,
administration of the synchronization mechanisms, configuration of the supervision and
monitoring features.

• Console: advanced diagnostic (for expert users only, local or remote connection). It is possible
to connect the PC through the serial cable to the CON port or using an Ethernet cable to an
ETH port and SSH.

• webTool: is the local and remote user interface for online monitoring, operating and
maintaining the CPU.

3.3 Software Tools

A basic configuration is included with HU, which should be adapted to the requirement of the
system. Depending on the type of HU, following software tools will be available for configuration or
maintenance:

Pag 36
User Manual – Saitel DR Platform 11/11/2019

• Easergy Builder: Engineering tool for the RTU OFFLINE configuration. It allows to include and
adapt the different functions of the RTU to the system where it is being integrated. It is a
software tool that needs to be installed on a PC.

• CAE: Only available for HU with Cybersecurity, HUe and HU120. Engineering tool for defining
the security policy and assigning roles to users. It allows defining a series of rights and
responsibilities in the system for authorized users. It defines WHO, WHAT, WHEN and HOW
can the user do it, according to the RBAC model. It is a software tool that needs to be installed
on a PC.

• webApp: Web tool for online maintenance and monitoring of the RTU with HU using Linux as
OS, HUe and HU120. Using the configuration defined in Easergy Builder and loaded in the HU,
the user can consult and/or change some parameters through the WEB server. Unlike Easergy
Builder, webApp does NOT allow adding new features. Only the parameters included in the
configuration can be changed.

• Saitel Webtool: Web tool for online maintenance and monitoring of the RTU with HU using
vxWorks as OS, HU_A and HU_AF.

• SFTP: Manual exchange of configuration files (for expert users only).

• Console: This tool should only be used by advanced users with a wide knowledge of the
system. The connection can be made through a serial channel (PC’s COMx port) or using SSH
through an Ethernet port. The console is a commands tool, which the user could execute or not
depending on the level of privileges assigned to him

• ISaGRAF (version 3 and 5): Third party software for design, configuration, debugging and
optimization of the embedded logic programs.

3.4 Software Compatibility

Depending on the type of HU, following devices and tools will be available or not:
Table 3 – Software compatibility

Software Function HU_A / HU_AF HUe / HU120

DNP Master Protocol √ √

DNP Slave Protocol √ √
Easergy Builder √ √
Formula √ √
IEC101 Master Protocol √ √
IEC101 Slave Protocol √ √
IEC103 Master Protocol √ √
IEC104 Master Protocol √ √
IEC104 Slave Protocol √ √
IEC6180 Server Ed 1 √ ×
IEC6180 Client Ed 1 √ ×
IEC6180 Server Ed 2 × √

IEC6180 Client Ed 2 × √

ISaGRAF √ √

Pag 37
11/11/2019 User Manual – Saitel DR Platform

Software Function HU_A / HU_AF HUe / HU120

ISaGRAF5 √ √
MICOM Master Protocol √ √
Modbus Master Protocol √ √
Modbus Slave Protocol √ √
Operating System VxWorks Linux
Saitel DR local acquisition (claq) √ √
Sepam Protocol √ √
Sequence of events (SOE) √ √
Synchronization (thm) √ √
Supervision √ √
webTool √ ×
webApp × √

3.5 Local Acquisition

Local acquisition is understood as the handling carried out by the system of the information arriving
to the HU from field devices either through available integrated local acquisition in the HU itself or
through external acquisition blocks (AB).
This manual describes the configuration of the local acquisition signals in general terms, with no
comprehensive information about the configuration of each AB. This chapter explains how
information is processed by the CPU once it is received from each module.
For more detailed information about each AB, please refer to the corresponding user manual.
With respect to the ITB architecture, there are two types:

• Centralized Local Acquisition: All modules are installed over the same ITB, in which there
will only be one HU (or two if redundant). The ITB could have several rows of modules, but only
the first one would have a CPU.

• Distributed Local Acquisition: There would be several acquisition ITB sending information to
a single control ITB. In this case, it would be like all AB would be installed in the same physical
ITB.

3.5.1 Centralized Local Acquisition

The local acquisition Device for Saitel DR is named “claq”. The main functionality of the Local
Acquisition Device Controller is supporting the communication between the inputs and the outputs
managed by the acquisition blocks and coreDb points. This device would be created by default in
every Saitel DR configuration.
The first step to configure the acquisition settings is assembling the ITB in the graphical interface,
including both the HU and the acquisition blocks in the same order as they are physically installed
in the DIN rail.

NOTICE
The graphical interface does not take into account if the ITB is assembled in one or multiple
rows. The modules should always be added in the adequate order, regardless of the number of
TU-XU modules that are installed.

Pag 38
User Manual – Saitel DR Platform 11/11/2019

If when creating the RTU, the needed acquisition blocks were not configured, they could be added
individually later on by editing the corresponding configuration.

It’s necessary to double click in the claq device of the configuration devices tree ( ). The ITB
configuration window is displayed. Then, it would be possible to add and/or remove the AB that are
required.
Figure 21 – Local acquisition configuration in Easergy Builder.

For further information about the configuration and addressing procedure of the ITB, please refer to
Easergy Builder User Manual.

3.5.2 Distributed Local Acquisition

If local acquisition is distributed in several ITB’s in our system, you need to number each ITB in
order to identify them individually within the global system.
Figure 22 – Distributed local acquisition.

To indicate that it is a distributed system, you will check the “IP Expand” box in the local acquisition
window.

Pag 39
11/11/2019 User Manual – Saitel DR Platform

Figure 23 – IP expand configuration.

When the box on the left is checked, the following fields are enabled:

• AB: Indicates the Ethernet port through which all ITB’s communicate in the distributed system.

• Position: If you have more than one distributed system within the same network, you will
assign an identifier to the system you are configuring as to identify its modules uniquely in the
network.
With respect to the configuration of the local acquisition in Easergy Builder, and using If local
acquisition is distributed in several ITB’s in our system, you need to number each ITB in order to
identify them individually within the global system.
Figure 24 – Configuration of the local acquisition in a distributed ITB.

Each acquisition block is configured as if all were physically assembled on the same ITB.

3.5.3 Signal Identification - Coordinates

The coordinate is an unique identifier of a signal within a Device. Its definition is different for each
Device Controller and the local acquisition is defined with ten digits with the following format:
1 XXX YY ZZZZ
Where:

• 1: The first number of its coordinate for all local acquisition signals will be 1.

• XXX: Number that identifies the module. It will be the address obtained for the module through
AAP. The HU modules are associated to 000 and the AB modules are associated to 001
onwards, but if the control module is a HU_AF or HU120, it will use 001 and the ABs will use
002 onwards.

• YY: Type of signal, which includes:

o 00: Diagnostic signals.
o 01: Analog signal (signed 32-bit signal).
o 02: Simple digital input (1 bit).
o 03: Counter (32 bits).
o 04: Analog output (16 bits).
o 05: Simple digital output (1 bit).
o 07: Double digital input (2 bits).
o 08: Frequency meter.
o 09: Quick counter (32 bits).
o 15: Double digital output (2 bits).

• ZZZZ: Signal number within the acquisition block. The number ranges from 0000 to 9999. For
Diagnostic signals (YY = 00), then 0000  module´s communication state and 0001 
Module’s hardware state.

Pag 40
User Manual – Saitel DR Platform 11/11/2019

Example:
In coreDb we create a point to with the local acquisition signal (Device claq) with the coordinate
1005030002 is assigned as the source. It means that this coreDb point obtains its value from the
third signal (0002) of 32-bits counter type (03) in module number 5 (05) of the ITB.

3.6 ITB Initialization Process

The diagram below shows the different ITB states during the initialization process, based on the
LED indicators status. If the CPU does not initialize correctly, the diagram describes the actions to
solve it.
If the HU module has the software loaded and operates properly, the LED RUN will be on and blink
after the reboot.
Figure 25 – Description of the ITB initialization.

LED FAIL lighted during the initialization indicates that an error has been detected in the loaded
configuration files. It can also indicate that no files are loaded. In either case, the operator will need
to load a correct configuration file and reset.
If the LED FAIL is blinking in an AB, it means it has detected a fault in the EEPROM, which is
forcing the module out of service.
Once a correct configuration file is loaded, the LED DIO on the HU module should be observed. If it
is on, the operator will need to check if the acquisition modules addressing is correct. The bus
physical connection must be reviewed, including the module bridges, the expansion cables and the
terminations. Check again when the LED DIO is on.
Check if the problem is that the table of addressed modules does not match with the connected
modules (see paragraph 5.2 ).
In this case the operator will need to review:

• The physical bus connection, including the module bridges, the expansion cables and the
terminations.

• The physical arrangement must match the order specified in the table, that is, the type of each
module must match the position specified in the loaded configuration file.

• The configuration file related to the bin controllers, signals, references, etc.

Pag 41
11/11/2019 User Manual – Saitel DR Platform

If necessary, a new configuration is loaded, and the module is reset.

Once configured correctly, run the AAP procedure until all the modules appear as connected in the
table (see paragraph 5.2 ).

3.7 Treatment of Local Acquisition Signals

3.7.1 Introduction
The input/output information processing is performed between the acquisition module and the head
unit, which will be in charge of the data exchange with the real-time data base by means of the
internal data bus. The information processing consists of treating and adapting the inputs and a
conditioning of the field outputs.
Figure 26 – Data processing in the Head Unit

All the signals stored in the real-time database are associated to quality information. This
information is generated by the status controller block, which uses the following information to
generate the quality flag:

• Diagnostic information, which is transmitted to the head unit by the AB.

• Diagnostic information and internal bus status.

• Information generated by other processing blocks in the same head unit.

The status of each signal and its associated quality bits can be viewed from Saitel Webtool, as
described in the “Baseline Software Platform” manual.
The following sections explain the types of data that Saitel DR can manage through the acquisition
block. These sections also describe the information processing procedure and the quality
associated to the stored data.

3.7.2 Digital Inputs

Saitel DR can manage digital inputs with or without timestamp. In both cases, the values are 0 and
1.
The acquisition block transmits the signal’s value to the HU whenever it changes; it also attaches a
timestamp if using this type of signals.
The quality values associated to the signal’s values are:

• Invalid value due to a polarization failure.

• Locked signal.

• Invalid time; the module is not synchronized (only for signals with timestamp).

Pag 42
 User Manual – Saitel DR Platform 11/11/2019

The types of points managed by RTDB and that are defined in function of these digital inputs are:

• Single digital.

• Double digital.

• Slow counter.
The digital inputs processing received from the field devices includes the functions explained
below. Each processing will be applied or not depending on the type of point generated.
Digital Filtering
This function can be used to define the period of time during which a value change has to be
retained to be considered (filtering time or TF). If the change lasts less than the time specified in
the TF parameter, it will be ignored.

NOTICE
This functionality is applicable to all the points generated from digital signals, being single,
double or slow counters.

The following figure illustrates an example of the digital filter operation:

Figure 27 – Digital filtering

The filtering time can take from 0 to 255 ms.

Change Memory
The change memory can store the changes detected in the inputs for a specified period of time
(Memory time or TM).

NOTICE
It only applies to single and double points. If the TM parameter is set to 0, this function is
disabled.

The change memory response for a digital input is represented in the following figures.
Figure 28 – Change memory

The memory time can range between 0 and 2,550 ms.

Pag 43
 11/11/2019 User Manual – Saitel DR Platform

Inversion
It applies for single, double and counter signals. By using this mechanism, the input can be
configured as enabled when the value is “1” or disabled when the value is “0”.
Settling Time
This processing is applicable only for points configured as double digital signals. These points are
considered as valid when only one of the two signals is active, and invalid if both signals are active
or inactive.
When one of them is active, the transition to the other status must be done by disabling the active
signal and then enabling the other signal. Since these changes do not necessarily take place at the
same time, there is a timeout (settling time or TS) from the deactivation of one of the inputs to the
activation of the other. During this period, the system does not consider that the input status is
invalid, but it interprets it is under transition.
The following figure shows an example in which the TS does not expire, so the invalid status of the
input signals is ignored:
Figure 29 – Status validation for double signals (no TS expiration).

If the TS expired, coreDb will register the signals invalid state until a new change occurs:
Figure 30 – Status validation for double signals (TS expiration).

If the settling time is set to zero, this processing will not be applied.

NOTICE
The two inputs need to be fixed for that period. Otherwise, the time counter will resume
operation.

Pag 44
 User Manual – Saitel DR Platform 11/11/2019

Edge Configuration for Counters

It applies only for the signals defined as slow counters.
It allows configuring each slow counter as single or double counter. In the first case the counter is
incremented when a rising edge is detected in the input. However, the double counters are
incremented when both rising and falling edges are detected.

NOTICE
The maximum input signal frequency is 45 Hz.

Anti-chattering
It applies to single and double signals.
The anti-chattering processing function is to detect a determined number of changes in a specific
time interval. If the specified number of changes is exceeded throughout this observation time:

• The event related to the last change is registered.

• The signal’s chattering is indicated by means of a quality bit.

• Events stop being registered until no changes are detected in the signal during a specific
period of time.

NOTICE
Considered changes are the valid events after going through the filtering process, since the
anti-chattering processing is the last treatment of digital inputs.

The anti-chattering parameters are:

• Monitoring period or TCHAT. It is the period of time during which the number of changes
cannot be exceeded. This time can be defined from 0 to 255 seconds.

• Maximum number of changes or NCHAT. It is the maximum number of changes in the signal
during a TCHAT period. This parameter can be defined from 1 to 255 changes.

• Idle time or TIDLE. Once the signal is marked as chattering, it will return to its normal status
(normal event reporting) if during TIDLE time no changes are detected in the signal input. This
parameter is not configurable, and its value is always equal to TCHAT.
The figure below illustrates the anti-chattering processing diagrams:
Figure 31 – Verification of the number of changes during TCHAT.

The observation window slides over time:

Figure 32 – Observation window movement.

Pag 45
11/11/2019 User Manual – Saitel DR Platform

If the number of changes occurred in the interval matches the number defined in NCHAT, the
signal is marked as in chattering and following events are ignored:
Figure 33 – The signal is marked as in chattering.

The changes in the signal are continuously observed (but events are not generated).
Figure 34 – The signals switch to a normal status.

When the TIDLE time expires with no signal change detected, it is marked as in normal status, the
last change event is transmitted with its timestamp and events continue being generated normally.

3.7.3 Digital Outputs

Saitel DR can manage two types of output signals:

• Standard digital signal. These signals are triggered by a direct command. They can operate as
latched signals or with variable pulse time (pulsing).

• “Select Before Operate” digital signals. These outputs have a selection mechanism
implemented that prevents the execution of multiple commands simultaneously. They operate
as latched signals.

NOTICE
All modules with DO signals installed in the ITB can be configured exclusively as SBO or DO,
depending on the type of commands to be received.

Both types of digital outputs can be mapped to single or double signals in the coreDb, so the
following types of points are possible:

• Single pulsing output.

• Single latched output.

• Double pulsing output.

• Double latched output.

• Single SBO.

• Double SBO.

Pag 46
 User Manual – Saitel DR Platform 11/11/2019

NOTICE
• Please note that when a point is defined as double in the coreDb, the two field signals
to be wired must be contiguous and on the same acquisition block.
• IMPORTANT: When the ITB is operating under “Local” mode, all commands received
on the digital outputs are rejected. This is not applicable for analog outputs.

The digital outputs processing includes the following functions:

Pulse Time
The pulse time is only applicable when the point is defined as pulsing; it specifies the output
duration. It can be configured through the system’s parameter called Execution Time or ExeTime,
which indicates the time in millisecond units, although with an accuracy of 100 ms. Its value is
selectable from 0 to 65535, but it shoudn’t be configured below 10 ms.
SBO Command Lock (AB_DO, AB_DIDO, HU120 and HU_AF modules)
This functionality is applicable to all SBO commands, being single or double.
If a module is configured as SBO, the reception of two simultaneous commands is not supported.
In other words, if a command A is received with a pulse time T, the module will block the reception
of any other command until this time expires. When time T expires and command A is completed,
the module will admit the next received command.

3.7.4 Analog Inputs

Saitel DR allows managing analog input signals related to voltage, current, temperature, frequency
and, in general, any analog measurement which can be obtained through a physical device and/or
protocol.
To manage the information from field devices, different types of points can be defined in the
coreDb, such as:

• Standard analog measurement. It can manage 16-bit signed values (from -32,768 to 32,767).

• RTD measurement (PT100). It manages 16-bit unsigned values (from 0 to 65,535).

• Standard counter. It can manage 32-bit unsigned values (from 0 to 4,294,967,295).

• Frequency measurement. Alike the counter, it manages 32-bit unsigned values (from 0 to
4,294,967,295).
The first two types of signals, standard and RTD measurements, have a quality bit associated
which indicates whether the value is invalid due to a power supply failure. Besides this bit, the last
two types, counters and frequency measurements, have an additional quality bit to report any
discrepancy in the quadrature of input signals.
Moreover, before storing the information into the corresponding point in the coreDb, the system
performs the following processing only for the first two types of signals:
Input Range
It is possible to define in coreDb the input range for each analog input received from an AB. It even
allows defining a different range for the coreDb input with respect to the range generated by the AB
for the respective analog measurement.
The processing of the received analog measurement includes the value conversion to the range
defined in the coreDb.

Pag 47
 11/11/2019 User Manual – Saitel DR Platform

The figure below shows the range conversion:

Figure 31 – Converting input range to engineering units.

NOTICE
The analog input processing distinguishes between unipolar and bipolar input ranges.

Out-of-Range Detection
If the system detects that the value is higher or lower than the valid range, after the conversion to
engineering units (grayed area in Figure 9-10), it will be indicated in the signal quality flag with the
corresponding bit activation,
Digital Filtering
It applies a digital filtering to minimize the noise effects. The user can specify the filter parameters
using Easergy Builder.
Scaling to Engineering Units
This functional block can convert the analog measurement value expressed in field units to
engineering units (UI). The user defines the relation between two points within the field values
range and their corresponding values in the engineering units scale. Based on this relation, the
system defines the scaling formula which will be used to convert any field value within its valid
range to engineering units.
Cancellation of Values Close to Zero
This filter prevents unwanted changes in the signal. The user defines a range around the lower limit
for field values, and any input value within this range is interpreted as zero. The range around the
lower limit is defined by the user as a percentage of the input total range.
Range Checking
The user can define four alarm values associated to each signal: Very low, low, high, and very
high. Each value has an alarm flag associated which is transmitted as an input to the “status
controller” block.
Change Threshold
The user can define, by means of a parameter, a value expressed in engineering units that
generates a range within which the input signal will remain invariable. This filter allows the system
to ignore small changes in the signal current value.

Pag 48
 User Manual – Saitel DR Platform 11/11/2019

3.7.5 Analog Outputs

NOTICE
The ITB operation in “Local” mode does not affect the execution of analog outputs; only
commands (digital outputs) are discarded.

The processing of analog outputs consists of the following steps:

Figure 31 – Converting input range to engineering units.

Reset Value
The user must define the output reset value, that is, the output initial value after resetting the
acquisition block. This value is defined in a 16-bit signed range (between -32,768 and 32,767).
Maintenance
If the acquisition block is not in RUN status (LED Run is off) and maintenance is configured, the
analog output will retain the last value written to it, or the reset value otherwise.
Scaling to Field Values
This module performs the opposite process than the “Scaling to Engineering Units” in analog input
processing, that is, it converts the output value expressed in engineering units to its corresponding
field units.
Figure 31 – Scaling to field values.

The configuration of this scaling is the same as described for the processing of analog inputs in the
block “Scaling to Engineering Units”.

Pag 49
 11/11/2019 User Manual – Saitel DR Platform

Output range configuration

The user can define the output range for each analog output using Easergy Builder. If the
acquisition block's hardware supports multirange, it should be configured with a range as close as
possible to the user-defined range. In any case, the user can define a value range different to the
hardware range for each analog signal.

Pag 50
User Manual – Saitel DR Platform 11/11/2019

4 Physical Mounting & Installing

Pag 51
11/11/2019 User Manual – Saitel DR Platform

Contents

4 PHYSICAL MOUNTING & INSTALLING ................................................................ 51

4.1 ITB INSTALLATION ................................................................................................. 53

4.1.1 HANDLING MODULES ...................................................................................... 53
4.1.2 MODULES LOCATION IN THE ITB ...................................................................... 53
4.1.3 POWER SUPPLY REQUIREMENTS .................................................................... 54
4.1.4 MOUNT AND DISMOUNT PROCEDURES ............................................................ 54
4.2 EXPANDING THE ITB .............................................................................................. 55
4.2.1 TERMINATION MODULES (TU) ......................................................................... 55
4.2.2 TERMINATION MODULE (BT) ........................................................................... 56
4.2.3 EXPANSION MODULE (XU) .............................................................................. 57
4.2.4 WIRING EXPANSION........................................................................................ 57
4.3 WIRING RECOMMENDATIONS FOR EMC .................................................................. 58
4.3.1 WIRING TYPES ............................................................................................... 58

Pag 52
 User Manual – Saitel DR Platform 11/11/2019

4.1 ITB Installation

4.1.1 Handling Modules

While all electronic components are installed into their enclosure, they are protected for relevant
levels of electrostatic discharge.

WARNING
The enclosure shouldn’t be retired when isn’t necessary, because this action has a risk for the
equipment.

Please follow all recommendations indicated in paragraph 1.6

4.1.2 Modules location in the ITB

Saitel DR modules cannot be placed at any position in the ITB. Some of them, such as the head
unit, the termination (TU or BT), the expansion (XU) and the communications module (AB_SER)
must be installed in a specific position in the ITB.
HU Module
The HU must always be the first module in the ITB, that is, it must be mounted in the first position
of the first DIN rail, being the bus initiator in the ITB.
The HU can only be found in the second position of the DIN rail if the ITB requires processing
redundancy. In this configuration, there is a main DIN rail in which two redundant HU modules
(without ABs) are installe d and connected to the acquisition ITB (if they exist) by means of an
Ethernet network; the system’s bus is not used in this case (see Figure 19 for a configuration
example).

NOTICE
To minimize the adverse effects of noise and heat, it is recommended to install the ITB’s head
unit as far as possible from other modules handling alternating current and high voltages.

Communication Modules
AB_SER modules always must be installed next to the HU and only on the first row of the ITB.
Acquisition Blocks
The set of acquisition blocks, installed in each row, will always be placed between two termination
blocks. The type of termination block will depend on the row position within the ITB (HU, TU, XU or
BT).
Termination Modules (BT and TU)
While the BT module can only be used as a bus termination, the TU module can also be used in
combination with an expansion module to connect to the next rows of modules.
When installing an acquisition ITB, the bus termination module must be located at the end of each
DIN rail. The BT, if used, will be attached to the right BUS connector in the last AB of the ITB’s last
row. Figure 11 shows the use of a TU and a BT module.
Expansion Module (XU)
The bus expansion module will be mounted in the first position of each DIN rail (except for the first
one). It has two main functions:

• It expands the ITB’s primary bus to the modules installed in the same rail, so that it is
connected directly to the TU module in the previous row.

• It powers the modules in its row.

Pag 53
11/11/2019 User Manual – Saitel DR Platform

4.1.3 Power Supply Requirements

To calculate the ITB’s power supply requirements, you will need to consider the power
consumption of each module. The modules’ power consumptions must be added plus a safety
margin (min. 20%). Each row in the ITB is powered independently thought the HU (first row) or XU
(second and following rows) module.
In order to avoid ITB overload, the power supply performance should also be considered (typically,
70-90%).
The power consumption data is detailed in the technical specifications table of each module’s user
manual and in the technical label on the equipment.

4.1.4 Mount and Dismount Procedures

Before replacing a module, it is important to back up the configuration to help ensure no parameter
settings are lost.
Before removing a module, you must first:

• Switch off the power supply.

• Disconnect all cables, connectors, and Ethernet bridges from the modules.

DANGER
HAZARD OF ELECTRIC SHOCK, ELECTRIC ARC OR BURNS

• Only qualified personnel should install this equipment. Such work should be performed
only after reading this entire set of instructions and checking the technical
characteristics of the device.
• NEVER work alone.
• Turn off all power supplying this equipment before working on or inside it. Consider all
sources of power, including the possibility of backfeeding.
• Always use a properly rated voltage sensing device to confirm that all power is off.
• Start by connecting the device to the protective earth and to the functional earth.
• Screw tight all terminals, even those not in use.
Failure to follow these instructions will result in death or serious injury.

In order to power down the equipment, cut the power supply of the cabinet (either externally or via
the circuit breaker inside the cabinet) and disconnect the battery from the power supply module.
Once both these actions have been implemented, all LEDs on the ITB will be off. This indicates
that the Saitel DR cabinet is therefore powered down (off).
All Saitel DR modules have a DIN-rail bracket at the rear side that allows mounting on a DIN rail:
Figure 35 – Mount bracket on DIN rail.

The mounting procedure is described below:

• Switch off the power supply.

• Attach the module’s rear bracket on the upper DIN rail.

Pag 54
User Manual – Saitel DR Platform 11/11/2019

• Press the lower front panel gently until a click confirms that the bracket is fit on the rail.

• Verify that the module is anchored firmly to the rail, although lateral movement is possible.
Figure 36 – Saitel DR module on a DIN rail.

The module is dismounted, with the ITB unpowered:

Figure 37 – Using a screwdriver to dismount a module.

1. Using a flat-blade screwdriver (< 6 mm), pull down the tab that holds the module in place on
the DIN rail.
2. Tilt the module forwards to free it from the rail.
3. Pull the top of the module upwards to remove it from the rail.

4.2 Expanding the ITB

4.2.1 Termination Modules (TU)

TU is a Saitel DR complementary module allowing to use multiple rows in an ITB.
Figure 38 – TU module.

The TU module performs two main roles in the ITB:

Pag 55
 11/11/2019 User Manual – Saitel DR Platform

The Row Termination (BUS Expansion)

The ITB can be divided into several rows of modules (max. 4). All these rows require a TU module
to perform the BUS expansion functions to the next row (except for the last row in which the TU
module is the ITB termination).
If the module is not in the last row, the TU must be connected to the XU module in the next row by
using the J1 connectors (DB15) available at both modules. This connection expands all the internal
bus lines except for the ground and power supply lines. For a detailed description about this
connector, please refer paragraph 4.2.4 .
Additionally, the TU module integrates a resistor which allows using it as the BUS termination; in
this case the resistor must be disconnected. This resistor must only be connected if the TU module
is used as the ITB termination.
To disconnect this resistor, the TU module has two switches on the right top side, which must be
set to OFF, as shown in the figure below: TU module performs two main roles in the ITB:
Figure 39 – Switches to disconnect the TU resistor.

ITB Termination
The data bus requires resistors which operate as bus termination at both ends. The initial resistor is
installed at the HU and the final resistor at the TU module, if it is correctly configured.
To configure the TU as ITB termination, the switches shown in previous figure must be set to ON
(upper position). Thus, the bus termination resistor will be activated.

4.2.2 Termination Module (BT)

BT only can be used in the last row to finish the bus. It allows finishing the ITB without having to install a
TU module.

Figure 40 – BT module.

The only function of this module is to act as a bus termination, so it will be installed in the output
connector of the bus expansion (right connector) of the last module in the ITB.
Figure 41 – BT module connection.

NOTICE
Please note the module’s orientation must be exactly as shown in the figure, that is, the BT
connector must be installed on the right and that it should not stick out of the module’s
enclosure.

Pag 56
 User Manual – Saitel DR Platform 11/11/2019

4.2.3 Expansion Module (XU)

The XU module, used in combination with a TU, allows making an ITB with multiple rows.
Figure 42 – XU module.

The XU module performs two main functions in the ITB:

Bus Expansion
The data bus is expanded through a cable which goes from the TU J1 connector (DB15) in the
previous row of the ITB, to the XU J1 connector (DB15).
The XU module gathers the data obtained from the TU module with the power supply and ground
connection and transmits everything to the rest of the ITB by means of the BUS connector on the
right side.
Power Supply of Row
XU module has a power supply input (B1 terminal block) to connect a 24 or 48 VDC (depending on
ordering option) ±20% power supply. This power input allows to power the rest of the modules in
the row where it is installed.
The B1 terminal block wiring, being the power input, is as follows:
Figure 22 – XU power input wiring.

4.2.4 Wiring Expansion

The J1 connector in the module TU is used to expand the bus to the next rows in the ITB. A cable
will connect this point to the DB15 male connector in the XU module, which has a typical
impedance of 120 Ω and it must be shielded.
At both end of this cable must be installed a female DB15 connector as follow:
Figure 43 – TU and XU connector for expansion.

Pag 57
11/11/2019 User Manual – Saitel DR Platform

NOTICE
The maximum length of the expansion cable is 1.5 m.

Both connectors in XU and TU are male and it has the following pin-out:
Figure 44 – TU and XU connector for expansion.

WARNING
The shielded of the cable must be connected to earth welding the shield to the metallic
enclosure of the connector.

4.3 Wiring recommendations for EMC

To improve the EMC behavior of the equipment, it is recommended to follow the following
indications in the wiring of the ITB.

4.3.1 Wiring Types

The field connection of all ABs is done by using screw terminals.
Considering the wiring types which could be used, there are five different groups:
Table 4 – Wiring groups:

Group Connection type

1 Analog signals field cabling.
2 Digital signals field cabling.
3 Communications signals cabling.
4 Power supply cabling (electronic, signal polarization and auxiliary).
5 Protection cabling (earth, human protection and EMC).
4.3.1.1 Group 1, 2 & 3 (Digital, Analog and Communication Signals)

Common Recommendations
With respect to the wiring of all these signals, it is very important to take the following
recommendations into account:

• Whenever possible, the cables from different groups should be wired separately. That is,
analog signals, digital signals and communication signals require three separate conduits.

• If separate wiring is not possible and the number of signals is reduced, this conduit can be
exceptionally shared. In this case, as analog and communication signals are the most
sensitive, these two signals should be wired through the same conduit, whereas digital signals
should be wired separately.

Pag 58
 User Manual – Saitel DR Platform 11/11/2019

• If separate conduit is not possible, it is extremely important to prevent analog, digital and
communication signals to be wired in parallel.

• If there are some sections in which parallel wiring cannot be avoided, these sections should be
as short as possible and at least, 5 centimeters apart.

• If cable needs to be crossed, these crossings should be perpendicular to each other.

• In order to increase protection in field inputs and outputs, the terminal blocks are normally used
for reinforcing the protection barrier. The power supply and protecting terminal blocks of DI,
DO, AI and AO are protection barriers. The input wiring to these elements must always be
separated from the output wiring of these barriers. They shall never share the conduit

NOTICE
Analog, digital and communication signals should never share the conduit with the power supply
cables of the electronic and auxiliary components.

Analog Signals
Analog signals must always be wired with shielded cables. The protection shield is connected to
the ground using the last pin (to the right) of the terminal block.
Figure 45 – Analog signals wiring.

For AI and AO signals, it is recommended to install a ferrite (model WÜRTH 74270062) with 2 turns
of the wire.
Digital Signals
The DI and DO signals connection shall be treated in the same way as the analog signals.
For these signals, it is recommended to install a ferrite (model WÜRTH 74270062) with 1 turn of
the wire.

NOTICE
Field input signal cables must never be laid jointly with cables for filtered signals.

Communication
When using shielded cables (sharing conduit), the wire netting shall be connected to only one end
of the cable.
It is recommended to install the following ferrites:

• RS-485 communications: Model WÜRTH 74271722, with 1 turn.

• Ethernet communications: Model WÜRTH 74271221 with 2 turns.

Pag 59
11/11/2019 User Manual – Saitel DR Platform

4.3.1.2 Group 4 (Power Supply)

The power supply for the electronic elements is the main barrier between the existing disturbances
in the power supply line and the system. That is why the power supply must include some
additional filters for a good electromagnetic behavior of the system. It is extremely important to
keep the filter’s input wiring independent from the output wiring.
The polarizing sources output has the same route as the digital signals for which this polarization is
used, so it should be treated as a field input/output. In some projects supplementary filters are
installed. In these cases the wiring should be independent for the filter’s input and output.
Figure 46 – Main power and polarization wiring.

The polarization and main power do not feature any galvanic connection to Saitel DR, so they
should be sufficiently separated from each other (independent conduits and layout) in order to
prevent possible disturbances to reach the equipment’s wiring.
It is very recommended to install supplementary filters (Recommended model: FIL1B of Schneider-
Electric), and the wiring should be independent for the filter’s input and output.
The polarizing power supply should never be combined with the power supply for the electronics.
Under no circumstances, shall the protection filter be shared, since the polarization power supply is
connected to the field with the rest of the I/O signals. As shown in the following figure, a wrong
connection of the polarization power supply reduces the effect of the protection barriers.
Figure 47 – Wrong connection of the polarization power supply.

4.3.1.3 Group 5 (Ground Connection)

Use cables with enough section according to the safety standards. Use twisted pair or wire netting
whenever possible.
The equipment or cabinet needs to have a ground wire in a given point in order to guarantee low
impedance for the rest of elements. Horizontal copper bars shall be installed, as well as vertical
copper bars, whenever possible. All the metal pieces in the equipment shall be connected to the

Pag 60
User Manual – Saitel DR Platform 11/11/2019

protection earth. If metal cabinets are used, the cabinet’s walls can be also used to distribute the
ground.
Figure 48 – General scheme of a correct ground connection.

All connections shall be as short as possible, must be established through a dedicated cable and
connected to the cabinet main ground connection bar.

WARNING
A “cascading” ground connection of the elements is not allowed, as the ground disconnection of
one element would leave other elements within the cabinets without a ground connection.

Previous figure shows a correct connection, in which all metal elements are connected through a
dedicated cable to the ground-connection bar. In figure below, the two ground connection cables
are attached to simplify the connections, showing an incorrect connection.
Figure 49 – General scheme of an incorrect ground connection.

It is very important that ground-connection cables are as short as possible. For that reason, the
entire cabinet metal surface should be used for the connection.

Pag 61
11/11/2019 User Manual – Saitel DR Platform

The electronic elements with metal coating, such as power supplies, must be connected to ground
in two points. Firstly, they are connected to the protection earth using a cable with enough diameter
(according the safety standars) linking the ground terminal and the ground-connection bar.
Secondly, there is a second cable linking the ground terminal to the closest metal surface.
It is recommended to use flexible twisted cables for mobile ground parts (such as the cabinet’s
doors). The ground twisted cables must be short but with a wide surface (the surface is an
essential value in order to reduce high-frequency disturbances).

Pag 62
User Manual – Saitel DR Platform 11/11/2019

5 Configuration & Maintenance

Pag 63
11/11/2019 User Manual – Saitel DR Platform

Content

5 CONFIGURATION & MAINTENANCE .................................................................... 63

5.1 GETTING STARTED ................................................................................................ 65

5.2 ITB ADDRESSING (AAP) ........................................................................................ 65
5.3 REDUNDANCY ........................................................................................................ 67
5.4 WORKING WITH SAITEL DR IN EASERGY BUILDER .................................................. 68
5.4.1 ADDING AN RTU ............................................................................................. 68
5.4.2 READING THE CONFIGURATION FROM THE HU ................................................. 70
5.4.3 CREATE A NEW CONFIGURATION .................................................................... 70
5.4.4 TRANSFERRING THE CONFIGURATION ............................................................. 72
5.5 CHANNEL CONFIGURATION .................................................................................... 72
5.5.1 LINK CONFIGURATION ..................................................................................... 72
5.6 SYNCHRONIZATION ................................................................................................ 73
5.7 COMMUNICATIONS ................................................................................................. 74
5.8 SEQUENCE OF EVENTS (SOE)................................................................................ 74
5.9 FORMULAS ............................................................................................................ 75
5.10 PLC CONFIGURATION ............................................................................................ 75
5.11 CONFIGURING LOCAL ............................................................................................ 75
5.12 SUPERVISION ......................................................................................................... 76

Pag 64
 User Manual – Saitel DR Platform 11/11/2019

5.1 Getting Started

There are several elements the user should be familiar with when working with the RTU.
• Installing and utilization of Easergy Builder in our PC: It is recommended to check the “Easergy
Builder user manual”, that describes the installation process and the use of this tool.
• Utilization of webTool (for HU_A and HU_AF) or webApp (for HUe): To learn how to use the
web server, it is recommended to check the webTool or webApp user manual.
• Saitel DR modules: All details of wiring, configuration and utilization of the different modules
that could be added to an ITB can be checked in the user manuals of all those modules.
The HU is provided with a basic configuration, which will help you have a first contact with the
system. To get started, you need to know following data:
Default IP addresses
Depending on the CPU type, the IP addresses are:
Table 5 – Factory default IP addresses.

CPU Port IP Mask

ETH1 172.19.5.123 255.255.255.0

HU_A / HU_AF
ETH2 172.19.6.123 255.255.255.0
MNT 192.168.2.1 255.255.255.0
HUe LAN1 10.1.1.1 255.0.0.0
LAN2 192.168.1.1 255.255.255.0

User
Default users are depending on the CPU type too.
Table 6 – Default users.

CPU User Password Description

HU_A / HU_AF target password Default user for installation and administration.
HUe Installer Installer1! Default user to use while you are installing the RTU

When configuring the CPU, other users could be added (more information in the user manual for
each HU).

5.2 ITB Addressing (AAP)

In the ITB, each acquisition or communication block must be identified with a number. This number
is assigned with Easergy Builder when the local acquisition is configured (see 5.12 section).
Once the local acquisition has been configured and transferred to the RTU, it’s necessary to
address also those modules while they are in operation. To do that, the AAP (Automatic
Addressing Procedure) procedure creates a table in which acquisition blocks mounted in the ITB
are related with their address and type. The physical system has to match with the system that has
been configured in Easergy Builder.

Pag 65
 11/11/2019 User Manual – Saitel DR Platform

NOTICE
For AAP to be executed, at least one configuration must be loaded in the RTU, and it should
match with the physical modules installed in the ITB. To learn how to define and load a
configuration in the RTU by using Easergy Builder, it’s necessary to check 5.4 section.

AAP must be executed under the following circumstances:

• When the ITB is initialized for the first time, after the configuration is transmitted to the RTU
with Easergy Builder.

• When a physical change is made to the ITB:

o When a module is replaced with another module (the same or different type).
o When the module position is rearranged.
o When a module is added or removed.
The AAP can be executed automatically or manually by an operator.
Automatic Execution
Using a combination of switches in the CPU (consult the CPU’s user manual) the AAP procedure
can be executed automatically when the module restart. This AAP is necessary to update the
RTU's table of modules which have been configured in Easergy Builder.
Each time the CPU is rebooted, at the end of the booting process the APP will be executed,
showing the information of all the modules that are installed and configured.
Figure 50 – Example with messages generated once AAP has finished.

When any of the acquisition blocks configured in Easergy Builder are not properly addressed
(“SUCCESSFUL!” message is not displayed on the console), RUN LED of the module does not
blink and the DIO LED keeps lit.
When the configuration in the CPU is stable, it is recommended to deactivated the automatic
execution of AAP using the CPU’s switches.
Manual Execution
Anytime the user could force the addressing of the modules.

NOTICE
For AAP to be executed, the CPU’s switch that allow this operation must be in ON position.
Consult the CPU’s user manual to identity the correct switch.

For manual AAP execution, next steps need to be followed:

• In the console, it’s necessary to execute the “claqStartAAP” command to run the procedure
and the “LAQ_StartAAP: Running AAP....please wait” message will appear until the end of the
process. For communication blocks, the command would be “MUX_startAAP” instead.
Afterwards, the screen will show the information about each node, such as the type, address,
and serial number.

• It’s necessary to check that all modules appear on the console and that “SUCCESSFUL!” is
indicated for each one of them.

Pag 66
 User Manual – Saitel DR Platform 11/11/2019

• To finish the procedure, one of the following commands has to be executed:

o claqTableAck: It confirms that the table with the data is correct, so it will be registered
permanently and applied from that moment on. As result of this command, a message
will appear to inform that the content of the list of modules has been modified.
o claqTableNack: The operator informs the system that the table with the data is not
valid, and therefore should not be applied. In this case, there are two options: the APP
can be executed again and the result of the claqTableAck command is confirmed, or
the ITB is completely reset so that it can have a valid addressing. The second option
would allow the ITB to restore the addressing tables before the AAP was executed.
o claqStartAAP: The AAP is re-executed, so addresses are reallocated for each node.
From this moment, the RTU will be ready to be initialized and switch to data exchange mode if the
application software has already been loaded. Otherwise, the software will have to be updated as
well.
Figure 51 – Example of manual AAP execution.

NOTICE
Addresses that have been obtained from the AAP must match the ones configured with Easergy
Builder.
Whenever a minor or major change is made to the ITB, the addressing procedure should be
executed. Moreover, prior to this addressing procedure, it’s necessary to check that the
configuration loaded into the RTU is correct with respect to the current condition of the ITB.
Until the claqTableAck command is not executed, information won’t be recorded permanently.

5.3 Redundancy

A Saitel DR RTU can be configured using two HUs controlling the system. There are some
differences in the configuration, for example, environment variables and supervision points.
Moreover, you have to define how redundancy will be implemented both in physical terms (control
mechanism) and functional terms (data redundancy mode).
To do so, you need access the dbRED tab in coreDb.

NOTICE
The dbRED section is only available in Easergy Builder if you have defined the CPU as
redundant.

Control mechanism
For Saitel DR only RCAP protocol (Redundancy Control Asynchronous Protocol) is available.
It consists of a redundant channel between the two HU modules that is switched when required by
means of a Schneider Electric proprietary protocol.

Pag 67
11/11/2019 User Manual – Saitel DR Platform

To implement this control mechanism, you can configure up to two different channels which are
used redundantly to obtain a fault-tolerant redundancy control:

• Through network ports. You need to define the IP addresses for CPU A and CPU B.

• Through a serial channel. You need to indicate the serial port you will use in both CPU’s.
Mode
There are two different modes to implement redundancy:

• Cold redundancy: The databases in both CPU's are NOT synchronized. When switching, the
other CPU will initialize with its own database using default values.

• Hot redundancy: You must define a high-speed communication channel (Ethernet) between
the two CPU’s to keep the database updated in the backup CPU. When switching, the
redundant CPU will initialize with updated values.

NOTICE
When using the “Hot redundancy” mode, the names of the points in both databases must be
identical, that is, it is very important to use the SAME Easergy Builder configuration in both
CPU’s.

The backup CPU's database is updated when exceptions are thrown (i.e. only the modified points
are updated), except for the initialization after which the entire database is updated. The
DB_UPDATE supervision point allows us to monitor the process.
Additional IPs
You can define a list of IP addresses related to the HOT CPU. These addresses are dynamically
associated, so that in redundant systems they can always communicate with the online CPU at the
time.

NOTICE
If you define a static IP address and a virtual address for the same device in the same subnet, a
warning console message will be displayed to inform about an anomalous situation
(sup_redAddIPs: dev xxx ip x.x.x.x subnetMask xxxxxxxx).

The message is an operating system warning, even though it will not cause a malfunction.

5.4 Working with Saitel DR in Easergy Builder

NOTICE
To perform the operations described in this chapter, the user must be familiar with the Easergy
Builder tool. Otherwise, please, refer to the tool's user manual.

5.4.1 Adding an RTU

Press button or right-click on the RTU tree to add a new RTU by entering the required
information in following fields:

Pag 68
User Manual – Saitel DR Platform 11/11/2019

Figure 52 – New RTU.

• Name: RTU name. The length can’t exceed 64 characters and can’t contain the characters
\, /, :, *, ?, “, <, > or |). The tree hierarchy will display a RTU identified with that name.

• Description: RTU’s description. This field is optional and can be 128 characters long
(optional).

• Type: Type of Saitel DR HU, for example HU_A.

• AB_SER: Number of the communication modules installed in the RTU. These modules are
not shown in Easergy Builder, even though its communication channels are available for
use.

• Redundancy: This field must be checked when the RTU is controlled by two redundant
CPU’s.

• Define default acquisition: If this box is checked, every time a configuration is created for
this RTU, you will add a series of default acquisition modules. These selectable modules
are specified below.
The previous parameters are assigned as default values in each Configuration created for this
RTU.
For example, if you check the “Define default acquisition” box, all the acquisition modules included
in this RTU will also be included in its corresponding Configurations. Moreover, the ITB
configuration window is displayed where you include the RTU's acquisition block:
Figure 53 – Configuring the ITB

You can also access and change this default configuration by clicking the button next to the
ITB figure.
Build the ITB using the buttons on the upper part of the screen.

Pag 69
11/11/2019 User Manual – Saitel DR Platform

You must take the following factors into account:

• The Addr field is the number associated to an acquisition block inside the ITB. This number
must be unique for each AB and will be used to identify both the AB and its points. The user
can change the associated address by selecting the module and using the buttons. If you
select the “Auto Address” box, when reordering the modules physically or when modifying the
ITB, all addresses are reassigned automatically. The address 1 is assigned to the closest AB to
the HU module. If the “Automatic Address” is unchecked, the modules retain the assigned
address ignoring the changes made to the ITB.

• The Automatic Addressing Procedure (AAP) must be performed every time the ITB structure
changes, that is, every time a module is added, deleted or replaced from the ITB. These
procedure can be launched both manually, using the Console or Easergy Builder, or
automatically by using the correct switch in the HU module (consult the HU user manual).
The RTU is ready for creating the different configurations with which you will work later on.

5.4.2 Reading the Configuration from the HU

If the HU module was not built-in from the factory, you might want to read the loaded configuration.
Once this configuration is read and loaded in Easergy Builder, you can edit it to make the
necessary modifications which will be resent to the CPU with the modifications.

NOTICE
We recommend backing up the original configuration in the RTU in order to restore the CPU to
its original state at any time. To back up the security configuration, select the RTU from the tree
and generate an EBR file by clicking the button. This file will include all the settings for that
RTU. If you only want to save a copy of the configuration, select the specific configuration from
the tree and click the same button. In this case, an EBC file is generated, which only includes the
selected configuration.

To load the existing configuration in the HU, it’s necessary to follow next steps from the Easergy
Builder Workspace.

• In the RTU tree, the RTU to which the new configuration will be associated has to be selected.
If there is no configuration, a new one has to be loaded. The HU needs to have configured an
IP address so it’s possible to communicate with it.

• Once the “Read Configuration” button ( ) is pressed, the user would need to introduce a user
and password.

• It’s necessary to choose the information to be loaded: “Network”, “Environment Variables”

and/or “Configuration”.

• In case that “Configuration” has been chosen, it will be necessary to choose a name for it. After
that, the configuration would appear available in the RTU tree. If “Environment Variables” and
“Network” were selected, the RTU will take the values defined in the HU that is being read.

5.4.3 Create a New Configuration

This section shows how to can create a new configuration using Easergy Builder.

Select the RTU and press button :

Figure 54 – New configuration addition.

Pag 70
User Manual – Saitel DR Platform 11/11/2019

Write the name of the new configuration.

If the RTU was created with an acquisition configuration by default, for a new configuration you can
select the field “Create defined RTU acquisition points” in order to include all points of the pre-
defined I/O modules in coreDb.
For example, for the RTU created in the previous paragraph, this configuration will include an
AB_DI, an AB_DO, an AB_AI and two AB_AO modules. If “Create defined RTU acquisition point” is
checked, their corresponding points will be created in coreDb. Then, the new configuration would
be available for the RTU.
Figure 55 – New configuration details.

Double clicking on the configuration will switch to Configuration mode, where the new configuration
can be edited.
Figure 56 – Configuration mode.

By right-clicking on the configuration name, a contextual menu is displayed:

Figure 57 – Contextual menu for Configuration.

Pag 71
11/11/2019 User Manual – Saitel DR Platform

This menu allows:

• Add, remove or modify a configuration.

• Create a template with the information associated to this configuration.

• Change the name or description of the Device (description field allows 128 characters
maximum).

5.4.4 Transferring the Configuration

To transfer the configuration from Easergy Builder (in the PC) to the CPU, if configuration mode is

active, select button . If Workspace mode is active select button . Then,

you are prompted to confirm the project save operation. Press “Yes” and the log window will
display the information about the operation progress.
Finally, reset the RTU and, if no problem occurs, the console will display the information about the
initialization progress of operating system and then the application. If everything is correct, the
message “CONF OK” should be shown in the console.

5.5 Channel Configuration

In the Easergy Builder Manual you can find the general operations that are necessary to know to
create and edit the communication channels available in the CPU and communications modules.
In Configuration mode, select Channels tab in order to access channel management window.
Figure 58 – Module management window.

NOTICE
The CON port cannot be used for communications, and that is why it is not necessary to
include it in the channel list.

Consult the user manual of you CPU to know all available channels.
Apart from those, depending if you have an AB_SER module, the serial channels for these
modules are also listed: AB_SERx-COM1..AB_SERx-COM4, being x the AB_SER module number.
Please refer to the Easergy Builder manual to obtain further details about how to create and define
parameters for communication channels.

5.5.1 Link Configuration

Some Devices support double channel management. This functionality can be different depending
on the protocol in use. A link is the association of two channels; you can also understand it as a
double channel.

Pag 72
User Manual – Saitel DR Platform 11/11/2019

To configure a channel, in the window displayed above, select “Link” and indicate the two channels
that will be associated to create the link; you will also define the operation mode and the link test
time:
Figure 59 – Link configuration window.

5.6 Synchronization

The factory configuration does not include a defined Synchronization Device. The configuration
source is defined in Easergy Builder. webApp only allows changing the configuration once it has
been previously defined with Easergy Builder.
For HU, you can define two synchronization channels: a primary channel and a secondary channel,
which will be used when the primary channel is not available
Figure 60 – Synchronization configuration.

Depending on the CPUThe synchronization sources to be used with HUe are:

• PROTOCOL: Time is received through a user-specific protocol. Most telecontrol protocols

enable slave devices to be synchronized.

• SNTP: The remote unit will operate as a SNTP client; therefore you will need to indicate the
SNTP server's IP address and the synchronization period through that server.

• IRIG: The time received from the IRIG device is used to set the system’s clock and RTC. The
configurable formats are: IRIG-B002, IRIG-B003, IRIG-B006, and IRIG-B007.

NOTICE
If the HUe is configured as IRIG-B server, an AB_SER module witn external polarization
(M56720000yZZ) must be included in the firt row of the ITB. The IRIG-B signal is sent to the
client devices through COM ports of this AB_SER.

Pag 73
11/11/2019 User Manual – Saitel DR Platform

• GPS: GPS35 and GPS16 of Garmin have been validated.

• PTP: As indicated in the IEEE-1588 standard, a PTP master will synchronize the accessible
slave PTP devices through one or multiple Ethernet interfaces.

• Console, using the commands:

o thmShow: It displays the states of the synchronization devices and the
information about current time and date.
o thmConsoleSetTime “YY:MM:DD:HH:NN:SS”:It configures the date and
time manually.
Moreover, the HUe module can be configured as a Simple Network Time Protocol (SNTP) server,
as a master PTP or as a IRIG-B server.
For further details about synchronization configuration, please refer to the Easergy Builder user
manual.

5.7 Communications

The default configuration does not include any communication Device, since this functionality
depends on how the RTU will be used in the system.
When you select a type of HU for your RTU in Easergy Builder, only available Devices for this type
of CPU will be shown.
Each Device has a dedicated user manual which detail all configuration parameters.

5.8 Sequence of Events (SOE)

HU includes a Sequence of Events file that registers the events produced in the RTU. This
functionality must be configured by the user, with the Easergy Builder tool.
Figure 61 – SOE configuration

For additional information about how to configure the SOE, please refer to the Easergy Builder user
manual and SOE manual

Pag 74
User Manual – Saitel DR Platform 11/11/2019

5.9 Formulas

coreDb signals can be associated to a series of functions such as: mathematic operations, logical
operations or event triggering. All these functions are implemented and controlled by the Formula
Device available in Easergy Builder.
In Easergy Builder user manual, you can find all the details about the use of this Device, as well as
available functions.

5.10 PLC Configuration

The HUe module integrates the use of ISaGRAF®, that is, a logic programming tool working under
the IEC 61131-3 environment to develop PLC programs.
ISaGRAF® is a third party tool consisting of two parts:

• Runtime: Control and execution environment for logic programs. The licence is included as part
of the Baseline Software Platform installed in the HUe module.

• Workbench: Development environment. It is installed in a PC, and needs to be purchased for

the project, since it requires an additional license that is not included as part of our software
platform.
The logic programming languages include:

• SFC: Sequential Function Chart

• FBD: Function Block Diagram

• LD: Ladder Diagram

• ST: Structured Text

• IL: Instruction List

To let ISaGRAF® interact with coreDb, you need to define a Device of this type in Easergy Builder.
For detailed information about the use of ISaGRAF® inside Saitel, please refer to the Device user
manual.

5.11 Configuring Local

As mentioned before, the local acquisition Device for Saitel DR is named “claq” and it is created by
default for each Saitel DR configuration.
Figure 62 – Configuring local acquisition for Saitel DR.

For HU_A the following types of modules can be configured:

Pag 75
11/11/2019 User Manual – Saitel DR Platform

Figure 63 – Available Saitel DR modules in Easergy Builder.

Back in the local acquisition configuration, several options are possible:

• button, to add a new module.

• button, to remove a module.

• buttons, to change the address of the modules.

• button, to create in coreDb acquisition and diagnostics points for all included modules.

For more information, you can look at the claq in the manual of the different acquisition modules.

5.12 Supervision

The Supervision Device is a default Device in Easergy Builder. The Device is used to monitor the
status of CPU's components and generates information about other components in the RTU.
You can double click the “Supervision” Device in the tree to see a complete list of all the concepts
you can monitor in this type of CPU:
Figure 64 – Supervision points for the HU.

Pag 76
User Manual – Saitel DR Platform 11/11/2019

It is always advisable to load the supervision Device, which is required to monitor the mentioned
elements of the CPU and essential in redundant configurations. The CPU itself cannot arbitrate
with another CPU in redundant systems, so there must be a monitoring part. Currently, only the
supervision Device can do these tasks, and in practice only this Device is used.
For redundant configurations, most of the supervision points are also available with “_A” and “_B”
suffixes in order to provide CPU-related information. For example, the points PS1_V, PS1_V_A,
and PS1_V_B are available for power supply voltage. Regardless which CPU is in online mode,
you can know the information about both CPU’s.
The information generated by the monitoring module is supplemented with the control and
diagnostic information generated in each Device.

NOTICE
For supervision device, the coordinates are the points name. For example, the coordinate
associated to the FAIL_PLC point is "FAIL_PLC".

WARNING
Depending on the RTU type, available points are different. Supervision signals for each CPU are
included in its user manual.

Pag 77
 11/11/2019 User Manual – Saitel DR Platform

Index of Figures
Figure 1 – Barrier of protection for elements with dangerous voltages. ....................................................................10
Figure 2 – Yellow and Green cable for earthing. .......................................................................................................12
Figure 3 – Terminal for functional earth (EMC). ........................................................................................................12
Figure 4 – Example of earthing for EMC. ..................................................................................................................12
Figure 5 – Technical label..........................................................................................................................................14
Figure 6 – Saitel DR. .................................................................................................................................................18
Figure 7 – Saitel DR module......................................................................................................................................19
Figure 8 – Connection between modules ..................................................................................................................19
Figure 9 – LED indicators ..........................................................................................................................................19
Figure 10 – Basic ITB ................................................................................................................................................23
Figure 11 – Saitel DR Architecture. ...........................................................................................................................24
Figure 12 – TU-XU connection. .................................................................................................................................25
Figure 14 – Communication between the CPU and acquisition blocks. ....................................................................26
Figure 16 – microRTU. ..............................................................................................................................................28
Figure 17 – Small / Medium RTU. .............................................................................................................................29
Figure 18 – Large RTU with distribute acquisition. ....................................................................................................29
Figure 19 – Distributed acquisition and control system / processing redundancy. ...................................................30
Figure 20 – Baseline Software Platform. ...................................................................................................................34
Figure 21 – Relation between coreDb and other applications...................................................................................34
Figure 22 – Interfaces with coreDb. ...........................................................................................................................36
Figure 23 – Local acquisition configuration in Easergy Builder. ................................................................................39
Figure 24 – Distributed local acquisition. ...................................................................................................................39
Figure 25 – IP expand configuration. .........................................................................................................................40
Figure 26 – Configuration of the local acquisition in a distributed ITB. .....................................................................40
Figure 27 – Description of the ITB initialization. ........................................................................................................41
Figure 28 – Data processing in the Head Unit...........................................................................................................42
Figure 29 – Digital filtering .........................................................................................................................................43
Figure 30 – Change memory .....................................................................................................................................43
Figure 31 – Status validation for double signals (no TS expiration). .........................................................................44
Figure 32 – Status validation for double signals (TS expiration). ..............................................................................44
Figure 33 – Verification of the number of changes during TCHAT............................................................................45
Figure 34 – Observation window movement. ............................................................................................................45
Figure 35 – The signal is marked as in chattering. ....................................................................................................46
Figure 36 – The signals switch to a normal status. ...................................................................................................46
Figure 37 – Mount bracket on DIN rail. ......................................................................................................................54
Figure 38 – Saitel DR module on a DIN rail. .............................................................................................................55
Figure 39 – Using a screwdriver to dismount a module. ...........................................................................................55
Figure 40 – TU module. .............................................................................................................................................55

Pag 78
 User Manual – Saitel DR Platform 11/11/2019

Figure 41 – Switches to disconnect the TU resistor. .................................................................................................56

Figure 42 – BT module. .............................................................................................................................................56
Figure 43 – BT module connection. ...........................................................................................................................56
Figure 44 – XU module. .............................................................................................................................................57
Figure 45 – TU and XU connector for expansion. .....................................................................................................57
Figure 46 – TU and XU connector for expansion. .....................................................................................................58
Figure 47 – Analog signals wiring. .............................................................................................................................59
Figure 48 – Main power and polarization wiring. .......................................................................................................60
Figure 49 – Wrong connection of the polarization power supply...............................................................................60
Figure 50 – General scheme of a correct ground connection. ..................................................................................61
Figure 51 – General scheme of an incorrect ground connection. .............................................................................61
Figure 52 – Example with messages generated once AAP has finished. .................................................................66
Figure 53 – Example of manual AAP execution. .......................................................................................................67
Figure 54 – New RTU. ...............................................................................................................................................69
Figure 55 – Configuring the ITB.................................................................................................................................69
Figure 56 – New configuration addition. ....................................................................................................................70
Figure 57 – New configuration details. ......................................................................................................................71
Figure 58 – Configuration mode. ...............................................................................................................................71
Figure 59 – Contextual menu for Configuration.........................................................................................................71
Figure 60 – Module management window.................................................................................................................72
Figure 61 – Link configuration window. .....................................................................................................................73
Figure 62 – Synchronization configuration. ...............................................................................................................73
Figure 63 – SOE configuration ..................................................................................................................................74
Figure 65 – Configuring local acquisition for Saitel DR. ............................................................................................75
Figure 66 – Available Saitel DR modules in Easergy Builder....................................................................................76
Figure 64 – Supervision points for the HU.................................................................................................................76

Pag 79
 11/11/2019 User Manual – Saitel DR Platform

Index of Tables
Table 1 – Symbols ........................................................................................................................................................9
Table 2 – Hardware and database limits depending on the HU .................................................................................25
Table 3 – Software compatibility .................................................................................................................................37
Table 4 – Wiring groups:.............................................................................................................................................58
Table 5 – Factory default IP addresses. .....................................................................................................................65
Table 6 – Default users...............................................................................................................................................65

Pag 80
User Manual – Saitel DR Platform 11/11/2019

Glossary
A
A: Ampere.
AAP: Automatic Addressing Procedure.
AB: Saitel DR Acquisition Block.
AB_AC: Direct measurements Acquisition Block.
AB_AI: Analog Inputs Acquisition Block.
AB_AO: Analog Outputs Acquisition Block.
AB_DI: Digital Inputs Acquisition Block.
AB_DIDO: Digital Inputs and Outputs Acquisition Blocks.
AB_DO: Digital Outputs Acquisition Blocks.
AB_MIO: Multiple Inputs and Outputs Acquisition Block.
AB_SER: Communication module for expansion.
AC: Alternate Current.
AI: Analog Input.
AO: Analog Output.
AWG: American Wire Gauge.

B
Bps: Bits per second.

C
ºC: Celsius degree.
COM: Puerto de comunicaciones.
CPU: Central Processing Unit.
CTS: Clear to Send.

D
DC: Direct Current.
DI: Digital Input.
DIN: Deutsches Institut für Normung.
DO: Digital Output.
DRAM: Dynamic Random Access Memory.

E
EMC: ElectroMagnetic Compatibility.
EPROM: Erasable Programmable Read Only Memory

Pag 81
11/11/2019 User Manual – Saitel DR Platform

F
FTP: File Transfer Protocol.

G
g: Gram.
GPS: Global Positioning System.

H
HU: Head Unit. Saitel DR CPU.
HU_A: Saitel DR Advanced Head Unit.
HU_AF: Saitel DR Advanced Head Unit with acquisition.
HU120: Saitel DR High-Performance Head Unit with acquisition.
HUe: Saitel DR High-Performance Head Unit.
Hz: Hertz.

I
IED: Intelligent Electronic Device.
I/O: Input / Output.
IRIG: Inter Range Instrumentation Group.
IRIG-B: Mode B of the standard IRIG.
ISO 9001: International standard for Quality Systems.
ITB: Intelligent Terminal Block.

K
KB: Kilobyte.
kHz: Kilohertz.

L
LAN: Local Area Network.
LED: Light Emitting Diode.

M
mA: Milliampere.
MHz: Megahertz.
MB: Megabyte.
Mbps: Megabits per second.
m: Meter.
mm: Millimeter.
ms: Millisecond.

Pag 82
User Manual – Saitel DR Platform 11/11/2019

N
N/A: Non-Application.

P
PC: Personal Computer.
PPS: Pulses per Second.
PS: Power Supply.
PWR: Power.

R
RAM: Random Access Memory.
RS-232: Communication standard.
RS-485: Multipoint differential Bus.
RTDB: Real Time DataBase.
RTS: Request To Send.
RTU: Remote Terminal Unit.
Rx: Reception

S
s: Second.
SCADA: Supervisory Control And Data Acquisition.
SNTP: Simple Network Time Protocol.
SRAM: Static Random Access Memory.

T
TCP/IP: Transmission Control Protocol/Internet Protocol.
TFTP: Trivial File Transfer Protocol.
TU: Terminal Unit.
Tx: Transmission.

V
VAC: Volt of Alternate Current.
VDC: Volt of Direct Current.

W
W: Watt.

X
XU: Expansion Unit.

Pag 83
 11/11/2019 User Manual – Saitel DR Platform

Printed in:

Monday, December 2, 2019

QR code

Schneider Electric
C/ Charles Darwin s/n
Parque Científico y Tecnológico de la Cartuja
Seville, Spain

© 2019 All rights reserved. The information contained in this document is

confidential and is owned by Schneider Electric. It cannot be copied or distributed
in any way, unless there is express written authorization by Schneider Electric.
Although this information was verified at the time of publication, may be subject to change without notice.

SE-F800-USR-01 11/2019

Pag 84