Saitel DR

M588AB000y / HUe

User Manual
This manual provides information for the assembly, wiring, configuration and
maintenance of the HUe module.

SE-M588-USR

Publication Date (01/2019)

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

www.schneider-electric.com
 14/01/2019 User Manual – HUe

Change Control

Rev Date Description

01 14-01-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-M588-USR

Revision/Date: 01 / 14-01-2019
File: HUe – 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-MSS-S856

webApp User Manual FTE-WPP-S856

IEC101 User Manual FTE-I1D-S854

IEC104 User Manual FTE-I4D-S854

IEC103 Master User Manual FTE-I3D-S854

Modbus User Manual FTE-MBD-S854

ISaGRAF® User Manual FTE-ISD-S854

DNP User Manual FTE-DNP-S854

SOE User Manual FTE-SOE-S854

IEC61850 User Manual - Ed1 FTE-IEC61-1-S854

IEC61850 User Manual - Ed2 FTE-IEC61-2-S854

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

Linux Lnx 18.06.08.12.24.45 1.2.10.3

Easergy Builder Tool 1.3.2

Local Acquisition claqBinC 10.00.13 CLAQ 01.01.04

Synchronization thm 05.03.18

coreDb coreDb 10.01.06

Pag 2
User Manual – HUe 14/01/2019

RTU Software Easergy Builder (Plugin)

Module
Module Version Plugin Version
Channels chan 03.00.19

Cybersecurity Brick CSBrick 02.03.00.04

BLMon BLMon 01.01.05

Formula formBinC 10.00.13

Web Server libwebServer 03.03.01

webApp webApp 01.00.20

Supervision sup 10.01.14

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

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

AB_MIO software AB_MIO.bin 02.00.03

AB_SER software AB_SER.bin 01.00.05

Pag 3
14/01/2019 User Manual – HUe

Content

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

2 INTRODUCTION TO SAITEL DR ............................................................................ 16

3 PHYSICAL MOUNTING & INSTALLING ................................................................ 29

4 CONFIGURATION & MAINTENANCE .................................................................... 48

5 EASERGY BUILDER ............................................................................................... 73

6 ADVANCED OPERATIONS .................................................................................... 87

7 TECHNICAL SPECIFICATIONS TABLE .............................................................. 105

Pag 4
1 Safety & Health
14/01/2019 User Manual – HUe

Content

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

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

1.1.1 INFORMATION OF SAFETY ................................................................................. 7
1.1.2 PRESENTATION ................................................................................................ 7
1.2 INTRODUCTION TO SAFETY ....................................................................................... 8
1.3 SYMBOLS AND LABELS ............................................................................................ 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 ..................................................................................... 14
1.10 DECOMMISSIONING AND DISPOSAL ....................................................................... 15
1.11 NORMS AND STANDARDS / CE MARK ................................................................... 15

Pag 6
User Manual – HUe 14/01/2019

1.1 Introduction

1.1.1 Information of Safety

Important information
Read these instructions carefully and look at the equipment to become familiar with the equipment
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.

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 the requirements in section 1.2 .

1.1.2 Presentation
This manual provides information for an appropriate handling, commissioning and testing. This
chapter about Safety 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 in
order to 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.

Pag 7
14/01/2019 User Manual – HUe

Before carrying out any work on the equipment the user should be familiar with the
contents of this Safety guide, the ratings on the equipment’s rating label and the user
manual.
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).

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.

Pag 8
User Manual – HUe 14/01/2019

1.3 Symbols and Labels

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
shock
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 disposed 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

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. The user should read the instructions of installation before proceeding to the use or
maintenance of the equipment.
Not following these instructions can be dangerous for the people and the equipment.

Pag 9
14/01/2019 User Manual – HUe

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 high voltages:

• HU_AF: Advanced head unit with acquisition (P/N M503xx3x0x and P/N M503xx4x0x). 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_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.

WARNING
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.
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 an user, all people must follow all instructions to prevent
electrical risk or discharges.

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

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 high voltages.

Pag 10
User Manual – HUe 14/01/2019

NOTICE
Terminals will not be accessible to the user directly once it has made the installation of the
equipment. The cabinet will have to remain closed with key or the screen of installed protection.

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 the fulfillment of all the safety requirements and
provision of each application. These requirements are according 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 the
sections 1.5.1 and 1.5.2 .
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:

• For purposes of electrical safety (Protective Earth, PE).

• Improve the behavior in Electromagnetic Compatibility (EMC) and derive perturbations to earth
(functional Earth).

1.5.1 Electrical Safety

Only qualified personnel, with knowledge about hazards associated with electrical equipment is
allowed to install Saitel DR. In general, the installation will be following IEC 61010-1
recommendations in order to be compliant with this norm.

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

Pag 11
14/01/2019 User Manual – HUe

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 high voltages (higher than 50 V).

1.5.2 Functional Earth (EMC)

In this case the main rule is that the connection has to be done with wires of the lower possible
length to the shield or earth connection nearest. In this case the section of the driver is less
notable, moreover, it is advised of the use of flat wires or flexible conductive bands for a good
behavior EMC.

NOTICE
The DIN rail must have terminals of earthing (of yellow and green colour) 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 HUe, HU_B, 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 – HUe 14/01/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 should ONLY be removed by authorized use and ONLY 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 equipment do not work
properly or even can damage 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
using the boards 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 equipment is IP20.

WARNING
This equipment has been designed ONLY for indoor use.

If it is necessary for his use in some external surroundings, it has to mount in 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
14/01/2019 User Manual – HUe

Other data to take into account about the environmental are:

• Altitude until 2000 m.

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

• 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 considered as a high voltage.

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 equipment. Don’t use force.
The design revision and manufacturing options can be determined using the P/N included in the
packaging label on packaging.
After unpacking the equipment, inspect it visually to be sure it is in proper mechanical condition.

Pag 14
User Manual – HUe 14/01/2019

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 of 1 m.

1.10 Decommissioning and Disposal

When the product is 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.

1.11 Norms and Standards / CE Mark

Saitel has been designed and manufactured in compliance with the following Directives:

• LVD: Low voltage (2014/35/UE).

• EMC: Electromagnetic compatibility (2014/30/UE).

• RoHS 2: Restriction of Hazardous Substances (2011/65/EU).

• WDEE: Waste Electrical and Electronic Equipment (2012/19/UE)

Pag 15
2 Introduction to Saitel DR
User Manual – HUe 14/01/2019

Content

2 INTRODUCTION TO SAITEL DR ............................................................................ 16

2.1 SAITEL DR ............................................................................................................ 18

2.2 SAITEL DR MODULES ............................................................................................ 18
2.2.1 TYPES OF MODULES ....................................................................................... 19
2.2.2 HIGH-PERFORMANCE CPU – HUE .................................................................. 19
2.3 BUS ARCHITECTURE – ITB (INTELLIGENT TERMINAL BLOCK) .................................. 22
2.3.1 DATA ACQUISITION BUS.................................................................................. 22
2.4 SAITEL DR TYPICAL ARCHITECTURES .................................................................... 23
2.4.1 STAND-ALONE CONFIGURATION ...................................................................... 23
2.4.2 MICRORTU .................................................................................................... 23
2.4.3 SMALL /MEDIUM RTU ..................................................................................... 23
2.4.4 LARGE RTU / DISTRIBUTED ACQUISITION ........................................................ 24
2.4.5 DISTRIBUTED ACQUISITION AND CONTROL/PROCESSING REDUNDANCY ........... 25
2.5 BASELINE SOFTWARE PLATFORM .......................................................................... 25
2.5.1 MAIN ELEMENTS............................................................................................. 27

Pag 17
14/01/2019 User Manual – HUe

2.1 Saitel DR

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 communication between the controls units integrated in a distributed system is mainly
established by Ethernet.

• The terminal blocks for field-connection are completely built into acquisition blocks.
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 electric safety, electromagnetic compatibility, and environmental standards.

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

NOTICE
Please note Saitel DR does not support hot-swapping, that is, module replacements during
operation.

2.2 Saitel DR Modules

Saitel DR electronic 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 – HUe 14/01/2019

2.2.1 Types of Modules

The platform consists of the following core elements:

• Control Unit or Head Unit (HU): CPU module with built-in (serial, Ethernet) communication
ports. Depending on the features, there are three types of CPU:
o High-performance CPU (HUe).
o Advanced CPU (HU_A) and advanced CPU with acquisition signals (HU_AF).
o Basic CPU (HU_B).

• Serial Communication Module (AB_SER): This module enables multiple RS-232/485/422

serial channels to be added. This module can be used only with HUe, HU_A and HU_AF. A
maximum of four AB_SER modules can be used for each HU.

• Acquisition Blocks (AB): I/O modules which are connected to the HU and perform data
acquisition and, in certain circumstances, pre-process signals, control and execute commands
to field devices. There are several types of AB: digital inputs (AB_DI), digital outputs (AB_DO),
analog inputs (AB_AI), analog outputs (AB_AO), “transducerless” direct AC analog inputs
(AB_AC and AB_AC_LPVT), digital inputs and outputs (AB_DIDO) and multiple inputs and
outputs (AB_MIO).

• Complementary Modules: These modules have no data processing function, but are
indispensable for the ITB architecture. They perform the termination (TU and BT) and the bus
expansion (XU) functions, among others.

2.2.2 High-Performance CPU – HUe

HUe is a high-performance CPU developed by Schneider Electric within the Saitel DR family. HUe
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 7 – Communication between HUe and ABs.

HUe controls and manages the following functions:

ITB Controller
This block controls the operation of both the HU and the ABs connected to the HU through the bus.
These functions include:

• 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 or webApp.

Pag 19
 14/01/2019 User Manual – HUe

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

• Firmware upgrade by SFTP or webApp (using MNT port) or USB 2.0 port.

ITB Configuration
HUe 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 the MNT port.

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.

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

The available synchronization sources are:

• A GPS connected to the COM1 port. The time received from the GPS is used to set the
system’s clock and the RTC.

• An SNTP source through Ethernet. HUe can be used as SNTP server and client.

• Protocol: Most telecontrol protocols allow synchronizing to slave devices.

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

• IRIG-B: HUe can be used as a server and/or a client. The communication always will be made
with IRIG-B compliant devices.

NOTICE
If the HU_A is configured as IRIG-B server you have to include an AB_SER module in the ITB.
The IRIG-B signal will be send 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 other source is configured.

ITB Communications
The HUe configuration includes information about definition and parameterization of
communications. For HUe you have:

• IEC101 master and slave.

• IEC104 master and slave.

• DNP 3.0 master and slave.

• IEC103 master.

• Modbus master and slave.

• IEC61850 client, Edition 1 and 2.

• IEC61850 server, Edition 2.

Pag 20
 User Manual – HUe 14/01/2019

I/O Acquisition
HUe manages the information exchange with the ABs. Its main functions include:

• Processing I/O information, which offers an added value to the information exchanged with the
ABs.

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

• The HUe module has 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 (more details below in this
manual).

Real-Time DataBase (RTDB)

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 HUe 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 RTDB and then
related to the communication protocols signals of the ITB, which function is to transfer that
information to the master device.
Figure 8 – coreDb operation example.

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 with an internal device of the
type "Formula".
Consult more information about this functionality in the Easergy Builder user manual.

Cybersecurity
The HUe module is 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.

Pag 21
14/01/2019 User Manual – HUe

2.3 Bus Architecture – ITB (Intelligent Terminal Block)

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

The following figure shows a typical architecture of a system based on the Saitel DR platform.
There are an HUe module connected to a series of AB acquisition blocks (maximum 32 ABs and
maximum 8 per row), including the expansion (XU) and termination units (TU or BT) needed.
Figure 10 – Basic ITB.

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.3.1 Data Acquisition Bus

Power, data, synchronization, signals and other information are transmitted between HUe 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.
Figure 11 – Module interconnection.

Pag 22
User Manual – HUe 14/01/2019

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 HUe and XU modules. This terminal is used in order to power
each row in the ITB.

Figure 12 – Bus expansion between rows.

At the end of each row there must be a termination module, that is, a TU or a BT. The latter only in
the last row.

2.4 Saitel DR Typical 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.4.1 Stand-alone Configuration

The HU_AF is a control module with integrated signal acquisition (digital inputs, digital outputs and
analog inputs). It can be used stand-alone, but can be expanded with other ABs if required.
This equipment can be mounted on DIN rail as well as back panel mounting.

2.4.2 microRTU
A single head unit (for example HU_B) plus a set of acquisition blocks (max. 16) make a microRTU
with a single ITB.
Figure 13 – microRTU.

2.4.3 Small /Medium RTU

The system illustrated in the previous example can be expanded by replacing the HU_B with an
advanded HU. This change increases both the processing capacity and the number of supported
ABs in the ITB. These components are used to build a small/medium size RTU.

Pag 23
14/01/2019 User Manual – HUe

Figure 14 – Small / Medium size RTU.

2.4.4 Large RTU / Distributed Acquisition

The following figure illustrates a system which integrates a large RTU with distributed data
acquisition and processing capabilities:
Figure 15 – Large size RTU with distributed 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 HUe, HU_A or HU_AF in charge of gathering and processing all
the information.

Pag 24
User Manual – HUe 14/01/2019

2.4.5 Distributed Acquisition and Control/Processing

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

Figure 16 – 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 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.

2.5 Baseline Software Platform

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

• Real-time operating system: VxWorks (HU_A and HU_AF) and Linux (HUe).

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

Pag 25
14/01/2019 User Manual – HUe

Figure 17 – 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 18 – Relation between coreDb and other applications.

Pag 26
 User Manual – HUe 14/01/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.

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

• 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).

• Coordinate: Point identification within a Device. It is unique for each point and has a different
structure for each Controller. It is described in detail in the appropriate manual of each
Controller.

• Configuration Plugin: Specific Configuration plugins extend the Easergy Builder application to
configure Device Controllers. Additional details about these plugins are provided in their
manuals.
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.

2.5.1 Main Elements

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

coreDb – Real-Time DataBase

coreDb is the real-time database backend on which BaseLine Software Platform is built. All the
information controlled and managed by the system is stored in this database.
Thanks to this architecture, the system’s functionalities can be easily expanded to manage new
protocols, customized controllers, etc. To accomplish this, trained developers only need to
implement the required Device Controller and the associated Configuration plugin for Easergy
Builder, allowing end users to configure the extended functionality.
coreDb registers are also called data points or, simply points (this term will be used onwards to
avoid confusing these with Device points).
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.

Pag 27
 14/01/2019 User Manual – HUe

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

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.

Software Tools
A basic configuration is included with HUe, which should be adapted to the requirement of the
system.

• 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: 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. Using the configuration
defined in Easergy Builder and loaded in the HUe, 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.

• 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 the maintenance Ethernet port (MNT). The console is a commands tool, which the user
could execute or not depending on the level of privileges assigned to him.

Pag 28
3 Physical Mounting & Installing
14/01/2019 User Manual – HUe

Content

3 PHYSICAL MOUNTING & INSTALLING ................................................................ 29

3.1 ITB INSTALLATION ................................................................................................. 31

3.1.1 HANDLING MODULES ...................................................................................... 31
3.1.2 HUE LOCATION IN THE ITB ............................................................................. 31
3.1.3 POWER SUPPLY REQUIREMENTS .................................................................... 31
3.1.4 MOUNT AND DISMOUNT PROCEDURES ............................................................ 31
3.2 GENERAL DESCRIPTION OF HUE ............................................................................ 32
3.2.1 INTERFACES & FUNCTIONS ............................................................................. 32
3.2.2 HARDWARE ARCHITECTURE ............................................................................ 33
3.3 WIRING RECOMMENDATIONS FOR EMC .................................................................. 34
3.3.1 WIRING TYPES ............................................................................................... 34
3.4 WIRING .................................................................................................................. 38
3.4.1 POWER AND RESET ........................................................................................ 38
3.4.2 DIGITAL INPUTS .............................................................................................. 39
3.4.3 SERIAL COMMUNICATIONS .............................................................................. 40
3.4.4 ETHERNET COMMUNICATIONS......................................................................... 42
3.4.5 IRIG-B AND WATCHDOG OUTPUT ................................................................... 44
3.4.6 SD CARD AND USB (HOST) ............................................................................ 44
3.4.7 EXPANSION .................................................................................................... 44
3.5 CONFIGURATION SWITCHES ................................................................................... 45
3.6 LED INDICATORS ................................................................................................... 46

Pag 30
User Manual – HUe 14/01/2019

3.1 ITB Installation

3.1.1 Handling Modules

Please note the following precautions to avoid electrostatic damages:

• You should never touch the pins of the bus connector.

• You should keep the module in its packaging box when unused.

WARNING
Electrostatic discharges may damage semi-conducive devices within the module.

3.1.2 HUe Location in the ITB

The HUe module 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 are
installed and connected to the acquisition ITB by means of an Ethernet network; the system’s bus
is not used in this case. Paragraph 2.4.5 shows an example of this configuration.

NOTICE
In order 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.

3.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 HUe (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.

3.1.4 Mount and Dismount Procedures

WARNING
It is important to assure that handling is always done while the ITB elements are unpowered.

Saitel DR modules have a DIN-rail bracket at the rear side that allows mounting on a DIN rail.
Figure 19 – Mount bracket on DIN rail.

Pag 31
14/01/2019 User Manual – HUe

The mounting procedure is described below:

• Switch off the power supply.

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

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

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

The module is dismounted from the DIN rail as follows:

• Switch off the power supply.

• If necessary, disconnect the bridge(s) connecting the module to the system bus.

• Holding the module by the front panel, push the upper metal tab downward. The user can also
pull the tab down using for example a screwdriver as shown:

• Pressing the tab, remove the module from the lower DIN rail.

• Once detached, the module can be removed easily.

3.2 General Description of HUe

3.2.1 Interfaces & Functions

The HUe module is a high-performance CPU, which offers superior performance to other Saitel DR
CPUs. It includes the Baseline Software Platform based on Linux operating system and with an
integrated cybersecurity brick.
Figure 21 – HUe front view.

Pag 32
User Manual – HUe 14/01/2019

The main features of this module are:

• Power input between 24 and 48 VDC, with tolerance of 20%.

• A reset button integrated allowing the user to reset the module mechanically.

• It implements a security mechanism for data in memory (NVRAM) allowing to keep the
information for some time if the power is temporarily down.

• 4 general-purpose digital inputs.

• Synchronization using: IRIG-B input, PPS signal (through a GPS), console or SNTP.

• A watchdog isolated output is available and can be used according to the requirements of the
system.

• A copper Fast-Ethernet port for configuration and maintenance (10/100BaseT).

• Two additional Fast-Ethernet ports, which can be copper (10/100BaseT) or fiber optic
(100BASE-FX) depending on the mounting options.

• Two RS-232 non-isolated communication ports. COM1 allows modem control but COM2 does
not.

• One RS-485 isolated communication port.

• One console port using a miniUSB connector.

• One USB 2.0 connector for software upgrading.

• SD slot.

3.2.2 Hardware Architecture

The module is composed by two or three electronic boards, depending on the manufacturing
options.
Figure 22 – Electronic boards in HUe.

These electronic boards and the metallic enclosure makeup the HUe module. This information is
shown in the technical label on the module with the Part Number (P/N):

Pag 33
14/01/2019 User Manual – HUe

Figure 23 – Part Number description.

If the module is manufactured without optic fiber, only two boards will be mounted.

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

3.3.1 Wiring Types

Considering the wiring types which could be used, there are five different groups:
Table 2 – 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).

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

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

Pag 34
 User Manual – HUe 14/01/2019

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 24 – 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.

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

Pag 35
14/01/2019 User Manual – HUe

Figure 25 – 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 26 – Wrong connection of the polarization power supply.

3.3.1.3 Group 5 (Ground Connection)

• Use cables with enough section (see paragraph 1.5 ), and 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 protection earth. If metal cabinets are used, the cabinet’s walls can be also
used to distribute the ground.

Pag 36
User Manual – HUe 14/01/2019

Figure 27 – 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.
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.

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

Pag 37
 14/01/2019 User Manual – HUe

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

• 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 (see paragraph 1.5 ) 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).

3.4 Wiring

The following section describes each HUe interface, including functionality and wiring when it is
required.

3.4.1 Power and Reset

Figure 29 – Power and Reset.

In the upper left area you can observe the power supply input terminal for the first row in the ITB.
There is a DC/DC converter, next to the filtering electronic components, which is used to power
both the HUe module itself and all the AB modules assembled on the same row.

NOTICE
The maximum power to be supplied to the rest of modules in the same row by the HUe module
is 10 W. If the modules to be assembled on the ITB require a higher power, then, you will need
to split the ITB into several rows, always observing the above-mentioned maximum power
allowed for each row.

A Reset button is included in this block allowing the user to reset all the ITB.

Power Wiring
The POWER connector must be used as power input. The input voltage range is 24 to 48 VDC, with
a tolerance of ±20%.

WARNING
For safety reasons, the use of ferrules on power input cables is recommended to avoid possible
short-circuits.

From left to right, the connecting order must be: functional Earth, negative and positive terminal.
Pag 38
 User Manual – HUe 14/01/2019

WARNING
For safety reasons, before connecting the aerial terminal to the module, it is recommended:

• To check that the voltage between the positive and negative poles does not exceed the
maximum operating voltage (see the technical table in chapter 7).
• To check that the polarity has not been inverted according to the label on the terminal..

3.4.2 Digital Inputs

Figure 30 – General-purpose digital inputs.

HUe has 4 digital inputs located in the lower left, only configurable as single inputs. These signals
are useful to inform the operator about some malfunction in the system.
The digital inpus 1 and 2 can be used for the following purposes:

• Digital input 1: This signal provides the HUe module with information about the digital inputs’
polarization status of the ABs installed in the ITB. When the signal is active, the polarization of
all digital signals is correct. If the signal is disabled, the HU will understand that there is a
polarization fault.

• Digital input 2: If this signal is enabled, the HUe module will interpret that the ITB is working in
LOCAL mode, whereas if it is disabled, the ITB is operating in REMOTE mode. When the ITB
is in LOCAL mode the commands are disabled.
To use these two signals with the purpose described above, they must be defined in the database
following the instructions included in paragraph 5.9 of this manual.

WARNING
Before doing any local operation, for safety reasons, the operator MUST:

• To be sure that the "Local" LED on HUe is lit.

• To be sure that the secondary relays are de-energized.

Digital Inputs Wiring

Use AUX DI terminal in order to use the general-purpose digital inputs. These signals are self-
polarized, that is, they do not need an external polarization source.

These digital inputs are designed for internal use within the cabinet where the HUe module is
installed.

WARNING
These signals must not be connected to equipment that are outside the cabinet. Failing this
instruction could modify EMC behavior of the equipment.

The following figure illustrates how each input receives the polarization through the common:

Pag 39
 14/01/2019 User Manual – HUe

WARNING
These digital inputs are internally polarized. Please, DON’T CONNECT to other power supply.
Failure to observe this instruction can result in equipment damage.

3.4.3 Serial Communications

Figure 31 – Serial communication ports.

• COM1 and COM2: non-isolated RS-232 communication ports for general-purpose. Both ports
use male DB-9 connector.

• CON: Console port with miniUSB connector.

• RS-485: Isolated TS-485 communication port.

RS-232 Communications Wiring (COM1 and COM2)

All modem signals are available in COM1 port. COM2 only uses RTS and CTS signals. The
maximum speed in both ports is 115200 bps.
Following tables show the pinout for both connectors:
Table 3 – Pinout of COM1

Pin Description I/O

1 DCD – Data Carrier Detect I
2 Rx – Data Reception I
3 Tx – Data Transmission O
4 DTR – Data Terminal Ready O
5 GND – Ground -
6 DSR - Data Set Ready I
7 RTS – Request to Send O
8 CTS – Clear to Send I
9 RI – Call indicator I

Pag 40
 User Manual – HUe 14/01/2019

Table 4 – Pinout of COM2

Pin Description I/O

1 Not connected -
2 Rx – Data Reception I
3 Tx – Data transmission O
4 Not connected -
5 GND – Ground -
6 Not connected -
7 RTS – Request to Send O
8 CTS – Clear to Send I
9 Not connected -

NOTICE
COM1 can receive a pulse per second signal (PPS) through pin 8, so it must be used as the
GPS input, if required. The input PPS signal must be valid for RS-232 levels.

The validated GPS devices to be connected to the COM1 port are GPS35 (Garmin) and GPS16
(Garmin).
Some GPS devices don’t allow to use PPS signal.This operation mode implies that the
synchronization accuracy will be lower. It can produce a desviation of up to 10 ms in the generation
of the signal.

NOTICE
When using a GPS synchronization device, it is always advisable to wire the PPS signal to
achieve the highest accuracy in the synchronization.

WARNING
The installer should check that the cable connected to each COMx port is correct. It is also
recommended to use identification tags on the cables to avoid errors.

Redundancy Wiring (COM1 and COM2)

For redundant system, both HUe can be connected using COM1 and COM2 ports. The following
pinout must be considered (other pins should not be connected):
Figure 32 –Pinout of the cable for redundancy.

Pag 41
 14/01/2019 User Manual – HUe

Console Port Wiring (CON)

The following table shows the pinout of the miniUSB port for the console:

Table 5 – Pinout of the console port.

Pin Name Wire color I/O

1 - Not connected
2 Data - White O
3 Data + Green I
4 Mode detection - Not connected
5 Ground Black Ground

RS-485 Wiring (RS-485)

This terminal block is used to communicate with other equipment through a 2-wire RS-485
communication (Half-Duplex). The figure below shows the pinout of this terminal:

The relationship between this 3-poles terminal and the SM_SER’s DB9 connector is the following:
Table 6 – 2-wire RS-485 to DB9

HUe connector DB9 connector

A Pin 9 (Y)
B Pin 8 (Z)
Ground Pin 5

3.4.4 Ethernet Communications

Figure 33 –Ethernet communication ports.

• MNT: Fast-Ethernet port (10/100BaseT) for maintenance purpose. It uses a RJ-45 connector.

• LAN1 and LAN2: Fast-Ethernet communication ports using copper or fiber optic depending on
the manufacturing options.
o Copper ports allow 10/100 BaseT IEEE 1588, with a RJ-45 connector.
o Fiber optic ports allow 100Base-FX with SFP connectors.

Pag 42
 User Manual – HUe 14/01/2019

WARNING
The installer should check that the cable connected to each Ethernet port is correct. It is also
recommended to use identification tags on the cables to avoid errors.

Ethernet Wiring – Copper ports

The pinout for RJ-45 connector is the following:

Table 7 – Pinout of the copper ports.

Pin Name Description TIA/EIA 568A TIA/EIA 568B

1 BI_DA+ Bi-directional pair A+ (TX) White/Green White/Orange

2 BI_DA- Bi-directional pair A- (TX) Green Orange

3 BI_DB+ Bi-directional pair B+ (RX) White/Orange White/Green

4 BI_DC+ Bi-directional pair C+ Blue Blue

5 BI_DC- Bi-directional pair C- White/Blue White/Blue

6 BI_DB- Bi-directional pair B- (RX) Orange Green

7 BI_DD+ Bi-directional pair D+ White/Brown White/Brown

8 BI_DD- Bi-directional pair D- Brown Brown

TIA/EIA 568A and TIA/EIA 568B are two color codes used for wiring eight-position RJ45 modular
plugs. Both are allowed under the ANSI/TIA/EIA wiring standards. The only difference between
both codes is that the orange and green pairs are interchanged.

WARNING
Each network segment cable length may be up to 100 m.

Ethernet Wiring – Fiber Optic Ports

If fiber optic is selected in manufacturing options for LAN1 and LAN2, they have to mount a SFP
transceiver with LC connector. These transceivers aren’t included with HUe.
The following figure shows two connectors which could be used in LAN1 and LAN2:

The following models are recommended:

• Models: HFBR-57E0PZ and HFBR-57E0APZ

o Full compliance with the optical performance requirements of 100Base-FX version of
IEEE802.3u.
o Operates with 62.5/125 μm and 50/125 μm multimode fiber, with a LED light
source of 1300 nm.
o Maximum link lenght: 2 km.
o Operating temperature: From -40 ºC to +85 ºC (only HFBR-57E0APZ)

Pag 43
 14/01/2019 User Manual – HUe

3.4.5 IRIG-B and Watchdog Output

Figure 34 –IRIG-B and WD output connectors.

IRIG-B Wiring
This terminal block is used to receive an IRIG-B signal (non modulated TTL) which can be used by
the CPU to synchronize the ITB.
The connector for IRIG-B has the following pinout:

HUe can be set as an IRIG-B client and/or server, according the standards IRIG-B002, 003, 006
and 007.

Watchdog Wiring (WD)

A watchdog output (identified as WD) is available in HUe for system monitoring. It is implemented
with a solid-state relay (normally closed), supporting a maximum voltage of 250 V and a current of
200 mA. The relay status depends on the FAIL_RTU supervision signal. A normal value of this
signal is 0, and value 1 is associated to the detection of a malfunction in the system.

3.4.6 SD Card and USB (Host)

Figure 35 – Slot for SD card and USB connector.

The slot for the SD card is located on the left side of the module. This card can be used for mass
storage of data, for example, the event log.
The USB (Host) port next to the SD card slot can be used for software upgrade.

3.4.7 Expansion
Figure 36 – Expansion bus connector.

Through a flat ribbon connector, the CPU starts the data and power bus, expanding it to the other
modules.

Pag 44
User Manual – HUe 14/01/2019

NOTICE
Before disconnecting the slave modules from the bus (disconnecting the flat ribbon) the ITB
must be unpowered.

3.5 Configuration Switches

There are 4 configuration switches on the front of the module. They are numbered 1 to 4 from the
left to the right.
Figure 37 – Configuration Switches.

This group of switches allows:

• Restoring the manufacturing default configuration.

• Enabling the automatic execution of the addressing procedure (AAP).

• Executing the AAP automatically when the ITB starts.

As is indicated on the label, the switch is in position ON if is up and OFF when is down.
These switches can be used as follow:

• Switch 4: It restores the factory IP configuration. If switch 4 is ON when HUe starts, the
network configuration will be restored for all Ethernet ports. If the network configuration file
(netConfig.xml) exists, it will be renamed to old_netConfig.xml. The default IP addresses are
indicated in paragraph 4.1 .

• Switch 3: It enables or not the automatic execution of the AAP:

o On: Enabled. When the ITB starts, the AAP procedure is automatically executed.
o Off: Disabled. The AAP procedure has to be executed with a command if it is
required. This command may be executed depending on the position of switch 2.

• Switch 2: It allows or not the execution of AAP:

o On: Allowed. The AAP can be executed.
o Off: Not allowed. The AAP cannot be executed either automatically or manually.

• Switch 1: Reserved. It must be in OFF position.

Pag 45
14/01/2019 User Manual – HUe

3.6 LED Indicators

There are 24 light indicators (LED) on the front of the module:

Figure 38 – LED indicators

The information by the LED indicators includes:

• General status of the module (On, Bat, Local and Sync)

• Configuration and acquisition status (Run, Fail, DIO and RED)

• Status of the 4 general-purpose digital inputs (Digital Input x).

• Transmission/Reception in COM1, COM2, CON and RS-485 ports (Tx and Rx).

• Communications in the Ethernet ports LAN1 (ETH1) and LAN2 (ETH2).

NOTICE
There is not a LED associated to the MNT port.

HUe’s LED provide the following information to the operator:

 Blink  On  Off

Table 8 – LED indicators.

LED Status Description Recommended action

On Powered. -
Unpowered. Connect the module to a power supply
according to the input voltage of the
module.
Bat The supercapacitor is discharged. While Switch 1 must be turned OFF. The led will
this led is on, the system cannot keep the turn off when the supercapacitor is loaded.
data in memory if a power down occurs.
Normal state. If the supercapacitor is fully
charged, data in memory can be kept for 8
hours (at 25 ºC) if a power down occurs.
Local RTU in LOCAL mode. Digital outputs are
disabled in the ITB.
RTU in REMOTE mode.
Sync The system uses an external
synchronization source.
Any external synchronization source is
being used.

Pag 46
User Manual – HUe 14/01/2019

LED Status Description Recommended action

Run RTU operative, with configuration or not.

RTU not operative. Use the console tool in order to check if the
message “CONF OK” is shown. The
supervision signal DOING_WELL must be
defined in coreDb and set to 1.
Fail RTU not configured or with errors. Use Easergy Builder and load a
configuration without errors in the CPU.
A correct configuration is loaded in the
CPU.
DIO There is at least one module in Fail status Identify the module with problems and
in the ITB. perform the recommended actions. More
information in the user manual of the
module in fail status.
All modules in the ITB are OK.
RED. Redundant system and this is the HUe
HOT.

Redundant system and this is the HUe

STANDBY.
Non redundant system or configuration.
Digital The digital input x is activated.
Inputs x The digital input x is deactivated or not
defined in coreDb.

Pag 47
4 Configuration & Maintenance
User Manual – HUe 14/01/2019

Content

4 CONFIGURATION & MAINTENANCE .................................................................... 48

4.1 GETTING STARTED ................................................................................................ 50

4.1.1 USING THE CONSOLE ..................................................................................... 51
4.1.2 FILE SYSTEM.................................................................................................. 52
4.1.3 NETWORK SETTINGS (IP / ROUTER / FIREWALLS) ............................................ 53
4.1.4 ENVIRONMENT VARIABLES .............................................................................. 56
4.2 CYBERSECURITY.................................................................................................... 56
4.2.1 CAE AND RBAC ............................................................................................ 57
4.2.2 USERS ........................................................................................................... 57
4.2.3 ROLES ........................................................................................................... 58
4.2.4 SECURITY EVENT LOG .................................................................................... 60
4.3 ITB ADDRESSING (AAP) ........................................................................................ 61
4.4 LOCAL ACQUISITION .............................................................................................. 62
4.4.1 CENTRALIZED LOCAL ACQUISITION ................................................................. 62
4.4.2 DISTRIBUTED LOCAL ACQUISITION .................................................................. 63
4.5 TREATMENT OF LOCAL ACQUISITION SIGNALS........................................................ 64
4.5.1 GENERAL-PURPOSE DIGITAL INPUTS .............................................................. 64
4.5.2 FIELD DIGITAL INPUTS .................................................................................... 65
4.5.3 DIGITAL OUTPUTS .......................................................................................... 69
4.5.4 ANALOG INPUTS ............................................................................................. 70
4.5.5 ANALOG OUTPUTS.......................................................................................... 71

Pag 49
 14/01/2019 User Manual – HUe

4.1 Getting Started

HUe is supplied with a basic configuration, which will help us have a first contact with the system.
To get started, you need to know the following data:

Default IP Addresses
Table 9 – Default IP Addresses.

Port Description IP Subnet Mask

LAN1 Operating system's eth0 port. 10.1.1.1 255.0.0.0
LAN2 Operating system's eth1 port. 192.168.1.1 255.255.255.0
Operating system's eth2 port. This is the 192.168.2.1 255.255.255.0
MNT
maintenance dedicated port.

User
In accordance to the policy provided with the CAE tool, the default users which can log into the
system are:
Table 10 – Default users.

User Level User Password Description

This user can view most of the system's
information (data, syslog, events, settings…) It
Operator Operator Operator1!
can write to coreDb, but it does NOT have
access to security parameters.
This user can view and modify all the system
information, except for the security parameters. It
Engineer Engineer Engineer1!
can also access the operating system's console,
although it cannot execute Saitel commands.
This user can view and modify all the system
information, except for the security parameters.
Installer Installer Installer1!
In the console, it can only access the BLMon
application and Saitel commands.
This user level can read coreDb settings and
Viewer Viewer Viewer1! data and can connect to webApp. It cannot make
changes to settings or to the coreDb data.
This user level is only used to define and modify
Administrator SecurityAdmin Security1!
the security parameters and user permissions.

NOTICE
We recommend using the Engineer user to perform configuration tasks with Easergy Builder
and the Installer user to use the console.

When working with the HUe module, the user will need to prepare the working environment, in
terms of installing the adequate tools, making the software files available, in case the CPU needs
to be upgraded, and so on.
There are certain tasks that the user must be familiar with before using Saitel DR, such as:

• Installing and using Easergy Builder: This manual describes specific operations to be
performed with this tool (see Chapter 5 in this manual). For detailed information about the use
of Easergy Builder, please refer to “Easergy Builder User Manual”.

Pag 50
 User Manual – HUe 14/01/2019

• Using webApp: For detailed information about the use of the web server, please refer to
“webApp User Manual”.

• Operating Saitel DR modules: For further information about the wiring, configuration, and use
of the modules which be included in an ITB, please refer to their respective user manual.

4.1.1 Using the Console

The material below is required to use the console:

• A HUe M588 Module.

• A console cable if a USB cable is used. For connecting to the HUe, the cable must have a
miniUSB connector (for further information about the CON port and its pinout, please refer to
section 3.4.3 in this manual).

• Software for serial channel connection. In the examples of this user manual, we have used
PuTTY, which is a free-license software that can be used in most PC’s running on Microsoft®
Windows® and several UNIX® platforms.

Connection
Connect the cable between the CON port (miniUSB connector) in the HUe to a PC serial port (one
of the USB ports can be used).
Switch on the HUe module and execute PuTTY (or another commercial software).

Working with the Console

Once you know which COMx port you need to connect in the PC. Open a console session with the
following parameters:

When the connection is established, you will be prompted to enter a valid user by the operating
system’s console:

Pag 51
14/01/2019 User Manual – HUe

The commands that can be executed in the console will depend on the logged-in user permissions.
In order to execute the usual actions with this tool, we recommend using the Installer user and
Installer1! password.

For a complete list of all BLMon commands and its actions, please refer to section 6.4 in this
manual.

4.1.2 File System

You can access the file system in the HUe module by using a secure connection, such as SFTP
(SSH – File Transfer Protocol).In the following examples, Filezilla software was used.
You can also browse several directories using the Linux commands available in the console.
The files constituting the Baseline Software Platform are installed in a non-volatile memory which is
accessible by the user. The file system is structured as follows:

• /mnt/bf:Flash memory. This is a general-purpose memory. It stores ISaGRAF®, web server,

and other application's files.

• /mnt/flash: Main memory. It stores user applications of Baseline Platform, for example, the
software for the Device Drivers and their configuration files.

• /mnt/nflash: Auxiliary memory assembled on a NAND flash memory.

• /nvRam: Non-volatile SRAM memory. Memory used for data storage (i.e. Event log).This
memory has a power fail protection by means of a supercapacitor, which is capable of retaining
data for 8 hours.

• /mnt/sd1: Memory for mass data storage in a SD memory card. The board needs to be
inserted in the slot on the module’s side panel. The /mnt/sd1 folder is listed in the file system
when the card is inserted in this slot. If the card is not inserted, then the folder will not be
displayed in the file system.

Pag 52
 User Manual – HUe 14/01/2019

• /mnt/usb1:Memory for mass data storage in a pen drive. When the device is connected to a
USB port, the /mnt/usb1 folder is listed in the file system, and we can access to its contents. If
there is no pen drive connected to this port, the folder is not displayed in the file system.

NOTICE
The host USB port can be used to update Baseline. You need to connect a pen drive containing
new Baseline file to be installed (for example, “Baseline_11.06.02.tar.gz”) and, then, click Reset
on the equipment.
IMPORTANT: For the update to be successful, there should only be one file
Baseline_XX.XX.XX.tar.gz on the pendrive.

4.1.3 Network Settings (IP / Router / Firewalls)

The configuration windows will depend on whether you are configuring a redundant RTU or not;
two or more tabs will be displayed in the network settings and environment variables screen.
If the RTU is not redundant, you can only see the following tabs: “Network” and “Environment
Variables A”. If the RTU is redundant, you will see the corresponding configuration tabs for each
CPU, that is “Network – CPU A”, “Network - CPU B”, “Environment Variables A”, and
“Environment Variables B”, where A is the main CPU and B is the secondary CPU.

Network Interfaces
Figure 39 – Network Interface Settings.

You can view the existing network settings in the CPU (by clicking ) or modify the interfaces
and, then, applying the changes (by clicking ) so that they are effective in the next initialization.
If you need to add new network interfaces, remove one of the existing interfaces or change their
respective parameters, use the , , and buttons respectively.
All the network interfaces integrated in the HUe can be set as DHCP client, so “IP Address” and
“Subnet Mask” fields are ignored. These data are automatically assigned by a DHCP server
through the network.

NOTICE
HUe cannot be set as a DHCP server.

Nevertheless, it is possible to configure a Parallel Redundancy Protocol (PRP) logical interface.

This interface allows two physical ports to be used as a single port, that is, both ports will have the
same MAC address and the same IP address.

NOTICE
If configuring the PRP interface, you CANNOT define the LAN ports.

Pag 53
 14/01/2019 User Manual – HUe

Routers
If you need to define interfaces in different networks, then you need to configure the device that
gives us access to different networks. Each device is configured in the “Routers” tab, in which we
specify their respective IP address. The figure below illustrates an example with two external
subnets.
Figure 40 – Using routers to configure subnets.

Define the following settings in Easergy Builder:

The Destination IP and Destination Mask fields are related to the IP addresses to be reached from
the router. The Router IP is the device's IP address in the main network.
You can register the default IP address and mask once (i.e., 0.0.0.0 and 0.0.0.0) in order to access
external networks. With these settings you can reach any device connected to the router from the
CPU.

As with network interfaces, you can use the buttons on the right to add, remove or edit a router.

Pag 54
 User Manual – HUe 14/01/2019

Firewalls
The network ports (MNT, LAN1, and LAN2) have the Firewalls tab in which you can define the
following:

• Defining a white list: A pool of IP addresses which will access the CPU through this port.

• Defining a black list: A pool of IP addresses which CANNOT access the CPU through this
port.

• Blocking a TCP or UDP port in the interface. In this case, no device can connect to this
network interface using the specified port.

To manage the firewall rules for each port, you need to select it from the list and click .

The configuration of the Firewalls in the system is not required. If the network interface does not
have Firewall settings, then no restrictions or capabilities are associated to use this feature.
To define a “White list:” or “Black List”, you need to select the Type and indicate the pool of
addresses to be included (IP Address / Subnet Mask).
To block a port, you need to select “Blocked port” in Type field and then indicate the port number
and type (TCP or UDP).
The firewall rules are defined in the order below:

• Firstly, indicate the Forwarding state.

• Secondly, close the ports

• Thirdly, block the “Black list” addresses

• Fourthly, allow the “White list” addresses

With this configuration, make sure that the information received from one port or one address will
be accepted or rejected in accordance to this rule ordering. When a rule matches, the information
is accepted or rejected. If no rule matches, then communication is enabled
It is also possible to forward a packet received through an Ethernet port with the IP Address
belonging to another port's subnet. This is known as Packet Forwarding between Ethernet ports.
To use this feature, you need to check the “Forwarding” box.
This feature is disabled by default for all ports.

Pag 55
14/01/2019 User Manual – HUe

4.1.4 Environment Variables

There are multiple environment variables defined in Baseline Software Platform which should be
known in order to configure our system according to our requirements. These variables are defined
in the “main_cfg.xml” en /mnt/flash file, which is managed and edited by means of Easergy Builder
tool, as shown below.
The environment variables that must be defined with default values are:

• CONFIG_DIR:(Default value:/mnt/flash/cfgFiles/).This is the folder in which configuration files

are stored. The CPU may have several projects stored in different associated configuration
folders. The system will load the project whose configuration folder is associated with the value
of this variable. If necessary, you can use an external storage device for these configuration
folders (SD card o USB pen drive).

• BIN_DIR:(Default value:/mnt/bf/).Alternative path for application or binary files. The default

directory in which application files are stored is /mnt/flash.If these files are not in this folder, the
system will search in an alternative file path, as indicated in BIN_DIR.

• SLOT: In a redundant system, it is necessary to define the type of CPU you are configuring. It
will have the value A in the main CPU, the one that is initialized HOT by default, and B for the
secondary CPU.

• WEB_IS_REMOTE:(It doesn’t apply with HUe).

If a redundant HUe is configured, then you will have two tabs; the first is associated to the CPU A
and the second is associated to CPU B. The figure below illustrates the variable definition in a
redundant CPU:

You can change the values in these tabs and send the changes to the CPU by clicking ; new

values will be applied in the next CPU initialization. If button is used, you can read the current
value for these variables.

4.2 Cybersecurity

The HUe module implements a standard security policy and a default RBAC model (Role-based
access control).This model is defined and managed by a special tool, i.e. CAE (EcoStruxure™
Cybersecurity Admin Expert). Based on this model, authorized users can create and manage other
system's users. Moreover, the CPU includes a firewall.
The RBAC model implemented in the HUe module complies with the IEC 62351-8 standard.

Pag 56
User Manual – HUe 14/01/2019

4.2.1 CAE and RBAC

CAE is the tool designed to administer the security policy and define access restrictions for the
system and/or communication interfaces.
A key aspect of this RBAC model is that every access is controlled by means of roles; each role is
defined as a set of permissions and privileges. Permissions are assigned to users by means of
roles; they can also inherit roles though a hierarchy.
The RBAC model provides the HUe module with:

• Secure connections for local and remote maintenance: HTTPS and SSH.

• Secure file transfer protocol: SFTP.

• Firewall capability.
Default RBAC model is detailed in further sections in this manual, including:

• List of objects.

• List of roles (users)

• Allocation of each role to each object's permission.

It is not necessary to modify the RBAC module supplied with the equipment, if it is fulfils the
system's requirements.
Otherwise, use the CAE tool for:

• Creating a user database

• Defining the roles

• Managing the RBAC model in each device centrally.

4.2.2 Users
During the engineering phase, CAE must be used to redefine or change the access restrictions for
the system, including the access rights and responsibilities.
In the basic model supplied with HUe, the SecurityAdmin user is the only user with sufficient
privileges to administer Saitel cybersecurity (please, see table below).It means that it is the only
user which is able to administer and/or modify the passwords and roles being assigned to the
users.
Table 11 – Default users

User Password Role

Viewer Viewer1! VIEWER

Operator Operator1! OPERATOR
Engineer Engineer1! ENGINEER
Installer Installer1! INSTALLER
SecurityAdmin Security1! SECADM
SecAud Secaud1! SECAUD
RbacMnt Rbacmnt1! RBACMNT

Once access levels are defined in the RBAC model, you can use HUe's web server (webApp) in
order to add or remove users, modify passwords and assign one or several predefined functions to
the users or modify them.

Pag 57
14/01/2019 User Manual – HUe

WARNING
When users are modified, if new RBAC configuration is uploaded from CAE, all changes here
will be overwritten.

In webApp, use Maintenance tab in order to manage the users:

Figure 41 – Managing users in HUe.

For further information, please refer to webApp User Manual.

NOTICE
For security reasons, these users’ password must be changed when the system is initialized.

4.2.3 Roles
Role-based-access-control (RBAC) is a control mechanism that defines the roles and privileges
assigned to each role. These privileges are defined in accordance to some objects and actions that
the user can act upon:
The table below illustrates the actions allowed for each object. Depending on the roles assigned to
the logged-in user in the system, a specific action is allowed or not for an object:
Table 12 – Default roles

Object Description Actions Privilege

Reading CONFDB_READ
CONF_DB Configuration files in coreDb.
Writing CONFDB_WRITE
Reading CONFSYS_READ
CONF_SYS Configuration files in the system.
Writing CONFSYS_WRITE

Pag 58
User Manual – HUe 14/01/2019

Object Description Actions Privilege

Reading FIRMWARE_READ
Directory in which Baseline executables and
FIRMWARE libraries are contained (excluding the Writing FIRMWARE_WRITE
smAutoLoad file).
Viewing FIRMWARE_VIEW
WEBSERVICE Web server. Access WEBSERVICES_ACCESS
SSH and SFTP connection to the operating SSH_ACCESS
SSH Access
system.
OSSHELL Operating system's console. Access OSSHELL_ACCESS
BLMON Baseline Console. Access BLSHELL_ACCESS
System's Log File (Baseline).It includes the Reading SYSLOG_READ
log file both for the system and SOE
SYSLOG
(sequence of events), but it does not include Writing SYSLOG_WRITE
the cybersecurity log.

Configuration of the model associated to Reading RBAC_READ

RBAC
cybersecurity brick. Writing RBAC_WRITE
RBAC_LOG Log file for the cybersecurity brick. Reading RBACLOG_READ
RESET System reset. Access RESET_ACCESS

Access to the information about coreDb Reading DATA_READ

DATA
points. Writing DATA_WRITE

The table below illustrates the privileges associated each role defined in the RBAC model for the
HUe module. In order to administer users and roles, you will need to log into webApp with
SecurityAdmin user.
Table 13 – User’s privileges.

Roles
OPERATOR

INSTALLER
ENGINEER

RBACMNT
Privilege
SECADM

SECAUD
VIEWER

CONF_DB √ √ √ √
CONFDB_WRITE √ √
CONFSYS_READ √ √ √
CONFSYS_WRITE √ √
FIRMWARE_VIEW √ √ √
FIRMWARE_READ √ √
FIRMWARE_WRITE √ √
WEBSERVICES_ACCESS √ √ √ √ √
SSH_ACCESS √ √
OSSHELL_ACCESS √
BLSHELL_ACCESS √
SYSLOG_READ √ √ √
Pag 59
14/01/2019 User Manual – HUe

Roles

OPERATOR

INSTALLER
ENGINEER

RBACMNT
Privilege

SECADM

SECAUD
VIEWER
SYSLOG_WRITE √ √ √ √
RBAC_READ √ √
RBAC_WRITE √ √
RBACLOG_READ √ √ √
RESET_ACCESS √ √ √ √

DATA_READ √ √ √
DATA_WRITE √ √

4.2.4 Security Event Log

The HUe module contains an event log which is exclusively used for cybersecurity. This file
registers the following data:

• Events associated with the connections to the CPU.

• Modifications made to the cybersecurity policy.

This file is only accessible by a user with the adequate rights to cybersecurity options. It can be
viewed and downloaded from webApp, by clicking Diagnostics  Cybersecurity menu.
Figure 42 – Cybersecurity Log.

Pag 60
 User Manual – HUe 14/01/2019

4.3 ITB Addressing (AAP)

Inside the ITB, each acquisition block or communication block must be identified with a number.
This number is assigned with Easergy Builder when configuring the local acquisition (please see
section 5.1 ).
Once the local acquisition is defined with the configuration tool and it is transferred to the RTU, it is
necessary to define these modules’ runtime addressing. To do so, execute a so-called Automatic
Addressing Procedure (AAP) that creates a table in the memory in which the acquisition blocks
assembled physically on the ITB are associated to an address and a type. The physical
components on the system must match the configuration in Easergy Builder.

NOTICE
For AAP execution, at least one configuration needs to be loaded in the RTU; it must match the
configuration loaded in the modules that are physically installed on the ITB. For further
information about how to define and load a configuration to the RTU by using Easergy Builder,
please refer to section 5.1 .

The Automatic Addressing Procedure (AAP) must be performed every time the ITB morphology
changes, that is, every time a module is added, deleted or replaced.
The AAP procedure can be executed both automatically and manually.

Automatic Execution
For a forced execution of the AAP when the ITB is reset, switches 2 and 3 in the HUe must be set
to ON (please, see section 3.5 ).After resetting the HUe module, an AAP procedure is executed,
displaying the information about the modules that are installed and configured.
The figure shown below illustrates an example of the messages generated by the console when
AAP procedure is completed:

In this case, there is an AB_AI module with the address 1 and an AB_DI module with the address
2.
If any of these acquisition blocks which was configured previously with Easergy Builder is not
properly addressed (the “SUCCESSFUL!” message is not shown in the console), the module's
RUN led DOES NOT flash and the DIO led on HUe module remains lit.

Manual Execution
The user can force the module addressing at any time.
Log into the console with the Installer user and in BLMon prompt, execute the “claqStartAAP”
command to route the acquisition AB and the “MUX_startAAP” command for the communication
AB.

Pag 61
14/01/2019 User Manual – HUe

NOTICE
To execute the AAP procedure, the switch 2 must be set to ON.

If switch 3 is also set to ON, the entire procedure is performed automatically. Otherwise, follow
these steps:

• When executing the claqStartAAP or MUX_startAAP command, the following message

appears. Upon the execution, the screen will display each module's information (type, assigned
address, and serial number).

• The user will need to verify that all necessary modules are displayed with the text
“SUCCESSFUL!” next to them.

• To complete the procedure, the user will need to execute the claqTableAck command to
confirm that the information is correct. In this case, the addressing information is stored
permanently. If the information is not correct, then you need to execute the claqTableNack
command in order to indicate that there was an addressing problem and that the information
being displayed must be ignored

NOTICE
Only after executing the claqTableAck command, the information will be recorded permanently.

4.4 Local Acquisition

We consider local acquisition as how the system treats the HUe information received from field
devices through 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 in the same ITB, in which you only
have a HUe module (or two if the configuration is redundant).The ITB may have more than one
row of modules, but only the first row may have a CPU.

• Distributed Local Acquisition: There are several acquisition ITB's reporting information to a
single ITB. In this case, the system is configured as if all AB modules are installed in the same
physical ITB.

4.4.1 Centralized Local Acquisition

If all the acquisition blocks required to configure our ITB were not included when the RTU was
created, you can always make changes and edit the configuration individually.

Double click the Device claq in the Device hierarchy ( ).The ITB configuration window
appears.
The graph displays two acquisition blocks inherited from our RTU. You can retain them, add more
or deleted them, as desired.

Pag 62
User Manual – HUe 14/01/2019

Figure 43 – Centralized local acquisition.

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

4.4.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 44 – Distributed local acquisition

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

Pag 63
14/01/2019 User Manual – HUe

Where:

• 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.
The local acquisition is as follows for the system displayed in the figure above:

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

4.5 Treatment of Local Acquisition Signals

The claq Device is responsible for the treatment and configuration of the local acquisition signals in
Easergy Builder. This Device is created by default in any configuration of Saitel DR.
For further information about how configuring ITB and how signals are added automatically in
coreDb, please refer to Easergy Builder User Manual.
Moreover, you will see how the HUe module processes the information based on the particular
signal type.

4.5.1 General-Purpose Digital Inputs

The HUe module integrates 4 digital inputs in the lower part, which are configurable only as simple
signals. These signals are useful to inform the operator about the general faults occurred.
The digital inputs 1 and 2 can be used for the following purpose:

• Digital 1: It informs the HUe module about the polarization of the digital signals of the AB's
installed in the ITB. When the signal is active, the polarization of all digital input is correct. If
there are inactive, the HUe module will understand that a problem with the polarization has
occurred. To use this signal for this purpose, in coreDb you must configure the Supervision
Device's POL_OK_ABDI signal (please refer to section 5.9 ).

• Digital 2:Depending on its on/off state, the HUe module will understand that the ITB is
operating in LOCAL or REMOTE respectively. In LOCAL mode, the command execution will be
disabled. To use this signal, in coreDb you must configure the Supervision Device's
LOCALREMOTE signal (please refer to section 3.4.2 and 5.9 ).
If you click the graph on the HUe figure, you see that it lights up in green and the 4 general-
purpose digital Inputs available in the module are displayed.
For each signal you need to define:

• Type: Type of digital input. You can only select DI_ISIM (simple digital input) for these digital
signals in the HUe module.

• Inverse: It indicates if the signal is inverted (Y) or not (N).

• TF (ms):Filtering time to be used for the digital filtering. Expressed in milliseconds, it can range
between 0 and 255.

• TM (ms*10):Memory time to be considered for change memory. The indicated value is

expressed with 10-ms intervals, and it can range between 0 and 255.

• NChat and TChat: They have no effect on these signals and cannot be configured.

Pag 64
 User Manual – HUe 14/01/2019

For this type of signals, you need to configure “Digital Filtering” and “Change Memory”. Both
concepts are explained in further details below.

4.5.2 Field Digital Inputs

The field digital inputs can be managed with or without timestamp. In both cases, the values are 0
and 1.
The AB transmits the signal’s value to the HUe 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 problem with a polarization fault.

• Locked signal.

• Invalid time; the module is not synchronized (only for signals with timestamp).
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.
This functionality is applicable to all the points generated from digital signals, being single, double
or slow counters.
Figure 45 – Digital filtering in digital inputs.

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).
It only applies to single and double points. If the TM parameter is set to 0, this function is disabled.

Pag 65
 14/01/2019 User Manual – HUe

Figure 46 – Change memory in digital inputs

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

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.
If the settling time is set to zero, this processing will not be applied.
The following figure shows an example in which the TS does not expire, so the invalid status of the
input signals is ignored:
Figure 47 – Settling time in digital inputs

If the TS expired, the RTDB will register the signals invalid state until a new change occurs.

Pag 66
 User Manual – HUe 14/01/2019

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

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.
The figure below illustrates the anti-chattering processing diagrams:
Figure 48 – Anti-chattering in digital inputs.

The observation window slides over time:

Pag 67
 14/01/2019 User Manual – HUe

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:

The changes in the signal are continuously observed (but events are not generated).

When the TIDLE time expires (TIDLE is equal to TCHAT) 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.

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

Edge Configuration for 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.

Pag 68
 User Manual – HUe 14/01/2019

4.5.3 Digital Outputs

NOTICE
When the ITB is operating under “Local” mode, all commands received on the digital outputs
are rejected. This is not applicable for analog 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 don't
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 output can be:

• Single pulsing or latched output.

• Double pulsing or latched output.

• Single pulsing SBO.

• Double pulsing SBO.

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.

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

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 the time T expires and the command A is
completed, the module will admit the next received command.

Pag 69
 14/01/2019 User Manual – HUe

4.5.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 down. 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.
The figure below shows the range conversion.
Figure 49 – Input range in analog inputs.

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

Out-of-Range Detection
If after the conversion to engineering units (greyed area in previous figure), the system detects that
the value is higher or lower than the valid range, it will be indicated in the signal quality flag with the
corresponding bit activation.

Pag 70
 User Manual – HUe 14/01/2019

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.

4.5.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 50 – Analog output processing.

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.

Pag 71
 14/01/2019 User Manual – HUe

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 51 – Scaling to field values in analog outputs.

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

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.

Pag 72
5 Easergy Builder
14/01/2019 User Manual – HUe

Content
5 EASERGY BUILDER ............................................................................................... 73

5.1 WORKING WITH HUE IN EASERGY BUILDER ............................................................ 75

5.1.1 READING THE CONFIGURATION FROM HUE ...................................................... 76
5.1.2 CREATING A NEW CONFIGURATION IN EASERGY BUILDER ................................ 77
5.1.3 EDITING THE CONFIGURATION......................................................................... 78
5.2 CHANNEL CONFIGURATION .................................................................................... 78
5.2.1 LINK CONFIGURATION ..................................................................................... 79
5.3 SYNCHRONIZATION ................................................................................................ 80
5.4 COMMUNICATIONS ................................................................................................. 80
5.5 USING FORMULAS.................................................................................................. 81
5.6 PLC CONFIGURATION ............................................................................................ 81
5.7 SUPERVISION ......................................................................................................... 81
5.8 REDUNDANCY ........................................................................................................ 85
5.9 CONFIGURING DIGITAL INPUTS ............................................................................... 86

Pag 74
User Manual – HUe 14/01/2019

5.1 Working with HUe 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.

In Easergy Builder environment, you need to create a new RTU using the button or right-
clicking on an empty area of the RTU tree hierarchy:
Figure 52 – New RTU.

• Name: RTU's name. The name cannot be longer than 64 characters and it cannot contain the
following symbols:\, /, :, *, ?, “, <, > o |.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.

• 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.
Pag 75
14/01/2019 User Manual – HUe

Build the ITB using the buttons on the upper part of the screen.
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 HUe 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 switch 3 in the HUe module.(Please see the section 3.5 in this user
manual).
The RTU is ready for creating the different configurations with which you will work later on.

5.1.1 Reading the Configuration from HUe

If the HUe 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.

You need to know the IP address of the CPU. If you don't know this data, you can use the following
console commands:
• Use the command i if you are in the BLMon menu.
• Use ifconfig command if you are in the operating system prompt.
More information about the console in section 6.4 .
To read the existing configuration in the CPU, you need to follow the following sequence in
Easergy Builder environment:

• From the RTU tree, select the HUe RTU to which you will associate the new configuration
being read. If there is no HUe, you must create it. The selected HUe must have an accessible
IP address defined.

• Click the “Read Configuration” button, as shown below:

• Enter user and password.

• Select the configuration you want to load: Network, Environment Variables and/or
Configuration.

Pag 76
User Manual – HUe 14/01/2019

• If “Configuration” is selected, you have to choose a name for it; it will be listed in the RTU tree
under the HUe previously selected.

• The configuration is loaded and it will be available in the tree. If you checked the “Environment
Variables” and “Network” boxes, the RTU will obtain the values from the HUe being read.

5.1.2 Creating a New Configuration in Easergy Builder

To create a new configuration for the HUe, select the RTU from the tree and right-click it, or click

the button.
Figure 54 – New configuration.

Type the new configuration's name.

If “Create defined RTU acquisition points” box is checked, all local acquisition points will be
included in coreDb for each acquisition blocks included in the default configuration associated to
the RTU.
For example, if a HUe has an associated ITB that includes an AB_DI module, an AB_AI module,
and another AB_DO module, after selecting the “Create acquisition points defined in the RTU” field
when creating a new configuration, the following points will be created in coreDb:

• 16 digital inputs in Status table.

• 8 analog inputs in Analog table.

Pag 77
14/01/2019 User Manual – HUe

• 8 digital outputs in Command table.

• The supervision points of each acquisition block.

When the operation completes, the new configuration will be listed in the RTU trees. Double-click
on it and the Easergy Builder tool enters Configuration mode.

5.1.3 Editing the Configuration

The figure below illustrates the Easergy Builder environment when editing a for a HUe CPU:
Figure 55 – Editing a configuration.

The user needs to be familiar with the use of Easergy Builder, since this user manual only makes
reference to certain aspects affecting directly the configuration of the HUe module.

5.2 Channel Configuration

The ports used to communicate with field devices are configured as communication channels.
Figure 56 – Channel configuration window.

Pag 78
User Manual – HUe 14/01/2019

You can show all configuration channels in tab “Channels” of Easergy Builder.
Once created and loaded in the CPU, you can view and even modify these channels’ parameters
through webApp.
The communication ports available in HUe are:

• Ethernet Ports. You will need to define as channels all the ports you will use for
communications. These ports can have channels associated as TCP or UDP.

• Serial ports (ASYNC):

o COM1 (GPS input).
o COM2
o RS-485
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.

NOTICE
It you set the RTS control to AUTO for a specific channel:

• In COM1 and COM2, the hardware will control RTS and CTS signals. CAUTION! If the CTS
signal is not received, then there is no transmission.

• For RS-485, the control for the RTS signal and the changes between the transmission and
reception modes would be controlled by the hardware IT IS HIGHLY RECOMMENDED!!

Please refer to the Easergy Builder manual to obtain further details about how to create and define
parameters for communication channels.

5.2.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.
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 57 – Link configuration window.

Pag 79
14/01/2019 User Manual – HUe

5.3 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 HUe, you can define two synchronization channels: a primary channel and a secondary
channel, which will be used when the primary channel is not available
The 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.

• 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.4 Communications

The default configuration does not include any communication Device, since this functionality
depends on how the RTU will be used in the system. Communication Devices available for the
HUe module are:

• Master and slave IEC101

• Master and slave IEC104

• Master and slave DNP 3.0.

• Master IEC103.

• Master and slave Modbus.

• IEC61850. Client (Editions 1 and 2) and server (Edition 2)

Each Device has a dedicated user manual which detail all configuration parameters.
Pag 80
User Manual – HUe 14/01/2019

5.5 Using 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.6 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.7 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:

Pag 81
14/01/2019 User Manual – HUe

Figure 58 – Supervision signals.

In this window you can check or uncheck the available supervision points to be used for that RTU.

NOTICE
We highly recommend configuring the Supervision; besides, it is essential in redundant
configurations. The CPU itself cannot be arbitrated autonomously with the other CPU in
redundant systems, so there must be some supervision in charge of this Device.

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.
If points are not available with _A and _B suffixes in a redundant configuration, it means that you
only have information about the its value in the online CPU, for example, DOING_WELL.
The information generated by the supervision is complemented with control and diagnostic
information that is generated by each Device.
The table below shows the supervision points available for HUe:
Table 14 – Supervision points

Point Table Type Description

COLD_RST_CNT Status Source Cold start-up counter.
COM_CTS Reserved use. Do not configure.
DAY Analog Source Current day.
1  The system is redundant and it is
DB_UPDATE Status Source configured as “Hot data”. The data has been
correctly updated.
1  The source to which the point is
associated is operating properly. If you need
do not need to define a source for this point,
DOING_WELL Status Destination you must assign the value “1” as the initial
value. This signal is generally set with an
ISaGRAF® point in order to control that PLC is
operating properly.

Pag 82
User Manual – HUe 14/01/2019

Point Table Type Description

The value “1” indicates a problem in the
FAIL_CONF Status Source
configuration.
It is used with ISaGRAF®.
FAIL_PLC Status Source 1 There is no a program in the PLC or
the program has been stoped.
1  The CPU state is anomalous.0  There
are no configuration errors (FAIL_CONF = 0);
the value of DOING_WELL = 1 and all the
tasks controlled by the watchdog are working
FAIL_RTU Status Source
properly. When the value for FAIL_RTU is “0”,
pulses for RTS and DTR are generated. If a
task doesn’t reply to the watchdog, the value
for FAIL_RTU will change to 1.
1  There is a problem in the corresponding
module (FAIL_SER1 indicates a problem in
module 1, and so on).The number of points
FAIL_SER1 ...FAIL_SER4 Status Source
you can configure will depend on the number
of communication modules included in the
configuration.
1  Synchronization problem in the main
FAIL_SYNC1 Status Source
synchronization source.
1  Synchronization problem in the
FAIL_SYNC2 Status Source
secondary synchronization source.
FAIL_SYNCDESV Status Source 1  There is a delay of at least 3 seconds.
1  Hardware problem in the synchronization
FAIL_SYNCHW Status Source
source.
HOUR Analog Source Current hour.
1  Problem detected in the local acquisition.
LAQ_FAIL Status Source At least one acquisition module is out of
service or with error.
LINK:LAN1 Status Source Link status in LAN1 port.
LINK:LAN2 Status Source Link status in LAN2 port.
LINK:MNT Status Source Link status in MNT port.
Value of Digital signal 2 in HUe.
1  The system is in local mode (no
commands can be executed on the digital
LOCALREMOTE Status Source signals).
0  The system is operating in remote mode.
This is the usual state of the RTU.
(*) See note at the end of the table.
INVERTED value of Digital signal 2 in HUe.
0  The system is in local mode (no
commands can be executed on the digital
LOCALREMOTE:I Status Source signals).
1  The system is operating in remote mode.
This is the usual state of the RTU.
(*) See note at the end of the table.
MEM_USAGE Analog Source Use of RAM in %.
MINUTE Analog Source Current minute.

Pag 83
14/01/2019 User Manual – HUe

Point Table Type Description

MONTH Analog Source Current month.
NODE_A Status Source 1  CPU configured as A (Main).
NODE_B Status Source 1  CPU configured as B (Secondary).
ONLINE Status Source In a redundant system, 1  CPU is HOT.
It is used with ISaGRAF®.
PLC_WARNING Status Source 1  There are ISaGRAF® points that are not
mapped in coreDb.
1  The polarization for digital inputs is
correct.
POL_OK_ABDI Status Source 0  The polarization is not correct or the point
has not been defined in coreDb, If the point is
not defined in coreDb, then the polarization of
digital inputs is not supervised.
LOCAL state of RTU redundancy, that is, the
CPU on which the Supervision controller is
operating.
RED_I_STATE Status Source
1  The local CPU status is HOT or
STANDBY.
0  The local CPU status is in FAIL status.
GENERAL status of the redundancy in the
RTU.
1  The redundant CPU status is in FAIL
RED_IT_FAIL Status Source
status.
0  The redundant CPU status is HOT or
STANDBY.
1  The main line of the RCAP protocol does
RED_VIA1_FAIL Status Source
not work properly.
1  The secondary line of the RCAP protocol
RED_VIA2_FAIL Status Source
does not work properly.
A value higher than 0 launches a command to
RESET_RTU Command Destination
reset the RTU.
Command that restarts the system reset
RESTART_RST_COUNTER Command Destination
counter.
SECOND Analog Source Current second.
TEMP Analog Source Chip's temperature.
1  The backup supercapacitor is
WARN_BAT Status Source
disconnected.
Day of the week, considering; 0-Sunday, 1-
WDAY Analog Source
Monday, .., 6:Saturday)
YEAR Analog Source Current year.

WARNING
(*) Please do not define LOCALREMOTE and LOCALREMOTE:I simultaneously in coreDb.
Otherwise, the behavior would be unpredictable.

Pag 84
 User Manual – HUe 14/01/2019

5.8 Redundancy

You have seen that when you have two redundant CPU’s, there are certain differences in the
configuration of, 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 HUe there is redundancy only through the RCAP protocol (Redundancy Control Asynchronous
Protocol).It consists of a redundant channel between the two HUe modules that is switched when
required by means of a Schneider Electric proprietary protocol.
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 IP’s
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.

Pag 85
14/01/2019 User Manual – HUe

5.9 Configuring Digital Inputs

HUe has 4 digital inputs located in the lower left, only configurable as single inputs. These signals
are useful to inform the operator about a general problem in the system. All signals can be
configured for a general-purpose, but Digital 1 and 2 can be used with the following purpose too:

• Digital 1: This signal provides the HU module with information about the digital inputs’
polarization status of the ABs installed in the ITB. When the signal is active (1), the polarization
of all digital signals is correct. If the signal is disabled (0), the HU will understand that there is a
problem with polarization.
In order for the CPU to interpret the value of Digital 1 in this way, the supervision signal
POL_OK_ABDI must be included in coreDb.

• Digital 2: Depending on this signal is active or not, the CPU will understand that the ITB is in
LOCAL mode (signal is 1) or in REMOTE mode (signal is 0). In order for the CPU to interpret
the value of Digital 2 in this way, the supervision signal LOCALREMOTE or LOCALREMOTE:I
must be included in coreDb.

WARNING
(*) Please do not define LOCALREMOTE and LOCALREMOTE:I simultaneously in coreDb.
Otherwise, the behaviour would be unpredictable.

If you define LOCALREMOTE, when Digital 2 is 1  LOCALREMOTE is 1, the ITB is in LOCAL

mode, so the commands are not enabled in the digital output modules. If the Digital 2 signal is 0 
LOCALREMOTE is 0, the ITB is in REMOTE mode, which will be the normal operating state.
If, instead, you create the LOCALREMOTE:i point in CoreDb, this signal inverts the value of Digital
2.
The REMOTE mode is the default mode when neither LOCALREMOTE nor LOCALREMOTE:I are
included in coreDb.

Pag 86
6 Advanced Operations
14/01/2019 User Manual – HUe

Content
6 ADVANCED OPERATIONS .................................................................................... 87

6.1 BASELINE UPDATE ................................................................................................ 89

6.1.1 UPDATE BY SFTP .......................................................................................... 89
6.1.2 UPDATE BY USB ............................................................................................ 90
6.1.3 UPDATE BY WEBAPP....................................................................................... 91
6.2 AB SOFTWARE UPDATE......................................................................................... 92
6.3 OPERATING SYSTEM UPDATE (LINUX) .................................................................... 93
6.4 USING THE CONSOLE ............................................................................................. 94
6.4.1 BLMON .......................................................................................................... 94
6.4.2 GENERAL COMMANDS .................................................................................... 97
6.4.3 COMMUNICATIONS .......................................................................................... 98
6.4.4 MONITORING AND SYNCHRONIZATION COMMANDS .......................................... 99
6.4.5 LOCAL ACQUISITION COMMANDS .................................................................. 100

Pag 88
User Manual – HUe 14/01/2019

6.1 Baseline Update

You have several options to update the Baseline and/or OS in a HUe module: using a SFTP client
(for example, Filezilla), using webApp (HUe web-based tool), or using a USB pen drive connected
to the USB Host port.
You need the following:

• An Ethernet cable connected to the CPU's MNT port and PC's Ethernet port. Both need to be
connected in the same network. This wired connection is only necessary when transferring the
update file through SFTP or webApp. If using a pen drive, it would not be necessary.

• A file with the new Baseline to be installed. It will be a compressed file with a name like
“Baseline_11.06.02.tar.gz”.
The file's name containing the image must have a specific syntax:

• It must start with "Baseline_", (no case sensitivity).

• It must finish with the ".tar.gz" extension

The following names are valid, for example: BaseLine_11.04.00.tar.gz, Baseline_10.tar.gz, and
BASELINE_9.3.0.tar.gz.

6.1.1 Update by SFTP

You must install the client SFTP software in our PC to connect to the CPU. This Ethernet cable
must be connected to the MNT port. Both the CPU and our PC must be in the same subnet.
You check the connection by using the ping command in a command prompt:

Once the connection is verified, you open the FTP client software and establish connection with the
CPU using the SFTP protocol and Installer (user) and Installer1! (password).

When connection is established, you can see the /home folder. You need to change to /mnt/bf or
/mnt/flash folder and transfer the Baseline file from our PC.

Pag 89
14/01/2019 User Manual – HUe

Figure 59 – SFTP connection.

When loading is completed, press the Reset button on the CPU. If the console is available you can
see that when browsing to the Baseline file, the installation is executed directly.
Once installed, the compressed file including the Baseline image is deleted.
Finally, reboot the system and Baseline is updated.

6.1.2 Update by USB

If you want to use the USB to upgrade the system, you only need to copy the file to the USB pen
drive's root folder, connect the drive to the port and reboot the HUe.
During Linux initialization, the USB drive is installed in /mnt/usb1 and, if the file with a Baseline
image is detected, the implementation is executed automatically.
There is a slight difference after the installation with respect to the previous section:

• The target image is not deleted from the /mnt/usb1 device. Therefore, you could use the pen
drive to restore the same image in different CPU’s.

• Since the /mnt/usb1 image is not deleted, the system does not reboot. Thus, any "auto-
installation" of the same image is prevented. We recommend that, after the file's automatic
installation from the /mnt/usb1 device, you remove the pen drive and reboot the system
manually.
The priority order for the update procedure is:

• File in USB drive

• File in /mnt/bf

• File in /mnt/flash

Pag 90
User Manual – HUe 14/01/2019

6.1.3 Update by webApp

If you use a web browser, such as Chrome, you can connect to the web server using the MNT port
and indicating its IP address.

NOTICE
Considering that the connection must be secure, you will type https://192.168.2.1 in the address
bar (or the IP address associated to the MNT port).

Figure 60 – webApp.

Log in with the “Installer” user and the webApp main screen appears:

In the lower area, identified with factory information, there is information about the Baseline version
you have installed.
To install the update from the main menu, click: Maintenance  Software.
You can see the information about the versions of the modules integrated in the Software Platform
and “Install new software” button.
After clicking, you will see the following screen:

Pag 91
14/01/2019 User Manual – HUe

Figure 61 – Firmware upgrade using webApp.

• You can drag and drop the file in the designated area or you can search for it using the “Select
file” button (Step 1).

• Click the “Load” button (Step 2).

• Next, you need to confirm that the software file is correct (Step 3).

• Click the “Install new firmware”, and the software file will be sent to the CPU to install the new
firmware (Step 4).

• Then, reboot the CPU (Step 5).

• Finally, the user will need to log in again and the CPU will be ready with the new software
version.

6.2 AB Software Update

Apart from the software installed in the HUe, both the acquisition blocks and the communication
blocks have a software to be updated.
To update the ITB modules’ software you need:

• To have a console connection with HUe.

• To have a correct addressing in all ITB modules (please, see section 4.3 ).

• Update file for each type of module.

Once Baseline is installed in the HUe module, the /mnt/flash directory will include all the files
required to update any of the modules in the ITB. If you have a file with a more recent update for
any of the modules, you need to copy the file using the SFTP software in this directory.

NOTICE
To be able to execute the update commands for the ITB modules, you need to use the Installer
user to log into the console. No other user has permissions to execute these commands.

The table below shows the file you use to update each type of module and the command to be
executed by the operator in the console.

Pag 92
User Manual – HUe 14/01/2019

Table 15 – Software Update File for ITB Modules.

Module File Command Description

All *.bin claqUpgrade “all” It updates all the acquisition AB
addressed in the ITB. You need to
use the adequate file for each block.
Position <Module type>.bin claqUpgrade “<position>” It updates the acquisition AB with
the <position> address, using the
adequate file for its type.
AB_DI AB_DI.bin claqUpgrade “all AB_DI” It updates all the AB_DI modules
installed in the ITB.
AB_AI AB_AI.bin claqUpgrade “all AB_AI” It updates all the AB_AI modules
installed in the ITB.
AB_AC abaca.t00 claqDSPUpgrade “all” It updates the DSP in all the AB_AC
modules installed in the ITB.
AB_AC_A.bin claqUpgrade “all AB_AC_A” It updates the firmware in all the
AB_AC modules installed in the ITB.
AB_DO AB_DO.bin claqUpgrade “all AB_DO” It updates all the AB_DO modules
installed in the ITB.
AB_AO AB_AO.bin claqUpgrade “all AB_AO” It updates all the AB_AO modules
installed in the ITB.
AB_MIO AB_MIO.bin claqUpgrade “all AB_MIO” It updates all the AB_MIO modules
installed in the ITB.
AB_DIDO AB_DIDO.bin claqUpgrade “all AB_DIDO” It updates all the AB_DIDO modules
installed in the ITB.
AB_SER AB_SER.bin MUX_upgrade “all” It updates the firmware in all the
AB_SER modules installed in the
ITB.
AB_SER AB_SER.bin MUX_upgrade “<position>” It updates the AB_SER module with
the <position> address in the ITB.

6.3 Operating System Update (Linux)

NOTICE
Only users with advanced knowledge about the equipment should perform the tasks described
in this section.

The operating system update is executed, if required, during Baseline installation, but only if the
currently installed version is older than the version to be uploaded.
Finally, reboot the system and the baseline is updated.

NOTICE
You can force the update for the operating system even though their version is older than the
version currently installed in the system (downgrade).You need to have a file with the file named
“_KFD.tar.gz”.

Pag 93
14/01/2019 User Manual – HUe

6.4 Using the Console

The HUe operating system offers a high-priority command console to help with certain monitoring
and diagnostic tasks.
The connection to this console from the PC is established through the CON port. The section 4.1.1
in this manual describes how you can access the command console.
You need to take the following factors into account:

• The use of the command console must be restricted only to expert operators in the system.

• The command execution in the console must return a “0” character when outputted. If it returns
other values, then there has been a problem in the execution. It is usually caused by
parameters with the wrong format.

• When executing a command for any controller, it must be saved into the memory to solve this
problem, that is, the controller must be included in the configuration loaded in the CPU from
Easergy Builder.

NOTICE
Only the Device controllers included in the current configuration will be loaded into the memory.

Then, the commands available in the console for the Installer user are displayed below. To find out
the arguments that a command requires, you have used the following convention:

• (No parameters):The command must be executed directly, with no additional parameter.

• <XX>:Required parameter. It must be replaced with the XX value. The symbols <>MUST NOT
be included.

• [YY]:Optional argument. If using the argument, it must be replaced with the YY value. The
characters [] MUST NOT be included.

6.4.1 BLMon
When accessing the console with the Installer user (recommended), the BLMon menu is directly
shown. The commands in this menu are executed on the operating system's prompt. Most
commands shown below are NOT available for the rest of the users.

The BLMon menu includes the following commands:

Pag 94
User Manual – HUe 14/01/2019

Command Use
a It displays the list of the commands available to obtain information about the local acquisition. This
chapter includes more information about these commands.

b It displays the version of the Baseline software being executed.

This command is similar to “baselineShowVer”.

e It starts the monitoring of the system events.
All the events occurred will be shown in the console.
c It starts the monitoring of a communication channel.

It displays the channels configured selectable by the user. If you press “Enter” instead of a channel
number, the command is aborted.
This command is similar to “chanSniffOn”.

f It finishes the monitoring of the communication links.

This command is similar to “chlnSniffOff”.

h Using this command, you access detailed information about the system's commands.
Apart from BLMon commands, the user has other commands to be executed in the prompt.
Type the desired “FUNCTION_HELP:” command to view the following information.
If you type “a”, you will see a list of the commands available.

m It displays the BLMon menu.

Pag 95
14/01/2019 User Manual – HUe

Command Use
l It starts the monitoring of a communication link.
It is similar to the “c” command but it is for a link (association between two communication
channels).
This command is similar to “chlnSniffOn”.
o It finishes the supervision of all the channels being monitored.
This command is similar to “chanSniffOff”.
s It displays the coreDb and configuration status.

t It displays the information about the configuration and the current synchronization status.

This command is similar to “thmShow”.

u It finishes the monitoring of the system events.
v It displays the current version of the operating system.

This command is similar to “version”.

p It displays the processes being executed.

This command is similar to the operating system’s command, “ps -eTcl”.

Pag 96
User Manual – HUe 14/01/2019

Command Use
i It displays the configuration of all network interfaces.
NOTICE!! Please note that the physical name shown for each interface has the following
relationship with the Ethernet ports’ names:
Port's name (Front label) Physical name (Linux)
MNT eth2
LAN1 eth0
LAN2 eth1

This command is similar to “ifconfig” and “route”.

6.4.2 General Commands

Command Parameters / Description

coreDbShowEvents (No parameters)
It starts the monitoring of the system events.
It is similar to the e of BLMon.
coreDbShowVer (No parameters)
It shows the version of coreDb for the Baseline in the CPU.
coreDbShowState (No parameters)
It displays the coreDb and configuration status.
It is similar to the s of BLMon.
coreDbUnShowEvents (No parameters)
It finishes the monitoring of the system events.
It is similar to the u of BLMon.

Pag 97
14/01/2019 User Manual – HUe

Command Parameters / Description

baselineShowVer (No parameters)
It displays the version of the controllers loaded into the application. Please note that if
a controller is not used in the current configuration, it will not be loaded into the
memory.

6.4.3 Communications

Command Parameters / Description

chanShowVer (No parameters)
It displays information about the channel controller.

chanSniffOff (No parameters)

It deactivates the transparent mode for ALL channels.
dnpeShowVer (No parameters)
It displays information about the controller of the DNP (slave) protocol.

dnpmShowVer (No parameters)

It displays information about the controller of the DNP (master) protocol.

chlnSniffOff (No parameters)

It deactivates the transparent mode for ALL links
chlnSniffOn <Link_Name>
It activates the transparent mode for the specified link. You can use the I command of
BLMon to execute this command more easily.
Example  chlnSniffOn Link1
The operation is the same as for chanSniffOn, but for a link instead of a channel.

Pag 98
User Manual – HUe 14/01/2019

Command Parameters / Description

chanSniffOn <Channel_Name>
It activates the transparent mode for the specified channel. You can use the c
command of BLMon to execute this command more easily.
Example  chanSniffOn Channel1
You can activate this transparent mode for more than one channel at the same time.
Each message will indicate the related channel.

For this example, you see messages from channel1 and Channel485HUe.

6.4.4 Monitoring and Synchronization Commands

Command Parameters / Description

supCpuUsage (No parameters)
It shows the instantaneous usage of the CPU.
supShowVer (No parameters)
It displays the software version of the supervision controller (sup) included in the
Baseline.
thmConsoleSetTime <AA>:<MM>:<DD>:<HH><mm>:<SS>
It sets the system date and time.
<AA>: Year
<MM>: Month
<DD>: Day
<HH>: Hour
<mm>: Minute
<SS>: Second
thmShow (No parameters)
It displays the information about the configuration and the current synchronization
status. It is similar to the t of BLMon.

thmShowVer (No parameters)

It displays the software version of the synchronization controller (thm) included in the
Baseline.

Pag 99
14/01/2019 User Manual – HUe

6.4.5 Local Acquisition Commands

Command Parameters / Description

claqSniffOn [0|1] <Node Address>
0:Link layer
1:Application Layer
<Node Address> AB you request information from
It displays the communications of the link or application layer in the local acquisition
data bus. Only the messages associated to the specified node in the second
parameters are displayed.
Example of the link message:

claqHelp (No parameters)

It displays a brief explanation of the list of commands available to interact with the
Local Acquisition Device and how they can be used.

claqSniffOff (No parameters)

It finishes the local acquisition data bus.
claqStartAAP (No parameters)
It starts the ITB addressing. All module addresses are recalculated.
To execute this addressing procedure, the configuration switch 2 must be set to ON.
For further information, please refer to section 4.3
claqTableAck (No parameters)
It confirms the information displayed by the claqStartAAP command so that it is stored
permanently in the ITB addressing table.
For further information, please refer to section 4.3

claqTableNack (No parameters)

It rejects the information displayed by the claqStartAAP command. The ITB
addressing table is not updated.
For further information, please refer to section 4.3

Pag 100
User Manual – HUe 14/01/2019

Command Parameters / Description

claqShowMod <AB address>
It displays the value of all input and diagnostic signals of the module. It does NOT
show the value of the output signals.

claqTableShow (No parameters)

It shows the ITB addressing table.

claqShowEvents (No parameters)

It activates the event monitoring.
claqUnShowEvents (No parameters)
It deactivates the event monitoring.
claqForceOut <Signal’s coordinate> <Value>
It forces a digital output to a value. Where:
<Signal’s coordinate>: Local acquisition coordinate of the signal.
<Value>: Value to which you want to force the signal.
claqForceOutNTimes <Signal’s coordinate> <Number > <Time>
It forces a digital output a number of times. Where:
<Signal’s coordinate>: Local acquisition coordinate of the signal.
<Number>: Number of times the signal will be forced.
<Tiempo>: How often (in ms) the signal will be forced. Maximum: 999 ms.
claqReboot <AB address>
Reboot an AB. If the command doesn’t work, the message "fun_Reboot: Unable to
reboot AB module 3" is shown. It is recommended to wait a few seconds and retry.
claqResetBusInfo (No parameters)
Set to zero the counter of bus errors.
claqShowInfoEmerOn (No parameters)
It allows that emergency information is shown.
claqShowInfoEmerOff (No parameters)
It hides that emergency information is shown.
claqShowVer (No parameters)
It displays the software version of the local acquisition controller (claq) included in the
Baseline.
Pag 101
14/01/2019 User Manual – HUe

Command Parameters / Description

claqShow (No parameters)
It shows the status of the ITB and the status of each addressed module.

The ITB can be in any of the following status:

• BOOT_HU: Initial status after a boot of the ITB.
• CHECK_LAQ: Local acquisition wasn’t configured.
• READY_HU: The information in the addressing table is compatible with the
loaded configuration.
• RUN_AB_LIST: HUe is asking for information of the status of each AB
module.
• WAIT_HU_AAP: Error detected in the addressing procedure. Information in
the addressing table is not compatible with the loaded configuration. An AAP
procedure must be executed.
• WAIT_END_AAP: The CPU is waiting for a validation of the addressing table
(claqTableAck command).
Each AB can be in the following status:
• START_HU_IDP: The AB needs to be identified by the. An AAP must be
executed.
• STOP_HU_AB: Problem in the addressing procedure. The AB module didn’t
answer the request for information from the HU.
• VERIFIED_HU_IDP: The AB was addressed correctly and it is waiting for the
configuration.
• START_HU_AB: The AB was configured correctly and it is waiting for go to
the normal work status (RUN_HU_AB).
• RUN_HU_AB: Normal work status. It is sharing data with the CPU.

claqVersion (No parameters)

Information about the firmware version installed in each of the AB.

claqGetMIT <AB address>

Information about the tests carried out in the factory. This information includes: Type
of module, S/N of the module and boards, P/N of the module and boards, date on
which the firmware were downloaded and its version.

claqFileVersion <File>
It shows information about the software version of a file (.bin). The name of the file
must include the full path. For example:

Pag 102
User Manual – HUe 14/01/2019

Command Parameters / Description

claqDSPUpgrade [all AB_AC | all AB_AC2 | <Address>]
This command updates the DSP firmware included in the AB_AC and AB_AC_LPVT
(AB_AC2) modules. The file ".t00" with the necessary software must be available in
folder "/mnt/flash" of the CPU.
It can be used as follows:
all AB_AC: Update the DSP in all AB_AC modules.
all AB_AC2: Update the DSP in all AB_AC_LPVT modules.
<Address>: Update the module AB_AC or AB_AC_LPVT with this address. If the
module with this address in not an AB_AC or AB_AC_LPVT modules, the following
message is shown “Node to flash should be an AB_AC or AB_AC2”.
claqCheckUpgrade (No parameters)
It makes a comparison between the software files in folder "/mnt/flash" (version to
install) and the software installed in each module (currently installed). For example:

If a module is included in the addressing table, but it is not installed in the ITB, the
following message will be displayed: “Module not available”.
claqUpgrade [all | all <Type of module> | <Address>]
This command is used to update the software of the AB modules installed in the ITB.
The ".bin" file (s) with the necessary software must be available in folder "/mnt/flash".
It can be used as follows:
all: Update all modules in the ITB (included in the addressing table).
all <Type of module>: Update all the ITB modules that are of the indicated type. For
example: claqUpgrade all AB_DI.
<Address>: Update only the module with this address. For example: claqUpgrade 1.

Pag 103
14/01/2019 User Manual – HUe

Command Parameters / Description

claqJtag <File>
Be careful using this command, it can block the AB modules in the ITB!! On this
situation, each blocked AB need to be sent to the repair service!!
It restores the software of a module when it can not be addressed in the ITB. This
command must be used when the claqUpdate command doesn't work and only for
users with great knowledge of the system.
<File>: File’s name, including the path. For example:
claqJtag /mnt/flash/AB_MIO.bin.
When this command is executed, the user must BE SURE of:
• The module has a bootLoader.
• Only the AB module to be restored shall must be connected in the ITB.
• The File must be the same time of the AB to to be restored. For example, for
an AB_MIO module, the file must be AB_MIO.bin

Pag 104
7 Technical Specifications Table
14/01/2019 User Manual – HUe

Hardware Specifications
Processing unit Sitara™ AM3356BZCZD60
Technology: ARM® Cortex™-A8
Data bus: 32-bits
Clock frequency: Up to 720 MHz

External RTC DS3232 controlled by I2C

RTC accuracy ±2 ppm (0°C to +40°C)
±3.5 ppm (-40°C to +85°C)

FLASH memory (NOR) 32 MB

FLASH memory (NAND) 256 MB
Static RAM memory 2 MB
Dynamic RAM memory (DDR3) 256 MB
Assurance for static RAM Integrated supercapacitor
Autonomy in power down Up to 8 hours (+25 ºC)
Consumption 5 W Maximum
Weight 600 g
Dimensions 134 mm x 129 mm x 60 mm
Coating AVR80 (Depending on P/N)
Protection degree IP20
Range of temperature Operation: From -40º C to +70º C
Storage: From -40º C to +125º C

Interfaces
Power supply (POWER) Voltage range 24 – 48 VDC (±20%)
3-pole terminal block
Wire: 2.5 mm² (13 AWG)
Console port (CON) RS-232 communications
Mini-USB connector
Serial port (RS-485) RS-485 communications
3-pole connector, with isolation
Wire: 1.5 mm² (15 AWG)
Serial port (COM1) RS-232 communications
Male DB9 connector, without isolation
Modem control (full)
GPS port

Serial port (COM2) RS-232 communications

Male DB9 connector, without isolation
Modem control (only RTS and CTS)
USB port 2.0 (Host)
SD card Up to 32 GB
Auxiliary digital inputs (AUX DI) 5-pole terminal block with isolation
4 digital inputs for general purpose

IRIG-B 2-pole terminal block with isolation

1.5 mm² (15 AWG)
External watchdog (WD) Maximum capacity of current: 200 mA max (25 ºC)
2-pole terminal block with isolation
1.5 mm² (15 AWG)
Pag 106
User Manual – HUe 14/01/2019

Interfaces
Ethernet port (MNT) Fast-Ethernet 10/100BaseT
RJ-45 connector
Ethernet ports (LAN1 and LAN2) Fast-Ethernet 10/100BaseT
(Copper)
Connector RJ-45
Ethernet ports (LAN1 and LAN2) Fast-Ethernet 100Base-FX
(Fiber Optic) Recommended transceivers for FO:

• HFBR-57E0PZ (From 0º C to +70º C)

• HFBR-57E0APZ (From -40º C to +85º C)

Communication with other modules Internal bus (power, data, synchronization, …)

Software
Operating System Linux
External synchronization GPS
IRIG-B
Protocol
Console
PTP
IRIG-B TTL input signal
Protocols: IRIG-B002, IRIG-B003, IRIG-B006 and IRIG-B007
Discrimination time for events 1 ms
Watchdog software Internal
Security control Cybersecurity brick included
Embedded firewall
Secured interfaces
User management based on a RBAC model

Cybersecurity
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

Ordering Options

Pag 107
14/01/2019 User Manual – HUe

CE Mark
Standards, Directives and LVD – Low Voltage Directive Directive 2014/35/UE
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 108
 User Manual – HUe 14/01/2019

Index of Figures
Figure 1 - Barrier of protection for elements with high 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 – Communication between HUe and ABs. ..................................................................................................19

Figure 8 – coreDb operation example. .......................................................................................................................21

Figure 9 – Basic ITB. .................................................................................................................................................22

Figure 10 – Basic ITB. ...............................................................................................................................................22

Figure 11 – Module interconnection. .........................................................................................................................22

Figure 12 – Bus expansion between rows.................................................................................................................23

Figure 13 – microRTU. ..............................................................................................................................................23

Figure 14 – Small / Medium size RTU. ......................................................................................................................24

Figure 15 – Large size RTU with distributed acquisition. ..........................................................................................24

Figure 16 – Distributed Acquisition and control system / Processing Redundancy ..................................................25

Figure 17 – Baseline Software Platform ....................................................................................................................26

Figure 18 – Relation between coreDb and other applications...................................................................................26

Figure 19 – Mount bracket on DIN rail. ......................................................................................................................31

Figure 20 – Saitel DR module on a DIN rail. .............................................................................................................32

Figure 21 – HUe front view. .......................................................................................................................................32

Figure 22 – Electronic boards in HUe. .......................................................................................................................33

Figure 23 – Part Number description. ........................................................................................................................34

Figure 24 – Analog signals wiring. .............................................................................................................................35

Figure 25 – Main power and polarization wiring. .......................................................................................................36

Figure 26 – Wrong connection of the polarization power supply...............................................................................36

Figure 27 – General scheme of a correct ground connection. ..................................................................................37

Figure 28 – General scheme of an incorrect ground connection. .............................................................................37

Figure 29 – Power and Reset. ...................................................................................................................................38

Figure 30 – General-purpose digital inputs. ..............................................................................................................39

Figure 31 – Serial communication ports. ....................................................................................................................40

Figure 32 –Pinout of the cable for redundancy..........................................................................................................41

Figure 33 –Ethernet communication ports.................................................................................................................42

Figure 34 –IRIG-B and WD output connectors. .........................................................................................................44

Pag 109
 14/01/2019 User Manual – HUe

Figure 35 – Slot for SD card and USB connector. ......................................................................................................44

Figure 36 – Expansion bus connector. ......................................................................................................................44

Figure 37 – Configuration Switches. ..........................................................................................................................45

Figure 38 – LED indicators ........................................................................................................................................46

Figure 39 – Network Interface Settings. ....................................................................................................................53

Figure 40 – Using routers to configure subnets.........................................................................................................54

Figure 41 – Managing users in HUe. .........................................................................................................................58

Figure 42 – Cybersecurity Log...................................................................................................................................60

Figure 43 – Centralized local acquisition. ...................................................................................................................63

Figure 44 – Distributed local acquisition ....................................................................................................................63

Figure 45 – Digital filtering in digital inputs. ...............................................................................................................65

Figure 46 – Change memory in digital inputs ............................................................................................................66

Figure 47 – Settling time in digital inputs ...................................................................................................................66

Figure 48 – Anti-chattering in digital inputs. ..............................................................................................................67

Figure 49 – Input range in analog inputs. ..................................................................................................................70

Figure 50 – Analog output processing. ......................................................................................................................71

Figure 51 – Scaling to field values in analog outputs. ...............................................................................................72

Figure 52 – New RTU. ...............................................................................................................................................75

Figure 53 – Configuring the ITB.................................................................................................................................75

Figure 54 – New configuration. ..................................................................................................................................77

Figure 55 – Editing a configuration. ...........................................................................................................................78

Figure 56 – Channel configuration window. ..............................................................................................................78

Figure 57 – Link configuration window. .....................................................................................................................79

Figure 58 – Supervision signals.................................................................................................................................82

Figure 59 – SFTP connection. ...................................................................................................................................90

Figure 60 – webApp. ..................................................................................................................................................91

Figure 61 – Firmware upgrade using webApp...........................................................................................................92

Pag 110
 User Manual – HUe 14/01/2019

Index of Tables
Table 1 – Symbols ........................................................................................................................................................9

Table 2 – Wiring groups ..............................................................................................................................................34

Table 3 – Pinout of COM1 ..........................................................................................................................................40

Table 4 – Pinout of COM2 ..........................................................................................................................................41

Table 5 – Pinout of the console port. ..........................................................................................................................42

Table 6 – 2-wire RS-485 to DB9 .................................................................................................................................42

Table 7 – Pinout of the copper ports. .........................................................................................................................43

Table 8 – LED indicators. ...........................................................................................................................................46

Table 9 – Default IP Addresses. .................................................................................................................................50

Table 10 – Default users.............................................................................................................................................50

Table 11 – Default users.............................................................................................................................................57

Table 12 – Default roles ..............................................................................................................................................58

Table 13 – User’s privileges. ......................................................................................................................................59

Table 14 – Supervision points ....................................................................................................................................82

Table 15 – Software Update File for ITB Modules......................................................................................................93

Pag 111
14/01/2019 User Manual – HUe

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: Communication port.
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 112
User Manual – HUe 14/01/2019

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.
HU_B: Saitel DR Basic Head Unit.
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 113
14/01/2019 User Manual – HUe

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.
SFTP: Secure File Transfer Protocol.
SNTP: Simple Network Time Protocol.
SRAM: Static Random Access Memory.
SSH: Secure SHell.

T
TCP/IP: Transmission Control Protocol/Internet 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 114
User Manual – HUe 14/01/2019

Pag 115
 Printed in:

Tuesday, March 5, 2019

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-M588-USR-01 01/2019

Pag 116